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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The corporate world also has classification systems. Each company has its own rules for the<br />

protection of <strong>in</strong>formation depend<strong>in</strong>g upon its sensitivity level to <strong>in</strong>tellectual property, bus<strong>in</strong>ess<br />

strategy, and other similar areas. In many respects, the corporate classification system follows<br />

the federal government system. As an example, there might be three levels of <strong>in</strong>formation<br />

control with<strong>in</strong> a corporation where the highest is limited and cannot be released outside of the<br />

company. Proprietary <strong>in</strong>formation can be released but only to those <strong>in</strong>dividuals and companies<br />

bound by a signed nondisclosure agreement. F<strong>in</strong>ally, any <strong>in</strong>formation not covered by the above<br />

can be released outside the company with<strong>in</strong> the restrictions placed by the federal government. In<br />

addition, International Traffic <strong>in</strong> Arms Regulations [89] controlled <strong>in</strong>formation, although<br />

unclassified and nonproprietary, must still be controlled to prevent disclosure to foreign<br />

nationals unless an appropriate export license has been obta<strong>in</strong>ed.<br />

6.3.3 Comparison of the Two Policy Systems.<br />

It is clear the <strong>FAA</strong> and civil aviation are concerned about airplane safety and so they def<strong>in</strong>e<br />

airborne software <strong>in</strong> terms of the possible safety affects of software failure conditions. The<br />

Federal Government, which <strong>in</strong>cludes the DoD, is concerned about protection of sensitive<br />

<strong>in</strong>formation and programs. It def<strong>in</strong>es its software systems <strong>in</strong> terms of the impact of that software<br />

upon the protection of sensitive <strong>in</strong>formation and programs. Although the focus on what is be<strong>in</strong>g<br />

protected aga<strong>in</strong>st is entirely different between these two policy systems, the <strong>in</strong>tent of the<br />

protection mechanisms are similar. Both enforce restrictions on how software operates with<strong>in</strong> its<br />

system context. Both are also concerned with the impact of protection mechanisms and the<br />

consequences of possible failure affects. Both def<strong>in</strong>e their assurance system <strong>in</strong> terms of the<br />

worst-case affects of failure conditions. Co<strong>in</strong>cidentally, both assurance systems are also<br />

remarkably similar to each other when viewed at a high level of abstraction, as shown <strong>in</strong> table 2.<br />

Table 2. Comparison of Safety Levels to Security Classifications<br />

Safety<br />

Level A (catastrophic condition)<br />

Level B (hazardous/severe-major condition)<br />

Level C (major condition)<br />

Level D (m<strong>in</strong>or condition)<br />

Level E (no-effect condition)<br />

Security<br />

Top Secret (exceptionally grave damage)<br />

Secret (serious damage)<br />

Confidential (damage)<br />

Sensitive but Unclassified (could adversely<br />

affect)<br />

Unclassified (no effect)<br />

Therefore, although the civil aviation and federal government systems are dist<strong>in</strong>ct systems from<br />

each other and are oriented around very different issues, they nevertheless share important<br />

attributes. Additional similarities and differences between the two systems <strong>in</strong>clude the<br />

follow<strong>in</strong>g:<br />

• Only the security side is concerned with confidentiality issues—this issue is briefly<br />

discussed <strong>in</strong> section 6.1.4.<br />

86

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

Saved successfully!

Ooh no, something went wrong!