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

More documents

Recommendations

Info

software items. Is there a security model or theory that could be discovered to authoritatively address this issue so that highly assured software could be definitively created within networked environments? • Industry has experience creating Bell-LaPadula Confidentiality Model, HAGs. However, there is little or no experience creating Biba Integrity Model HAGs. Therefore, there is a need to study and articulate the controls needed within Biba Integrity Model HAGs. This study should distinguish the differences (if any) between Biba Integrity Model HAG technology and Bell-LaPadula Confidentiality Model HAG technology. • What are the mechanisms that will integrate DoD and FAA certification processes and procedures? Is it possible to create a common certification system that reliably addresses safety in FAA environments and security in DoD environments, and both safety and security in joint certification environments? • Should Level D software systems be treated as Requirement 1 systems and organized into VPN enclaves as this study currently states (see section 8.2), or should they rather become Requirement 2 systems and not be enclaved into network partitions (VPNs) such as Level E systems? 12. REFERENCES. 1. ARP 4754, “Certification Considerations for Highly-Integrated or Complex Aircraft Systems,” 1996, SAE International, 400 Commonwealth Drive, Warrendale, PA 15096- 0001. 2. ARP 4761, “Guidelines and Methods for Conducting the Safety Assessment Process on Civil Airborne Systems and Equipment,” 1996, SAE International, 400 Commonwealth Drive, Warrendale, PA 15096-0001. 3. 14 CFR 23.1309, Equipment, systems, and installations, Revised January 1, 2006. 4. 14 CFR 25.1309, Equipment, systems, and installations, Revised January 1, 2006. 5. RTCA/DO-178B, “Software Considerations in Airborne Systems and Equipment Certification,” December 1, 1992, Prepared by SC-167. 6. RTCA/DO-254, “Design Assurance Guidance for Airborne Electronic Hardware,” April 19, 2000, Prepared by SC-180. 7. Knight, J., “Software Challenges in Aviation Systems,” NASA Grant number NAG-1- 2290, 2002. http://dependability.cs.virginia.edu/publications/safecomp.2002.pdf 8. FAA Advisory Circular 120-76A, “Guidelines for the Certification, Airworthiness, and Operational Approval of Electronic Flight Bag Computing Devices,” March 17, 2003. 148
9. Lee, Y., Rachlin, E., and Scandura, Jr., P., “Safety and Certification Approaches for Ethernet-Based Aviation Databuses,” FAA report DOT/FAA/AR-05/52, December 2005. 10. Yost, R., “Airplanes can be Networked,” Abstract, American Institute of Aeronautics and Astronautics, 2002. 11. Donohue, G.L., “Air Transportation is a Complex Adaptave [SIC] System: Not an Aircraft Design,” American Institute of Aeronautics and Astronautics, 2003. 12. Buede, D., Farr, J., Powell, R., and Verma, D., “Air Traffic Management Design Considerations,” IEEE AES Systems Magazine, October 2003, pp. 3-8. 13. U.S. Department of Transportation Federal Aviation Administration Order 1370.82. Subject: Information Systems Security Program, June 9, 2000, Initiated by AIO-1, distribution A-WZYZ-2; A-FOF-O. 14. “The Transnational Dimension of Cyber Crime and Terrorism,” Abraham D. Sofaer and Seymour E. Goodman, eds., Hoover Institution Press, 2001. 15. Birman, K., “The Untrustworthy Web Services Revolution,” IEEE Computer Magazine, February 2006, pp. 98-100. 16. Campbell, S., “How to Think About Security Failures,” Communications of the ACM, Volume 49, Number 1, January 2006, pp. 37-39. 17. “Future Communications Study: Initial Discussion of Radio Frequency Security Requirements, Version 1.5,” prepared by FAA ACB-250, April 10, 2005. 18. Mehan, D., “Information Systems Security: The Federal Aviation Administration’s Layered Approach,” Transportation Research Board National Research Council, November-December 2000, TR NEWS—Transportation Security—Protecting the System from Attack and Theft, Number 211. 19. Mehan, D. and Potter, M., “Building Trustworthy Systems: An FAA Perspective,” Software Technology News, Volume 4, Number 3, Federal Aviation Agency Issue, Data & Analysis Center for Software, Rome, NY, 2001. 20. Federal Aviation Administration Information System Security Technology Overview, Version 2.0, Prepared by The MITRE Corporation for the Office of Information Services, September 30, 2003. 149
Page 1 and 2:
DOT/FAA/AR-08/31 Air Traffic Organi
Page 3 and 4:
1. Report No. DOT/FAA/AR-08/31 4. T
Page 5 and 6:
5.4.2 Aircraft as a Node (MIP and M
Page 7 and 8:
11.1 Findings and Recommendations 1
Page 9 and 10:
22 Customer’s L3VPN Protocol Stac
Page 11 and 12:
LIST OF ACRONYMS AND ABBREVIATIONS
Page 13 and 14:
PBN PC PE PEP PFS PIB PIM-DM PIM-SM
Page 15 and 16:
This report states that the primary
Page 17 and 18:
1. INTRODUCTION. This is the final
Page 19 and 20:
protocol (IP)-based communications.
Page 21 and 22:
of linking aircraft-resident system
Page 23 and 24:
Industry and governments are extrem
Page 25 and 26:
2.1 NOTIONAL NETWORKED AIRCRAFT ARC
Page 27 and 28:
Other Control Sites Controller ATC
Page 29 and 30:
• The security viability of curre
Page 31 and 32:
alternative requires that parallel
Page 33 and 34:
Aircraft network security is a syst
Page 35 and 36:
4. NETWORK RISKS. This section spec
Page 37 and 38:
General Threat Identifiers FAILURE
Page 39 and 40:
esources so that the required real-
Page 41 and 42:
“With the rise of client-side att
Page 43 and 44:
• During an 11-month period (Apri
Page 45 and 46:
attempt the theft of passwords. Non
Page 47 and 48:
IP networks are organized in terms
Page 49 and 50:
either the user or the trusted soft
Page 51 and 52:
However, the previous paragraph beg
Page 53 and 54:
Table 1. Internet Engineering Task
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
• Lightweight directory access pr
Page 61 and 62:
mechanism to overcome the key distr
Page 63 and 64:
Deployments that need to support mu
Page 65 and 66:
Today’s Reality: Islands of Commu
Page 67 and 68:
Simultaneously, IP addresses are al
Page 69 and 70:
in-depth manner. Defense-in-depth m
Page 71 and 72:
Protection Detection Reaction / Neu
Page 73 and 74:
encrypted and then encapsulated wit
Page 75 and 76:
Internet (grouping of autonomous sy
Page 77 and 78:
via that same IP address. Specifica
Page 79 and 80:
deployments. Regional flights that
Page 81 and 82:
neighbor as a next hop after “Hol
Page 83 and 84:
Interface Interface Customer Site S
Page 85 and 86:
Interface Customer’s Application
Page 87 and 88:
Although the vast majority of PBN s
Page 89 and 90:
6. RELATING SAFETY AND SECURITY FOR
Page 91 and 92:
6.1.1 Integrity. As section 4.3 ind
Page 93 and 94:
As mentioned in section 4.4, the hi
Page 95 and 96:
6.1.4 Confidentiality. Confidential
Page 97 and 98:
their own classification level nor
Page 99 and 100:
integrity is not permitted to obser
Page 101 and 102:
software has been confirmed as leve
Page 103 and 104:
• Both safety and security are co
Page 105 and 106:
Device at Safety level X Device at
Page 107 and 108:
in a Biba Integrity Model environme
Page 109 and 110:
Common Criteria Classes ACM—Confi
Page 111 and 112:
(see section 9.10). A secure mechan
Page 113 and 114: employed in security-critical appli
Page 115 and 116: concept, which is needed to create
Page 117 and 118: 4. Learn from past mistakes. Poor d
Page 119 and 120: exemplar airborne network architect
Page 121 and 122: • Requirement 8: Biba Integrity M
Page 123 and 124: Figure 31 shows how the recommended
Page 125 and 126: to-live (TTL) field in the IP heade
Page 127 and 128: using the traditional dual router i
Page 129 and 130: mechanism relies upon the controlle
Page 131 and 132: HAGs are high-assurance devices tha
Page 133 and 134: 8.3.5 Firewall. The firewall needs
Page 135 and 136: (AJ) or low probability of intercep
Page 137 and 138: design decisions that need to be de
Page 139 and 140: 9.2 INTEGRATED MODULAR AVIONICS IMP
Page 141 and 142: 9.3 USING PUBLIC IPs. The model and
Page 143 and 144: alerted the pilots because the fail
Page 145 and 146: environments. If the certification
Page 147 and 148: DSS (FIPS 186 [81]). Code signing i
Page 149 and 150: elationship with other equipment in
Page 151 and 152: approach is to keep the log informa
Page 153 and 154: 11. SUMMARY. Current civilian aircr
Page 155 and 156: environments should be extended to
Page 157 and 158: 12. COTS computer systems cannot be
Page 159 and 160: 14. NAS and airborne network archit
Page 161 and 162: 22. If SWAP considerations permit,
Page 163: 11.2 TOPICS NEEDING FURTHER STUDY.
Page 167 and 168: 32. Loscocco, P., Smalley, S., Muck
Page 169 and 170: 59. Raisinghani, V. and Sridhar, I.
Page 171 and 172: the following is a pointer to a rel
Page 173 and 174: Department of Defense Instruction N
Page 175 and 176: Information Assurance—The Departm
Page 177 and 178: Threat source—Either (1) intent a
Page 179 and 180: information found within these data
Page 181 and 182: (HTTP) traffic (port 80), port scan
Page 183 and 184: The simple network management proto
Page 185 and 186: opportunities to crack the hosting
Page 187 and 188: authorized to perform. 13 However,
Page 189 and 190: sniffers, log-cleaning scripts, and
Page 191 and 192: A.3.1 DENIAL OF SERVICE ATTACKS. Th
Page 193 and 194: • Disclosure: Disclosure of routi
Page 195 and 196: affected by the signal intermittenc
Page 197 and 198: A-15. Barbir, A., Murphy, S., and Y
Page 199 and 200: Survey Question What is the primary
Page 201 and 202: Survey Question What is the primary
Page 203 and 204: should be emphasized that there is
show all

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

Create successful ePaper yourself

Delete template?

Save as template?