Special Publication 800-53 Recommended Security Controls for Federal Information Systems ________________________________________________________________________________________________ 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, P.L. 107-347. 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 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. 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.
National Institute of Standards and Technology Special Publication 800-53, 116 pages (February 2005) 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 and Homeland Security Presidential Directive #12. These include: NIST Special Publication 800-53A, FIPS 200, and FIPS 201. The methodologies in this document may be used even before the completion of the aforementioned 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: http://csrc.nist.gov/publications.
COMMENTS MAY BE SUBMITTED TO THE COMPUTER SECURITY DIVISION, NIST, VIA ELECTRONIC MAIL AT SEC-CERT@NIST.GOV OR VIA REGULAR MAIL AT 100 BUREAU DRIVE (MAIL STOP 8930)
GAITHERSBURG, MD 20899-8930
PAGE iii
Special Publication 800-53 Recommended Security Controls for Federal Information Systems ________________________________________________________________________________________________
• Security awareness training to inform personnel (including contractors and other users of information systems that support the operations and assets of the organization) of the information security risks associated with their activities and their responsibilities in complying with organizational policies and procedures designed to reduce these risks;
• Periodic testing and evaluation of the effectiveness of information security policies, procedures, practices, and security controls to be performed with a frequency depending on risk, but no less than annually;
• A process for planning, implementing, evaluating, and documenting remedial actions to address any deficiencies in the information security policies, procedures, and practices of the organization;
• Procedures for detecting, reporting, and responding to security incidents; and
• Plans and procedures to ensure continuity of operations for information systems that support the operations and assets of the organization. It is of paramount importance that responsible individuals within the organization understand the risks and other factors that could adversely affect their operations and assets. Moreover, these officials must understand the current status of their security programs and the security controls planned or in place to protect their information systems in order to make informed judgments and investments that appropriately mitigate risks to an acceptable level. The ultimate objective is to conduct the day-to-day operations of the organization and to accomplish the organization’s stated missions with what the Office of Management and Budget (OMB) Circular A-130 defines as adequate security, or security commensurate with risk, including the magnitude of harm resulting from the unauthorized access, use, disclosure, disruption, modification, or destruction of information.
1.1 PURPOSE AND APPLICABILITY
The purpose of this publication is to provide guidelines for selecting and specifying security controls for information systems supporting the executive agencies of the federal government. The guidelines apply to all components5 of an information system that process, store, or transmit federal information. The guidelines have been developed to help achieve more secure information systems within the federal government by:
• Facilitating a more consistent, comparable, and repeatable approach for selecting and specifying security controls for information systems;
• Providing a recommendation for minimum security controls for information systems categorized in accordance with Federal Information Processing Standards (FIPS) 199, Standards for Security Categorization of Federal Information and Information Systems;
• Promoting a dynamic, extensible catalog of security controls for information systems to meet the demands of changing requirements and technologies; and
• Creating a foundation for the development of assessment methods and procedures for determining security control effectiveness.
5 Information system components include, but are not limited to, mainframes, servers, workstations, network components, operating systems, middleware, and applications. Network components can include such devices as firewalls, switches, routers, gateways, wireless access points, and network appliances. Servers can include database servers, authentication servers, electronic mail and web servers, proxy servers, domain name servers, and network time servers. Information system components are either purchased commercially off-the-shelve or are custom developed.
PAGE 2
Special Publication 800-53 Recommended Security Controls for Federal Information Systems ________________________________________________________________________________________________ security controls may also serve as templates for further control refinement. An organization may choose, for example, to implement the CP-2 (Contingency Planning) security control as a master template for a generalized contingency plan for all organizational information systems with individual information system owners tailoring the plan, where appropriate, for system-specific issues.
Information system owners are responsible for any system-specific issues associated with the implementation of an organization’s common security controls. These issues are identified and described in the system security plans for the individual information systems. The senior agency information security officer, acting on behalf of the Chief Information Officer, should coordinate with organizational officials (e.g., facilities managers, site managers, personnel managers) responsible for the development and implementation of the designated common security controls to ensure that the required controls are put into place, the controls are assessed, and the assessment results are shared with the appropriate information system owners.
Partitioning security controls into common security controls and system-specific security controls can result in significant savings to the organization in control development and implementation costs. It can also result in a more consistent application of the security controls across the organization at large. Moreover, equally significant savings can be realized in the security certification and accreditation process. Rather than assessing common security controls in every information system, the certification process draws upon any applicable results from the most current assessment of the common security controls performed at the organization level. An organization-wide approach to reuse and sharing of assessment results can greatly enhance the efficiency of the security certifications and accreditations being conducted by organizations and significantly reduce security program costs.
While the concept of security control partitioning into common security controls and system- specific controls is straightforward and intuitive, the application of this principle within an organization takes planning, coordination, and perseverance. If an organization is just beginning to implement this approach or has only partially implemented this approach, it may take some time to get the maximum benefits from security control partitioning and the associated reuse of assessment evidence. Because of the potential dependence on common security controls by many of an organization’s information systems, a failure of such common controls may result in a significant increase in agency-level risk—risk th at arises from the operation of the systems that depend on these controls.
2.3 SECURITY CONTROL BASELINES
Organizations must employ security controls to meet security requirements defined by laws, executive orders, directives, policies, or regulations (e.g., Federal Information Security Management Act, OMB Circular A-130, Appendix III).15 The challenge for organizations is to determine the appropriate set of security controls, which if implemented and determined to be effective in their application, would comply with the stated security requirements. Selecting the appropriate set of security controls to meet the specific, and sometimes unique, security requirements of an organization is an important task—a task that de monstrates the organization’s
15 An information system may require security controls at different layers within the system. For example, an operating system or network component typically provides an identification and authentication capability. An application running on that operating system or network may also provide its own identification and authentication capability rendering an additional level of protection for the overall information system. The selection and specification of security controls should consider components at all layers within the information system.
PAGE 9
Special Publication 800-53 Recommended Security Controls for Federal Information Systems ________________________________________________________________________________________________
38. National Institute of Standards and Technology Special Publication 800-60, Guide for
Mapping Types of Information and Information Systems to Security Categories, June 2004.
39. National Institute of Standards and Technology Special Publication 800-61, Computer
Security Incident Handling Guide, January 2004.
40. National Institute of Standards and Technology Special Publication 800-63, Version 1.0.1, Electronic Authentication Guideline, September 2004.
41. National Institute of Standards and Technology Special Publication 800-64, Revision1, Security Considerations in the Information System Development Life Cycle, June 2004.
42. National Institute of Standards and Technology Special Publication 800-65, Integrating
Security into the Capital Planning and Investment Control Process, January 2005.
43. National Institute of Standards and Technology Special Publication 800-70, Security
Configuration Checklists Program for IT Products: Guidance for Checklists Users and Developers, May 2005.
44. Office of Management and Budget, Circular A-130, Appendix III, Transmittal
Memorandum #4, Management of Federal Information Resources, November 2000.
45. Office of Management and Budget, Federal Enterprise Architecture Program Management
Office, Business Reference Model (v2.0), June 2003.
46. Office of Management and Budget Memorandum 03-19, Reporting Instructions for the
Federal Information Security Management Act and Updated Guidance on Quarterly IT Security Reporting, August 2003.
47. Office of Management and Budget Memorandum 03-22, OMB Guidance for Implementing
the Privacy Provisions of the E-Government Act of 2002, September 2003.
48. Office of Management and Budget Memorandum 04-04, E-Authentication Guidance for
Federal Agencies, December 2003.
49. Paperwork Reduction Act of 1995 (P.L.
104-13), May 1995.
50. Privacy Act of 1974 (P.L.
93-579), September 1975.
PAGE 20
Special Publication 800-53 Recommended Security Controls for Federal Information Systems ________________________________________________________________________________________________
APPENDIX B GLOSSARY COMMON TERMS AND DEFINITIONS
Appendix B provides definitions for security terminology used within Special Publication 800-53. 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.
Accreditation [NIST SP 800-37] The official management decision given by a senior agency official to authorize operation of an information system and to explicitly accept the risk to agency operations (including mission, functions, image, or reputation), agency assets, or individuals, based on the implementation of an agreed-upon set of security controls.
Accreditation Boundary [NIST SP 800-37] All components of an information system to be accredited by an authorizing official and excludes separately accredited systems, to which the information system is connected. Synonymous with the term security perimeter defined in CNSS Instruction 4009 and
DCID 6/3.
Accrediting Authority See Authorizing Official. 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. Agency See Executive Agency. Authentication Verifying the identity of a user, process, or device, often as a prerequisite to allowing access to resources in an information system.
Authenticity The property of being genuine and being able to be verified and trusted; confidence in the validity of a transmission, a message, or message originator. See authentication. Authorize Processing See Accreditation. Authorizing Official [NIST SP 800-37] Official with the authority to formally assume responsibility for operating an information system at an acceptable level of risk to agency operations (including mission, functions, image, or reputation), agency assets, or individuals.
Availability [44 U.S.C., Sec. 3542] Ensuring timely and reliable access to and use of information.
PAGE 21
Special Publication 800-53 Recommended Security Controls for Federal Information Systems ________________________________________________________________________________________________ Controlled Interface [CNSS Inst. 4009] Mechanism that facilitates the adjudication of different interconnected system security policies (e.g., controlling the flow of information into or out of an interconnected system).
Executive Agency [41 U.S.C., Sec. 403] An executive department specified in 5 U.S.C., Sec. 101; a military department specified in 5 U.S.C., Sec. 102; an independent establishment as defined in 5 U.S.C., Sec. 104(1); and a wholly owned Government corporation fully subject to the provisions of 31 U.S.C., Chapter 91.
Federal Enterprise Architecture [FEA Program Management Office] A business-based framework for government-wide improvement developed by the Office of Management and Budget that is intended to facilitate efforts to transform the federal government to one that is citizen-centered, results-oriented, and market-based.
Federal Information System [40 U.S.C., Sec. 11331] An information system used or operated by an executive agency, by a contractor of an executive agency, or by another organization on behalf of an executive agency. General Support System [OMB Circular A-130,
Appendix III]
An interconnected set of information resources under the same direct management control that shares common functionality. It normally includes hardware, software, information, data, applications, communications, and people. High-Impact System An information system in which at least one security objective (i.e., confidentiality, integrity, or availability) is assigned a FIPS 199 potential impact value of high.
Information Owner [CNSS Inst. 4009] Official with statutory or operational authority for specified information and responsibility for establishing the controls for its generation, collection, processing, dissemination, and disposal. Information Resources [44 U.S.C., Sec. 3502] Information and related resources, such as personnel, equipment, funds, and information technology.
Information Security [44 U.S.C., Sec. 3542] The protection of information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide confidentiality, integrity, and availability. Information Security Policy [CNSS Inst. 4009] Aggregate of directives, regulations, rules, and practices that prescribes how an organization manages, protects, and distributes information.
Information System [44 U.S.C., Sec. 3502] [OMB Circular A-130,
Appendix III]
A discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information. Information System Owner (or Program Manager) [CNSS Inst. 4009, Adapted] Official responsible for the overall procurement, development, integration, modification, or operation and maintenance of an information system.
PAGE 23
Special Publication 800-53 Recommended Security Controls for Federal Information Systems ________________________________________________________________________________________________ Information System Security Officer [CNSS Inst. 4009, Adapted] Individual assigned responsibility by the senior agency information security officer, authorizing official, management official, or information system owner for ensuring the appropriate operational security posture is maintained for an information system or program.
Information Technology [40 U.S.C., Sec. 1401] Any equipment or interconnected system or subsystem of equipment that is used in the automatic acquisition, storage, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data or information by the executive agency. For purposes of the preceding sentence, equipment is used by an executive agency if the equipment is used by the executive agency directly or is used by a contractor under a contract with the executive agency which:
(i) requires the use of such equipment; or (ii) requires the use, to a significant extent, of such equipment in the performance of a service or the furnishing of a product. The term information technology includes computers, ancillary equipment, software, firmware, and similar procedures, services (including support services), and related resources.
Information Type [FIPS 199] A specific category of information (e.g., privacy, medical, proprietary, financial, investigative, contractor sensitive, security management) defined by an organization or in some instances, by a specific law, executive order, directive, policy, or regulation.
Integrity [44 U.S.C., Sec. 3542] Guarding against improper information modification or destruction, and includes ensuring information non-repudiation and authenticity. Label See Security Label. Low-Impact System An information system in which all three security objectives (i.e., confidentiality, integrity, and availability) are assigned a FIPS 199 potential impact value of low.
Major Application [OMB Circular A-130,
Appendix III]
An application that requires special attention to security due to the risk and magnitude of harm resulting from the loss, misuse, or unauthorized access to or modification of the information in the application. Note: All federal applications require some level of protection. Certain applications, because of the information in them, however, require special management oversight and should be treated as major. Adequate security for other applications should be provided by security of the systems in which they operate.
Major Information System [OMB Circular A-130] An information system that requires special management attention because of its importance to an agency mission; its high development, operating, or maintenance costs; or its significant role in the administration of agency programs, finances, property, or other resources.
PAGE 24
Special Publication 800-53 Recommended Security Controls for Federal Information Systems ________________________________________________________________________________________________
CA-3 INFORM ATION SYSTEM CONNECTIONS
Control: The organization authorizes all connections from the information system to other information systems outside of the accreditation boundary and monitors/controls the system interconnections on an ongoing basis. Appropriate organizational officials approve information system interconnection agreements.
Supplemental Guidance: Since FIPS 199 security categorizations apply to individual information systems, the organization should carefully consider the risks that may be introduced when systems are connected to other information systems with different security requirements and security controls, both within the organization and external to the organization. Risk considerations should also include information systems sharing the same networks. NIST Special Publication 800-47 provides guidance on interconnecting information systems.
Control Enhancements: None.
LOW CA-3 MOD CA-3 HIGH CA-3
CA-4 SECURITY CERTIFICATION
Control: The organization conducts an assessment of the security controls in the information system to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting the security requirements for the system.
Supplemental Guidance: A security certification is conducted by the organization in support of the OMB Circular A-130, Appendix III requirement for accrediting the information system. The security certification is integrated into and spans the System Development Life Cycle (SDLC).
NIST Special Publication 800-53A provides guidance on the assessment of security controls. NIST Special Publication 800-37 provides guidance on security certification and accreditation. Control Enhancements: None.
LOW CA-4 MOD CA-4 HIGH CA-4
CA-5 PLAN OF ACTION AND MILESTONES
Control: The organization develops and updates [Assignment: organization-defined frequency], a plan of action and milestones for the information system that documents the organization’s planned, implemented, and evaluated remedial actions to correct any deficiencies noted during the assessment of the security controls and to reduce or eliminate known vulnerabilities in the system.
Supplemental Guidance: The plan of action and milestones updates are based on the findings from security control assessments, security impact analyses, and continuous monitoring activities. The plan of action and milestones is a key document in the security accreditation package developed for the authorizing official. NIST Special Publication 800-37 provides guidance on the security certification and accreditation of information systems. NIST Special Publication 800-30 provides guidance on risk mitigation.
Control Enhancements: None.
LOW CA-5 MOD CA-5 HIGH CA-5
PAGE 55
Special Publication 800-53 Recommended Security Controls for Federal Information Systems ________________________________________________________________________________________________
CA-6 SECURITY ACCREDITATION
Control: The organization authorizes (i.e., accredits) the information system for processing before operations and updates the authorization [Assignment: organization-defined frequency]. A senior organizational official signs and approves the security accreditation.
Supplemental Guidance: OMB Circular A-130, Appendix III, establishes policy for security accreditations of federal information systems. The organization assesses the security controls employed within the information system before and in support of the security accreditation.
Security assessments conducted in support of security accreditations are called security certifications. NIST Special Publication 800-37 provides guidance on the security certification and accreditation of information systems. Control Enhancements: None.
LOW CA-6 MOD CA-6 HIGH CA-6
CA-7 CON TINUOUS MONITORING
Control: The organization monitors the security controls in the information system on an ongoing basis. Supplemental Guidance: Continuous monitoring activities include configuration management and control of information system components, security impact analyses of changes to the system, ongoing assessment of security controls, and status reporting. The organization establishes the selection criteria for control monitoring and subsequently selects a subset of the security controls employed within the information system for purposes of continuous monitoring. NIST Special Publication 800-37 provides guidance on the continuous monitoring process. NIST Special Publication 800-53A provides guidance on the assessment of security controls.
Control Enhancements: None.