TSA Information Assurance Handbook
Total Page:16
File Type:pdf, Size:1020Kb
TRANSPORTATION SECURITY ADMINISTRATION INFORMATION TECHNOLOGY INFORMATION ASSURANCE AND CYBERSECURITY DIVISION TSA Information Assurance Handbook Attachment 1 to TSA MD 1400.3 IT Security Date Signed: 07/27/2018 Paul D. Morris (Executive Director, CISO) Version 14.0 Records Disposition Schedule (RDS) Policy Records Code and Item: 2000.4.1 PERMANENT: Cut off at the end of calendar year in which superseded or obsolete. Transfer to NARA 10 years after cut off. [Authority N1-560-04-10, Item 5b] INFORMATION TECHNOLOGY INFORMATION ASSURANCE HANDBOOK This Page Intentionally Left Blank Page 2 of 273 INFORMATION TECHNOLOGY INFORMATION ASSURANCE HANDBOOK Table of Contents TSA Information Assurance Handbook ............................................................................................ 1 Table of Contents ............................................................................................................................... 3 1. Purpose ....................................................................................................................................... 4 2. Scope .......................................................................................................................................... 4 3. Policy .......................................................................................................................................... 7 4. Roles and Responsibilities ...................................................................................................... 226 5. Definitions .............................................................................................................................. 244 6. Abbreviations ......................................................................................................................... 255 7. Acknowledgements ................................................................................................................ 261 8. Authorities .............................................................................................................................. 262 9. Document Change History ..................................................................................................... 264 10. Document Control Information .......................................................................................... 265 11. Effective Date and Implementation .................................................................................... 265 12. Appendix A - References (Federal Information Assurance (IA) Policy Mandate -- Top- Down Alignment Diagram and Detailed Authorities): .................................................................. 266 Page 3 of 273 INFORMATION TECHNOLOGY INFORMATION ASSURANCE HANDBOOK 1. Purpose This handbook implements the policies and requirements of the Transportation Security Administration (TSA) Management Directive (MD) 1400.3, Information Technology Security by establishing guidance applicable to the use, development, and maintenance of TSA Information Technology (IT) assets, networks, and systems. The guidance contained herein is designed to ensure the Confidentiality, Integrity, Availability, and overall assurance of TSA information. This handbook is supplemented by published extension documents, TSA Technical Standards (TSs), and Standard Operating Procedures (SOPs). The IA HB, TSs, SOPs and other relevant documents are published in the IA Policy Outreach page. This document is used to identify responsibilities by educating and increasing awareness of TSA information assurance (IA) policy. An accountability matrix containing roles and responsibilities of key personnel mentioned in this Handbook can be found in an Information Assurance (IA) Roles and Responsibilities spreadsheet located in our IA Policy Outreach site. References to the specific areas and authorities to enable successful execution of tasks and job requirements are identified herein. Appendix A (References) located in the back of this Handbook contains a Figure 1 diagram, which illustrates a top-down approval and alignment order as derived IAW federal policy mandates. 2. Scope The policies within this handbook apply to all TSA employees, contractors, vendors, detailees, others working on behalf of TSA, and to non-TSA individuals authorized to access TSA information systems, software and/or applications. It also applies to all TSA information systems, software and/or applications that collect, generate, process, store, display, transmit, or receive TSA data, including prototypes and telecommunications systems, in all phases of the Systems Engineering Life Cycle (SELC) unless an approved waiver has been granted using the proper waiver form. The above assets shall be collectively referred to as "IT assets" throughout the document. As required by the Department of Homeland Security (DHS), the Federal Chief Information Officer (CIO) and Office of Management and Budget (OMB) guidance, program and project managers shall be provided with guidance to support the implementation of Agile Information Technology (IT) Development. Requirements shall reference the DHS “Carwash” User Guide, the DHS Directive System Instruction Number 102-01-004: Agile Development and Delivery for Information Technology and the DHS Agile Center of Excellence - Tools. These guides enhance understanding as to why Agile is a preferred approach to federal IT development, how it provides a starting point for increasing DHS-wide application of Agile methodologies, and helps managers and other key stakeholders identify options for tailoring the SELC for Agile. The private sector uses Agile as an effective and efficient method to deliver software faster, better, and cheaper compared to other methods. Important note for System Owners (SOs) and Information Systems Security Officers (ISSOs) – In the context of this IA Handbook, the term “System” is synonymous with “Application” and “Software”, and the expectation for adherence is the same. The structure of this document is based on the controls contained in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations. Information on privacy controls and related privacy overlays can be found here. Furthermore, the controls identified are mapped to Federal Page 4 of 273 INFORMATION TECHNOLOGY INFORMATION ASSURANCE HANDBOOK Information Processing Standards (FIPS) Publication 199, Standards for Security Categorization of Federal Information and Information Systems, which establishes the foundation for categorizing systems based on three security objectives: Confidentiality, Integrity, and Availability (C, I, A). These publications, and other relevant NIST guidance, are available online at http://csrc.nist.gov/. Security objectives are assigned a potential impact level, also known as “impact level” throughout this handbook, of Low, Moderate, or High. Within the tables of requirements in this document, the applicability of each control statement is provided in the “Category” column with the following abbreviations: Low (L), Moderate (M), High (H), Privacy System (P), or Chief Financial Officer (CFO) Designated Financial System (F). Definitions for terms are located in Section 5 Definitions. For definitions not identified, the NIST Glossary of Key Information Security Terms shall be used as a baseline for reference. The DHS Sensitive Systems Policy Directive 4300A, and its supporting Handbook, shall take precedence in instances where there is conflict with TSA MD 1400.3 ITS and this supporting handbook, unless otherwise identified in TSA policy. With the DHS Trusted Internet Connection (TIC) infrastructure initiative as mandated by OMB M- 08-05, this TSA IA Handbook and its extension documents shall address the expansion in scope from a current TSA-only management service function to a DHS entity entrusted in providing a more centrally managed Semi-Trusted/DMZ environment. The overall purpose of the DHS TIC effort is to optimize and standardize the security of individual external network connections (extranet services) currently in use by the TSA and other agencies. Regarding vulnerabilities, weaknesses and mitigations, POA&Ms shall not exceed the maximum duration for closure based on FIPS 199 impact levels for the system: 45 days (for high), 60 days (for moderate), and 90 days (for low). NOTE: Based on directions from the DHS USM Memo titled “Strengthening DHS Cyber Defenses” (July 22, 2015), a unique type of “High” impact level category classified as “Critical” may be used under certain circumstances and in response to escalation in cyber related attacks. Weaknesses or vulnerabilities identified as Critical by the National Cybersecurity Assessment and Technical Services (NCATS) must be mitigated within 30 days. This newly created Critical impact is also supported by the Binding Operational Directive (BOD) 15-01: “Critical Vulnerability Mitigation Requirement for Federal Civilian Executive Branch Departments’ and Agencies’ Internet-Accessible Systems”. In these special cases, subsequent instructions shall be forthcoming by the TSA Authorizing Official (AO). Those systems not in compliance with this 30-day mitigation requirement risks being shut down or removed from the network at the discretion of the AO. The CISO has the flexibility and the resources to work with DHS with the presumption that TSA has the full and complete trust in DHS from an architectural perspective to serve as the provider