← Back to research report

Document · 2010-02-01

SP 800-37 Rev. 1: Risk Management Framework

Selected pages that mention A-130. Other pages are omitted.

About this text

This text has been formatted for reading on screen. Page links open the original PDF. Older scans may contain errors in words, tables, or reading order.

Document sections
Jump to a PDF page · 4 included

Special Publication 800-37 Guide for Applying the Risk Management Framework to Federal Information Systems Revision 1 A Security Life Cycle Approach ________________________________________________________________________________________________ Authority This publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Management Act (FISMA), Public Law (P.L.) 107-347. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such 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 Circular A-130, Appendix IV: Analysis of Key Sections.

Supplemental information is provided in Circular A-130, Appendix III, Security of Federal Automated Information Resources. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. 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.

This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-37 Revision 1 Natl. Inst. Stand. Technol. Spec. Publ. 800-37 Revision 1, 102 pages (February 2010)

CODEN: NSPUE2

This publication is available free of charge from: http://dx.doi.org/10.6028/NIST.SP.800 -37r1

Comments on this publication may be submitted to: National Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory

100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930

Electronic Mail: sec-cert@nist.gov 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 NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose.

There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of t hese new publications by NIST.

Organizations are encouraged to review draft publications during the designated public comment periods and provide feedback to NIST. Computer Security Division publications are available at http://csrc.nist.gov/publications.

PAGE ii

Special Publication 800-37 Guide for Applying the Risk Management Framework to Federal Information Systems Revision 1 A Security Life Cycle Approach ________________________________________________________________________________________________

• To support consistent, well-informed, and ongoing security authorization decisions (through continuous monitoring), transparency of security and risk management-related information, and reciprocity;11 and

• To achieve more secure information and information systems within the federal government through the implementation of appropriate risk mitigation strategies. This publication satisfies the requirements of the Federal Information Security Management Act

(FISMA) and meets or exceeds the information security requirements established for executive agencies12 by the Office of Management and Budget (OMB) in Circular A-130, Appendix III, Security of Federal Automated Information Resources. The guidelines in this publication are applicable to all federal information systems other than those systems designated as national security systems as defined in 44 U.S.C., Section 3542. The guidelines have been broadly developed from a technical perspective to complement similar guidelines for national security systems and may be used for such systems with the approval of appropriate federal officials exercising policy authority over such systems. State, local, and tribal governments, as well as private sector organizations are encouraged to consider using these guidelines, as appropriate.

13

1.3 TARGET AUDIENCE

This publication serves individuals associated with the design, development, implementation, operation, maintenance, and disposition of federal information systems including:

• Individuals with mission/business ownership responsibilities or fiduciary responsibilities (e.g., heads of federal agencies, chief executive officers, chief financial officers);

• Individuals with information system development and integration responsibilities (e.g., program managers, information technology product developers, information system developers, information systems integrators, enterprise architects, information security architects);

• Individuals with information system and/or security management/oversight responsibilities (e.g., senior leaders, risk executives, authorizing officials, chief information officers, senior information security officers 14); 11 Reciprocity is the mutual agreement among participating organizations to accept each other’s security assessments in order to reuse information system resources and/or to accept each other’s assessed security posture in order to share information. Reciprocity is best achieved by promoting the concept of transparency (i.e., making sufficient evidence regarding the security state of an information system available, so that an authorizing official from another organization can use that evidence to make credible, risk-based decisions regarding the operation and use of that system or the information it processes, stores, or transmits).

12 An executive agency is: (i) an executive department specified in 5 U.S.C., Section 101; (ii) a military department specified in 5 U.S.C., Section 102; (iii) an independent establishment as defined in 5 U.S.C., Section 104(1); and (iv) a wholly owned government corporation fully subject to the provisions of 31 U.S.C., Chapter 91. In this publication, the term executive agency is synonymous with the term federal agency.

13 In accordance with the provisions of FISMA and OMB policy, whenever the interconnection of federal information systems to information systems operated by state/local/tribal governments, contractors, or grantees involves the processing, storage, or transmission of federal information, the information security standards and guidelines described in this publication apply. Specific information security requirements and the terms and conditions of the system interconnections, are expressed in the Memorandums of Understanding and Interconnection Security Agreements established by participating organizations.

14 At the agency level, this position is known as the Senior Agency Information Security Officer. Organizations also refer to this position as the Chief Information Security Officer.

CHAPTER 1 PAGE 3

Special Publication 800-37 Guide for Applying the Risk Management Framework to Federal Information Systems Revision 1 A Security Life Cycle Approach ________________________________________________________________________________________________

APPENDIX A REFERENCES LAWS, POLICIES, DIRECTIVES, INSTRUCTIONS, STANDARDS, AND GUIDELINES LEGISLATION

1. E-Government Act [includes FISMA] (P.L.

107-347), December 2002.

2. Federal Information Security Management Act (P.L.

107-347, Title III), December 2002.

3. Paperwork Reduction Act (P.L.

104-13), May 1995.

POLICIES, DIRECTIVES, INSTRUCTIONS

1. Committee on National Security Systems (CNSS) Instruction 4009, National Information

Assurance Glossary, June 2006.

2. Committee on National Security Systems (CNSS) Instruction 1253, Security

Categorization and Control Selection for National Security Systems, October 2009.

3. Office of Management and Budget, Circular A-130, Appendix III, Transmittal

Memorandum #4, Management of Federal Information Resources, November 2000.

4. Office of Management and Budget Memorandum M-02-01, Guidance for Preparing and

Submitting Security Plans of Action and Milestones, October 2001. STANDARDS

1. National Institute of Standards and Technology Federal Information Processing

Standards Publication 199, Standards for Security Categorization of Federal Information and Information Systems, February 2004.

2. National Institute of Standards and Technology Federal Information Processing

Standards Publication 200, Minimum Security Requirements for Federal Information and Information Systems, March 2006.

GUIDELINES

1. National Institute of Standards and Technology Special Publication 800-18, Revision 1, Guide for Developing Security Plans for Federal Information Systems, February 2006.

2. National Institute of Standards and Technology Special Publication 800-27, Revision A, Engineering Principles for Information Technology Security (A Baseline for Achieving Security), June 2004.

3. National Institute of Standards and Technology Special Publication 800-30, Risk

Management Guide for Information Technology Systems, July 2002.

4. National Institute of Standards and Technology Special Publication 800-39 (Second

Public Draft), Managing Risk from Information Systems: An Organizational Perspective, April 2008.

5. National Institute of Standards and Technology Special Publication 800-53, Revision 3, Recommended Security Controls for Federal Information Systems and Organizations, August 2009.

APPENDIX A PAGE A-1

Special Publication 800-37 Guide for Applying the Risk Management Framework to Federal Information Systems Revision 1 A Security Life Cycle Approach ________________________________________________________________________________________________

APPENDIX B GLOSSARY COMMON TERMS AND DEFINITIONS

Appendix B provides definitions for security terminology used within Special Publication 800-37. Unless specifically defined in this glossary, all terms used in this publication are consistent with the definitions contained in CNSS Instruction 4009, National Information Assurance Glossary.

Adequate Security [OMB Circular A-130,

Appendix III]

Security commensurate with the risk and the magnitude of harm resulting from the loss, misuse, or unauthorized access to or modification of information. This includes assuring that systems and applications used by the agency operate effectively and provide appropriate confidentiality, integrity, and availability, through the use of cost-effective management, personnel, operational, and technical controls.

Agency See Executive Agency. Allocation The process an organization employs to determine whether security controls are defined as system-specific, hybrid, or common. The process an organization employs to assign security controls to specific information system components responsible for providing a particular security capability (e.g., router, server, remote sensor).

Application A software program hosted by an information system. Assessment See Security Control Assessment. Assessor See Security Control Assessor. Assurance The grounds for confidence that the set of intended security controls in an information system are effective in their application.

Authorization (to operate) The official management decision given by a senior organizational official to authorize operation of an information system and to explicitly accept the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, individuals, other organizations, and the Nation based on the implementation of an agreed-upon set of security controls.

Authorization Boundary All components of an information system to be authorized for operation by an authorizing official and excludes separately authorized systems, to which the information system is connected. Authorize Processing See Authorization.

APPENDIX B PAGE B-1