1 federal aviation administration william j. hoffman cissp, ciso enterprise engineering services,...

1Federal AviationAdministration

William J. Hoffman CISSP, CISO

Enterprise Engineering Services, LLC.

This presentation is my own work. If I used data, ideas, words, diagrams, pictures, or other information from any source, I have cited them . The opinions, conclusions and recommendations expressed or implied are those of the author and do not necessarily reflect the views of the Federal Aviation Administration or the Department of Transportation

FAA Next Generation Air Transportation System

DHS / TSCP Collaboration

Identity and Access Management Discussion

2Enterprise Engineering Services, LLC.

What is What is NextGen? NextGen? Who are Who are

Collaboration Collaboration Partners?Partners?• Federal Aviation Administration

(FAA)• National Aeronautics and Space

Administration (NASA)• the Department of Commerce

(DoC) / National Oceanic and Atmospheric Administration (NOAA)

• Department of Defense (DoD• Department of Homeland Security

(DHS)

FAA Interagency Planning Office for NextGen ∙ 55 M Street SE 8th Floor Washington DC 20003 ∙ 202-267-4963


US, Eurocontrol , ICAO & Cyber HarmonzationUS, Eurocontrol , ICAO & Cyber Harmonzation


The Aeronautical Information Exchange Model (AIXM)The Flight Information Exchange Model (FIXM)The Weather Information Exchange Model (WXXM)


FAA NAS Identity and FAA NAS Identity and Access Management Access Management

(IAM) Planned (IAM) Planned Enterprise ServicesEnterprise Services

https://nasea.faa.gov/products/roadmap/main/display/10

NextGen & DHS Cyber Security NextGen & DHS Cyber Security FrameworkFramework

2015-2017 ,Authentication –US Common Policy Compliant PKI credentials and others approved by FAA policy2016-2018 ,Authorization - OASIS based standards to include FICAM SAML and XACML 2017-2019 ,Federation FAA and Industry Assess alternatives for Implementation FAA provide Partner Policy and Guidance for Federation


Feb 2015 FAA/DHS/TSCP IAM Collaboration Feb 2015 FAA/DHS/TSCP IAM Collaboration MeetingMeeting

Attendees

Jim Daum, FAA Enterprise Safety and

Information Security Division Manager

John Chung, FAA Information Security Branch Manager

Kelly Mesveskas, FAA SWIM Prototype Lead

Frank Happel, FAA NAS ISS Engineering Team Manager

Jim Laymon, FAA NAS IAM Development and

Implementation Team Lead

Keith Ward, TSCP Director

Philippe Laflandre, Airbus ICAM VP

Bill Hoffman, EES Chief Information Security Officer

John Daniels, EES Federal Programs VP

Overview

Keith - proposed Pilot Program plan for FAA to demonstrate IAM technologies

Philippe - stressed the value and scope of these investments; as well as need for continued international harmonization

Jim Daum - stressed need of identifying FAA requirements related to IAM collaboration efforts

Action/Results

• Bill Hoffman to collaborate with TSCP to develop Pilot Program to demonstrate TSCP Trust Framework in the Aeronautical Information Management (AIM) domain; particularly the use of a digital credential by AIM stakeholders to access data and/or services.

• Keith Ward indicated that TSCP may be able to obtain funding through DHS Science & Technology by submitting white-paper.

• TSCP, Airbus, and EES will work together to produce white-paper approach.

• FAA will determine viability of AIM Program as target source.


Pilot Plan – team with Airport Council International/ North Pilot Plan – team with Airport Council International/ North America & use DHS/TSCP frameworkAmerica & use DHS/TSCP framework

Criteria for Selection of Participating Criteria for Selection of Participating Airport AuthoritiesAirport Authorities

The proposed pilot calls for 3 Airport authorities to participate that were recommended by Chris Oswalt and Matt Griffin of the Airport Council International, North America at the NextGen Federated Identity Credentialing and Access Management (FICAM) Workshop June, 2013 meeting.Recommended participation:•Port Authority of NY and NJ•Denver International Airport•Los Angeles World Airports Authority

During discussions with Chris Oswalt, the selection of these 3 was based on:1. Geographic diversity.2. Available resources to include very technically competent personnel. 3. All have significant on airport law enforcement personnel, interactions with external Law enforcement and various organizations within DHS and emergency response operations.4. All have significant interactions with Aviation Military operations functional entities and on airport Military and or Coast Guard Fleet assets.5. Approximately 40% to 50% of all international flights originate and terminate at airports controlled by them which will help international airport operators buy into this collaboration effort and ACI NA would help bring them on board.6. PANYNJ and LAWA control the 2 largest General Aviation and Business jet airports in the world (Teterboro and Van Nuys) which will help with future collaboration efforts with AOPA and the Business Jet owners associations.

Team will deliver an operational pilot using a Federated Aviation Information Cloud Service (FAICS) capability in a production-ready mode


Operational Concept Operational Concept Pilot Scenario Details1. Airport modifications and safety assessments - Sally works for the City & County of Denver Department of Aviation, which provides data to FAICS about new construction projects at Denver (DEN) airport that may impact aircraft missed approach or other procedures.2. Emergency Response Operations - Keith works at the Port Authority of NY & NJ (PANYNJ) and has a contract to provide data to the FAICS for use by the City of New York Command Center, FAA Aeronautical Common Service (ACS), FAA Emergency Operations Network (EON), and the DHS Homeland Security Information Network.3. Law Enforcement Operations. John works for the Drug Enforcement Administration Office of Diversion Control Angeles Field Division. He has received credible information that a flight originating in Mexico that will land at the VNS airport has controlled substances aboard, as well as a senior drug cartel member. Coordination is required between FAA and LAWA.

Table 1. Use case and LOA 2-4 credential types

Use Case Data Consumer Data Provider

Entity

LOA 2-4Credential Types

Entity LOA 2-4

Credential Types

1a NY Port

Authority PIV-I / non PIV-I FAA/DHS NPE

1b FAA/DHS PIV NY Port Authority NPE /PIV-I / non

PIV-I

2a Denver PIV-I / non PIV-I FAA PIV/NPE

2b FAA PIV/NPE Denver PIV-I / non PIV-I

3a LAX PIV-I / non PIV-I FAA/ DHS/ DOD PIV/NPE

3b FAA/ DHS/

DOD PIV/NPE LAX PIV-I / non PIV-I

Roles for Operational Concept


Technical Concept - Technical Concept - Team will deliver an operational pilot using Team will deliver an operational pilot using

the the Federated Aviation Information Cloud Service (FAICS) Federated Aviation Information Cloud Service (FAICS) in a in a

production-ready modeproduction-ready mode. . Subsystem Technical Solution Implementation

A) Trust Framework

TSCP Trust Framework Services

Credential Providers: Both Personal Identity Verification Interoperability (PIV-I) and two-factor, non-PKI Credential Providers will be enabled

B) Data Providers

Use VM technology – FAISC and FAA CyTF lab

FAA simulated one Stop Shop Portal and messaging services (JMS, other) Airport Operator Simulation message non-CUI and CUI to Airports provider,

Airport simulated messages to FAA – Non-CUI, CUI include NOTAMs (ACY, JFK, LAX, and DEN)

DHS, DoD, and Local Law enforcement Emergency Response messaging to FAA – non-CUI and CUI to FAA

Flight Operations messaging – non-CUI and CUI (mostly from DOD, DHS, and Law enforcement entities) to FAA

C) Data Consumers

Airports Access Simulated FAA AIM one stop Shop Portal and messaging services (JMS, other) non-CUI and CUI

FAA consumes Airport simulated messages to FAA – Non-CUI, CUI include NOTAMs (ACY, JFK, LAX, and DEN)

FAA to DHS, DoD, First Responders, and Local Law enforcement Emergency Response messaging – non-CUI and CUI to FAA

FAA Flight Operations messaging – non-CUI and CUI (mostly from DOD, DHS, and Law enforcement users) to Air Operations personnel (ACY and or JFK, LAX, DEN)

D) Identity Services / Attribute Exchange Network

Attribute Exchange Network

Level of Assurance (LOA) 3 Verifier: two-factor, non-PKI credential authentication

LOA 4 Verifier: FAISC for PKI path discovery and validation as well as CRL checking

Attribute Provider: FAISC Attribute Directory which has implemented user role and attributes

E) Federation and Directory Services

Federation Services software to manage federated connections and support Security Assertion Markup Language (SAML) 2.0 protocol which has implemented the FAA tailoring SAML 2.0 profiles developed for the project.

F) Attribute Based Access Control Services

Entitlement Management for Microsoft SharePoint solution (Policy Enforcement Point)

Control Center is an Information Control Platform (ICP) that turns business policy into automated information controls for data access, use, and sharing across server, client, and cloud applications (Policy Administration Point and Policy Decision Point)

G) Application Services

Microsoft SharePoint 2013

Possible Aeronautical Common Services for FAICS

Mapping Service – a Web Map Service (WMS) that provides map and aeronautical feature imagery that can be used to display maps

ACS Query – The Aeronautical Common Service Query service is a Web Feature Service (WFS) that executes a user-submitted query and returns the aeronautical features (e.g., airports, Special Use Airspace (SUA), SUA schedules, navaids, obstacles, procedures, and NOTAMs) that match that query

ACS Notification – The Aeronautical Common Service Notification publishes notifications to users of updates to aeronautical features (e.g., airports, Special Use Airspace (SUA), SUA schedules, navaids, obstacles, procedures, NOTAMs) to which they have subscribed.


Pilot Goals and ObjectivesPilot Goals and Objectives

Support Department of Homeland Security’s (DHS) specific mission to develop “advanced cyber security and information assurance solutions to secure the Nation’s current and future cyber and critical infrastructures against persistent threats and dynamic attacks” with particular attention to CSD.05, Identity Management. DHS S&T help the advancement of FAA IAM initiatives as depicted in the NAS Infrastructure Roadmap.

Goals/Objectives 1.Conduct a pilot for FAA’s mission need to perform IAM for its service-oriented architecture

– data source provider confidence aviation Controlled Unclassified Information (CUI) data entered into the system will be shared with, and accessible only by, identity-vetted, authorized personnel. (e.g., civil aviation, space transportation, law enforcement, First Responders, DHS and DoD stakeholders etc.)

2. Develop business authorization rules for access control.

3. Create a policy framework (including a trust agreement) to enable data sharing.

4. Test the access management policy framework in a pilot environment with participants from FAA’s critical infrastructure relationships.

Use cases will simulate secure access to shared data transported within, and across, aviation systems and subsystems.

5. Leverage and expand the DHS Backend Attribute Exchange (BAE) to enable access control for shared aviation data.

6. Create, validate, and/or update existing TSCP and FAA Security documents and specifications


Identifying FAA Requirements related to IAM collaboration efforts.Identifying FAA Requirements related to IAM collaboration efforts.

1. Validate FAA SWIM Security Profile Specifications ( DRAFT ) for use and tailoring of SAML 2.0 profiles for messaging services that will be deployed and operated within the FAA System Wide Information Management (SWIM) Service Oriented Architecture (SOA) environment for information exchanges among NAS Stakeholders. Pilot would include Role attributes and CUI labeling.

Relationship to FAA Administrator Strategy - Industry, DHS and DOD Collaboration on adaptation of SAML standard, profiles and updates to FAA Specification.

2. Apply FAA/ ANG Security Label Definition Effort for Controlled Unclassified Information (CUI )

Relationship to FAA Administrator Strategy - Industry, DHS and DOD Collaboration on adaptation of CUI definitions and updates to FAA DATA Standards/NARA is requirement project will address.

3. Apply TSCP specifications where applicable for information labeling.

Relationship to FAA Administrator Strategy - Collaboration on adaptation of industry specifications.

4. Tailor the DHS Global Federated Identity and Privilege Management (GFIPM) Implementation Guidance for use by National Airspace System stakeholders (this work was started in 2012 but stopped based on FAA reorganizations)

Leverage role attributes already agreed to by FAA and DHS for Law enforcement, first responders and Search and Rescue participants.

Relationship to FAA Administrator Strategy – Federal partner - DHS and DOD Collaboration on adaptation of DHS First responder & law enforcement Operations -a work already accomplished with FAA and updates to FAA /aviation domain attributes project defined with participating Airport Authorities.

.

5. Leverage FAA’s CyTF IAM, AIMM and SWIM infrastructure to demonstrate interoperability

Relationship to ANG Cyber strategy – Pilot establishes framework for other partner use of CyTF where Policy based Identity and Access management interoperability piloting and or assessment are desired.


Big picture potential end game Big picture potential end game viewview

Common Support:Web Services Security, Data Standards & Harmonization

Networks:FTI & SWIM

are the basis for Network-Centric Operations

in FAA

Attribute Exchange

Network (AXN)

Aviation Trust Framework Provider (s)

Attribute Providers

Identity Providers (IdP)

Federated Aviation Information Cloud Service Concept of Operations

External Mission Services partner/ Data Producers and Consumers

12


Significance Of Pilot Significance Of Pilot DemonstrationDemonstration

• Establishment of an environment featuring cross organizational trust through Common Operating Rules– The application owner does not need to

issue any new credentials – Reduced costs of credential management– Reuse of existing strong credentials

• Automated enforcement of CUI & Intellectual Property Controls– Reduced business risks of data loss or

leakage• Allows the setup of a secure collaborative

environment– User friendly experience using sign on

screens users are familiar with– Rapidly deployable architecture

13

1 federal aviation administration william j. hoffman cissp, ciso enterprise engineering services,...

Documents