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

More documents

Recommendations

Info

• Corrupted or Careless Insider • Are authorized to access the network • E.g., NAS personnel, aircraft personnel or passengers, local systems • Hostile Outsider • Are not authorized to access the network • May be located on “the Internet” • Client-side Attacks • Malicious software lurking in “neutral” environments (e.g., email, web sites, other) • The historic distinction between “data” and “code” is vanishing • NAS personnel, aircraft personnel, and aircraft passengers may be duped into inadvertently executing, and thereby introducing, malicious software into the network • Network users therefore have become an integral element of a network’s security defenses Figure 9. Threat Agents in a Networked Environment This topic will resume in section 4.4 when the implications of mixing embedded systems and generic OSs within the same network will be discussed. Before that discussion can occur, however, it is first necessary to discuss the vulnerabilities that exist within a networked environment. 4.3 COMMERICIAL OFF-THE-SHELF VULNERABILITIES IN A NETWORKED ENVIRONMENT. While this section specifically addresses well-known COTS vulnerabilities in networked environments, similar problems may or may not exist within embedded avionics systems, depending upon whether latent bugs exist within those systems that can be exploited by network attacks. Lance Spitzner has gathered together the following statistics, which provide partial evidence that the worldwide Internet infrastructure is a very dangerous place: • “At the end of the year 2000, the life expectancy of a default installation of Red Hat 6, a commonly used version of Linux [a computer OS], was less than 72 hours. • One of the fastest recorded times a honeypot [i.e., a device deployed in order to study the behavior of electronic attackers] was compromised was 15 minutes. This means that within 15 minutes of being connected to the Internet, the system was found, probed, attacked, and successfully exploited by an attacker. The record for capturing a worm was under 90 seconds. 26
• During an 11-month period (April 2000-March 2001), there was a 100 percent increase in unique scans and an almost 900 percent increase in Intrusion Detection Alerts, based on Snort [an Intrusion Detection utility]. • In the beginning of 2002, a home network was scanned on average by 31 different systems a day.” [26] This list can be supplemented by many other data points including: • “The most virulent [computer] virus to date infected several million machines in about 20 minutes….” [15] • “When we put this [honeypot] machine online it was, on average, hit by a potential security assault every 15 minutes. None of these attacks were solicited, merely putting the machine online was enough to attract them. The fastest an attack struck was mere seconds and it was never longer than 15 minutes before the honeypot logged an attempt to subvert it. … • At least once an hour, on average, the BBC honeypot was hit by an attack that could leave an unprotected machine unusable or turn it into a platform for attacking other PCs. … • By using carefully crafted packets of data, attackers hope to make the PC run commands that hand control of it to someone else. Via this route many malicious hackers recruit machines for use in what is known as a botnet. This is simply a large number of hijacked machines under the remote control of a malicious hacker.” [27] • “IronPort recently published a report showing that Trojan horses and system monitors – two of the most serious types of malware – infect one out of every 14 corporate PCs. That means that in an organization of 1,000 desktop PCs, there is an average of 70 computers that represent a major security risk. … Dwarfing Trojans and system monitors are less serious types of malware, such as adware and tracking cookies, which infect 48% and 77% of PCs, respectively.” [28] • “The number of new [COTS] software security vulnerabilities identified by security experts, hackers and others during the first eight months of this year [2006] has already exceeded the total recorded for all of 2005, according to Internet Security Systems. Vulnerabilities through September have reached 5,300, leaping past the 5,195 discovered for all of 2005, says Gunter Ollmann, director of the X-Force research group at ISS. ‘Eight hundred seventy-one were found to affect Microsoft operating systems, while 701 vulnerabilities were only found to affect Unix operating system,’ Ollmann says. But many vulnerabilities cross platform 27
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: “With the rise of client-side att
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 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 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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?