AU2016218307A1 - Apparatus and method for providing possible causes, recommended actions, and potential impacts related to identified cyber-security risk items - Google Patents

Abstract

This disclosure provides an apparatus and method for providing possible causes, recommended actions, and potential impacts related to identified cyber-security risk items. A method includes identifying (305), by a risk manager system (154), a plurality of connected devices (106, 114, 122, 130, 138) that are vulnerable to cyber-security risks. The method includes identifying (310), by the risk manager system (154), cyber-security risks in the connected devices (106, 114, 122, 130, 138). The method includes, for each identified cyber-security risk, identifying (315) by the risk manager system (154) at least one possible cause (230), at least one recommended action (234), and at least one potential impact (232). The method includes displaying (320), by the risk manager system (154), a user interface (220) that includes a summary (206, 216, 224) of the identified cyber-security risks.

Description

PCT/US2016/016519 WO 2016/130394 1

APP ARATUS AND METHOD FOR PROVIDING POSSIBL E; CAUSES, RECOMMENDED ACTIONS, AND POTENTIAL IMPACTS RELATED TO IDENTIFIED CYBER-SECURITY RISK ITEMS

CROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of the filing date of United States Provisional Patent Application 62/114,865, filed February 11,2015, which is hereby incorporated by reference. to

TECHNICAL FIELD

[0002] This disclosure relates generally to network security. More specifically, this disclosure relates to an apparatus and method for providing possible causes, 15 recommended actions, and potential impacts related to identified cyber-security risk items.

BACKGROUND 20 [0003] Processing facilities are often managed using industrial process control and automation systems. Conventional control and automation systems routinely include a variety of networked devices, such as servers, workstations, switches, routers, firewalls, safety- systems, proprietary real-time controllers, and industrial field devices. Oftentimes, this equipment comes from a number of different vendors. In industrial environments, 25 cyber-security is of increasing concern, and unaddressed security vulnerabilities in any of these components could be exploited by attackers to disrupt operations or cause unsafe conditions in an industrial facility. 30 PCT/US2016/016519 WO 2016/130394 2

SUMMARY

[0004] This disclosure provides an apparatus and method for providing possible causes, recommended actions, and potential impacts related to identified cyber-security risk items. A method includes identifying, by a risk manager system, a plurality of connected 5 devices that are vulnerable to cyber-security risks. The method includes identifying, by the risk manager system, cyber-security risks in the connected devices. The method includes, for each identified cyber-security risk, identifying by the risk manager system at least one possible cause, at least one recommended action, and at least one potential impact. The method includes displaying, by the risk manager system, a user interface 10 that includes a summary of the identified cyber-security risks.

[0005] Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims. PCT/US2016/016519 WO 2016/130394 3

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] For a more complete understanding of this disclosure, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which: 5 [0007] FIGURE 1 illustrates an example industrial process control and automation system according to this disclosure, [0008] FIGURES 2A through 2C illustrate an example graphical user interface for providing possible causes, recommended actions, and potential impacts related to identified cyber-security risk items according to this disclosure; and 10 [0009] FIGURE 3 illustrates a flowchart of a process in accordance with disclosed embodiments. PCT/US2016/016519 WO 2016/130394 4

DETAILED DESCRIPTION

[0010] The figures, discussed below, and the various embodiments used to describe the principles of the present invention in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the invention. Those skilled 5 in the art will understand that the principles of the invention may be implemented in any type of suitably arranged device or system.

[0011] Figure 1 illustrates an example industrial process control and automation system 100 according to this disclosure. As shown in Figure 1, the system 100 includes various components that facilitate production or processing of at least one product or other 10 material. For instance, the system 100 is used here to facilitate control over components in one or multiple plants 10Ia-I01n. Each plant lOla-lOln represents one or more processing facilities (or one or more portions thereof), such as one or more manufacturing facilities for producing at least one product or other material. In general, each plant 101a-10In may implement one or more processes and can individually or 15 collectively be referred to as a process system. A process system generally represents any system or portion thereof configured to process one or more products or other materials in some manner.

[0012] In Figure 1, the system 100 is implemented using the Purdue model of process control . In the Purdue model, “Level 0” may include one or more sensors 102a and one 20 or more actuators 102b. The sensors 102a and actuators 102b represent components in a process system that may perform any of a wide variety of functions. For example, the sensors 102a could measure a wide variety of characteristics in the process system, such as temperature, pressure, or flow rate. Also, the actuators 102b could alter a wide variety of characteristics in the process system. The sensors 102a and actuators 102b could 25 represent any other or additional components in any suitable process system. Each of the sensors 102a includes any suitable structure for measuring one or more character!sti es in a process system. Each of the actuators 102b includes any suitable structure for operating on or affecting one or more conditions in a process system.

[0013] At least one network 104 is coupled to the sensors 102a and actuators 102b. The 30 network 104 facilitates interaction with the sensors 102a and actuators 102b. For example, the network 104 could transport measurement data from the sensors 102a and PCT/US2016/016519 WO 2016/130394 5 provide control signals to the actuators 102b. The network 104 could represent any suitable network or combination of networks. As particular examples, the network 104 could represent an Ethernet network, an electrical signal network (such as a HART or FOUNDATION FIELDBUS network), a pneumatic control signal network, or any other 5 or additional type(s) of network(s).

[0014] In the Purdue model, “Level 1 ” may include one or more control lers 106, which are coupled to the network 104. Among other things, each controller 106 may use the measurements from one or more sensors 102a to control the operation of one or more actuators 102b. For example, a controller 106 could receive measurement data from one 10 or more sensors 102a and use the measurement data to generate control signals for one or more actuators 102b. Each controller 106 includes any suitable structure for interacting with one or more sensors 102a and controlling one or more actuators 102b. Each controller 106 could, for example, represent a proportional-integral-derivative (FID) controller or a multivariable controller, such as a Robust Multivariable Predictive Control 15 Technology (RMPCT) controller or other type of controller implementing model predictive control (MFC) or other advanced predictive control (AFC). As a particular example, each controller 106 could represent a computing device running a real-time operating system.

[0015] Two networks 108 are coupled to the controllers 106. The networks 108 20 facilitate interaction with the controllers 106, such as by transporting data to and from the controllers 106. The networks 108 could represent any suitable networks or combination of networks. As a particular example, the networks 108 could represent a redundant pair of Ethernet networks, such as a FAULT TOLERANT ETHERNET (FTE) network from HONEYWELL INTERNATIONAL INC. 25 [0016] At least one switch/firewall 110 couples the networks 108 to two networks 112.

The switch/firewali 110 may transport traffic from one network to another. The switch/firewall 110 may also block traffic on one network from reaching another network. The switch/firewall 110 includes any suitable structure for providing communication between networks, such as a HONEYWELL CONTROL FIREWALL 30 (C’F9) device. The networks 112 could represent any suitable networks, such as an FTE network. PCT/US2016/016519 2016/130394 6 [0017] In the Purdue model, “Level 2” may include one or more machine-level controllers 114 coupled to the networks 112. The machine-level controllers 114 perform various functions to support the operation and control of the controllers 106, sensors 102a, and actuators 102b, which could be associated with a particular piece of industrial equipment (such as a boiler or other machine). For example, the machine-level controllers 114 could log information collected or generated by the controllers 106, such as measurement data from the sensors 102a or control signals for the actua tors 102b. The machine-level controllers 114 could also execute applications that control the operation of the controllers 106, thereby controlling the operation of the actuators 102b. In addition, the machine-level controllers 114 could provide secure access to the controllers 106. Each of the machine-level controllers 114 includes any suitable structure for providing access to, control of, or operations related to a machine or other individual piece of equipment. Each of the machine-level controllers 114 could, for example, represent a server computing device running a MICROSOFT WINDOWS operating system. Although not shown, different machine-level controllers 114 could be used to control different pieces of equipment in a process system (where each piece of equipment is associated with one or more controllers 106, sensors 102a, and actuators 102b).

[0018] One or more operator stations 1.1.6 are coupled to the networks 1.12. The operator stations 116 represent computing or communication devices providing user access to the machine-level controllers 114, which could then provide user access to the controllers 106 (and possibly the sensors 102a and actuators 102b). As particular examples, the operator stations 116 could allow users to review the operational hi story of the sensors 102a and actuators 102b using information collected by the controllers 106 and/or the machine-level controllers 114. The operator stations 116 could also allow' the users to adjust the operation of the sensors 102a, actuators 102b, controllers 106, or machine-level controllers 114. In addition, the operator stations 116 could receive and display warnings, alerts, or other messages or displays generated by the control] ers 106 or the machine-level controllers 114. Each of the operator stations 116 includes any suitable structure for supporting user access and control of one or more components in the system 100. Each of the operator stations 116 could, for example, represent a computing device running a MICROSOFT WINDOWS operating system.

[0019] At least one router/firewall 118 couples the networks 112 to two networks 120. PCT/US2016/016519 WO 2016/130394 7

The router/firewall 118 includes any suitable structure for providing communication between networks, such as a secure router or combination router/firewall. The networks 120 could represent any suitable networks, such as an FTE network.

[0020] In the Purdue model, “Level 3” may include one or more unit-level controllers 5 122 coupled to the networks 120. Each unit-level controller 122 is typically associated with a unit in a process system, which represents a collection of different machines operating together to implement at least part of a process. The unit-level controllers 122 perform various functions to support the operation and control of components in the lower levels. For example, the unit-level controllers 122 could log information collected 10 or generated by the components in the lower levels, execute applications that control the components in the lower levels, and provide secure access to the components in the lower levels. Each of the unit-level controllers 122 includes any suitable stnjcture for providing access to, control of or operations related to one or more machines or other pieces of equipment in a process unit. Each of the unit-level controllers 122 could, for example, 15 represent a server computing device running a MICROSOFT WINDOWS operating system. Although not shown, different unit-level controllers 122 could be used to control different units in a process system (where each unit is associated with one or more machine-level controllers 114, controllers 106, sensors 102a, and actuators 102b).

[0021] Access to the unit-level controllers 122 may be provided by one or more 20 operator stations 124. Each of the operator stations 124 includes any suitable structure for supporting user access and control of one or more components in the system 100. Each of the operator stations 124 could, for example, represent a computing device running a MICROSOFT WINDOWS operating system.

[0022] At least one router/firewall 126 couples the networks 120 to two networks 128. 25 The router/firewall 126 includes any suitable structure for providing communication between networks, such as a secure router or combination router/firewall. The networks 128 could represent any suitable networks, such as an FTE network.

[0023] In the Purdue model, “Level 4” may include one or more plant-level controllers 130 coupled to the networks 128. Each plant-level controller 130 is typically associated 30 with one of the plants lOia-lOln, which may include one or more process units that PCT/US2016/016519 WO 2016/130394 8 implement the same, similar, or different processes. The plant-level controllers 130 perform various functions to support the operation and control of components in the lower levels. As particular examples, the plant-level controller 130 could execute one or more manufacturing execution system (MES) applications, scheduling applications, or 5 other or additional plant or process control applications. Each of the plant-level controllers 130 includes any suitable structure for providing access to, control of, or operations related to one or more process units in a process plant. Each of the plant-level controllers 130 could, for example, represent a server computing device running a MICROSOFT WINDOWS operating system. 10 [0024] Access to the plant-level controllers 130 may be provided by one or more operator stations 132, Each of the operator stations 132 includes any suitable structure for supporting user access and control of one or more components in the system 100. Each of the operator stations 132 could, for example, represent a computing device running a MICROSOFT WINDOWS operating system. 15 [0025] At least one router/firewall 134 couples the networks 128 to one or more networks 136. The router/firewall 134 includes any suitable structure for providing communication between networks, such as a secure router or combination router/firewall. The network 136 could represent any suitable netw'ork, such as an enterprise-wide Ethernet or other network or all or a portion of a larger network (such as the Internet). 20 [0026] In the Purdue model, “Level 5” may include one or more enterprise-level controllers 138 coupled to the network 136. Each enterprise-level controller 138 is typically able to perform planning operations for multiple plants lOla-lOln and to control various aspects of the plants IOla-101 n. The enterprise-level controllers 138 can also perform various functions to support the operation and control of components in the 25 plants lOla-lOln. As particular examples, the enterprise-level controller 138 could execute one or more order processing applications, enterprise resource planning (ERP) applications, advanced planning and scheduling (APS) applications, or any other or additional enterprise control applications. Each of the enterprise-level controllers 138 includes any suitable structure for providing access to, control of, or operations related to

30 the control of one or more plants. Each of the enterprise-level controllers 138 could, for example, represent a server computing device tunning a MICROSOFT WINDOWS PCT/US2016/016519 WO 2016/130394 9 operating system. In this document, the term “enterprise” refers to an organization having one or more plants or other processing facilities to be managed. Note that if a single plant 101a is to be managed, the functionality of the enterprise-level controller 138 could be incorporated into the plant-level controller 130. 5 [0027] Access to the enterprise-level controllers 138 may be provided by one or more operator stations 140. Each of the operator stations 140 includes any suitable structure for supporting user access and control of one or more components in the system 100. Each of the operator stations 140 could, for example, represent a computing device running a MICROSOFT WINDOWS operating system. 10 [0028] Various levels of the Purdue model can include other components, such as one or more databases. The database(s) associated with each level could store any suitable information associated with that level or one or more other levels of the system 100, For example, a historian 141 can be coupled to the network 136. The historian 141 could represent a component that stores various information about the system 100. The 15 historian 141 could, for instance, store information used during production scheduling and optimization. The historian 141 represents any suitable structure for storing and facilitating retrieval of information. Although shown as a single centralized component coupled to the network 136, the historian 141 could be located elsewhere in the system 100, or multiple historians could be distributed in different locations in the system 100. 20 [0029] In particular embodiments, the various controllers and operator stations in

Figure 1 may represent computing devices. For example, each of the controllers 106,114, 122, 130, 138 could include one or more processing devices 142 and one or more memories 144 for storing instructions and data used, generated, or collected by the processing device(s) 142. Each of the controllers 106, 114, 122, 130, 138 could also 25 include at least one network interface 146, such as one or more Ethernet interfaces or wireless transceivers. Also, each of die operator stations 116, 124,132,140 could include one or more processing devices 148 and one or more memories 150 for storing instructions and data used, generated, or collected by the processing device(s) 148. Each of the operator stations 116, 124, 132, 140 could also include at least one network 30 interface 152, such as one or more Ethernet interfaces or wireless transceivers. PCT/US2016/016519 WO 2016/130394 10 [0030] As noted above, cyber-security is of increasing concern with respect to industrial process control and automation systems. Unaddressed security vulnerabilities in any of the components in the system 100 could be exploited by attackers to disrupt operations or cause unsafe conditions in an industrial facility. However, in many 5 instances, operators do not have a complete understanding or inventory of all equipment running at a particular industrial site. As a result, it is often difficult to quickly determine potential sources of risk, to a control and automation system. This disclosure recognizes a need for a solution that understands potential vulnerabilities in various systems, prioritizes the vulnerabilities based on risk to an overall system, and guides a user to 10 mitigate the vulnerabilities, [0031] Moreover, in the context of an industrial process control and automation system, personnel within industrial control environments (such as industrial plants) are not typically trained to deal with cyber-security threats, vulnerabilities, and risks. Because of this, cyber-security tools often provide less value in those contexts because 15 users are unlikely to fully understand what the information being presented means to them and their facilities. Disclosed embodiments address this issue by providing information and advice to a user, educating the user during use. For example, if an indicator of a cyber-security risk is presented, the indicator can be explained in layman’s terms. Also, possible causes of the indicator can be explained, as well as potential 20 impacts to an industrial facility. Advice on what actions should be taken to resolve a specific cause of a risk can further be provided to help guide the user to take appropriate steps towards risk mitigation.

[0032] This can be accomplished (among other ways) using a risk manager 154. Among other things, the risk manager 154 supports a technique for providing possible 25 causes, recommended actions, and potential impacts related to identified cyber-security risk items. As a particular example of this functionality, when the risk manager 154 identifies an indicator of a cyber-security risk (such as by using a rule engine), the risk manager 154 uses that, indicator to determine possible causes, recommended actions, and potential impacts associated with the risk. Values for these three items can be determined 30 using the indicator, such as by retrieving associated information from a database 155. When a rule triggers and identifies a risk item, the relevant values can be retrieved from the database 155, associated with the indicator, and displayed within a user interface PCT/US2016/016519 WO 2016/130394 11 (such as under an “additional details” option in the user interface). The three values may be statically defined, reference other areas of the risk manager 154, and/or make calls for additional information.

[0033] The “possible causes” values are typically influenced by the risk indicator itself 5 and involve a database lookup to determine the values. For cyber-security vulnerabilities, causes can often include misconfigurations or inherent weaknesses in software. For cyber-security threats, causes can often include actual hacking of a device or exposure of a device to malware.

[0034] The “potential impacts” values are often determined for a risk indicator based 10 on the target or targets to which a risk applies (such as a PC or other networked device, a “zone” containing multiple devices, etc.). The risk indicator can be cross-referenced against outside criteria, such as the possible impact of the specific risk item or the potential impact due to the loss of a target device or other devices that are dependent on the target device (such as process controllers, I/O devices, etc.). In various embodiments, 15 the risk manager 154 can uses its understanding of the network architecture, such as industrial process control and automation system 100, and specific connected control devices to identify what control assets could be impacted by a cyber incident targeting a device at higher levels in the Purdue model.

[0035] The “recommended actions” values are typically influenced by the risk indicator 20 itself and can be determined by cross-referencing specific risk items to the database 155 of relevant actions or mitigations.

[0036] In this example, the risk manager 154 includes one or more processing devices 156; one or more memories .158 for storing instructions and data used, generated, or collected by the processing device(s) 156; and at least one network interface 160. Each 25 processing device 156 could represent a microprocessor, microcontroller, digital signal process, field programmable gate array, application specific integrated circuit, or discrete logic. Each memory 158 could represent a volatile or non-volatile storage and retrieval device, such as a random access memory or Flash memory. Each network interface 160 could represent an Ethernet interface, wireless transceiver, or other device facilitating 30 external communication. The functionality of the risk manager 154 could be PCT/US2016/016519 WO 2016/130394 12 implemented using any suitable hardware or a combination of hardware and software/firmware instructions. The database 155 denotes any suitable structure facilitating storage and retrieval of information.

[0037] Although Figure 1 illustrates one example of an industrial process control and 5 automation system 100, various changes may be made to Figure 1. For example, a control and automation system could include any number of sensors, actuators, controllers, servers, operator stations, networks, risk managers, and other components. Also, the makeup and arrangement of the system 100 in Figure 1 is for illustration only. Components could be added, omitted, combined, or placed in any other suitable 10 configuration according to particular needs. Further, particular functions have been described as being performed by particular components of the system 100, This is for illustration only. In general, control and automation systems are highly configurable and can be configured in any suitable manner according to particular needs. In addition, Figure 1 illustrates an example environment in which the functions of the risk manager 15 154 can be used. This functionality can be used in any other suitable device or system.

[0038] Figures 2A through 2C illustrate an example graphical user interface (GUI) for providing possible causes, recommended actions, and potential impacts related to identified cyber-security risk items according to this disclosure. This GUI can be implemented, for example as a display of risk manager 154 for interactions with a user, 20 as described in more detail below. Note that, while the figures for this patent document are shown in black-and-white, the GUI can and generally will display the data using color coding to indicate such factors as relative risk level, different components or zones, or other data.

[0039] In particular, Figure 2A illustrates a user interface 200 providing a graphical 25 summary of the cyber-security risk items identified by the risk manager 154. User interface 200 can include a number of features to indicate cyber-security risk items and related data. User interface 200 can include a net site risk area 202 that illustrates the relative risk percentages for a plurality· of system zones and risk types. As illustrated in this example, the “patches” risk type (for software that has not been fully updated or 30 patched) is very high in system zone 1. Net site risk area 202 can also display an overall net site risk, which is shown as 80% in this example. PCT/US2016/016519 WO 2016/130394 13 [0040] User interface 200 can include a notification area 204 that notifies users of important information such as notifications, warnings, and alerts. Each of these notification types can indicate a different severity, such as an alert being more severe than a warning, which is more severe than a notification. Each notification type can be 5 represented by a different symbol or color, as illustrated. A user can select one of the symbols to see the actual notification, warning, or alert in the user interface 200.

[0041] User interface 200 can include a risk level summary 206 by area for one or more zones. In this example, risk level summary' 206 uses “gauge” graphics to illustrate the risk level in each of the areas of network security, patches, backup, and endpoint 10 security'. As illustrated here, additional data can be included that describes the reason for a particular area’s risk level. For example, the “network security” area shows a 62% risk level, and indicates that there are two security issues.

[0042] User interface 200 can also include a trend-view chart 208 that illustrates the net site risk over a selectable peri od of time. In this example, the “30-day” chart has been 15 selected, and the trend-view' chart 208 shows a 30-day net site trend.

[0043] Figure 2B illustrates a user interface 210 providing a graphical summary of the cyber-security risk items identified by the risk manager 154, such as a list summary of the cyber-security risk items identified by the risk manager 154. User interface 210 can include a number of features to indicate cyber-security risk items and related data. User 20 interface 200 can include a net site risk area 212 that displays, for each of a plurality of system zones, a current risk value and a 30-day risk value graph. Net site risk area 212 can also can also display an overall net site risk that indicates the relative overall cybersecurity risk of the system, which is shown as 80% in this example.

[0044] User interface 210 can include a notification area 214 that notifies users of 25 important information such as notifications, warnings, and alerts. Each of these notification types can indicate a different severity, such as an alert being more severe than a warning, which is more severe than a notification. Each notification type can be represented by a different symbol or color, as illustrated. A user can select one of the symbols to see the actual notification, warning, or alert in the user interface 200. 30 Notification area 214 can display a 30-day notification graph for each notification type; PCT/US2016/016519 WO 2016/130394 14 as shown in this example, there are 30-day notification graphs for the notifications, warnings, and alerts.

[0045] User interface 210 can include a risk level summary 216 by area for one or more zones. In this example, risk level summary 216 uses a percentage number to 5 illustrate the risk level in each of the areas of network security, patches, backup, and endpoint security. As illustrated here, additional data can be included that describes the reason for a particular area’s risk level. For example, the “network security'’ area shows a 62% risk level, and indicates that there are two security' issues. This example of the risk level summary 215 by area also includes a 30-day level chart graph for each area. 10 [0046] User interface 210 can al so include a trend-view chart 218 that il lustrates the net site risk over a selectable period of time. In this example, the “30-day” chart has been selected, and the trend-view chart 208 shows a 30-day net site trend.

[0047] Figure 2C illustrates that a particular risk item has been selected to reveal the possible causes, potential impacts, and recommended actions for that risk item. Figure 2€ 15 illustrates a user interface 220 that includes a notification area 224 that notifies users of important information such as notifications, warnings, and alerts. Each of these notification types can indicate a different severity', such as an alert being more severe than a warning, which is more severe than a notification. Each notification type can be represented by a different symbol or color, as illustrated. A user can select one of the 20 symbols to see the actual notification, warning, or alert in the user interface 200. Notification area 214 can display a 30-day notification graph for each notification type; as shown in this example, there are 30-day notification graphs for the notifications, warnings, and alerts.

[0048] As illustrated in Figure 2C, the notification area 224 can receive a user selection 25 of a notification, warning, or alert, and in response, display details of the particular notification, warning, or alert. The details can include such details as a parameter name 226 and a description 228. The details can include possible causes 230, potential impacts 232, and recommended actions 234.

[0049] Although Figures 2A through 2€ illustrate one example of a graphical user 30 interface for providing possible causes, recommended actions, and potential impacts PCT/US2016/016519 WO 2016/130394 15 related to identified cvber-security risk items, various changes may be made to Figures 2A through 2C. For example, the content and layout of information in each figure is for illustration only.

[0050] Figure 3 illustrates a flowchart of a method 300 in accordance with disclosed 5 embodiments, as can be performed, for example, by risk manager 154 or another device or controller (referred to as the “system” below).

[0051] The system identifies a plurality of connected devices that are vulnerable to cyber-security risks (305). These could be any of the devices or components as illustrated in Figure 1, or others. The devices can each be associated with a zone of a 10 system such as system 100.

[0052] The system identifies cyber-security risks in the connected devices (310). Each cyber-security risk can be classified by type such as a notification, a warning, or an alert.

[0053] For each identified cyber-security risk, the system identifies at least one possible cause, at least one recommended action, and at least one potential impact (315). 15 [0054] The system stores these and displays, to a user, a user interface that includes a summaiy of the identified cyber-security risk items identified by the risk manager (320). The summary can include graphical indicators such as trend-view charts and other charts, gauge graphics, colors or symbol s to designate risk types, etc. The summary can include, for each identified cyber-security risk, the corresponding identified possible cause, 20 recommended action, and potential impact. The summary can group the identified cyber-security risks by associated zones.

[0055] Note that the risk manager 154 and/or the graphical user interfaces shown here could use or operate in conjunction with any combination or all of various features described in the following previously-filed and concurrently-filed patent applications (all 25 of which are hereby incorporated by reference): • U.S. Patent Application No. 14/482,888 entitled “DYNAMIC QUANTIFICATION OF CYBER-SECURITY RISKS IN A CONTROL SYSTEM”; * U.S. Provisional Patent Application No. 62/036,920 entitled “ANALYZING CYBER-SECURITY RISKS IN AN INDUSTRIAL CONTROL ENVIRONMENT”; PCT/US2016/016519 2016/130394 16 • U.S. Provisional Patent Application No. 62/113,075 entitled “RULES ENGINE FOR CONVERTING SYSTEM-RELATED CHARACTERISTICS AND EVENTS INTO CYBER-SECURITY RISK ASSESSMENT VALUES” and corresponding nonprovisional U.S. Patent Application 14/871,695 of like title (Docket No. H0048932-0115) filed concurrently herewith; • U.S. Provisional Patent Application No. 62/113,221 entitled “NOTIFICATION SUBSYSTEM FOR GENERATING CONSOLIDATED, FILTERED, AND RELEVANT SECURITY RISK-BASED NOTIFICATIONS” and corresponding non-provisional U.S, Patent Application 14/871,521 of like title (Docket No. H0048937-0115) filed concurrently herewith; • U.S. Provisional Patent Application No. 62/113,100 entitled “TECHNIQUE FOR USING INFRASTRUCTURE MONITORING SOFTWARE TO COLLECT CYBER-SECURITY RISK DATA” and corresponding non-provisional U.S. Patent Application 14/871,855 of like title (Docket No. H0048943-0115) filed concurrently herewith; • U.S. Provisional Patent Application No. 62/113,186 entitled “INFRASTRUCTURE MONITORING TOOL FOR COLLECTING INDUSTRIAL PROCESS CONTROL AND AUTOMATION SYSTEM RISK DATA” and corresponding non-provisional U.S. Patent Application 14/871,732 of like title (Docket No. H0Q48945-0115) filed concurrently herewith; • U.S, Provisional Patent Application No. 62/113,165 entitled “PATCH MONITORING AND ANALYSIS” and corresponding non-provisional U.S. Patent Application 14/871,921 of like title (Docket No. H0048973-0115) filed concurrently herewith; • U.S. Provisional Patent Application No. 62/113,152 entitled “APPARATUS AND METHOD FOR AUTOMATIC HANDLING OF CYBER-SECURITY RISK EVENTS” and corresponding non-provisional U.S. Patent Application 14/871,503 oflike title (Docket No. H0049067-0115) filed concurrently herewith, • U.S. Provisional Patent Application No. 62/114,928 entitled “.APPARATUS AND METHOD FOR DYNAMIC CUSTOMIZATION OF CYBER-SECURITY RISK ITEM RULES” and corresponding non-provisional U.S. Patent Application 14/871,605 oflike title (Docket No. H0049099-0115) filed concurrently herewith;

• U.S. Provisional Patent Application No. 62/114,937 entitled “APPARATUS PCT/US2016/016519 WO 2016/130394 17 AND METHOD FOR TYING CYBER-SECURITY RISK ANALYSIS TO COMMON RISK METHODOLOGIES AND RISK LEVELS” and corresponding non-provisional U.S. Patent Application 14/871,136 of like title (Docket No. H0049104-0115) filed concurrently herewith; and

5 · U.S. Provisional Patent Application No. 62/116,245 entitled “RISK MANAGEMENT IN AN ADI-GAPPED ENVIRONMENT” and corresponding nonprovisional U.S. Patent Application 14/871,547 of like title (Docket No. H0049081-0115) filed concurrently herewith.

[0056] In some embodiments, various functions described in this patent document are 10 implemen ted or supported by a computer program that i s formed from computer readable program code and that is embodied in a computer readable medium. The phrase “computer readable program code” includes any type of computer code, including source code, object code, and executable code. The phrase “computer readable medium” includes any type of medium capable ofbeing accessed by a computer, such as read only 15 memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. A “non-transitory” computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory7 electrical or other signals. A non-transitory computer readable medium includes media where data can be permanently stored and media where data can 20 be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.

[0057] It may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The terms “application” and “program” refer to one or more computer programs, software components, sets of instructions, procedures, 25 functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer code (including source code, object code, or executable code). The term “communicate,” as well as derivatives thereof, encompasses both direct and indirect communication. The terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation. The term “or” is inclusive, 30 meaning and/or. The phrase “associated with,” as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, PCT/US2016/016519 WO 2016/130394 18 be proximate to, be bound to or with, have, have a property ot, have a relationship to or with, or the like. The phrase “at least one of,” when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, “at least one of: A, B, and C” includes any of the 5 following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0058] While this disclosure has described certain embodiments and generally associated methods, alterations and permutations of these embodiments and methods will be apparent to those skilled in the art. Accordingly, the above description of example embodiments does not define or constrain this disclosure. Other changes, substitutions, 10 and alterations are also possible without departing from the spirit and scope of this disclosure, as defined by the following claims.

Claims (15)

1. WHAT IS CLAIMED IS:

   1. A method comprising: identifying (305), by a risk manager system (154), a plurality of connected devices (106, 114, 122, 130, 138) that are vulnerable to cyber-security risks; identifying (310), by the risk manager system (154), cyber-security risks in the connected devices (106, 114, 122, 130, 138); for each identified cyber-security risk, identifying (315) by the risk manager system (154) at least one possible cause (230), at least one recommended action (234), and at least one potential impact (232); and displaying (320), by the risk manager system (154), a user interface (220) that includes a summary (206, 216, 224) of the identified cyber-security risks.
2. 2. The method of claim 1, wherein the summary (206, 216, 224) includes graphical indicators including at least one of a trend-view chart, a 30-day graph, gauge graphics, colors, or symbols that designate risk types.
3. 3. The method of claim 1, wherein the summary (206,216,224) includes, for each identified cyber-security risk, the corresponding identified possible cause (230), recommended action (234), and potential impact (232).
4. 4. The method of clai tn 1, wherein each of the connected devices (106,114, 122, 130, 138) is associated with a zone of a system and the summary (216) groups the identified cyber-security risks by associated zones.
5. 5. The method of claim 1, wherein the each cyber-security risk is classified (214) by type selected from a notification, a warning, or an alert.
6. 6. The method of claim 1, wherein the each cyber-security risk is classified (204) by a type indicating a respective severity of the cyber-security risk.
7. 7. The method of claim 1, wherein the summary (212) includes an overall net site risk that indicates the relative overall cyber-security risk of the system.
8. 8. A risk manager system (154) comprising: a controller (156); and a display, the risk manager system configured to identify (305) a plurality of connected devices (106,114, 122, 130, 138) that are vulnerable to cyber-security risks; identify (310) cyber-security7 risks in the connected devices (106, 114,122, 130, 138); for each identified cyber-security risk, identify (315) at least one possible cause (230), at least one recommended action (234), and at least one potential impact (232); and display (320) a user interface (220) that includes a summary (206, 216, 224) of the identified cyber-security risks.
9. 9. The risk manager system of claim 8, wherein the summary (206,216,224) includes graphical indicators including at least one of a trend-view chart, a 30-day graph, gauge graphics, colors, or symbols that designate risk types.
10. 10. The risk manager system of claim 8, wherein the summary' (206,216,224) includes, for each identified cyber-security risk, the corresponding identified possible cause (230), recommended action (234), and potential impact (232).
11. 11. The risk manager system of claim 8, wherein each of the connected devices (106, 114, 122,130, 138) is associated with a zone of a system and the summary (216) groups the identified cyber-security7 risks by associated zones.
12. 12. The risk manager system of claim 8, w'herein the each cyber-security risk is classified (214) by type selected from a notification, a warning, or an alert.
13. 13. The risk manager system of claim 8, w'herein the each cyber-security risk is classified (204) by a type indicating a respective severity of the cyber-security risk.
14. 14. The risk manager system of claim 8, wherein the summary (212) includes an overall net site risk that indicates the relative overall cyber-security7 risk of the system.
15. 15. A non-transitory machine-readable medium (158) encoded with executable instructions that, when executed, cause one or more processors (156) of a risk management system (154) to: identify (305) a plurality of connected devices (106, 114, 122, 130, 138) that are vulnerable to cvber-security risks; identify (310) cyber-security risks in the connected devices (106, 114, 122, 130, 138); for each identified cyber-security risk, identify (315) at least one possible cause (230), at least one recommended action (234), and at least one potential impact (232); and display (320) a user interface (220) that includes a summary' (206, 216, 224) of the identified cyber-security risks.