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.

the bottom network system. However, figure 27 can also be <strong>in</strong>terpreted as show<strong>in</strong>g a network<br />

hav<strong>in</strong>g the same ubiquitous physical media subdivided <strong>in</strong>to logically different network elements.<br />

In the latter case, the top left, top right, and bottom all use the same physical media. In this case,<br />

different logical network systems, each hav<strong>in</strong>g effective network security and isolation through<br />

protocol encapsulation, have been created from the same physical system. This latter<br />

observation is directly applicable to aircraft systems shar<strong>in</strong>g a common LAN system. That is,<br />

COMSEC and VPN techniques permit the creation of partitioned network systems even when<br />

shar<strong>in</strong>g a common physical network.<br />

This study recommends us<strong>in</strong>g the Biba Integrity Model to extend current <strong>FAA</strong> policies <strong>in</strong>to<br />

arbitrarily complex networked environments because it is a formal model on the par with the<br />

DoD’s Bell-LaPadula Confidentiality Model and also because it creates structures that are the<br />

direct analog of the Bell-LaPadula Confidentiality Model. Other security models are also<br />

available, <strong>in</strong>clud<strong>in</strong>g other <strong>in</strong>tegrity models (e.g., the Clark-Wilson Integrity Model). Similarly,<br />

the <strong>FAA</strong> could <strong>in</strong>vent a security model of its own, <strong>in</strong>clud<strong>in</strong>g perform<strong>in</strong>g the necessary<br />

mathematical proofs. Any of these are valid alternatives for the <strong>FAA</strong> to consider. What is not a<br />

valid alternative is to attempt to extend ARP 4754 <strong>in</strong>to networked environments without us<strong>in</strong>g a<br />

viable formal mathematical model (e.g., a security model) of some sort. Any such extension<br />

would necessarily be ad hoc and produce results that cannot be trusted to be safe.<br />

6.5 RELATING SAFETY CLASSIFICATION LEVELS TO THE CC.<br />

The exemplar network architecture described <strong>in</strong> section 8.3 relies upon security controls (e.g.,<br />

firewall, packet filter, ASBR, VPN encapsulation gateways, and HAGs) to provide security<br />

protections for the networked system so that the result<strong>in</strong>g system is assured to operate at a<br />

specific safety level. Section 6.4 expla<strong>in</strong>ed that airborne networks operate at specific safety<br />

levels as def<strong>in</strong>ed by <strong>FAA</strong> policy (e.g., DO-178B and ARP 4574) and enforced by the Biba<br />

Integrity Model. Therefore, for certification purposes, the <strong>in</strong>tegrity of these security controls<br />

must be mapped to the appropriate DO-178B safety level. This implies that these security<br />

controls can be evaluated <strong>in</strong> terms of specific DO-178B safety level assurances for the Biba<br />

Integrity Model provisions to be viable. This section discusses this issue.<br />

The <strong>FAA</strong> has sponsored a grow<strong>in</strong>g body of work evaluat<strong>in</strong>g common security and safety<br />

processes and systems [41 and 72, 73, and 76]. This issue directly impacts aircraft that need to<br />

be dual certified by both the <strong>FAA</strong> (for safety) and DoD (e.g., the U.S. Air Force; for security).<br />

However, this issue is also of a more generic <strong>in</strong>terest. For example, the DoD, <strong>in</strong> addition to<br />

def<strong>in</strong><strong>in</strong>g their <strong>in</strong>formation systems <strong>in</strong> accordance with security (i.e., confidentiality <strong>in</strong> particular)<br />

constructs, is also concerned with safety issues, which are def<strong>in</strong>ed <strong>in</strong> terms of MIL-STD-882D<br />

[90]. MIL-STD-882D shares many similarities with exist<strong>in</strong>g civil aviation concepts <strong>in</strong>clud<strong>in</strong>g a<br />

similar safety five-level classification system.<br />

Although safety and security are very dist<strong>in</strong>ct concepts, they share some common attributes that<br />

permit them to be compared (and equated) <strong>in</strong> several different ways. For example, the <strong>FAA</strong> and<br />

the DoD have created comparable certification environments hav<strong>in</strong>g similar concepts of<br />

assurance. Both safety and security also have similar <strong>in</strong>tegrity attributes that may be leveraged<br />

90

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

Saved successfully!

Ooh no, something went wrong!