27.06.2013 Views

6th European Conference - Academic Conferences

6th European Conference - Academic Conferences

6th European Conference - Academic Conferences

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

Harm Schotanus et al.<br />

In this setup we add a third element, namely the release mechanism. Essentially, the other elements<br />

stay the same. This release mechanism has a two-fold purpose. The first is to verify that a suitable<br />

label accompanies the information and if not, try to retrieve the label from the information<br />

management system. The suitability is established by validating that all the necessary information is<br />

present. The second purpose is the ability to translate an internal label to an external label. For<br />

example certain elements may be removed from the document (such as the name of the author) or<br />

other information may be added (e.g. the date of information exchange), or a different labelling<br />

structure may be used for internal and external purposes 2 .<br />

3.3 Integrity protection<br />

The third step in extending the labelling architecture is to realise integrity protection of information.<br />

Integrity protection refers to the means to establish whether a document is authentic or has been<br />

changed. And as a secondary benefit, it may be established who assessed the authenticity.<br />

The label has to be extended to include a secure binding to link the information and the label together,<br />

in such a way that it can always be detected if an existing label is attached to other (different or<br />

altered) information, or if the label content has been changed. Making a change to an information<br />

object can be detected because that would result in a different object.<br />

For the binding to be secure we need cryptographic support. A method, amongst others, of realising<br />

this is through a PKI. A user has to use a private key to sign the binding in the label, which links the<br />

binding also directly to the user. That is, it can easily be determined who created the label. To validate<br />

the integrity of the document, the public key of the user that created the binding can be used to verify<br />

the binding in the label. In case any changes have been made, the verification will fail.<br />

Certificates<br />

and CRL<br />

Labelling<br />

application<br />

Trusted OS<br />

Workstation<br />

Labels and<br />

documents<br />

PKI<br />

Document<br />

Information<br />

management<br />

system<br />

Label<br />

Release<br />

mechanism<br />

and IEG<br />

Figure 4: Labelling for integrity protection<br />

For a high assurance environment 3 , we also need to ensure that the labelling process works correctly.<br />

In other words we must have a level of assurance that the information the user actually labelled is the<br />

correct information and has not been modified unbeknownst to the user during the process. We<br />

cannot attain that level of assurance on a normal platform (operating system); therefore we need an<br />

operating system or platform that can provide us the needed assurance. This has been named a<br />

trusted operating system. Essentially, each step in the process of labelling must be carried out under<br />

2 Note that the release mechanism does not comprise the entire interconnection here, there may be other elements needed too,<br />

for instance cryptographic units or firewalls to ensure a secure connection.<br />

3 For instance information domains which process highly classified information.<br />

233

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

Saved successfully!

Ooh no, something went wrong!