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.

Device at<br />

Safety level X<br />

Device at<br />

Safety level X<br />

Device at<br />

Safety level X<br />

Device at<br />

Safety level X<br />

<strong>Networks</strong><br />

operat<strong>in</strong>g at<br />

a Safety Level X<br />

Encapsulates<br />

& Encrypts<br />

Encapsulates<br />

& Encrypts<br />

Network operat<strong>in</strong>g at<br />

a Safety Level different<br />

than X (i.e., Y)<br />

Device at<br />

Safety level Y<br />

Device at<br />

Safety level Y<br />

Device at<br />

Safety level Y<br />

Figure 27. DO-178B Classifications Us<strong>in</strong>g Biba Integrity Model<br />

Figure 27 shows devices operat<strong>in</strong>g at safety classification X (e.g., either level A, B, C, D, or E).<br />

These devices operate with<strong>in</strong> a network (e.g., a VPN) function<strong>in</strong>g at that specific safety<br />

classification level. Network partition<strong>in</strong>g <strong>in</strong> terms of safety classifications may implicitly<br />

<strong>in</strong>volve data categorization to the extent that data is directly related to safety dist<strong>in</strong>ctions. Figure<br />

27 shows that those networks operat<strong>in</strong>g at the same safety level may be discont<strong>in</strong>uous. For<br />

example, the items located at the top left need to communicate with the items located at the top<br />

right, and vice versa. These discont<strong>in</strong>uous network segments can be jo<strong>in</strong>ed by a different<br />

network system operat<strong>in</strong>g at a different safety level through encrypt<strong>in</strong>g the orig<strong>in</strong>al packets and<br />

encapsulat<strong>in</strong>g them <strong>in</strong>to the protocol headers of the lower network system (see figure 17). The<br />

top networks <strong>in</strong> figure 27 are the customer site networks mentioned <strong>in</strong> figure 20. It is a RED<br />

(pla<strong>in</strong> text) network. The bottom (l<strong>in</strong>k<strong>in</strong>g) network is the service provider network mentioned <strong>in</strong><br />

figure 20. It is a BLACK (cipher text) network—although, as a po<strong>in</strong>t of fact, it almost certa<strong>in</strong>ly<br />

conveys pla<strong>in</strong> text packets that are operational at its own classification level. The encapsulation<br />

and encryption is performed <strong>in</strong> accordance with IPsec’s ESP <strong>in</strong> tunnel mode, which is the<br />

“encapsulates and encrypts” function shown with<strong>in</strong> figure 27. That function is also the<br />

“<strong>in</strong>terface” described <strong>in</strong> figure 20. The stack chart of the packets from the top network system<br />

(operat<strong>in</strong>g at safety level X) appears as is shown <strong>in</strong> figure 22, when they are conveyed over the<br />

bottom network system of figure 27 (operat<strong>in</strong>g at safety level Y). Consequently, one can see this<br />

approach corresponds to both DoD COMSEC and <strong>in</strong>dustry VPNs.<br />

VPN encryption should use FIPS compliant encryption algorithms. Protocol encapsulation<br />

ensures that these are logically dist<strong>in</strong>ct network systems that are unable to address or <strong>in</strong>terwork<br />

with different logical network systems operat<strong>in</strong>g at different safety levels except at the<br />

encapsulation and encryption <strong>in</strong>terface. However, s<strong>in</strong>ce each <strong>in</strong>terface is specialized to only one<br />

VPN <strong>in</strong>stance (i.e., it physically cannot support multiple RED VPN systems), confusion between<br />

VPNs cannot occur. This is true regardless of whether or not these networks have physically<br />

dist<strong>in</strong>ct media systems. Specifically, figure 27 can be <strong>in</strong>terpreted as show<strong>in</strong>g <strong>in</strong>terconnected<br />

networks hav<strong>in</strong>g three dist<strong>in</strong>ct physical media <strong>in</strong>stances (top left, top right, bottom), with the top<br />

two physical media systems operat<strong>in</strong>g at the same safety level that is a different safety level than<br />

89

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

Saved successfully!

Ooh no, something went wrong!