1
MILS Research Montage MILS Research Montage
LAW LAW Work-In-Progress Session Work-In-Progress Session December 6, 2011 December 6, 2011
Rance DeLong Rance DeLong Consulting Researcher Consulting Researcher
MILS Research Montage MILS Research Montage LAW LAW - - PowerPoint PPT Presentation
MILS Research Montage MILS Research Montage LAW LAW Work-In-Progress Session Work-In-Progress Session December 6, 2011 December 6, 2011 Rance DeLong Rance DeLong Consulting Researcher Consulting Researcher 1 MILS Efforts Overview
1
Rance DeLong Rance DeLong Consulting Researcher Consulting Researcher
2
Implementation Science Standards Eval & Cert Products Dissemination MILS Vision
Constitution
Manifesto
Math
Lecture Notes RTI OIS GHS LW WRS
SKPP MIPP
Concepts
Compos. Cert. DCI Galois
Example
CCAE
LAW
Evidence
Effort Categories Efforts/Results to date
* Sponsored by AFRL / CMPO
Guard MCSPP MNSPP
*
ICCC DASC TOG RCI Found’nl Comps Opera’nl Comps
Tools
API
Inter-op
Patterns
Assemblies
Ref Impls
*
Scheme
Sysgo NSA TOG
Future
AADL
3
l l Objective:
l l 4 Themes
– – Components Components – – development and assurance of individual components development and assurance of individual components – – Integration Integration – – integration of MILS components and systems integration of MILS components and systems – – Deployment Deployment – – facilitate MILS deployment facilitate MILS deployment – – Certification Certification – – enable MILS evaluation and certification enable MILS evaluation and certification
l l Initial tasks (2010)
– – Evidence and Evidence and toolchains toolchains for MILS certification study for MILS certification study – – MILS Cross Domain Solution (CDS) operational component Study MILS Cross Domain Solution (CDS) operational component Study – – MILS Delivery, Configuration, and Initialization (DCI) Study MILS Delivery, Configuration, and Initialization (DCI) Study
* Performed at SRI, sponsored by AF Research Laboratory and AF Cryptographic Modernization Program Office.
4
l l Current tasks (2011-2012) -
– – AADL and MILS AADL and MILS – – MIPP completion (MIPP as a document) MIPP completion (MIPP as a document) – – “ “Programming the MIPP Programming the MIPP” ” (MIPP encoded in the CCAE) (MIPP encoded in the CCAE) – – MILS Delivery, Configuration, Initialization model MILS Delivery, Configuration, Initialization model – – MILS Cross Domain Solution investigation MILS Cross Domain Solution investigation – – MILS Network Subsystem Protection Profile MILS Network Subsystem Protection Profile
* Performed at SRI, sponsored by AF Research Laboratory and AF Cryptographic Modernization Program Office.
5
l l Separation Kernel (SKPP)
l l MILS Network System (MNSPP)
l l MILS Console System (MCSPP)
l l MILS Extended Attributes PP (MEAPP)
l l MILS File System (MFSPP)
l l . . .
l l MILS Integration Protection Profile (MIPP)
MIPP MFSPP MEAPP MCSPP MNSPP SKPP . . .
“Conforms to” “Patterned after” “Extended by”
6
CC MEAPP MCSPP MNSPP MFSPP STMEA STMCS STMNS STMFS STMEA STMCS STMNS STMFS STMEA STMCS STMNS STMFS STMEA STMCS STMNS STMFS MEA2 Console2 Network2 File System2 MEA4 Console4 Network4 File System4 MEA1 Console1 Network1 File System1 MEA3 Console3 Network3 File System3 SKPP STSK STSK STSK STSK SK2 SK4 SK1 SK3 SK4 MEA2 Console1 File System3 Network3
SK1 MEA3 Console4 File System4 Network1
7
MILS Console Subsystem Session Manager
MILS File and Directory Subsystem
MLS RVM Auth Data Mgmt
Audit Mgmt
I&A
Human
I’face Devs
MILS Network Subsystem
System Management
Application Instantiator
MILS PCS MILS
CORBA
App Mgmt Audit Client Partitions / Subjects Client Partitions / Subjects Client Partitions / Subjects MLS RVM
8
Architecture as an Integration Framework Something that must be designed. Something that has properties.
9
l l The system level
l l The system level
l l The system level
l l A system concept and
l l Identification of, and connections among, the
l l A basis for formal
l l Constraints
– – Security objectives, or modified ones, that pass to the component Security objectives, or modified ones, that pass to the component – – Relationships and obligations (rely-guarantee) among the Relationships and obligations (rely-guarantee) among the components components – – Interaction schemas for interacting components Interaction schemas for interacting components
10
Mbuf Mgmt Socket Layer Transport Layer Network Layer Interface Layer calls queues calls queues calls queues
Apps
Dev
Driver
calls Socket Layer Transport Layer calls queues calls queues
Apps
Dev
Driver
calls
MLS App
calls Dev
b t b t b t
Dev Dev sw intr sw intr
sw intr
sw intr
sw intr
hw intr sw intr Dev Labeled Sep calls Crypto Sep
Socket Layer Transport Layer Network Layer Interface Layer calls queues calls queues calls queues
Apps
Dev Driver calls Socket Layer Transport Layer Network Layer Interface Layer calls queues calls queues calls queues
Apps
Dev Driver calls
Individual data items associated with a single security domain Code manipulates data in multiple security domains
Socket Layer Transport Layer Network Layer Interface Layer Driver Mbufs / Clusters calls queues calls queues calls queues
Apps
calls
Mbuf Mgmt
Nothing Trusted Everything Trusted Combination of Trusted and Untrusted
Dev Dev Dev Dev
11
HIGH inputs LOW outputs LOW inputs HIGH outputs
Relies Guarantees IIIIIIIII… iiiiiiii… OOOOOOO…
12
HIGH Inputs LOW Outputs LOW Inputs HIGH Outputs
Relies Guarantees H(HI,HO) L(LI,LO) S(HI,HO,LI,LO)
Constraints:
IIIIIIIII… iiiiiiii… OOOOOOO…
Properties: P(HI,HO,LI,LO) st S ≤ P
13
Relies Guarantees
a) b) c)
14
l l
Compose assurance cases using Assume-Guarantee Reasoning Compose assurance cases using Assume-Guarantee Reasoning
l l
Assumptions from MI assurance case become requirements on the Assumptions from MI assurance case become requirements on the components components
l l
Assured Claims from component assurance cases become evidence Assured Claims from component assurance cases become evidence for MI for MI
MI Claims
Evidence Evidence Evidence Inference rule Inference rule MI Assurance Argument
SK Claims MNS Claims MCS Claims
Inference rule Inference rule Inference rule Inference rule Inference rule Inference rule SK Assurance Argument MNS Assurance Argument MCS Assurance Argument
Rely Guarantee
15
CCAE CCAE CCAE CCAE CCAE Co Collaboration En Environment CCAE CCAE CCAE CCAE CCAE CCAE Author Author Reviewers Reviewers Evaluators Evaluators Certifiers
CCAE CCAE
16
Rule Base
CC Component Operation Rules, Semantic Rules, Relational Model, Workflow Rules
Doc Creation Library
Conventions, Doc comp classes Doc generators: PP, ST, FSP
Env Library
Components, CC SFRs/SARs, Interps, CIM, Security Ontology, Resource Registry MILS Integ FW
Parent PP, MILS TOE Concept,
Requirements
PP, ST, stats Document Publishing
Project Team Exchange
Doc Assembly, Catalog Selection, Checking, Reviewing, Inference, Rule Execution, Queries, XML gen
XML PDF, DOCX, XLSX, …
Current Document Factbase
Documents & Reports
Rendering & Conversion
CCAE Document Repository UI Agent
17
Functional Requirements Assurance Requirements Assumptions Policies Threats Security Objectives Environment Requirements Environment Security Objectives
FAU, FCO, FCS, FDP, FIA, FMT, FPR, FPT, FRU, FTA, FTP ACM, ADO, ADV, AGD, ALC, (AMA), ATE, AVA
T
Π
Α
SFR
SAR )
18
PP = ( 2 PP = ( 2T
T
× × 2 2Π
Π
× × 2 2Α
Α
× × Ω Ω × × 2 2SFR
SFR
× × 2 2SAR
SAR )
)
C
E E ⊂ ⊂ PP evaluatable PPs PP evaluatable PPs M M ⊂ ⊂ E MILS evaluatable PPs E MILS evaluatable PPs
C a candidate
CCAE drives MC toward M by measuring consistency and coverage with respect to MCCAE
19
PPABC
PPAC PPAB PPA
Work Units A
Work Units AB \ {A} Work Units AC \ {A,AB}
Work Units ABC \ {A,AB,AC}
Difference operator “ \ ” applies comp’nt dependency, hierarchy, and other PP property closures. Differential work units assume
Evaluation Work Unit Checklists Standard PPs
Polymorphic PP with sub-profiles A, B, C
20
PPA
Note, the following Venn diagrams represent contents of projected PPs, not PPP sub-profiles. Projected PPs may have substantial intersection, while sub-profiles may be disjoint.
21
PPAB
PPA
PPA ∩ PPAB
22
PPAB PPA
PPA ∩ PPAB
PPABC
(PPA ∩ PPAB) ∩ PPABC
23
l l Interleaved configuration and delivery
l l Configuration and integration is
l l OEM TOE developer is responsible for providing trusted delivery and for
l l Trusted delivery should protect TOE to the deployment environment,
l l There can be multiple intermediate integrator environments!
Developer Environment Integrator Environment(s)
Dev Delivery Config Init Operation OEM Config
User (deployment) Environment
Config Delivery
24
fs pcs net con sk ap1 ap2 fs pcs net con ap1 ap2 C cn c6 c5 c4 c3 c2 c1 c7
bundle
init cm sk cd
25
Development Env Configuration Delivery Initialization Integration Env(s) Operation Reconfig User Env
Developer Environment Integrator Environment(s) User (deployment) Environment
26
…
Operational Interval 1
…
Operational Interval 2
Φ - system configuration property φi - interval configuration property τR - reconfiguration transition
Trace of System States
s0
1
s0
2
Interval Configuration Properties System Configuration Property