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

More documents

Recommendations

Info

VPN that is provided to the customer only appears to the customer to be a subnetwork (e.g., point-to-point wide area network (WAN) link, multipoint LAN) within the customer’s own network. L2VPNs can be created by physically leveraging deployments of the service provider’s asynchronous transfer mode, frame relay, Ethernet encapsulation in IP, or multiprotocol label switching (MPLS, see RFC 2031) networks. • A Layer 3 Virtual Private Network (L3VPN) provides VPNs at the network layer (i.e., IP layer). In L3VPNs 20 , a network provider offers the customer a private network infrastructure via an IP layer service interface (see figure 20). Consequently, the VPN that the service provider provides for the customer may be any IP topology hierarchy entity (e.g., subnetwork, area, AS, or network of networks). L3VPN networks that are designed for heightened security use IPSec’s (see RFC 4301) ESP (see RFC 4305) in tunnel mode (e.g., see figure 21). Other technologies, in addition to IPsec, can be used to create other types of L3VPNs: BGP/MPLS, see RFC 2547 and reference 67), layer two tunneling protocol (see RFC 2661), IP/IP (see RFC 2003), and generic routing encapsulation (see RFC 2784). Figure 21 shows a Layer 3 VPN example. This specific example is an IPv4 network that is using IPsec in tunnel mode to create the VPN. Note that this figure is essentially the same as figure 17, which showed how DoD COMSEC works in the DoD’s GIG network. RIPH RIPP ESP BIPH Red IP Header (Red = inner IP layer = IP Layer used by the End Users) End user’s original data payload IPsec ESP Header & Trailer Black IP Header (Black = outer IP layer) 100.1.1.4 100.1.1.1 Workstation RIPHRIPPRIPP Destination 100.1.6.1 Source 100.1.1.4 RIPH RIPP Destination 100.1.6.1 Source 100.1.1.4 Workstation 100.1.6.1 100.1.3.1 VPN Encapsulation 200.1.1.1 BIPH ESP RIPH RIPP ESP Destination 200.1.4.1 Source 200.1.1.1 BIPH ESP RIPH RIPP ESP VPN Encapsulation 200.1.4.1 Black IP BIPH ESP RIPH RIPP ESP BIPH ESP RIPH RIPP ESP Black IP 200.1.2.1 200.1.3.1 Black “Service Mobile Provider” Intranet 1 Network Figure 21. Example of VPN Encapsulation Using IPsec Service providers provide L3VPN services by encapsulating an extra IP layer to the customer’s IP layer protocol stack (see figure 22). 20 See http://www.ietf.org/html.charters/l3vpn-charter.html 68
Interface Customer’s Application Layer Customer’s Transport Layer Customer’s IP Layer Service Provider IP Layer Data Link Layer Original Private Customer Network Packet Encapsulated Packet Header from Service Provider Figure 22. Customer’s L3VPN Protocol Stack Shown Within the Network Service Provider’s Network Specifically, the service provider provides an interface above its own IP layer for the customer to use to access the service provider’s network. Figure 22 shows a common L3VPN protocol stack example where two IP layer protocols exist: one for the virtual network (i.e., the underlying service provider network) and one for the customer’s own IP. Because the service provider’s IP layer is an encapsulating redundant IP instance, it ensures that end-systems within the two network systems cannot communicate or be aware of each other (i.e., end-systems have only one IP layer protocol, not two). In this manner, the customer uses the service provider’s network without being aware of other traffic using that same network, because the network traffic within the service provider’s network occurs at the encapsulating IP layer, which the customer cannot see. It is similarly unable to access any devices directly attached to that network, nor can those devices access the customer’s network because they only support a single IP layer and cannot see an (encapsulated) two IP layer protocol stack. It should be explicitly noted that the virtual part of the VPN occurs because of the abstraction that the service provider’s network is solely supporting the customer: The other customers using that network infrastructure are not aware of each other’s existence. L3VPNs are, therefore, an instance of multilevel network systems (see section 5.4.3). RFC 4110, RFC 4111, and RFC 4176 provide architectural guidance for the creation of L3VPN network deployments. L3VPNs are an instance of multilevel network systems (see section 5.4.3). 5.7 SECURITY ZONES AND POLICY-BASED NETWORKING. Policy-based networking (PBN) is a mechanism to create adaptive networking systems that continuously tune the network to achieve goals established by the network administrator. For example, it promises enterprises the ability to define business rules that can be translated into security or QoS policies that configure and control the network and its services as they evolve over time. While the approach sounds directly relevant to the topic of this study, this section explains why that is not the case. The final conclusion is that all open PBN alternatives have 69
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 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: Interface Interface Customer Site S
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?