US20110055923A1 - Hierarchical statistical model of internet reputation - Google Patents
Hierarchical statistical model of internet reputation Download PDFInfo
- Publication number
- US20110055923A1 US20110055923A1 US12/552,395 US55239509A US2011055923A1 US 20110055923 A1 US20110055923 A1 US 20110055923A1 US 55239509 A US55239509 A US 55239509A US 2011055923 A1 US2011055923 A1 US 2011055923A1
- Authority
- US
- United States
- Prior art keywords
- facility
- communication identifier
- network
- client
- computer program
- 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.)
- Granted
Links
- 238000013179 statistical model Methods 0.000 title 1
- 238000004891 communication Methods 0.000 claims abstract description 105
- 238000004590 computer program Methods 0.000 claims description 18
- 238000012544 monitoring process Methods 0.000 claims description 8
- 238000007726 management method Methods 0.000 description 138
- 238000000034 method Methods 0.000 description 41
- 230000009471 action Effects 0.000 description 25
- 230000000246 remedial effect Effects 0.000 description 15
- 230000003993 interaction Effects 0.000 description 14
- 230000015654 memory Effects 0.000 description 14
- 241000700605 Viruses Species 0.000 description 13
- 238000011156 evaluation Methods 0.000 description 13
- 238000001514 detection method Methods 0.000 description 12
- 238000012545 processing Methods 0.000 description 12
- 238000012360 testing method Methods 0.000 description 12
- 230000008569 process Effects 0.000 description 10
- 238000001914 filtration Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 9
- 230000006399 behavior Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 6
- 230000008901 benefit Effects 0.000 description 5
- 230000003542 behavioural effect Effects 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 230000006855 networking Effects 0.000 description 4
- 238000011160 research Methods 0.000 description 4
- 238000013459 approach Methods 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 3
- 238000005259 measurement Methods 0.000 description 3
- 230000000737 periodic effect Effects 0.000 description 3
- 230000002265 prevention Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 238000002955 isolation Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 229920001690 polydopamine Polymers 0.000 description 2
- 238000005067 remediation Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 241000256251 Spodoptera frugiperda Species 0.000 description 1
- 230000001133 acceleration Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000011157 data evaluation Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000007123 defense Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
- 238000012502 risk assessment Methods 0.000 description 1
- 239000010979 ruby Substances 0.000 description 1
- 229910001750 ruby Inorganic materials 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000007619 statistical method Methods 0.000 description 1
- 230000000153 supplemental effect Effects 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/212—Monitoring or handling of messages using filtering or selective blocking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/105—Multiple levels of security
Definitions
- the present invention is related to computer security, and more specifically to reputation of Internet entities.
- the present invention may provide for a hierarchical modeling processing facility to build a hierarchical reputation model of Internet entities that allows for the automated clustering of “neighborhoods” of related systems, and thus the reputation assessment even of brand new hosts within a neighborhood.
- the reputation of such a neighborhood, with an accompanying confidence level, may be derived statistically from measurements of observed behavior of the systems within it. This may in turn be used to produce an action to provide additional security to users.
- the present invention may receive a communication from a first communication identifier, parse the first communication identifier into its components, and assign the components to a hierarchical tree structure, where the hierarchical tree structure maintains the hierarchical relationship between the components of the communication identifier.
- the present invention may monitor and keep count of a number of communications from the first communication identifier, wherein the number of communications may be kept for both malicious and/or unwanted communications and non-malicious and/or unwanted communications.
- Attributes may then be provided to the number of communications for each appropriate component of the hierarchical tree, and a statistical measure may be calculated as related to the number of communications for each component of the hierarchical tree.
- the present invention may then receive a communication from a second communication identifier, where the second communication identifier may be previously unknown and have a common component with the hierarchical tree.
- the statistical measure of the common component may then be assigned to the second communication identifier, and utilizing the statistical measure assigned to the second communication identifier, may provide a prediction of reputation of the second communication identifier.
- the communication identifier may be in the form of a web address, a domain name, domain name components, an IP address, IP address components, an email address, an IM address, a telephone number, a VoIP telephony address, and the like.
- the component may be at a root level, a top level, a lower level, and the like.
- the at least one of malicious and unwanted communication may be spam, from a computer that is part of a botnet, and the like.
- the statistical measure may relate the number of at least one of malicious and unwanted communications to the number of total communications.
- the reputation may be related to how much spam the website communicates.
- FIG. 1 depicts a block diagram of a threat management facility providing protection to an enterprise against a plurality of threats.
- FIG. 2 depicts the security management facility related to Internet entities through a hierarchical modeling processing facility and reputation database.
- FIG. 3 depicts an example of a hierarchical tree structure in an embodiments of the present invention.
- FIGS. 4 through 10 depict an example of how a hierarchical tree may be built for a domain name structure in an embodiment of the present invention.
- FIGS. 11 through 14 depict an example of how a hierarchical tree may be built for an IP address structure in an embodiment of the present invention.
- FIG. 15 depicts a functional flow diagram in an embodiment of the present invention.
- FIG. 1 depicts a block diagram of a threat management facility providing protection to an enterprise against a plurality of threats.
- An aspect of the present invention relates to corporate policy management and implementation through a unified threat management facility 100 .
- a threat management facility 100 may be used to protect computer assets from many threats, both computer-generated threats and user-generated threats.
- the threat management facility 100 may be multi-dimensional in that it may be designed to protect corporate assets from a variety of threats and it may be adapted to learn about threats in one dimension (e.g. worm detection) and apply the knowledge in another dimension (e.g. spam detection).
- Policy management is one of the dimensions for which the threat management facility can provide a control capability.
- a corporation or other entity may institute a policy that prevents certain people (e.g. employees, groups of employees, types of employees, guest of the corporation, etc.) from accessing certain types of computer programs.
- the corporation may elect to prevent its accounting department from using a particular version of an instant messaging service or all such services.
- the policy management facility 112 may be used to update the policies of all corporate computing assets with a proper policy control facility or it may update a select few.
- the threat management facility 100 can take care of updating all of the other corporate computing assets.
- the threat management facility 100 may provide multiple services, and policy management may be offered as one of the services. We will now turn to a description of certain capabilities and components of the threat management system 100 .
- malware has become a major problem across the internet 154 .
- the categorization of a specific threat type is becoming reduced in significance.
- the threat no matter how it is categorized, may need to be stopped at various points of a networked computing environment, such as one of an enterprise facility 102 , including at one or more laptops, desktops, servers, such as the server facility 142 , gateways, communication ports, handheld or mobile devices, firewalls, and the like.
- a networked computing environment such as one of an enterprise facility 102 , including at one or more laptops, desktops, servers, such as the server facility 142 , gateways, communication ports, handheld or mobile devices, firewalls, and the like.
- a consolidated threat management facility 100 may need to apply a similar set of technologies and capabilities for all threats.
- the threat management facility 100 may provide a single agent on the desktop, and a single scan of any suspect file. This approach may eliminate the inevitable overlaps and gaps in protection caused by treating viruses and spyware as separate problems, while simultaneously simplifying administration and minimizing desktop load.
- the level of connectivity available to all IT users may have lead to a rapid increase in the speed at which threats may move.
- an unprotected PC connected to the internet 154 may be infected quickly (perhaps within 10 minutes) which may require acceleration for the delivery of threat protection.
- the threat management facility 100 may automatically and seamlessly update its product set against spam and virus threats quickly, for instance, every five minutes, every minute, continuously, or the like. Analysis and testing may be increasingly automated, and also may be performed more frequently; for instance, it may be completed in 15 minutes, and may do so without compromising quality.
- the threat management facility 100 may also extend techniques that may have been developed for virus and malware protection, and provide them to enterprise facility 102 network administrators to better control their environments. In addition to stopping malicious code, the threat management facility 100 may provide policy management that may be able to control legitimate applications, such as VoIP, instant messaging, peer-to-peer file-sharing, and the like, that may undermine productivity and network performance within the enterprise facility 102 .
- the threat management facility 100 may provide an enterprise facility 102 protection from computer-based malware, including viruses, spyware, adware, Trojans, intrusion, spam, policy abuse, uncontrolled access, and the like, where the enterprise facility 102 may be any entity with a networked computer-based infrastructure.
- FIG. 1 may depict a block diagram of the threat management facility providing protection to an enterprise against a plurality of threats.
- the enterprise facility 102 may be corporate, commercial, educational, governmental, or the like, and the enterprise facility's 102 computer network may be distributed amongst a plurality of facilities, and in a plurality of geographical locations.
- the threat management facility 100 may include a plurality of functions, such as security management facility 122 , policy management facility 112 , update facility 120 , definitions facility 114 , network access rules facility 124 , remedial action facility 128 , detection techniques facility 130 , testing facility 118 , threat research facility 132 , and the like.
- the threat protection provided by the threat management facility 100 may extend beyond the network boundaries of the enterprise facility 102 to include client facilities 144 that have moved into network connectivity not directly associated or controlled by the enterprise facility 102 .
- Threats to client facilities 144 may come from a plurality of sources, such as from network threats 104 , physical proximity threats 110 , secondary location threats 108 , and the like.
- the threat management facility 100 may provide an enterprise facility 102 protection from a plurality of threats to multiplatform computer resources in a plurality of locations and network configurations, with an integrated system approach.
- the threat management facility 100 may be provided as a stand-alone solution. In other embodiments, the threat management facility 100 may be integrated into a third-party product.
- An application programming interface e.g. a source code interface
- the threat management facility 100 may be stand-alone in that it provides direct threat protection to an enterprise or computer resource, where protection is subscribed to directly 100 .
- the threat management facility may offer protection indirectly, through a third-party product, where an enterprise may subscribe to services through the third-party product, and threat protection to the enterprise may be provided by the threat management facility 100 through the third-party product.
- the security management facility 122 may include a plurality of elements that provide protection from malware to enterprise facility 102 computer resources, including endpoint security and control, email security and control, web security and control, reputation-based filtering, control of unauthorized users, control of guest and non-compliant computers, and the like.
- the security management facility 122 may be a software application that may provide malicious code and malicious application protection to a client facility 144 computing resource.
- the security management facility 122 may have the ability to scan the client facility 144 files for malicious code, remove or quarantine certain applications and files, prevent certain actions, perform remedial actions and perform other security measures.
- scanning the client facility 144 may include scanning some or all of the files stored to the client facility 144 on a periodic basis, may scan applications once the application has been requested to execute, may scan files as the files are transmitted to or from the client facility 144 , or the like.
- the scanning of the applications and files may be to detect known malicious code or known unwanted applications.
- new malicious code and unwanted applications may be continually developed and distributed, and updates to the known code database may be provided on a periodic basis, on a demand basis, on an alert basis, or the like.
- the security management facility 122 may provide for email security and control, where security management may help to eliminate spam, viruses, spyware and phishing, control of email content, and the like.
- the security management facility's 122 email security and control may protect against inbound and outbound threats, protect email infrastructure, prevent data leakage, provide spam filtering, and the like.
- security management facility 122 may provide for web security and control, where security management may help to detect or block viruses, spyware, malware, unwanted applications, help control web browsing, and the like, which may provide comprehensive web access control enabling safe, productive web browsing.
- Web security and control may provide internet use policies, reporting on suspect devices, security and content filtering, active monitoring of network traffic, URI filtering, and the like.
- the security management facility 122 may provide for network access control, which may provide control over network connections.
- Network control may stop unauthorized, guest, or non-compliant systems from accessing networks, and may control network traffic that may not be bypassed from the client level.
- network access control may control access to virtual private networks (VPN), where VPNs may be a communications network tunneled through another network, establishing a logical connection acting as a virtual network.
- VPN virtual private networks
- a VPN may be treated in the same manner as a physical network.
- the security management facility 122 may provide for host intrusion prevention through behavioral based protection, which may guard against unknown threats by analyzing behavior before software code executes. Behavioral based protection may monitor code when it runs and intervene if the code is deemed to be suspicious or malicious. Advantages of behavioral based protection over runtime protection may include code being prevented from running, whereas runtime protection may only interrupt code that has already partly executed; behavioral protection may identify malicious code at the gateway or on the file servers and deletes it before reaching end-point computers and the like.
- the security management facility 122 may provide for reputation filtering, which may target or identify sources of known malware.
- reputation filtering may include lists of URIs of known sources of malware or known suspicious IP addresses, or domains, say for spam, that when detected may invoke an action by the threat management facility 100 , such as dropping them immediately. By dropping the source before any interaction can initiate, potential threat sources may be thwarted before any exchange of data can be made.
- information may be sent from the enterprise back to a third party, a vendor, or the like, which may lead to improved performance of the threat management facility 100 .
- the types, times, and number of virus interactions that a client experiences may provide useful information for the preventions of future virus threats.
- This type of feedback may be useful for any aspect of threat detection.
- Feedback of information may also be associated with behaviors of individuals within the enterprise, such as being associated with most common violations of policy, network access, unauthorized application loading, unauthorized external device use, and the like.
- this type of information feedback may enable the evaluation or profiling of client actions that are violations of policy that may provide a predictive model for the improvement of enterprise policies.
- the security management facility 122 may provide for the overall security of the enterprise facility 102 network or set of enterprise facility 102 networks, may provide updates of malicious code information to the enterprise facility 102 network, and associated client facilities 144 .
- the updates may be a planned update, an update in reaction to a threat notice, an update in reaction to a request for an update, an update based on a search of known malicious code information, or the like.
- the administration facility 134 may provide control over the security management facility 122 when updates are performed.
- the updates may be automatically transmitted without an administration facility's 134 direct control, manually transmitted by the administration facility 134 , or the like.
- the security management facility 122 may include the management of receiving malicious code descriptions from a provider, distribution of malicious code descriptions to enterprise facility 102 networks, distribution of malicious code descriptions to client facilities 144 , or the like.
- the management of malicious code information may be provided to the enterprise facility's 102 network, where the enterprise facility's 102 network may provide the malicious code information through the enterprise facility's 102 network distribution system.
- the threat management facility 100 may provide a policy management facility 112 that may be able to block non-malicious applications, such as VoIP 164 , instant messaging 162 , peer-to-peer file-sharing, and the like, that may undermine productivity and network performance within the enterprise facility 102 .
- the policy management facility 112 may be a set of rules or policies that may indicate enterprise facility 102 access permissions for the client facility 144 , such as access permissions associated with the network, applications, external computer devices, and the like.
- the policy management facility 112 may include a database, a text file, a combination of databases and text files, or the like.
- a policy database may be a block list, a black list, an allowed list, a white list, or the like that may provide a list of enterprise facility 102 external network locations/applications that may or may not be accessed by the client facility 144 .
- the policy management facility 112 may include rules that may be interpreted with respect to an enterprise facility 102 network access request to determine if the request should be allowed.
- the rules may provide a generic rule for the type of access that may be granted; the rules may be related to the policies of an enterprise facility 102 for access rights for the enterprise facility's 102 client facility 144 . For example, there may be a rule that does not permit access to sporting websites.
- a security facility may access the rules within a policy facility to determine if the requested access is related to a sporting website.
- the security facility may analyze the requested website to determine if the website matches with any of the policy facility rules.
- the policy management facility 112 may be similar to the security management facility 122 but with the addition of enterprise facility 102 wide access rules and policies that may be distributed to maintain control of client facility 144 access to enterprise facility 102 network resources.
- the policies may be defined for application type, subset of application capabilities, organization hierarchy, computer facility type, user type, network location, time of day, connection type, or the like.
- Policies may be maintained by the administration facility 134 , through the threat management facility 100 , in association with a third party, or the like. For example, a policy may restrict IM 162 activity to only support personnel for communicating with customers.
- the policy management facility 112 may be a stand-alone application, may be part of the network server facility 142 , may be part of the enterprise facility 102 network, may be part of the client facility 144 , or the like.
- the threat management facility 100 may provide configuration management, which may be similar to policy management, but may specifically examine the configuration set of applications, operating systems, hardware, and the like, and managing changes to their configurations. Assessment of a configuration may be made against a standard configuration policy, detection of configuration changes, remediation of improper configuration, application of new configurations, and the like.
- An enterprise may keep a set of standard configuration rules and policies which may represent the desired state of the device. For example, a client firewall may be running and installed, but in the disabled state, where remediation may be to enable the firewall.
- the enterprise may set a rule that disallows the use of USB disks, and sends a configuration change to all clients, which turns off USB drive access via a registry.
- the threat management facility 100 may also provide for the removal of applications that may interfere with the operation of the threat management facility 100 , such as competitor products that may also be attempting similar threat management functions.
- the removal of such products may be initiated automatically whenever such products are detected.
- the application may be suspended until action is taken to remove or disable the third-party product's protection facility.
- Threat management against a sometimes quickly evolving malware environment may require timely updates, and the update management facility 120 may be provided by the threat management facility 100 .
- a policy management facility 112 may also require update management (e.g. as provided by the update facility 120 herein described), as the enterprise facility 102 requirements for policies change enterprise facility 102 , client facility 144 , server facility 142 enterprise facility 102 .
- the update management for the security facility 122 and policy management facility 112 may be provided directly by the threat management facility 100 , such as by a hosted system or in conjunction with the administration facility 134 .
- the threat management facility 100 may provide for patch management, where a patch may be an update to an operating system, an application, a system tool, or the like, where one of the reasons for the patch is to reduce vulnerability to threats.
- the security facility 122 and policy management facility 112 may push information to the enterprise facility 102 network and/or client facility 144 , the enterprise facility 102 network and/or client facility 144 may pull information from the security facility 122 and policy management facility 112 network server facilities 142 , there may be a combination of pushing and pulling of information between the security facility 122 and the policy management facility 112 network servers 142 , enterprise facility 102 network, and client facilities 144 , or the like.
- the enterprise facility 102 network and/or client facility 144 may pull information from the security facility 122 and policy management facility 112 network server facility 142 may request the information using the security facility 122 and policy management facility 112 update module; the request may be based on a certain time period, by a certain time, by a date, on demand, or the like.
- the security facility 122 and policy management facility 112 network servers 142 may push the information to the enterprise facility's 102 network and/or client facility 144 by providing notification that there are updates available for download and then transmitting the information.
- the combination of the security management 122 network server facility 142 and security update module may function substantially the same as the policy management facility 112 network server and policy update module by providing information to the enterprise facility 102 network and the client facility 144 in a push or pull method.
- the policy management facility 112 and the security facility 122 management update modules may work in concert to provide all the needed information to the enterprise facility's 102 network and/or client facility 144 for control of application execution.
- the policy update module and security update module may be combined into a single update module.
- the threat management facility 100 may create definition updates that may be used to allow the threat management facility 100 to detect and remediate the latest malicious software, unwanted applications, configuration and policy changes, and the like.
- the threat definition facility 114 may contain threat identification updates, also referred to as definition files.
- a definition file may be a virus identity file that may include definitions of known or potential malicious code.
- the virus identity (IDE) definition files may provide information that may identify malicious code within files, applications, or the like.
- the definition files may be accessed by security management facility 122 when scanning files or applications within the client facility 144 for the determination of malicious code that may be within the file or application.
- the definition files may contain a number of commands, definitions, or instructions, to be parsed and acted upon, or the like.
- the client facility 144 may be updated with new definition files periodically to provide the client facility 144 with the most recent malicious code definitions; the updating may be performed on a set time period, may be updated on demand from the client facility 144 , may be updated on demand from the network, may be updated on a received malicious code alert, or the like.
- the client facility 144 may request an update to the definition files from an update facility 120 within the network, may request updated definition files from a computing facility external to the network, updated definition files may be provided to the client facility 114 from within the network, definition files may be provided to the client facility 144 from an external computing facility from an external network, or the like.
- a definition management facility 114 may provide for the timely updates of definition files information to the network, client facilities 144 , and the like. New and altered malicious code and malicious applications may be continually created and distributed to networks worldwide.
- the definition files that maintain the definitions of the malicious code and malicious application information for the protection of the networks and client facilities 144 may need continual updating to provide continual defense of the network and client facility 144 from the malicious code and malicious applications.
- the definition files management may provide for automatic and manual methods of updating the definition files.
- the network may receive definition files and distribute the definition files to the network client facilities 144 , the client facilities 144 may receive the definition files directly, or the network and client facilities 144 may both receive the definition files, or the like.
- the definition files may be updated on a fixed periodic basis, on demand by the network and/or the client facility 144 , as a result of an alert of a new malicious code or malicious application, or the like.
- the definition files may be released as a supplemental file to an existing definition files to provide for rapid updating of the definition files.
- the security management facility 122 may be used to scan an outgoing file and verify that the outgoing file is permitted to be transmitted per the enterprise facility 102 rules and policies. By checking outgoing files, the security management facility 122 may be able discover malicious code infected files that were not detected as incoming files as a result of the client facility 144 having been updated with either new definition files or policy management facility 112 information.
- the definition files may discover the malicious code infected file by having received updates of developing malicious code from the administration facility 134 , updates from a definition files provider, or the like.
- the policy management facility 112 may discover the malicious code infected file by having received new updates from the administration facility 134 , from a rules provider, or the like.
- the threat management facility 100 may provide for a way to control access to the enterprise facility 102 networks.
- the enterprise facility 102 may want to restrict access to certain applications, networks, files, printers, servers, databases, or the like.
- the enterprise facility 102 may want to restrict user access under certain conditions, such as the user's location, usage history, need to know, job position, connection type, time of day, method of authentication, client-system configuration, or the like.
- Network access rules may be developed by the enterprise facility 102 , or pre-packaged by a supplier, and managed by the threat management facility 100 in conjunction with the administration facility 134 .
- Network access rules and control may be responsible for determining if a client facility 144 application should be granted access to a requested network location.
- the network location may be on the same network as the facility or may be on another network.
- the network access control may verify access rights for client facilities 144 from within the network or may verify access rights of computer facilities from external networks.
- the network access control may send an information file to the client facility 144 , the information file may contain data or commands that may provide instructions for the remedial action facility 128 .
- the information sent by the network access facility 124 control may be a data file.
- the data file may contain a number of commands, definitions, instructions, or commands to be parsed and acted upon through the remedial action facility 128 , or the like.
- the information sent by the network access facility 124 control may be a command or command file that the remedial action facility 128 may access and take action upon.
- the network access rules 124 may provide an information store to be accessed by the network access control.
- the network access rules facility 124 may include databases such as a block list, a black list, an allowed list, a white list, an unacceptable network site database, an acceptable network site database, a network site reputation database, or the like of network access locations that may or may not be accessed by the client facility 144 .
- the network access rules facility 124 may incorporate rule evaluation; the rule evaluation may parse network access requests and apply the parsed information to network access rules.
- the network access rule facility 124 may have a generic set of rules that may be in support of an enterprise facility's 102 network access policies, such as denying access to certain types of websites 158 , controlling instant messenger 162 accesses, or the like.
- Rule evaluation may include regular expression rule evaluation, or other rule evaluation method for interpreting the network access request and comparing the interpretation to the established rules for network access.
- the network access rules facility 124 may receive a rules evaluation request from the network access control and may return the rules evaluation to the network access control.
- the network access rule facility 124 may provide updated rules and policies to the enterprise facility 102 .
- the network access rules facility 124 may be maintained by the network administration facility 134 , using network access rules facility 124 management.
- the network administration facility 134 may be able to maintain a set of access rules manually by adding rules, changing rules, deleting rules, or the like.
- the administration facility 134 may be able to retrieve predefined rule sets from a provider that may provide a set of rules to be applied to an entire enterprise facility 102 .
- the network administration facility 134 may be able to modify the predefined rules as needed for a particular enterprise facility 102 using the network access rules management facility 124 .
- the threat management facility 100 may provide for a remedial action facility 128 .
- Remedial action may take a plurality of forms, such as terminating or modifying an ongoing process or interaction, sending a warning to a client or administration facility 134 of an ongoing process or interaction, executing a program or application to remediate against a threat or violation, record interactions for subsequent evaluation, or the like.
- Remedial action may be associated with an application that responds to information that a client facility 144 network access request has been denied.
- remedial action may parse the data file, interpret the various aspects of the data file, and act on the parsed data file information to determine actions to be taken on an application requesting access to a denied network location.
- remedial action may access the threat definitions to parse the data file and determine an action to be taken on an application requesting access to a denied network location.
- the information received from the facility may be a command or a command file. The remedial action facility may carry out any commands that are received or parsed from a data file from the facility without performing any interpretation of the commands.
- the remedial action facility may interact with the received information and may perform various actions on a client requesting access to a denied network location.
- the action may be one or more of continuing to block all requests to a denied network location, a malicious code scan on the application, a malicious code scan on the client facility 144 , quarantine of the application, terminating the application, isolation of the application, isolation of the client facility 144 to a location within the network that restricts network access, blocking a network access port from a client facility 144 , reporting the application to a administration facility 134 , or the like.
- the detection techniques facility 130 may include monitoring the enterprise facility 102 network or end-point devices, such as by monitoring streaming data through the gateway, across the network, through routers and hubs, and the like.
- the detection techniques facility 130 may include monitoring activity and stored files on computing facilities, such as on server facilities 142 , desktop computers, laptop computers, other mobile computing devices, and the like.
- Detection techniques such as scanning a computer's stored files, may provide the capability of checking files for stored threats, either in the active or passive state.
- Detection techniques, such as streaming file management may provide the capability of checking files received at the network, gateway facility, client facility 144 , and the like.
- the streaming file may be broken into blocks of information, and a plurality of virus identities may be used to check each of the blocks of information for malicious code.
- any blocks that are not determined to be clear of malicious code may not be delivered to the client facility 144 , gateway facility, or network.
- Verifying that the threat management facility 100 is detecting threats and violations to established policy may require the ability to test the system, either at the system level or for a particular computing component.
- the testing facility 118 may allow the administration facility 134 to coordinate the testing of the security configurations of client facility 144 computing facilities on a network.
- the administration facility 134 may be able to send test files to a set of client facility 144 computing facilities to test the ability of the client facility 144 to determine acceptability of the test file.
- a recording facility may record the actions taken by the client facility 144 in reaction to the test file.
- the recording facility may aggregate the testing information from the client facility 144 and report the testing information to the administration facility 134 .
- the administration facility 134 may be able to determine the level of preparedness of the client facility 144 computing facilities by the reported information. Remedial action may be taken for any of the client facility 144 computing facilities as determined by the administration facility 134 ; remedial action may be taken by the administration facility 134 or by the user of the client facility 144 .
- the threat research facility 132 may provide a continuously ongoing effort to maintain the threat protection capabilities of the threat management facility 100 in light of continuous generation of new or evolved forms of malware.
- Threat research may include researchers and analysts working on known and emerging malware, such as viruses, rootkits a spyware, as well as other computer threats such as phishing, spam, scams, and the like.
- the threat management facility 100 may be able to provide swift, global responses to the latest threats.
- the threat management facility 100 may provide threat protection to the enterprise facility 102 , where the enterprise facility 102 may include a plurality of networked components, such as client facility 144 , server facility 142 , administration facility 134 , firewall 138 , gateway, hubs and routers 148 , threat management appliance 140 , desktop users, mobile users, and the like. In embodiments, it may be the end-point computer security facility 152 , located on a computer's desktop, which may provide threat protection to a user, and associated enterprise facility 102 .
- the enterprise facility 102 may include a plurality of networked components, such as client facility 144 , server facility 142 , administration facility 134 , firewall 138 , gateway, hubs and routers 148 , threat management appliance 140 , desktop users, mobile users, and the like. In embodiments, it may be the end-point computer security facility 152 , located on a computer's desktop, which may provide threat protection to a user, and associated enterprise facility 102 .
- end-point may refer to a computer system that may source data, receive data, evaluate data, buffer data, or the like (such as a user's desktop computer as an end-point computer), a firewall as a data evaluation end-point computer system, a laptop as a mobile end-point computer, a PDA as a hand-held end-point computer, a mobile phone as an end-point computer, or the like.
- end-point may refer to a source or destination for data, including such components where the destination is characterized by an evaluation point for data, and where the data may be sent to a subsequent destination after evaluation.
- the end-point computer security facility 152 may be an application loaded onto the computer platform or computer support component, where the application may accommodate the plurality of computer platforms and/or functional requirements of the component.
- a client facility 144 computer may be one of a plurality of computer platforms, such as Windows, Macintosh, Linux, and the like, where the end-point computer security facility 152 may be adapted to the specific platform, while maintaining a uniform product and product services across platforms.
- components may have different functions to serve within the enterprise facility's 102 networked computer-based infrastructure.
- computer support components provided as hubs and routers 148 , server facility 142 , firewalls 138 , and the like, may require unique security application software to protect their portion of the system infrastructure, while providing an element in an integrated threat management system that extends out beyond the threat management facility 100 to incorporate all computer resources under its protection.
- the enterprise facility 102 may include a plurality of client facility 144 computing platforms on which the end-point computer security facility 152 is adapted.
- a client facility 144 computing platform may be a computer system that is able to access a service on another computer, such as a server facility 142 , via a network.
- This client facility 144 server facility 142 model may apply to a plurality of networked applications, such as a client facility 144 connecting to an enterprise facility 102 application server facility 142 , a web browser client facility 144 connecting to a web server facility 142 , an e-mail client facility 144 retrieving e-mail from an internet 154 service provider's mail storage servers 142 , and the like.
- client facility 144 applications may be switched to websites, which may increase the browser's role as a client facility 144 .
- Clients 144 may be classified as a function of the extent to which they perform their own processing. For instance, client facilities 144 are sometimes classified as a fat client facility 144 or thin client facility 144 .
- the fat client facility 144 also known as a thick client facility 144 or rich client facility 144 , may be a client facility 144 that performs the bulk of data processing operations itself, and does not necessarily rely on the server facility 142 .
- the fat client facility 144 may be most common in the form of a personal computer, where the personal computer may operate independent of any server facility 142 .
- Programming environments for fat clients 144 may include CURI, Delphi, Droplets, Java, win32, X11, and the like.
- Thin clients 144 may offer minimal processing capabilities, for instance, the thin client facility 144 may primarily provide a graphical user interface provided by an application server facility 142 , which may perform the bulk of any required data processing.
- Programming environments for thin clients 144 may include JavaScript/AJAX, ASP, JSP, Ruby on Rails, Python's Django, PHP, and the like.
- the client facility 144 may also be a mix of the two, such as processing data locally, but relying on a server facility 142 for data storage.
- this hybrid client facility 144 may provide benefits from both the fat client facility 144 type, such as multimedia support and high performance, and the thin client facility 144 type, such as high manageability and flexibility.
- the threat management facility 100 , and associated end-point computer security facility 152 may provide seamless threat protection to the plurality of clients 144 , and client facility 144 types, across the enterprise facility 102 .
- the enterprise facility 102 may include a plurality of server facilities 142 , such as application servers, communications servers, file servers, database servers, proxy servers, mail servers, fax servers, game servers, web servers, and the like.
- a server facility 142 which may also be referred to as a server facility 142 application, server facility 142 operating system, server facility 142 computer, or the like, may be an application program or operating system that accepts client facility 144 connections in order to service requests from clients 144 .
- the server facility 142 application may run on the same computer as the client facility 144 using it, or the server facility 142 and the client facility 144 may be running on different computers and communicating across the network.
- Server facility 142 applications may be divided among server facility 142 computers, with the dividing depending upon the workload.
- the threat management facility 100 may provide threat protection to server facilities 142 within the enterprise facility 102 as load conditions and application changes are made.
- a server facility 142 may also be an appliance facility 140 , where the appliance facility 140 provides specific services onto the network.
- the appliance facility 140 is a server facility 142 computer, that may be loaded with a server facility 142 operating system and server facility 142 application, the enterprise facility 102 user may not need to configure it, as the configuration may have been performed by a third party.
- an enterprise facility 102 appliance may be a server facility 142 appliance that has been configured and adapted for use with the threat management facility 100 , and located within the facilities of the enterprise facility 102 .
- the enterprise facility's 102 threat management appliance may enable the enterprise facility 102 to administer an on-site local managed threat protection configuration, where the administration facility 134 may access the threat resources through an interface, such as a web portal.
- the enterprise facility 102 may be managed remotely from a third party, vendor, or the like, without an appliance facility 140 located within the enterprise facility 102 .
- the appliance functionality may be a shared hardware product between pluralities of enterprises 102 .
- the appliance facility 140 may be located at the enterprise facility 102 , where the enterprise facility 102 maintains a degree of control.
- a hosted service may be provided, where the appliance 140 may still be an on-site black box to the enterprise facility 102 , physically placed there because of infrastructure requirements, but managed by a third party, vendor, or the like.
- Simple server facility 142 appliances may also be utilized across the enterprise facility's 102 network infrastructure, such as switches, routers, wireless routers, hubs and routers, gateways, print servers, net modems, and the like. These simple server facility appliances may not require configuration by the enterprise facility 102 , but may require protection from threats via an end-point computer security facility 152 . These appliances may provide interconnection services within the enterprise facility 102 network, and therefore may advance the spread of a threat if not properly protected.
- a personal firewall may be an application that controls network traffic to and from a client, permitting or denying communications based on a security policy.
- personal firewalls may be designed for use by end-users, which may result in protection for only the computer on which it's installed.
- personal firewalls may be able to control network traffic by providing prompts each time a connection is attempted and adapting security policy accordingly.
- personal firewalls may also provide some level of intrusion detection, which may allow the software to terminate or block connectivity where it suspects an intrusion is being attempted.
- a personal firewall may include alerts about outgoing connection attempts, control of program access to networks, hiding the client from port scans by not responding to unsolicited network traffic, monitoring of applications that may be listening for incoming connections, monitoring and regulation of incoming and outgoing network traffic, prevention of unwanted network traffic from installed applications, reporting applications that make connection attempts, reporting destination servers with which applications may be attempting communications, and the like.
- the personal firewall may be provided by the threat management facility 100 .
- a network firewall facility 138 may be a hardware or software device that may be configured to permit, deny, or proxy data through a computer network that has different levels of trust in its source of data.
- a network firewall facility 138 may be a hardware or software device that may be configured to permit, deny, or proxy data through a computer network that has different levels of trust in its source of data.
- an internal enterprise facility 102 network may have a high level of trust, because the source of all data has been sourced from within the enterprise facility 102 .
- An example of a low level of trust is the Internet 154 , because the source of data may be unknown.
- a zone with an intermediate trust level, situated between the Internet 154 and a trusted internal network may be referred to as a “perimeter network”.
- firewall facilities 138 represent boundaries between threat levels
- the end-point computer security facility 152 associated with the firewall facility 138 may provide resources that may control the flow of threats at this enterprise facility 102 network entry point.
- Firewall facilities 138 , and associated end-point computer security facility 152 may also be associated with a network node that may be equipped for interfacing between networks that use different protocols.
- the end-point computer security facility 152 may provide threat protection in a plurality of network infrastructure locations, such as at the enterprise facility 102 network entry point, i.e. the firewall facility 138 or gateway; at the server facility 142 ; at distribution points within the network, i.e. the hubs and routers 148 ; at the desktop of client facility 144 computers; and the like.
- the most effective location for threat detection may be at the user's computer desktop end-point computer security facility 152 .
- the interface between the threat management facility 100 and the enterprise facility 102 , and through the appliance facility 140 to embedded end-point computer security facilities, may include a set of tools that may be the same for all enterprise implementations, but allow each enterprise to implement different controls.
- these controls may include both automatic actions and managed actions.
- Automatic actions may include downloads of the end-point computer security facility 152 to components of the enterprise facility 102 , downloads of updates to existing end-point computer security facilities of the enterprise facility 102 , uploaded network interaction requests from enterprise facility 102 components to the threat management facility 100 , and the like.
- automatic interactions between the enterprise facility 102 and the threat management facility 100 may be configured by the threat management facility 100 and an administration facility 134 in the enterprise facility 102 .
- the administration facility 134 may configure policy rules that determine interactions, such as developing rules for accessing applications, as in who is authorized and when applications may be used; establishing rules for ethical behavior and activities; rules governing the use of entertainment software such as games, or personal use software such as IM 162 and VoIP 164 ; rules for determining access to enterprise facility 102 computing resources, including authentication, levels of access, risk assessment, and usage history tracking; rules for when an action is not allowed, such as whether an action is completely deigned or just modified in its execution; and the like.
- the administration facility 134 may also establish license management, which in turn may further determine interactions associated with a licensed application.
- interactions between the threat management facility 100 and the enterprise facility 102 may provide threat protection to the enterprise facility 102 by managing the flow of network data into and out of the enterprise facility 102 through automatic actions that may be configured by the threat management facility 100 or the administration facility 134 .
- Client facilities 144 within the enterprise facility 102 may be connected to the enterprise facility 102 network by way of wired network facilities 148 A or wireless network facilities 148 B.
- Client facilities 144 connected to the enterprise facility 102 network via a wired facility 148 A or wireless facility 148 B may receive similar protection, as both connection types are ultimately connected to the same enterprise facility 102 network, with the same end-point computer security facility 152 , and the same threat protected enterprise facility 102 environment.
- Mobile wireless facility clients 144 B-F because of their ability to connect to any wireless 148 B,D network access point, may connect to the internet 154 outside the enterprise facility 102 , and therefore outside the threat-protected environment of the enterprise facility 102 .
- the mobile client facility 144 B-F if not for the presence of the end-point computer security facility 152 may experience a malware attack or perform actions counter to enterprise facility 102 established policies.
- the threat management facility 100 may protect the out-of-enterprise facility 102 mobile client facility 144 D-F that has an embedded end-point computer security facility 152 , such as by providing URI filtering in personal routers, using a web appliance as a DNS proxy, or the like.
- Mobile client facilities 144 D-F that are components of the enterprise facility 102 but temporarily outside connectivity with the enterprise facility 102 network, may be provided with the same threat protection and policy control as client facilities 144 inside the enterprise facility 102 .
- mobile client facilities 144 B-F may receive the same interactions to and from the threat management facility 100 as client facilities 144 inside the enterprise facility 102 , where mobile client facilities 144 B-F may be considered a virtual extension of the enterprise facility 102 , receiving all the same services via their embedded end-point computer security facility 152 .
- Threat management facility 100 downloads and upgrades to the enterprise facility 102 may be passed from the firewalled networks of the threat management facility 100 through to the end-point computer security facility 152 equipped components of the enterprise facility 102 .
- the end-point computer security facility 152 components of the enterprise facility 102 may upload policy and access requests back across the internet 154 and through to the threat management facility 100 .
- the Internet 154 is also the path through which threats may be transmitted from their source.
- These network threats may include threats from a plurality of sources, including websites 158 , e-mail 160 , IM 162 , VoIP 164 , application software, and the like. These threats may attempt to attack a mobile enterprise client facility 144 B-F equipped with an end-point computer security facility 152 , but in embodiments, as long as the mobile client facility 144 B-F is embedded with an end-point computer security facility 152 , as described above, threats may have no better success than if the mobile client facility 144 B-F were inside the enterprise facility 102 .
- the mobile client facility 144 may be required to request network interactions through the threat management facility 100 , where contacting the threat management facility 100 may be performed prior to any other network action.
- the client facility's 144 end-point computer security facility 152 may manage actions in unprotected network environments such as when the client facility 144 F is in a secondary location 108 or connecting wirelessly to a non-enterprise facility 102 wireless internet connection, where the end-point computer security facility 152 may dictate what actions are allowed, blocked, modified, or the like.
- the end-point computer security facility 152 may inform the user of such, and recommend that the connection not be made.
- the end-point computer security facility 152 may perform specific actions during or after the unprotected connection is made, including running scans during the connection period, running scans after the connection is terminated, storing interactions for subsequent threat and policy evaluation, contacting the threat management facility 100 upon first instance of a secured connection for further actions and or scanning,restricting access to network and local resources, or the like.
- the end-point computer security facility 152 may perform specific actions to remediate possible threat incursions or policy violations during or after the unprotected connection.
- the secondary location 108 may have no end-point computer security facilities 152 as a part of its computer components, such as its firewalls 138 B, servers 142 B, clients 144 G, hubs and routers 148 C-D, and the like.
- the computer components of the secondary location 108 may be open to threat attacks, and become potential sources of threats, as well as any mobile enterprise facility clients 144 B-F that may be connected to the secondary location's 108 network. In this instance, these computer components may now unknowingly spread a threat to other components connected to the network.
- Some threats may not come directly from the Internet 154 , such as from non-enterprise facility controlled mobile devices that are physically brought into the enterprise facility 102 and connected to the enterprise facility 102 client facilities 144 .
- the connection may be made from direct connection with the enterprise facility's 102 client facility 144 , such as through a USB port, or in physical proximity with the enterprise facility's 102 client facility 144 such that a wireless facility connection can be established, such as through a Bluetooth connection.
- These physical proximity threats 110 may be another mobile computing device, a portable memory storage device, a mobile communications device, or the like, such as CDs and DVDs 170 , memory stick 174 , flash drive 174 , external hard drive, cell phone 178 , PDAs 180 , MP3 players, digital cameras, point-to-point devices, digital picture frames, digital pens, navigation devices, appliances, and the like.
- a physical proximity threat 110 may have been previously infiltrated by network threats while connected to an unprotected network connection outside the enterprise facility 102 , and when connected to the enterprise facility 102 client facility 144 , pose a threat.
- physical proximity threats 110 may infiltrate computing resources in any location, such as being physically brought into the enterprise facility 102 site, connected to an enterprise facility 102 client facility 144 while that client facility 144 is mobile, plugged into an unprotected client facility 144 at a secondary location 108 , and the like.
- a mobile device once connected to an unprotected computer resource, may become a physical proximity threat 110 .
- the end-point computer security facility 152 may provide enterprise facility 102 computing resources with threat protection against physical proximity threats 110 , for instance, through scanning the device prior to allowing data transfers, through security validation certificates, through establishing a safe zone within the enterprise facility 102 computing resource to transfer data into for evaluation, and the like.
- assessing the reputation (“trustworthiness”) of Internet entities 208 via communication identifiers such as such as a web address, a domain names, an IP addresses, host names, email addresses, IM addresses, telephone numbers, VoIP telephony addresses, and the like, may be a function of security management 122 within the threat management facility 100 .
- the security management facility 122 may provide for reputation filtering, which may target or identify sources of known malware.
- reputation filtering may include lists of URIs of known sources of malware or known suspicious IP addresses, or domains, say for spam or for botnets, that when detected may invoke an action by the threat management facility 100 .
- the present invention may provide for a hierarchical modeling processing facility 202 to build a hierarchical reputation model of these entities 208 that allows for the automated clustering of “neighborhoods” of related systems, and thus the reputation assessment even of brand new hosts within a neighborhood.
- the reputation of such a neighborhood may be derived statistically from measurements of observed behavior of the systems within it.
- a hierarchical model may allow an entity's 208 reputation to be partially or wholly inherited from its parent.
- reputations for these entities 208 may be stored in a reputation database 204 .
- a hierarchical reputation model may reflect the natural hierarchy of Internet entities 208 , both named (i.e. with a hostname, the logical level) and unnamed (i.e. with just an IP address, the physical level).
- Named entities 208 are provided by the Domain Name System, a globally distributed mapping of hostnames to IP addresses.
- the DNS is arranged hierarchically, and different parts of the tree are maintained by different organizations. For example, Bigcorp, Inc. will be officially charged with responsibility for the “bigcorp.com” domain name and all the hostnames underneath it, e.g. “www.bigcorp.com” and “mail.bigcorp.com”.
- SomeISP's zone of authority begins at the someisp node 308 and extends to the leaves 318 , 320 , 322 , 324 , 328 , 330 .
- the administrator has decided to establish three major subzones, corp 310 for the company's corporate network, biz 312 for their business customers, and res 314 for their residential customers.
- Each major subzone is further divided, with the leaves 318 , 320 , 322 , 324 , 328 , 330 representing a specific host (e.g. computer, collection of computers, and the like).
- the DNS provides a natural clustering of similarly purposed hosts, with clusters delimited by the organization's own naming policy: the host “bob.res.someisp.net” 328 may for instance be treated similarly to the host “alice.res.someisp.net” 330 , because they both belong to residential customers. For example, the two hosts may have similar corresponding probability of being part of a spammer's botnet. On the other hand, the hosts “ceo.corp.someisp.net” 318 and “janitor.corp.someisp.net” 320 may be less likely to be part of a botnet, such as by virtue of being behind a professionally administered firewall.
- the present invention leverages the information provided by organizations' DNS sub-trees to cluster hosts for the purpose of determining their reputation. For instance, and referring again to FIG. 3 , that a new host “chieftechnologist.corp.someisp.net” may likely to behave more similarly to “ceo.corp.someisp.net” 318 than to “alice.res.someisp.net” 330 .
- a new host “chieftechnologist.corp.someisp.net” may likely to behave more similarly to “ceo.corp.someisp.net” 318 than to “alice.res.someisp.net” 330 .
- By augmenting a tree structure such as the one presented in FIG. 3 , with the appropriate metrics as obtained through direct observations of the hosts involved, one may then predict the behavior of hosts one hasn't yet had the opportunity to observe by estimating the reputation of the neighborhood (i.e. a subtree) within which they are located.
- the resulting structure is sometimes referred to as a “
- FIGS. 4-9 provide a hierarchical building of a named, or logical, tree.
- the metrics we are monitoring are ‘total mails sent’ and ‘total spams sent’, in order to calculate a very simple reputation score of total spams sent/total mails sent, i.e. the ratio of spams to total mail sent by a host, or the probability that a subsequent email will also be spam.
- FIG. 4 presents an empty tree, where there are no hosts associated with the root level 302 A, and so no emails or spams accounted. Now suppose we observe the host “mx1.bigcorp.com” send, over a period of time, 50 emails, of which 2 were spam.
- FIG. 7 illustrates the observation that a host “home-user-9-8-7-6.nyc.someisp.net” 710 send 25 emails, 22 of which were spam.
- the metrics for “NYC” 708 , “someisp” 704 , and “net” 702 show the counts from below in the tree.
- FIG. 8 another New York-based SomeISP customer “home-user-5-6-7-8.nyc.someisp.net” 802 is seen sending 80 emails, of which 70 were spam, where the metrics for “NYC” 708 , “someisp” 704 , “net” 702 , and root 302 A show the additional counts from the new host 802 .
- FIG. 9 we observe SomeISP's mail server “smtp52.someisp.net” 902 send 200 emails, 5 of which were spam.
- a reputation in this instance, the probability that a subsequent email will be spam
- a host already in the tree We break apart and reverse the labels as during an insert, and walk the tree from the root until we find the corresponding leaf node.
- Querying may be performed in the same way as with the logical tree as described herein, by walking from the root 302 B to the leaf (or as far as possible in the case of a partial match) and calculating or estimating the reputation score at that point.
- the same statistical method as described herein may be used to obtain a confidence interval in the estimated probability.
- the present invention uses hierarchies to model parent/child relationships between and within entities 208 , thereby representing the entities 208 in a natural and useful way. This is achieved through the inheritance of reputation from ancestral entities to their descendants.
- a significant advantage of the present invention may be that reputation can be assigned to entities 208 even if they have never been seen before, provided the entity 208 has a known ancestor somewhere in the reputation tree. As a result the system may not need to be updated as often, and may only degrade slowly in its utility over time if updates do not occur, and thus the data may be updated and published on a less demanding schedule.
- this invention may provide a unified view of all relationships affecting the reputability of an entity 208 , from the network owner at the highest level to individual hosts, web pages etc. at the lowest level.
- it may be possible to assign a reliable and statistically justifiable reputation score to Internet entities 208 even if previously unseen, while eliminating the requirement that the model be updated and published to consumers with the utmost urgency.
- using the present invention may result in more botnet spam blocked than is possible with a simple flat list of bad senders, no matter how rapidly it is updated.
- the present invention may receive a communication 1502 from a first communication identifier, parse the first communication identifier into its components, and assign the components to a hierarchical tree structure, where the hierarchical tree structure maintains the hierarchical relationship between the components of the communication identifier.
- the present invention may monitor and keep count 1504 of a number of communications from the first communication identifier, wherein the number of communications may be kept for both malicious and/or unwanted communications and non-malicious and/or unwanted communications. Attributes may then be provided 1508 to the number of communications for each appropriate component of the hierarchical tree, and a statistical measure may be calculated as related to the number of communications for each component of the hierarchical tree. The present invention may then receive a communication 1510 from a second communication identifier, where the second communication identifier may be previously unknown and have a common component with the hierarchical tree.
- the statistical measure of the common component may then be assigned 1512 to the second communication identifier, and utilizing the statistical measure assigned to the second communication identifier, may provide a prediction of reputation of the second communication identifier.
- the communication identifier may be in the form of a web address, a domain name, domain name components, an IP address, IP address components, an email address, an IM address, a telephone number, a VoIP telephony address, and the like.
- the component may be at a root level, a top level, a lower level, and the like.
- the at least one of malicious and unwanted communication may be spam, from a computer that is part of a botnet, and the like.
- the statistical measure may relate the number of at least one of malicious and unwanted communications to the number of total communications.
- the reputation may be related to how much spam the website communicates.
- the methods and systems described herein may be deployed in part or in whole through a machine that executes computer software, program codes, and/or instructions on a processor.
- the present invention may be implemented as a method on the machine, as a system or apparatus as part of or in relation to the machine, or as a computer program product embodied in a computer readable medium executing on one or more of the machines.
- the processor may be part of a server, client, network infrastructure, mobile computing platform, stationary computing platform, or other computing platform.
- a processor may be any kind of computational or processing device capable of executing program instructions, codes, binary instructions and the like.
- the processor may be or include a signal processor, digital processor, embedded processor, microprocessor or any variant such as a co-processor (math co-processor, graphic co-processor, communication co-processor and the like) and the like that may directly or indirectly facilitate execution of program code or program instructions stored thereon.
- the processor may enable execution of multiple programs, threads, and codes. The threads may be executed simultaneously to enhance the performance of the processor and to facilitate simultaneous operations of the application.
- methods, program codes, program instructions and the like described herein may be implemented in one or more thread.
- the thread may spawn other threads that may have assigned priorities associated with them; the processor may execute these threads based on priority or any other order based on instructions provided in the program code.
- the processor may include memory that stores methods, codes, instructions and programs as described herein and elsewhere.
- the processor may access a storage medium through an interface that may store methods, codes, and instructions as described herein and elsewhere.
- the storage medium associated with the processor for storing methods, programs, codes, program instructions or other type of instructions capable of being executed by the computing or processing device may include but may not be limited to one or more of a CD-ROM, DVD, memory, hard disk, flash drive, RAM, ROM, cache and the like.
- a processor may include one or more cores that may enhance speed and performance of a multiprocessor.
- the process may be a dual core processor, quad core processors, other chip-level multiprocessor and the like that combine two or more independent cores (called a die).
- the methods and systems described herein may be deployed in part or in whole through a machine that executes computer software on a server, client, firewall, gateway, hub, router, or other such computer and/or networking hardware.
- the software program may be associated with a server that may include a file server, print server, domain server, internet server, intranet server and other variants such as secondary server, host server, distributed server and the like.
- the server may include one or more of memories, processors, computer readable media, storage media, ports (physical and virtual), communication devices, and interfaces capable of accessing other servers, clients, machines, and devices through a wired or a wireless medium, and the like.
- the methods, programs or codes as described herein and elsewhere may be executed by the server.
- other devices required for execution of methods as described in this application may be considered as a part of the infrastructure associated with the server.
- the server may provide an interface to other devices including, without limitation, clients, other servers, printers, database servers, print servers, file servers, communication servers, distributed servers and the like. Additionally, this coupling and/or connection may facilitate remote execution of program across the network. The networking of some or all of these devices may facilitate parallel processing of a program or method at one or more location without deviating from the scope of the invention.
- any of the devices attached to the server through an interface may include at least one storage medium capable of storing methods, programs, code and/or instructions.
- a central repository may provide program instructions to be executed on different devices.
- the remote repository may act as a storage medium for program code, instructions, and programs.
- the software program may be associated with a client that may include a file client, print client, domain client, internet client, intranet client and other variants such as secondary client, host client, distributed client and the like.
- the client may include one or more of memories, processors, computer readable media, storage media, ports (physical and virtual), communication devices, and interfaces capable of accessing other clients, servers, machines, and devices through a wired or a wireless medium, and the like.
- the methods, programs or codes as described herein and elsewhere may be executed by the client.
- other devices required for execution of methods as described in this application may be considered as a part of the infrastructure associated with the client.
- the client may provide an interface to other devices including, without limitation, servers, other clients, printers, database servers, print servers, file servers, communication servers, distributed servers and the like. Additionally, this coupling and/or connection may facilitate remote execution of program across the network. The networking of some or all of these devices may facilitate parallel processing of a program or method at one or more location without deviating from the scope of the invention.
- any of the devices attached to the client through an interface may include at least one storage medium capable of storing methods, programs, applications, code and/or instructions.
- a central repository may provide program instructions to be executed on different devices.
- the remote repository may act as a storage medium for program code, instructions, and programs.
- the methods and systems described herein may be deployed in part or in whole through network infrastructures.
- the network infrastructure may include elements such as computing devices, servers, routers, hubs, firewalls, clients, personal computers, communication devices, routing devices and other active and passive devices, modules and/or components as known in the art.
- the computing and/or non-computing device(s) associated with the network infrastructure may include, apart from other components, a storage medium such as flash memory, buffer, stack, RAM, ROM and the like.
- the processes, methods, program codes, instructions described herein and elsewhere may be executed by one or more of the network infrastructural elements.
- the methods, program codes, and instructions described herein and elsewhere may be implemented on a cellular network having multiple cells.
- the cellular network may either be frequency division multiple access (FDMA) network or code division multiple access (CDMA) network.
- FDMA frequency division multiple access
- CDMA code division multiple access
- the cellular network may include mobile devices, cell sites, base stations, repeaters, antennas, towers, and the like.
- the cell network may be a GSM, GPRS, 3G, EVDO, mesh, or other networks types.
- the mobile devices may include navigation devices, cell phones, mobile phones, mobile personal digital assistants, laptops, palmtops, netbooks, pagers, electronic books readers, music players and the like. These devices may include, apart from other components, a storage medium such as a flash memory, buffer, RAM, ROM and one or more computing devices.
- the computing devices associated with mobile devices may be enabled to execute program codes, methods, and instructions stored thereon. Alternatively, the mobile devices may be configured to execute instructions in collaboration with other devices.
- the mobile devices may communicate with base stations interfaced with servers and configured to execute program codes.
- the mobile devices may communicate on a peer to peer network, mesh network, or other communications network.
- the program code may be stored on the storage medium associated with the server and executed by a computing device embedded within the server.
- the base station may include a computing device and a storage medium.
- the storage device may store program codes and instructions executed by the computing devices associated with the base station.
- the computer software, program codes, and/or instructions may be stored and/or accessed on machine readable media that may include: computer components, devices, and recording media that retain digital data used for computing for some interval of time; semiconductor storage known as random access memory (RAM); mass storage typically for more permanent storage, such as optical discs, forms of magnetic storage like hard disks, tapes, drums, cards and other types; processor registers, cache memory, volatile memory, non-volatile memory; optical storage such as CD, DVD; removable media such as flash memory (e.g.
- RAM random access memory
- mass storage typically for more permanent storage, such as optical discs, forms of magnetic storage like hard disks, tapes, drums, cards and other types
- processor registers cache memory, volatile memory, non-volatile memory
- optical storage such as CD, DVD
- removable media such as flash memory (e.g.
- USB sticks or keys floppy disks, magnetic tape, paper tape, punch cards, standalone RAM disks, Zip drives, removable mass storage, off-line, and the like; other computer memory such as dynamic memory, static memory, read/write storage, mutable storage, read only, random access, sequential access, location addressable, file addressable, content addressable, network attached storage, storage area network, bar codes, magnetic ink, and the like.
- the methods and systems described herein may transform physical and/or or intangible items from one state to another.
- the methods and systems described herein may also transform data representing physical and/or intangible items from one state to another.
- machines may include, but may not be limited to, personal digital assistants, laptops, personal computers, mobile phones, other handheld computing devices, medical equipment, wired or wireless communication devices, transducers, chips, calculators, satellites, tablet PCs, electronic books, gadgets, electronic devices, devices having artificial intelligence, computing devices, networking equipments, servers, routers and the like.
- the elements depicted in the flow chart and block diagrams or any other logical component may be implemented on a machine capable of executing program instructions.
- the methods and/or processes described above, and steps thereof, may be realized in hardware, software or any combination of hardware and software suitable for a particular application.
- the hardware may include a general purpose computer and/or dedicated computing device or specific computing device or particular aspect or component of a specific computing device.
- the processes may be realized in one or more microprocessors, microcontrollers, embedded microcontrollers, programmable digital signal processors or other programmable device, along with internal and/or external memory.
- the processes may also, or instead, be embodied in an application specific integrated circuit, a programmable gate array, programmable array logic, or any other device or combination of devices that may be configured to process electronic signals. It will further be appreciated that one or more of the processes may be realized as a computer executable code capable of being executed on a machine readable medium.
- the computer executable code may be created using a structured programming language such as C, an object oriented programming language such as C++, or any other high-level or low-level programming language (including assembly languages, hardware description languages, and database programming languages and technologies) that may be stored, compiled or interpreted to run on one of the above devices, as well as heterogeneous combinations of processors, processor architectures, or combinations of different hardware and software, or any other machine capable of executing program instructions.
- a structured programming language such as C
- an object oriented programming language such as C++
- any other high-level or low-level programming language including assembly languages, hardware description languages, and database programming languages and technologies
- each method described above and combinations thereof may be embodied in computer executable code that, when executing on one or more computing devices, performs the steps thereof.
- the methods may be embodied in systems that perform the steps thereof, and may be distributed across devices in a number of ways, or all of the functionality may be integrated into a dedicated, standalone device or other hardware.
- the means for performing the steps associated with the processes described above may include any of the hardware and/or software described above. All such permutations and combinations are intended to fall within the scope of the present disclosure.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Entrepreneurship & Innovation (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Tourism & Hospitality (AREA)
- General Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Description
- 1. Field
- The present invention is related to computer security, and more specifically to reputation of Internet entities.
- 1. Description of the Related Art
- Assessing the reputation (“trustworthiness”) of Internet entities via identifiers such as IP addresses and hostnames is a fundamental network security task. Most current approaches relying on black- and white-lists of known identifiers suffer from a grave weakness: they are unable to assign a reputation score to an entity not already encountered—such as the many thousands of new bots that are brought online daily. Therefore there exists a need for improved reputation assessment, where a reputation score may be assigned to new entities as they are encountered for the first time.
- In embodiments, the present invention may provide for a hierarchical modeling processing facility to build a hierarchical reputation model of Internet entities that allows for the automated clustering of “neighborhoods” of related systems, and thus the reputation assessment even of brand new hosts within a neighborhood. The reputation of such a neighborhood, with an accompanying confidence level, may be derived statistically from measurements of observed behavior of the systems within it. This may in turn be used to produce an action to provide additional security to users.
- In embodiments of the present invention improved capabilities are described for predicting the reputation of a communication identifier, such as a web address, a domain name, an IP address, host name, email address, IM address, telephone number, VoIP telephony address, and the like. In embodiments, the present invention may receive a communication from a first communication identifier, parse the first communication identifier into its components, and assign the components to a hierarchical tree structure, where the hierarchical tree structure maintains the hierarchical relationship between the components of the communication identifier. The present invention may monitor and keep count of a number of communications from the first communication identifier, wherein the number of communications may be kept for both malicious and/or unwanted communications and non-malicious and/or unwanted communications. Attributes may then be provided to the number of communications for each appropriate component of the hierarchical tree, and a statistical measure may be calculated as related to the number of communications for each component of the hierarchical tree. The present invention may then receive a communication from a second communication identifier, where the second communication identifier may be previously unknown and have a common component with the hierarchical tree. The statistical measure of the common component may then be assigned to the second communication identifier, and utilizing the statistical measure assigned to the second communication identifier, may provide a prediction of reputation of the second communication identifier. In embodiments, the communication identifier may be in the form of a web address, a domain name, domain name components, an IP address, IP address components, an email address, an IM address, a telephone number, a VoIP telephony address, and the like. In embodiments, the component may be at a root level, a top level, a lower level, and the like. In embodiments, the at least one of malicious and unwanted communication may be spam, from a computer that is part of a botnet, and the like. In embodiments, the statistical measure may relate the number of at least one of malicious and unwanted communications to the number of total communications. In embodiments, the reputation may be related to how much spam the website communicates.
- These and other systems, methods, objects, features, and advantages of the present invention will be apparent to those skilled in the art from the following detailed description of the preferred embodiment and the drawings. All documents mentioned herein are hereby incorporated in their entirety by reference.
- The invention and the following detailed description of certain embodiments thereof may be understood by reference to the following figures:
-
FIG. 1 depicts a block diagram of a threat management facility providing protection to an enterprise against a plurality of threats. -
FIG. 2 depicts the security management facility related to Internet entities through a hierarchical modeling processing facility and reputation database. -
FIG. 3 depicts an example of a hierarchical tree structure in an embodiments of the present invention. -
FIGS. 4 through 10 depict an example of how a hierarchical tree may be built for a domain name structure in an embodiment of the present invention. -
FIGS. 11 through 14 depict an example of how a hierarchical tree may be built for an IP address structure in an embodiment of the present invention. -
FIG. 15 depicts a functional flow diagram in an embodiment of the present invention. - While the invention has been described in connection with certain preferred embodiments, other embodiments would be understood by one of ordinary skill in the art and are encompassed herein.
- All documents referenced herein are hereby incorporated by reference.
-
FIG. 1 depicts a block diagram of a threat management facility providing protection to an enterprise against a plurality of threats. An aspect of the present invention relates to corporate policy management and implementation through a unifiedthreat management facility 100. As will be explained in more detail below, athreat management facility 100 may be used to protect computer assets from many threats, both computer-generated threats and user-generated threats. Thethreat management facility 100 may be multi-dimensional in that it may be designed to protect corporate assets from a variety of threats and it may be adapted to learn about threats in one dimension (e.g. worm detection) and apply the knowledge in another dimension (e.g. spam detection). Policy management is one of the dimensions for which the threat management facility can provide a control capability. A corporation or other entity may institute a policy that prevents certain people (e.g. employees, groups of employees, types of employees, guest of the corporation, etc.) from accessing certain types of computer programs. For example, the corporation may elect to prevent its accounting department from using a particular version of an instant messaging service or all such services. In this example, thepolicy management facility 112 may be used to update the policies of all corporate computing assets with a proper policy control facility or it may update a select few. By using thethreat management facility 100 to facilitate the setting, updating and control of such policies the corporation only needs to be concerned with keeping thethreat management facility 100 up to date on such policies. Thethreat management facility 100 can take care of updating all of the other corporate computing assets. - It should be understood that the
threat management facility 100 may provide multiple services, and policy management may be offered as one of the services. We will now turn to a description of certain capabilities and components of thethreat management system 100. - Over recent years, malware has become a major problem across the
internet 154. From both technical and user perspectives, the categorization of a specific threat type, whether as virus, worm, spam, phishing exploration, spyware, adware, or the like, is becoming reduced in significance. The threat, no matter how it is categorized, may need to be stopped at various points of a networked computing environment, such as one of anenterprise facility 102, including at one or more laptops, desktops, servers, such as the server facility 142, gateways, communication ports, handheld or mobile devices, firewalls, and the like. Similarly, there may be less and less benefit to the user in having different solutions for known and unknown threats. As such, a consolidatedthreat management facility 100 may need to apply a similar set of technologies and capabilities for all threats. In certain embodiments, thethreat management facility 100 may provide a single agent on the desktop, and a single scan of any suspect file. This approach may eliminate the inevitable overlaps and gaps in protection caused by treating viruses and spyware as separate problems, while simultaneously simplifying administration and minimizing desktop load. As the number and range of types of threats has increased, so may have the level of connectivity available to all IT users. This may have lead to a rapid increase in the speed at which threats may move. Today, an unprotected PC connected to theinternet 154 may be infected quickly (perhaps within 10 minutes) which may require acceleration for the delivery of threat protection. Where once monthly updates may have been sufficient, thethreat management facility 100 may automatically and seamlessly update its product set against spam and virus threats quickly, for instance, every five minutes, every minute, continuously, or the like. Analysis and testing may be increasingly automated, and also may be performed more frequently; for instance, it may be completed in 15 minutes, and may do so without compromising quality. Thethreat management facility 100 may also extend techniques that may have been developed for virus and malware protection, and provide them toenterprise facility 102 network administrators to better control their environments. In addition to stopping malicious code, thethreat management facility 100 may provide policy management that may be able to control legitimate applications, such as VoIP, instant messaging, peer-to-peer file-sharing, and the like, that may undermine productivity and network performance within theenterprise facility 102. - The
threat management facility 100 may provide anenterprise facility 102 protection from computer-based malware, including viruses, spyware, adware, Trojans, intrusion, spam, policy abuse, uncontrolled access, and the like, where theenterprise facility 102 may be any entity with a networked computer-based infrastructure. In an embodiment,FIG. 1 may depict a block diagram of the threat management facility providing protection to an enterprise against a plurality of threats. Theenterprise facility 102 may be corporate, commercial, educational, governmental, or the like, and the enterprise facility's 102 computer network may be distributed amongst a plurality of facilities, and in a plurality of geographical locations. Thethreat management facility 100 may include a plurality of functions, such assecurity management facility 122,policy management facility 112,update facility 120,definitions facility 114, networkaccess rules facility 124,remedial action facility 128,detection techniques facility 130,testing facility 118,threat research facility 132, and the like. In embodiments, the threat protection provided by thethreat management facility 100 may extend beyond the network boundaries of theenterprise facility 102 to include client facilities 144 that have moved into network connectivity not directly associated or controlled by theenterprise facility 102. Threats to client facilities 144 may come from a plurality of sources, such as fromnetwork threats 104,physical proximity threats 110,secondary location threats 108, and the like. In embodiments, thethreat management facility 100 may provide anenterprise facility 102 protection from a plurality of threats to multiplatform computer resources in a plurality of locations and network configurations, with an integrated system approach. - In embodiments, the
threat management facility 100 may be provided as a stand-alone solution. In other embodiments, thethreat management facility 100 may be integrated into a third-party product. An application programming interface (e.g. a source code interface) may be provided such that thethreat management facility 100 may be integrated. For instance, thethreat management facility 100 may be stand-alone in that it provides direct threat protection to an enterprise or computer resource, where protection is subscribed to directly 100. Alternatively, the threat management facility may offer protection indirectly, through a third-party product, where an enterprise may subscribe to services through the third-party product, and threat protection to the enterprise may be provided by thethreat management facility 100 through the third-party product. - The
security management facility 122 may include a plurality of elements that provide protection from malware toenterprise facility 102 computer resources, including endpoint security and control, email security and control, web security and control, reputation-based filtering, control of unauthorized users, control of guest and non-compliant computers, and the like. Thesecurity management facility 122 may be a software application that may provide malicious code and malicious application protection to a client facility 144 computing resource. Thesecurity management facility 122 may have the ability to scan the client facility 144 files for malicious code, remove or quarantine certain applications and files, prevent certain actions, perform remedial actions and perform other security measures. In embodiments, scanning the client facility 144 may include scanning some or all of the files stored to the client facility 144 on a periodic basis, may scan applications once the application has been requested to execute, may scan files as the files are transmitted to or from the client facility 144, or the like. The scanning of the applications and files may be to detect known malicious code or known unwanted applications. In an embodiment, new malicious code and unwanted applications may be continually developed and distributed, and updates to the known code database may be provided on a periodic basis, on a demand basis, on an alert basis, or the like. - In an embodiment, the
security management facility 122 may provide for email security and control, where security management may help to eliminate spam, viruses, spyware and phishing, control of email content, and the like. The security management facility's 122 email security and control may protect against inbound and outbound threats, protect email infrastructure, prevent data leakage, provide spam filtering, and the like. In an embodiment,security management facility 122 may provide for web security and control, where security management may help to detect or block viruses, spyware, malware, unwanted applications, help control web browsing, and the like, which may provide comprehensive web access control enabling safe, productive web browsing. Web security and control may provide internet use policies, reporting on suspect devices, security and content filtering, active monitoring of network traffic, URI filtering, and the like. In an embodiment, thesecurity management facility 122 may provide for network access control, which may provide control over network connections. Network control may stop unauthorized, guest, or non-compliant systems from accessing networks, and may control network traffic that may not be bypassed from the client level. In addition, network access control may control access to virtual private networks (VPN), where VPNs may be a communications network tunneled through another network, establishing a logical connection acting as a virtual network. In embodiments, a VPN may be treated in the same manner as a physical network. - In an embodiment, the
security management facility 122 may provide for host intrusion prevention through behavioral based protection, which may guard against unknown threats by analyzing behavior before software code executes. Behavioral based protection may monitor code when it runs and intervene if the code is deemed to be suspicious or malicious. Advantages of behavioral based protection over runtime protection may include code being prevented from running, whereas runtime protection may only interrupt code that has already partly executed; behavioral protection may identify malicious code at the gateway or on the file servers and deletes it before reaching end-point computers and the like. - In an embodiment, the
security management facility 122 may provide for reputation filtering, which may target or identify sources of known malware. For instance, reputation filtering may include lists of URIs of known sources of malware or known suspicious IP addresses, or domains, say for spam, that when detected may invoke an action by thethreat management facility 100, such as dropping them immediately. By dropping the source before any interaction can initiate, potential threat sources may be thwarted before any exchange of data can be made. - In embodiments, information may be sent from the enterprise back to a third party, a vendor, or the like, which may lead to improved performance of the
threat management facility 100. For example, the types, times, and number of virus interactions that a client experiences may provide useful information for the preventions of future virus threats. This type of feedback may be useful for any aspect of threat detection. Feedback of information may also be associated with behaviors of individuals within the enterprise, such as being associated with most common violations of policy, network access, unauthorized application loading, unauthorized external device use, and the like. In embodiments, this type of information feedback may enable the evaluation or profiling of client actions that are violations of policy that may provide a predictive model for the improvement of enterprise policies. - In an embodiment, the
security management facility 122 may provide for the overall security of theenterprise facility 102 network or set ofenterprise facility 102 networks, may provide updates of malicious code information to theenterprise facility 102 network, and associated client facilities 144. The updates may be a planned update, an update in reaction to a threat notice, an update in reaction to a request for an update, an update based on a search of known malicious code information, or the like. Theadministration facility 134 may provide control over thesecurity management facility 122 when updates are performed. The updates may be automatically transmitted without an administration facility's 134 direct control, manually transmitted by theadministration facility 134, or the like. Thesecurity management facility 122 may include the management of receiving malicious code descriptions from a provider, distribution of malicious code descriptions toenterprise facility 102 networks, distribution of malicious code descriptions to client facilities 144, or the like. In an embodiment, the management of malicious code information may be provided to the enterprise facility's 102 network, where the enterprise facility's 102 network may provide the malicious code information through the enterprise facility's 102 network distribution system. - The
threat management facility 100 may provide apolicy management facility 112 that may be able to block non-malicious applications, such asVoIP 164,instant messaging 162, peer-to-peer file-sharing, and the like, that may undermine productivity and network performance within theenterprise facility 102. Thepolicy management facility 112 may be a set of rules or policies that may indicateenterprise facility 102 access permissions for the client facility 144, such as access permissions associated with the network, applications, external computer devices, and the like. Thepolicy management facility 112 may include a database, a text file, a combination of databases and text files, or the like. In an embodiment, a policy database may be a block list, a black list, an allowed list, a white list, or the like that may provide a list ofenterprise facility 102 external network locations/applications that may or may not be accessed by the client facility 144. Thepolicy management facility 112 may include rules that may be interpreted with respect to anenterprise facility 102 network access request to determine if the request should be allowed. The rules may provide a generic rule for the type of access that may be granted; the rules may be related to the policies of anenterprise facility 102 for access rights for the enterprise facility's 102 client facility 144. For example, there may be a rule that does not permit access to sporting websites. When a website is requested by the client facility 144, a security facility may access the rules within a policy facility to determine if the requested access is related to a sporting website. In an embodiment, the security facility may analyze the requested website to determine if the website matches with any of the policy facility rules. - The
policy management facility 112 may be similar to thesecurity management facility 122 but with the addition ofenterprise facility 102 wide access rules and policies that may be distributed to maintain control of client facility 144 access toenterprise facility 102 network resources. The policies may be defined for application type, subset of application capabilities, organization hierarchy, computer facility type, user type, network location, time of day, connection type, or the like. Policies may be maintained by theadministration facility 134, through thethreat management facility 100, in association with a third party, or the like. For example, a policy may restrictIM 162 activity to only support personnel for communicating with customers. This may allow communication for departments requiring access, but may maintain the network bandwidth for other activities by restricting the use ofIM 162 to only the personnel that need access toIM 162 in support of theenterprise facility 102. In an embodiment, thepolicy management facility 112 may be a stand-alone application, may be part of the network server facility 142, may be part of theenterprise facility 102 network, may be part of the client facility 144, or the like. - In embodiments, the
threat management facility 100 may provide configuration management, which may be similar to policy management, but may specifically examine the configuration set of applications, operating systems, hardware, and the like, and managing changes to their configurations. Assessment of a configuration may be made against a standard configuration policy, detection of configuration changes, remediation of improper configuration, application of new configurations, and the like. An enterprise may keep a set of standard configuration rules and policies which may represent the desired state of the device. For example, a client firewall may be running and installed, but in the disabled state, where remediation may be to enable the firewall. In another example, the enterprise may set a rule that disallows the use of USB disks, and sends a configuration change to all clients, which turns off USB drive access via a registry. - In embodiments, the
threat management facility 100 may also provide for the removal of applications that may interfere with the operation of thethreat management facility 100, such as competitor products that may also be attempting similar threat management functions. The removal of such products may be initiated automatically whenever such products are detected. In the case where such applications are services are provided indirectly through a third-party product, the application may be suspended until action is taken to remove or disable the third-party product's protection facility. - Threat management against a sometimes quickly evolving malware environment may require timely updates, and the
update management facility 120 may be provided by thethreat management facility 100. In addition, apolicy management facility 112 may also require update management (e.g. as provided by theupdate facility 120 herein described), as theenterprise facility 102 requirements for policies changeenterprise facility 102, client facility 144, server facility 142enterprise facility 102. The update management for thesecurity facility 122 andpolicy management facility 112 may be provided directly by thethreat management facility 100, such as by a hosted system or in conjunction with theadministration facility 134. In embodiments, thethreat management facility 100 may provide for patch management, where a patch may be an update to an operating system, an application, a system tool, or the like, where one of the reasons for the patch is to reduce vulnerability to threats. - In embodiments, the
security facility 122 andpolicy management facility 112 may push information to theenterprise facility 102 network and/or client facility 144, theenterprise facility 102 network and/or client facility 144 may pull information from thesecurity facility 122 andpolicy management facility 112 network server facilities 142, there may be a combination of pushing and pulling of information between thesecurity facility 122 and thepolicy management facility 112 network servers 142,enterprise facility 102 network, and client facilities 144, or the like. For example, theenterprise facility 102 network and/or client facility 144 may pull information from thesecurity facility 122 andpolicy management facility 112 network server facility 142 may request the information using thesecurity facility 122 andpolicy management facility 112 update module; the request may be based on a certain time period, by a certain time, by a date, on demand, or the like. In another example, thesecurity facility 122 andpolicy management facility 112 network servers 142 may push the information to the enterprise facility's 102 network and/or client facility 144 by providing notification that there are updates available for download and then transmitting the information. The combination of thesecurity management 122 network server facility 142 and security update module may function substantially the same as thepolicy management facility 112 network server and policy update module by providing information to theenterprise facility 102 network and the client facility 144 in a push or pull method. In an embodiment, thepolicy management facility 112 and thesecurity facility 122 management update modules may work in concert to provide all the needed information to the enterprise facility's 102 network and/or client facility 144 for control of application execution. In an embodiment, the policy update module and security update module may be combined into a single update module. - As threats are identified and characterized, the
threat management facility 100 may create definition updates that may be used to allow thethreat management facility 100 to detect and remediate the latest malicious software, unwanted applications, configuration and policy changes, and the like. Thethreat definition facility 114 may contain threat identification updates, also referred to as definition files. A definition file may be a virus identity file that may include definitions of known or potential malicious code. The virus identity (IDE) definition files may provide information that may identify malicious code within files, applications, or the like. The definition files may be accessed bysecurity management facility 122 when scanning files or applications within the client facility 144 for the determination of malicious code that may be within the file or application. The definition files may contain a number of commands, definitions, or instructions, to be parsed and acted upon, or the like. In embodiments, the client facility 144 may be updated with new definition files periodically to provide the client facility 144 with the most recent malicious code definitions; the updating may be performed on a set time period, may be updated on demand from the client facility 144, may be updated on demand from the network, may be updated on a received malicious code alert, or the like. In an embodiment, the client facility 144 may request an update to the definition files from anupdate facility 120 within the network, may request updated definition files from a computing facility external to the network, updated definition files may be provided to theclient facility 114 from within the network, definition files may be provided to the client facility 144 from an external computing facility from an external network, or the like. - In an embodiment, a
definition management facility 114 may provide for the timely updates of definition files information to the network, client facilities 144, and the like. New and altered malicious code and malicious applications may be continually created and distributed to networks worldwide. The definition files that maintain the definitions of the malicious code and malicious application information for the protection of the networks and client facilities 144 may need continual updating to provide continual defense of the network and client facility 144 from the malicious code and malicious applications. The definition files management may provide for automatic and manual methods of updating the definition files. In embodiments, the network may receive definition files and distribute the definition files to the network client facilities 144, the client facilities 144 may receive the definition files directly, or the network and client facilities 144 may both receive the definition files, or the like. In an embodiment, the definition files may be updated on a fixed periodic basis, on demand by the network and/or the client facility 144, as a result of an alert of a new malicious code or malicious application, or the like. In an embodiment, the definition files may be released as a supplemental file to an existing definition files to provide for rapid updating of the definition files. - In a similar manner, the
security management facility 122 may be used to scan an outgoing file and verify that the outgoing file is permitted to be transmitted per theenterprise facility 102 rules and policies. By checking outgoing files, thesecurity management facility 122 may be able discover malicious code infected files that were not detected as incoming files as a result of the client facility 144 having been updated with either new definition files orpolicy management facility 112 information. The definition files may discover the malicious code infected file by having received updates of developing malicious code from theadministration facility 134, updates from a definition files provider, or the like. Thepolicy management facility 112 may discover the malicious code infected file by having received new updates from theadministration facility 134, from a rules provider, or the like. - The
threat management facility 100 may provide for a way to control access to theenterprise facility 102 networks. For instance, theenterprise facility 102 may want to restrict access to certain applications, networks, files, printers, servers, databases, or the like. In addition, theenterprise facility 102 may want to restrict user access under certain conditions, such as the user's location, usage history, need to know, job position, connection type, time of day, method of authentication, client-system configuration, or the like. Network access rules may be developed by theenterprise facility 102, or pre-packaged by a supplier, and managed by thethreat management facility 100 in conjunction with theadministration facility 134. Network access rules and control may be responsible for determining if a client facility 144 application should be granted access to a requested network location. The network location may be on the same network as the facility or may be on another network. In an embodiment, the network access control may verify access rights for client facilities 144 from within the network or may verify access rights of computer facilities from external networks. When network access for a client facility 144 is denied, the network access control may send an information file to the client facility 144, the information file may contain data or commands that may provide instructions for theremedial action facility 128. The information sent by thenetwork access facility 124 control may be a data file. The data file may contain a number of commands, definitions, instructions, or commands to be parsed and acted upon through theremedial action facility 128, or the like. The information sent by thenetwork access facility 124 control may be a command or command file that theremedial action facility 128 may access and take action upon. - In an embodiment, the
network access rules 124 may provide an information store to be accessed by the network access control. The networkaccess rules facility 124 may include databases such as a block list, a black list, an allowed list, a white list, an unacceptable network site database, an acceptable network site database, a network site reputation database, or the like of network access locations that may or may not be accessed by the client facility 144. Additionally, the networkaccess rules facility 124 may incorporate rule evaluation; the rule evaluation may parse network access requests and apply the parsed information to network access rules. The networkaccess rule facility 124 may have a generic set of rules that may be in support of an enterprise facility's 102 network access policies, such as denying access to certain types ofwebsites 158, controllinginstant messenger 162 accesses, or the like. Rule evaluation may include regular expression rule evaluation, or other rule evaluation method for interpreting the network access request and comparing the interpretation to the established rules for network access. In an embodiment, the networkaccess rules facility 124 may receive a rules evaluation request from the network access control and may return the rules evaluation to the network access control. - Similar to the
threat definitions facility 114, the networkaccess rule facility 124 may provide updated rules and policies to theenterprise facility 102. The networkaccess rules facility 124 may be maintained by thenetwork administration facility 134, using networkaccess rules facility 124 management. In an embodiment, thenetwork administration facility 134 may be able to maintain a set of access rules manually by adding rules, changing rules, deleting rules, or the like. Additionally, theadministration facility 134 may be able to retrieve predefined rule sets from a provider that may provide a set of rules to be applied to anentire enterprise facility 102. Thenetwork administration facility 134 may be able to modify the predefined rules as needed for aparticular enterprise facility 102 using the network accessrules management facility 124. - When a threat or policy violation is detected by the
threat management facility 100, thethreat management facility 100 may provide for aremedial action facility 128. Remedial action may take a plurality of forms, such as terminating or modifying an ongoing process or interaction, sending a warning to a client oradministration facility 134 of an ongoing process or interaction, executing a program or application to remediate against a threat or violation, record interactions for subsequent evaluation, or the like. Remedial action may be associated with an application that responds to information that a client facility 144 network access request has been denied. In an embodiment, when the data file is received, remedial action may parse the data file, interpret the various aspects of the data file, and act on the parsed data file information to determine actions to be taken on an application requesting access to a denied network location. In an embodiment, when the data file is received, remedial action may access the threat definitions to parse the data file and determine an action to be taken on an application requesting access to a denied network location. In an embodiment, the information received from the facility may be a command or a command file. The remedial action facility may carry out any commands that are received or parsed from a data file from the facility without performing any interpretation of the commands. In an embodiment, the remedial action facility may interact with the received information and may perform various actions on a client requesting access to a denied network location. The action may be one or more of continuing to block all requests to a denied network location, a malicious code scan on the application, a malicious code scan on the client facility 144, quarantine of the application, terminating the application, isolation of the application, isolation of the client facility 144 to a location within the network that restricts network access, blocking a network access port from a client facility 144, reporting the application to aadministration facility 134, or the like. - Remedial action may be provided as a result of a detection of a threat or violation. The
detection techniques facility 130 may include monitoring theenterprise facility 102 network or end-point devices, such as by monitoring streaming data through the gateway, across the network, through routers and hubs, and the like. Thedetection techniques facility 130 may include monitoring activity and stored files on computing facilities, such as on server facilities 142, desktop computers, laptop computers, other mobile computing devices, and the like. Detection techniques, such as scanning a computer's stored files, may provide the capability of checking files for stored threats, either in the active or passive state. Detection techniques, such as streaming file management, may provide the capability of checking files received at the network, gateway facility, client facility 144, and the like. This may provide the capability of not allowing a streaming file or portions of the streaming file containing malicious code from entering the client facility 144, gateway facility, or network. In an embodiment, the streaming file may be broken into blocks of information, and a plurality of virus identities may be used to check each of the blocks of information for malicious code. In an embodiment, any blocks that are not determined to be clear of malicious code may not be delivered to the client facility 144, gateway facility, or network. - Verifying that the
threat management facility 100 is detecting threats and violations to established policy, may require the ability to test the system, either at the system level or for a particular computing component. Thetesting facility 118 may allow theadministration facility 134 to coordinate the testing of the security configurations of client facility 144 computing facilities on a network. Theadministration facility 134 may be able to send test files to a set of client facility 144 computing facilities to test the ability of the client facility 144 to determine acceptability of the test file. After the test file has been transmitted, a recording facility may record the actions taken by the client facility 144 in reaction to the test file. The recording facility may aggregate the testing information from the client facility 144 and report the testing information to theadministration facility 134. Theadministration facility 134 may be able to determine the level of preparedness of the client facility 144 computing facilities by the reported information. Remedial action may be taken for any of the client facility 144 computing facilities as determined by theadministration facility 134; remedial action may be taken by theadministration facility 134 or by the user of the client facility 144. - The
threat research facility 132 may provide a continuously ongoing effort to maintain the threat protection capabilities of thethreat management facility 100 in light of continuous generation of new or evolved forms of malware. Threat research may include researchers and analysts working on known and emerging malware, such as viruses, rootkits a spyware, as well as other computer threats such as phishing, spam, scams, and the like. In embodiments, through threat research, thethreat management facility 100 may be able to provide swift, global responses to the latest threats. - The
threat management facility 100 may provide threat protection to theenterprise facility 102, where theenterprise facility 102 may include a plurality of networked components, such as client facility 144, server facility 142,administration facility 134, firewall 138, gateway, hubs and routers 148, threat management appliance 140, desktop users, mobile users, and the like. In embodiments, it may be the end-pointcomputer security facility 152, located on a computer's desktop, which may provide threat protection to a user, and associatedenterprise facility 102. In embodiments, the term end-point may refer to a computer system that may source data, receive data, evaluate data, buffer data, or the like (such as a user's desktop computer as an end-point computer), a firewall as a data evaluation end-point computer system, a laptop as a mobile end-point computer, a PDA as a hand-held end-point computer, a mobile phone as an end-point computer, or the like. In embodiments, end-point may refer to a source or destination for data, including such components where the destination is characterized by an evaluation point for data, and where the data may be sent to a subsequent destination after evaluation. The end-pointcomputer security facility 152 may be an application loaded onto the computer platform or computer support component, where the application may accommodate the plurality of computer platforms and/or functional requirements of the component. For instance, a client facility 144 computer may be one of a plurality of computer platforms, such as Windows, Macintosh, Linux, and the like, where the end-pointcomputer security facility 152 may be adapted to the specific platform, while maintaining a uniform product and product services across platforms. Additionally, components may have different functions to serve within the enterprise facility's 102 networked computer-based infrastructure. For instance, computer support components provided as hubs and routers 148, server facility 142, firewalls 138, and the like, may require unique security application software to protect their portion of the system infrastructure, while providing an element in an integrated threat management system that extends out beyond thethreat management facility 100 to incorporate all computer resources under its protection. - The
enterprise facility 102 may include a plurality of client facility 144 computing platforms on which the end-pointcomputer security facility 152 is adapted. A client facility 144 computing platform may be a computer system that is able to access a service on another computer, such as a server facility 142, via a network. This client facility 144 server facility 142 model may apply to a plurality of networked applications, such as a client facility 144 connecting to anenterprise facility 102 application server facility 142, a web browser client facility 144 connecting to a web server facility 142, an e-mail client facility 144 retrieving e-mail from aninternet 154 service provider's mail storage servers 142, and the like. In embodiments, traditional large client facility 144 applications may be switched to websites, which may increase the browser's role as a client facility 144. Clients 144 may be classified as a function of the extent to which they perform their own processing. For instance, client facilities 144 are sometimes classified as a fat client facility 144 or thin client facility 144. The fat client facility 144, also known as a thick client facility 144 or rich client facility 144, may be a client facility 144 that performs the bulk of data processing operations itself, and does not necessarily rely on the server facility 142. The fat client facility 144 may be most common in the form of a personal computer, where the personal computer may operate independent of any server facility 142. Programming environments for fat clients 144 may include CURI, Delphi, Droplets, Java, win32, X11, and the like. Thin clients 144 may offer minimal processing capabilities, for instance, the thin client facility 144 may primarily provide a graphical user interface provided by an application server facility 142, which may perform the bulk of any required data processing. Programming environments for thin clients 144 may include JavaScript/AJAX, ASP, JSP, Ruby on Rails, Python's Django, PHP, and the like. The client facility 144 may also be a mix of the two, such as processing data locally, but relying on a server facility 142 for data storage. As a result, this hybrid client facility 144 may provide benefits from both the fat client facility 144 type, such as multimedia support and high performance, and the thin client facility 144 type, such as high manageability and flexibility. In embodiments, thethreat management facility 100, and associated end-pointcomputer security facility 152, may provide seamless threat protection to the plurality of clients 144, and client facility 144 types, across theenterprise facility 102. - The
enterprise facility 102 may include a plurality of server facilities 142, such as application servers, communications servers, file servers, database servers, proxy servers, mail servers, fax servers, game servers, web servers, and the like. A server facility 142, which may also be referred to as a server facility 142 application, server facility 142 operating system, server facility 142 computer, or the like, may be an application program or operating system that accepts client facility 144 connections in order to service requests from clients 144. The server facility 142 application may run on the same computer as the client facility 144 using it, or the server facility 142 and the client facility 144 may be running on different computers and communicating across the network. Server facility 142 applications may be divided among server facility 142 computers, with the dividing depending upon the workload. For instance, under light load conditions all server facility 142 applications may run on a single computer and under heavy load conditions a single server facility 142 application may run on multiple computers. In embodiments, thethreat management facility 100 may provide threat protection to server facilities 142 within theenterprise facility 102 as load conditions and application changes are made. - A server facility 142 may also be an appliance facility 140, where the appliance facility 140 provides specific services onto the network. Though the appliance facility 140 is a server facility 142 computer, that may be loaded with a server facility 142 operating system and server facility 142 application, the
enterprise facility 102 user may not need to configure it, as the configuration may have been performed by a third party. In an embodiment, anenterprise facility 102 appliance may be a server facility 142 appliance that has been configured and adapted for use with thethreat management facility 100, and located within the facilities of theenterprise facility 102. The enterprise facility's 102 threat management appliance may enable theenterprise facility 102 to administer an on-site local managed threat protection configuration, where theadministration facility 134 may access the threat resources through an interface, such as a web portal. In an alternate embodiment, theenterprise facility 102 may be managed remotely from a third party, vendor, or the like, without an appliance facility 140 located within theenterprise facility 102. In this instance, the appliance functionality may be a shared hardware product between pluralities ofenterprises 102. In embodiments, the appliance facility 140 may be located at theenterprise facility 102, where theenterprise facility 102 maintains a degree of control. In embodiments, a hosted service may be provided, where the appliance 140 may still be an on-site black box to theenterprise facility 102, physically placed there because of infrastructure requirements, but managed by a third party, vendor, or the like. - Simple server facility 142 appliances may also be utilized across the enterprise facility's 102 network infrastructure, such as switches, routers, wireless routers, hubs and routers, gateways, print servers, net modems, and the like. These simple server facility appliances may not require configuration by the
enterprise facility 102, but may require protection from threats via an end-pointcomputer security facility 152. These appliances may provide interconnection services within theenterprise facility 102 network, and therefore may advance the spread of a threat if not properly protected. - One way for a client facility 144 to be protected from threats from within the
enterprise facility 102 network may be a personal firewall. A personal firewall may be an application that controls network traffic to and from a client, permitting or denying communications based on a security policy. Personal firewalls may be designed for use by end-users, which may result in protection for only the computer on which it's installed. Personal firewalls may be able to control network traffic by providing prompts each time a connection is attempted and adapting security policy accordingly. Personal firewalls may also provide some level of intrusion detection, which may allow the software to terminate or block connectivity where it suspects an intrusion is being attempted. Other features that may be provided by a personal firewall may include alerts about outgoing connection attempts, control of program access to networks, hiding the client from port scans by not responding to unsolicited network traffic, monitoring of applications that may be listening for incoming connections, monitoring and regulation of incoming and outgoing network traffic, prevention of unwanted network traffic from installed applications, reporting applications that make connection attempts, reporting destination servers with which applications may be attempting communications, and the like. In embodiments, the personal firewall may be provided by thethreat management facility 100. - Another important component that may be protected by an end-point
computer security facility 152 is a network firewall facility 138, which may be a hardware or software device that may be configured to permit, deny, or proxy data through a computer network that has different levels of trust in its source of data. For instance, aninternal enterprise facility 102 network may have a high level of trust, because the source of all data has been sourced from within theenterprise facility 102. An example of a low level of trust is theInternet 154, because the source of data may be unknown. A zone with an intermediate trust level, situated between theInternet 154 and a trusted internal network, may be referred to as a “perimeter network”. Since firewall facilities 138 represent boundaries between threat levels, the end-pointcomputer security facility 152 associated with the firewall facility 138 may provide resources that may control the flow of threats at thisenterprise facility 102 network entry point. Firewall facilities 138, and associated end-pointcomputer security facility 152, may also be associated with a network node that may be equipped for interfacing between networks that use different protocols. In embodiments, the end-pointcomputer security facility 152 may provide threat protection in a plurality of network infrastructure locations, such as at theenterprise facility 102 network entry point, i.e. the firewall facility 138 or gateway; at the server facility 142; at distribution points within the network, i.e. the hubs and routers 148; at the desktop of client facility 144 computers; and the like. In embodiments, the most effective location for threat detection may be at the user's computer desktop end-pointcomputer security facility 152. - The interface between the
threat management facility 100 and theenterprise facility 102, and through the appliance facility 140 to embedded end-point computer security facilities, may include a set of tools that may be the same for all enterprise implementations, but allow each enterprise to implement different controls. In embodiments, these controls may include both automatic actions and managed actions. Automatic actions may include downloads of the end-pointcomputer security facility 152 to components of theenterprise facility 102, downloads of updates to existing end-point computer security facilities of theenterprise facility 102, uploaded network interaction requests fromenterprise facility 102 components to thethreat management facility 100, and the like. In embodiments, automatic interactions between theenterprise facility 102 and thethreat management facility 100 may be configured by thethreat management facility 100 and anadministration facility 134 in theenterprise facility 102. Theadministration facility 134 may configure policy rules that determine interactions, such as developing rules for accessing applications, as in who is authorized and when applications may be used; establishing rules for ethical behavior and activities; rules governing the use of entertainment software such as games, or personal use software such asIM 162 andVoIP 164; rules for determining access toenterprise facility 102 computing resources, including authentication, levels of access, risk assessment, and usage history tracking; rules for when an action is not allowed, such as whether an action is completely deigned or just modified in its execution; and the like. Theadministration facility 134 may also establish license management, which in turn may further determine interactions associated with a licensed application. In embodiments, interactions between thethreat management facility 100 and theenterprise facility 102 may provide threat protection to theenterprise facility 102 by managing the flow of network data into and out of theenterprise facility 102 through automatic actions that may be configured by thethreat management facility 100 or theadministration facility 134. - Client facilities 144 within the
enterprise facility 102 may be connected to theenterprise facility 102 network by way ofwired network facilities 148A orwireless network facilities 148B. Client facilities 144 connected to theenterprise facility 102 network via awired facility 148A orwireless facility 148B may receive similar protection, as both connection types are ultimately connected to thesame enterprise facility 102 network, with the same end-pointcomputer security facility 152, and the same threat protectedenterprise facility 102 environment. Mobilewireless facility clients 144B-F, because of their ability to connect to anywireless 148B,D network access point, may connect to theinternet 154 outside theenterprise facility 102, and therefore outside the threat-protected environment of theenterprise facility 102. In this instance themobile client facility 144B-F, if not for the presence of the end-pointcomputer security facility 152 may experience a malware attack or perform actions counter toenterprise facility 102 established policies. In addition, there may be a plurality of ways for thethreat management facility 100 to protect the out-of-enterprise facility 102mobile client facility 144D-F that has an embedded end-pointcomputer security facility 152, such as by providing URI filtering in personal routers, using a web appliance as a DNS proxy, or the like.Mobile client facilities 144D-F that are components of theenterprise facility 102 but temporarily outside connectivity with theenterprise facility 102 network, may be provided with the same threat protection and policy control as client facilities 144 inside theenterprise facility 102. In addition,mobile client facilities 144B-F may receive the same interactions to and from thethreat management facility 100 as client facilities 144 inside theenterprise facility 102, wheremobile client facilities 144B-F may be considered a virtual extension of theenterprise facility 102, receiving all the same services via their embedded end-pointcomputer security facility 152. - Interactions between the
threat management facility 100 and the components of theenterprise facility 102, includingmobile client facility 144B-F extensions of theenterprise facility 102, may ultimately be connected through theinternet 154.Threat management facility 100 downloads and upgrades to theenterprise facility 102 may be passed from the firewalled networks of thethreat management facility 100 through to the end-pointcomputer security facility 152 equipped components of theenterprise facility 102. In turn the end-pointcomputer security facility 152 components of theenterprise facility 102 may upload policy and access requests back across theinternet 154 and through to thethreat management facility 100. TheInternet 154 however, is also the path through which threats may be transmitted from their source. These network threats may include threats from a plurality of sources, includingwebsites 158,e-mail 160,IM 162,VoIP 164, application software, and the like. These threats may attempt to attack a mobileenterprise client facility 144B-F equipped with an end-pointcomputer security facility 152, but in embodiments, as long as themobile client facility 144B-F is embedded with an end-pointcomputer security facility 152, as described above, threats may have no better success than if themobile client facility 144B-F were inside theenterprise facility 102. - However, if the mobile client facility 144 were to attempt to connect into an unprotected connection point, such as at a
secondary location 108 that is not a part of theenterprise facility 102, the mobile client facility 144 may be required to request network interactions through thethreat management facility 100, where contacting thethreat management facility 100 may be performed prior to any other network action. In embodiments, the client facility's 144 end-pointcomputer security facility 152 may manage actions in unprotected network environments such as when theclient facility 144F is in asecondary location 108 or connecting wirelessly to anon-enterprise facility 102 wireless internet connection, where the end-pointcomputer security facility 152 may dictate what actions are allowed, blocked, modified, or the like. For instance, if the client facility's 144 end-pointcomputer security facility 152 is unable to establish a secured connection to thethreat management facility 100, the end-pointcomputer security facility 152 may inform the user of such, and recommend that the connection not be made. In the instance when the user chooses to connect despite the recommendation, the end-pointcomputer security facility 152 may perform specific actions during or after the unprotected connection is made, including running scans during the connection period, running scans after the connection is terminated, storing interactions for subsequent threat and policy evaluation, contacting thethreat management facility 100 upon first instance of a secured connection for further actions and or scanning,restricting access to network and local resources, or the like. In embodiments, the end-pointcomputer security facility 152 may perform specific actions to remediate possible threat incursions or policy violations during or after the unprotected connection. - The
secondary location 108 may have no end-pointcomputer security facilities 152 as a part of its computer components, such as itsfirewalls 138B,servers 142B,clients 144G, hubs androuters 148C-D, and the like. As a result, the computer components of thesecondary location 108 may be open to threat attacks, and become potential sources of threats, as well as any mobileenterprise facility clients 144B-F that may be connected to the secondary location's 108 network. In this instance, these computer components may now unknowingly spread a threat to other components connected to the network. - Some threats may not come directly from the
Internet 154, such as from non-enterprise facility controlled mobile devices that are physically brought into theenterprise facility 102 and connected to theenterprise facility 102 client facilities 144. The connection may be made from direct connection with the enterprise facility's 102 client facility 144, such as through a USB port, or in physical proximity with the enterprise facility's 102 client facility 144 such that a wireless facility connection can be established, such as through a Bluetooth connection. Thesephysical proximity threats 110 may be another mobile computing device, a portable memory storage device, a mobile communications device, or the like, such as CDs andDVDs 170,memory stick 174,flash drive 174, external hard drive,cell phone 178,PDAs 180, MP3 players, digital cameras, point-to-point devices, digital picture frames, digital pens, navigation devices, appliances, and the like. Aphysical proximity threat 110 may have been previously infiltrated by network threats while connected to an unprotected network connection outside theenterprise facility 102, and when connected to theenterprise facility 102 client facility 144, pose a threat. Because of their mobile nature,physical proximity threats 110 may infiltrate computing resources in any location, such as being physically brought into theenterprise facility 102 site, connected to anenterprise facility 102 client facility 144 while that client facility 144 is mobile, plugged into an unprotected client facility 144 at asecondary location 108, and the like. A mobile device, once connected to an unprotected computer resource, may become aphysical proximity threat 110. In embodiments, the end-pointcomputer security facility 152 may provideenterprise facility 102 computing resources with threat protection againstphysical proximity threats 110, for instance, through scanning the device prior to allowing data transfers, through security validation certificates, through establishing a safe zone within theenterprise facility 102 computing resource to transfer data into for evaluation, and the like. Now that the overall system has been described, we turn towards a set of reputation embodiments relating to the creation and use of hierarchical statistical Internet reputation metrics. It should be understood that the following embodiments may be managed through athreat management facility 100 along with other services, such as those described herein. - Referring to
FIG. 2 , assessing the reputation (“trustworthiness”) ofInternet entities 208 via communication identifiers such as such as a web address, a domain names, an IP addresses, host names, email addresses, IM addresses, telephone numbers, VoIP telephony addresses, and the like, may be a function ofsecurity management 122 within thethreat management facility 100. In embodiments, thesecurity management facility 122 may provide for reputation filtering, which may target or identify sources of known malware. For instance, reputation filtering may include lists of URIs of known sources of malware or known suspicious IP addresses, or domains, say for spam or for botnets, that when detected may invoke an action by thethreat management facility 100. In embodiments, the present invention may provide for a hierarchicalmodeling processing facility 202 to build a hierarchical reputation model of theseentities 208 that allows for the automated clustering of “neighborhoods” of related systems, and thus the reputation assessment even of brand new hosts within a neighborhood. The reputation of such a neighborhood, with an accompanying confidence level, may be derived statistically from measurements of observed behavior of the systems within it. Expressed another way, a hierarchical model may allow an entity's 208 reputation to be partially or wholly inherited from its parent. In embodiments, reputations for theseentities 208 may be stored in areputation database 204. - A hierarchical reputation model may reflect the natural hierarchy of
Internet entities 208, both named (i.e. with a hostname, the logical level) and unnamed (i.e. with just an IP address, the physical level). Namedentities 208 are provided by the Domain Name System, a globally distributed mapping of hostnames to IP addresses. The DNS is arranged hierarchically, and different parts of the tree are maintained by different organizations. For example, Bigcorp, Inc. will be officially charged with responsibility for the “bigcorp.com” domain name and all the hostnames underneath it, e.g. “www.bigcorp.com” and “mail.bigcorp.com”. Because medium to large organizations tend to have a significant number of hosts within their DNS sub-tree, it is a very common practice for administrators to subdivide their part of the DNS tree into manageable units, often clustering hosts with similar functions together in the same neighborhood of the tree. For example, a hypothetical Internet service provider (ISP), “someisp.net” 308, with a large base of both business and consumer customers might organize their part of the DNS tree as shown inFIG. 3 , where its domain name is ‘someisp’, its top-level domain name is ‘net’ 304, and its root zone is 302. In this example, SomeISP's zone of authority begins at thesomeisp node 308 and extends to theleaves corp 310 for the company's corporate network,biz 312 for their business customers, andres 314 for their residential customers. Each major subzone is further divided, with theleaves - Thus it can be seen that the DNS provides a natural clustering of similarly purposed hosts, with clusters delimited by the organization's own naming policy: the host “bob.res.someisp.net” 328 may for instance be treated similarly to the host “alice.res.someisp.net” 330, because they both belong to residential customers. For example, the two hosts may have similar corresponding probability of being part of a spammer's botnet. On the other hand, the hosts “ceo.corp.someisp.net” 318 and “janitor.corp.someisp.net” 320 may be less likely to be part of a botnet, such as by virtue of being behind a professionally administered firewall.
- The present invention leverages the information provided by organizations' DNS sub-trees to cluster hosts for the purpose of determining their reputation. For instance, and referring again to
FIG. 3 , that a new host “chieftechnologist.corp.someisp.net” may likely to behave more similarly to “ceo.corp.someisp.net” 318 than to “alice.res.someisp.net” 330. By augmenting a tree structure such as the one presented inFIG. 3 , with the appropriate metrics as obtained through direct observations of the hosts involved, one may then predict the behavior of hosts one hasn't yet had the opportunity to observe by estimating the reputation of the neighborhood (i.e. a subtree) within which they are located. In embodiments, the resulting structure is sometimes referred to as a “weighted tree”. In embodiments, the same may be achieved for IP addresses using a slightly different structure. - In an example,
FIGS. 4-9 provide a hierarchical building of a named, or logical, tree. Suppose the metrics we are monitoring are ‘total mails sent’ and ‘total spams sent’, in order to calculate a very simple reputation score of total spams sent/total mails sent, i.e. the ratio of spams to total mail sent by a host, or the probability that a subsequent email will also be spam. To begin with,FIG. 4 presents an empty tree, where there are no hosts associated with theroot level 302A, and so no emails or spams accounted. Now suppose we observe the host “mx1.bigcorp.com” send, over a period of time, 50 emails, of which 2 were spam. To update the logical tree, we first break the hostname into its component labels “mx1” 508, “bigcorp” 504, and “com” 502. We work backwards through the labels adding a node for each, accumulating our metrics at every node, including the root. The result is illustrated inFIG. 5 . InFIG. 6 we see the result of observing the host “mx2.bigcorp.com” 602 sending 100 emails, of which 10 were spam. Note that the metrics for “mx1” 508 and “mx2” 602 show the counts for those individual hosts, while theirancestor nodes FIG. 7 illustrates the observation that a host “home-user-9-8-7-6.nyc.someisp.net” 710 send 25 emails, 22 of which were spam. Note again that the metrics for “NYC” 708, “someisp” 704, and “net” 702 show the counts from below in the tree. Next, as shown inFIG. 8 , another New York-based SomeISP customer “home-user-5-6-7-8.nyc.someisp.net” 802 is seen sending 80 emails, of which 70 were spam, where the metrics for “NYC” 708, “someisp” 704, “net” 702, androot 302A show the additional counts from thenew host 802. Finally, as shown inFIG. 9 , we observe SomeISP's mail server “smtp52.someisp.net” 902 send 200 emails, 5 of which were spam. - Continuing with this example, the determination of a reputation (in this instance, the probability that a subsequent email will be spam) of a host already in the tree is straightforward. We break apart and reverse the labels as during an insert, and walk the tree from the root until we find the corresponding leaf node. As shown in
FIG. 10 , to find the reputation of “home-user-9-8-7-6.nyc.someisp.net” 710 we can see the probability of a new email from that host being spam is 22/25=0.88. - The power of this model, however, comes from the ability to estimate a reputation score for a host whose behavior has not previously been observed. In that case we walk as far towards the leaves of the tree as possible then calculate the probability at that point. For example, to find the reputation score of the host “mx3.bigcorp.com” we would walk the tree as far as the
bigcorp node 504, at which point we could make no further progress. Thus we would assign to this host the score at that node, i.e. 12/150=0.08. This score can be considered the aggregate reputation of all nodes underneathbigcorp 504, i.e. mx1 508 andmx2 602. In the case of such a partial match, we are able to provide a statistical measure of confidence in our estimation by calculating the standard error. By considering the nodes belowbigcorp 504 to be a sample population of two in which the mean probability is that of thebigcorp node 504, we can then calculate the variances ofmx1 508 andmx2 602 to obtain the standard error of the measurement. In this way we can require a certain level of confidence in the probability estimate that is a function of the number of nodes beneathbigcorp 504 and the degree of similarity (in terms of behavior) between them. In other words, the more samples we take (i.e., the more descendants that are underneath the last node of our partial match) and the more uniform those samples are, the more confident we can be that our estimate for “mx3.bigcorp.com” is accurate. In this example, of course, we do not have enough samples to be at all confident in our estimate, and so a likely result of this query might be “not enough information”. - The previous example was for the development and utilization of a named, or logical, tree. In embodiments an unnamed, or physical, tree may be developed. The physical tree may be very similar conceptually to the logical tree as described herein, with the only difference being that we must construct it based on the IP addresses of the inserted hosts. We once again start at the
root 302B with the empty tree as shown inFIG. 11 . Now let us add the host 1.2.3.4, which was observed sending 40 emails, 18 of which were spam. To do this we convert the IP address in dotted quad form to binary: - 1.2.3.4=00000001 00000010 00000011 00000100
- We then insert a
node 1202 corresponding to the host, as shown inFIG. 12 . Next we insert the host 15.16.17.18, which sent 50 emails, none of which were spam. We first convert the IP address to binary: - 15.90.152.3=00001111 01011010 10011000 00000011
- Notice that this differs from the previous address at the 5th binary digit from the left, which in the previous was 0 and in the current is 1. We thus add a “splitter”
node 1302 as the parent of the existingleaf 1202 and add thenew leaf 1304 as its second child, as shown inFIG. 13 . Finally we add the host 3.99.58.12, which sent 15 emails, 14 of which were spam: - 3.99.58.12=00000011 01100011 00111010 00001100
- This time the binary address varies from those already present at the 7th digit, resulting in the addition of a new splitter 1402 and the addition of the
new leaf 1404 as its second child, as shown inFIG. 14 . Thus we form a binary search tree given the IP addresses of the hosts we are inserting. - Querying may be performed in the same way as with the logical tree as described herein, by walking from the
root 302B to the leaf (or as far as possible in the case of a partial match) and calculating or estimating the reputation score at that point. The same statistical method as described herein may be used to obtain a confidence interval in the estimated probability. - In embodiments, the present invention uses hierarchies to model parent/child relationships between and within
entities 208, thereby representing theentities 208 in a natural and useful way. This is achieved through the inheritance of reputation from ancestral entities to their descendants. A significant advantage of the present invention may be that reputation can be assigned toentities 208 even if they have never been seen before, provided theentity 208 has a known ancestor somewhere in the reputation tree. As a result the system may not need to be updated as often, and may only degrade slowly in its utility over time if updates do not occur, and thus the data may be updated and published on a less demanding schedule. Finally, this invention may provide a unified view of all relationships affecting the reputability of anentity 208, from the network owner at the highest level to individual hosts, web pages etc. at the lowest level. By using the present invention it may be possible to assign a reliable and statistically justifiable reputation score toInternet entities 208 even if previously unseen, while eliminating the requirement that the model be updated and published to consumers with the utmost urgency. In embodiments, using the present invention may result in more botnet spam blocked than is possible with a simple flat list of bad senders, no matter how rapidly it is updated. - Referring to
FIG. 15 , in embodiments of the present invention improved capabilities are described for predicting the reputation of acommunication identifier 1500, such as a web address, a domain name, an IP address, host name, email address, IM address, telephone number, VoIP telephony address, and the like. In embodiments, the present invention may receive acommunication 1502 from a first communication identifier, parse the first communication identifier into its components, and assign the components to a hierarchical tree structure, where the hierarchical tree structure maintains the hierarchical relationship between the components of the communication identifier. The present invention may monitor and keepcount 1504 of a number of communications from the first communication identifier, wherein the number of communications may be kept for both malicious and/or unwanted communications and non-malicious and/or unwanted communications. Attributes may then be provided 1508 to the number of communications for each appropriate component of the hierarchical tree, and a statistical measure may be calculated as related to the number of communications for each component of the hierarchical tree. The present invention may then receive acommunication 1510 from a second communication identifier, where the second communication identifier may be previously unknown and have a common component with the hierarchical tree. The statistical measure of the common component may then be assigned 1512 to the second communication identifier, and utilizing the statistical measure assigned to the second communication identifier, may provide a prediction of reputation of the second communication identifier. In embodiments, the communication identifier may be in the form of a web address, a domain name, domain name components, an IP address, IP address components, an email address, an IM address, a telephone number, a VoIP telephony address, and the like. In embodiments, the component may be at a root level, a top level, a lower level, and the like. In embodiments, the at least one of malicious and unwanted communication may be spam, from a computer that is part of a botnet, and the like. In embodiments, the statistical measure may relate the number of at least one of malicious and unwanted communications to the number of total communications. In embodiments, the reputation may be related to how much spam the website communicates. - The methods and systems described herein may be deployed in part or in whole through a machine that executes computer software, program codes, and/or instructions on a processor. The present invention may be implemented as a method on the machine, as a system or apparatus as part of or in relation to the machine, or as a computer program product embodied in a computer readable medium executing on one or more of the machines. The processor may be part of a server, client, network infrastructure, mobile computing platform, stationary computing platform, or other computing platform. A processor may be any kind of computational or processing device capable of executing program instructions, codes, binary instructions and the like. The processor may be or include a signal processor, digital processor, embedded processor, microprocessor or any variant such as a co-processor (math co-processor, graphic co-processor, communication co-processor and the like) and the like that may directly or indirectly facilitate execution of program code or program instructions stored thereon. In addition, the processor may enable execution of multiple programs, threads, and codes. The threads may be executed simultaneously to enhance the performance of the processor and to facilitate simultaneous operations of the application. By way of implementation, methods, program codes, program instructions and the like described herein may be implemented in one or more thread. The thread may spawn other threads that may have assigned priorities associated with them; the processor may execute these threads based on priority or any other order based on instructions provided in the program code. The processor may include memory that stores methods, codes, instructions and programs as described herein and elsewhere. The processor may access a storage medium through an interface that may store methods, codes, and instructions as described herein and elsewhere. The storage medium associated with the processor for storing methods, programs, codes, program instructions or other type of instructions capable of being executed by the computing or processing device may include but may not be limited to one or more of a CD-ROM, DVD, memory, hard disk, flash drive, RAM, ROM, cache and the like.
- A processor may include one or more cores that may enhance speed and performance of a multiprocessor. In embodiments, the process may be a dual core processor, quad core processors, other chip-level multiprocessor and the like that combine two or more independent cores (called a die).
- The methods and systems described herein may be deployed in part or in whole through a machine that executes computer software on a server, client, firewall, gateway, hub, router, or other such computer and/or networking hardware. The software program may be associated with a server that may include a file server, print server, domain server, internet server, intranet server and other variants such as secondary server, host server, distributed server and the like. The server may include one or more of memories, processors, computer readable media, storage media, ports (physical and virtual), communication devices, and interfaces capable of accessing other servers, clients, machines, and devices through a wired or a wireless medium, and the like. The methods, programs or codes as described herein and elsewhere may be executed by the server. In addition, other devices required for execution of methods as described in this application may be considered as a part of the infrastructure associated with the server.
- The server may provide an interface to other devices including, without limitation, clients, other servers, printers, database servers, print servers, file servers, communication servers, distributed servers and the like. Additionally, this coupling and/or connection may facilitate remote execution of program across the network. The networking of some or all of these devices may facilitate parallel processing of a program or method at one or more location without deviating from the scope of the invention. In addition, any of the devices attached to the server through an interface may include at least one storage medium capable of storing methods, programs, code and/or instructions. A central repository may provide program instructions to be executed on different devices. In this implementation, the remote repository may act as a storage medium for program code, instructions, and programs.
- The software program may be associated with a client that may include a file client, print client, domain client, internet client, intranet client and other variants such as secondary client, host client, distributed client and the like. The client may include one or more of memories, processors, computer readable media, storage media, ports (physical and virtual), communication devices, and interfaces capable of accessing other clients, servers, machines, and devices through a wired or a wireless medium, and the like. The methods, programs or codes as described herein and elsewhere may be executed by the client. In addition, other devices required for execution of methods as described in this application may be considered as a part of the infrastructure associated with the client.
- The client may provide an interface to other devices including, without limitation, servers, other clients, printers, database servers, print servers, file servers, communication servers, distributed servers and the like. Additionally, this coupling and/or connection may facilitate remote execution of program across the network. The networking of some or all of these devices may facilitate parallel processing of a program or method at one or more location without deviating from the scope of the invention. In addition, any of the devices attached to the client through an interface may include at least one storage medium capable of storing methods, programs, applications, code and/or instructions. A central repository may provide program instructions to be executed on different devices. In this implementation, the remote repository may act as a storage medium for program code, instructions, and programs.
- The methods and systems described herein may be deployed in part or in whole through network infrastructures. The network infrastructure may include elements such as computing devices, servers, routers, hubs, firewalls, clients, personal computers, communication devices, routing devices and other active and passive devices, modules and/or components as known in the art. The computing and/or non-computing device(s) associated with the network infrastructure may include, apart from other components, a storage medium such as flash memory, buffer, stack, RAM, ROM and the like. The processes, methods, program codes, instructions described herein and elsewhere may be executed by one or more of the network infrastructural elements.
- The methods, program codes, and instructions described herein and elsewhere may be implemented on a cellular network having multiple cells. The cellular network may either be frequency division multiple access (FDMA) network or code division multiple access (CDMA) network. The cellular network may include mobile devices, cell sites, base stations, repeaters, antennas, towers, and the like. The cell network may be a GSM, GPRS, 3G, EVDO, mesh, or other networks types.
- The methods, programs codes, and instructions described herein and elsewhere may be implemented on or through mobile devices. The mobile devices may include navigation devices, cell phones, mobile phones, mobile personal digital assistants, laptops, palmtops, netbooks, pagers, electronic books readers, music players and the like. These devices may include, apart from other components, a storage medium such as a flash memory, buffer, RAM, ROM and one or more computing devices. The computing devices associated with mobile devices may be enabled to execute program codes, methods, and instructions stored thereon. Alternatively, the mobile devices may be configured to execute instructions in collaboration with other devices. The mobile devices may communicate with base stations interfaced with servers and configured to execute program codes. The mobile devices may communicate on a peer to peer network, mesh network, or other communications network. The program code may be stored on the storage medium associated with the server and executed by a computing device embedded within the server. The base station may include a computing device and a storage medium. The storage device may store program codes and instructions executed by the computing devices associated with the base station.
- The computer software, program codes, and/or instructions may be stored and/or accessed on machine readable media that may include: computer components, devices, and recording media that retain digital data used for computing for some interval of time; semiconductor storage known as random access memory (RAM); mass storage typically for more permanent storage, such as optical discs, forms of magnetic storage like hard disks, tapes, drums, cards and other types; processor registers, cache memory, volatile memory, non-volatile memory; optical storage such as CD, DVD; removable media such as flash memory (e.g. USB sticks or keys), floppy disks, magnetic tape, paper tape, punch cards, standalone RAM disks, Zip drives, removable mass storage, off-line, and the like; other computer memory such as dynamic memory, static memory, read/write storage, mutable storage, read only, random access, sequential access, location addressable, file addressable, content addressable, network attached storage, storage area network, bar codes, magnetic ink, and the like.
- The methods and systems described herein may transform physical and/or or intangible items from one state to another. The methods and systems described herein may also transform data representing physical and/or intangible items from one state to another.
- The elements described and depicted herein, including in flow charts and block diagrams throughout the figures, imply logical boundaries between the elements. However, according to software or hardware engineering practices, the depicted elements and the functions thereof may be implemented on machines through computer executable media having a processor capable of executing program instructions stored thereon as a monolithic software structure, as standalone software modules, or as modules that employ external routines, code, services, and so forth, or any combination of these, and all such implementations may be within the scope of the present disclosure. Examples of such machines may include, but may not be limited to, personal digital assistants, laptops, personal computers, mobile phones, other handheld computing devices, medical equipment, wired or wireless communication devices, transducers, chips, calculators, satellites, tablet PCs, electronic books, gadgets, electronic devices, devices having artificial intelligence, computing devices, networking equipments, servers, routers and the like. Furthermore, the elements depicted in the flow chart and block diagrams or any other logical component may be implemented on a machine capable of executing program instructions. Thus, while the foregoing drawings and descriptions set forth functional aspects of the disclosed systems, no particular arrangement of software for implementing these functional aspects should be inferred from these descriptions unless explicitly stated or otherwise clear from the context. Similarly, it will be appreciated that the various steps identified and described above may be varied, and that the order of steps may be adapted to particular applications of the techniques disclosed herein. All such variations and modifications are intended to fall within the scope of this disclosure. As such, the depiction and/or description of an order for various steps should not be understood to require a particular order of execution for those steps, unless required by a particular application, or explicitly stated or otherwise clear from the context.
- The methods and/or processes described above, and steps thereof, may be realized in hardware, software or any combination of hardware and software suitable for a particular application. The hardware may include a general purpose computer and/or dedicated computing device or specific computing device or particular aspect or component of a specific computing device. The processes may be realized in one or more microprocessors, microcontrollers, embedded microcontrollers, programmable digital signal processors or other programmable device, along with internal and/or external memory. The processes may also, or instead, be embodied in an application specific integrated circuit, a programmable gate array, programmable array logic, or any other device or combination of devices that may be configured to process electronic signals. It will further be appreciated that one or more of the processes may be realized as a computer executable code capable of being executed on a machine readable medium.
- The computer executable code may be created using a structured programming language such as C, an object oriented programming language such as C++, or any other high-level or low-level programming language (including assembly languages, hardware description languages, and database programming languages and technologies) that may be stored, compiled or interpreted to run on one of the above devices, as well as heterogeneous combinations of processors, processor architectures, or combinations of different hardware and software, or any other machine capable of executing program instructions.
- Thus, in one aspect, each method described above and combinations thereof may be embodied in computer executable code that, when executing on one or more computing devices, performs the steps thereof. In another aspect, the methods may be embodied in systems that perform the steps thereof, and may be distributed across devices in a number of ways, or all of the functionality may be integrated into a dedicated, standalone device or other hardware. In another aspect, the means for performing the steps associated with the processes described above may include any of the hardware and/or software described above. All such permutations and combinations are intended to fall within the scope of the present disclosure.
- While the invention has been disclosed in connection with the preferred embodiments shown and described in detail, various modifications and improvements thereon will become readily apparent to those skilled in the art. Accordingly, the spirit and scope of the present invention is not to be limited by the foregoing examples, but is to be understood in the broadest sense allowable by law.
- All documents referenced herein are hereby incorporated by reference.
Claims (16)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/552,395 US7890627B1 (en) | 2009-09-02 | 2009-09-02 | Hierarchical statistical model of internet reputation |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/552,395 US7890627B1 (en) | 2009-09-02 | 2009-09-02 | Hierarchical statistical model of internet reputation |
Publications (2)
Publication Number | Publication Date |
---|---|
US7890627B1 US7890627B1 (en) | 2011-02-15 |
US20110055923A1 true US20110055923A1 (en) | 2011-03-03 |
Family
ID=43568660
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/552,395 Active 2029-10-14 US7890627B1 (en) | 2009-09-02 | 2009-09-02 | Hierarchical statistical model of internet reputation |
Country Status (1)
Country | Link |
---|---|
US (1) | US7890627B1 (en) |
Cited By (72)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060248580A1 (en) * | 2005-03-28 | 2006-11-02 | Wake Forest University | Methods, systems, and computer program products for network firewall policy optimization |
US20110055916A1 (en) * | 2009-08-28 | 2011-03-03 | Ahn David K | Methods, systems, and computer readable media for adaptive packet filtering |
US20110238864A1 (en) * | 2010-03-24 | 2011-09-29 | Alcatel-Lucent Usa Inc. | System and domain name server for ad-hoc networks |
US20120072384A1 (en) * | 2010-08-05 | 2012-03-22 | Ben Schreiner | Techniques for generating a trustworthiness score in an online environment |
US20120174221A1 (en) * | 2011-01-04 | 2012-07-05 | Seung Chul Han | Apparatus and method for blocking zombie behavior process |
US8381289B1 (en) | 2009-03-31 | 2013-02-19 | Symantec Corporation | Communication-based host reputation system |
US8413251B1 (en) | 2008-09-30 | 2013-04-02 | Symantec Corporation | Using disposable data misuse to determine reputation |
US8499063B1 (en) | 2008-03-31 | 2013-07-30 | Symantec Corporation | Uninstall and system performance based software application reputation |
US8510836B1 (en) * | 2010-07-06 | 2013-08-13 | Symantec Corporation | Lineage-based reputation system |
US8554907B1 (en) * | 2011-02-15 | 2013-10-08 | Trend Micro, Inc. | Reputation prediction of IP addresses |
US8555388B1 (en) | 2011-05-24 | 2013-10-08 | Palo Alto Networks, Inc. | Heuristic botnet detection |
US8595282B2 (en) | 2008-06-30 | 2013-11-26 | Symantec Corporation | Simplified communication of a reputation score for an entity |
US8650647B1 (en) | 2006-12-29 | 2014-02-11 | Symantec Corporation | Web site computer security using client hygiene scores |
US8701190B1 (en) | 2010-02-22 | 2014-04-15 | Symantec Corporation | Inferring file and website reputations by belief propagation leveraging machine reputation |
US8904520B1 (en) | 2009-03-19 | 2014-12-02 | Symantec Corporation | Communication-based reputation system |
US8925082B2 (en) * | 2012-08-22 | 2014-12-30 | International Business Machines Corporation | Cooperative intrusion detection ecosystem for IP reputation-based security |
US8966625B1 (en) * | 2011-05-24 | 2015-02-24 | Palo Alto Networks, Inc. | Identification of malware sites using unknown URL sites and newly registered DNS addresses |
WO2015006175A3 (en) * | 2013-07-10 | 2015-05-28 | Microsoft Corporation | Automatic isolation and detection of outbound spam |
US9104870B1 (en) | 2012-09-28 | 2015-08-11 | Palo Alto Networks, Inc. | Detecting malware |
US9124472B1 (en) | 2012-07-25 | 2015-09-01 | Symantec Corporation | Providing file information to a client responsive to a file download stability prediction |
US20150249589A1 (en) * | 2012-08-29 | 2015-09-03 | NSFOCUS Information Technology Co., Ltd. | Method and apparatus for determining automatic scanning action |
US20150295951A1 (en) * | 2012-12-24 | 2015-10-15 | Tencent Technology (Shenzhen) Company Limited | Method, server, and system for automatically rating reputation of a web site |
US9178888B2 (en) | 2013-06-14 | 2015-11-03 | Go Daddy Operating Company, LLC | Method for domain control validation |
US9215239B1 (en) | 2012-09-28 | 2015-12-15 | Palo Alto Networks, Inc. | Malware detection based on traffic analysis |
US9262638B2 (en) | 2006-12-29 | 2016-02-16 | Symantec Corporation | Hygiene based computer security |
US9317574B1 (en) | 2012-06-11 | 2016-04-19 | Dell Software Inc. | System and method for managing and identifying subject matter experts |
US9349016B1 (en) | 2014-06-06 | 2016-05-24 | Dell Software Inc. | System and method for user-context-based data loss prevention |
US9390240B1 (en) | 2012-06-11 | 2016-07-12 | Dell Software Inc. | System and method for querying data |
US9413722B1 (en) | 2015-04-17 | 2016-08-09 | Centripetal Networks, Inc. | Rule-based network-threat detection |
US9489516B1 (en) | 2014-07-14 | 2016-11-08 | Palo Alto Networks, Inc. | Detection of malware using an instrumented virtual machine environment |
US9501744B1 (en) | 2012-06-11 | 2016-11-22 | Dell Software Inc. | System and method for classifying data |
US9521138B2 (en) | 2013-06-14 | 2016-12-13 | Go Daddy Operating Company, LLC | System for domain control validation |
US9542554B1 (en) | 2014-12-18 | 2017-01-10 | Palo Alto Networks, Inc. | Deduplicating malware |
US9560077B2 (en) | 2012-10-22 | 2017-01-31 | Centripetal Networks, Inc. | Methods and systems for protecting a secured network |
US9560176B2 (en) | 2015-02-10 | 2017-01-31 | Centripetal Networks, Inc. | Correlating packets in communications networks |
US9565213B2 (en) | 2012-10-22 | 2017-02-07 | Centripetal Networks, Inc. | Methods and systems for protecting a secured network |
US9563782B1 (en) | 2015-04-10 | 2017-02-07 | Dell Software Inc. | Systems and methods of secure self-service access to content |
US9569626B1 (en) | 2015-04-10 | 2017-02-14 | Dell Software Inc. | Systems and methods of reporting content-exposure events |
US9578060B1 (en) * | 2012-06-11 | 2017-02-21 | Dell Software Inc. | System and method for data loss prevention across heterogeneous communications platforms |
US9613210B1 (en) | 2013-07-30 | 2017-04-04 | Palo Alto Networks, Inc. | Evaluating malware in a virtual machine using dynamic patching |
US9641555B1 (en) | 2015-04-10 | 2017-05-02 | Dell Software Inc. | Systems and methods of tracking content-exposure events |
US9674148B2 (en) | 2013-01-11 | 2017-06-06 | Centripetal Networks, Inc. | Rule swapping in a packet network |
US9686193B2 (en) | 2013-03-12 | 2017-06-20 | Centripetal Networks, Inc. | Filtering network data transfers |
US9805193B1 (en) | 2014-12-18 | 2017-10-31 | Palo Alto Networks, Inc. | Collecting algorithmically generated domains |
US9842218B1 (en) | 2015-04-10 | 2017-12-12 | Dell Software Inc. | Systems and methods of secure self-service access to content |
US9842220B1 (en) | 2015-04-10 | 2017-12-12 | Dell Software Inc. | Systems and methods of secure self-service access to content |
US9917856B2 (en) | 2015-12-23 | 2018-03-13 | Centripetal Networks, Inc. | Rule-based network-threat detection for encrypted communications |
US9990506B1 (en) | 2015-03-30 | 2018-06-05 | Quest Software Inc. | Systems and methods of securing network-accessible peripheral devices |
US10019575B1 (en) | 2013-07-30 | 2018-07-10 | Palo Alto Networks, Inc. | Evaluating malware in a virtual machine using copy-on-write |
JP2018132823A (en) * | 2017-02-13 | 2018-08-23 | 富士通株式会社 | Policy setting device, policy setting method and policy setting program |
US10142391B1 (en) | 2016-03-25 | 2018-11-27 | Quest Software Inc. | Systems and methods of diagnosing down-layer performance problems via multi-stream performance patternization |
US10157358B1 (en) | 2015-10-05 | 2018-12-18 | Quest Software Inc. | Systems and methods for multi-stream performance patternization and interval-based prediction |
US10218588B1 (en) | 2015-10-05 | 2019-02-26 | Quest Software Inc. | Systems and methods for multi-stream performance patternization and optimization of virtual meetings |
US10237240B2 (en) * | 2016-07-21 | 2019-03-19 | AT&T Global Network Services (U.K.) B.V. | Assessing risk associated with firewall rules |
US10284526B2 (en) | 2017-07-24 | 2019-05-07 | Centripetal Networks, Inc. | Efficient SSL/TLS proxy |
US10326748B1 (en) | 2015-02-25 | 2019-06-18 | Quest Software Inc. | Systems and methods for event-based authentication |
US10333898B1 (en) | 2018-07-09 | 2019-06-25 | Centripetal Networks, Inc. | Methods and systems for efficient network protection |
US10417613B1 (en) | 2015-03-17 | 2019-09-17 | Quest Software Inc. | Systems and methods of patternizing logged user-initiated events for scheduling functions |
US10454866B2 (en) | 2013-07-10 | 2019-10-22 | Microsoft Technology Licensing, Llc | Outbound IP address reputation control and repair |
US10503899B2 (en) | 2017-07-10 | 2019-12-10 | Centripetal Networks, Inc. | Cyberanalysis workflow acceleration |
US10536352B1 (en) | 2015-08-05 | 2020-01-14 | Quest Software Inc. | Systems and methods for tuning cross-platform data collection |
US10650023B2 (en) * | 2018-07-24 | 2020-05-12 | Booz Allen Hamilton, Inc. | Process for establishing trust between multiple autonomous systems for the purposes of command and control |
US10673719B2 (en) | 2016-02-25 | 2020-06-02 | Imperva, Inc. | Techniques for botnet detection and member identification |
US10862909B2 (en) | 2013-03-15 | 2020-12-08 | Centripetal Networks, Inc. | Protecting networks from cyber attacks and overloading |
US10867041B2 (en) | 2013-07-30 | 2020-12-15 | Palo Alto Networks, Inc. | Static and dynamic security analysis of apps for mobile devices |
US10956573B2 (en) | 2018-06-29 | 2021-03-23 | Palo Alto Networks, Inc. | Dynamic analysis techniques for applications |
US11010474B2 (en) | 2018-06-29 | 2021-05-18 | Palo Alto Networks, Inc. | Dynamic analysis techniques for applications |
US11159546B1 (en) | 2021-04-20 | 2021-10-26 | Centripetal Networks, Inc. | Methods and systems for efficient threat context-aware packet filtering for network protection |
US11196765B2 (en) | 2019-09-13 | 2021-12-07 | Palo Alto Networks, Inc. | Simulating user interactions for malware analysis |
US11233777B2 (en) | 2017-07-24 | 2022-01-25 | Centripetal Networks, Inc. | Efficient SSL/TLS proxy |
US11539664B2 (en) | 2020-10-27 | 2022-12-27 | Centripetal Networks, Inc. | Methods and systems for efficient adaptive logging of cyber threat incidents |
US11729144B2 (en) | 2016-01-04 | 2023-08-15 | Centripetal Networks, Llc | Efficient packet capture for cyber threat analysis |
Families Citing this family (44)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR100926804B1 (en) | 2004-04-30 | 2009-11-12 | 리서치 인 모션 리미티드 | System and method for handling data transfers |
US8566928B2 (en) | 2005-10-27 | 2013-10-22 | Georgia Tech Research Corporation | Method and system for detecting and responding to attacking networks |
US10027688B2 (en) * | 2008-08-11 | 2018-07-17 | Damballa, Inc. | Method and system for detecting malicious and/or botnet-related domain names |
US8578497B2 (en) | 2010-01-06 | 2013-11-05 | Damballa, Inc. | Method and system for detecting malware |
US8826438B2 (en) | 2010-01-19 | 2014-09-02 | Damballa, Inc. | Method and system for network-based detecting of malware from behavioral clustering |
US8955131B2 (en) | 2010-01-27 | 2015-02-10 | Mcafee Inc. | Method and system for proactive detection of malicious shared libraries via a remote reputation system |
US8474039B2 (en) | 2010-01-27 | 2013-06-25 | Mcafee, Inc. | System and method for proactive detection and repair of malware memory infection via a remote memory reputation system |
US20110185428A1 (en) * | 2010-01-27 | 2011-07-28 | Mcafee, Inc. | Method and system for protection against unknown malicious activities observed by applications downloaded from pre-classified domains |
US8819826B2 (en) * | 2010-01-27 | 2014-08-26 | Mcafee, Inc. | Method and system for detection of malware that connect to network destinations through cloud scanning and web reputation |
US8910279B2 (en) | 2010-03-10 | 2014-12-09 | Sonicwall, Inc. | Reputation-based threat protection |
WO2011123981A1 (en) * | 2010-04-07 | 2011-10-13 | Google Inc. | Detection of boilerplate content |
US9147071B2 (en) | 2010-07-20 | 2015-09-29 | Mcafee, Inc. | System and method for proactive detection of malware device drivers via kernel forensic behavioral monitoring and a back-end reputation system |
US9516058B2 (en) | 2010-08-10 | 2016-12-06 | Damballa, Inc. | Method and system for determining whether domain names are legitimate or malicious |
US9536089B2 (en) | 2010-09-02 | 2017-01-03 | Mcafee, Inc. | Atomic detection and repair of kernel memory |
US8560616B1 (en) * | 2010-09-27 | 2013-10-15 | Amazon Technologies, Inc. | IP management for outbound E-mails |
US8631489B2 (en) | 2011-02-01 | 2014-01-14 | Damballa, Inc. | Method and system for detecting malicious domain names at an upper DNS hierarchy |
WO2012174601A1 (en) * | 2011-06-21 | 2012-12-27 | Jajoza Connected Solutions Pty Ltd | A system and method for providing safety policies for communications and interaction |
US8726379B1 (en) | 2011-07-15 | 2014-05-13 | Norse Corporation | Systems and methods for dynamic protection from electronic attacks |
US9161226B2 (en) | 2011-10-17 | 2015-10-13 | Blackberry Limited | Associating services to perimeters |
US9497220B2 (en) | 2011-10-17 | 2016-11-15 | Blackberry Limited | Dynamically generating perimeters |
US9613219B2 (en) | 2011-11-10 | 2017-04-04 | Blackberry Limited | Managing cross perimeter access |
US8799227B2 (en) | 2011-11-11 | 2014-08-05 | Blackberry Limited | Presenting metadata from multiple perimeters |
US8549612B2 (en) | 2011-11-28 | 2013-10-01 | Dell Products, Lp | System and method for incorporating quality-of-service and reputation in an intrusion detection and prevention system |
US9369466B2 (en) | 2012-06-21 | 2016-06-14 | Blackberry Limited | Managing use of network resources |
US10547674B2 (en) | 2012-08-27 | 2020-01-28 | Help/Systems, Llc | Methods and systems for network flow analysis |
US9894088B2 (en) | 2012-08-31 | 2018-02-13 | Damballa, Inc. | Data mining to identify malicious activity |
US9166994B2 (en) | 2012-08-31 | 2015-10-20 | Damballa, Inc. | Automation discovery to identify malicious activity |
US9680861B2 (en) | 2012-08-31 | 2017-06-13 | Damballa, Inc. | Historical analysis to identify malicious activity |
US10084806B2 (en) | 2012-08-31 | 2018-09-25 | Damballa, Inc. | Traffic simulation to identify malicious activity |
US20140280698A1 (en) * | 2013-03-13 | 2014-09-18 | Qnx Software Systems Limited | Processing a Link on a Device |
US9571511B2 (en) | 2013-06-14 | 2017-02-14 | Damballa, Inc. | Systems and methods for traffic classification |
US9306895B1 (en) | 2013-09-06 | 2016-04-05 | Amazon Technologies, Inc. | Prediction of message deliverability events |
US10108918B2 (en) | 2013-09-19 | 2018-10-23 | Acxiom Corporation | Method and system for inferring risk of data leakage from third-party tags |
US10104109B2 (en) * | 2013-09-30 | 2018-10-16 | Entit Software Llc | Threat scores for a hierarchy of entities |
US9083730B2 (en) | 2013-12-06 | 2015-07-14 | At&T Intellectual Property I., L.P. | Methods and apparatus to identify an internet protocol address blacklist boundary |
US9264418B1 (en) * | 2014-02-20 | 2016-02-16 | Amazon Technologies, Inc. | Client-side spam detection and prevention |
US9942250B2 (en) | 2014-08-06 | 2018-04-10 | Norse Networks, Inc. | Network appliance for dynamic protection from risky network activities |
EP3215943B1 (en) * | 2014-11-03 | 2021-04-21 | Vectra AI, Inc. | A system for implementing threat detection using threat and risk assessment of asset-actor interactions |
US9124622B1 (en) * | 2014-11-07 | 2015-09-01 | Area 1 Security, Inc. | Detecting computer security threats in electronic documents based on structure |
USD814494S1 (en) | 2015-03-02 | 2018-04-03 | Norse Networks, Inc. | Computer display panel with an icon image of a live electronic threat intelligence visualization interface |
US9930065B2 (en) | 2015-03-25 | 2018-03-27 | University Of Georgia Research Foundation, Inc. | Measuring, categorizing, and/or mitigating malware distribution paths |
USD810775S1 (en) | 2015-04-21 | 2018-02-20 | Norse Networks, Inc. | Computer display panel with a graphical live electronic threat intelligence visualization interface |
US9923914B2 (en) * | 2015-06-30 | 2018-03-20 | Norse Networks, Inc. | Systems and platforms for intelligently monitoring risky network activities |
EP3293938B1 (en) | 2016-09-12 | 2021-06-30 | Vectra AI, Inc. | Method and system for detecting suspicious administrative activity |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090265198A1 (en) * | 2008-04-22 | 2009-10-22 | Plaxo, Inc. | Reputation Evalution Using a contact Information Database |
US20100306249A1 (en) * | 2009-05-27 | 2010-12-02 | James Hill | Social network systems and methods |
-
2009
- 2009-09-02 US US12/552,395 patent/US7890627B1/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090265198A1 (en) * | 2008-04-22 | 2009-10-22 | Plaxo, Inc. | Reputation Evalution Using a contact Information Database |
US20100306249A1 (en) * | 2009-05-27 | 2010-12-02 | James Hill | Social network systems and methods |
Cited By (150)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060248580A1 (en) * | 2005-03-28 | 2006-11-02 | Wake Forest University | Methods, systems, and computer program products for network firewall policy optimization |
US8042167B2 (en) * | 2005-03-28 | 2011-10-18 | Wake Forest University | Methods, systems, and computer program products for network firewall policy optimization |
US8650647B1 (en) | 2006-12-29 | 2014-02-11 | Symantec Corporation | Web site computer security using client hygiene scores |
US9262638B2 (en) | 2006-12-29 | 2016-02-16 | Symantec Corporation | Hygiene based computer security |
US8499063B1 (en) | 2008-03-31 | 2013-07-30 | Symantec Corporation | Uninstall and system performance based software application reputation |
US8595282B2 (en) | 2008-06-30 | 2013-11-26 | Symantec Corporation | Simplified communication of a reputation score for an entity |
US8413251B1 (en) | 2008-09-30 | 2013-04-02 | Symantec Corporation | Using disposable data misuse to determine reputation |
US9246931B1 (en) | 2009-03-19 | 2016-01-26 | Symantec Corporation | Communication-based reputation system |
US8904520B1 (en) | 2009-03-19 | 2014-12-02 | Symantec Corporation | Communication-based reputation system |
US8381289B1 (en) | 2009-03-31 | 2013-02-19 | Symantec Corporation | Communication-based host reputation system |
US8495725B2 (en) | 2009-08-28 | 2013-07-23 | Great Wall Systems | Methods, systems, and computer readable media for adaptive packet filtering |
US20110055916A1 (en) * | 2009-08-28 | 2011-03-03 | Ahn David K | Methods, systems, and computer readable media for adaptive packet filtering |
US8701190B1 (en) | 2010-02-22 | 2014-04-15 | Symantec Corporation | Inferring file and website reputations by belief propagation leveraging machine reputation |
US20110238864A1 (en) * | 2010-03-24 | 2011-09-29 | Alcatel-Lucent Usa Inc. | System and domain name server for ad-hoc networks |
US8621086B2 (en) * | 2010-03-24 | 2013-12-31 | Alcatel Lucent | System and domain name server for ad-hoc networks |
US8510836B1 (en) * | 2010-07-06 | 2013-08-13 | Symantec Corporation | Lineage-based reputation system |
US20120072384A1 (en) * | 2010-08-05 | 2012-03-22 | Ben Schreiner | Techniques for generating a trustworthiness score in an online environment |
US8781984B2 (en) * | 2010-08-05 | 2014-07-15 | Ben Schreiner | Techniques for generating a trustworthiness score in an online environment |
US20120174221A1 (en) * | 2011-01-04 | 2012-07-05 | Seung Chul Han | Apparatus and method for blocking zombie behavior process |
US9060016B2 (en) * | 2011-01-04 | 2015-06-16 | Npcore Inc. | Apparatus and method for blocking zombie behavior process |
US8554907B1 (en) * | 2011-02-15 | 2013-10-08 | Trend Micro, Inc. | Reputation prediction of IP addresses |
US8555388B1 (en) | 2011-05-24 | 2013-10-08 | Palo Alto Networks, Inc. | Heuristic botnet detection |
US8966625B1 (en) * | 2011-05-24 | 2015-02-24 | Palo Alto Networks, Inc. | Identification of malware sites using unknown URL sites and newly registered DNS addresses |
US9779260B1 (en) | 2012-06-11 | 2017-10-03 | Dell Software Inc. | Aggregation and classification of secure data |
US9501744B1 (en) | 2012-06-11 | 2016-11-22 | Dell Software Inc. | System and method for classifying data |
US10146954B1 (en) | 2012-06-11 | 2018-12-04 | Quest Software Inc. | System and method for data aggregation and analysis |
US9390240B1 (en) | 2012-06-11 | 2016-07-12 | Dell Software Inc. | System and method for querying data |
US9578060B1 (en) * | 2012-06-11 | 2017-02-21 | Dell Software Inc. | System and method for data loss prevention across heterogeneous communications platforms |
US9317574B1 (en) | 2012-06-11 | 2016-04-19 | Dell Software Inc. | System and method for managing and identifying subject matter experts |
US9124472B1 (en) | 2012-07-25 | 2015-09-01 | Symantec Corporation | Providing file information to a client responsive to a file download stability prediction |
US8925082B2 (en) * | 2012-08-22 | 2014-12-30 | International Business Machines Corporation | Cooperative intrusion detection ecosystem for IP reputation-based security |
US20150249589A1 (en) * | 2012-08-29 | 2015-09-03 | NSFOCUS Information Technology Co., Ltd. | Method and apparatus for determining automatic scanning action |
US10057155B2 (en) * | 2012-08-29 | 2018-08-21 | NSFOCUS Information Technology Co., Ltd. | Method and apparatus for determining automatic scanning action |
US9215239B1 (en) | 2012-09-28 | 2015-12-15 | Palo Alto Networks, Inc. | Malware detection based on traffic analysis |
US9104870B1 (en) | 2012-09-28 | 2015-08-11 | Palo Alto Networks, Inc. | Detecting malware |
US10785266B2 (en) | 2012-10-22 | 2020-09-22 | Centripetal Networks, Inc. | Methods and systems for protecting a secured network |
US10091246B2 (en) | 2012-10-22 | 2018-10-02 | Centripetal Networks, Inc. | Methods and systems for protecting a secured network |
US11012474B2 (en) | 2012-10-22 | 2021-05-18 | Centripetal Networks, Inc. | Methods and systems for protecting a secured network |
US9560077B2 (en) | 2012-10-22 | 2017-01-31 | Centripetal Networks, Inc. | Methods and systems for protecting a secured network |
US10567437B2 (en) | 2012-10-22 | 2020-02-18 | Centripetal Networks, Inc. | Methods and systems for protecting a secured network |
US9565213B2 (en) | 2012-10-22 | 2017-02-07 | Centripetal Networks, Inc. | Methods and systems for protecting a secured network |
US9894094B2 (en) * | 2012-12-24 | 2018-02-13 | Tencent Technology (Shenzhen) Company Limited | Method, server, and system for automatically rating reputation of a web site |
US20150295951A1 (en) * | 2012-12-24 | 2015-10-15 | Tencent Technology (Shenzhen) Company Limited | Method, server, and system for automatically rating reputation of a web site |
US11502996B2 (en) | 2013-01-11 | 2022-11-15 | Centripetal Networks, Inc. | Rule swapping in a packet network |
US10284522B2 (en) | 2013-01-11 | 2019-05-07 | Centripetal Networks, Inc. | Rule swapping for network protection |
US11539665B2 (en) | 2013-01-11 | 2022-12-27 | Centripetal Networks, Inc. | Rule swapping in a packet network |
US10511572B2 (en) | 2013-01-11 | 2019-12-17 | Centripetal Networks, Inc. | Rule swapping in a packet network |
US10681009B2 (en) | 2013-01-11 | 2020-06-09 | Centripetal Networks, Inc. | Rule swapping in a packet network |
US9674148B2 (en) | 2013-01-11 | 2017-06-06 | Centripetal Networks, Inc. | Rule swapping in a packet network |
US10541972B2 (en) | 2013-01-11 | 2020-01-21 | Centripetal Networks, Inc. | Rule swapping in a packet network |
US11012415B2 (en) | 2013-03-12 | 2021-05-18 | Centripetal Networks, Inc. | Filtering network data transfers |
US11418487B2 (en) | 2013-03-12 | 2022-08-16 | Centripetal Networks, Inc. | Filtering network data transfers |
US10505898B2 (en) | 2013-03-12 | 2019-12-10 | Centripetal Networks, Inc. | Filtering network data transfers |
US10567343B2 (en) | 2013-03-12 | 2020-02-18 | Centripetal Networks, Inc. | Filtering network data transfers |
US10735380B2 (en) | 2013-03-12 | 2020-08-04 | Centripetal Networks, Inc. | Filtering network data transfers |
US9686193B2 (en) | 2013-03-12 | 2017-06-20 | Centripetal Networks, Inc. | Filtering network data transfers |
US11496497B2 (en) | 2013-03-15 | 2022-11-08 | Centripetal Networks, Inc. | Protecting networks from cyber attacks and overloading |
US10862909B2 (en) | 2013-03-15 | 2020-12-08 | Centripetal Networks, Inc. | Protecting networks from cyber attacks and overloading |
US9521138B2 (en) | 2013-06-14 | 2016-12-13 | Go Daddy Operating Company, LLC | System for domain control validation |
US9178888B2 (en) | 2013-06-14 | 2015-11-03 | Go Daddy Operating Company, LLC | Method for domain control validation |
WO2015006175A3 (en) * | 2013-07-10 | 2015-05-28 | Microsoft Corporation | Automatic isolation and detection of outbound spam |
US10454866B2 (en) | 2013-07-10 | 2019-10-22 | Microsoft Technology Licensing, Llc | Outbound IP address reputation control and repair |
US9455989B2 (en) | 2013-07-10 | 2016-09-27 | Microsoft Technology Licensing, Llc | Automatic isolation and detection of outbound spam |
US9749271B2 (en) | 2013-07-10 | 2017-08-29 | Microsoft Technology Licensing, Llc | Automatic isolation and detection of outbound spam |
US10019575B1 (en) | 2013-07-30 | 2018-07-10 | Palo Alto Networks, Inc. | Evaluating malware in a virtual machine using copy-on-write |
US10678918B1 (en) | 2013-07-30 | 2020-06-09 | Palo Alto Networks, Inc. | Evaluating malware in a virtual machine using copy-on-write |
US10867041B2 (en) | 2013-07-30 | 2020-12-15 | Palo Alto Networks, Inc. | Static and dynamic security analysis of apps for mobile devices |
US9804869B1 (en) | 2013-07-30 | 2017-10-31 | Palo Alto Networks, Inc. | Evaluating malware in a virtual machine using dynamic patching |
US9613210B1 (en) | 2013-07-30 | 2017-04-04 | Palo Alto Networks, Inc. | Evaluating malware in a virtual machine using dynamic patching |
US10142372B2 (en) | 2014-04-16 | 2018-11-27 | Centripetal Networks, Inc. | Methods and systems for protecting a secured network |
US10749906B2 (en) | 2014-04-16 | 2020-08-18 | Centripetal Networks, Inc. | Methods and systems for protecting a secured network |
US10944792B2 (en) | 2014-04-16 | 2021-03-09 | Centripetal Networks, Inc. | Methods and systems for protecting a secured network |
US10951660B2 (en) | 2014-04-16 | 2021-03-16 | Centripetal Networks, Inc. | Methods and systems for protecting a secured network |
US11477237B2 (en) | 2014-04-16 | 2022-10-18 | Centripetal Networks, Inc. | Methods and systems for protecting a secured network |
US9349016B1 (en) | 2014-06-06 | 2016-05-24 | Dell Software Inc. | System and method for user-context-based data loss prevention |
US9489516B1 (en) | 2014-07-14 | 2016-11-08 | Palo Alto Networks, Inc. | Detection of malware using an instrumented virtual machine environment |
US10515210B2 (en) | 2014-07-14 | 2019-12-24 | Palo Alto Networks, Inc. | Detection of malware using an instrumented virtual machine environment |
US11036859B2 (en) | 2014-12-18 | 2021-06-15 | Palo Alto Networks, Inc. | Collecting algorithmically generated domains |
US9805193B1 (en) | 2014-12-18 | 2017-10-31 | Palo Alto Networks, Inc. | Collecting algorithmically generated domains |
US9542554B1 (en) | 2014-12-18 | 2017-01-10 | Palo Alto Networks, Inc. | Deduplicating malware |
US10846404B1 (en) | 2014-12-18 | 2020-11-24 | Palo Alto Networks, Inc. | Collecting algorithmically generated domains |
US10659573B2 (en) | 2015-02-10 | 2020-05-19 | Centripetal Networks, Inc. | Correlating packets in communications networks |
US10530903B2 (en) | 2015-02-10 | 2020-01-07 | Centripetal Networks, Inc. | Correlating packets in communications networks |
US11683401B2 (en) | 2015-02-10 | 2023-06-20 | Centripetal Networks, Llc | Correlating packets in communications networks |
US9560176B2 (en) | 2015-02-10 | 2017-01-31 | Centripetal Networks, Inc. | Correlating packets in communications networks |
US11956338B2 (en) | 2015-02-10 | 2024-04-09 | Centripetal Networks, Llc | Correlating packets in communications networks |
US10931797B2 (en) | 2015-02-10 | 2021-02-23 | Centripetal Networks, Inc. | Correlating packets in communications networks |
US10326748B1 (en) | 2015-02-25 | 2019-06-18 | Quest Software Inc. | Systems and methods for event-based authentication |
US10417613B1 (en) | 2015-03-17 | 2019-09-17 | Quest Software Inc. | Systems and methods of patternizing logged user-initiated events for scheduling functions |
US9990506B1 (en) | 2015-03-30 | 2018-06-05 | Quest Software Inc. | Systems and methods of securing network-accessible peripheral devices |
US9842218B1 (en) | 2015-04-10 | 2017-12-12 | Dell Software Inc. | Systems and methods of secure self-service access to content |
US9569626B1 (en) | 2015-04-10 | 2017-02-14 | Dell Software Inc. | Systems and methods of reporting content-exposure events |
US9842220B1 (en) | 2015-04-10 | 2017-12-12 | Dell Software Inc. | Systems and methods of secure self-service access to content |
US10140466B1 (en) | 2015-04-10 | 2018-11-27 | Quest Software Inc. | Systems and methods of secure self-service access to content |
US9563782B1 (en) | 2015-04-10 | 2017-02-07 | Dell Software Inc. | Systems and methods of secure self-service access to content |
US9641555B1 (en) | 2015-04-10 | 2017-05-02 | Dell Software Inc. | Systems and methods of tracking content-exposure events |
US11012459B2 (en) | 2015-04-17 | 2021-05-18 | Centripetal Networks, Inc. | Rule-based network-threat detection |
US10567413B2 (en) | 2015-04-17 | 2020-02-18 | Centripetal Networks, Inc. | Rule-based network-threat detection |
US10757126B2 (en) | 2015-04-17 | 2020-08-25 | Centripetal Networks, Inc. | Rule-based network-threat detection |
US9413722B1 (en) | 2015-04-17 | 2016-08-09 | Centripetal Networks, Inc. | Rule-based network-threat detection |
US11792220B2 (en) | 2015-04-17 | 2023-10-17 | Centripetal Networks, Llc | Rule-based network-threat detection |
US10193917B2 (en) | 2015-04-17 | 2019-01-29 | Centripetal Networks, Inc. | Rule-based network-threat detection |
US11516241B2 (en) | 2015-04-17 | 2022-11-29 | Centripetal Networks, Inc. | Rule-based network-threat detection |
US11700273B2 (en) | 2015-04-17 | 2023-07-11 | Centripetal Networks, Llc | Rule-based network-threat detection |
US10609062B1 (en) | 2015-04-17 | 2020-03-31 | Centripetal Networks, Inc. | Rule-based network-threat detection |
US9866576B2 (en) | 2015-04-17 | 2018-01-09 | Centripetal Networks, Inc. | Rule-based network-threat detection |
US10542028B2 (en) * | 2015-04-17 | 2020-01-21 | Centripetal Networks, Inc. | Rule-based network-threat detection |
US11496500B2 (en) | 2015-04-17 | 2022-11-08 | Centripetal Networks, Inc. | Rule-based network-threat detection |
US10536352B1 (en) | 2015-08-05 | 2020-01-14 | Quest Software Inc. | Systems and methods for tuning cross-platform data collection |
US10218588B1 (en) | 2015-10-05 | 2019-02-26 | Quest Software Inc. | Systems and methods for multi-stream performance patternization and optimization of virtual meetings |
US10157358B1 (en) | 2015-10-05 | 2018-12-18 | Quest Software Inc. | Systems and methods for multi-stream performance patternization and interval-based prediction |
US11811810B2 (en) | 2015-12-23 | 2023-11-07 | Centripetal Networks, Llc | Rule-based network threat detection for encrypted communications |
US11824879B2 (en) | 2015-12-23 | 2023-11-21 | Centripetal Networks, Llc | Rule-based network-threat detection for encrypted communications |
US11811809B2 (en) | 2015-12-23 | 2023-11-07 | Centripetal Networks, Llc | Rule-based network-threat detection for encrypted communications |
US11811808B2 (en) | 2015-12-23 | 2023-11-07 | Centripetal Networks, Llc | Rule-based network-threat detection for encrypted communications |
US9917856B2 (en) | 2015-12-23 | 2018-03-13 | Centripetal Networks, Inc. | Rule-based network-threat detection for encrypted communications |
US11563758B2 (en) | 2015-12-23 | 2023-01-24 | Centripetal Networks, Inc. | Rule-based network-threat detection for encrypted communications |
US11477224B2 (en) | 2015-12-23 | 2022-10-18 | Centripetal Networks, Inc. | Rule-based network-threat detection for encrypted communications |
US11729144B2 (en) | 2016-01-04 | 2023-08-15 | Centripetal Networks, Llc | Efficient packet capture for cyber threat analysis |
US10673719B2 (en) | 2016-02-25 | 2020-06-02 | Imperva, Inc. | Techniques for botnet detection and member identification |
US10911472B2 (en) * | 2016-02-25 | 2021-02-02 | Imperva, Inc. | Techniques for targeted botnet protection |
US10142391B1 (en) | 2016-03-25 | 2018-11-27 | Quest Software Inc. | Systems and methods of diagnosing down-layer performance problems via multi-stream performance patternization |
US10728217B2 (en) | 2016-07-21 | 2020-07-28 | AT&T Global Network Services (U.K.) B.V. | Assessing risk associated with firewall rules |
US10237240B2 (en) * | 2016-07-21 | 2019-03-19 | AT&T Global Network Services (U.K.) B.V. | Assessing risk associated with firewall rules |
JP2018132823A (en) * | 2017-02-13 | 2018-08-23 | 富士通株式会社 | Policy setting device, policy setting method and policy setting program |
US11574047B2 (en) | 2017-07-10 | 2023-02-07 | Centripetal Networks, Inc. | Cyberanalysis workflow acceleration |
US11797671B2 (en) | 2017-07-10 | 2023-10-24 | Centripetal Networks, Llc | Cyberanalysis workflow acceleration |
US10503899B2 (en) | 2017-07-10 | 2019-12-10 | Centripetal Networks, Inc. | Cyberanalysis workflow acceleration |
US10284526B2 (en) | 2017-07-24 | 2019-05-07 | Centripetal Networks, Inc. | Efficient SSL/TLS proxy |
US11233777B2 (en) | 2017-07-24 | 2022-01-25 | Centripetal Networks, Inc. | Efficient SSL/TLS proxy |
US11620383B2 (en) | 2018-06-29 | 2023-04-04 | Palo Alto Networks, Inc. | Dynamic analysis techniques for applications |
US10956573B2 (en) | 2018-06-29 | 2021-03-23 | Palo Alto Networks, Inc. | Dynamic analysis techniques for applications |
US11604878B2 (en) | 2018-06-29 | 2023-03-14 | Palo Alto Networks, Inc. | Dynamic analysis techniques for applications |
US11960605B2 (en) | 2018-06-29 | 2024-04-16 | Palo Alto Networks, Inc. | Dynamic analysis techniques for applications |
US11010474B2 (en) | 2018-06-29 | 2021-05-18 | Palo Alto Networks, Inc. | Dynamic analysis techniques for applications |
US10333898B1 (en) | 2018-07-09 | 2019-06-25 | Centripetal Networks, Inc. | Methods and systems for efficient network protection |
US11290424B2 (en) | 2018-07-09 | 2022-03-29 | Centripetal Networks, Inc. | Methods and systems for efficient network protection |
US10650023B2 (en) * | 2018-07-24 | 2020-05-12 | Booz Allen Hamilton, Inc. | Process for establishing trust between multiple autonomous systems for the purposes of command and control |
US11392615B2 (en) * | 2018-07-24 | 2022-07-19 | Booz Allen Hamilton, Inc. | Process for establishing trust between multiple autonomous systems for the purposes of command and control |
US11706251B2 (en) | 2019-09-13 | 2023-07-18 | Palo Alto Networks, Inc. | Simulating user interactions for malware analysis |
US11196765B2 (en) | 2019-09-13 | 2021-12-07 | Palo Alto Networks, Inc. | Simulating user interactions for malware analysis |
US11736440B2 (en) | 2020-10-27 | 2023-08-22 | Centripetal Networks, Llc | Methods and systems for efficient adaptive logging of cyber threat incidents |
US11539664B2 (en) | 2020-10-27 | 2022-12-27 | Centripetal Networks, Inc. | Methods and systems for efficient adaptive logging of cyber threat incidents |
US11159546B1 (en) | 2021-04-20 | 2021-10-26 | Centripetal Networks, Inc. | Methods and systems for efficient threat context-aware packet filtering for network protection |
US11444963B1 (en) | 2021-04-20 | 2022-09-13 | Centripetal Networks, Inc. | Efficient threat context-aware packet filtering for network protection |
US11316876B1 (en) | 2021-04-20 | 2022-04-26 | Centripetal Networks, Inc. | Efficient threat context-aware packet filtering for network protection |
US11552970B2 (en) | 2021-04-20 | 2023-01-10 | Centripetal Networks, Inc. | Efficient threat context-aware packet filtering for network protection |
US11824875B2 (en) | 2021-04-20 | 2023-11-21 | Centripetal Networks, Llc | Efficient threat context-aware packet filtering for network protection |
US11349854B1 (en) | 2021-04-20 | 2022-05-31 | Centripetal Networks, Inc. | Efficient threat context-aware packet filtering for network protection |
US11438351B1 (en) | 2021-04-20 | 2022-09-06 | Centripetal Networks, Inc. | Efficient threat context-aware packet filtering for network protection |
Also Published As
Publication number | Publication date |
---|---|
US7890627B1 (en) | 2011-02-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7890627B1 (en) | Hierarchical statistical model of internet reputation | |
US11763019B2 (en) | Protecting sensitive information from a secure data store | |
US11244049B2 (en) | Use of an application controller to monitor and control software file and application environments | |
US8479267B2 (en) | System and method for identifying unauthorized endpoints | |
US9104864B2 (en) | Threat detection through the accumulated detection of threat characteristics | |
US8266687B2 (en) | Discovery of the use of anonymizing proxies by analysis of HTTP cookies | |
US9210182B2 (en) | Behavioral-based host intrusion prevention system | |
US8392972B2 (en) | Protected access control method for shared computer resources | |
US9015789B2 (en) | Computer security lock down methods | |
US8392379B2 (en) | Method and system for preemptive scanning of computer files | |
US8407804B2 (en) | System and method of whitelisting parent virtual images | |
US8090852B2 (en) | Managing use of proxies to access restricted network locations | |
US8732791B2 (en) | Multi-part internal-external process system for providing virtualization security protection | |
US8832828B2 (en) | Dynamic scanning based on compliance metadata | |
US20100251369A1 (en) | Method and system for preventing data leakage from a computer facilty | |
US20090241192A1 (en) | Virtual machine configuration sharing between host and virtual machines and between virtual machines | |
US20100212010A1 (en) | Systems and methods that detect sensitive data leakages from applications | |
US20110078497A1 (en) | Automated recovery from a security event | |
US20110239267A1 (en) | Password complexity policy for externally controlled systems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SOPHOS PLC, UNITED KINGDOM Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:THOMAS, ROSS G.;REEL/FRAME:023182/0949 Effective date: 20090901 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: ROYAL BANK OF CANADA EUROPE LIMITED, AS COLLATERAL Free format text: SECURITY AGREEMENT;ASSIGNOR:SOPHOS LIMITED F/K/A SOPHOS PLC;REEL/FRAME:026717/0424 Effective date: 20110805 |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT, NE Free format text: SECURITY INTEREST;ASSIGNOR:RBC EUROPE LIMITED, AS EXISTING ADMINISTRATION AGENT AND COLLATERAL AGENT;REEL/FRAME:028198/0285 Effective date: 20120510 |
|
AS | Assignment |
Owner name: SOPHOS LIMITED, UNITED KINGDOM Free format text: CHANGE OF NAME;ASSIGNOR:SOPHOS PLC;REEL/FRAME:030194/0299 Effective date: 20101011 |
|
AS | Assignment |
Owner name: DEUTSCHE BANK AG NEW YORK BRANCH, AS COLLATERAL AG Free format text: ASSIGNMENT OF SECURITY INTEREST;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:032152/0883 Effective date: 20140131 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552) Year of fee payment: 8 |
|
AS | Assignment |
Owner name: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT, NEW YORK Free format text: PATENT SECURITY AGREEMENT FIRST LIEN;ASSIGNOR:SOPHOS LIMITED;REEL/FRAME:053124/0350 Effective date: 20200703 Owner name: OWL ROCK CAPITAL CORPORATION, AS COLLATERAL AGENT, NEW YORK Free format text: PATENT SECURITY AGREEMENT SECOND LIEN;ASSIGNOR:SOPHOS LIMITED;REEL/FRAME:053476/0681 Effective date: 20200703 |
|
AS | Assignment |
Owner name: SOPHOS LIMITED, UNITED KINGDOM Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK AG NEW YORK BRANCH;REEL/FRAME:053334/0220 Effective date: 20200727 |
|
AS | Assignment |
Owner name: SOPHOS LIMITED, UNITED KINGDOM Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT R/F 053476/0681;ASSIGNOR:OWL ROCK CAPITAL CORPORATION, AS COLLATERAL AGENT;REEL/FRAME:056469/0815 Effective date: 20210308 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |