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.

22-4 Industrial Communication Systems<br />

Company or internet domain<br />

(entrance domain)<br />

Intranet domain<br />

(checking domain, DMZ)<br />

Security<br />

measure<br />

Security<br />

measure<br />

Shop floor<br />

domain<br />

(fieldbus)<br />

Inner security structure<br />

Trustworthy<br />

entity<br />

Security<br />

measure<br />

FIGURE 22.1<br />

Three-zone security model.<br />

locked doors to the shop floor, and locked cabinets to the control. Figure 22.1 shows a three-zone security<br />

model optimized for <strong>industrial</strong> <strong>communication</strong> applications as also introduced by [SC2,TR1,KHA1].<br />

Corresponding to the interconnection zones in the company network three zones are available. The<br />

inner fieldbus zone hosting the field-level <strong>communication</strong> <strong>systems</strong> mostly located at the shop floor, the<br />

intranet zone often build upon IP-based LANs inside the plant (it also includes demilitarized zones<br />

(DMZs) and checking domains or inner security structures to strengthen the security), and finally the<br />

Internet zone also referred to as company or entrance domain connecting multiple plants, remote maintenance<br />

sites, customers, etc. The zones are separated from each other by dedicated security measures<br />

often located at dedicated network nodes that can be used as anchor points for the security strategy.<br />

Typical examples are firewalls between the company and the intranet domain or application gateways<br />

between the intranet domain and the shop floor. As there is only a limited number of those network<br />

nodes (between every couple of zones), it is possible to use state-of-the-art components in regard to security<br />

without straining available resources too much. In this way, a defense-in-depth approach is installed<br />

preventing that an adversary has access to all zones and especially to the most inner zone forming the<br />

core of production. Additionally, focusing most of the efforts to those anchor points of the network<br />

infrastructure avoids misconfiguration that may happen if the number of security-relevant nodes grows.<br />

22.3 Security Measures to Counteract Network Attacks<br />

To counteract network attacks, two possibilities exist. First, unauthorized access to the network and<br />

thus to the data that is transmitted over the network can be avoided. One approach is to limit the physical<br />

access to the network medium by, for example, immuring the network cable. Obviously, preventing<br />

physical access is not always possible. Consider, for example, the use of wireless or wide area networks<br />

where public access cannot be avoided. Therefore, organizational measures that limit the logical access<br />

can be used instead. Typical examples are the use of virtual private networks (VPNs) (cf. Section 22.3.1)<br />

and firewalls (cf. Section 22.3.2).<br />

Second, the transmitted data itself can be protected in a way that an adversary is not able to maliciously<br />

interfere with it even in cases where an adversary has access to the network. According to [GR1],<br />

the following security objectives can be guaranteed: data confidentiality (against interception attacks),<br />

data integrity and authentication (against modification attacks), data freshness (against fabrication<br />

attacks), and data availability (against interruption attacks). Depending on the security requirements<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!