[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SAs and SPIs
John,
There is a blank section of the architecture document that
addresses the MLS issue, more generically described as information flow
security models. It is possible to make use of IPsec to support such
models, but we are probably going to defer the details to another document,
to facilitate faster completion of the current document. However, the
general approach would be roughly as follows:
- include security authorization info in certificates, so that the
authorized processing ranges for each user/host/net is available. this can
include hierarchic and non-hierarchic authorizations.
- expand the SPD to include references to the sensitivity labels
associated with the users/hosts/nets, as a means of expressing data flow
access controls
- use the authorization info from the certificates as an input to
the SA management procedure, along with the SPD, to establish sensitivity
ranges for each SA
- hosts authorized to process data at multiple levels
(compartments, etc.) can use separate SAs for different levels, with
implicit labelling for each SA.
Steve
References: