22.01.2015 Views

Military Communications and Information Technology: A Trusted ...

Military Communications and Information Technology: A Trusted ...

Military Communications and Information Technology: A Trusted ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

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

is more difficult in the context of the “NATO as an Alliance” scenario, implying<br />

operations across governance realms. Apart from st<strong>and</strong>ard technical<br />

solution <strong>and</strong> internally developed procedures, it is necessary to develop<br />

templates for business agreements <strong>and</strong> processes for cross-domain forensic<br />

measures in order to facilitate auditing <strong>and</strong> ensure that investigative authorities<br />

have access to necessary information <strong>and</strong> can correlate information<br />

across domains as part of a detective control or for incident response.<br />

F. Trust relationships<br />

This decision point should determine the terms on which a domain may<br />

establish federations with partners. Depending on the federation scenario, trust<br />

relationships require agreements at a subset or at all the three levels as follows:<br />

• technical, proving technical framework of security specifications that can be<br />

derived from specifications defined in operational security,<br />

• business, describing functional aspects derived from the business case<br />

of the federation as well as the governance framework,<br />

• legal, proving the legal framework for the federation.<br />

Detailed analysis of the business <strong>and</strong> legal aspects are out of scope of this investigation.<br />

They seem, however, to be more relevant in the context of the “NATO<br />

as an Alliance” scenario. Specific regulations should address at least:<br />

• purpose of the federation,<br />

• required assurance levels,<br />

• use cases,<br />

• required security practices,<br />

• identity data usage limitations,<br />

• audit or assessment criteria for compliance with the federation regulations.<br />

Compliance validation with the federation rules is addressed in section H.<br />

G. Authorization <strong>and</strong> attribution<br />

This decision point is aimed to provide an answer to the following questions:<br />

• What attributes are going to be used for authorization decisions<br />

• How should attributes be exchanged between domains<br />

1) Federated authorization position:<br />

The current approach in NATO for authorization services is either to rely<br />

on Microsoft Active Directory (AD) capabilities or to utilize application specific<br />

authorization modules. As a result, NATO has to deal with highly decentralized<br />

(<strong>and</strong> often internally incoherent) policy infrastructures. It does not seem to be<br />

possible to easily change this approach. However, the upcoming service-oriented<br />

business processing pattern in NATO will pose new security challenges. Therefore,

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

Saved successfully!

Ooh no, something went wrong!