(AGIE) Using Internet Protocols - Aviation Committees - AEEC - AMC

More documents

Recommendations

Info

ARINC PROJECT PAPER 830 – Page 122.0 AGIE PURPOSE AND OBJECTIVESThese domains as defined in ARINC 664 include ACD, AISD and PIESD domains.The key to efficient operations is a single system (possibly partitioned) that sharesnetwork, computing and messaging resources while meeting privacy, security,certification/approval, and safety requirements. AGIE not only supports crossdomainmessaging, but also supports certified FAR Part 25 and operationallyapproved systems, data, and datalinks.2.5.2 Security ObjectivesAGIE’s approach allows flexible selection of features to meet the particularrequirements of the implementation, which may support a range of security,certification, and operating parameters. AGIE leverages security functions present inother layers and devices of the overall information systems environment. While thissection focuses on security, other aspects of security are functionally integrated intoother sections of this document where possible and appropriate.The overall approach taken for AGIE is to leverage existing standards and bestpractices to the maximum extent possible and/or practical while limiting theintroduction of new AGIE-unique security features. In particular, AGIE leverages tothe IETF Transport Layer Security (TLS) standard, ARINC 842 Standard and ATASpecification 42 as well as the security features that integral part of protocolschosen to be part of AGIE, e.g. TLS within AMQP.Actual AGIE security requirements are defined in Section 4.7.2.5.3 Security GuidanceAGIE security guidance is focused on functional requirements of the messaginglayer of the standard. Specific AGIE security guidance addresses: AGIE functions Interfaces to external systems AGIE administrative operationsAGIE security guidance specifically addresses user needs for protecting aviationdata including:1. Integrity (primary need):a. Protect messages from being tampered with at endpoints as well as intransitb. Prevent spoofed or unauthorized messages being injected into thesystemc. Authenticate and correctly authorize AGIE servers and clients to eachother2. Confidentiality:a. Prevent messages from being read or intercepted at rest or in transit3. Availabilitya. Minimize impact to timely message delivery resulting from attacks onAGIE system4. Monitoringa. AGIE system generates sufficient logging data for security monitoringpurposes, e.g., detection of bogus messages
2.0 AGIE PURPOSE AND OBJECTIVESAGIE security guidance intentionally does not specify:Airline IT security practicesPhysical securityARINC PROJECT PAPER 830 – Page 13Security functions for other layers of the IT system, e.g., end-to-end securityneeds of the applications2.5.4 Security AssumptionsSystem security specifications related to AGIE are not adequate by themselves andneed to be integrated with an organization’s overall security risk managementprocess.Applications and/or data requiring additional protections for sensitive user data areresponsible for protecting it end-to-end (application-to-application).AGIE operators and service providers need to design and operate their IT systemsand networks according to industry best practices for security. Requirements andguidance are defined in Section 4.7 and Section 5.6.
Page 2 and 3: ARINC PROJECT PAPER 830TABLE OF CON
Page 5 and 6: ARINC PROJECT PAPER 830 - Page 11.0
Page 7 and 8: ARINC PROJECT PAPER 830 - Page 31.0
Page 9 and 10: 2.0 AGIE PURPOSE AND OBJECTIVESARIN
Page 15: 2.0 AGIE PURPOSE AND OBJECTIVESARIN
Page 19 and 20: ARINC PROJECT PAPER 830 - Page 153.
Page 33 and 34: 4.0 AGIE FUNCTIONAL SPECIFICATIONAR
Page 67 and 68:
4.0 AGIE FUNCTIONAL SPECIFICATIONAR
Page 69 and 70:
4.0 AGIE FUNCTIONAL SPECIFICATIONAR
Page 71 and 72:
ARINC PROJECT PAPER 830 - Page 675.
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
6.0 AGIE PROTOCOL INTERFACESARINC P
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
ARINC PROJECT PAPER 830 - Page 83AP
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
APPENDIX BAGIE OPERATIONAL THREADSA
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
APPENDIX CAPPENDIX CAMQP THREAD MAP
show all

(AGIE) Using Internet Protocols - Aviation Committees - AEEC - AMC

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

Delete template?

Save as template?