The
objective of the Tuesday sessions was to reach agreement on an approach
for moving forward with the standardization of APIs for the Multiple
Independent Levels (MILS) Architecture.
Summary
The session started with Rance DeLong, LynuxWorks,
providing an initial overview of
the Multiple Independent Levels of Security (MILS) architecture.
This overview was provided for new and potential members of the Forum,
so that those unfamiliar with MILS could know the context, be able to
understand subsequent presentations, and participate in ensuing
discussions about the standardization of APIs for the MILS architecture.
Rance DeLong facilitated most of the MILS session,
reiterating the commitment by LynuxWorks to participate in this effort
and to contributing a minimal application runtime, which could serve as
the basis for a standard API.
There
was further discussion on the value of standardization and what it would
mean to MILS customers if there were standard APIs, in terms of
stability and independence from any one vendor.There was good discussion on what specific content/requirements
should be included in the API.
Outputs
After
much discussion on how to proceed, the group settled on the approach
that we would start with the IEEE POSIX 1003.13, PSE 51 standard, and
then determine which of the specification elements should be included in
a minimal runtime MILS API.
Next Steps
The group will create a spreadsheet listing each
of the separate specification elements of the IEEE POSIX 1003.13, PSE 51
(by February 15), with additional columns for each participating
organization.
The
spreadsheet will be distributed to the MILS working group with a
prioritization scheme included, so that each organization will be able
to provide input on their priorities for inclusion in a minimal runtime
API. These will be collected, tabulated, and presented for discussion
via an RT&ES webinar in mid-March.
