23.03.2017 Views

wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Security in Industrial Communication Systems 22-3<br />

22.2 Planned Approach to Security: Defense in Depth<br />

Security should be a planned process that comprises the complete system. The security policy, also called<br />

security architecture, describes all security measures but also all relevant organizational procedures and<br />

the system environment required to protect a system. It includes the organization’s approach to risk, a<br />

formal statement of rules through which people are given access to the organization’s assets, a definition<br />

of business and security goals, and a description of the implemented security measures.<br />

Security is only 20% technology and 80% organization including personnel, process descriptions, etc.<br />

Relevant areas can be comprehended in the 4 P’s of security: People, Policy, Processes, and Procedures.<br />

The setup and maintenance of a security policy includes the following steps:<br />

1. Asset and risk analysis identifying the values to be protected (e.g., information or hardware),<br />

possible attacks, and the possible damage to the system.<br />

2. Threat analysis is based on the risk analysis and is assigning the impact of damage. Whereas the<br />

risk analysis is only committed to the identification of risks, the threat analysis is giving a priority<br />

to the impact of risks and assigns occurrence probabilities as well as the extent of damage. The<br />

resulting risk finally is the product of caused damage and the probability of the threat. In general,<br />

for <strong>industrial</strong> <strong>communication</strong> <strong>systems</strong>, a qualitative risk assessment is common since it is hard to<br />

precisely determine values for damage and its probability.<br />

3. Analysis of weaknesses tracking vulnerabilities of the system. In this step, the system will be carefully<br />

analyzed. Based on the previous two steps, actual weaknesses will be identified. Only for<br />

these weaknesses countermeasures must be designed.<br />

4. Design and specification of security measures dealing with the planning and implementation of<br />

appropriate countermeasures. Especially important in this step is to find the trade-off between<br />

consequences of an attack and “comfort.” For example, consequences could be a monetary loss<br />

but also a damage of the image or an environmental damage, whereas “comfort” subsumes many<br />

areas beginning from efficient data transmission, low installation costs, easy usability, or social<br />

acceptance. Hundred percent security is not possible. Only an optimum within this trade-off can<br />

be found on the base of a certain application or application class. Another important part of this<br />

phase is the definition of the system boundaries of the security architecture. For example, the best<br />

cryptography to protect the transmission channel is useless, if the password requires being so<br />

complex that all users maintain a paper copy of the password beneath their keyboard.<br />

This general procedure to design a security policy is a continuous process throughout the life time<br />

of a system. In particular, a good security policy is active and not only reactive in the sense that it foresees<br />

incidents and avoids being a pure reaction on attacks. Adversaries are favored; they can concentrate<br />

on certain vulnerabilities and do not have to protect the whole system. To all these procedures,<br />

the principle of Kerckhoff should be applied demanding that the complete cryptographic algorithm<br />

must be public and the security should only rely on the secrecy of the keys [KER]. No security by<br />

obscurity. Allowing algorithms and procedures to be open allows wide spread security analysis, and<br />

therefore reduces the risk of undiscovered security holes. Additionally, this principle also reduces the<br />

risk of insider attacks since the knowledge of the system structure offers no advantages unless the<br />

proper keys are known.<br />

For <strong>industrial</strong> automation <strong>systems</strong> a “defense-in-depth” concept is the favorable approach to protect<br />

<strong>systems</strong> since many <strong>industrial</strong> <strong>communication</strong> <strong>systems</strong> are already structured in a hierarchical way following<br />

the computer-integrated manufacturing (CIM) model philosophy and also following the need<br />

to structure the network. Defense in depth relies on different security layers to protect valuable assets:<br />

Using the famous onion analogon, we see that removing the outmost (security) layer reveals another<br />

layer and many more remain to be peeled away before the assets become vulnerable. In the physical<br />

world such a procedure is natural (also in <strong>industrial</strong> automation) having a fence around the factory area,<br />

© <strong>2011</strong> by Taylor and Francis Group, LLC

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!