EP1625687A1 - Systeme d'evaluation de risques de securite - Google Patents
Systeme d'evaluation de risques de securiteInfo
- Publication number
- EP1625687A1 EP1625687A1 EP03729010A EP03729010A EP1625687A1 EP 1625687 A1 EP1625687 A1 EP 1625687A1 EP 03729010 A EP03729010 A EP 03729010A EP 03729010 A EP03729010 A EP 03729010A EP 1625687 A1 EP1625687 A1 EP 1625687A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- application
- computer
- security
- trust
- readable medium
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/51—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/55—Detecting local intrusion or implementing counter-measures
- G06F21/56—Computer malware detection or handling, e.g. anti-virus arrangements
- G06F21/566—Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
Definitions
- the present invention relates to computer security systems. More particularly, the present invention relates to a mechanism for evaluating and aggregating security assessment information for computing systems.
- Computer users today have access to a multitude of different applications and utilities.
- the typical computer user may install dozens of computer programs on a computer over the course of a year.
- a user may install a program unknowingly, such as by visiting a particular Web site that is configured to install an applet or small program on the users computer.
- Installing programs on computers has become so commonplace today that some users are unaware of the security issues involved with installing new software. Other users are keenly aware of the security issues in general, but are typically uncertain about the particular issues that may surround installing a particular program.
- each security utility operates separately from each other and without knowledge of each other's results, thus burdening the user with assimilating the information from each security utility.
- Security systems today operate in a vacuum with respect to each other, and each reports to the user only on its specific security risk. Most users do not want separate notifications of different security risks from several disparate systems. Rather, they want their security systems just to work.
- the patchwork nature of security utilities today typically leaves users in fear that they have left a hole in their defenses, and that malicious or undesirable programs will slip through. Because of that fear, many users are reluctant to try new programs, especially in online environments.
- the present invention is directed at a system and method for accumulating security assessment information about a program and operating on that information in a convenient and usable fashion.
- a hosting environment is responsible for loading an application.
- the hosting environment invokes a trust manager to evaluate any security risks associated with that application.
- the trust manager invokes a plurality of trust evaluators, where each trust evaluator is responsible for analyzing and assessing a different security risk.
- results of those individual security risk evaluations are returned to the trust manager.
- the trust manager aggregates the variety of security risk evaluation results and makes a security determination based on the aggregated evaluation results.
- That determination may be to move forward with loading the application, to block the load of the application, or perhaps to prompt the user for a decision about whether to move forward with the load.
- the user can make a decision based on the collective security assessment of the application, which provides the user with a greater sense of protection about his computer system in general.
- FIGURE 1 is a functional block diagram that illustrates a computing device that may be used in implementations of the present invention.
- FIGURE 2 is a functional block diagram generally illustrating components of a system for performing a security evaluation of an application and for presenting a user with a collective security assessment of that evaluation.
- FIGURE 3 is a graphical representation of one illustrative grant set for an application that associates particular permissions with components of the application in the context of the application.
- FIGURE 4 is a graphical representation of one illustrative user interface that may be used to present collective security assessment information to a user.
- FIGURE 5 is a logical flow diagram generally illustrating a process for evaluating the security risks associated with an application and for presenting to a user the collective security assessment.
- FIGURE 1 illustrates a computing device that may be used in illustrative implementations of the present invention.
- computing device 100 In a very basic configuration, computing device 100 typically includes at least one processing unit 102 and system memory 104.
- system memory 104 may be volatile (such as RAM), non- volatile (such as ROM, flash memory, etc.) or some combination of the two.
- System memory 104 typically includes an operating system 105, one or more program modules 106, and may include program data 107. This basic configuration of computing device 100 is illustrated in FIGURE 1 by those components within dashed line 108.
- Computing device 100 may have additional features or functionality.
- computing device 100 may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape.
- additional storage is illustrated in FIGURE 1 by removable storage 109 and non-removable storage 110.
- Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data.
- System memory 104, removable storage 109 and non-removable storage 110 are all examples of computer storage media.
- Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks ("DVD”) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computing device 100. Any such computer storage media may be part of device 100.
- Computing device 100 may also have input device(s) 112 such as keyboard 122, mouse 123, pen, voice input device, touch input device, scanner, etc.
- Output device(s) 114 such as a display, speakers, printer, etc. may also be included. These devices are well known in the art and need not be discussed at length here.
- Computing device 100 may also contain communication connections 116 that allow the device to communicate with other computing devices 118, such as over a network.
- Communication connections 116 is one example of communication media.
- Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media.
- modulated data signal means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
- communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
- the term computer readable media as used herein includes both storage media and communication media.
- FIGURE 2 is a functional block diagram generally illustrating components of an environment implementing the present invention.
- a trust evaluation system 200 is configured to evaluate an application 201 and identify any security risks associated with the application 201.
- the application 201 may be any executable code that is available to the computing device 100. There are inherently some security risks associated with executing the application 201 on the computing device 100. For instance, the application 201 may contain a virus or it may constitute spyware. Accordingly, the system 200 is configured to analyze the application 201 to assess and quantify those risks in a meaningful way. The trust evaluation system 200 then makes a decision about loading the application 201.
- the application 201 may be composed of several components operating in conjunction.
- the application 201 may include multiple modules or assemblies, such as assembly A 202 and assembly B 203.
- the application 201 may include metadata that describes the application and each of its constituent components. That metadata may be contained in a manifest 205 or otherwise stored in association with the application 201.
- the metadata may include information such as the name of the application, the version of the application, what rights and permissions the constituent components of the application desire, privacy policy information, digital signature information, and the like.
- the application 201 may be first loaded onto the computing device 100 in one of many ways.
- the application 201 may be downloaded during an Internet session, it may be obtained on an optical disk or other permanent storage, it may be received in an e-mail message, or through some other mechanism.
- the application 201 is loaded by and executed in a hosting environment 220.
- the hosting environment 220 includes any environment in which the application 201 will be executed.
- the hosting environment 220 may be a managed code runtime environment, a shell, another application, or the like.
- the hosting environment 220 may include a priority rating based on the type of host it is.
- the hosting environment 220 is configured to create an Application
- the hosting environment 220 includes in the ADO 221 sufficient information about the application 201 to effectively evaluate the security risks associated with the application 201. Accordingly, the ADO 221 may include, in object form, the name of the application, the version of the application, what rights and permissions the constituent components of the application desire, privacy policy information, digital signature information, and the like.
- the hosting environment 220 is further configured to invoke a Trust Manager 210 to perform the evaluation.
- the Trust Manager 210 may be a trusted component of an operating system resident on the computing device 100.
- the Trust Manager 210 exposes an interface that is called by the hosting environment 220 to initiate the security evaluation of the application 201.
- the Trust Manager 210 receives the ADO 221 from the hosting environment 220 via the interface.
- the Trust Manager 201 is further configured to invoke a series of trust evaluation engines to assess the security risk associated with the application 201.
- Each evaluation engine is configured to evaluate a particular class of threat based on information in the ADO 221 or on the components of the application 201 itself.
- evaluation engine 240 may be a scoring engine that evaluates evidence about the application, as may be contained in the ADO 221 or elsewhere, to determine the ability of the application to perform malicious acts on the computing device 100.
- Evaluation engine 241 may be a virus checker and evaluation engine 242 may be configured to evaluate privacy concerns about the application 201.
- Each of the evaluation engines may derive from a base class, or may be implemented as an interface.
- Each evaluation engine is configured to assess the application 201 against its particular rules or criteria to determine a score 245. Examples of the score include a numerical value between a minimum and maximum, or a discrete value from a set of alternative security levels. These are only examples and not an exhaustive list.
- the score 245 may then be returned to the Trust Manager 210 by each evaluation engine at the conclusion of its assessment.
- the Trust Manager 210 is configured to aggregate the individual scores into a score collection 250, which represents the collective security assessment of the application in each of the areas for which an evaluation engine exists.
- the Trust Manager 210 may have sufficient information to make a loading decision without involving the user. For instance, pre-determined thresholds (either set by default or perhaps provided by the user) may govern what programs are loaded without seeking user acceptance, or what programs are blocked without prompting the user. If the collective security assessment for the particular application being loaded falls between those two thresholds, the user may be prompted for a loading decision.
- the Trust Manager 210 constructs a Trust Object 261 that describes the level of permissions with which the application will be loaded, if at all.
- the Trust Object 261 may include data that defines a permission grant set 262 for the application on a component-by-component basis.
- a permission grant set 262 for the application on a component-by-component basis.
- One example of an illustrative permission grant set 262 is illustrated in Figure 3 and described below. If the collective security assessment for the application 201 falls between the two thresholds mentioned above, the Trust Manager 210 may pass the Trust Object 261 to a User Interface 260 so that the user may be prompted.
- the User Interface 260 is a mechanism for presenting the collective security assessment to the user in a meaningful way so that the user can make an informed decision about proceeding.
- the User Interface 260 may take many forms, such as a dialog box, an audible signal, an iconic indicator, or the like.
- a potential User Interface 260 is illustrated in Figure 4 and described below.
- the User Interface 260 may prompt the user with the potential security ramifications of allowing the application load to proceed, and possibly presenting the user with various levels of permissions that may be assigned to the application. The user is asked to make a determination whether to proceed with loading the application or not.
- the User Interface 260 adds the user's response information to the Trust Object 261 and returns it to the Trust Manager 210.
- the Trust Manager 210 may return that grant set 262 to the hosting environment 220.
- the hosting environment 220 could cache the security assessment information for subsequent use without involving the Trust Manager 210.
- the hosting environment 220 will then apply any access permissions identified in the grant set 262 to the application 201. More specifically, the hosting environment 220 may apply the access permissions to each individual component, such as assembly A 202, of the application 201. It is equally feasible that the hosting environment 220 or some other application may present a component to the Trust Manager 210 for a security assessment without the specific intent of then executing the component.
- FIGURE 3 is a graphical representation of one illustrative grant set 301 that may be generated by implementations of the present invention.
- the term "grant set,” as used in this document means any collection of information that is used to define the security environment in which an application may execute.
- the term "grant set” used in this document is not limited to a particular security environment, such as a Common Language Runtime environment, but rather is intended to cover information used to define the security environment within which an application executes regardless of the particular operating environment.
- the grant set 301 may be data within an object, such as a Trust Object or the like.
- the grant set 301 includes information that identifies each component of the application.
- the grant set 301 includes information that defines the permissions for each component of the application.
- a components table 310 identifies the components Assembly A, Assembly B, and Assembly C and associates each of those components with a permission set.
- Assembly A is identified as having permission set PSI.
- a permissions table 320 is also included in the grant set 301 to define specifically those permissions are security rights that are associated with each permission set.
- permission set PSI includes those permissions and rights identified in the example as Permissions 1. It will be appreciated that, as described above, when the hosting environment 220 begins to load the components of the application, by referring to the grant set 301 the appropriate permissions may be applied to each component of the application in the context of the application.
- some other application may also include Assembly B, but in the context of that other application, Assembly B may have a different permission set. In that case, when the other application was executed, and Assembly B was loaded, it would have the permission set defined by a grant set associated with the other application.
- FIGURE 4 is an illustrative User Interface dialogue that may be presented to a user based on a security assessment of an application.
- the dialog 401 is presented based on an evaluation of an application that has requested access to the file system and the network, hi addition, a virus evaluator has determined that the application does not contain a virus, h iconic indication of the risk level 405 may also be included.
- the user is presented with the option of allowing the load to proceed, such as by clicking an OK button 410, or to abort the load.
- the User Interface shown in FIGURE 4 is for the purpose of illustration only, and is not to be viewed as limiting or the exclusive mechanism for presenting security information to the user.
- FIGURE 5 is a logical flow diagram generally illustrating a process for identifying and collectively presenting, in meaningful way, information about security risks posed by an application.
- the process begins at starting block 501, where an application is being loaded for execution on a computing system.
- an application may be loaded in many ways through various types of hosts. Accordingly, at starting block 501, a particular application is being loaded through use of a particular host.
- the process continues at block 503.
- the host constructs an Application Description Object (ADO) based on information about the application.
- ADO Application Description Object
- the information may be obtained from a manifest included with the application, or through any other metadata associated with the application.
- the ADO contains descriptive information about the application, such as the name and version of the application, any rights being requested by the application, any code access permissions being requested by the application, digital signature information related to the application, privacy policy information, and the like.
- the host invokes a Trust Manager with an instruction to evaluate the security risks associated with the application.
- the host passes the ADO to the Trust Manager for use in the evaluation.
- the Trust Manager begins evaluating the security risks of the application by invoking a series of Trust Evaluators that each evaluate a specific area of security risk. For instance a virus evaluator may be configured to examine each component of an application for the possibility that the application contains a virus. A privacy evaluator may evaluate the permissions requested by the application to determine what level of threat to privacy the application presents. Many other Trust Evaluators may also be used, as will be apparent to those skilled in the art.
- Loop 508 is performed for each Trust Evaluator in the system.
- the Loop 508 begins at block 509, where the current Trust Evaluator examines the information in the ADO and/or the components of the application to assess the security risk.
- the information in the ADO may be compared against a set of rules or other criteria to build a score that quantifies the security risk of the application.
- a score may be a value from zero (maximum risk) to one (minimum risk).
- the score may also include a priority and a string descriptor.
- each Trust Evaluator assesses its respective security risk and returns the score collection to the Trust Manager (block 511).
- the loop 508 terminates and the process continues to block 513.
- the Trust Manager analyzes the score collections from the Trust Evaluators.
- the Trust Manager may prioritize the score collections based on some pre-determined criteria, such as a priority associated with a particular Trust Evaluator, or some other prioritization scheme. For instance, a high risk that a virus is present may outweigh a low risk that a privacy violation may occur.
- the Trust Manager determines, from the prioritized score collections, an aggregate security impact on the computing system. If the aggregate security impact on the system exceeds some pre-determined threshold, the Trust Manager may simply block the load of the application. If the aggregate security impact is below some other threshold, the Trust Manager may simply build a Trust Object that includes sufficient permissions for the application to execute. If however, neither of these cases exists, the Trust Manager may invoke a User Interface to prompt the user to make the determination.
- the Trust Manager passes the prioritized score collection and aggregate impact information to the User Interface for final evaluation if required from the user. If so, the aggregate security impact is presented to the user.
- the presentation may be in the form of a dialog box that summarizes or details specifically the security risks associated with loading the application. For instance, a scoring engine may have determined that the application has requested sufficient permissions to read and modify files on the computer, and to transmit data over a network connection. Based on that information, together with perhaps other evidence, a privacy evaluator may have determined that the application is likely to share the user's information over the network. Accordingly, that information may be combined to inform the user that loading the application is likely to result in the user being targeting by telemarketing campaigns or other inappropriate uses of the user's personal information.
- the user is presented with disparate security information collected into a common notification, such as a dialog box or the like.
- the Trust Manager modifies the Trust Object to describe the security environment in which the application may be executed.
- the Trust Object includes data that associates the application, or components of the application, with a permission grant set.
- the permission grant set describes the level of security that will be applied to the application when executed.
- a permission grant set is associated with each component of the application. In that way, a component that is shared among different applications may be executed with different permissions depending on the application context in which it is executing.
- the process may idle at block 517 until the application is actually executed, thereby causing the host to begin loading components of the evocation. At that point, the process continues to block 519.
- the application is being loaded by the host.
- the host queries the Trust Manager for the Trust Object associated with the application.
- the permission grant set associated with that component is applied, hi this way, applications that have been loaded in accordance with the invention are only allowed those permissions which the user has, in an informed way, directly and comprehensively established. If sufficient privileges to execute have not been granted to the application, the Trust Manager may block the execution of the application.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Virology (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Storage Device Security (AREA)
Abstract
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/US2003/015709 WO2004107647A1 (fr) | 2003-05-17 | 2003-05-17 | Systeme d'evaluation de risques de securite |
US10/440,518 US8156558B2 (en) | 2003-05-17 | 2003-05-17 | Mechanism for evaluating security risks |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1625687A1 true EP1625687A1 (fr) | 2006-02-15 |
EP1625687A4 EP1625687A4 (fr) | 2011-11-23 |
Family
ID=34118079
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP03729010A Withdrawn EP1625687A4 (fr) | 2003-05-17 | 2003-05-17 | Systeme d'evaluation de risques de securite |
Country Status (10)
Country | Link |
---|---|
US (1) | US8156558B2 (fr) |
EP (1) | EP1625687A4 (fr) |
JP (2) | JP2006526193A (fr) |
KR (1) | KR100968003B1 (fr) |
CN (1) | CN1618198A (fr) |
AU (1) | AU2003233574B9 (fr) |
BR (1) | BR0307030A (fr) |
CA (1) | CA2472366A1 (fr) |
MX (1) | MXPA04007406A (fr) |
WO (1) | WO2004107647A1 (fr) |
Families Citing this family (90)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2472366A1 (fr) * | 2003-05-17 | 2004-11-17 | Microsoft Corporation | Mecanisme d'evaluation des risques de securite |
GB2403309B (en) * | 2003-06-27 | 2006-11-22 | Hewlett Packard Development Co | Apparatus for and method of evaluating security within a data processing or transactional environment |
US8214906B2 (en) * | 2003-10-21 | 2012-07-03 | International Business Machines Corporation | System, method and program product to determine security risk of an application |
JP2005316890A (ja) * | 2004-04-30 | 2005-11-10 | Sony Corp | プログラム、コンピュータ、データ処理方法、通信システムおよびその方法 |
US7774824B2 (en) * | 2004-06-09 | 2010-08-10 | Intel Corporation | Multifactor device authentication |
KR20060030993A (ko) * | 2004-10-07 | 2006-04-12 | 한국전자통신연구원 | 정보 자산의 보안 수준 분석 방법 |
US7600256B2 (en) | 2005-02-04 | 2009-10-06 | Microsoft Corporation | Security critical data containers |
US8117640B1 (en) * | 2005-02-23 | 2012-02-14 | Mark Moriconi | Systems and methods for analyzing application security policies |
US8359645B2 (en) * | 2005-03-25 | 2013-01-22 | Microsoft Corporation | Dynamic protection of unpatched machines |
US7685149B2 (en) * | 2005-03-28 | 2010-03-23 | Microsoft Corporation | Identifying and removing potentially unwanted software |
US8516583B2 (en) | 2005-03-31 | 2013-08-20 | Microsoft Corporation | Aggregating the knowledge base of computer systems to proactively protect a computer from malware |
US8060860B2 (en) * | 2005-04-22 | 2011-11-15 | Apple Inc. | Security methods and systems |
US20060259967A1 (en) * | 2005-05-13 | 2006-11-16 | Microsoft Corporation | Proactively protecting computers in a networking environment from malware |
US20070028300A1 (en) * | 2005-07-28 | 2007-02-01 | Bishop Ellis E | System and method for controlling on-demand security |
US20070124803A1 (en) * | 2005-11-29 | 2007-05-31 | Nortel Networks Limited | Method and apparatus for rating a compliance level of a computer connecting to a network |
US7725325B2 (en) * | 2006-01-18 | 2010-05-25 | International Business Machines Corporation | System, computer program product and method of correlating safety solutions with business climate |
US8572381B1 (en) * | 2006-02-06 | 2013-10-29 | Cisco Technology, Inc. | Challenge protected user queries |
US8270941B2 (en) | 2006-02-24 | 2012-09-18 | Qualcomm Incorporated | System and method for downloading user interface components to wireless devices |
US20070204167A1 (en) * | 2006-02-28 | 2007-08-30 | Aladdin Knowledge Systems Ltd. | Method for serving a plurality of applications by a security token |
JP4434169B2 (ja) * | 2006-03-30 | 2010-03-17 | ブラザー工業株式会社 | 情報処理装置、及び、プログラム |
US7793110B2 (en) * | 2006-05-24 | 2010-09-07 | Palo Alto Research Center Incorporated | Posture-based data protection |
CN100423494C (zh) * | 2006-06-13 | 2008-10-01 | 南京大学 | 一种基于依赖关系的信息技术产品安全保证评估流程生成方法 |
CN100409622C (zh) * | 2006-06-13 | 2008-08-06 | 南京大学 | 一种基于依赖关系的信息技术产品安全保证评估流程控制方法 |
US8117441B2 (en) * | 2006-06-20 | 2012-02-14 | Microsoft Corporation | Integrating security protection tools with computer device integrity and privacy policy |
US8959568B2 (en) * | 2007-03-14 | 2015-02-17 | Microsoft Corporation | Enterprise security assessment sharing |
US20090019170A1 (en) * | 2007-07-09 | 2009-01-15 | Felix Immanuel Wyss | System and method for secure communication configuration |
AU2008281314A1 (en) * | 2007-07-30 | 2009-02-05 | Michael Kefaloukos | A computer-implemented security method and system |
US8037536B2 (en) * | 2007-11-14 | 2011-10-11 | Bank Of America Corporation | Risk scoring system for the prevention of malware |
US10318730B2 (en) * | 2007-12-20 | 2019-06-11 | Bank Of America Corporation | Detection and prevention of malicious code execution using risk scoring |
US8136164B2 (en) * | 2008-02-27 | 2012-03-13 | Microsoft Corporation | Manual operations in an enterprise security assessment sharing system |
US8532978B1 (en) * | 2008-10-31 | 2013-09-10 | Afrl/Rij | Natural language interface, compiler and de-compiler for security policies |
US8156388B2 (en) * | 2008-11-24 | 2012-04-10 | Symbol Technologies, Inc. | Analysis leading to automatic action |
US8336080B2 (en) * | 2009-06-26 | 2012-12-18 | Symbol Technologies, Inc. | Methods and apparatus for rating device security and automatically assessing security compliance |
CN106097107B (zh) | 2009-09-30 | 2020-10-16 | 柯蔼文 | 用于社交图数据分析以确定社区内的连接性的系统和方法 |
JP5333141B2 (ja) * | 2009-10-09 | 2013-11-06 | ソニー株式会社 | 情報処理装置および方法、並びにプログラム |
US20110099164A1 (en) | 2009-10-23 | 2011-04-28 | Haim Zvi Melman | Apparatus and method for search and retrieval of documents and advertising targeting |
US20130042298A1 (en) | 2009-12-15 | 2013-02-14 | Telefonica S.A. | System and method for generating trust among data network users |
WO2011106897A1 (fr) | 2010-03-05 | 2011-09-09 | Chrapko Evan V | Systèmes et procédés permettant de procéder à des évaluations plus fiables avec des statistiques de connectivité |
WO2011134086A1 (fr) | 2010-04-30 | 2011-11-03 | Evan V Chrapko | Systèmes et procédés pour effectuer des évaluations fiables à l'aide d'informations de connectivité |
US8413249B1 (en) * | 2010-09-30 | 2013-04-02 | Coverity, Inc. | Threat assessment of software-configured system based upon architecture model and as-built code |
JP5651065B2 (ja) * | 2011-04-08 | 2015-01-07 | Kddi株式会社 | アプリケーション評価装置およびプログラム |
US8656465B1 (en) * | 2011-05-09 | 2014-02-18 | Google Inc. | Userspace permissions service |
US8646100B2 (en) | 2011-06-03 | 2014-02-04 | Apple Inc. | Method for executing an application in a restricted operating environment |
CN102890629B (zh) * | 2011-07-21 | 2017-07-21 | 富泰华工业(深圳)有限公司 | 具有操作提示功能的电子装置及操作提示方法 |
KR101326896B1 (ko) * | 2011-08-24 | 2013-11-11 | 주식회사 팬택 | 단말기 및 이를 이용하는 어플리케이션의 위험도 제공 방법 |
CN102521549A (zh) * | 2011-11-28 | 2012-06-27 | 宇龙计算机通信科技(深圳)有限公司 | 一种应用程序安全预判装置及方法 |
WO2013097026A1 (fr) | 2011-12-28 | 2013-07-04 | Chrapko Evan V | Systèmes et procédés de visualisation de graphes de réseaux sociaux |
US8978094B2 (en) * | 2012-02-03 | 2015-03-10 | Apple Inc. | Centralized operation management |
US9443086B2 (en) | 2012-02-23 | 2016-09-13 | Infosys Limited | Systems and methods for fixing application vulnerabilities through a correlated remediation approach |
KR101308351B1 (ko) * | 2012-02-24 | 2013-09-17 | 주식회사 팬택 | 어플리케이션에 권한을 할당하는 단말기 및 상기 단말기의 권한 할당 방법 |
US20130254880A1 (en) * | 2012-03-21 | 2013-09-26 | Mcafee, Inc. | System and method for crowdsourcing of mobile application reputations |
CN103368987B (zh) * | 2012-03-27 | 2017-02-08 | 百度在线网络技术(北京)有限公司 | 云服务器、应用程序的审核认证及管理系统和方法 |
CN103366118A (zh) * | 2012-04-06 | 2013-10-23 | 腾讯科技(深圳)有限公司 | 进行安装包病毒查杀的方法及装置 |
US9626503B2 (en) | 2012-11-26 | 2017-04-18 | Elwha Llc | Methods and systems for managing services and device data |
US10216957B2 (en) | 2012-11-26 | 2019-02-26 | Elwha Llc | Methods and systems for managing data and/or services for devices |
US9749206B2 (en) | 2012-10-30 | 2017-08-29 | Elwha Llc | Methods and systems for monitoring and/or managing device data |
US9886458B2 (en) | 2012-11-26 | 2018-02-06 | Elwha Llc | Methods and systems for managing one or more services and/or device data |
US9088450B2 (en) | 2012-10-31 | 2015-07-21 | Elwha Llc | Methods and systems for data services |
US10091325B2 (en) | 2012-10-30 | 2018-10-02 | Elwha Llc | Methods and systems for data services |
CN103853975A (zh) * | 2012-11-28 | 2014-06-11 | 联想(北京)有限公司 | 一种信息处理方法及电子设备 |
US8613094B1 (en) * | 2012-12-17 | 2013-12-17 | Google Inc. | Using a honeypot workflow for software review |
US9268940B1 (en) * | 2013-03-12 | 2016-02-23 | Symantec Corporation | Systems and methods for assessing internet addresses |
CN104217155A (zh) * | 2013-05-30 | 2014-12-17 | 宁夏新航信息科技有限公司 | 一种对计算机软件进行保护的方法和装置 |
US9323931B2 (en) * | 2013-10-04 | 2016-04-26 | Bitdefender IPR Management Ltd. | Complex scoring for malware detection |
US11218507B2 (en) * | 2013-10-18 | 2022-01-04 | Nokia Technologies Oy | Method and system for operating and monitoring permissions for applications in a electronic device |
US20150235025A1 (en) * | 2014-02-20 | 2015-08-20 | Mark Mundy | Process to prevent malicious changes to electronic files on an electronic storage device |
CA2955457A1 (fr) * | 2014-07-14 | 2016-01-21 | Iota Security Inc. | Systeme, procede et appareil de detection de vulnerabilites dans des dispositifs electroniques |
US10783254B2 (en) * | 2014-10-02 | 2020-09-22 | Massachusetts Institute Of Technology | Systems and methods for risk rating framework for mobile applications |
US20160162269A1 (en) * | 2014-12-03 | 2016-06-09 | Oleg POGORELIK | Security evaluation and user interface for application installation |
US9578043B2 (en) | 2015-03-20 | 2017-02-21 | Ashif Mawji | Calculating a trust score |
US10614223B2 (en) | 2015-05-28 | 2020-04-07 | Micro Focus Llc | Security vulnerability detection |
US10089465B2 (en) | 2015-07-24 | 2018-10-02 | Bitdefender IPR Management Ltd. | Systems and methods for tracking malicious behavior across multiple software entities |
US9767291B2 (en) * | 2015-10-06 | 2017-09-19 | Netflix, Inc. | Systems and methods for security and risk assessment and testing of applications |
CN105404806B (zh) * | 2015-12-03 | 2018-07-24 | 烟台南山学院 | 一种对计算机软件进行保护的方法和装置 |
US10860742B2 (en) | 2015-12-22 | 2020-12-08 | Micro Focus Llc | Privacy risk information display |
US20170235792A1 (en) | 2016-02-17 | 2017-08-17 | Www.Trustscience.Com Inc. | Searching for entities based on trust score and geography |
US9679254B1 (en) | 2016-02-29 | 2017-06-13 | Www.Trustscience.Com Inc. | Extrapolating trends in trust scores |
US9438619B1 (en) * | 2016-02-29 | 2016-09-06 | Leo M. Chan | Crowdsourcing of trustworthiness indicators |
US9721296B1 (en) | 2016-03-24 | 2017-08-01 | Www.Trustscience.Com Inc. | Learning an entity's trust model and risk tolerance to calculate a risk score |
US10313383B2 (en) * | 2016-06-01 | 2019-06-04 | Mastercard International Incorporated | Systems and methods for use in evaluating vulnerability risks associated with payment applications |
KR101766847B1 (ko) * | 2017-01-24 | 2017-08-11 | (주)지란지교소프트 | 사용자 행위에 기반한 프로세스 평가 방법 |
US10572680B2 (en) * | 2017-03-21 | 2020-02-25 | Microsoft Technology Licensing, Llc | Automated personalized out-of-the-box and ongoing in-application settings |
US10180969B2 (en) | 2017-03-22 | 2019-01-15 | Www.Trustscience.Com Inc. | Entity resolution and identity management in big, noisy, and/or unstructured data |
US10592837B2 (en) * | 2017-04-21 | 2020-03-17 | Accenture Global Solutions Limited | Identifying security risks via analysis of multi-level analytical records |
KR101790761B1 (ko) * | 2017-06-01 | 2017-10-31 | (주)지란지교소프트 | 사용자 행위에 기반한 프로세스 평가 방법 |
US10719610B2 (en) | 2017-08-14 | 2020-07-21 | Blackberry Limited | Generating security manifests for software components using binary static analysis |
US10915638B2 (en) * | 2018-05-16 | 2021-02-09 | Target Brands Inc. | Electronic security evaluator |
US10820205B1 (en) * | 2019-02-27 | 2020-10-27 | NortonLifeLock, Inc. | Systems and methods for performing reputation-based identification of applications on unmanaged mobile devices |
US11347865B2 (en) | 2019-03-29 | 2022-05-31 | Blackberry Limited | Determining security risks in binary software code |
CN112270014B (zh) * | 2020-10-16 | 2022-06-10 | 维沃移动通信有限公司 | 应用程序控制方法、装置及电子设备 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1168166A2 (fr) * | 2000-06-30 | 2002-01-02 | Fujitsu Limited | Méthode et système d'installation d'un programme |
WO2002097620A2 (fr) * | 2001-05-31 | 2002-12-05 | Qualcomm Incorporated | Execution et distribution fiables d'application dans un environnement sans fil |
Family Cites Families (50)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH04199436A (ja) | 1990-11-29 | 1992-07-20 | Nec Corp | ソフトウェア検査システム |
JPH04310188A (ja) * | 1991-03-01 | 1992-11-02 | Internatl Business Mach Corp <Ibm> | 文書/画像ライブラリのためのライブラリサービス方法 |
US5421006A (en) * | 1992-05-07 | 1995-05-30 | Compaq Computer Corp. | Method and apparatus for assessing integrity of computer system software |
JP2501771B2 (ja) | 1993-01-19 | 1996-05-29 | インターナショナル・ビジネス・マシーンズ・コーポレイション | 不所望のソフトウェア・エンティティの複数の有効なシグネチャを得る方法及び装置 |
JPH07160495A (ja) * | 1993-12-03 | 1995-06-23 | Toshiba Corp | ソースコード評価装置 |
US5832208A (en) | 1996-09-05 | 1998-11-03 | Cheyenne Software International Sales Corp. | Anti-virus agent for use with databases and mail servers |
US5960170A (en) | 1997-03-18 | 1999-09-28 | Trend Micro, Inc. | Event triggered iterative virus detection |
US5974549A (en) * | 1997-03-27 | 1999-10-26 | Soliton Ltd. | Security monitor |
US6167521A (en) * | 1997-08-29 | 2000-12-26 | International Business Machines Corporation | Securely downloading and executing code from mutually suspicious authorities |
US6279113B1 (en) * | 1998-03-16 | 2001-08-21 | Internet Tools, Inc. | Dynamic signature inspection-based network intrusion detection |
US6282546B1 (en) | 1998-06-30 | 2001-08-28 | Cisco Technology, Inc. | System and method for real-time insertion of data into a multi-dimensional database for network intrusion detection and vulnerability assessment |
JP3703064B2 (ja) | 1998-08-12 | 2005-10-05 | 株式会社日立製作所 | ソフトウェア品質評価装置および品質評価方法 |
US6321338B1 (en) * | 1998-11-09 | 2001-11-20 | Sri International | Network surveillance |
US6782478B1 (en) * | 1999-04-28 | 2004-08-24 | Thomas Probert | Techniques for encoding information in computer code |
US6446069B1 (en) | 1999-09-17 | 2002-09-03 | International Business Machines Corporation | Access control system for a multimedia datastore |
JP4084914B2 (ja) * | 1999-09-29 | 2008-04-30 | 株式会社日立製作所 | セキュリティ評価方法および装置、セキュリティ施策の作成支援方法および装置 |
US6883101B1 (en) * | 2000-02-08 | 2005-04-19 | Harris Corporation | System and method for assessing the security posture of a network using goal oriented fuzzy logic decision rules |
US7096502B1 (en) | 2000-02-08 | 2006-08-22 | Harris Corporation | System and method for assessing the security posture of a network |
AU2001262958A1 (en) * | 2000-04-28 | 2001-11-12 | Internet Security Systems, Inc. | Method and system for managing computer security information |
US7131143B1 (en) * | 2000-06-21 | 2006-10-31 | Microsoft Corporation | Evaluating initially untrusted evidence in an evidence-based security policy manager |
AUPQ885400A0 (en) | 2000-07-18 | 2000-08-10 | Proteome Systems Ltd | Release of sugars from biomolecules |
US7350204B2 (en) * | 2000-07-24 | 2008-03-25 | Microsoft Corporation | Policies for secure software execution |
US7032114B1 (en) * | 2000-08-30 | 2006-04-18 | Symantec Corporation | System and method for using signatures to detect computer intrusions |
US7178166B1 (en) * | 2000-09-19 | 2007-02-13 | Internet Security Systems, Inc. | Vulnerability assessment and authentication of a computer by a local scanner |
JP2002123494A (ja) * | 2000-10-17 | 2002-04-26 | International Network Securitiy Inc | セキュリティ情報提供システム及びセキュリティ情報提供方法 |
US7168093B2 (en) * | 2001-01-25 | 2007-01-23 | Solutionary, Inc. | Method and apparatus for verifying the integrity and security of computer networks and implementation of counter measures |
US7281267B2 (en) * | 2001-02-20 | 2007-10-09 | Mcafee, Inc. | Software audit system |
JP2002342279A (ja) * | 2001-03-13 | 2002-11-29 | Fujitsu Ltd | フィルタリング装置、フィルタリング方法およびこの方法をコンピュータに実行させるプログラム |
JP4254988B2 (ja) | 2001-03-16 | 2009-04-15 | 株式会社日立製作所 | セキュリティ診断システムおよびセキュリティ診断方法 |
EP2261796A3 (fr) | 2001-05-14 | 2011-02-23 | NTT DoCoMo, Inc. | Système de gestion de programme stocké dans un bloc de stockage d'un terminal mobile |
JP2003050723A (ja) | 2001-08-03 | 2003-02-21 | Toshiba Corp | 計算機プログラム品質管理装置、計算機プログラムエディタ、プログラム、計算機プログラム品質管理方法、計算機プログラムエディット方法 |
NZ531131A (en) * | 2001-08-13 | 2005-12-23 | Qualcomm Inc | Using permissions to allocate device resources to an application |
GB2378783B (en) | 2001-08-17 | 2004-12-29 | F Secure Oyj | Preventing virus infection in a computer system |
JP4733885B2 (ja) * | 2001-09-29 | 2011-07-27 | 株式会社東芝 | 脆弱性評価プログラム、方法及びシステム |
US7359865B1 (en) * | 2001-11-05 | 2008-04-15 | I2 Technologies Us, Inc. | Generating a risk assessment regarding a software implementation project |
MXPA04006473A (es) * | 2001-12-31 | 2004-10-04 | Citadel Security Software Inc | Sistema de resolucion automatizado para vulnerabilidad de computadora. |
JP2003216447A (ja) * | 2002-01-17 | 2003-07-31 | Ntt Docomo Inc | サーバ装置、移動通信端末、情報送信システム及び情報送信方法 |
US20030172291A1 (en) * | 2002-03-08 | 2003-09-11 | Paul Judge | Systems and methods for automated whitelisting in monitored communications |
US6785820B1 (en) * | 2002-04-02 | 2004-08-31 | Networks Associates Technology, Inc. | System, method and computer program product for conditionally updating a security program |
US7290275B2 (en) * | 2002-04-29 | 2007-10-30 | Schlumberger Omnes, Inc. | Security maturity assessment method |
US20040006704A1 (en) * | 2002-07-02 | 2004-01-08 | Dahlstrom Dale A. | System and method for determining security vulnerabilities |
US7472421B2 (en) * | 2002-09-30 | 2008-12-30 | Electronic Data Systems Corporation | Computer model of security risks |
US6952779B1 (en) * | 2002-10-01 | 2005-10-04 | Gideon Cohen | System and method for risk detection and analysis in a computer network |
US7437760B2 (en) * | 2002-10-10 | 2008-10-14 | International Business Machines Corporation | Antiviral network system |
WO2004061596A2 (fr) * | 2002-12-18 | 2004-07-22 | Goldman, Sachs & Co. | Gestion interactive de risque de securite |
US7134015B2 (en) * | 2003-01-16 | 2006-11-07 | International Business Machines Corporation | Security enhancements for pervasive devices |
US7240332B2 (en) * | 2003-04-18 | 2007-07-03 | Ounce Labs, Inc. | Method and system for detecting vulnerabilities in source code |
US7328454B2 (en) * | 2003-04-24 | 2008-02-05 | At&T Delaware Intellectual Property, Inc. | Systems and methods for assessing computer security |
CA2472366A1 (fr) * | 2003-05-17 | 2004-11-17 | Microsoft Corporation | Mecanisme d'evaluation des risques de securite |
KR200329618Y1 (ko) | 2003-07-01 | 2003-10-10 | 배병철 | 척추 교정 및 복부 맛사지기 |
-
2003
- 2003-05-17 CA CA002472366A patent/CA2472366A1/fr not_active Abandoned
- 2003-05-17 BR BR0307030-1A patent/BR0307030A/pt not_active IP Right Cessation
- 2003-05-17 AU AU2003233574A patent/AU2003233574B9/en not_active Ceased
- 2003-05-17 CN CNA03801954XA patent/CN1618198A/zh active Pending
- 2003-05-17 US US10/440,518 patent/US8156558B2/en not_active Expired - Fee Related
- 2003-05-17 EP EP03729010A patent/EP1625687A4/fr not_active Withdrawn
- 2003-05-17 MX MXPA04007406A patent/MXPA04007406A/es not_active Application Discontinuation
- 2003-05-17 WO PCT/US2003/015709 patent/WO2004107647A1/fr active Application Filing
- 2003-05-17 KR KR1020047010654A patent/KR100968003B1/ko not_active IP Right Cessation
- 2003-05-17 JP JP2005500406A patent/JP2006526193A/ja active Pending
-
2010
- 2010-05-06 JP JP2010106615A patent/JP4908611B2/ja not_active Expired - Fee Related
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1168166A2 (fr) * | 2000-06-30 | 2002-01-02 | Fujitsu Limited | Méthode et système d'installation d'un programme |
WO2002097620A2 (fr) * | 2001-05-31 | 2002-12-05 | Qualcomm Incorporated | Execution et distribution fiables d'application dans un environnement sans fil |
Non-Patent Citations (1)
Title |
---|
See also references of WO2004107647A1 * |
Also Published As
Publication number | Publication date |
---|---|
JP4908611B2 (ja) | 2012-04-04 |
MXPA04007406A (es) | 2005-02-17 |
AU2003233574B8 (en) | 2010-03-18 |
KR20060079854A (ko) | 2006-07-07 |
US20040230835A1 (en) | 2004-11-18 |
AU2003233574B9 (en) | 2010-03-25 |
KR100968003B1 (ko) | 2010-07-07 |
JP2006526193A (ja) | 2006-11-16 |
CN1618198A (zh) | 2005-05-18 |
AU2003233574A1 (en) | 2005-01-21 |
JP2010205287A (ja) | 2010-09-16 |
EP1625687A4 (fr) | 2011-11-23 |
CA2472366A1 (fr) | 2004-11-17 |
AU2003233574B2 (en) | 2010-02-18 |
WO2004107647A1 (fr) | 2004-12-09 |
US8156558B2 (en) | 2012-04-10 |
BR0307030A (pt) | 2005-03-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8156558B2 (en) | Mechanism for evaluating security risks | |
RU2589862C1 (ru) | Способ обнаружения вредоносного кода в оперативной памяти | |
US7478237B2 (en) | System and method of allowing user mode applications with access to file data | |
US7765410B2 (en) | System and method of aggregating the knowledge base of antivirus software applications | |
US9892261B2 (en) | Computer imposed countermeasures driven by malware lineage | |
US7765400B2 (en) | Aggregation of the knowledge base of antivirus software | |
EP1655682B1 (fr) | Système et méthode d'agréger la base de connaissance des applications de logiciel d'Antivirus | |
US8341736B2 (en) | Detection and dynamic alteration of execution of potential software threats | |
RU2571723C2 (ru) | Система и способ для снижения нагрузки на операционную систему при работе антивирусного приложения | |
US8117441B2 (en) | Integrating security protection tools with computer device integrity and privacy policy | |
US7756843B1 (en) | Identifying and processing confidential information on network endpoints | |
US8161557B2 (en) | System and method of caching decisions on when to scan for malware | |
US8621608B2 (en) | System, method, and computer program product for dynamically adjusting a level of security applied to a system | |
US9147073B2 (en) | System and method for automatic generation of heuristic algorithms for malicious object identification | |
US20060259948A1 (en) | Integrated document handling in distributed collaborative applications | |
US20070055711A1 (en) | Generic rootkit detector | |
JP2017021773A (ja) | 望ましくないプログラムのインストール及び実行を予防するシステム及び方法 | |
RU2587424C1 (ru) | Способ контроля приложений | |
CN115189938A (zh) | 一种业务安全防护方法和装置 | |
ZA200405127B (en) | Mechanism for evaluating security risks. | |
RU2334363C2 (ru) | Механизм для оценки рисков безопасности | |
RU2592383C1 (ru) | Способ формирования антивирусной записи при обнаружении вредоносного кода в оперативной памяти | |
RU2794713C1 (ru) | Способ обнаружения вредоносного файла с использованием базы уязвимых драйверов | |
Corregedor et al. | ATE: Anti-malware technique evaluator |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20051102 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: FARRO, JOE Inventor name: COOL, JAMIE Inventor name: SCHREINER, TONY Inventor name: BYBEE, ANDREW Inventor name: EPLING, JEREMY Inventor name: RAMDATMISIER, VIRESH Inventor name: GOLDFEDER, AARON Inventor name: HAWKINS, JOHN Inventor name: FEE, GREGORY DARRELL Inventor name: XU, JINGYANG Inventor name: KHORUN, SERGE |
|
DAX | Request for extension of the european patent (deleted) | ||
REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 1087264 Country of ref document: HK |
|
A4 | Supplementary search report drawn up and despatched |
Effective date: 20111025 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 9/00 20060101AFI20111020BHEP |
|
17Q | First examination report despatched |
Effective date: 20120330 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN |
|
REG | Reference to a national code |
Ref country code: HK Ref legal event code: WD Ref document number: 1087264 Country of ref document: HK |
|
18W | Application withdrawn |
Effective date: 20121015 |