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.

11.2 TOPICS NEEDING FURTHER STUDY.<br />

This report identifies the follow<strong>in</strong>g topics as need<strong>in</strong>g further study:<br />

• Perta<strong>in</strong><strong>in</strong>g to the last recommendation noted above, what is the trust model between civil<br />

aviation regions? Will the trust model for the regions’ Level A software network<br />

partitions (enclaves) be the same as for their Level C software network enclaves? What<br />

is the trust model between aircraft and ground entities? If air-to-air communications<br />

occur, what is the trust model between aircraft belong<strong>in</strong>g to different airl<strong>in</strong>es? Will the<br />

Level A VPN components of the NAS completely trust European Level A VPN<br />

components and vice versa, or will they establish dist<strong>in</strong>ct policies and SLA mapp<strong>in</strong>gs<br />

between their components? What security protections (e.g., firewalls) will be <strong>in</strong>serted to<br />

protect the rest of the VPN elements at that safety level from a contam<strong>in</strong>ation that<br />

occurred with<strong>in</strong> a specific region? How will aircraft that travel between regions ma<strong>in</strong>ta<strong>in</strong><br />

their connectivity <strong>in</strong> a seamless, safe, and secure manner? If air-to-air applications and<br />

systems are created, what mechanisms (e.g., firewalls) will protect the VPN at a given<br />

safety level <strong>in</strong> one airplane from (perhaps undiagnosed) misbehaviors occurr<strong>in</strong>g <strong>in</strong> the<br />

VPN at that same safety level <strong>in</strong> a different airplane? What policy systems will govern<br />

the <strong>in</strong>terrelationship between aircraft and ground entities? Will SLAs be required?<br />

• The worldwide civil aviation community needs to identify common solutions for identity<br />

(see section 4.8), IP address<strong>in</strong>g (see sections 5.3 and 5.4), nam<strong>in</strong>g, rout<strong>in</strong>g (see section<br />

5.5), protocol security (see section 4.5), and authentication (see section 4.9) subsystems.<br />

• Because network management issues for airborne networks are directly related to airl<strong>in</strong>e,<br />

manufacturer, and <strong>FAA</strong> concept of operations, this study has not provided a welldeveloped<br />

network management recommendation. Nevertheless, these issues need to be<br />

competently addressed and a viable network management system needs be designed if<br />

airborne LAN systems are to be safely networked. Therefore, network management<br />

designs and architectures need to be established for airborne networks.<br />

• Carol Taylor, Jim Alves-Foss, and Bob R<strong>in</strong>ker of the University of Idaho have studied<br />

the issue of dual software certification [93] for CC and DO-178B. Their study suggested<br />

that security functionality certified at EAL 5 can be directly compared with DO-178B<br />

Level A. This report recommends that their conclusion should be verified by further<br />

evaluation and study for the specific issue of establish<strong>in</strong>g assurance equivalencies<br />

between CC-certified security controls and safety assurance levels.<br />

• Are there better mechanisms to address the problem of how best to remove latent<br />

software bugs that can be attacked from software items <strong>in</strong> networked environments?<br />

While test<strong>in</strong>g probably provides part of the solution, it is obvious that test<strong>in</strong>g alone<br />

cannot warranty the absence of bugs for elements unexam<strong>in</strong>ed by the test suite. Because<br />

of the vast array of possible software bugs that can exist, it is improbable that a complete<br />

test<strong>in</strong>g corpus can be created. Therefore, best current practice is to cont<strong>in</strong>ue to enforce<br />

l<strong>in</strong>e-by-l<strong>in</strong>e code <strong>in</strong>spection with<strong>in</strong> the certification process for the highest assurance<br />

147

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

Saved successfully!

Ooh no, something went wrong!