← Back to research report

Document · 2012-09-01

SP 800-30 Rev. 1: Risk Assessments

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-30 Guide for Conducting Risk Assessments ________________________________________________________________________________________________ PAGE iii 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. NIST Special Publication 800-30, 95 pages (September 2012)

CODEN: NSPUE2

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 and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guideline s, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.

Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. All NIST publications are available at http://csrc.nist.gov/publications.

Special Publication 800-30 Guide for Conducting Risk Assessments ________________________________________________________________________________________________

CHAPTER 1 PAGE 2 1.1 PURPOSE AND APPLICABILITY

The purpose of Special Publication 800-30 is to provide guidance for conducting risk assessments of federal information systems and organizations, amplifying the guidance in Special Publication 800-39. Risk assessments, carried out at all three tiers in the risk management hierarchy, are part of an overall risk management process— providing senior leaders/executives with the information needed to determine appropriate courses of action in response to identified risks. In particular, this document provides guidance for carrying out each of the steps in the risk assessment process (i.e., preparing for the assessment, conducting the assessment, communicating the results of the assessment, and maintaining the assessment) and how risk assessments and other organizational risk management processes complement and inform each other. Special Publication 800-30 also provides guidance to organizations on identifying specific risk factors to monitor on an ongoing basis, so that organizations can determine whether risks have increased to unacceptable levels (i.e., exceeding organizational risk tolerance) and different courses of action should be taken.

This publication satisfies the requirements of FISMA and meets or exceeds the information security requirements established for executive agencies9 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.

1.2 TARGET AUDIENCE

This publication is intended to serve a diverse group of risk management professionals including:

• Individuals with oversight responsibilities for risk management (e.g., heads of agencies, chief executive officers, chief operating officers, risk executive [function]);

• Individuals with responsibilities for conducting organizational missions/business functions (e.g., mission/business owners, information owners/stewards, authorizing officials);

• Individuals with responsibilities for acquiring information technology products, services, or information systems (e.g., acquisition officials, procurement officers, contracting officers);

• Individuals with information system/security design, development, and implementation responsibilities (e.g., program managers, enterprise architects, information security architects, information system/security engineers, information systems integrators);

• Individuals with information security oversight, management, and operational responsibilities (e.g., chief information officers, senior information security officers,10 information security managers, information system owners, common control providers); and

9 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.

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

Special Publication 800-30 Guide for Conducting Risk Assessments ________________________________________________________________________________________________

APPENDIX A PAGE A-1

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.

POLICIES, DIRECTIVES, INSTRUCTIONS

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

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

2. Committee on National Security Systems Instruction (CNSSI) No.

4009, National Information Assurance (IA) Glossary, April 2010.

3. Committee on National Security Systems Instruction (CNSSI) No.

1253, Security Categorization and Control Selection for National Security Systems, March 2012.

4. Department of Homeland Security Federal Continuity Directive 2 (FCD 2), Federal

Executive Branch Mission Essential Function and Primary Mission Essential Function Identification and Submission Process, February 2008. 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.

3. ISO/IEC 31000:2009, Risk management – Principles and guidelines.

4. ISO/IEC 30101:2009, Risk management – Risk assessment techniques.

5. ISO/IEC Guide 73, Risk management – Vocabulary.

6. ISO/IEC 27005:2011, Information technology – Security techniques – Information

security risk management. 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-34, Revision 1, Contingency Planning Guide for Federal Information Systems, May 2010.

3. National Institute of Standards and Technology Special Publication 800-37, Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach, February 2010.

Special Publication 800-30 Guide for Conducting Risk Assessments ________________________________________________________________________________________________

APPENDIX B PAGE B-1

APPENDIX B GLOSSARY COMMON TERMS AND DEFINITIONS

his appendix provides definitions for security terminology used within Special Publication 800-30. The terms in the glossary are consistent with the terms used in the suite of FISMA-related security standards and guidelines developed by NIST. Unless otherwise stated, all terms used in this publication are also consistent with the definitions contained in the CNSSI No. 4009, National Information Assurance (IA) Glossary.

Adequate Security [OMB Circular A-130, Appendix III] Security commensurate with the risk and magnitude of harm resulting from the loss, misuse, or unauthorized access to or modification of information. Advanced Persistent Threat [NIST SP 800-39] An adversary with sophisticated levels of expertise and significant resources, allowing it through the use of multiple different attack vectors (e.g., cyber, physical, and deception), to generate opportunities to achieve its objectives which are typically to establish and extend its presence within the information technology infrastructure of organizations for purposes of continually exfiltrating information and/or to undermine or impede critical aspects of a mission, program, or organization, or place itself in a position to do so in the future; moreover, the advanced persistent threat pursues its objectives repeatedly over an extended period of time, adapting to a defender’s efforts to resist it, and with determination to maintain the level of interaction needed to execute its objectives.

Adversary [DHS Risk Lexicon] Individual, group, organization, or government that conducts or has the intent to conduct detrimental activities. Agency See Executive Agency. Analysis Approach The approach used to define the orientation or starting point of the risk assessment, the level of detail in the assessment, and how risks due to similar threat scenarios are treated.

Assessment See Security Control Assessment or Risk Assessment. Assessment Approach The approach used to assess risk and its contributing risk factors, including quantitatively, qualitatively, or semi- quantitatively. Assessor See Security Control Assessor or Risk Assessor.

Attack [CNSSI No. 4009]

Any kind of malicious activity that attempts to collect, disrupt, deny, degrade, or destroy information system resources or the information itself. T