Volume II: appendices to guide for mapping types of ...

1 NIST Special Publication 800-60 Volume II Revision 1 Volume II: appendices to guide for mapping types of Information and Information Systems to Security Categories Kevin Stine Rich Kissel William C. Barker Annabelle Lee Jim Fahlsing I N F O R M A T I O N S E C U R I T YComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930 August 2008 DEPARTMENT OF COMMERCE Carlos M. Gutierrez, Secretary NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY James M. Turner, Deputy Director Reports on Computer Systems Technology The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the economy and public welfare by providing technical leadership for the nation s measurement and standards infrastructure.

2 ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL s responsibilities include the development of management , administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. This Special Publication 800-series reports on ITL s research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ii iii Authority This document has been developed by the National Institute of Standards and Technology (NIST) to further its statutory responsibilities under the Federal Information Security management Act (FISMA) of 2002, 107-347.

3 NIST is responsible for developing standards and guidelines, including minimum requirements, for providing adequate information security for all agency operations and assets, but such standards and guidelines shall not apply to national security systems. This guideline is consistent with the requirements of the office of management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems, as analyzed in A-130, Appendix IV: Analysis of Key Sections. Supplemental information is provided in A-130, Appendix III. This guideline has been prepared for use by federal agencies. It may also be used by nongovernmental organizations on a voluntary basis and is not subject to copyright. (Attribution would be appreciated by NIST.) Nothing in this document should be taken to contradict standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority.

4 Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. NIST Special Publication 800-60 Volume II, Revision 1, 304 pages (Date) CODEN: NSPUE2 Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There are references in this publication to documents currently under development by NIST in accordance with responsibilities assigned to NIST under the Federal Information Security management Act of 2002.

5 The methodologies in this document may be used even before the completion of such companion documents. Thus, until such time as each document is completed, current requirements, guidelines, and procedures (where they exist) remain operative. For planning and transition purposes, agencies may wish to closely follow the development of these new documents by NIST. Individuals are also encouraged to review the public draft documents and offer their comments to NIST. All NIST documents mentioned in this publication, other than the ones noted above, are available at Acknowledgements The authors wish to thank their colleagues who helped update this document, prepare drafts, and review materials. In addition, special thanks are due to our reviewers who greatly contributed to the document s development.

6 The authors also gratefully acknowledge and appreciate the many comments from the public and private sectors whose thoughtful and constructive comments improved the quality and usefulness of this publication. iv Note NIST Special Publication (SP) 800-60 may be used by organizations in conjunction with a family of security-related publications including: FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems; FIPS Publication 200, Minimum Security Controls for Federal Information Systems; NIST SP 800-30, Risk management guide for Information Technology Systems1; NIST SP 800-37, guide for the Security Certification and Accreditation of Federal Information Systems; NIST Draft SP 800-39, Managing Risk from Information Systems: An Organizational Perspective; NIST SP 800-53, Recommended Security Controls for Federal Information Systems.

7 NIST SP 800-53A, guide for Assessing the Security Controls in Federal Information Systems; and NIST SP 800-59, Guideline for Identifying an Information System as a National Security System. This series of nine documents is intended to provide a structured, yet flexible framework for selecting, specifying, employing, and evaluating the security controls in Federal information systems and thus, make a significant contribution toward satisfying the requirements of the Federal Information Security management Act (FISMA) of 2002. While the publications are mutually reinforcing and have some dependencies, in most cases, they can be effectively used independently of one another. This is Volume II of two volumes. Volume I contains the basic guidelines for mapping types of information and information systems to security categories.

8 The appendices contained in Volume II include security categorization recommendations and rationale for mission-based and management and support information types . The SP 800-60 information types and security impact levels are based on the OMB Federal Enterprise Architecture Program management office s October 2007 FEA Consolidated Reference Model Document, Version inputs from participants in NIST SP 800-60 workshops, and FIPS 199. Rationale for the example security impact level recommendations provided in the appendices have been derived from multiple sources, and as such, will require several iterations of review, comment, and subsequent modification to achieve consistency in terminology, structure, and content. 1 This document is currently under revision and will be reissued as Special Publication 800-30, Revision 1, guide for Conducting Risk Assessments.

9 V EXECUTIVE SUMMARY Title III of the E-Government Act (Public Law 107-347), titled the Federal Information Security management Act (FISMA), tasked the National Institute of Standards and Technology (NIST) to develop: Standards to be used by all Federal agencies to categorize all information and information systems collected or maintained by or on behalf of each agency based on the objectives of providing appropriate levels of information security according to a range of risk levels; Guidelines recommending the types of information and information systems to be included in each such category; and Minimum information security requirements ( , management , operational, and technical security controls), for information and information systems in each such category.

10 In response to the second of these tasks, this guideline has been developed to assist Federal government agencies to categorize information and information systems. The guideline s objective is to facilitate provision of appropriate levels of information security according to a range of levels of impact or consequences that might result from the unauthorized disclosure, modification, or loss of availability of the information or information system. This guideline assumes that the user is familiar with Standards for Security Categorization of Federal Information and Information Systems (FIPS 199). The guideline and its appendices : Review the security categorization terms and definitions established by FIPS 199; Recommend a security categorization process; Describe a methodology for identifying types of Federal information and information systems; Suggest provisional security impact levels for common information types ; Discuss information attributes that may result in variances from the provisional security impact level assignment; and Describe how to establish a system security categorization based on the system s use, connectivity, and aggregate information content.