Patent Application
20180144144
The present disclosure relates to security and network operations.
Operational technology networks associated with industrial control systems generally use proprietary technology and are generally isolated. However, operational technology networks and controller devices within the networks can be connected with other networks (e.g., enterprise networks), raising the possibility of network attacks to operational technology networks and/or controller devices in an industrial control system. Insider attacks may be launched by authorized users in an enterprise network or operational technology network control zone, whereas outsider attacks may be launched by attackers who are not authorized users. Properties targeted by an attacker may generally include control (e.g., timeliness) and security (e.g., availability, integrity, confidentiality) properties.
In general, one innovative aspect of the subject matter described in this specification can be embodied in systems including an industrial control network, one or more controller devices, one or more emulators, and an encryption relay processor. Each controller device can be operable to control one or more operational devices connected to the industrial control network. Each emulator can be configured to communicate with a respective controller device, and each emulator can be configured to reference a respective profile that includes information about security capabilities of the respective controller device. The encryption relay processor can be operable to facilitate communication to and from each emulator over the industrial control network. The encryption relay processor can execute a cryptographic function for a communication between the emulator and a node on the industrial control network when the respective controller device is incapable of performing the cryptographic function.
This and other embodiments may each optionally include one or more of the following features. For instance, a security server can be included, operable to maintain the respective profile for the respective controller device and to implement the emulator. The security server can be operable to reference specification information for the respective controller device and to generate the profile based on the specification information. The security server can be operable to create the emulator based on its respective profile. The security server and the encryption relay processor can each be operable to maintain a list of controller devices that are incapable of performing the cryptographic function. The security server and the encryption relay processor can each be operable to maintain a shared encryption key and to perform key negotiation protocols. The communication can be encrypted or decrypted using the shared encryption key. The encryption relay processor may not execute the cryptographic function for the communication between the emulator and the node on the industrial control network when the respective controller device is capable of performing the cryptographic function. A firewall can be included between the one or more emulators and the encryption relay processor.
In general, another innovative aspect of the subject matter described in this specification can be embodied in methods for facilitating communication in an industrial control network, including receiving, from a site security server, an encrypted query for a controller device; determining that the controller device is incapable of performing a cryptographic operation; after determining that the controller device is incapable of performing a cryptographic operation, decrypting the query for the controller device and providing the decrypted query to the controller device; in response to receiving an unencrypted query response from the controller device, encrypting the query response; and providing the encrypted query response to the site security server.
This and other embodiments may each optionally include one or more of the following features. For instance, specification information for the controller device can be referenced and a profile for the controller device can be generated that includes information about its security capabilities, based on the specification information. An emulator for the controller device can be created based on the profile for the controller device. The emulator can handle cryptographic operations for its corresponding controller device. Determining that the controller device is incapable of performing the cryptographic operation can include referencing the profile for the controller device. A list of controller devices that are incapable of performing the cryptographic operation can be maintained. Determining that the controller device is incapable of performing the cryptographic operation can include referencing the list. The encrypted query for the controller device can be received from the site security server through a firewall, and the encrypted query response can be provided to the site security server through the firewall.
Other embodiments of these aspects include corresponding computer methods, and include corresponding apparatus and computer programs recorded on one or more computer storage devices, configured to perform the actions of the methods. A system of one or more computers can be configured to perform particular operations or actions by virtue of having software, firmware, hardware, or a combination of them installed on the system that in operation causes or cause the system to perform the actions. One or more computer programs can be configured to perform particular operations or actions by virtue of including instructions that, when executed by data processing apparatus, cause the apparatus to perform the actions.
Particular embodiments of the subject matter described in this specification may be implemented so as to realize one or more of the following advantages. Assets of an industrial control system can be protected in a connected networking environment, such as an operational technology network connected to an enterprise network and/or the Internet. Device emulators can be created for protecting controller devices from security threats, based on company guidelines—thus, customized security policies can be implemented for particular environments. Emulators can be customized for particular devices that are to be accessed from outside of the operational technology network, based on device capabilities. Security for an industrial control system can be implemented without interrupting operation of an operational technology network, and without installing software or software patches on controller devices to be protected. Security controls for emulated controller devices can be managed flexibly—obsolete controls can be removed and new controls can be added. Information from multiple controller devices and/or from multiple operational technology networks can be aggregated and accessed at a single terminal. Centralized control and configuration can be provided for multiple controller devices and/or multiple operational technology networks.
The details of one or more embodiments of the subject matter described in this specification are set forth in the accompanying drawings and the description below. Other potential features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.
Like reference symbols in the various drawings indicate like elements.
This specification describes systems, methods, and computer programs for providing an industrial security agent platform. Information technology networks (e.g., enterprise technology networks) may be connected with operational technology networks and/or the Internet to facilitate access, efficiency, and situational awareness. However, connecting information technology networks with operational technology networks may bring security risks to either or both networks. In general, controller devices (e.g., programmable logic controllers) may be used to send, receive, and/or process data from sensors, and may be used to control physical hardware devices such as valves and actuators in an industrial control system. Some controller devices that operate within an industrial control system may be manufactured without cybersecurity features and may not be updated or replaced due to operational issues. When connected to an information technology network or the Internet, for example, such controller devices may be vulnerable to unauthorized access and/or security attacks.
An industrial security agent platform may be provided for protecting assets in an industrial control system in a connected networking environment. To protect assets in an operational technology network, for example, a virtual security entity (e.g., an emulated device) may be created and maintained for each controller device. Device emulators, for example, may handle network communications to and from their associated controller devices, and may provide a secure representation of the controller devices to a network. In general, the industrial security agent platform can implement cyber security controls, such as authentication and encryption, on a device emulator. Communications between a controller device and a network may be handled by the device emulator, for example, subject to implemented security controls (e.g. access, encryption, and/or decryption) for the particular device.
The enterprise network 102 can include a management server 114 and one or more associated input/output devices (e.g., an interface device 112). The management server 114, for example, can include one or more processors configured to execute instructions stored by computer-readable media for performing various operations, such as input/output, communication, data processing and/or data maintenance. For example, the management server 114 can perform tasks such as inventory and status monitoring for various site security servers (e.g., site security servers 124a, 124b, and 124n), where each site security server is configured to provide security services (e.g., authentication, cryptographic capabilities) for a respective operational technology network (e.g., networks 104a, 104b, and 104n). Each of the site security servers 124a, 124b, and 124n, for example, can provide configuration data to controller devices included in each of the operational technology networks 104a, 104b, and 104n, and can implement an aggregate view of information from the networks. To interact with the management server 114, for example, a user can employ the interface device 112 (e.g., including one or more presentation components such as a display, and one or more input components such as a keyboard, mouse, and/or touchpad).
Each of the operational technology networks 104a, 104b, and 104n can include a respective site security server 124a, 124b, and 124n and one or more associated input/output devices (e.g., interface devices 122a, 122b, and 122n). Each of the site security servers 124a, 124b, and 124n, for example, can include one or more processors configured to execute instructions stored by computer-readable media for performing various operations, such as input/output, communication, data processing and/or data maintenance. For example, the site security server 124a can provide security functions for one or more controller devices 126a in the operational technology network 104a, the site security server 124b can provide security functions for one or more controller devices 126b in the operational technology network 104b, and the site security server 124n can provide security functions for one or more controller devices 126n in the operational technology network 104n. To interact with each of the respective security servers 124a, 124b, and 124n, for example, a user can employ the respective associated interface device 122a, 122b, or 122n (e.g., including one or more presentation components such as a display, and one or more input components such as a keyboard, mouse, and/or touchpad).
In some implementations, a site security server may provide (or provide access to) various site management and facility tools. For example, each of the site security servers 124a, 124b, and 124n can include software tools to locate existing controller devices in an operational technology network. To locate controller devices, for example, network-based techniques may be used to explore a network, or a device information data store (e.g., device information store 116a, 116b, or 116n) may be accessed. As another example, each of the site security servers 124a, 124b, and 124n can include software tools to orchestrate its security controls with security controls provided by other devices (e.g., firewalls and site security servers). As another example, each of the site security servers 124a, 124b, and 124n can include software tools to enable or disable remote access to particular controller devices and/or particular operational technology networks.
In some implementations, each site security server may be in communication with a respective security relay server. For example, the site security server 124a can communicate with a security relay server 128a, the site security server 124b can communicate with a security relay server 128b, and the site security server 124n can communicate with a security relay server 128n. Each of the security relay servers 128a, 128b, and 128n, for example, can perform various security functions, such as encrypting and decrypting packets to and from respective controller devices 126a, 126b, and 126n that are incapable of performing cryptographic operations, such that data communication between each of the site security servers 124a, 124b, and 124n, and the respective controller devices 126a, 126b, and 126n are encrypted. In some implementations, a site security server may be deployed in a different network than its respective security relay server. For example, each site security server 124a, 124b, and 124n may be deployed in a peripheral network (e.g., a DMZ network), whereas each security relay server 128a, 128b, and 128n may be deployed its respective operational technology network 104a, 104b, and 104n.
The enterprise zone 202, for example, can include an enterprise network, a site business planning network, a logistics network, and other suitable networks, such as the Internet. In the present example, the enterprise zone 202 includes a management server 214 (e.g., similar to the management server 114, shown in
In general, the management server 214 may be used to manage operational technology networks for various industrial sites, and to provide information related to each of the networks. The management server 214, for example, can perform functions such as lifecycle management (e.g., providing deployment, configuration, status monitoring, updates, termination, etc.) for various site security servers, can provide an aggregate view of information (e.g., network and/or device statuses) from various site security servers and operational technology networks, and can provide secure communications to and from site security servers and operational technology networks. Providing secure communications between the management server 214 and a site security server 224 (e.g., similar to the site security servers 124a, 124b, and 124n, shown in
The DMZ 204 (or peripheral network) may be physically located outside of the enterprise zone 202 and the control zone 206, for example in a location in which authorized employees have access. In the present example, the DMZ 204 includes the site security server 224, and includes terminal services 230, a historian mirror 232, a patch management server 234, an application server 236, an antivirus server 238, and a firewall 240.
In general, the site security server 224 may be used to provide cyber security functions for an operational technology network, and for controller devices included in the operational technology network. Cyber security functions, for example, may include functions such as operational technology network security functions (e.g., group membership management, key and password management and distribution, group bootstrapping management, and network-level intrusion detection and prevention), device-level security functions (e.g., authentication, access control, secure communication, bootstrapping management, device-level patching, and device-level intrusion detection and prevention), and device security capability profiling. The site security server 224, for example, can handle secure communications between the management server 214 and an operational technology network in the control zone 206. When handling such communications, for example, the site security server 224 can perform group-level and device-level security functions. To interact with the site security server 224 and/or other devices included in the DMZ 204, for example, a user can employ an interface device 222 (e.g., including one or more presentation components such as a display, and one or more input components such as a keyboard, mouse, and or touchpad.)
In some implementations, network-based intrusion detection systems (NIDS) and/or host-based intrusion detection systems (HIDS) can be employed to detect attacks targeting control devices in the control zone 206 and nodes in the enterprise zone 202 and DMZ 204, and attacks targeting the site security server 224 itself. For example, signature-based and/or anomaly-based approaches may be used to detect an attack. In response to a detected attack, for example, an appropriate response may be performed.
Referring to other devices included in the DMZ 204, the terminal services 230, the historian mirror 232, the patch management server 234, the application server 236, and the antivirus server 238, for example, can each provide services and/or data to devices in the control zone 206. The terminal services 230, for example, can provide a remote interface to devices. The historian mirror 232, for example, can back up information related to various device factors (e.g., activity, status, configuration, etc.), and can provide an interface for presenting such information. The patch management server 234, for example, can store scheduling information and can facilitate device patching based on a schedule. The application server 236, for example, can host custom applications that may operate within the DMZ 204. The antivirus server 238, for example, can scan devices and/or network traffic for potential computer viruses.
The control zone 206, for example, may include one or more operational technology networks for controlling devices (e.g., sensors, valves, and actuators) at an industrial site such as a manufacturing facility. Since some controller devices in the control zone 206 may not be equipped with security modules, for example, clear text communication may occur unless remedial measures are employed. In the present example, the control zone 206 includes a security relay 228 (e.g., similar to the security relay servers 128a, 128b, and 128n, shown in
Referring to other components included in the control zone 206, for example, controller devices 250a, 252a, 250b, and 252b are included. Each of the controller devices 250a, 252a, 250b, and 252b, for example, can be a low-level controller, such as a batch control, discrete control, continuous control, or hybrid control. Supervisory controls 254a and 254b, for example, can each control multiple low-level controls. For example, supervisory control 254a can coordinate controller devices 250a and 252a, and supervisory control 254b can coordinate controller devices 250b and 252b. Each of the controller devices 250a, 252a, 250b, and 252b, and each of the supervisory controls 254a and 254b, for example, may be programmable logic controllers (PLCs). Human-machine interface (HMI) devices 256a and 256b, for example, can provide an interface to controller devices and supervisory controls in the control zone 206.
Referring to other components included in the control zone 206, for example, various high-level controls are included. In the present example, the control zone 206 includes a production control 260, an optimizing control 262, and a historian 264. The production control 260, for example, can be used to manage a production process, and the optimizing control 262 can be used to optimize the process. The historian 264, for example, can store, maintain, and provide information related to the production process and to activities performed by each controller device in the control zone 206. In some implementations, a portion of a control zone may be partitioned behind a firewall. In the present example, the high-level controls 260, 262, and 264 can be partitioned from different portions of the control zone 206 (e.g., portions including different supervisory controls and low-level controls) by the firewalls 258a and 258b.
The security agent 402, for example, can include various components (e.g., software modules, objects, libraries, etc.) including a group management component 410, a security information distribution component 412, a bootstrapping management component 414, and a defense component 416. In general, the components 410, 412, 414, and 416 may relate to providing functionality for groups of devices and/or providing functionality at a network level. The group management component 410, for example, can be used to add or remove emulated devices from the security agent 402, and can provide access to device groups. The security information distribution component 412, for example, can be used to provide security information (e.g., keys and/or passwords) to devices or device groups. The bootstrapping management component 414, for example, can be used to provide initial configurations for controller devices when the devices boot up. The defense component 416, for example, can be used to provide intrusion detection based on network traffic.
The emulated device 404, for example, can include a device profile 420 and a device security component 422. The device profile 420, for example, can include information related to security capabilities that are provided by its corresponding controller device. The device security component 422, for example, can provide functions related to access control (e.g., providing access to users), authentication (e.g., validating passwords from authorized users, for human-to-device and device-to-device communication), bootstrapping management, host-based intrusion, device-specific content inspection (e.g., for analyzing packet content), software patching, and other aspects of cyber security.
In general, to create a device profile for an emulated device, various automated or semi-automated techniques may be employed. Referring to
In some implementations, penetration testing and/or network monitoring techniques may be used to create device profiles. For example, passive network monitoring techniques may be used to determine whether a particular controller device encrypts its network communications or does not encrypt its communications. As another example, penetration testing techniques may be used to attempt a connection with a controller device's network services, and a determination can be made of whether the controller device requests for user credentials or does not request for credentials. Such penetration testing and/or network monitoring techniques may be employed independently of accessing a device's specifications, for example, and may be automated using software security products.
In general, the security relay 528 may be implemented in hardware and/or software, and may be used to handle communications between the site security server 524 and the controller device 526, and may be used to provide security services (e.g., authentication and encryption/decryption) for controller devices which require such services. To provide security services, for example, the security relay 528 can access and/or execute one or more components (e.g., software modules, objects, libraries, etc.). For example, the emulated device 504 may be associated with an encryption component 540 and a decryption component 542. The encryption component 540, for example, can be used by the security relay 528 to encrypt traffic to the site security server 528 for a controller device without cryptographic capability (e.g., the controller device 526), whereas the decryption component 542, for example, can be used by the security relay 528 to decrypt traffic from the site security server 524 for the controller device.
In some implementations, corresponding emulated devices may be maintained by a site security server and a corresponding security relay for handling secure communications between the site security server and the security relay. For example, the site security server 524 and the security relay 528 can each maintain instances of the emulated device 504 corresponding to the controller device 526. As another example, the site security server 524 and the security relay 528 can each maintain lists of controller devices which require security services (e.g., encryption/decryption services). The site security server 524 and the security relay 528, for example, can use a shared cryptographic key, and can use key negotiation protocols to periodically change the shared key. When either the site security server 524 or the security relay 528 sends a message to the other on behalf of a controller device that requires security services (e.g., a device that is incapable of encryption/decryption), for example, the message may be encrypted using the shared key, whereas the message may not be encrypted when it is to be sent to a controller device that does not require security services (e.g., a device that is capable of encryption/decryption). After receiving a cleartext message from a controller device that is incapable of encryption/decryption, for example, the security relay 528 can encrypt the message with the shared key and send the encrypted message to the site security server 524. After receiving an encrypted message from the site security server 524 for a controller device that is incapable of encryption/decryption, for example, the security relay 528 can decrypt the message and send the cleartext message to the controller device.
A user can be authenticated (602). Referring to
A request for information can be received from the user (604). For example, the user can employ the interface device 222 to request information about a particular controller device in the control zone 206, or may request information related to a group of devices. In the present example, the user requests information related to the production activity of a group of controller devices (e.g., the devices 250a and 252a) in the control zone 206. The request for information can be provided by the site security server 224 to the device(s) that pertain to the request. Communications between the site security server 224 and devices in the control zone 206 can pass through the firewall 240, for example.
A query corresponding to the request for information can be created (606). For example, the site security server 224 can parse the request for information received from the user, can sanitize the parsed request (e.g., to prevent restricted actions), and can translate the request into a query format that is recognizable by its intended recipient (e.g., each of the controller devices 250a and 252a). In general, sanitizing a request may include examining content associated with the request, determining that the request is of a valid format, and determining that parameters and payloads associated with the request are valid.
The query can be encrypted (608). Referring to
The encrypted query may be decrypted (610), depending on whether its intended recipient requires security services. Referring to
The query can be provided to a controller device (612). Referring again to
Information can be received from the controller device (614). For example, the security relay 228 may receive unencrypted information from the controller device 250a (e.g., a security incapable device) and may receive encrypted information from the controller device 252a (e.g., a security capable device). Referring to
The information can be aggregated and normalized (616). For example, the site security server 224 can aggregate and normalize the information from each of the controller devices 250a and 252a, for example, by collecting information from different sources and organizing the information.
The information can be provided to the user (618). For example, the site security server 224 can provide the aggregated and normalized information to the management server 214 for presentation to the requesting user through the interface device 212.
Embodiments of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, in tangibly-embodied computer software or firmware, in computer hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a tangible non-transitory program carrier for execution by, or to control the operation of, data processing apparatus. Alternatively or in addition, the program instructions can be encoded on an artificially-generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. The computer storage medium can be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of them.
The term “data processing apparatus” refers to data processing hardware and encompasses all kinds of apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can also be or further include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). The apparatus can optionally include, in addition to hardware, code that creates an execution environment for computer programs, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.
A computer program, which may also be referred to or described as a program, software, a software application, a module, a software module, a script, or code, can be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data, e.g., one or more scripts stored in a markup language document, in a single file dedicated to the program in question, or in multiple coordinated files, e.g., files that store one or more modules, sub-programs, or portions of code. A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
The processes and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
Computers suitable for the execution of a computer program include, by way of example, general or special purpose microprocessors or both, or any other kind of central processing unit. Generally, a central processing unit will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a central processing unit for performing or executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device, e.g., a universal serial bus (USB) flash drive, to name just a few.
Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
To provide for interaction with a user, embodiments of the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user; for example, by sending web pages to a web browser on a user's device in response to requests received from the web browser.
Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.
The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In some embodiments, a server transmits data, e.g., an HTML page, to a user device, e.g., for purposes of displaying data to and receiving user input from a user interacting with the user device, which acts as a client. Data generated at the user device, e.g., a result of the user interaction, can be received from the user device at the server.
An example of one such type of computer is shown in
The memory 720 stores information within the system 700. In one implementation, the memory 720 is a computer-readable medium. In one implementation, the memory 720 is a volatile memory unit. In another implementation, the memory 720 is a non-volatile memory unit.
The storage device 730 is capable of providing mass storage for the system 700. In one implementation, the storage device 730 is a computer-readable medium. In various different implementations, the storage device 730 may be a floppy disk device, a hard disk device, an optical disk device, or a tape device.
The input/output device 740 provides input/output operations for the system 700. In one implementation, the input/output device 740 includes a keyboard and/or pointing device. In another implementation, the input/output device 740 includes a display unit for displaying graphical user interfaces.
While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any invention or on the scope of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system modules and components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
Particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results. As one example, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous.
This application is a continuation (and claims the benefit of priority under 35 USC 120) of U.S. application Ser. No. 14/839,331, filed Aug. 28, 2015, titled “INDUSTRIAL SECURITY AGENT PLATFORM,” which claims benefit of U.S. Provisional Patent Application No. 62/054,181, filed Sep. 23, 2014, and titled “INDUSTRIAL SECURITY AGENT PLATFORM,” both of which are hereby incorporated by reference in their entirety.
| Number | Date | Country | |
|---|---|---|---|
| 62054181 | Sep 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14839331 | Aug 2015 | US |
| Child | 15822824 | US |
