Military Communications and Information Technology: A Trusted ...

Military Communications and Information Technology: A Trusted ... Military Communications and Information Technology: A Trusted ...

22.01.2015 Views

382 Military Communications and Information Technology... IV. Evolutionary approach The phased approach has been proposed to implementation and deployment of the HAAG in order to address both urgent operational requirements and provide a robust and flexible solution to cross-domain information sharing for the NNEC and FMN infrastructure. The approach consists of 3 phases that incrementally improve information sharing capability. Phase 0 is a cascading design that provides an immediate response to the urgent requirements for information sharing between NATO and international organizations / non-NATO nations. Phase 1 uses the HAAG as a gateway that enforces authentication, authorization, and accountability of all end-users. Phase 2 uses the HAAG to provide a service where information is released based on security and protection requirements derived from a dynamic policy. A. Phase 0: Cascading design using XLG Phase 0 represents an incremental development path for the existing NCIA medium assurance XML-Labelling Guard (XLG). The proposed solution, applicability of which shall be confirmed case by case through an extensive security risk assessment, attempts to partially compensate lower security assurance level of the XLG by introducing an intermediate, NATO Restricted (NR), security domain between IO/NNN and the NATO Secret (NS) system. The XLG is located between the NR and the NS domain. Several reactive security services, such as intrusion detection and malware protection are redundantly deployed in the NR and NS domains in order to provide increased security assurance via a cascading architecture. Figure 3. Example of a cascading design for IEG-D Phase 0 implementation

Chapter 4: Information Assurance & Cyber Defence 383 B. Phase 1: High assurance automated guard as a gateway A logical evolution of the Phase 0 design is to replace the cascade with a single high assurance guard used as a gateway, an architecture shown in Figure 4. Figure 4. High assurance automated guard (HAAG) as a gateway This architecture uses the HAAG as a dedicated information flow control device between the domain with a lower and a higher trustworthiness. In addition, the HAAG must be accompanied by, and usually collocated with, additional security tools, such as firewalls and malware detection software. Compared to the Phase 0 architecture, there are two important differences. First, the HAAG authenticates users from both low and high domains, whereas only network interfaces were authenticated in Phase 0. The authentication is mainly for auditing and accountability purposes, but can also constitute an input for an authorization of access to the data (e.g. basic enforcement of need-to-know principle). Second, the required assurance level for the HAAG design and implementation is significantly higher. Phase 1 improves the assurance and information flow capabilities in a short to medium time-frame. It relies on support for cross-domain authentication, e.g. by implementing a claims-based identity and access control [11]. This architecture allows also a gradual introduction of elements of the CPR security policies. The CPR security model is envisaged to replace in the long term an inflexible Bell-LaPadula security model, which is not suitable for a modern dynamic and federated coalition environment. C. Phase 2: High assurance automated guard as a separation service In Phase 2 of the HAAG development a more radical approach is taken toward solving the information sharing challenges. This approach is based on a complete rethinking of the security model used within NATO and utilizing implementation of advanced cryptographic mechanisms. In this architecture, depicted in Figure 5, the concept of security domains is abandoned, and the information flow is controlled through a HAAG service implemented in a distributed fashion.

382 <strong>Military</strong> <strong>Communications</strong> <strong>and</strong> <strong>Information</strong> <strong>Technology</strong>...<br />

IV. Evolutionary approach<br />

The phased approach has been proposed to implementation <strong>and</strong> deployment<br />

of the HAAG in order to address both urgent operational requirements <strong>and</strong> provide<br />

a robust <strong>and</strong> flexible solution to cross-domain information sharing for the NNEC<br />

<strong>and</strong> FMN infrastructure.<br />

The approach consists of 3 phases that incrementally improve information<br />

sharing capability. Phase 0 is a cascading design that provides an immediate response<br />

to the urgent requirements for information sharing between NATO <strong>and</strong> international<br />

organizations / non-NATO nations. Phase 1 uses the HAAG as a gateway<br />

that enforces authentication, authorization, <strong>and</strong> accountability of all end-users.<br />

Phase 2 uses the HAAG to provide a service where information is released based<br />

on security <strong>and</strong> protection requirements derived from a dynamic policy.<br />

A. Phase 0: Cascading design using XLG<br />

Phase 0 represents an incremental development path for the existing NCIA medium<br />

assurance XML-Labelling Guard (XLG). The proposed solution, applicability<br />

of which shall be confirmed case by case through an extensive security risk assessment,<br />

attempts to partially compensate lower security assurance level of the XLG<br />

by introducing an intermediate, NATO Restricted (NR), security domain between<br />

IO/NNN <strong>and</strong> the NATO Secret (NS) system. The XLG is located between the NR<br />

<strong>and</strong> the NS domain. Several reactive security services, such as intrusion detection<br />

<strong>and</strong> malware protection are redundantly deployed in the NR <strong>and</strong> NS domains<br />

in order to provide increased security assurance via a cascading architecture.<br />

Figure 3. Example of a cascading design for IEG-D Phase 0 implementation

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

Saved successfully!

Ooh no, something went wrong!