13.09.2014 Views

Local Area Networks (LANs) in Aircraft - FTP Directory Listing - FAA

Local Area Networks (LANs) in Aircraft - FTP Directory Listing - FAA

Local Area Networks (LANs) in Aircraft - FTP Directory Listing - FAA

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

<strong>in</strong>tegrity is not permitted to observe (read) an object at a lower level of <strong>in</strong>tegrity (no read down).<br />

The Biba * (star) Integrity axiom requires that an object at one level of <strong>in</strong>tegrity is not permitted<br />

to modify (write to) an object of a higher level of <strong>in</strong>tegrity (no write up), thereby preserv<strong>in</strong>g the<br />

higher level of <strong>in</strong>tegrity. As with the Bell-LaPadula Confidentiality Model, a subject at one level<br />

of <strong>in</strong>tegrity cannot <strong>in</strong>voke a subject at a higher level of <strong>in</strong>tegrity.<br />

Also similar to the Bell-LaPadula Confidentiality Model, the Biba Integrity Model has<br />

provisions for HAGs, which enable highly controlled functions to occur that would have<br />

otherwise been prohibited by the model. HAGs are trusted subjects that operate <strong>in</strong> a highly<br />

controlled and highly localized manner. However, <strong>in</strong> the Biba case, the HAG is concerned with<br />

<strong>in</strong>tegrity issues that permit a highly trusted <strong>in</strong>tegrity environment to safely receive<br />

communication from a less trusted one <strong>in</strong> a highly controlled way. For example, a HAG might<br />

be <strong>in</strong>serted <strong>in</strong>to the network to support a Level C software system that needs to communicate<br />

with a Level A software system.<br />

6.3 COMPARING CIVILIAN AIRCRAFT SAFETY AND FEDERAL GOVERNMENT<br />

SECURITY LEVELS.<br />

6.3.1 Civil <strong>Aircraft</strong> Software Levels.<br />

The civilian aircraft <strong>in</strong>dustry’s DO-178B software levels are:<br />

“based upon the contribution of software to potential failure conditions as<br />

determ<strong>in</strong>ed by the system safety assessment process. The software level<br />

implies that the level of effort required to show compliance with certification<br />

requirements varies with the failure condition category.” (Quoted from<br />

Section 2.2.2 of reference 5.)<br />

DO-178B def<strong>in</strong>es the follow<strong>in</strong>g specific failure condition categories.<br />

“The categories are:<br />

a. Catastrophic: Failure conditions which would prevent cont<strong>in</strong>ued safe flight<br />

and land<strong>in</strong>g.<br />

b. Hazardous/Severe-Major: Failure conditions which would reduce the<br />

capability of the aircraft of the ability of the crew to cope with adverse<br />

operat<strong>in</strong>g conditions to the extent that there would be:<br />

(1) a large reduction <strong>in</strong> safety marg<strong>in</strong>s or functional capabilities,<br />

(2) physical distress or higher workload such that the flight crew could not be<br />

relied on to perform their tasks accurately or completely, or<br />

(3) adverse effects on occupants <strong>in</strong>clud<strong>in</strong>g serious or potentially fatal <strong>in</strong>juries<br />

to a small number of those occupants.<br />

83

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

Saved successfully!

Ooh no, something went wrong!