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

More documents

Recommendations

Info

Threats / Hazards Ops Environment Technology Vulnerability Analysis Design Concepts FAA safety Security requirements Working Group IA Security Criteria Criteria Analysis Security Specification Requirements Countermeasures Adversary Analysis Baseline Design Concept Lessons Learned Trade-Off Studies System Security Security Specification Development Entry into Development Figure 29. Security Engineering Process The Systems and Software Consortium 31 has developed well-accepted SSE processes. Their generic approach can be summarized by the following steps. 1. Determine the security policies. This is a high-level definition of what is allowed and what is forbidden within the system. The policies provide the basis for determining the security requirements that will be developed and implemented. Without good security policies, one cannot determine the high-value assets and data that must be protected. 2. Determine and specify the security requirements. In this step, requirements for the protection of assets and data are determined using the security policies as a guide. It is essential that only requirements be specified, not solutions or constraints. Therefore, the requirements must be stated in technology neutral terms. In addition, the requirements must be practical and testable to permit eventual verification that the requirements have been satisfied by the final system. Finally, the security requirements should not be open to interpretation. This is accomplished in high-assurance systems by specifying the security design via mathematical formalisms. However, this is rare. In most cases, English is used to specify the requirements. Care must be taken to avoid ambiguity of meaning. 3. Establish a security engineering plan. This plan should include items critical to the design and implementation of the security protection mechanisms. Such items include the security requirements, constraints, and decisions already made. It should be used to help allocate the resources needed to properly complete the project while simultaneously establishing realistic expectations. 31 See http://www.software.org 100
4. Learn from past mistakes. Poor development practices typically result in security vulnerabilities. By examining these past development practices and identifying those that improve or hinder system security, valuable lessons can be obtained and future implementations improved. 5. Document the operational environment. This is typically done in a document called the Concept of Operations (CONOPS). It describes the environment in which the system will operate, the roles and responsibilities of the major players, how the system is designed to normally operate, and potential contingency modes of operation. The security environment can be included in the CONOPS as a separate section or included in its own document (a Security CONOPS.) Elements of this security CONOPS should include a reiteration of the security requirements, the process used to select all countermeasures, how defense-in-depth is implemented, how the security mechanisms will operate, including user impacts, the effectiveness of the implemented countermeasures, how misuse is prevented or detected, the response mechanisms to a misuse incident, and the recovery process, if needed. 6. Perform a risk analysis. The risk analysis examines the operational environment to determine high-value assets, the threats to these assets, their vulnerabilities, countermeasures needed to reduce the risk for each threat/vulnerability pairing, and validation of the cost effectiveness of each countermeasure. For airborne environments, this approach differs from the traditional security engineering process by including safety as a key factor. It also differs from traditional safety analysis by considering the possible effects of malicious actions. In more detail, the first step is to determine the high-value assets to assist in focusing where the limited security dollars should be spent. In placing a value on each asset, the cost effectiveness of the selected countermeasures can later be determined. Once the assets are determined, each threat, which is asset- and environment-dependent, must be ascertained. In conjunction with this, the vulnerabilities of these assets must also be determined. Once the threats and vulnerabilities are determined, each threat is matched with the appropriate vulnerability. Any vulnerability without a threat or vice versa can be ignored. Otherwise, countermeasures are selected to reduce the threat and the cost of the countermeasures determined. A tradeoff is then performed between threat and vulnerability matches, countermeasure costs, and protected asset value. 7. Design the security architecture using the above information. The above risk analysis will identify the areas requiring protection and the cost-effective countermeasures requiring implementation. The security design should be consistent with accepted best practices. One such best practice is the concept of defense-in-depth (discussed in section 3.5). This concept uses the medieval castle as its model. Multiple layers of defense are implemented so that when one layer is successfully penetrated, other layers of protection still exist. While it is widely accepted that no security mechanism is foolproof, an architecture implementing the defense-in-depth concept should sufficiently delay the attacker to allow for the detection of the attack and to implement an appropriate response. This assumes that full control life cycles have been implemented to enable attack detection and response. Other best practices include least privilege, object reuse, 101
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: concept, which is needed to create
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 and 164: 11.2 TOPICS NEEDING FURTHER STUDY.
Page 165 and 166: 9. Lee, Y., Rachlin, E., and Scandu
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?