Authentication between industrial elements in an industrial control system

CROSS-REFERENCE TO RELATED APPLICATIONS

0001The present application is a continuation-in-part of International Application No. PCT/US2013/053721, filed Aug. 6, 2013, and titled, “SECURE INDUSTRIAL CONTROL SYSTEM.” The present application is also a continuation-in-part under 35 U.S.C. §120 of U.S. patent application Ser. No. 14/469,931, filed Aug. 27, 2014, and titled “SECURE INDUSTRIAL CONTROL SYSTEM.” The present application is also a continuation-in-part under 35 U.S.C. §120 of U.S. patent application Ser. No. 14/446,412, filed Jul. 30, 2014, and titled “INDUSTRIAL CONTROL SYSTEM CABLE,” which claims priority under 35 U.S.C. §119(e) of U.S. Provisional Application Ser. No. 62/021,438, filed Jul. 7, 2014, and titled “INDUSTRIAL CONTROL SYSTEM CABLE.” U.S. Provisional Application Ser. No. 62/021,438; U.S. patent application Ser. Nos. 14/446,412 and 14/469,931; and International Application No. PCT/US2013/053721 are herein incorporated by reference in their entireties.

BACKGROUND

0002Industrial control systems, such as standard industrial control systems (ICS) or programmable automation controllers (PAC), include various types of control equipment used in industrial production, such as supervisory control and data acquisition (SCADA) systems, distributed control systems (DCS), programmable logic controllers (PLC), and industrial safety systems certified to safety standards such as IEC 1508. These systems are used in industries including electrical, water and wastewater, oil and gas production and refining, chemical, food, pharmaceuticals and robotics. Using information collected from various types of sensors to measure process variables, automated and/or operator-driven supervisory commands from the industrial control system can be transmitted to various actuator devices such as control valves, hydraulic actuators, magnetic actuators, electrical switches, motors, solenoids, and the like. These actuator devices collect data from sensors and sensor systems, open and close valves and breakers, regulate valves and motors, monitor the industrial process for alarm conditions, and so forth.

0003In other examples, SCADA systems can use open-loop control with process sites that may be widely separated geographically. These systems use Remote Terminal Units (RTUs) to send supervisory data to one or more control centers. SCADA applications that deploy RTU's include fluid pipelines, electrical distribution and large communication systems. DCS systems are generally used for real-time data collection and continuous control with high-bandwidth, low-latency data networks and are used in large campus industrial process plants, such as oil and gas, refining, chemical, pharmaceutical, food and beverage, water and wastewater, pulp and paper, utility power, and mining and metals. PLCs more typically provide Boolean and sequential logic operations, and timers, as well as continuous control and are often used in stand-alone machinery and robotics. Further, ICE and PAC systems can be used in facility processes for buildings, airports, ships, space stations, and the like (e.g., to monitor and control Heating, Ventilation, and Air Conditioning (HVAC) equipment and energy consumption). As industrial control systems evolve, new technologies are combining aspects of these various types of control systems. For instance, PACs can include aspects of SCADA, DCS, and PLCs.

SUMMARY

0004According to various embodiments of this disclosure, a secure industrial control system includes one or more industrial elements and a set of redundant communications/control modules that drive the one or more industrial elements. The set of redundant communications/control modules includes at least a first communications/control module and a second communications/control module. The first and second communications/control modules are configured to perform an authentication sequence (sometimes referred to as a “handshake”) including the operations of: transmitting a request datagram from the first communications/control module to the second communications/control module, the request datagram including a first nonce, a first device authentication key certificate, and a first identity attribute certificate; transmitting a response datagram from the second communications/control module to the first communications/control module, the response datagram including a second nonce, a first signature associated with the first and second nonces, a second device authentication key certificate, and a second identity attribute certificate; and transmitting an authentication datagram from the first communications/control module to the second communications/control module when the response datagram is valid, the authentication datagram including a second signature associated with the first and second nonces.

0005In some embodiments, each communications/control module performs an authentication sequence. Requiring redundant elements to authenticate one another can prevent events that degrade system security. For example, authentication by one or more peer communications/control modules may prevent counterfeit or hacked communications/control modules being maliciously or unintentionally introduced into the system. Should the first communications/control module and the second communications/control module fail to complete the authentication sequence, the newly introduced device and/or both devices can be partially or completely disabled to prevent a security breach or other harm resulting therefrom (e.g., manufacturing defects, deviated control parameters, malicious interference, data loss/corruption, and so forth).

0006The first communications/control module includes at least one processor and a non-transitory medium bearing a set of instructions executable by the processor. The set of instructions includes instructions to: send a request datagram to the second communications/control module, the request datagram including a first nonce, a first device authentication key certificate, and a first identity attribute certificate; receive a response datagram from the second communications/control module, the response datagram including a second nonce, a first signature associated with the first and second nonces, a second device authentication key certificate, and a second identity attribute certificate; and send an authentication datagram to the second communications/control module when the response datagram is valid, the authentication datagram including a second signature associated with the first and second nonces.

0007The second communications/control module includes at least one processor and a non-transitory medium bearing a set of instructions executable by the processor. The set of instructions includes instructions to: receive a request datagram from the first communications/control module, the request datagram including a first nonce, a first device authentication key certificate, and a first identity attribute certificate; and send a response datagram to the first communications/control module when the request datagram is valid, the response datagram including a second nonce, a first signature associated with the first and second nonces, a second device authentication key certificate, and a second identity attribute certificate. The second communications/control module can be further configured to: receive an authentication datagram from the first communications/control module, the authentication datagram including a second signature associated with the first and second nonces; and send a responsive authentication datagram to the first communications/control module, the responsive authentication datagram including a signature associated with the first nonce and a success or failure message.

0008This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. (This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.)

DRAWINGS

0009The Detailed Description is described with reference to the accompanying figures. The use of the same reference numbers in different instances in the description and the figures may indicate similar or identical items.

0010<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram illustrating an industrial control system including a set of redundant communications/control modules in accordance with example embodiments of the present disclosure.

0011<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram illustrating a first communications/control module performing an authentication sequence with a second communications/control module in accordance with example embodiments of the present disclosure.

0012<figref idref="DRAWINGS">FIG. 3</figref> is a block diagram illustrating a communications/control module in accordance with example embodiments of the present disclosure.

0013<figref idref="DRAWINGS">FIG. 4</figref> is a flow diagram illustrating an authentication sequence performed by a first communications/control module authenticating with a second communications/control module in accordance with example embodiments of the present disclosure.

0014<figref idref="DRAWINGS">FIG. 5</figref> is a flow diagram illustrating a responsive authentication sequence performed by a second communications/control module in response to an authentication sequence (e.g., as illustrated in <figref idref="DRAWINGS">FIG. 4</figref>) performed by a first communications/control module in accordance with example embodiments of the present disclosure.

DETAILED DESCRIPTION

0015Overview

0016In industrial control systems, various industrial elements/subsystems (e.g., input/output (I/O) modules, power modules, process sensors and/or actuators, switches, workstations, and/or physical interconnect devices) are controlled or driven by control elements/subsystems (e.g., communications/control modules). Two or more communications/control modules can operate in parallel and/or in a “master-slave” configuration to achieve enhanced throughput and/or redundancy (i.e., one control module takes over when the other one fails). In cases where a control subsystem includes two or more redundant communications/control modules, the industrial control system can be more vulnerable to counterfeit, hacked, or otherwise unauthorized (e.g., non-OEM) communications/control modules being introduced, particularly where a handoff occurs between a primary “master” communications/control module to a secondary “slave” communications/control module. For example, the master may unknowingly handoff control to an unauthorized slave during a failure or overload event. This can lead to degraded security and/or performance from manufacturing defects, deviated control parameters, malicious interference, data loss/corruption, and so forth.

0017The present disclosure is directed to industrial control system communications/control modules, subsystems and techniques for preventing unauthorized devices from being introduced into an industrial control system. In implementations, two or more redundant communications/control modules (e.g., a first communications/control module and a second communications/control module) are configured to perform an authentication sequence (sometimes referred to as a “handshake”) when a new communications/control module is installed, at startup/reset, periodically, at scheduled times, and/or other predefined events. When the redundant communications/control modules fail to authenticate one another, at least one of the communications/control modules (e.g., the unauthenticated communications/control module) can be partially or completely disabled and/or restricted from communicating with other devices.

0018Example Implementations

0019<figref idref="DRAWINGS">FIG. 1</figref> illustrates an industrial control system <b>100</b> in accordance with an example embodiment of the present disclosure. In embodiments, the industrial control system <b>100</b> may comprise an industrial control system (ICS), a programmable automation controller (PAC), a supervisory control and data acquisition (SCADA) system, a distributed control system (DCS), programmable logic controller (PLC), and industrial safety system certified to safety standards such as IEC 1508, or the like. As shown in <figref idref="DRAWINGS">FIG. 1</figref>, the industrial control system <b>100</b> includes one or more industrial elements (e.g., input/output modules, power modules, sensors, actuators, switches, workstations, and/or physical interconnect devices) that are controlled or driven by one or more control elements or subsystems <b>102</b> distributed throughout the system. In some embodiments, a control element or subsystem <b>102</b> includes a set of redundant communications/control modules <b>106</b>, where the communications/control modules <b>106</b> are enabled to operate in parallel and/or takeover control for one another in case of a failure/overload event. For example, one or more I/O modules <b>104</b> may be connected to a set of redundant communications/control modules <b>106</b> making up the control element/subsystem <b>102</b>. The industrial control system <b>100</b> is configured to transmit data to and from the I/O modules <b>104</b>. The I/O modules <b>104</b> can comprise input modules, output modules, and/or input and output modules. For instance, input modules can be used to receive information from input devices <b>130</b> (e.g., sensors) in the process, while output modules can be used to transmit instructions to output devices (e.g., actuators). For example, an I/O module <b>104</b> can be connected to a process sensor for measuring pressure in piping for a gas plant, a refinery, and so forth and/or connected to a process actuator for controlling a valve, binary or multiple state switch, transmitter, or the like. Field devices <b>130</b> are communicatively coupled with the IO modules <b>104</b> either directly or via network connections. These devices <b>130</b> can include control valves, hydraulic actuators, magnetic actuators, motors, solenoids, electrical switches, transmitters, input sensors/receivers (e.g., illumination, radiation, gas, temperature, electrical, magnetic, and/or acoustic sensors) communications sub-busses, and the like.

0020In implementations, the I/O modules <b>104</b> can be used the industrial control system <b>100</b> collect data in applications including, but not necessarily limited to critical infrastructure and/or industrial processes, such as product manufacturing and fabrication, utility power generation, oil, gas, and chemical refining; pharmaceuticals, food and beverage, pulp and paper, metals and mining and facility and large campus industrial processes for buildings, airports, ships, and space stations (e.g., to monitor and control Heating, Ventilation, and Air Conditioning (HVAC) equipment and energy consumption).

0021In implementations, an I/O module <b>104</b> can be configured to convert analog data received from the sensor to digital data (e.g., using Analog-to-Digital Converter (ADC) circuitry, and so forth). An I/O module <b>104</b> can also be connected to one or more process actuators such as a motor or a regulating valve or an electrical relay and other forms of actuators and configured to control one or more operating characteristics of the motor, such as motor speed, motor torque, or position of the regulating valve or state of the electrical relay and so forth. Further, the I/O module <b>104</b> can be configured to convert digital data to analog data for transmission to the actuator (e.g., using Digital-to-Analog (DAC) circuitry, and so forth). In implementations, one or more of the I/O modules <b>104</b> can comprise a communications module configured for communicating via a communications sub-bus, such as an Ethernet bus, an H1 field bus, a Process Field Bus (PROFIBUS), a Highway Addressable Remote Transducer (HART) bus, a Modbus, and so forth. Further, two or more I/O modules <b>104</b> can be used to provide fault tolerant and redundant connections for various field devices <b>130</b> such as control valves, hydraulic actuators, magnetic actuators, motors, solenoids, electrical switches, transmitters, input sensors/receivers (e.g., illumination, radiation, gas, temperature, electrical, magnetic, and/or acoustic sensors) communications sub-busses, and the like.

0022Each I/O module <b>104</b> can be provided with a unique identifier (ID) for distinguishing one I/O module <b>104</b> from another I/O module <b>104</b>. In implementations, an I/O module <b>104</b> is identified by its ID when it is connected to the industrial control system <b>100</b>. Multiple I/O modules <b>104</b> can be used with the industrial control <b>100</b> to provide redundancy. For example, two or more I/O modules <b>104</b> can be connected to a process sensor and/or actuator. Each I/O module <b>104</b> can include one or more ports that furnish a physical connection to hardware and circuitry included with the I/O module <b>104</b>, such as a printed circuit board (PCB), and so forth. For example, each I/O module <b>104</b> includes a connection for a cable that connects the cable to a printed wiring board (PWB) in the I/O module <b>104</b>.

0023One or more of the I/O modules <b>104</b> can include an interface for connecting to other networks including, but not necessarily limited to: a wide-area cellular telephone network, such as a 3G cellular network, a 4G cellular network, or a Global System for Mobile communications (GSM) network; a wireless computer communications network, such as a Wi-Fi network (e.g., a Wireless LAN (WLAN) operated using IEEE 802.11 network standards); a Personal Area Network (PAN) (e.g., a Wireless PAN (WPAN) operated using IEEE 802.15 network standards); a Wide Area Network (WAN); an intranet; an extranet; an internet; the Internet; and so on. Further, one or more of the I/O modules <b>104</b> can include a connection for connecting an I/O module <b>104</b> to a computer bus, and so forth.

0024The communications/control module <b>106</b> can be used to monitor and control the I/O modules <b>104</b>, and to connect two or more I/O modules <b>104</b> together. In embodiments of the disclosure, a communications/control module <b>106</b> can update a routing table when an I/O module <b>104</b> is connected to the industrial control system <b>100</b> based upon a unique ID for the I/O module <b>104</b>. Further, when multiple redundant I/O modules <b>104</b> are used, each communications/control module <b>106</b> can implement mirroring of informational databases regarding the I/O modules <b>104</b> and update them as data is received from and/or transmitted to the I/O modules <b>104</b>. As discussed above, two or more communications/control modules <b>106</b> are used to provide redundancy. The communications/control modules <b>106</b> are configured to perform an authentication sequence or handshake to authenticate one another at predefined events or times including such as startup, reset, installation of a new communications/control module <b>106</b>, replacement of a communications/control module <b>106</b>, periodically, scheduled times, and the like.

0025<figref idref="DRAWINGS">FIG. 2</figref> shows exemplary datagrams <b>200</b> transmitted between a first communications/control module <b>106</b>A and a second communications/control module <b>106</b>B in performance of the authentication sequence. To initiate the authentication sequence, the first communications/control module <b>106</b>A is configured to transmit a request datagram <b>202</b> to the second communications/control module <b>106</b>B. In implementations, the request datagram <b>202</b> includes a first plain text nonce (NonceA), a first device authentication key certificate (CertDAKA) containing a first device authentication key (DAKA), and a first identity attribute certificate (IACA). In some embodiments, the first communications/control module <b>106</b>A is configured to generate the first nonce (NonceA) with a true random number generator (hereinafter “TRNG”) and concatenate or otherwise combine the first nonce (NonceA), the first device authentication key certificate (CertDAKA), and the first identity attribute certificate (IACA) to generate the request datagram <b>202</b>. In some embodiments, the first device authentication key certificate (CertDAKA) and the first identity attribute certificate (IACA) are locally stored by the first communications/control module <b>106</b>A. For example, the certificates may be stored in a local memory (e.g., ROM, RAM, flash memory, or other non-transitory storage medium) of the first communications/control module <b>106</b>A.

0026The second communications/control module <b>106</b>B is configured to validate the request datagram by verifying the first device authentication key certificate (CertDAKA) and the first identity attribute certificate (IACA) with public keys that are generated by a device lifecycle management system (DLM) or derived utilizing crypto library functions. In this regard, the public keys may be stored in SRAM or another local memory of the communications/control module <b>106</b> and used with crypto library functions to verify or cryptographically sign exchanged data, such as the nonces exchanged between the communications/control modules <b>106</b>. In some embodiments, the second communications/control module <b>106</b>B may verify the certificates with an elliptic curve digital signing algorithm (hereinafter “ECDSA”) or other verification operation. In some embodiments, the second communications/control module <b>106</b>B may be further configured to validate the certificate values from plain text values by verifying the following: certificate type is device authentication key (hereinafter “DAK”) or identity attribute certificate (hereinafter “IAC”) for each certificate; IAC names match, DAK certificate module type matches module type argument; and/or microprocessor serial number (hereinafter “MPSN”) of each certificate in the message payload match each other. In some embodiments, the second communications/control module <b>106</b>B may be further configured to verify the DAK and IAC certificates are not in a local revocation list (e.g., a list or database including revoked and/or invalid certificates). When the second communications/control module <b>106</b>B fails to validate the request datagram, the second communications/control module <b>106</b>B may generate an error message, partially or completely disable the first communications/control module <b>106</b>A, and/or discontinue or restrict communications to/from the first communications/control module <b>106</b>A.

0027Responsive to a valid request datagram <b>202</b>, the second communications/control module <b>106</b>B is configured to transmit a response datagram <b>204</b> to the first communications/control module <b>106</b>A. In implementations, the response datagram <b>204</b> includes a second plain text nonce (NonceB), a first signature associated with the first and second nonces (SigB[NonceA∥NonceB]), a second device authentication key certificate (certDAKB) containing a second device authentication key (DAKB), and a second identity attribute certificate (IACB). In some embodiments, the second communications/control module <b>106</b>B is configured to generate the second nonce (NonceB) with a TRNG, concatenate or otherwise combine the first nonce (NonceA) and the second nonce (NonceB), and sign the concatenated/combined nonces with a private key (e.g., DAK) that is locally stored by the second communications/control module <b>106</b>B. The second communications/control module <b>106</b>B is further configured to concatenate or otherwise combine the second nonce (NonceB), the first signature associated with the first and second nonces (SigB[NonceA∥NonceB]), the second device authentication key certificate (certDAKB), and the second identity attribute certificate (IACB) to generate the response datagram <b>204</b>. In some embodiments, the second device authentication key certificate (CertDAKB) and the second identity attribute certificate (IACB) are locally stored by the second communications/control module <b>106</b>B. For example, the certificates may be stored in a local memory (e.g., ROM, RAM, flash memory, or other non-transitory storage medium) of the second communications/control module <b>106</b>B.

0028The first communications/control module <b>106</b>A is configured to validate the response datagram by verifying the second device authentication key certificate (CertDAKB) and the second identity attribute certificate (IACB) with public keys that are locally stored or retrieved from a crypto library utilizing ECDSA or another verification operation. In some embodiments, the first communications/control module <b>106</b>A may be further configured to validate the certificate values from plain text values by verifying the following: IAC &amp; DAK certificates have matching MPSNs, IAC names match, certificate types are correct on both certificates (IAC &amp; DAK), the correct issuer name is on both certificates, DAK module type is the correct type (e.g., check to see if module type=communications/control module). In some embodiments, the first communications/control module <b>106</b>A may be further configured to verify the DAK and IAC certificates are not in a local revocation list.

0029To validate the response datagram, the first communications/control module <b>106</b>A is further configured to verify the first signature associated with the first and second nonces (sigB[NonceA∥NonceB]). In some embodiments, the first communications/control module <b>106</b>A is configured to verify the first signature (sigB[NonceA∥Nonce B]) by concatenating the first locally stored nonce (NonceA) and the second plaintext nonce (NonceB) received from the second communications/control module <b>106</b>B, verfying the first cryptographic signature (sigB[NonceA∥NonceB]) with a public device authentication key (e.g., using DAKB from certDAKB), and comparing the locally generated concatenation of the first nonce and the second nonce with the cryptographically verified concatenation of the first nonce and the second nonce. When the first communications/control module <b>106</b>A fails to validate the response datagram, the first communications/control module <b>106</b>A may generate an error message, partially or completely disable the second communications/control module <b>106</b>B, and/or discontinue or restrict communications to/from the second communications/control module <b>106</b>B.

0030The first communications/control module <b>106</b>A is further configured to transmit an authentication datagram <b>206</b> to the second communications/control module <b>106</b>B when the response datagram <b>204</b> is valid. In implementations, the authentication datagram <b>206</b> includes a second signature associated with the first and second nonces (sigA[NonceA∥Nonce B]). In some embodiments, the first communications/control module <b>106</b>A is configured to sign the locally generated concatenation of the first and second nonces a private key (e.g., DAK) that is locally stored by the first communications/control module <b>106</b>A. When the response datagram is invalid, the authentication datagram <b>206</b> may be replaced with a “failed” authentication datagram <b>206</b> including a signature associated with the second nonce and an error reporting (e.g., “failure”) message (sigA[NonceB∥Error ]) generated by the first communications/control module <b>106</b>A.

0031Responsive to the authentication datagram <b>206</b>, the second communications/control module <b>106</b>B may be further configured to transmit a responsive authentication datagram <b>208</b> to the first communications/control module <b>106</b>A. In implementations, the responsive authentication datagram <b>208</b> includes a signature associated with the first nonce and an error reporting (e.g., “success” or “failure”) message (sigB[NonceA∥Error]) generated by the second communications/control module <b>106</b>B. In some embodiments, the second communications/control module <b>106</b>B is configured to validate the authentication datagram <b>206</b> by verifying the second signature associated with the first and second nonces (sigA[NonceA∥NonceB]). In some embodiments, the second communications/control module <b>106</b>B is configured to verify the second signature (sigA[NonceA∥NonceB]) by concatenating the first plaintext nonce (NonceA) received from the first communications/control module <b>106</b>A and the second locally stored nonce (NonceB), verifying the second cryptographic signature (sigA[NonceA∥NonceB]) with a public device authentication key (e.g., using DAKA from certDAKA), and comparing the locally generated concatenation of the first nonce and the second nonce with the cryptographically verified concatenation of the first nonce and the second nonce. In addition to the error reporting message, when the second communications/control module <b>106</b>B fails to validate the authentication datagram, the second communications/control module <b>106</b>B may partially or completely disable the first communications/control module <b>106</b>A, and/or discontinue or restrict communications to/from the first communications/control module <b>106</b>A.

0032In implementations where the communications/control modules <b>106</b> are arranged according to a “master-slave” configuration, the master (e.g., the first communications/control module <b>106</b>A) may be configured to authenticate each slave. In the event of a failed authentication, the master may at least partially disable or restrict communications to/from the unauthenticated slave. Alternatively, two or more slave communications/control modules <b>106</b> and/or two or more communications/control modules <b>106</b> operating in parallel without a master may authenticate one another. A failed authentication may result in both devices or a pseudo-secondary device (e.g., non-initiating communications/control module) being partially or completely disabled. For example, two or more redundant communications/control modules <b>106</b> can be disabled should they fail to successfully complete the authentication sequence at startup or another predefined time/event.

0033Each communications/control module <b>106</b> may include circuitry and/or logic enabled to perform the functions described herein. As shown in <figref idref="DRAWINGS">FIG. 3</figref>, embodiments of the communications/control module <b>106</b> include a controller <b>300</b> having at least one processor <b>302</b> configured to execute program instruction <b>306</b> stored permanently, semi-permanently, or temporarily by a non-transitory machine readable medium <b>304</b> such as a hard disk drive (HDD), solid-state disk (SDD), optical disk, magnetic storage device, flash drive, or the like. For example, each communications/control module <b>106</b> may include a controller <b>300</b> configured to carry out an authentication initiator sequence <b>400</b> and/or an authentication responder sequence <b>500</b> illustrated in <figref idref="DRAWINGS">FIGS. 4 and 5</figref>, respectively.

0034Referring to <figref idref="DRAWINGS">FIG. 4</figref>, the authentication initiator sequence <b>400</b> implemented by the first communications/control module <b>106</b>A (i.e., the initiator) includes: (<b>402</b>) sending a request datagram to a second communications/control module <b>106</b>B (i.e. the responder), the request datagram including a first nonce, a first device authentication key certificate, and a first identity attribute certificate; (<b>404</b>) receiving a response datagram from the second communications/control module <b>106</b>B, the response datagram including a second nonce, a first signature associated with the first and second nonces, a second device authentication key certificate, and a second identity attribute certificate; (<b>406</b>) validating the response datagram by verifying the first signature associated with the first and second nonces, the second device authentication key certificate, and the second identity attribute certificate; and (<b>410</b>) sending an authentication datagram to the second communications/control module <b>106</b>B when the response datagram is valid, the authentication datagram including a second signature associated with the first and second nonces; or (<b>408</b>) sending a failed authentication datagram to the second communications/control module <b>106</b>B when the response datagram is invalid, the failed authentication datagram including a signature associated with the second nonce and an error message.

0035Referring to <figref idref="DRAWINGS">FIG. 5</figref>, the authentication responder sequence <b>500</b> implemented by the second communications/control module <b>106</b>B includes: (<b>502</b>) receiving a request datagram from the first communications/control module <b>106</b>A, the request datagram including a first nonce, a first device authentication key certificate, and a first identity attribute certificate; (<b>504</b>) validating the request datagram by verifying the first device authentication key certificate and the first identity attribute certificate; (<b>506</b>) sending a response datagram to the first communications/control module <b>106</b>A when the request datagram is valid, the response datagram including a second nonce, a first signature associated with the first and second nonces, a second device authentication key certificate, and a second identity attribute certificate; (<b>508</b>) receiving an authentication datagram from the first communications/control module <b>106</b>A, the authentication datagram including a second signature associated with the first and second nonces; (<b>510</b>) validating the authentication datagram by verifying the second signature associated with the first and second nonces; and (<b>512</b>) sending a responsive authentication datagram to the first communications/control module <b>106</b>A, the responsive authentication datagram including a signature associated with the first nonce and a success or failure message.

0036In some embodiments, other elements of the industrial control system <b>100</b>, such as I/O modules <b>104</b>, field devices <b>130</b> (e.g. sensors or actuators), power modules <b>112</b>, physical interconnect devices, switches, and so forth, can be configured to authenticate one another by performing a sequence or handshake such as the authentication sequence (between redundant communications/control modules) described above. For example, a first I/O module <b>104</b> and a second I/O module <b>104</b> can be configured to perform the authentication functions or operations carried out by the first communications/control module <b>106</b>A and the second communications/control module <b>106</b>B, respectively, to complete an authentication sequence with one another.

0037Referring again to <figref idref="DRAWINGS">FIG. 1</figref>, data transmitted by the industrial control system <b>100</b> can be packetized, i.e., discrete portions of the data can be converted into data packets comprising the data portions along with network control information, and so forth. The industrial control system <b>100</b> can use one or more protocols for data transmission, including a bit-oriented synchronous data link layer protocol such as High-Level Data Link Control (HDLC). In some embodiments, the industrial control system <b>100</b> implements HDLC according to an International Organization for Standardization (ISO) 13239standard, or the like. Further, two or more control modules <b>106</b> can be used to implement redundant HDLC. However, it should be noted that HDLC is provided by way of example only and is not meant to be restrictive of the present disclosure. Thus, the industrial control system <b>100</b> can use other various communications protocols in accordance with the present disclosure.

0038One or more of the communications/control module <b>106</b> can be configured for exchanging information with components used for monitoring and/or controlling the field devices <b>130</b> (e.g., sensor and/or actuator instrumentation) connected to the industrial control system <b>100</b> via the I/O modules <b>104</b>, such as one or more control loop feedback mechanisms/controllers. In implementations, a controller can be configured as a microcontroller/Programmable Logic Controller (PLC), a Proportional-Integral-Derivative (PID) controller, and so forth. In some embodiments, the I/O modules <b>104</b> and the communications/control modules <b>106</b> include network interfaces, e.g., for connecting one or more I/O modules <b>104</b> to one or more controllers via a network. In implementations, a network interface can be configured as a Gigabit Ethernet interface for connecting the I/O modules <b>104</b> to a Local Area Network (LAN). Further, two or more communications/control modules <b>106</b> can be used to implement redundant Gigabit Ethernet. However, it should be noted that Gigabit Ethernet is provided by way of example only and is not meant to be restrictive of the present disclosure. Thus, a network interface can be configured for connecting the communications/control modules <b>106</b> to other various networks including, but not necessarily limited to: a wide-area cellular telephone network, such as a 3G cellular network, a 4G cellular network, or a GSM network; a wireless computer communications network, such as a Wi-Fi network (e.g., a WLAN operated using IEEE 802.11 network standards); a PAN (e.g., a WPAN operated using IEEE 802.15 network standards); a WAN; an intranet; an extranet; an internet; the Internet; and so on. Additionally, a network interface can be implemented using a computer bus. For example, a network interface can include a Peripheral Component Interconnect (PCI) card interface, such as a Mini PCI interface, and so forth. Further, the network can be configured to include a single network or multiple networks across different access points.

0039The industrial control system <b>100</b> can receive electrical power from multiple sources. For example, AC power is supplied from a power grid <b>108</b> (e.g., using high voltage power from AC mains). AC power can also be supplied using local power generation (e.g., an on-site turbine or diesel local power generator <b>110</b>). A power supply <b>112</b> is used to distribute electrical power from the power grid <b>108</b> to automation equipment of the industrial control system <b>100</b>, such as controllers, I/O modules, and so forth. A power supply <b>112</b> can also be used to distribute electrical power from the local power generator <b>110</b> to the industrial control system equipment. The industrial control system <b>100</b> can also include additional (backup) power supplies configured to store and return DC power using multiple battery modules. For example, a power supply <b>112</b> functions as a UPS. In embodiments of the disclosure, multiple power supplies <b>112</b> can be distributed (e.g., physically decentralized) within the industrial control system <b>100</b>.

0040In some embodiments, the control elements/subsystems and/or industrial elements (e.g., the I/O modules <b>104</b>, the communications/control modules <b>106</b>, the power supplies <b>112</b>, and so forth) are connected together by one or more backplanes <b>114</b>. For example, communications/control modules <b>106</b> can be connected to I/O modules <b>104</b> by a communications backplane <b>116</b>. Further, power supplies <b>112</b> can be connected to I/O modules <b>104</b> and/or to communications/control modules <b>106</b> by a power backplane <b>118</b>. In some embodiments, physical interconnect devices (e.g., switches, connectors, or cables such as, but not limited to, those described in U.S. Non-provisional application Ser. No. 14/446,412) are used to connect to the I/O modules <b>104</b>, the communications/control modules <b>106</b>, the power supplies <b>112</b>, and possibly other industrial control system equipment. For example, a cable can be used to connect a communications/control module <b>106</b> to a network <b>120</b>, another cable can be used to connect a power supply <b>112</b> to a power grid <b>108</b>, another cable can be used to connect a power supply <b>112</b> to a local power generator <b>110</b>, and so forth.

0041In some embodiments, the industrial control system <b>100</b> implements a secure control system. For example, the industrial control system <b>100</b> includes a security credential source (e.g., a factory <b>122</b>) and a security credential implementer (e.g., a key management entity <b>124</b>). The security credential source is configured to generate a unique security credential (e.g., a key, a certificate, etc., such as a unique identifier, and/or a security credential). The security credential implementer is configured to provision the control elements/subsystems and/or industrial elements (e.g., cables, devices <b>130</b>, I/O modules <b>104</b>, communications/control modules <b>106</b>, power supplies <b>112</b>, and so forth) with a unique security credential generated by the security credential source.

0042Multiple (e.g., every) device <b>130</b>, I/O module <b>104</b>, communications/control module <b>106</b>, power supply <b>112</b>, physical interconnect devices, etc., of the industrial control system <b>100</b> can be provisioned with security credentials for providing security at multiple (e.g., all) levels of the industrial control system <b>100</b>. Still further, the control elements/subsystems and/or industrial elements including the sensors and/or actuators and so forth, can be provisioned with the unique security credentials (e.g., keys, certificates, etc.) during manufacture (e.g., at birth), and can be managed from birth by a key management entity <b>124</b> of the industrial control system <b>100</b> for promoting security of the industrial control system <b>100</b>.

0043In some embodiments, communications between the control elements/subsystems and/or industrial elements including the sensors and/or actuators and so forth, of the industrial control system <b>100</b> includes an authentication process. The authentication process can be performed for authenticating control elements/subsystem and/or industrial elements including the sensors and/or actuators and so forth, implemented in the industrial control system <b>100</b>. Further, the authentication process can utilize security credentials associated with the element and/or physical interconnect device for authenticating that element and/or physical interconnect device. For example, the security credentials can include encryption keys, certificates (e.g., public key certificates, digital certificates, identity certificates, security certificates, asymmetric certificates, standard certificates, non-standard certificates) and/or identification numbers.

0044In implementations, multiple control elements/subsystems and/or industrial elements of the industrial control system <b>100</b> are provisioned with their own unique security credentials. For example, each element of the industrial control system <b>100</b> may be provisioned with its own unique set(s) of certificates, encryption keys and/or identification numbers when the element is manufactured (e.g., the individual sets of keys and certificates are defined at the birth of the element). The sets of certificates, encryption keys and/or identification numbers are configured for providing/supporting strong encryption. The encryption keys can be implemented with standard (e.g., commercial off-the-shelf (COTS)) encryption algorithms, such as National Security Agency (NSA) algorithms, National Institute of Standards and Technology (NIST) algorithms, or the like.

0045The cryptographic keys and certificates can be stored in on-chip memory (OCM), for example, in SRAM of a communications/control module <b>106</b>. Additionally, sensitive tasks (e.g., tasks with secret information and sometimes even with public information) may have a stack that executes in OCM. For example, cryptographic tasks may be performed in kernel space or application space from stacks locally stored in OCM.

0046Based upon the results of the authentication process, the element being authenticated can be activated, partial functionality of the element can be enabled or disabled within the industrial control system <b>100</b>, complete functionality of the element can be enabled within the industrial control system <b>100</b>, and/or functionality of the element within the industrial control system <b>100</b> can be completely disabled (e.g., no communication facilitated between that element and other elements of the industrial control system <b>100</b>).

0047In embodiments, the keys, certificates and/or identification numbers associated with an element of the industrial control system <b>100</b> can specify the original equipment manufacturer (OEM) of that element. As used herein, the term “original equipment manufacturer” or “OEM” can be defined as an entity that physically manufactures the device (e.g., element) and/or a supplier of the device such as an entity that purchases the device from a physical manufacturer and sells the device. Thus, in embodiments, a device can be manufactured and distributed (sold) by an OEM that is both the physical manufacturer and the supplier of the device. However, in other embodiments, a device can be distributed by an OEM that is a supplier, but is not the physical manufacturer. In such embodiments, the OEM can cause the device to be manufactured by a physical manufacturer (e.g., the OEM can purchase, contract, order, etc. the device from the physical manufacturer).

0048Additionally, where the OEM comprises a supplier that is not the physical manufacturer of the device, the device can bear the brand of the supplier instead of brand of the physical manufacturer. For example, in embodiments where an element (e.g., a communications/control module <b>106</b>) is associated with a particular OEM that is a supplier but not the physical manufacturer, the element's keys, certificates and/or identification numbers can specify that origin. During authentication of an element of the industrial control system <b>100</b>, when a determination is made that an element being authenticated was manufactured or supplied by an entity that is different than the OEM of one or more other elements of the industrial control system <b>100</b>, then the functionality of that element can be at least partially disabled within the industrial control system <b>100</b>. For example, limitations can be placed upon communication (e.g., data transfer) between that element and other elements of the industrial control system <b>100</b>, such that the element cannot work/function within the industrial control system <b>100</b>. When one of the elements of the industrial control system <b>100</b> requires replacement, this feature can prevent a user of the industrial control system <b>100</b> from unknowingly replacing the element with a non-homogenous element (e.g., an element having a different origin (a different OEM) than the remaining elements of the industrial control system <b>100</b>) and implementing the element in the industrial control system <b>100</b>. In this manner, the techniques described herein can prevent the substitution of elements of other OEM's into a secure industrial control system <b>100</b>. In one example, the substitution of elements that furnish similar functionality in place of elements provided by an originating OEM can be prevented, since the substituted elements cannot authenticate and operate within the originating OEM's system. In another example, a first reseller can be provided with elements having a first set of physical and cryptographic labels by an originating OEM, and the first reseller's elements can be installed in an industrial control system <b>100</b>. In this example, a second reseller can be provided with elements having a second (e.g., different) set of physical and cryptographic labels by the same originating OEM. In this example, the second reseller's elements may be prevented from operating within the industrial control system <b>100</b>, since they may not authenticate and operate with the first reseller's elements. However, it should also be noted that the first reseller and the second reseller may enter into a mutual agreement, where the first and second elements can be configured to authenticate and operate within the same industrial control system <b>100</b>. Further, in some embodiments, an agreement between resellers to allow interoperation can also be implemented so the agreement only applies to a specific customer, group of customers, facility, etc.

0049In another instance, a user can attempt to implement an incorrectly designated (e.g., mismarked) element within the industrial control system <b>100</b>. For example, the mismarked element can have a physical indicia marked upon it which falsely indicates that the element is associated with the same OEM as the OEM of the other elements of the industrial control system <b>100</b>. In such instances, the authentication process implemented by the industrial control system <b>100</b> can cause the user to be alerted that the element is counterfeit. This process can also promote improved security for the industrial control system <b>100</b>, since counterfeit elements are often a vehicle by which malicious software can be introduced into the industrial control system <b>100</b>. In embodiments, the authentication process provides a secure air gap for the industrial control system <b>100</b>, ensuring that the secure industrial control system is physically isolated from insecure networks.

0050In implementations, the secure industrial control system <b>100</b> includes a key management entity <b>124</b>. The key management entity <b>124</b> can be configured for managing cryptographic keys (e.g., encryption keys) in a cryptosystem. This managing of cryptographic keys (e.g., key management) can include the generation, exchange, storage, use, and/or replacement of the keys. For example, the key management entity <b>124</b> is configured to serve as a security credentials source, generating unique security credentials (e.g., public security credentials, secret security credentials) for the elements of the industrial control system <b>100</b>. Key management pertains to keys at the user and/or system level (e.g., either between users or systems).

0051In embodiments, the key management entity <b>124</b> comprises a secure entity such as an entity located in a secure facility. The key management entity <b>124</b> can be remotely located from the I/O modules <b>104</b>, the communications/control modules <b>106</b>, and the network <b>120</b>. For example, a firewall <b>126</b> can separate the key management entity <b>124</b> from the control elements or subsystems <b>102</b> and the network <b>120</b> (e.g., a corporate network). In implementations, the firewall <b>126</b> can be a software and/or hardware-based network security system that controls ingoing and outgoing network traffic by analyzing data packets and determining whether the data packets should be allowed through or not, based on a rule set. The firewall <b>126</b> thus establishes a barrier between a trusted, secure internal network (e.g., the network <b>120</b>) and another network <b>128</b> that is not assumed to be secure and trusted (e.g., a cloud and/or the Internet). In embodiments, the firewall <b>126</b> allows for selective (e.g., secure) communication between the key management entity <b>124</b> and one or more of the control elements or subsystems <b>102</b> and/or the network <b>120</b>. In examples, one or more firewalls can be implemented at various locations within the industrial control system <b>100</b>. For example, firewalls can be integrated into switches and/or workstations of the network <b>120</b>.

0052The secure industrial control system <b>100</b> can further include one or more manufacturing entities (e.g., factories <b>122</b>). The manufacturing entities can be associated with original equipment manufacturers (OEMs) for the elements of the industrial control system <b>100</b>. The key management entity <b>124</b> can be communicatively coupled with the manufacturing entity via a network (e.g., a cloud). In implementations, when the elements of the industrial control system <b>100</b> are being manufactured at one or more manufacturing entities, the key management entity <b>124</b> can be communicatively coupled with (e.g., can have an encrypted communications pipeline to) the elements. The key management entity <b>124</b> can utilize the communications pipeline for provisioning the elements with security credentials (e.g., inserting keys, certificates and/or identification numbers into the elements) at the point of manufacture.

0053Further, when the elements are placed into use (e.g., activated), the key management entity <b>124</b> can be communicatively coupled (e.g., via an encrypted communications pipeline) to each individual element worldwide and can confirm and sign the use of specific code, revoke (e.g., remove) the use of any particular code, and/or enable the use of any particular code. Thus, the key management entity <b>124</b> can communicate with each element at the factory where the element is originally manufactured (e.g., born), such that the element is born with managed keys. A master database and/or table including all encryption keys, certificates and/or identification numbers for each element of the industrial control system <b>100</b> can be maintained by the key management entity <b>124</b>. The key management entity <b>124</b>, through its communication with the elements, is configured for revoking keys, thereby promoting the ability of the authentication mechanism to counter theft and re-use of components.

0054In implementations, the key management entity <b>124</b> can be communicatively coupled with one or more of the control elements/subsystems, industrial elements, and/or the network <b>120</b> via another network (e.g., a cloud and/or the Internet) and firewall. For example, in embodiments, the key management entity <b>124</b> can be a centralized system or a distributed system. Moreover, in embodiments, the key management entity <b>124</b> can be managed locally or remotely. In some implementations, the key management entity <b>124</b> can be located within (e.g., integrated into) the network <b>120</b> and/or the control elements or subsystems <b>102</b>. The key management entity <b>124</b> can provide management and/or can be managed in a variety of ways. For example, the key management entity <b>124</b> can be implemented/managed: by a customer at a central location, by the customer at individual factory locations, by an external third party management company and/or by the customer at different layers of the industrial control system <b>100</b>, and at different locations, depending on the layer.

0055Varying levels of security (e.g., scalable, user-configured amounts of security) can be provided by the authentication process. For example, a base level of security can be provided which authenticates the elements and protects code within the elements. Other layers of security can be added as well. For example, security can be implemented to such a degree that a component, such as the communications/control module <b>106</b>, cannot power up without proper authentication occurring. In implementations, encryption in the code is implemented in the elements, while security credentials (e.g., keys and certificates) are implemented on the elements. Security can be distributed (e.g., flows) through the industrial control system <b>100</b>. For example, security can flow through the industrial control system <b>100</b> all the way to an end user, who knows what a module is designed to control in that instance. In embodiments, the authentication process provides encryption, identification of devices for secure communication and authentication of system hardware or software components (e.g., via digital signature).

0056In implementations, the authentication process can be implemented to provide for and/or enable interoperability within the secure industrial control system <b>100</b> of elements manufactured and/or supplied by different manufacturers/vendors/suppliers (e.g., OEMs). For example, selective (e.g., some) interoperability between elements manufactured and/or supplied by different manufacturers/vendors/suppliers can be enabled. In embodiments, unique security credentials (e.g., keys) implemented during authentication can form a hierarchy, thereby allowing for different functions to be performed by different elements of the industrial control system <b>100</b>.

0057The communication links connecting the components of the industrial control system <b>100</b> can further employ data packets, such as runt packets (e.g., packets smaller than sixty-four (64) bytes), placed (e.g., injected and/or stuffed) therein, providing an added level of security. The use of runt packets increases the level of difficulty with which outside information (e.g., malicious content such as false messages, malware (viruses), data mining applications, etc.) can be injected onto the communications links. For example, runt packets can be injected onto a communication link within gaps between data packets transmitted between a first communications/control module <b>106</b>A and a second communications/control module <b>106</b>B to hinder an external entity's ability to inject malicious content onto the communication link.

0058Generally, any of the functions described herein can be implemented using hardware (e.g., fixed logic circuitry such as integrated circuits), software, firmware, manual processing, or a combination thereof. Thus, the blocks discussed in the above disclosure generally represent hardware (e.g., fixed logic circuitry such as integrated circuits), software, firmware, or a combination thereof. In the instance of a hardware configuration, the various blocks discussed in the above disclosure may be implemented as integrated circuits along with other functionality. Such integrated circuits may include all of the functions of a given block, system, or circuit, or a portion of the functions of the block, system, or circuit. Further, elements of the blocks, systems, or circuits may be implemented across multiple integrated circuits. Such integrated circuits may comprise various integrated circuits, including, but not necessarily limited to: a monolithic integrated circuit, a flip chip integrated circuit, a multichip module integrated circuit, and/or a mixed signal integrated circuit. In the instance of a software implementation, the various blocks discussed in the above disclosure represent executable instructions (e.g., program code) that perform specified tasks when executed on a processor. These executable instructions can be stored in one or more tangible computer readable media. In some such instances, the entire system, block, or circuit may be implemented using its software or firmware equivalent. In other instances, one part of a given system, block, or circuit may be implemented in software or firmware, while other parts are implemented in hardware.

0059Although the subject matter has been described in language specific to structural features and/or process operations, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.