System and method for generating risk scores based on actual loss events

By generating risk scores for attack strategies and assets based on data sets based on actual loss events, the risk score problem of network security incidents is solved, threat identification and response efficiency is improved, resource allocation is optimized, and security management is achieved.

CN119032368APending Publication Date: 2024-11-26CISCO TECHNOLOGY INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380030903.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-07-07
Filing Date
2023-03-28
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

The existing technology is difficult to effectively determine the risk score of network security incidents, which makes it difficult for security operation analysts to quickly identify high-risk threats when facing a large number of events, affecting the efficiency of incident response.

Method used

By determining risk scores for attack strategies based on data sets of actual loss events, and generating asset risk scores based on asset priorities, using real-world data to prioritize events, providing a data-driven risk management method.

Benefits of technology

Improves visibility and contextual understanding of threats, helps security teams quickly identify and respond to high-risk events, reduce financial losses, and optimize resource allocation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119032368A_ABST
    Figure CN119032368A_ABST
Patent Text Reader

Abstract

In one embodiment, a method includes determining an attack policy risk score for one or more attack policies based on a dataset of actual loss events, and determining an event risk score for an event based on the one or more attack policy risk scores. The method also includes determining a priority value for the asset. The asset is associated with an event. The method further includes generating an asset risk score for the asset based on the priority value of the asset and the event risk score.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Related Applications

[0002] This application claims priority to U.S. Provisional Application No. 63 / 326,388, filed on April 1, 2022, which is hereby incorporated by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to generating risk scores and, more particularly, to systems and methods for generating risk scores based on actual loss events. Background Art

[0004] Cybersecurity is the practice of protecting systems, networks and / or programs from digital attacks. These cyberattacks are often aimed at accessing, altering and / or destroying sensitive information, extorting money from users and / or disrupting normal business processes. In order to effectively implement cybersecurity measures, security operations analysts need to determine whether the incidents are malicious and whether they need to be further investigated. However, this proves to be challenging due to the large number of incidents. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 An example system for generating risk scores based on actual loss events is illustrated;

[0006] Figure 2 illustrates an example method for generating a risk score based on actual loss events; and

[0007] Figure 3 An example computer system is illustrated with which the systems and methods described herein may be used. DETAILED DESCRIPTION

[0008] Overview

[0009] Various aspects of the invention are recited in the independent claims and preferred features are recited in the dependent claims. Features of one aspect may be applied individually to each aspect or in combination with other aspects.

[0010] According to one embodiment, a network component includes one or more processors and one or more computer-readable non-transitory storage media coupled to the one or more processors, the media including instructions that, when executed by the one or more processors, cause the network component to perform operations. The operations include determining attack strategy risk scores for one or more attack strategies based on a data set of actual loss events, and determining event risk scores for events based on the one or more attack strategy risk scores. The operations also include determining a priority value for an asset associated with the event. The operations also include generating an asset risk score for the asset based on the priority value of the asset and the event risk score.

[0011] In some embodiments, the data set of actual loss events includes breach data and assurance data. In some embodiments, the event risk score is associated with the probability that the event will result in a financial loss to the enterprise. In some embodiments, the event risk score is associated with one of: a highest attack strategy risk score for one or more attack strategies or an average attack strategy risk score for one or more attack strategies. In some embodiments, the event risk score is one of a plurality of event risk scores associated with an asset.

[0012] In some embodiments, the attack strategy risk score for each of the one or more attack strategies is a value in the range of 1 to 100. In some embodiments, the event risk score for an event is a value in the range of 1 to 100. In some embodiments, the priority value of an asset is a value in the range of 1 to 10. In some embodiments, the asset risk score is a value in the range of 1 to 1000. An asset risk score for an asset may be generated based on the priority value of the asset and the plurality of event risk scores. For example, generating an asset risk score for an asset may include multiplying the priority value of the asset by one or more event risk scores associated with the asset.

[0013] According to another embodiment, a method includes determining an attack strategy risk score for one or more attack strategies based on a data set of actual loss events, and determining an event risk score for an event based on the one or more attack strategy risk scores. The method also includes determining a priority value for an asset associated with the event. The method also includes generating an asset risk score for the asset based on the priority value of the asset and the event risk score.

[0014] According to another embodiment, one or more computer-readable non-transitory storage media embody instructions that, when executed by a processor, cause the processor to perform operations. The operations include determining an attack strategy risk score for one or more attack strategies based on a data set of actual loss events, and determining an event risk score for an event based on the one or more attack strategy risk scores. The operations also include determining a priority value for an asset associated with the event. The operations also include generating an asset risk score for the asset based on the priority value of the asset and the event risk score.

[0015] Technical advantages of certain embodiments of the present disclosure may include one or more of the following advantages. Certain embodiments of the present disclosure use a prioritization model to prioritize events using real-world data, rather than prioritizing alerts based on confidence in the alerts or Security Operations Center (SOC) analysts relying on their expertise to identify alerts as high risk. Certain embodiments of the present disclosure use real-world data to prioritize threats and assign probabilities of attacks. Considering that some entities may not have the ability to fix all identified security incidents, the present disclosure assists entities in sifting through complex information to focus on threats that pose direct and / or serious threats. For smaller teams, this may include prioritizing events. For larger teams, who may try to resolve each incident and may have a larger SOC, this may include prioritizing personnel and capacity constraints.

[0016] Certain embodiments of the present disclosure determine a data-driven probability of attack for each event. Through this method of event prioritization, groups outside the security risk management team can better quantify and understand risks. For example, the financial planning team, the executive leadership team, and board members can view and monitor a data-driven and quantifiable method of security events over a period of time. Certain embodiments of the present disclosure use real-time data to guide the classification and prioritization of events so that the security team can effectively fix the events.

[0017] In some embodiments, the Endpoint Detection and Response (EDR) solution is judged based on MITRE Adversarial Tactics, Techniques, and Common Knowledge (ATT&CK) coverage. The risk model of the present disclosure can provide complete coverage by using more comprehensive data, risk-based frameworks and / or prioritized strategies and / or techniques. Certain prioritization models of the present disclosure use real-world events that have occurred in the past to help determine the risk and severity of current events. These events can be quantified and / or correlated to determine the probability and likelihood that a certain technology will actually cause losses. In some embodiments, real-world data is used to determine the likelihood that a particular event will result in a leak and the severity of the leak.

[0018] Other technical advantages will be readily apparent to those skilled in the art from the following drawings, descriptions and claims.In addition, although specific advantages are listed above, various embodiments may include all, some or none of the listed advantages.

[0019] Example Embodiments

[0020] The present disclosure describes systems and methods for generating risk scores based on actual loss events. Certain network security technologies such as Extended Detection and Response (XDR) monitor and / or mitigate network threats. Specifically, XDR is used to collect and / or correlate data across various network points (e.g., email, endpoints, servers, cloud workloads, networks, etc.), thereby providing visibility and situational understanding of advanced threats. XDR can be used to analyze, prioritize and / or remediate threats to reduce and / or prevent data loss and security vulnerabilities. In certain embodiments, XDR improves visibility and situational understanding of threats, so that previously unprocessed events can surface and reach a higher level of awareness. This increase in visibility can allow security teams to reduce and / or eliminate any further impact. This increase in visibility can also help reduce the severity and scope of attacks.

[0021] EDR is the predecessor to XDR. EDR improves malware detection and remediation beyond antivirus detection methods. EDR solutions differ from XDR in that they focus on endpoints (e.g., laptops) and record system activities and events to assist security teams (e.g., SOCs) in gaining the visibility they need to uncover incidents that would normally go undetected. XDR expands the scope of EDR to include additional security solutions. XDR provides greater visibility by collecting and correlating threat information and using analytics and automation to help detect current and future attacks.

[0022] Embodiments of the present disclosure use data sets of actual loss events to determine risk scores (e.g., risk-based XDRs). In certain embodiments, real-time data is used to inform risk analysis. Events may be categorized, and alerts prioritized to facilitate categorization of events. In some embodiments, the data is based on internal information based on what the entity may have observed on its products and from its customers.

[0023] Figure 1 An example system 100 for generating risk scores based on actual loss events is illustrated. System 100 or a portion thereof may be associated with an entity, which may include any entity that generates risk scores, such as a business, company, or enterprise. In some embodiments, the entity may be a service provider that provides security services. Components of system 100 may include any suitable combination of hardware, firmware, and software. For example, components of system 100 may be configured using Figure 3 One or more components of a computer system. Figure 1In the illustrated embodiment of , system 100 includes a network 110, an infrastructure 120, an asset 122, an event 124, a repository 130, an attack strategy 132, an actual loss event 134, a cloud 140, a server 142, a security tool 144, an attack strategy risk score 146, an event risk score 148, an asset priority value 150, an asset risk score 152, a user device 160, a user 162, and a dashboard 164.

[0024] The network 110 of the system 100 is any type of network that facilitates communications between components of the system 100. The network 110 may connect one or more components of the system 100. One or more portions of network 110 may include an ad hoc network, the Internet, an intranet, an extranet, a virtual private network (VPN), an Ethernet VPN (EVPN), a local area network (LAN), a wireless LAN (WLAN), a virtual LAN (VLAN), a wide area network (WAN), a wireless WAN (WWAN), a software-defined wide area network (SD-WAN), a metropolitan area network (MAN), a portion of a Public Switched Telephone Network (PSTN), a cellular telephone network, a Digital Subscriber Line (DSL), a Multiprotocol Label Switching (MPLS) network, a 3G / 4G / 5G network, a Long Term Evolution (LTE) network, a cloud network, a combination of two or more of these, or other suitable types of networks. Network 110 may include one or more networks of different types. The network 110 may be any communication network, such as a private network, a public network, a connection through the Internet, a mobile network, a WI-FI network, etc. The network 110 may include a core network, an access network of a service provider, an Internet service provider (ISP) network, etc. One or more components of the system 100 may communicate through the network 110.

[0025] The network 110 may include one or more nodes. A node is a connection point within the network 110 that receives, creates, stores, and / or sends data along a path. A node may include one or more redistribution points that identify, process, and forward data to other nodes of the network. A node may include virtual and / or physical nodes. In some embodiments, a node includes one or more virtual machines, hardware devices, bare metal servers, and the like. In some embodiments, a node may include a data communication device, such as a computer, a router, a server, a printer, a workstation, a switch, a bridge, a modem, a hub, and the like. A node may use static and / or dynamic routing to send data to and / or receive data from other nodes of the system 100.

[0026] The infrastructure 120 of the system 100 is the hardware, software, services and / or facilities associated with an entity (e.g., an enterprise). The infrastructure 120 provides network connectivity and communication between users, devices, applications, the Internet, and the like. The infrastructure 120 may include one or more wired and / or wireless networks. For example, the infrastructure 120 may include one or more wired networks so that data flows through cables. In some embodiments, one end of the cable may be connected to an interface card in a terminal device, and the other end may be connected to an Ethernet port on a network switch or router. For another example, the infrastructure 120 may include one or more wireless networks so that data flows in the air via radio waves. These signals may be transmitted from the terminal device to a wireless access point, which is connected to the network 110.

[0027] The infrastructure 120 of the system 100 includes assets 122. Assets 122 are valuable components of the entity's infrastructure 120 that support information-related activities. Assets 122 may include hardware (e.g., routers, gateways, switches, firewalls, hubs, printers, servers, hosts, desktop computers, laptops, wireless access points, etc.), software (e.g., operating systems (OS), applications, updates, patches, etc.), and / or confidential information. Applications perform specific functions and include web browsers, multimedia software, content access software, enterprise software, database software, etc. In some embodiments, multiple similar assets 122 may be assigned to a group. For example, multiple assets 122 utilizing Windows OS may be assigned to a group. Assets 122 may be identified by one or more owners of the assets 122, one or more administrators of the assets 122, one or more hosts of the assets 122 (e.g., cloud hosts), network accessibility of the assets 122, combinations of these, and the like. In certain embodiments, the asset 122 is identified by an asset identifier, an Internet Protocol (IP) address, a host name, a Media Access Control (MAC) address, a Uniform Resource Locator (URL) address, a comment, a combination of these, and the like.

[0028] In some embodiments, assets 122 of infrastructure 120 may be associated with one or more events 124. Events 124 are intrusion events that are likely to cause financial losses to an enterprise associated with infrastructure 120. Financial losses may refer to any financial losses to an enterprise or financial losses that exceed a predetermined threshold (e.g., a monetary value of $10,000, $1,000,000, etc.). In some embodiments, events 124 violate one or more security policies associated with infrastructure 120. Events 124 may be associated with one or more of the following: data breach events, malware, denial of service (DoS), unauthorized management access, website tampering, compromised system integrity, pranks, theft, damage, privilege escalation, internal threats, phishing, man-in-the-middle attacks, and the like. Some events 124 are more important to the availability, confidentiality, and / or integrity of assets 122 than other events. For example, port scan detection may track port scan activity within infrastructure 120, even though security policies may not explicitly prohibit port scans or consider them as high priority threats. As another example, certain events may indicate that a host within infrastructure 120 has been compromised and is engaging in a distributed denial-of-service (DDoS) attack, which may violate one or more security policies associated with infrastructure 120 .

[0029] Event 124 may be identified by the type of event (e.g., data breach, malware, etc.), information about the affected assets (e.g., host name and / or IP, time zone, purpose or function of the host, etc.), information about the source of the attack (e.g., host name and / or IP, time zone, any contact with the attacker, estimated cost to handle the incident, etc.), a description of the event (e.g., date, intrusion method, intruder tools involved, software version and / or patch level, any intruder tool output, details of the vulnerability exploited, source of the attack, any other associated information, etc.), combinations of these, and the like.

[0030] Repository 130 is a central location for storing and / or managing data. Repository 130 may include one or more digital repositories, online repositories, open access repositories, databases, subject-based repositories, Git repositories, combinations of these, and the like. Repository 130 may be stored on one or more file systems, hosted on a computer cluster, hosted in cloud storage, and the like. Repository 130 may be public or private. Public repositories 130 are accessible to all Internet users, while private repositories 130 are accessible to explicitly authorized users. Figure 1 In the illustrated embodiment of , repository 130 stores attack strategies 132 and actual loss events 134 .

[0031] Attack strategies 132 are adversarial strategies, techniques, procedures, and / or combinations thereof used by cyber threat actors to plan and / or execute cyber attacks on business infrastructure 120. In some embodiments, attack strategies 132 are stored in a globally accessible knowledge base (e.g., the MITRE ATT&CK database). A strategy represents the reason why an adversary performs a specific action. A strategy may be associated with one or more of the following: reconnaissance strategy (e.g., port scanning); resource exploitation strategy; initial access strategy (e.g., phishing); execution strategy (e.g., native API); persistence strategy; privilege escalation strategy; defense evasion strategy; credential access strategy (e.g., insecure credentials); discovery strategy (e.g., network sniffing); lateral movement strategy; collection strategy; command and control strategy (e.g., web services); penetration strategy; influence strategy, etc.

[0032] Each strategy may include one or more techniques. The technique represents the strategy target received by the adversary to perform a specific action. The attack strategy 132 may include techniques such as active scanning, network information phishing, account establishment, interaction with native OS application programming interface (application programming interface, API) to perform behavior, mandatory authentication, hijacking execution flow, obtaining, developing and / or implementing capabilities in stages, deploying containers, etc. In some embodiments, the strategy may include one or more techniques. For example, a reconnaissance strategy may include techniques involving the adversary actively and / or passively collecting information that can be used to support target positioning (e.g., detailed information of the victim's organization). For another example, a resource development strategy may include techniques involving the adversary purchasing, creating and / or destroying resources (e.g., accounts) that can be used to support target positioning. Another example is that the initial access strategy may include techniques (e.g., directed spear phishing) using an entry vector to obtain access rights within the infrastructure 120. In some embodiments, the attack strategy 132 may include a single strategy, multiple strategies, a single technique, multiple techniques, and / or any combination of these.

[0033] Actual loss events 134 represent any information related to historical losses due to security incidents. Actual loss events 134 may include incident tracking data, victim demographics, incident description data, incident discovery data, incident response data, incident impact assessment data, and the like. Actual loss events 134 may identify the actor behind a particular incident (e.g., external, internal, or partner actor), the method(s) used by the actor (e.g., malware, hacker, social, abuse, physical, error, environmental, and the like), information about the affected assets 122 (e.g., ownership, management, hosting, accessibility, cloud, and the like), information about how the assets 122 were affected (confidentiality, ownership, integrity, authenticity, availability, utility, and the like), and the like.

[0034] Actual loss events 134 may be stored in one or more public and / or private repositories 120. For example, information related to actual loss events 134 may be retrieved from a Vocabulary for Event Recording and Incident Sharing (VERIS) repository (e.g., a VERIS Community Database (VCDB)). VERIS is a set of metrics that provide a common language for describing security events in a structured manner. For another example, information related to actual loss events 134 may be retrieved from a private database of an enterprise. The private database of an enterprise may include actual loss events 134 that directly or indirectly resulted in financial losses to the enterprise.

[0035] In some embodiments, actual loss events 134 provide a historical view of cyber loss events. Actual loss events 134 may include one or more of the following characteristics: case type, case status, impacted count, incident date, loss source, loss type, actor, loss amount, company size, company type, number of employees, industry code, geographic location, etc. In some embodiments, actual loss events 134 are associated with one or more of the following types of cyber risks: leaked data, secured data, cyber extortion, inadvertently disclosed data, physically lost or stolen data, unauthorized data collection, unauthorized contact or disclosure, fraudulent use / account access, network / website outages, phishing, deception, social engineering, information theft, physical tampering, information technology (IT) configuration / implementation errors, IT processing errors, etc.

[0036] Actual loss events 134 may be collected from private sources and / or publicly available sources. For example, actual loss events 134 may be collected by a private organization (e.g., a business or entity) that monitors events 124. For another example, actual loss events 134 may be collected from publicly available sources, such as a VERIS repository or an Advisen database. Actual loss events 134 may be categorized by industry (e.g., education, finance, public sector, hospitality, retail, etc.). In some embodiments, a data set of actual loss events 134 is based on a specific industry. In some embodiments, attack strategies 132 and actual loss events 134 are communicated to cloud 140.

[0037] The cloud 140 of the system 100 refers to a server accessed via the Internet. The cloud 140 may be a private cloud, a public cloud, or a hybrid cloud. The cloud 140 may be associated with one or more of the following cloud computing service models: Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS), Infrastructure-as-a-Service (IaaS), Function-as-a-Service (FaaS), etc. Figure 1 In the illustrated embodiment of the system 100, the server 142 is hosted in the cloud 140. The server 142 may be physically located in a data center. The server 142 includes software and hardware and has computing and storage capabilities. Figure 1 In the illustrated embodiment of , server 142 hosts security tool 144 .

[0038] The security tool 144 of the system 100 is a software program used by the server 140 to determine a risk score. In some embodiments, the security tool 144 interoperates with other network components (e.g., infrastructure 120, repository 130, agent, endpoint, cloud, security product, etc.) to determine a risk score. The security tool 144 can collect, combine and / or correlate threat intelligence to efficiently respond to the incident 124. In some embodiments, the security tool 144 generates an attack strategy risk score 146, an event risk score 148, an asset priority value 150, and an asset risk score 152.

[0039] Each attack strategy risk score 146 represents the probability that the associated attack strategy 132 will result in a financial loss to the enterprise. Attack strategy risk scores 146 can be assigned to attack strategies 132 based on actual loss events 134. In some embodiments, security tools 144 analyze actual loss events 134 to understand whether they are prone to vulnerability exploits, malware exploits, active leaks (e.g., active Internet leaks), popularity as a target, etc. In some embodiments, attack strategy risk scores 146 are based on internal information based on what the enterprise may have observed on its products and / or from its customers.

[0040] In some embodiments, the security tool 144 may take into account unique universal identifiers of publicly known network security vulnerabilities (e.g., Common Vulnerabilities and Exposure (CVE) identifiers), community-developed lists of software and / or hardware weakness types (e.g., Common Weakness Enumeration (CWE) identifiers), Web Application Security Consortium (WASC) identifiers, normalized Common Vulnerability Scoring System (CVSS) scores from the National Vulnerability Database, etc., to generate the attack strategy risk score 146. For example, the security tool 144 may use one or more algorithms to layer information assessed from actual loss events 134 onto a base CVSS score associated with an attack strategy 132 to generate an attack strategy risk score 146 for that particular attack strategy 132. In some embodiments, the attack strategy risk score 146 of each attack strategy 132 is a value in the range of 0 (or 1) to 10, such that an attack strategy risk score 146 of 0 (or 1) indicates that the associated attack strategy 134 has no probability of causing financial losses to the enterprise, while an attack strategy risk score 146 of 10 indicates that the associated attack strategy 134 has the greatest probability of causing financial losses to the enterprise.

[0041] Each event 124 within the infrastructure 120 may be associated with one or more attack strategies 132. For example, a data breach event may be associated with a reconnaissance strategy, a phishing technique, a resource exploitation strategy, and / or a compromised account technique. For another example, a malware event may be associated with an execution strategy, a defense evasion strategy, and a process injection technique.

[0042] In some embodiments, the security tool 144 assigns an event risk score 148 to the event 124. Each event risk score 148 represents a probability that the associated event 124 will result in a financial loss to the enterprise. The event risk score 148 may be based on the attack strategy 132. For example, the event risk score 148 assigned to the event 124 may be the highest attack strategy risk score 146 of one or more attack strategies 132 associated with the event 124. For another example, the event risk score 148 assigned to the event 124 may be the average attack strategy risk score 146 of one or more attack strategies 132 associated with the event 124. In some embodiments, the event risk score 148 of each event 124 is a value in the range of 0 (or 1) to 100, so that an event risk score 148 of 0 (or 1) indicates that the associated event 134 has no probability of causing a financial loss to the enterprise, while an event risk score 148 of 10 indicates that the associated event 134 has the highest probability of causing a financial loss to the enterprise.

[0043] In some embodiments, the security tool 144 assigns asset priority values ​​150 to the assets 122. The asset priority values ​​150 indicate the importance of each asset 122 to a party (e.g., a business associated with the infrastructure 120). In some embodiments, the asset priority value 150 for each asset 122 is a value in the range of 0 (or 1) to 10, such that a value of 0 (or 1) indicates that the asset 122 is not important to the party, while a value of 10 indicates that the asset 122 is of the greatest importance to the party. For example, the chief executive officer's (CEO) device may be assigned an asset priority of 10, while a rarely used printer may be assigned an asset priority of 1. In some embodiments, the asset priority value 150 may refer to a priority value assigned to a group of assets 122. The security tool 144 may determine the asset priority value 150 for a group of assets 122 by averaging the asset priority values ​​150 for the group of assets 122, by taking the highest asset priority value 150 for the group of assets 122, and so on.

[0044] The asset priority value 150 may be assigned to each asset 122 manually and / or automatically. For example, the asset priority value 150 may be assigned individually by an administrator. For another example, the asset priority value 150 may be automatically assigned using a software tool (e.g., Kenna). In some embodiments, the asset priority value 150 is determined based on the identity of the asset 122, metadata associated with the asset 122, tags associated with the asset 122, detailed information of the asset 122 (e.g., IP address, host name, MAC address, operating system, etc.), users of the asset 122 (e.g., CEO, financial analyst, etc.), and the like.

[0045] In some embodiments, the security tool 144 generates an asset risk score 152 for one or more assets 122. Each asset risk score 152 represents a probability that the asset 122 will cause a financial loss to the enterprise. In some embodiments, the asset risk score 152 is determined based on the asset priority value 150 and the event risk score 148. For example, the asset risk score 152 of the asset 122 can be generated by multiplying the asset priority value 150 of the asset 122 (or a group of assets 122) by one or more event risk scores 148 associated with the asset 122. For another example, the asset risk score 152 of the asset 122 can be generated by multiplying the asset priority value 150 of the group of assets 122 by one or more event risk scores 148 associated with the group of assets 122. In some embodiments, the asset risk score 152 is a value in the range of 0 (or 1) to 1000, whereby a value of 0 indicates that the asset 122 has no probability of causing a financial loss to the enterprise, while a value of 1000 indicates that the asset 122 has the greatest probability of causing a financial loss to the enterprise.

[0046] In certain embodiments, the thresholds 154 are used to classify the asset risk scores 152. For example, a value of the asset risk score 152 that is equal to or lower than the first predetermined threshold 154 (e.g., a score of 330) may indicate that the probability that the associated asset 122 will cause a financial loss to the business is low. For another example, a value of the asset risk score 152 that is higher than the first predetermined threshold 154 (e.g., a score of 330) but lower than the second predetermined threshold 154 (e.g., a score of 670) may indicate that the probability that the associated asset 122 will cause a financial loss to the business is medium. As another example, a value of the asset risk score 152 that is equal to or higher than the second predetermined threshold 154 (e.g., a score of 670) may indicate that the probability that the associated asset 122 will cause a financial loss to the business is high.

[0047] In some embodiments, the threshold 154 is used to prioritize the asset risk scores 152. For example, the security tool 144 may prioritize asset risk scores 152 with values ​​equal to or greater than the threshold 154 (e.g., 670) over asset risk scores 152 with values ​​below the threshold 154. In some embodiments, the security tool 144 prioritizes the asset risk scores 152 based on the probability that the associated assets 122 of a particular number of asset risk scores 152 will cause a financial loss to the enterprise. For example, the security tool 144 may prioritize a predetermined number (e.g., 10, 50, or 100) of the asset risk scores 152 with the highest values. In certain embodiments, the security tool 144 may use one or more conditions (e.g., threshold 154) to generate an alert 156.

[0048] Alerts 156 are notifications based on configured conditions. In some embodiments, alerts 156 notify users 162 of any issues associated with events 124. For example, alerts 156 may notify users 162 which asset risk scores 152 exceed a predetermined threshold 154. For another example, alerts 156 may notify users 162 which asset risk scores 152 are among a predetermined number of top (e.g., top 100) asset risk scores 152. Alerts 156 may generate one or more sound tones, sound phrases, visual representations (e.g., graphs, charts, tables, lists, or any other appropriate format) to notify users 162 of the probability that one or more assets 122 will cause financial losses to the enterprise. In some embodiments, alerts 156 provide an overall view of one or more events 124 that allows users 162 to quickly determine which events 124 require immediate attention. In some embodiments, alerts 156 generate one or more reports that provide visual representations of event-related information. In some embodiments, security tools 144 generate conditions that trigger alerts 156 using thresholds 154.

[0049] The user devices 160 of the system 100 include any user device capable of receiving, creating, processing, storing and / or communicating information. The user devices 160 may include one or more workstations, desktop computers, laptop computers, mobile phones (e.g., smart phones), tablet devices, personal digital assistants (PDAs), wearable devices, and the like. In some embodiments, the user devices 160 include a liquid crystal display (LCD), an organic light-emitting diode (OLED) flat screen interface, digital buttons, a digital keyboard, physical buttons, a physical keyboard, one or more touch screen components, a graphical user interface (GUI), and the like. The user devices 160 may be located in any suitable location to receive information and communicate it to the user 162 of the system 100. In Figure 1 In the illustrated embodiment of FIG. 1 , user device 160 alerts user 162 of the probability that one or more assets 122 will result in a financial loss to the enterprise.

[0050] A user 162 of the system 100 is a person or group of people who utilize a user device 160 of the system 100. A user 162 may be associated with one or more accounts. A user 162 may be a local user, a remote user, an administrator, a customer, a company, a combination of these, and the like. A user 162 may be associated with a username, a password, a user profile, and the like. A user 162 of a user device 160 may be a security analyst, a financial analyst, and the like.

[0051] The dashboard 164 of the system 100 allows the user 162 to visualize any security issues associated with the infrastructure 120. In some embodiments, the dashboard 164 provides an overall security view of one or more events 124 and / or asset risk scores 152, which allows the user 162 to quickly determine the probability that the asset 122 will cause a financial loss to the enterprise. The dashboard 164 can display one or more graphs, charts, tables, lists, or any other suitable format to represent information related to the event. In some embodiments, the dashboard 164 provides the user 162 with a visual representation of one or more assets 122, events 124, repositories 130, attack strategies 132, actual loss events 134, attack strategy risk scores 146, event risk scores 148, asset priority values ​​150, and asset risk scores 152.

[0052] In operation, a server 142 of the cloud 140 receives data associated with assets 122 (e.g., applications, firewalls, devices, printers, etc.) and events 124 (e.g., data breach events, malware events, etc.) from the infrastructure 120. The security tool 144 also receives data associated with attack strategies 132 (e.g., reconnaissance strategies, resource exploitation strategies, initial access strategies, etc.) and actual loss events 134 (e.g., breach data and / or assurance data) from the repository 130. The security tool 144 determines an attack strategy risk score 146 (e.g., a score from 0 to 100) for each attack strategy 132 based in part on the data set of actual loss events 134. The security tool 144 also determines an event risk score 148 (e.g., a score from 0 to 100) for the event based on the attack strategy risk score 146. Each event risk score 148 is associated with a probability that the event 124 will result in a financial loss to the enterprise. The security tool 144 determines an asset priority value 150 (e.g., a score from 0 to 10) for each asset 122 and generates an asset risk score 152 (e.g., a score from 0 to 1000) for the asset 122 by multiplying the asset priority value 150 by the event risk score 148 associated with the asset 122. The security tool 144 compares the asset risk score 152 to a predetermined threshold 154 and generates an alert 156 if the asset risk score 152 exceeds the predetermined threshold 154. Thus, the system 100 allows an administrator to quickly determine which assets 122 are more likely to cause financial losses to the enterprise.

[0053] Although Figure 1A particular number of networks 110, infrastructures 120, assets 122, events 124, repositories 130, attack strategies 132, actual loss events 134, clouds 140, servers 142, security tools 144, attack strategy risk scores 146, event risk scores 148, asset priority values ​​150, asset risk scores 152, user devices 160, users 162, and dashboards 164 are illustrated, but the present disclosure contemplates any suitable number of networks 110, infrastructures 120, assets 122, events 124, repositories 130, attack strategies 132, actual loss events 134, clouds 140, servers 142, security tools 144, attack strategy risk scores 146, event risk scores 148, asset priority values ​​150, asset risk scores 152, user devices 160, users 162, and dashboards 164. For example, system 100 may include more than one infrastructure 120.

[0054] Although Figure 1 A particular arrangement of network 110, infrastructure 120, assets 122, events 124, repository 130, attack strategies 132, actual loss events 134, cloud 140, server 142, security tools 144, attack strategy risk scores 146, event risk scores 148, asset priority values ​​150, asset risk scores 152, user devices 160, users 162, and dashboard 164 is illustrated, but the present disclosure contemplates any suitable arrangement of network 110, infrastructure 120, assets 122, events 124, repository 130, attack strategies 132, actual loss events 134, cloud 140, server 142, security tools 144, attack strategy risk scores 146, event risk scores 148, asset priority values ​​150, asset risk scores 152, user devices 160, users 162, and dashboard 164. For example, repository 130 may be located in cloud 140.

[0055] In addition, although Figure 1 While specific components, devices, or systems are described and illustrated as performing particular actions, this disclosure contemplates any suitable combination of any suitable components, devices, or systems performing any suitable actions.

[0056] Figure 2 An example method 200 for generating risk scores based on actual loss events is illustrated. The method 200 begins at step 205. At step 210 of the method 200, the security tool receives assets and events from the infrastructure. For example, referring to Figure 1, the security tool 144 of the system 100 may receive information associated with assets 122 and events 124 from the infrastructure 120. Assets are valuable components of an entity's infrastructure that support information-related activities. Assets 122 may include routers, gateways, switches, firewalls, hubs, printers, servers, hosts, desktop computers, laptops, wireless access points, applications, updates, patches, confidential information, and the like. Events are intrusion events that may result in financial losses to an enterprise associated with the infrastructure. Events may include data leaks, malware, denial of service (DoS), unauthorized management access, website tampering, compromised system integrity, pranks, theft, damage, privilege escalation, internal threats, phishing, malware, man-in-the-middle attacks, and the like. Then, the method 200 moves from step 210 to step 215.

[0057] At step 215 of method 200, the security tool receives the attack strategy and the actual loss event from the repository. Figure 1 , the security tool 144 of the system 100 may receive the attack strategy 132 and the actual loss event 134 from the repository 130. The attack strategy is the countermeasure strategy, technique and / or procedure used by the network threat actor to plan and / or execute the network attack on the business infrastructure. The attack strategy may include reconnaissance strategy (e.g., port scanning), resource development strategy, initial access strategy, execution strategy, persistence strategy, privilege escalation strategy, defense avoidance strategy, credential access strategy, discovery strategy (e.g., network sniffing), lateral movement strategy, collection strategy, command and control strategy (e.g., web service), penetration strategy, influence strategy, etc. The attack strategy may include techniques such as active scanning, network information phishing, account establishment, interaction with native OS API to perform behavior, forced authentication, hijacking execution flow, obtaining, developing and / or implementing capabilities in stages, deploying containers, etc. Then, the method 200 moves from step 215 to step 220.

[0058] At step 220 of method 200, the security tool determines an attack strategy risk score for each attack strategy based on actual loss events. Figure 1 , the security tool 144 can determine an attack strategy risk score 146 for each attack strategy 132 based on the actual loss event 134. The security tool can use one or more algorithms to layer the information from the actual loss event assessment onto the base CVSS score associated with the attack strategy to generate an attack strategy risk score for the attack strategy. Then, the method 200 moves from step 220 to step 225.

[0059] At step 225 of method 200, the security tool determines an event risk score for each event based on one or more attack strategy risk scores. Figure 1 , the security tool 144 may determine an event risk score 148 for the event 124 based on one or more attack strategy risk scores 146. Each event risk score represents the probability that the associated event will result in a financial loss to the enterprise. In some embodiments, the event risk score for a particular event may be the highest attack strategy risk score of one or more attack strategies associated with the event. In some embodiments, the event risk score for a particular event may be the average attack strategy risk score of one or more attack strategies associated with the event. Then, the method 200 moves from step 225 to step 230.

[0060] At step 230 of method 200, the security tool determines a priority value for the asset. Figure 1 , the security tool 144 may determine an asset priority value 150 for the asset 122. The asset priority value indicates the importance of each asset to a party (e.g., a business associated with the infrastructure). The method 200 then moves from step 230 to step 235, where the security tool determines whether one or more events are associated with the asset. For example, referring to Figure 1 , the security tool 144 can determine whether one or more events 124, such as a data breach or malware, are associated with the asset 122. If, at step 235, the security tool determines that one or more events are associated with the asset, the method 200 moves from step 235 to step 240, where the security tool generates an asset risk score for the asset based on the asset's priority value and the event risk score. For example, referring to Figure 1 , the security tool 144 may generate an asset risk score 152 for the asset 122 by multiplying the asset priority value 150 of the asset 122 by the event risk score 148. Each asset risk score represents the probability that the asset will cause a financial loss to the enterprise.

[0061] In some embodiments, the asset risk score is a value in the range of 0 to 1000, whereby a value of 0 indicates that the asset has no probability of causing financial losses to the enterprise, while a value of 1000 indicates that the asset has the highest probability of causing financial losses to the enterprise. For example, for a particular asset with an asset priority value of 10 and an event risk score of 100, the asset risk score is 1000, indicating that the asset has the highest probability of causing financial losses to the enterprise. For another example, for a particular asset with an asset priority value of 0 and an event risk score of 0, the asset risk score is 0, indicating that the asset has no probability of causing financial losses to the enterprise. Then, the method 200 moves from step 240 to step 255.

[0062] If, at step 235, the security tool determines that no events are associated with the asset, then method 200 proceeds from step 235 to step 245, where the security tool determines whether one or more events are associated with the asset group. Figure 1 , the security tool 144 can determine whether one or more events 124, such as a data breach or malware, are associated with a group of assets 122. If, at step 245, the security tool determines that the one or more events are not associated with a group of assets, the method 200 proceeds from step 245 to step 265, where the method 200 ends.

[0063] If, at step 245, the security tool determines that one or more events are associated with the asset group, then method 200 moves from step 245 to step 250, where the security tool generates an asset risk score for the asset group based on the priority value of the asset group and the one or more event risk scores associated with the assets. Figure 1 , the security tool 144 can generate an asset risk score 152 for a group of assets 122 by multiplying the asset priority value 150 of the asset 122 by the (one or more) event risk score 148. Each asset risk score represents the probability that the asset group will cause financial loss to the enterprise. The method 200 then moves to step 255.

[0064] At step 255 of method 200, the security tool determines whether the asset risk score exceeds a predetermined threshold. Figure 1 , the security tool 144 may determine whether the asset risk score 152 exceeds the threshold 154. In some embodiments, the threshold is used to classify the asset risk score. For example, an asset risk score of an asset (or asset group) equal to or higher than the first threshold 670 may indicate that the associated asset (or asset group) has a high probability of causing a financial loss to the enterprise; a value of the asset risk score higher than the second threshold 330 but lower than the first threshold 670 may indicate that the associated asset (or asset group) has a medium probability of causing a financial loss to the enterprise; and a value of the asset risk score equal to or lower than the second threshold 330 may indicate that the associated asset (or asset group) has a low probability of causing a financial loss to the enterprise. If the security tool determines that the asset risk score does not exceed the predetermined threshold, the method 200 proceeds from step 255 to step 265, where the method 200 ends.

[0065] If, at step 255, the security tool determines that the asset risk score exceeds a predetermined threshold, then method 200 moves from step 255 to step 260, where the security tool generates an alert for the asset. Figure 1, if the asset risk score 152 (e.g., a value of 550 or 730) exceeds the threshold 154 (e.g., a value of 670), the security tool 144 may generate an alert 156 for the asset 122 (or a group of assets 122). In some embodiments, the alert is communicated to a dashboard of the user device. The alert may notify a user of the user device of certain events / assets that require immediate attention. The method 200 then moves from step 260 to step 265, where the method 200 ends. Thus, the method 200 allows an administrator to quickly determine which assets are more likely to cause financial losses to the enterprise.

[0066] Although this disclosure describes and illustrates Figure 2 The specific steps of method 200 are not intended to occur in a specific order, but the present disclosure contemplates Figure 2 Any suitable steps of method 200 may occur in any suitable order. For example, step 230 for determining a priority value for an asset may occur before step 210 for receiving assets and events from the infrastructure. Although the present disclosure describes and illustrates an example method 200 for generating risk scores based on actual loss events, including Figure 2 However, the present disclosure contemplates any suitable method for generating a risk score based on actual loss events, which may include, where appropriate Figure 2 All, some or none of the steps of the method. Figure 2 While specific components, devices, or systems are described and illustrated as performing particular actions, this disclosure contemplates any suitable combination of any suitable components, devices, or systems performing any suitable actions.

[0067] Figure 3 An example computer system 300 is illustrated. In particular embodiments, one or more computer systems 300 perform one or more steps of one or more methods described or illustrated herein. In particular embodiments, one or more computer systems 300 provide functionality described or illustrated herein. In particular embodiments, software running on one or more computer systems 300 performs one or more steps of one or more methods described or illustrated herein or provides functionality described or illustrated herein. Particular embodiments include one or more portions of one or more computer systems 300. In this document, reference to a computer system may encompass a computing device and vice versa, where appropriate. Furthermore, reference to a computer system may encompass one or more computer systems, where appropriate.

[0068] The present disclosure contemplates any suitable number of computer systems 300. The present disclosure contemplates that computer system 300 takes any suitable physical form. By way of example and not limitation, computer system 300 may be an embedded computer system, a system-on-chip (SOC), a single-board computer system (SBC) (e.g., a computer-on-module (COM) or a system-on-module (SOM)), a desktop computer system, a laptop or notebook computer system, an interactive digital kiosk, a mainframe, a grid of computer systems, a mobile phone, a personal digital assistant (PDA), a server, a tablet computer system, an augmented / virtual reality device, or a combination of two or more of these. Where appropriate, computer system 300 may include one or more computer systems 300; may be single, or distributed; may span multiple locations; may span multiple machines; may span multiple data centers; or may reside in a cloud, which may include one or more cloud components in one or more networks. Where appropriate, one or more computer systems 300 may perform one or more steps of one or more methods described or illustrated herein without substantial spatial or temporal limitations. As an example and not limitation, one or more computer systems 300 may perform one or more steps of one or more methods described or illustrated herein in real time or in batch mode. Where appropriate, one or more computer systems 300 may perform one or more steps of one or more methods described or illustrated herein at different times or at different locations.

[0069] In a particular embodiment, computer system 300 includes a processor 302, a memory 304, a storage device 306, an input / output (I / O) interface 308, a communication interface 310, and a bus 312. Although this disclosure describes and illustrates a particular computer system having a particular number of particular components in a particular arrangement, this disclosure contemplates any suitable computer system having any suitable number of any suitable components in any suitable arrangement.

[0070] In certain embodiments, the processor 302 includes hardware for executing instructions, such as those that constitute a computer program. By way of example and not limitation, to execute instructions, the processor 302 may retrieve (or obtain) instructions from an internal register, an internal cache, a memory 304, or a storage device 306; decode and execute the instructions; and then write one or more results to an internal register, an internal cache, a memory 304, or a storage device 306. In certain embodiments, the processor 302 may include one or more internal caches for data, instructions, or addresses. The present disclosure contemplates that the processor 302 includes any appropriate number of any appropriate internal caches, as appropriate. By way of example and not limitation, the processor 302 may include one or more instruction caches, one or more data caches, and one or more translation lookaside buffers (TLBs). The instructions in the instruction cache may be copies of instructions in the memory 304 or the storage device 306, and the instruction cache may speed up the retrieval of these instructions by the processor 302. The data in the data cache may be a copy of data in the memory 304 or storage device 306 for the instruction operation executed at the processor 302; the result of the previous instruction executed at the processor 302, for the subsequent instruction executed at the processor 302 to access or write to the memory 304 or storage device 306; or other appropriate data. The data cache may accelerate the read or write operation of the processor 302. The TLB may accelerate the virtual address translation for the processor 302. In a particular embodiment, the processor 302 may include one or more internal registers for data, instructions, or addresses. The present disclosure contemplates that the processor 302 includes any appropriate number of any appropriate internal registers, as appropriate. The processor 302 may include one or more arithmetic logic units (ALUs), as appropriate; may be a multi-core processor; or may include one or more processors 302. Although the present disclosure describes and illustrates a particular processor, the present disclosure contemplates any appropriate processor.

[0071] In certain embodiments, memory 304 includes main memory for storing instructions for execution by processor 302 or data for operation by processor 302. By way of example and not limitation, computer system 300 may load instructions from storage device 306 or another source (e.g., another computer system 300) to memory 304. Processor 302 may then load instructions from memory 304 to internal registers or internal caches. To execute the instructions, processor 302 may retrieve the instructions from the internal registers or internal caches and decode them. During or after execution of the instructions, processor 302 may write one or more results (which may be intermediate or final results) to the internal registers or internal caches. Processor 302 may then write one or more of these results to memory 304. In certain embodiments, processor 302 executes only instructions in one or more internal registers or internal caches or in memory 304 (rather than storage device 306 or elsewhere) and operates only on data in one or more internal registers or internal caches or in memory 304 (rather than storage device 306 or elsewhere). One or more memory buses (each of which may include an address bus and a data bus) may couple the processor 302 to the memory 304. The bus 312 may include one or more memory buses, as described below. In a particular embodiment, one or more memory management units (MMUs) exist between the processor 302 and the memory 304 and facilitate access to the memory 304 requested by the processor 302. In a particular embodiment, the memory 304 includes a random access memory (RAM). Where appropriate, this RAM may be a volatile memory. Where appropriate, this RAM may be a dynamic RAM (DRAM) or a static RAM (SRAM). In addition, where appropriate, this RAM may be a single-port or multi-port RAM. The present disclosure contemplates any suitable RAM. Where appropriate, the memory 304 may include one or more memories 304. Although the present disclosure describes and illustrates specific memories, the present disclosure contemplates any suitable memory.

[0072] In a particular embodiment, the storage device 306 includes a large-capacity storage device for data or instructions. As an example and not limitation, the storage device 306 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a tape, or a Universal Serial Bus (USB) drive or a combination of two or more of these. Where appropriate, the storage device 306 may include a removable or non-removable (or fixed) medium. Where appropriate, the storage device 306 may be inside or outside the computer system 300. In a particular embodiment, the storage device 306 is a non-volatile solid-state memory. In a particular embodiment, the storage device 306 includes a read-only memory (ROM). Where appropriate, this ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), an electrically alterable ROM (EAROM), or a flash memory, or a combination of two or more of these. The present disclosure contemplates that mass storage device 306 takes any suitable physical form. Storage device 306 may include one or more storage control units that facilitate communication between processor 302 and storage device 306, where appropriate. Storage device 306 may include one or more storage devices 306, where appropriate. Although the present disclosure describes and illustrates particular storage devices, the present disclosure contemplates any suitable storage devices.

[0073] In a particular embodiment, the I / O interface 308 includes hardware, software, or both that provide one or more interfaces for communication between the computer system 300 and one or more I / O devices. Where appropriate, the computer system 300 may include one or more of these I / O devices. One or more of these I / O devices can enable communication between a person and the computer system 300. As an example and not limitation, the I / O device may include a keyboard, a keypad, a microphone, a monitor, a mouse, a printer, a scanner, a speaker, a static camera, a stylus, a tablet device, a touch screen, a trackball, a video camera, another appropriate I / O device, or a combination of two or more of these. The I / O device may include one or more sensors. The present disclosure contemplates any appropriate I / O device and any appropriate I / O interface 308 for them. Where appropriate, the I / O interface 308 may include one or more device or software drivers so that the processor 302 can drive one or more of these I / O devices. Where appropriate, the I / O interface 308 may include one or more I / O interfaces 308. Although the present disclosure describes and illustrates a specific I / O interface, the present disclosure contemplates any appropriate I / O interface.

[0074] In a particular embodiment, the communication interface 310 includes hardware, software, or both that provide one or more interfaces for communication (e.g., packet-based communication) between the computer system 300 and one or more other computer systems 300 or one or more networks. By way of example and not limitation, the communication interface 310 may include a network interface controller (NIC) or a network adapter for communicating with an Ethernet or other line-based network, or a wireless NIC (WNIC) or a wireless adapter for communicating with a wireless network such as a WI-FI network. The present disclosure contemplates any suitable network and any suitable communication interface 310 for it. By way of example and not limitation, the computer system 300 may communicate with one or more portions of an ad hoc network, a personal area network (PAN), a LAN, a WAN, a MAN, or the Internet, or a combination of two or more of these. One or more portions of one or more of these networks may be wired or wireless. As an example, the computer system 300 may communicate with a wireless PAN (WPAN) (e.g., a Bluetooth WPAN), a WI-FI network, a WI-MAX network, a cellular telephone network (e.g., a Global System for Mobile Communications (GSM) network, a 3G network, a 4G network, a 5G network, an LTE network), or other suitable wireless networks, or a combination of two or more of these. Where appropriate, the computer system 300 may include any suitable communication interface 310 for any of these networks. Where appropriate, the communication interface 310 may include one or more communication interfaces 310. Although the present disclosure describes and illustrates particular communication interfaces, the present disclosure contemplates any suitable communication interface.

[0075] In certain embodiments, bus 312 includes hardware, software, or both that couples components of computer system 300 to each other. By way of example and not limitation, bus 312 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a front-side bus (FSB), a HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an INFINIBAND interconnect, a low-pin-count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCIe) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association local (VLB) bus, or other suitable bus, or a combination of two or more of these. Where appropriate, bus 312 may include one or more buses 312. Although this disclosure describes and illustrates a particular bus, this disclosure contemplates any suitable bus or interconnect.

[0076] In summary, in one embodiment, a method includes determining an attack strategy risk score for one or more attack strategies based on a data set of actual loss events, and determining an event risk score for an event based on the one or more attack strategy risk scores. The method also includes determining a priority value for an asset. The asset is associated with the event. The method also includes generating an asset risk score for the asset based on the priority value of the asset and the event risk score.

[0077] As used herein, one or more computer-readable non-transitory storage media may include one or more semiconductor-based or other integrated circuits (ICs) (e.g., field-programmable gate arrays (FPGAs) or application-specific ICs (ASICs)), hard disk drives (HDDs), hybrid hard disk drives (HHDs), optical disks, optical disk drives (ODDs), magneto-optical disks, magneto-optical drives, floppy disks, floppy disk drives (FDDs), magnetic tapes, solid-state drives (SSDs), RAM drives, secure digital cards or drives, any other suitable computer-readable non-transitory storage media, or any suitable combination of two or more of these, where appropriate. Where appropriate, computer-readable non-transitory storage media may be volatile, non-volatile, or a combination of volatile and non-volatile.

[0078] As used herein, "or" is inclusive and not exclusive, unless expressly indicated otherwise or indicated by context. Thus, as used herein, "A or B" means "A, B, or both," unless expressly indicated otherwise or indicated by context. Additionally, "and" is both conjunctive and several, unless expressly indicated otherwise or indicated by context. Thus, as used herein, "A and B" means "A and B, jointly or severally," unless expressly indicated otherwise or indicated by context.

[0079] The scope of the present disclosure covers all changes, substitutions, variations, modifications and modifications to the example embodiments described or illustrated herein that will be understood by those of ordinary skill in the art. The scope of the present disclosure is not limited to the example embodiments described or illustrated herein. In addition, although the present disclosure describes and illustrates the various embodiments herein as including specific components, elements, features, functions, operations or steps, any of these embodiments may include any combination or permutation of any components, elements, features, functions, operations or steps described or illustrated anywhere herein that will be understood by those of ordinary skill in the art. In addition, the device or system or the component of the device or system mentioned in the attached claims is adapted to, arranged to, capable of, configured to, enabled to, operable to, or operated to perform a specific function, covering the device, system, component, whether it or the specific function is activated, turned on or unlocked, as long as the device, system or component is so adapted, arranged to, capable of doing so, configured to, enabled to, operable to, or operated to. In addition, although the present disclosure describes or illustrates that a specific embodiment provides a specific advantage, a specific embodiment may not provide these advantages or provide part or all of these advantages.

Claims

1. A network component comprising one or more processors and one or more computer-readable non-transitory storage media coupled to the one or more processors, the media comprising instructions that, when executed by the one or more processors, cause the network component to perform operations comprising: determining an attack strategy risk score for one or more attack strategies based on a data set of actual loss events; determining an event risk score for the event based on the one or more attack strategy risk scores; determining a priority value for an asset, wherein the asset is associated with the event; and An asset risk score is generated for the asset based on the priority value of the asset and the event risk score.

2. The network component of claim 1, wherein: The event risk score is associated with the probability that the event will result in a financial loss to the enterprise.

3. The network component according to claim 1 or 2, wherein: The event risk score is associated with one of the following: a highest attack strategy risk score of the one or more attack strategies; or An average attack strategy risk score for the one or more attack strategies.

4. The network component according to any one of claims 1 to 3, wherein: Generating the asset risk score for the asset includes multiplying the priority value of the asset by the event risk score.

5. The network component according to any one of claims 1 to 4, wherein: The event risk score is one of a plurality of event risk scores associated with the asset; and Generating the asset risk score for the asset is based on the priority value of the asset and the plurality of event risk scores.

6. The network component according to any one of claims 1 to 5, wherein: The attack strategy risk score for each of the one or more attack strategies is a value in the range of 1 to 100; The event risk score of the event is a value in the range of 1 to 100; and The priority value of the asset is a value in the range of 1 to 10; and The asset risk score is a value in the range of 1 to 1000.

7. The network component according to any one of claims 1 to 6, wherein: The data set of actual loss events includes leakage data and assurance data.

8. A method comprising: determining an attack strategy risk score for one or more attack strategies based on a data set of actual loss events; determining an event risk score for the event based on the one or more attack strategy risk scores; determining a priority value for an asset, wherein the asset is associated with the event; and An asset risk score is generated for the asset based on the priority value of the asset and the event risk score.

9. The method of claim 8, wherein: The event risk score is associated with the probability that the event will result in a financial loss to the enterprise.

10. The method according to claim 8 or 9, wherein: The event risk score is associated with one of the following: The highest attack strategy risk score of the one or more attack strategies; or An average attack strategy risk score for the one or more attack strategies.

11. The method according to any one of claims 8 to 10, wherein: Generating the asset risk score for the asset includes multiplying the priority value of the asset by the event risk score.

12. The method according to any one of claims 8 to 11, wherein: The event risk score is one of a plurality of event risk scores associated with the asset; and Generating the asset risk score for the asset is based on the priority value of the asset and the plurality of event risk scores.

13. The method of any one of claims 8 to 12, wherein: The attack strategy risk score for each of the one or more attack strategies is a value in the range of 1 to 100; The event risk score of the event is a value in the range of 1 to 100; and The priority value of the asset is a value in the range of 1 to 10; and The asset risk score is a value in the range of 1 to 1000.

14. The method according to any one of claims 8 to 13, wherein: The data set of actual loss events includes leakage data and assurance data.

15. One or more computer-readable non-transitory storage media, the media embodying instructions that, when executed by a processor, cause the processor to perform operations comprising: determining an attack strategy risk score for one or more attack strategies based on a data set of actual loss events; determining an event risk score for the event based on the one or more attack strategy risk scores; determining a priority value for an asset, wherein the asset is associated with the event; and An asset risk score is generated for the asset based on the priority value of the asset and the event risk score.

16. The one or more computer-readable non-transitory storage media of claim 15, wherein: The event risk score is associated with the probability that the event will result in a financial loss to the enterprise.

17. One or more computer-readable non-transitory storage media as claimed in claim 15 or 16, wherein: The event risk score is associated with one of the following: a highest attack strategy risk score of the one or more attack strategies; or An average attack strategy risk score for the one or more attack strategies.

18. One or more computer-readable non-transitory storage media as claimed in any one of claims 15 to 17, wherein: Generating the asset risk score for the asset includes multiplying the priority value of the asset by the event risk score.

19. One or more computer-readable non-transitory storage media as claimed in any one of claims 15 to 18, wherein: The event risk score is one of a plurality of event risk scores associated with the asset; and Generating the asset risk score for the asset is based on the priority value of the asset and the plurality of event risk scores.

20. One or more computer-readable non-transitory storage media as claimed in any one of claims 15 to 19, wherein: The attack strategy risk score for each of the one or more attack strategies is a value in the range of 1 to 100; The event risk score of the event is a value in the range of 1 to 100; and The priority value of the asset is a value in the range of 1 to 10; and The asset risk score is a value in the range of 1 to 1000.

21. A network component comprising: means for determining an attack strategy risk score for one or more attack strategies based on a data set of actual loss events; means for determining an event risk score for the event based on the one or more attack strategy risk scores; means for determining a priority value for an asset, wherein the asset is associated with the event; as well as Means for generating an asset risk score for the asset based on the priority value of the asset and the event risk score.

22. The network component of claim 21, further comprising means for implementing the method of any one of claims 9 to 14.

23. A computer program, a computer program product or a computer readable medium comprising instructions which, when executed by a computer, cause the computer to perform the steps of the method of any one of claims 8 to 14.