← Back to research report

Document · 2020-10-01

SP 800-53B: Control Baselines

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 · 15 included

NIST SP 800-53B CONTROL BASELINES FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ i This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B

Authority This publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems. Such information security standards and guidelines shall not apply to national security systems without the express approval of the 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.

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, OMB Director, 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-53B Natl. Inst. Stand. Technol. Spec. Publ. 800-53B, 85 pages (October 2020)

CODEN: NSPUE2

This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B

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

Email: sec-cert@nist.gov All comments are subject to release under the Freedom of Information Act (FOIA) [FOIA96]. Certain commercial entities, equipment, or materials may be identified in this document 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 these new publications by NIST.

Organizations are encouraged to review draft publications during the designated public comment periods and provide feedback to NIST. Many NIST publications, other than the ones noted above, are available at https://csrc.nist.gov/publications .

NIST SP 800-53B CONTROL BASELINES FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________

CHAPTER ONE PAGE 1

This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B

CHAPTER ONE INTRODUCTION THE NEED FOR SECURITY AND PRIVACY CONTROL BASELINES

ecurity controls are the safeguards or countermeasures selected and implemented within an information system1 or an organization to protect the confidentiality, integrity, and availability of the system and its information and to manage information security risk.

Privacy controls are the administrative, technical, and physical safeguards employed within a system or an organization to ensure compliance with applicable privacy requirements and to manage privacy risks.2 Security and privacy controls are selected and implemented to satisfy the security and privacy requirements levied on an information system and/or organization. The requirements are derived from applicable laws, executive orders, directives, regulations, policies, standards, and mission needs to ensure the confidentiality, integrity, and availability of information processed, stored, or transmitted and to manage risks to individual privacy. The selection, design, and effective implementation of controls are important tasks that have significant implications for the operations and assets of organizations as well as the welfare of individuals and the Nation.

NIST Special Publication (SP) 800-37 [SP 800-37] defines two approaches for the selection of security and privacy controls: a baseline control selection approach and an organization- generated control selection approach. The baseline control selection approach uses control baselines, which are predefined sets of controls specifically assembled to meet the protection needs of a group, organization, or community of interest. The control baselines serve as a starting point for the protection of individuals’ privacy, information, and information systems.

The organization-generated control selection approach is not addressed in this publication.

1.1 PURPOSE AND APPLICABILITY

This publication establishes security and privacy control baselines for federal information systems and organizations and provides tailoring guidance for those baselines. The control baselines can be implemented by any organization that processes, stores, or transmits information (e.g., federal, state, local, and tribal governments, as well as private sector organizations). Implementation of a minimum set of controls selected from NIST SP 800-53, Revision 5 [SP 800-53] is mandatory to protect federal information and information systems 3 in accordance with the Office of Management and Budget (OMB) Circular A-130 [OMB A-130] and the provisions of the Federal Information Security Modernization Act4 [FISMA]. Whereas use of

1 An information system is a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information. 2 [OMB A-130] defines security controls and privacy controls. 3 A federal information system is an information system used or operated by an agency, a contractor of an agency, or another organization on behalf of an agency.

4 Information systems that have been designated as national security systems (as defined in 44 U.S.C., Section 3542) are not subject to the requirements in [FISMA]. However, the controls established in this publication may be selected for national security systems as otherwise required (e.g., the Privacy Act of 1974) or with the approval of federal officials exercising policy authority over such systems. CNSS Policy No. 22 [CNSSP 22] and CNSS Instruction No. 1253 [CNSSI 1253] provide guidance for national security systems. DoD Instruction 8510.01 [DODI 8510.01] provides guidance for the Department of Defense.

S

NIST SP 800-53B CONTROL BASELINES FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________

CHAPTER ONE PAGE 2

This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B

the privacy control baseline is not mandated by law or [OMB A-130], SP 800-53B—along with other supporting NIST publications—is designed to help organizations identify the security and privacy controls needed to manage risk and to satisfy the security and privacy requirements in FISMA, the Privacy Act of 1974 [PRIVACT], selected OMB policies (e.g., [OMB A-130]), and designated Federal Information Processing Standards (FIPS), among others.

This publication satisfies security and privacy requirements by applying assumptions that inform the development of the security and privacy control baselines, as described in Section 2.3. The baselines serve as a starting point to meet the protection needs of organizations. The controls in the baselines are tailored following the process described in Section 2.4 to further facilitate the management of security and privacy risk specific to the organization. The tailoring process can be guided and informed by many factors, including organizational mission and business needs, stakeholder protection needs, and assessments of risk. The combination of control baseline selection and control tailoring processes can help organizations satisfy their stated security and privacy requirements.

1.2 TARGET AUDIENCE

This publication is intended to serve a diverse audience, including:

• Individuals with system, information security, privacy, or risk management and oversight responsibilities, including authorizing officials, chief information officers, senior agency information security officers, and senior agency officials for privacy

• Individuals with system development responsibilities, including mission owners, program managers, system engineers, system security engineers, privacy engineers, hardware and software developers, system integrators, and acquisition or procurement officials

• Individuals with logistical or disposition-related responsibilities, including program managers, procurement officials, system integrators, and property managers

• Individuals with security and privacy implementation and operations responsibilities, including mission or business owners, system owners, information owners or stewards, system administrators, and system security or privacy officers

• Individuals with security and privacy assessment and monitoring responsibilities, including auditors, Inspectors General, system evaluators, control assessors, independent verifiers and validators, and analysts

• Commercial entities, including industry partners, who produce component products and systems and develop security and privacy technologies

1.3 ORGANIZATIONAL RESPONSIBILITIES

Organizations have the responsibility to choose a control selection approach in accordance with [SP 800-37].5 If the baseline control selection approach is chosen, organizations select a security

5 In the baseline control selection approach and organization-generated control selection approach, organizations develop a well-defined set of security and privacy requirements using a life cycle-based systems engineering process, as described in the Risk Management Framework (RMF) Prepare—System Level step, Task P-15, Requirements Definition. The requirements definition process generates a set of requirements that can be used to guide and inform the selection of controls to satisfy the requirements.

NIST SP 800-53B CONTROL BASELINES FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________

CHAPTER ONE PAGE 3

This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B

control baseline and privacy control baseline as described in Chapter Three. Once the control baseline is selected, organizations apply the tailoring guidance provided in Chapter Two to help ensure that the resulting controls are necessary and sufficient to manage security risk6 and privacy risk.7

1.4 RELATIONSHIP TO OTHER PUBLICATIONS

This publication establishes security and privacy control baselines derived from the controls in [SP 800-53]. The control baselines in this publication are in accordance with requirements for federal information and information systems included in [OMB A-130],8 Federal Information Processing Standard 199 [FIPS 199], and Federal Information Processing Standard 200 [FIPS 200]. [SP 800-37] provides guidance on control selection approaches.

1.5 REVISIONS AND EXTENSIONS

The security and privacy controls specified in the baselines represent the state-of-the-practice protection measures for individuals, information systems, and organizations. The controls comprising the baselines are periodically reviewed and revised to reflect the experience gained from using the controls; new or revised laws, executive orders, directives, regulations, policies, and standards; changing security and privacy requirements; emerging threats, vulnerabilities, attacks, and information processing methods; and the availability of new technologies. Thus, the security and privacy controls specified in the baselines are also expected to change over time as controls are withdrawn, revised, and added. In addition to the need for change, the need for stability is addressed by requiring that proposed changes to the baseline undergo a rigorous and transparent public review process to obtain public and private sector feedback and to build a consensus for baseline changes. The public review process provides a stable, flexible, and technically sound set of security and privacy control baselines.

1.6 PUBLICATION ORGANIZATION

The remainder of this special publication is organized as follows:

• Chapter Two describes the fundamental concepts associated with control baselines, selecting the appropriate baseline, baseline assumptions, tailoring baselines, overlays, and capabilities.

• Chapter Three provides a set of tables organized by control family that contain the controls that comprise the low-impact, moderate-impact, and high-impact security control baselines as well as the privacy control baseline.

• A list of informative References9 is provided after Chapter Three.

• Supporting appendices include: - Appendix A: Glossary

6 [SP 800-30] provides guidance on the risk assessment process. 7 [IR 8062] introduces privacy risk assessment concepts. 8 [OMB A-130] establishes policy for the planning, budgeting, governance, acquisition, and management of federal information, personnel, equipment, funds, IT resources, and supporting infrastructure and services.

9 Unless otherwise stated, all references to NIST publications refer to the most recent version of those publications.

NIST SP 800-53B CONTROL BASELINES FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________

CHAPTER TWO PAGE 5

This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B

CHAPTER TWO THE FUNDAMENTALS CONTROL BASELINES, TAILORING, OVERLAYS, AND CAPABILITIES

his chapter presents the fundamental concepts associated with security and privacy control baselines, including the purpose of control baselines, how control baselines are selected, assumptions associated with control baselines, how the tailoring process is used to customize controls and baselines, the purpose of overlays and how they are used to address the security and privacy needs of communities of interest, and how the concept of capabilities can facilitate the grouping of mutually reinforcing controls.

2.1 CONTROL BASELINES

A significant challenge for organizations is selecting a set of security and privacy controls that can protect their mission and business functions and provide the capability to manage security and privacy risk. The selected controls, if correctly implemented and determined to be effective, meet security and privacy requirements defined by applicable laws, executive orders, policies, regulations, and directives. There is no single set of controls that addresses all security and privacy concerns in every situation. However, choosing the most appropriate controls for a specific situation or system to adequately respond to risk requires a fundamental understanding of the organization’s mission and business priorities, the mission and business functions that the systems will support, and the environments in which the systems will operate. It also requires close collaboration with key organizational stakeholders. With that understanding, organizations can demonstrate how to efficiently and cost-effectively assure the confidentiality, integrity, and availability of organizational information and systems, as well as the privacy of individuals in the context of supporting the organization’s mission and business functions.

The concept of a control baseline is introduced to assist organizations in selecting a set of controls for their systems that is commensurate with security and privacy risk. A control baseline is a collection of controls from [SP 800-53] assembled to address the protection needs of a group, organization, or community of interest.10 It provides a generalized set of controls that represents a starting point for the subsequent tailoring activities that are applied to the baseline to produce a targeted or customized security and privacy solution for the entity that the baseline is intended to serve. Control baselines are tailored based on a variety of factors, including threat information, mission or business requirements, types of systems, sector-specific requirements, specific technologies, operating environments, organizational assumptions and constraints, individuals’ privacy interests, laws, executive orders, regulations, policies, directives, standards, or industry best practices. Tailoring activities are described in greater detail in Section 2.4.

10 The U.S.

Government—in accordance with the requirements set forth in [FISMA], [OMB A-130], and Federal Information Processing Standards—has established federally mandated security control baselines. The control baselines for non-national security systems are listed in Chapter Three.

T

NIST SP 800-53B CONTROL BASELINES FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________

CHAPTER TWO PAGE 7

This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B

Once the impact level of the system is determined, organizations select the appropriate security control baseline.15 The selection of the security control baseline is based on the [FIPS 200] impact level of the system as determined by the security categorization process described above. The organization selects one of three security control baselines from Chapter Three corresponding to the low-impact, moderate-impact, or high-impact categorization of the system. Note that not all controls or control enhancements identified in [SP 800-53] are assigned to control baselines as indicated in the tables in Chapter Three. The controls and control enhancements that are assigned to baselines are indicated by an “x” in the low, moderate, or high columns in Tables 3-1 through 3-20. The use of the term control baseline is intentional. The controls and control enhancements in the baselines are a starting point from which controls or enhancements may be removed, added, or specialized based on the tailoring guidance in Section 2.4.16 Privacy Control Baseline In addition to the three security control baselines, Chapter Three provides an initial privacy control baseline for federal agencies to address privacy requirements and manage privacy risks that arise from the processing of PII based on privacy program responsibilities under [OMB A- 130].17 The controls and control enhancements that are assigned to the privacy baseline are indicated by an “x.”18 Not all controls or control enhancements that address privacy risk are assigned to the privacy control baseline. This approach provides a starting point from which controls or control enhancements may be removed, added, or specialized based on the tailoring guidance in Section 2.4.19 Organizations conduct privacy risk assessments that consider the nature of the PII processing and its impact on individuals to guide the tailoring of the privacy control baseline for their programs and systems. Privacy risk assessments include evaluating the applicability of legal and policy requirements for their programs. For example, organizations may remove controls or control enhancements related to legal or policy requirements that are not applicable to them unless they determine that, based on a privacy risk assessment, the controls or control enhancements would be helpful in mitigating identified privacy risks. In addition, organizations may add unassigned controls or control enhancements to mitigate privacy risks specific to their information systems as determined by their privacy risk assessments.

15 The general control baseline selection process may be augmented or further detailed by additional sector-specific guidance, such as for a community with common risk management objectives or an industry sub-sector, as described in Appendix C, Overlays. 16 Specialization refers to the modification of controls or control enhancements (including organization-defined parameters), or supplemental guidance to allow an organization to further refine the control baseline to address specific requirements, technologies, mission or business functions, or environments of operation. To address the need for specialized sets of controls for communities of interest, systems, and organizations, the overlay concept is introduced. For more information on overlays, see Appendix C.

17 Federal agencies should not assume that the implementation of the privacy control baseline means that they have met all of their obligations under [OMB A-130]. Agencies may need to take additional, separate steps to fully comply with OMB privacy requirements.

18 Privacy control enhancements in Tables 3-1 through 3-20 in Chapter Three cannot be selected and implemented without the selection and implementation of the associated base control. Such actions may require collaboration with security programs in cases where the security program has responsibility for the base control. Organizations ensure that the responsibility for the selection and implementation of controls is clearly defined between the information security and privacy programs.

19 See footnote 16.

NIST SP 800-53B CONTROL BASELINES FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________

CHAPTER THREE PAGE 15

This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B

CHAPTER THREE THE CONTROL BASELINES SECURITY AND PRIVACY CONTROL BASELINES

ables 3-1 through 3-20 provide a listing of the controls and control enhancements assigned to the control families in [SP 800-53] and the respective control allocations to the privacy control baseline and the low-impact, moderate-impact, and high-impact security control baselines. Section 2.2 (Privacy Control Baseline) provides additional information on the privacy control selection criteria.

T

SECURITY AND PRIVACY CONTROL BASELINE RELATIONSHIPS

• Controls and control enhancements that are assigned to security control baselines are used to manage risks arising from the loss of confidentiality, integrity, and availability. Since Senior Agency Officials for Privacy (SAOPs) have the responsibility for managing privacy risk in accordance with [OMB A-130], and since privacy risks arise from both the processing of PII and the loss of confidentiality, integrity, and availability of PII, it is important that organizations consider how privacy and security programs collaborate in activities related to these controls, such as categorization, tailoring, implementation, and assessment.

• Controls and control enhancements that are assigned only to the privacy control baseline and not to the security control baselines are important for managing privacy program responsibilities under [OMB A-130] but do not generally support the management of risks that arise from the loss of confidentiality, integrity, and availability.

• Controls and control enhancements that are assigned to both the privacy and security control baselines are used to manage privacy program responsibilities under [OMB A-130] and risks that arise from the loss of confidentiality, integrity, and availability (including PII).

• Some controls and control enhancements are not assigned to any control baseline. Through tailoring, organizations make their own determinations as to whether the controls and control enhancements are needed to meet applicable requirements or are useful for managing risks that arise from the loss of confidentiality, integrity, and availability or the processing of PII.

NIST SP 800-53B CONTROL BASELINES FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________

REFERENCES PAGE 56

This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B

REFERENCES

LAWS, POLICIES, INSTRUCTIONS, STANDARDS, GUIDELINES, AND INTERNAL REPORTS LAWS

[FISMA] Federal Information Security Modernization Act (P.L. 113-283), December

2014. https://www.congress.gov/113/plaws/publ283/PLAW-113publ283.pdf [FOIA96] Freedom of Information Act (FOIA), 5 U.S.C. § 552, As Amended By Public Law No. 104-231, 110 Stat. 3048, Electronic Freedom of Information Act Amendments of 1996. https://www.govinfo.gov/content/pkg/PLAW-104publ231/pdf/PLAW- 104publ231.pdf [PRIVACT] Privacy Act (P.L. 93-579), December 1974.

https://www.govinfo.gov/content/pkg/STATUTE-88/pdf/STATUTE-88-Pg1896.pdf [44 USC 3552] Title 44 U.S. Code, Sec. 3552, Definitions. 2017 ed. https://www.govinfo.gov/app/details/USCODE-2017-title44/USCODE-2017-title44- chap35-subchapII-sec3552

POLICIES AND INSTRUCTIONS

[CNSSI 1253] Committee on National Security Systems Instruction No. 1253, Security Categorization and Control Selection for National Security Systems, March

2014. https://www.cnss.gov/CNSS/issuances/Instructions.cfm [CNSSP 22] Committee on National Security Systems Policy No. 22, Cybersecurity Risk Management Policy, August 2016. https://www.cnss.gov/CNSS/issuances/Policies.cfm [DODI 8510.01] Department of Defense Instruction 8510.01, Risk Management Framework

(RMF) for DoD Information Technology (IT), March 2014. https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/851001p.pdf ?ver=2019-02-26-101520-300 [OMB A-130] Office of Management and Budget Memorandum Circular A-130, Managing Information as a Strategic Resource, July 2016.

https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/circulars/A130/a13 0revised.pdf

STANDARDS, GUIDELINES, AND INTERNAL REPORTS

[FIPS 199] National Institute of Standards and Technology (2004) Standards for Security Categorization of Federal Information and Information Systems. (U.S. Department of Commerce, Washington, D.C.), Federal Information Processing Standards Publication (FIPS) 199.

https://doi.org/10.6028/NIST.FIPS.199

NIST SP 800-53B CONTROL BASELINES FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________

APPENDIX A PAGE 59

This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B

APPENDIX A GLOSSARY COMMON TERMS AND DEFINITIONS

ppendix A provides definitions for terminology used in NIST SP 800-53B. Sources for terms used in this publication are cited as applicable. Where no citation is noted, the source of the definition is SP 800-53B. agency [OMB A-130] Any executive agency or department, military department, Federal Government corporation, Federal Government- controlled corporation, or other establishment in the Executive Branch of the Federal Government, or any independent regulatory agency. See executive agency.

assignment operation A control parameter that allows an organization to assign a specific, organization-defined value to the control or control enhancement (e.g., assigning a list of roles to be notified or a value for the frequency of testing). See organization-defined control parameters and selection operation.

assurance Grounds for justified confidence that a [security or privacy] claim has been or will be achieved. Note 1: Assurance is typically obtained relative to a set of specific claims. The scope and focus of such claims may vary (e.g., security claims, safety claims), and the claims themselves may be interrelated.

Note 2: Assurance is obtained through techniques and methods that generate credible evidence to substantiate claims. authorizing official [OMB A-130] A senior Federal official or executive with the authority to authorize (i.e., assume responsibility for) the operation of an information system or the use of a designated set of common controls at an acceptable level of risk to agency operations (including mission, functions, image, or reputation), agency assets, individuals, other organizations, and the Nation.

availability [FISMA] Ensuring timely and reliable access to and use of information. capability A combination of mutually reinforcing security and/or privacy controls implemented by technical means, physical means, and procedural means. Such controls are typically selected to achieve a common information security- or privacy-related purpose.

common control [OMB A-130] A security or privacy control that is inherited by multiple information systems or programs. common control provider [SP 800-37] An organizational official responsible for the development, implementation, assessment, and monitoring of common controls (i.e., security or privacy controls inheritable by systems).

A

NIST SP 800-53B CONTROL BASELINES FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________

APPENDIX A PAGE 60

This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B

compensating controls The security and privacy controls employed in lieu of the controls in the baselines described in NIST Special Publication 800-53B that provide equivalent or comparable protection for a system or organization. confidentiality [FISMA] Preserving authorized restrictions on information access and disclosure, including means for protecting personal privacy and proprietary information.

control baseline [FIPS 200, Adapted] The set of security and privacy controls defined for a low-impact, moderate-impact, or high-impact system or selected based on the privacy selection criteria that provide a starting point for the tailoring process. control enhancement Augmentation of a security or privacy control to build in additional but related functionality to the control, increase the strength of the control, or add assurance to the control.

control inheritance A situation in which a system or application receives protection from security or privacy controls (or portions of controls) that are developed, implemented, assessed, authorized, and monitored by entities other than those responsible for the system or application; entities either internal or external to the organization where the system or application resides. See common control.

environment of operation [OMB A-130] The physical surroundings in which an information system processes, stores, and transmits information. high-impact system [FIPS 200] A system in which at least one security objective (i.e., confidentiality, integrity, or availability) is assigned a FIPS Publication 199 potential impact value of high.

hybrid control [OMB A-130] A security or privacy control that is implemented for an information system, in part as a common control and in part as a system-specific control. impact The effect on organizational operations, organizational assets, individuals, other organizations, or the Nation (including the national security interests of the United States) of a loss of confidentiality, integrity, or availability of information or a system.

impact value [FIPS 199] The assessed worst-case potential impact that could result from a compromise of the confidentiality, integrity, or availability of information expressed as a value of low, moderate, or high. information [OMB A-130] Any communication or representation of knowledge such as facts, data, or opinions in any medium or form, including textual, numerical, graphic, cartographic, narrative, electronic, or audiovisual forms.

NIST SP 800-53B CONTROL BASELINES FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________

APPENDIX A PAGE 61

This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B

information security [OMB A-130] The protection of information and systems from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide confidentiality, integrity, and availability. information system [OMB A-130] A discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information.

integrity [FISMA] Guarding against improper information modification or destruction, and includes ensuring information non-repudiation and authenticity. low-impact system [FIPS 200] A system in which all three security objectives (i.e., confidentiality, integrity, and availability) are assigned a FIPS Publication 199 potential impact value of low.

moderate-impact system [FIPS 200] A system in which at least one security objective (i.e., confidentiality, integrity, or availability) is assigned a FIPS Publication 199 potential impact value of moderate and no security objective is assigned a potential impact value of high.

national security system [OMB A-130] Any system (including any telecommunications system) used or operated by an agency or by a contractor of an agency, or other organization on behalf of an agency—(i) the function, operation, or use of which involves intelligence activities; involves cryptologic activities related to national security; involves command and control of military forces; involves equipment that is an integral part of a weapon or weapons system; or is critical to the direct fulfillment of military or intelligence missions (excluding a system that is to be used for routine administrative and business applications, for example, payroll, finance, logistics, and personnel management applications); or (ii) is protected at all times by procedures established for information that have been specifically authorized under criteria established by an Executive Order or an Act of Congress to be kept classified in the interest of national defense or foreign policy.

organization [FIPS 200, Adapted] An entity of any size, complexity, or positioning within an organizational structure, including federal agencies, private enterprises, academic institutions, state, local, or tribal governments, or as appropriate, any of their operational elements.

organization-defined control parameter The variable part of a control or control enhancement that is instantiated by an organization during the tailoring process by either assigning an organization-defined value or selecting a value from a predefined list provided as part of the control or control enhancement. See assignment operation and selection operation.

NIST SP 800-53B CONTROL BASELINES FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________

APPENDIX A PAGE 62

This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B

overlay [OMB A-130] A specification of security or privacy controls, control enhancements, supplemental guidance, and other supporting information employed during the tailoring process, that is intended to complement (and further refine) security control baselines. The overlay specification may be more stringent or less stringent than the original security control baseline specification and can be applied to multiple information systems.

See tailoring. personally identifiable information [OMB A-130] Information that can be used to distinguish or trace an individual’s identity, either alone or when combined with other information that is linked or linkable to a specific individual. potential impact [FIPS 199] The loss of confidentiality, integrity, or availability could be expected to have a limited adverse effect (FIPS Publication 199 low), a serious adverse effect (FIPS Publication 199 moderate), or a severe or catastrophic adverse effect (FIPS Publication 199 high) on organizational operations, organizational assets, or individuals.

privacy control [OMB A-130] The administrative, technical, and physical safeguards employed within an agency to ensure compliance with applicable privacy requirements and manage privacy risks. privacy impact assessment [OMB A-130] An analysis of how information is handled to ensure handling conforms to applicable legal, regulatory, and policy requirements regarding privacy; to determine the risks and effects of creating, collecting, using, processing, storing, maintaining, disseminating, disclosing, and disposing of information in identifiable form in an electronic information system; and to examine and evaluate protections and alternate processes for handling information to mitigate potential privacy concerns. A privacy impact assessment is both an analysis and a formal document detailing the process and the outcome of the analysis.

privacy plan [OMB A-130] A formal document that details the privacy controls selected for an information system or environment of operation that are in place or planned for meeting applicable privacy requirements and managing privacy risks, details how the controls have been implemented, and describes the methodologies and metrics that will be used to assess the controls.

privacy program plan [OMB A-130] A formal document that provides an overview of an agency’s privacy program, including a description of the structure of the privacy program, the resources dedicated to the privacy program, the role of the Senior Agency Official for Privacy and other privacy officials and staff, the strategic goals and objectives of the privacy program, and the program management controls and common controls in place or planned for meeting applicable privacy requirements and managing privacy risks.

NIST SP 800-53B CONTROL BASELINES FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________

APPENDIX A PAGE 63

This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B

processing [IR 8062] Operation or set of operations performed upon PII that can include but is not limited to the collection, retention, logging, generation, transformation, use, disclosure, transfer, and disposal of PII. risk [OMB A-130] A measure of the extent to which an entity is threatened by a potential circumstance or event, and typically is a function of: (i) the adverse impact, or magnitude of harm, that would arise if the circumstance or event occurs; and (ii) the likelihood of occurrence.

risk assessment [SP 800-39]

The process of identifying risks to organizational operations (including mission, functions, image, reputation), organizational assets, individuals, other organizations, and the Nation, resulting from the operation of a system. Part of risk management, incorporates threat and vulnerability analyses and analyses of privacy problems arising from information processing and considers mitigations provided by security and privacy controls planned or in place. Synonymous with risk analysis.

risk management [OMB A-130] The program and supporting processes to manage risk to agency operations (including mission, functions, image, reputation), agency assets, individuals, other organizations, and the Nation, and includes: establishing the context for risk-related activities, assessing risk, responding to risk once determined, and monitoring risk over time.

scoping considerations A part of tailoring guidance providing organizations with specific considerations on the applicability and implementation of security and privacy controls in the control baselines. Considerations include policy or regulatory, technology, physical infrastructure, system component allocation, public access, scalability, common control, operational or environmental, and security objective.

security category [OMB A-130] The characterization of information or an information system based on an assessment of the potential impact that a loss of confidentiality, integrity, or availability of such information or information system would have on agency operations, agency assets, individuals, other organizations, and the Nation.

security control [OMB A-130] The safeguards or countermeasures prescribed for an information system or an organization to protect the confidentiality, integrity, and availability of the system and its information. security control baseline [OMB A-130] The set of minimum security controls defined for a low-impact, moderate-impact, or high-impact information system.

NIST SP 800-53B CONTROL BASELINES FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________

APPENDIX A PAGE 64

This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B

security functionality The security-related features, functions, mechanisms, services, procedures, and architectures implemented within organizational information systems or the environments in which those systems operate. security functions The hardware, software, or firmware of the system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based.

security objective [FIPS 199] Confidentiality, integrity, or availability. security plan Formal document that provides an overview of the security requirements for an information system or an information security program and describes the security controls in place or planned for meeting those requirements. The system security plan describes the system components that are included within the system, the environment in which the system operates, how the security requirements are implemented, and the relationships with or connections to other systems.

See system security plan. security requirement [FIPS 200, Adapted] A requirement levied on an information system or an organization that is derived from applicable laws, executive orders, directives, regulations, policies, standards, procedures, or mission/business needs to ensure the confidentiality, integrity, and availability of information that is being processed, stored, or transmitted.

Note: Security requirements can be used in a variety of contexts from high- level policy-related activities to low-level implementation-related activities in system development and engineering disciplines. selection operation A control parameter that allows an organization to select a value from a list of predefined values provided as part of the control or control enhancement (e.g., selecting to either restrict an action or prohibit an action).

See assignment operation and organization-defined control parameter. senior agency official for privacy [OMB A-130] The senior official, designated by the head of each agency, who has agency-wide responsibility for privacy, including implementation of privacy protections; compliance with Federal laws, regulations, and policies relating to privacy; management of privacy risks at the agency; and a central policy-making role in the agency’s development and evaluation of legislative, regulatory, and other policy proposals.

system owner (or program manager) Official responsible for the procurement, development, integration, modification, operation, and maintenance of a system.

NIST SP 800-53B CONTROL BASELINES FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________

APPENDIX A PAGE 65

This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B

system security plan

See security plan. system-specific control [OMB A-130] A security or privacy control for an information system that is implemented at the system level and is not inherited by any other information system. tailored control baseline A set of controls resulting from the application of tailoring guidance to a control baseline. See tailoring.

tailoring The process by which security and privacy control baselines are modified by identifying and designating common controls, applying scoping considerations on the applicability and implementation of baseline controls, selecting compensating controls, assigning specific values to organization-defined control parameters, supplementing baselines with additional controls or control enhancements, and providing additional specification information for control implementation.