david
/
a130


			
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728
							<!DOCTYPE html>
<html>
<head>
  <meta name="google-site-verification" content="xXEGpPeG9CfACp-aeM0kS8pSS9Vk7Z8OS0QB_EehREs" />

  <meta http-equiv="X-UA-Compatible" content="IE=edge">
  <meta charset="utf-8">
  <meta content="width=device-width, initial-scale=1.0" name="viewport">

  <link rel="stylesheet" href="/assets/css/normalize.css">
  <link href="/assets/css/google-fonts.css" rel="stylesheet" type="text/css">
  <link rel="stylesheet" href="/assets/css/styles.css?201509271090037">
  <link rel="stylesheet" href="/assets/css/syntax.css">
  <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js"></script>
  <script src="/assets/js/jquery.navgoco.min.js"></script>  


  <!--[if lt IE 9]>
    <script src="/assets/js/html5.js"></script>
    <script src="/assets/js/respond.min.js"></script>
  <![endif]-->

  <link rel="shortcut icon" type="image/ico" href="/assets/favicon.ico" />

  <link rel="canonical" href="https://ombegov.github.io/a130//appendix3/" />

  
    <title>Appendix III</title>
    <meta property="og:title" content="Appendix III" />
  

    <meta name="description" content="Appendix III: Responsibilities for Protecting Federal Information Resources">
    <meta property="og:description" content="Appendix III: Responsibilities for Protecting Federal Information Resources" />
  

</head>
<body>

<div class="container">
  <header role="banner">
    <h1>
      <a href="/">OMB Circular A-130</a>
    </h1>
  </header>

  <div class="wrap content">
    <aside>
  <a class="skip-link visuallyhidden focusable" href="#main">Skip to Main Content</a>
  <nav class="sidebar-nav" role="navigation">
    <ul>
      
        
        <li class="">
          <a href="/">Home</a>
        </li>
      
        
        <li class="">
          <a href="/introduction/">Introduction</a>
        </li>
      
        
        <li class="">
          <a href="/purpose/">Purpose</a>
        </li>
      
        
        <li class="">
          <a href="/applicability/">Applicability</a>
        </li>
      
        
        <li class="">
          <a href="/basic_consideration/">Basic Considerations</a>
        </li>
      
        
        <li class="">
          <a href="/policy/">Policy</a>
        </li>
      
        
        <li class="">
          <a href="/gov-wide-responsbilities/">Government-Wide Responsbilities</a>
        </li>
      
        
        <li class="">
          <a href="/effectiveness/">Effectiveness</a>
        </li>
      
        
        <li class="">
          <a href="/oversight/">Oversight</a>
        </li>
      
        
        <li class="">
          <a href="/autorities/">Authorities</a>
        </li>
      
        
        <li class="">
          <a href="/definitions/">Definitions</a>
        </li>
      
        
        <li class="">
          <a href="/inquiries/">Inquiries</a>
        </li>
      
        
        <li class="">
          <a href="/appendix1/">Appendix I</a>
        </li>
      
        
        <li class="">
          <a href="/appendix2/">Appendix II</a>
        </li>
      
        
        <li class="sidebar-nav-active">
          <a href="/appendix3/">Appendix III</a>
        </li>
      
    </ul>
  </nav>
  <p>
    <a href="https://github.com/OMBEGOV/a130/edit/gh-pages/pages/appendix3.md">Edit this page</a>
  </p>
</aside>


    <article id="main" class="main-content" role="main">
      <h1>Appendix III</h1>

<h2 id="appendix-iii-to-omb-circular-no.-a-130"><strong>Appendix III to OMB Circular No. A-130</strong></h2>

<p><strong>Responsibilities for Protecting Federal Information Resources</strong></p>

<h3 id="introduction"><strong>Introduction</strong></h3>

<p>Agencies of the Federal Government depend on the secure acquisition, processing, storage, transmission, and disposition of information to carry out their core missions and business functions. This allows diverse information resources ranging from large enterprise information systems (or systems of systems) to small mobile computing devices to collect, process, store, maintain, transmit, and disseminate this information. The information relied upon is subject to a range of threats that could potentially harm or adversely affect organizational operations (e.g., mission, functions, image, or reputation), organizational assets, individuals, other organizations, or the Nation. These threats include environmental disruptions, purposeful attacks, structural failures, human errors, and other threats that can compromise the confidentiality, integrity, or availability of information. Leaders at all levels of the Federal Government must understand their responsibilities and be held accountable for managing information security and protecting privacy.</p>

<p>Federal agencies must implement information security programs and privacy programs with the flexibility to meet current and future information management needs and the sufficiency to comply with applicable requirements. Emerging technologies and services will continue to shift the ways in which agencies acquire, develop, manage, and use information and technology. As technologies and services continue to change, so will the threat environment. Agency programs must have the capability to identify, respond to, and recover from current threats while protecting their information resources and the privacy of the individuals whose information they maintain. The programs must also have the capability to address new and emerging threats. To be effective, information security and privacy considerations must be part of the day-to-day operations of agencies. This is best accomplished by planning for the requisite security and privacy capabilities as an integral part of the agency strategic planning and risk management processes, not as a separate activity. This includes, but is not limited to, the integration of information security and privacy requirements (and security and privacy controls) into the enterprise architecture, system development life cycle activities, systems engineering processes, and acquisition processes.</p>

<p>To ensure that Federal agencies can successfully carry out their assigned missions and business operations in an environment of sophisticated and complex threats, they must deploy systems that are both <em>trustworthy</em> and <em>resilient</em>. To increase the level of trustworthiness and resilience of Federal information systems, the systems should employ technologies that can significantly increase the built-in protection capability of those systems and make them inherently less vulnerable. This can require a significant investment in security architectures, trust technologies, and the application of systems security engineering concepts and principles in the design of Federal information systems with the fundamental objective of strengthening Federal systems to ensure their confidentiality, integrity and availability.</p>

<p>As Federal agencies take advantage of emerging information technologies and services to obtain more effective mission and operational capabilities, achieve greater efficiencies, and reduce costs, they must also apply the principles and practices of risk management, information security, and privacy, to the acquisition and use of those technologies and services. OMB requires agencies to take a risk-based approach to information security to ensure that appropriate safeguards and countermeasures are selected and implemented in a prioritized manner for current missions and business operations. Such risk-based approaches involve framing, assessing, responding to, and monitoring security risks on an ongoing basis. Risk-based approaches can also support potential performance improvements and cost savings when agencies make decisions about maintaining, modernizing, or replacing existing information technologies and services or implementing new technologies and services that leverage internal, other government, or private sector innovative and market-driven solutions. These responsibilities extend to the creation, collection, processing, storage, transmission, dissemination, and disposal of Federal information when such information is hosted by non-Federal entities on behalf of the Federal Government. Ultimately, agency heads remain responsible and accountable for ensuring that information management practices comply with all applicable requirements, and that Federal information is adequately protected commensurate with the risk resulting from the unauthorized access, use, disclosure, disruption, modification, or destruction of such information.</p>

<p>While it is essential for agencies to take a coordinated approach to identifying and addressing security and privacy requirements, it is also important to recognize that security and privacy are different and may require different approaches. For example, privacy laws and policies often establish rules and requirements with which agencies must comply when collecting, using, maintaining, or disseminating personally identifiable information (PII). When agencies are taking steps to meet these specific requirements, a purely risk-based approach is not taken since the requirements must be satisfied in full. However, once these basic requirements are met, agencies are expected to use privacy impact assessments and other tools to further analyze privacy risks and consider the implementation of additional privacy control enhancements to protect against adverse impact on individuals. For more information about privacy requirements, consult Appendix I to this Circular, <em>Responsibilities for Management of Personally Identifiable Information</em>.</p>

<h3 id="purpose"><strong>Purpose</strong></h3>

<p>This Appendix establishes minimum requirements for Federal information security programs, assigns Federal agency responsibilities for the security of information and information systems, and links agency information security programs and agency management control systems established in accordance with OMB Circular No. A-123, <em>Management&rsquo;s Responsibility for Internal Control</em>. This Appendix also establishes requirements for Federal privacy programs, assigns responsibilities for privacy program management, and describes how agencies should take a coordinated approach to implementing information security and privacy controls.</p>

<p>This Appendix revises requirements contained in previous versions of Appendix III to OMB Circular No. A-130, and incorporates requirements of the Federal Information Security Modernization Act of 2014 (44 U.S.C. chapter 35), the E-Government Act of 2002 (44 U.S.C. § 101), and responsibilities assigned in Executive Orders and Presidential Directives.</p>

<h3 id="general-requirements"><strong>General Requirements</strong></h3>

<ol>
<li>Agencies shall ensure the requirements of the Federal Information Technology Acquisition Act (FITARA) are considered in establishing the responsibilities and accountability for the implementation of information and information security programs.</li>
<li><p>Agencies shall develop, implement, document, maintain, and oversee agency-wide information security and privacy programs including people, processes, and technologies to:</p>

<ol>
<li>Provide for agency information security and privacy policies, planning, budgeting, management, implementation, and oversight;</li>
<li>Cost-effectively manage information security risk, which includes reducing such risk to an acceptable level;</li>
<li>Ensure compliance with all applicable privacy requirements in law, regulation, and policy, and use privacy impact assessments and other tools to analyze and address privacy risks;</li>
<li>Protect information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide for their confidentiality, integrity, and availability;</li>
<li>Provide adequate security for all information, including PII, created, collected, processed, stored, transmitted/disseminated, or disposed of by or on behalf of the Federal Government, to include Federal information residing in contractor information systems and networks;</li>
<li>Employ systems security engineering concepts and techniques during the development of new or updated information systems to facilitate the trustworthiness and resilience of those systems;</li>
<li>Implement supply chain risk management principles to protect against the insertion of counterfeits, unauthorized production, tampering, theft, insertion of malicious software, as well as poor manufacturing and development practices throughout the system development lifecycle;</li>
<li>Provide information security safeguards and countermeasures commensurate with the risk from unauthorized access, use, disclosure, disruption, modification, or destruction of information collected or maintained by or on behalf of the agency and information systems used or operated by an agency, or by a contractor of an agency or other organization on behalf of an agency;</li>
<li>Implement an agency-wide risk management approach that frames, assesses, responds to, and monitors information security risk across three organizational tiers (i.e., organization level, mission/business process level, and information system level);</li>
<li>Implement a risk management framework to guide and inform the categorization of Federal information and information systems; the selection, implementation, and assessment of security and privacy controls; the authorization of information systems and common controls; and the continuous monitoring of information systems and environments of operation;</li>
<li>Ensure, for information systems and the environments in which those systems operate, that security and privacy controls are implemented correctly, operating as intended, and continually monitored and assessed; that procedures are in place to ensure that security and privacy controls remain effective over time; and that steps are taken to maintain risk at an acceptable level within organizational risk tolerance;</li>
<li>Implement policies and procedures to ensure that all personnel are held accountable for complying with agency-wide information security and privacy programs; and</li>
<li>Ensure that performance plans for all Federal employees include an element addressing the need to adhere to Federal and agency-specific requirements for the protection of information and information systems; and for individuals with significant security and privacy responsibilities, include requirements regarding their role in protecting information and information systems.</li>
</ol></li>
<li><p>Agencies shall protect Controlled Unclassified Information (CUI) in accordance with requirements set forth by the National Archives and Records Administration.</p></li>
<li><p>Agencies shall implement security and privacy policies issued by the Office of Management and Budget (OMB), and related government-wide requirements and procedures issued by the Department of Commerce, Department of Homeland Security, General Services Administration, and the Office of Personnel Management. This includes applying the standards and guidelines contained in National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS), NIST (800-series) Special Publications, and, where appropriate and directed by OMB, NIST Interagency or Internal Reports (NISTIRs).</p></li>
<li><p>Agencies shall ensure that all contracts, grants, and other third-party agreements for services incorporate all relevant information security and privacy requirements outlined in law, OMB policy, Executive Orders, and Presidential Directives.</p></li>
</ol>

<h3 id="specific-requirements"><strong>Specific Requirements</strong></h3>

<ol>
<li>Security Categorization</li>
</ol>

<p>Agencies shall:</p>

<ol>
<li>Identify authorization boundaries for information systems; and</li>
<li><p>Categorize information and information systems, in accordance with FIPS Publication 199 and NIST Special Publication 800-60, considering potential adverse security and privacy impacts to organizational operations and assets, individuals, other organizations, and the Nation.</p></li>
<li><p>Planning, Budgeting, and Enterprise Architecture</p></li>
</ol>

<p>Agencies shall:</p>

<ol>
<li>Identify and plan for the resources needed to implement information security and privacy programs;</li>
<li>Ensure that information security and privacy is addressed throughout the life cycle of each agency information system, and that security and privacy activities and costs are explicitly identified and included in IT investment capital plans and budgetary requests;</li>
<li>Plan and budget to replace any legacy information systems for which security and privacy protections commensurate with risk cannot be effectively implemented;</li>
<li>Ensure that investment plans submitted to OMB as part of the budget process meet the information security and privacy requirements appropriate for the life cycle stage of the investment; and</li>
<li><p>Incorporate information security and privacy requirements into the organization&rsquo;s enterprise architecture to ensure information systems and the environments in which those systems operate achieve the necessary levels of trustworthiness, protection, and resilience.</p></li>
<li><p>Plans, Controls, and Assessments</p></li>
</ol>

<p>Agencies shall:</p>

<ol>
<li>Develop and maintain information security program and privacy program plans that provide an overview of the organization-wide information security and privacy requirements and describe the program management controls and common controls in place or planned for meeting those requirements;</li>
<li>Employ a system life cycle process that incorporates the principles, concepts, methods, and techniques of systems security engineering as described in NIST Special Publication 800-160 to ensure the development of trustworthy and resilient information systems;</li>
<li>Develop supply chain risk management plans for all organizational tiers as described in NIST Special Publication 800-161 to ensure the integrity, security, resilience, and quality of information systems;</li>
<li>Implement a risk-based security control selection process for information systems and environments of operation that satisfies the minimum information security requirements in FIPS Publication 200 and security control baselines in NIST Special Publication 800-53, tailored as appropriate;</li>
<li>Implement a privacy control selection process for information systems and environments of operation that satisfies the privacy requirements in OMB guidance, including, but not limited to, Appendix I to this Circular, OMB Circular No. A-108, <em>Federal Agency Responsibilities for Review, Reporting, and Publication under the Privacy Act</em>, and NIST Special Publication 800-53;</li>
<li>Develop and maintain security and privacy plans for information systems and environments of operation to record security and privacy controls and implementation details;</li>
<li>Designate common controls in order to provide cost-effective security and privacy capabilities that can be inherited by multiple organizational information systems;</li>
<li>Implement security controls and privacy controls in information systems and environments of operation using systems/security engineering principles, concepts, methods, practices, and techniques;</li>
<li>Deploy effective security controls to provide Federal employees and contractors with multifactor authentication, digital signature, and encryption capabilities that provide assurance of identity and are interoperable and accepted across all Executive Branch agencies;</li>
<li>Assess all selected and implemented security and privacy controls in organizational information systems (and environments in which those systems operate) prior to operation, and periodically thereafter, consistent with the frequency defined in the organizational information security continuous monitoring (ISCM) and privacy continuous monitoring (PCM) strategies and the organizational risk tolerance;</li>
<li>Conduct and record the results of security control assessments and privacy control assessments in security and privacy assessment reports, respectively;</li>
<li>Use agency Plans of Action and Milestones (POA&amp;Ms), and make available or provide access to OMB, DHS, Inspectors General, and the Government Accountability Office, upon request, to record and manage the mitigation and remediation of identified weaknesses and deficiencies, not associated with accepted risks, in organizational information systems and environments of operation; and</li>
<li><p>Obtain approval from the authorizing official for connections from the information system, as defined by its authorization boundary, to other information systems based on the risk to the organization&rsquo;s operations and assets, individuals, other organizations, and the Nation.</p></li>
<li><p>Authorization and Continuous Monitoring</p></li>
</ol>

<p>Agencies shall:</p>

<ol>
<li>Designate senior Federal officials to formally: authorize an information system to operate; and authorize organization-designated common controls for use based on a determination of, and explicit acceptance of, the information security and privacy risk to organizational operations and assets, individuals, other organizations, and the Nation, and prior to operational status;</li>
<li>Complete an initial authorization for each information system and all organization-designated common controls;</li>
<li>Transition information systems and common controls to an ongoing authorization process when eligible for such a process and with the formal approval of the respective authorizing officials;</li>
<li>Reauthorize information systems and common controls as needed, on a time- or event-driven basis in accordance with organizational risk tolerance;</li>
<li><p>Develop and maintain an ISCM strategy and PCM strategy to address information security and privacy risks and requirements across the organizational risk management tiers (i.e., organization/governance tier, mission/business process tier, and/or information system tier);</p></li>
<li><p>Implement and periodically update the ISCM strategy and PCM strategy to reflect: the effectiveness of deployed controls; significant changes to information systems and environments of operations; and adherence to Federal statutes, policies, directives, instructions, regulations, standards, and guidelines;</p></li>
<li><p>Ensure that all selected and implemented controls are addressed in the ISCM strategy and PCM strategy and are effectively monitored on an ongoing basis, as determined by the agency&rsquo;s ISCM and PCM programs;</p></li>
<li><p>Establish and maintain an ISCM program that:</p></li>
<li><p>Provides an understanding of organizational risk tolerance and helps officials set priorities and manage information security risk consistently throughout the organization;</p></li>
<li><p>Includes metrics that provide meaningful indications of security status at all organizational tiers;</p></li>
<li><p>Ensures the continued effectiveness of all security controls selected and implementedby monitoring controls with the frequencies specified in the ISCM strategy;</p></li>
<li><p>Verifies compliance with information security requirements derived from missions/business functions, Federal statutes, directives, instructions, regulations, policies, and standards/guidelines;</p></li>
<li><p>Is informed by all applicable organizational IT assets to help maintain visibility into the security of the assets;</p></li>
<li><p>Ensures knowledge and control of changes to information systems and environments of operation; and</p></li>
<li><p>Maintains awareness of threats and vulnerabilities;</p></li>
<li><p>Establish and maintain a PCM program that:</p>
<div class="highlight"><pre><code class="language-" data-lang="">1. Ensures continued compliance with all applicable privacy requirements;
2. Verifies the continued effectiveness of all privacy controls selected and implemented across all organizational tiers;
3. Includes metrics to monitor the effective implementation of privacy requirements and privacy controls across all organizational tiers;
4. Monitors changes to information systems and environments of operation that collect, process, store, maintain, use, or disseminate PII; and
5. Maintains adequate awareness of any threats and vulnerabilities that may affect PII and impact individual privacy;
</code></pre></div></li>
<li><p>Ensure that a robust ISCM program and PCM program are in place before organizational information systems or common controls are eligible for ongoing authorization; and</p></li>
<li><p>Leverage available Federal shared services, where practicable and appropriate.</p></li>
<li><p>Privacy Controls for Federal Information Systems and Organizations</p></li>
</ol>

<p>The senior agency official for privacy (SAOP) has overall agency-wide responsibility and accountability for developing, implementing, and maintaining an organization-wide governance and privacy program to ensure compliance with all applicable laws, regulations, and policies regarding the collection, use, maintenance, dissemination, and disposal of PII by programs and information systems. The SAOP shall:</p>

<ol>
<li>Develop and maintain a PCM strategy to address privacy risks and requirements across the organizational risk management tiers (i.e., organization/governance tier, mission/business process tier, and/or information system tier);</li>
<li>Establish and maintain a PCM program to maintain ongoing awareness of privacy risks and assess privacy controls at a frequency sufficient to ensure compliance with applicable requirements and to adequately protect PII;</li>
<li>Review IT capital investment plans and budgetary requests to ensure that privacy requirements (and associated privacy controls), as well as any associated costs, are explicitly identified and included;</li>
<li>Review and approve, in accordance with NIST FIPS Publication 199 and Special Publication 800-60, the categorization of information systems that collect, process, store, maintain, or disseminate PII;</li>
<li>Designate system-specific, hybrid, and common privacy controls;</li>
<li>Review and approve the privacy plans for organizational information systems prior to authorization, reauthorization, or ongoing authorization;</li>
<li>Conduct privacy control assessments to ensure that privacy controls are implemented correctly, operating as intended, and effective in satisfying privacy requirements; and</li>
<li><p>Review authorization packages and determine that all applicable privacy requirements are met and the risk to PII is sufficiently addressed prior to authorizing officials making risk determination and acceptance decisions.</p>

<ol>
<li>Incident Detection, Response and Recovery</li>
</ol></li>
</ol>

<p>After agencies have selected and implemented the necessary security controls to protect their information and systems consistent with their understanding of organizational operations and assets and management of information security risk, agencies shall subsequently ensure they can react appropriately to information security incidents.</p>

<p>Agencies shall:</p>

<ol>
<li>Develop and implement incident management policies and procedures that address incident detection, response, and recovery. This includes developing and implementing appropriate activities to identify the occurrence of an incident; developing and implementing appropriate activities to take action regarding a detected cybersecurity incident; and developing and implementing the appropriate activities to maintain plans for resilience and to restore any capabilities or services that were impaired due to an incident;</li>
<li>Designate sensitive positions and execute commensurate security clearance levels for appropriate agency personnel;</li>
<li>Establish clear roles and responsibilities to ensure the oversight and coordination of incident response activities and that incidents are appropriately documented, reported, investigated and handled;</li>
<li>Periodically test incident response procedures to ensure effectiveness of such procedures;</li>
<li>Document lessons learned for incident response and update procedures annually and/or as required by OMB and/or DHS;</li>
<li>Ensure processes are in place to verify corrective actions;</li>
<li>Maintain formal security and privacy incident response capabilities and mechanisms to include breach notification and adequate training and awareness for employees and contractors on how to report and respond to security and privacy incidents;</li>
<li>Report security and privacy incidents to OMB, DHS, the SAOP, their respective Inspectors General and General Counsel, law enforcement, and Congress in accordance with procedures issued by OMB;</li>
<li>Implement formal security and privacy incident policies to include definitions, detection and analysis, containment, internal and external notification and reporting requirements, incident reporting methods, post-incident procedures, roles and responsibilities, and guidance on how to mitigate impacts to the agency and its respondents following an incident; and</li>
<li><p>Provide reports on incidents as required by FISMA, OMB policy, DHS binding operational directives, US-CERT guidelines, NIST guidelines, and agency procedures.</p></li>
<li><p>Contingency Planning</p></li>
</ol>

<p>Agencies shall:</p>

<ol>
<li><p>Develop contingency plans for information systems that:</p></li>
<li><p>Identify essential missions and business functions and associated contingency requirements;</p></li>
<li><p>Provide recovery objectives, restoration priorities, and metrics;</p></li>
<li><p>Address contingency roles and responsibilities; and</p></li>
<li><p>Address maintaining essential missions and business functions despite a disruption, compromise, or failure of information systems; and</p></li>
<li><p>Provide for the recovery and reconstitution of information systems to a known state after a disruption, compromise, or failure.</p></li>
<li><p>Awareness and Training</p></li>
</ol>

<p>Agencies shall:</p>

<ol>
<li>Develop and maintain mandatory agency-wide information security and privacy awareness and training programs for all employees and contractors;</li>
<li>Ensure that the security and privacy awareness and training programs are consistent with applicable standards and guidelines issued by OMB, NIST, and OPM;</li>
<li>Apprise agency personnel about available assistance and technical security and privacy products and techniques;</li>
<li>Provide foundational as well as more advanced levels of security and privacy awareness training to information system users (including managers, senior executives, and contractors) and ensure that measures are in place to test the knowledge level of information system users;</li>
<li>Provide role-based security and privacy training to personnel with assigned security and privacy roles and responsibilities before authorizing access to the information system or performing assigned duties;</li>
<li>Establish rules of behavior, that include consequences for violating rules of behavior, for personnel having access to organizational information and information systems;</li>
<li>Ensure that agency personnel have read and agreed to abide by the rules of behavior for the information systems for which they require access prior to being granted access; and</li>
<li><p>Enforce consequences for violating rules of behavior to include reprimand, suspension, removal, or other actions in accordance with applicable law and agency policy.</p></li>
<li><p>Specific Safeguarding Measures to Reinforce the Protection of Federal Information and Information Systems</p></li>
</ol>

<p>Agencies shall:</p>

<ol>
<li>Implement a policy of least functionality by only permitting the use of networks, systems, applications, and data, as well as programs, functions, ports, protocols, and/or services that are necessary in meeting mission or business needs;</li>
<li>Implement policies of least privilege at multiple layers – network, system, application, and data so that users have role-based access to only the information and resources that are necessary for legitimate purpose;</li>
<li>Implement a policy of separation of duties to address the potential for abuse of authorized privileges and help to reduce the risk of malicious activity without collusion;</li>
<li>Isolate sensitive and/or critical information resources (e.g., information systems, system components, applications, databases, and information) into separate security domains with appropriate levels of protection based on the sensitivity/criticality of those resources;</li>
<li>Implement access control policies for information resources that ensure individuals have appropriate authorization and need, and that the appropriate level of identity proofing and/or background investigation is conducted prior to granting access;</li>
<li>Protect administrator, user, and system documentation related to the design, development, operation, maintenance, and security of the hardware, firmware, and software components of information systems;</li>
<li>Continuously monitor, log, and audit the execution of information system functions by privileged users to detect misuse and to help reduce the risk from insider threats;</li>
<li><p>Prohibit the use of unsupported information systems and system components, and ensure that systems and components that cannot be appropriately protected or secured are given a high priority for upgrade or replacement;</p></li>
<li><p>Implement and maintain current updates and patches for all software and firmware components of information systems;</p></li>
<li><p>For systems that promote public access, ensure that identity proofing, registration, and authentication processes provide assurance of identity consistent with security and privacy requirements, in accordance with Executive Order 13681,</p></li>
</ol>

<p>OMB policy, and NIST standards and guidelines;
11. Require use of multifactor authentication for employees and contractors in accordance with government-wide identity management standards;
12. Encrypt all moderate-impact and high-impact information at rest and in transit, unless encrypting such information: is technically infeasible or would demonstrably affect the ability of agencies to carry out their respective missions, functions, or operations; and the risk of not encrypting is accepted by the authorizing official and approved by the agency CIO;
13. Implement the current encryption algorithms and validated cryptographic modules in accordance with NIST standards and guidelines;
14. Ensure that only users with legitimate need for access have the ability to decrypt sensitive information.
15. Develop and implement policies and procedures to support employees and contractors in uniformly applying digital signatures to secure documents and communications;
16. Implement attribute-based access controls</p>

<p>to control and monitor access to Federal information; and
17. Ensure that all Federal systems and services identified in the Domain Name System are protected with Domain Name System Security (DNSSEC) and that all systems are capable of validating DNSSEC protected information.</p>

<ol>
<li>Contracts, Grants, and Agreements</li>
</ol>

<p>Organizations that collect or maintain information on behalf on a Federal agency or that operate or use information systems on behalf of a Federal agency, must comply with the requirements in the FISMA and OMB policies. Agencies shall ensure that terms and conditions in contracts, grants, and agreements involving the processing, storage, transmission, and destruction of Federal information are sufficient to enable agencies to meet necessary security and privacy requirements concerning Federal information. For additional information and associated requirements pertaining to information technology acquisitions, refer to the Federal Acquisition Regulation.</p>

<ol>
<li>Oversight of Non-Federal Entities</li>
</ol>

<p>Agencies shall:</p>

<ol>
<li><p>Provide oversight of information systems used or operated by contractors or other entities on behalf of the Federal government or that collect or maintain Federal information on behalf of the Federal government, to include:</p></li>
<li><p>Documenting and implementing policies and procedures for information security and privacy oversight, to include ensuring appropriate vetting and access control processes for contractors and others with access to systems containing Federal information;</p></li>
<li><p>Ensuring that security and privacy controls of such information systems and services are effectively implemented and comply with NIST standards and guidelines and organizational requirements;</p></li>
<li><p>Maintaining and continuously updating an inventory of information systems and system components using automated reporting, cataloguing, and inventory tools;</p></li>
<li><p>Ensuring that the inventory identifies interfaces between these systems and organization-operated systems;</p></li>
<li><p>Ensuring that procedures are in place for incident response for these systems including timelines for breach notification;</p></li>
<li><p>Requiring agreements (e.g., Memorandum of Understandings, Interconnection Security Agreements, contracts) for interfaces between these systems and agency-owned and operated systems; and</p></li>
<li><p>Implementing policies, procedures, and verification methods to ensure, within the risk tolerance of the agency, that systems that are owned or operated by contractors or entities that contain Federal information are compliant with FISMA requirements, OMB policies, and applicable NIST standards and guidelines;</p></li>
<li><p>Collaborate with non-Federal entities and other agencies as appropriate to ensure that security and privacy requirements pertaining to these non-Federal entities, such as State, local, tribal, and territorial governments, are consistent to the greatest extent possible; and</p></li>
<li><p>Ensure that non-Federal entities protect CUI in accordance with NARA requirements and any associated NIST standards and guidelines.</p></li>
<li><p>Mitigation of Deficiencies and Issuance of Status Reports</p></li>
</ol>

<p>Agencies must correct deficiencies that are identified through information security and privacy assessments, ISCM and PCM programs, or internal/external audits and reviews, to include OMB reviews. OMB Circular No. A-123, <em>Management&rsquo;s Responsibility for Internal Control</em>, provides guidance to determine whether a deficiency in controls is material when so judged by the agency head against other agency deficiencies. Material deficiencies must be included in the annual Federal Managers Financial Integrity Act (FMFIA) report, and remediation tracked and managed through the agency&rsquo;s POA&amp;M process. Less significant deficiencies need not be included in the FMFIA report, but must be tracked and managed through the agency&rsquo;s POA&amp;M process.</p>

<ol>
<li>Reporting</li>
</ol>

<p>Agencies shall provide FISMA reports in accordance with processes established by OMB and DHS.</p>

<ol>
<li>Cybersecurity Framework</li>
</ol>

<p>The Cybersecurity Framework was developed by NIST in response to Executive Order 13636, <em>Improving Critical Infrastructure Cybersecurity</em>. The Framework describes five core cybersecurity functions (i.e., Identify, Protect, Detect, Respond, and Recover) that may be helpful in raising awareness and facilitating communication among agency stakeholders, including executive leadership. The Cybersecurity Framework may also be helpful in improving communications across organizations, allowing cybersecurity expectations to be shared with business partners, suppliers, and among sectors. The Framework is not intended to duplicate the current information security and risk management practices in place within the Federal Government. However, in the course of managing information security risk using the established NIST Risk Management Framework and associated security standards and guidelines required by FISMA, agencies can leverage the Cybersecurity Framework to complement their current information security programs. NIST will provide additional guidance on how agencies can use the Cybersecurity Framework and in particular, how the two frameworks can work together to help agencies develop, implement, and continuously improve their information security programs.</p>

<ol>
<li>Independent Evaluations</li>
</ol>

<p>Agencies shall:</p>

<ol>
<li><p>Perform an independent evaluation of the information security programs and practices to determine the effectiveness of such programs and practices. The evaluation may include an evaluation of their privacy program and practices, as appropriate. Each evaluation must include:</p></li>
<li><p>Testing of the effectiveness of information security policies, procedures, and practices of a representative subset of the agency&rsquo;s information systems;</p></li>
<li><p>An assessment of the effectiveness of the information security policies, procedures, and practices of the agency; and</p></li>
<li><p>Separate presentations, as appropriate, regarding information security relating to national security systems.</p></li>
<li><p>For each agency with an Inspector General appointed under the Inspector General Act of 1978, the annual evaluation required by this section must be performed by the Inspector General or by an independent external auditor, as determined by the Inspector General of the agency. For agencies in which the Inspector General Act of 1978 does not apply, the head of the agency shall engage an independent external auditor to perform the evaluation.</p></li>
</ol>

<h3 id="government-wide-responsibilities"><strong>Government-wide Responsibilities</strong></h3>

<ol>
<li>Department of Commerce</li>
</ol>

<p>The Secretary of Commerce shall:</p>

<ol>
<li>Develop and issue standards and guidelines for the security and privacy of information in Federal information systems, and systems which create, collect, process, store, transmit/disseminate, or dispose of information on behalf of the Federal Government;</li>
<li>Review and update guidelines for information security awareness, training, and education and accepted information security practices, with assistance from OPM;</li>
<li>Provide guidance to agencies to assist in their development of security plans;</li>
<li>Provide guidance and assistance, as appropriate, to agencies concerning cost-effective security controls;</li>
<li>Evaluate new information technologies to assess their security vulnerabilities, with technical assistance from the Department of Defense (DoD) and DHS;</li>
<li>Follow a transparent process that allows and addresses input from the agencies and the public when developing standards and guidelines; and</li>
<li><p>Solicit and consider the recommendations of the Information Security and Privacy Advisory Board, established by the National Institute of Standards and Technology Act.</p></li>
<li><p>Department of Homeland Security</p></li>
</ol>

<p>The Secretary of Homeland Security shall:</p>

<ol>
<li>Monitor and assist agencies with the implementation of information security policies and practices for information systems;</li>
<li>Assist OMB in carrying out its information security oversight and policy responsibilities;</li>
<li><p>Develop and oversee the implementation of binding operational directives that reinforce the policies, principles, standards, and guidelines developed by OMB, that focus on:</p>

<ol>
<li>Requirements for the mitigation of exigent risks to information systems;</li>
<li>Requirements for the mitigation of known or reasonably suspected information security threats, vulnerabilities, and risks;</li>
<li>Requirements for reporting incidents to the Federal information security incident center; and</li>
<li>Other operational requirements, as deemed necessary by OMB;</li>
</ol></li>
<li><p>Coordinate the development of binding operational directives and the oversight of the implementation of such directives with OMB and NIST to ensure consistency with OMB policies and NIST standards and guidelines;</p></li>
<li><p>Consult with the Director of NIST regarding any binding operational directives that implement or affect the standards and guidelines developed by NIST;</p></li>
<li><p>Convene meetings with senior agency officials to help ensure the effective implementation of information security policies and procedures;</p></li>
<li><p>Coordinate government-wide efforts on information security policies and practices, including consultation with the CIO Council and NIST;</p></li>
<li><p>Manage government-wide information security programs and provide and operate Federal information security shared services, as directed by OMB;</p></li>
<li><p>Provide operational and technical assistance to agencies in implementing policies, principles, standards, and guidelines on information security. This includes:</p>

<ol>
<li>Operating the Federal information security incident center;</li>
<li>Deploying technology to assist agencies to continuously diagnose and mitigate cyber threats and vulnerabilities, with or without reimbursement and at the request of the agency;</li>
<li>Compiling and analyzing data on agency information security; and</li>
<li>Developing and conducting targeted operational evaluations, including threat and vulnerability assessments, on information systems;</li>
</ol></li>
<li><p>Provide agencies with intelligence about cyber threats, vulnerabilities, and incidents for risk assessments and proactive mitigation;</p></li>
<li><p>Consult with OMB to determine what other actions may be necessary to support implementation of effective government-wide information security programs;</p></li>
<li><p>Provide the public with timely notice and opportunities for comment on proposed information security directives and procedures to the extent that such directives and procedures affect the public or communication with the public; and</p></li>
<li><p>Solicit and consider the recommendations of the Information Security Privacy Advisory Board, established by the National Institute of Standards and Technology Act.</p></li>
<li><p>Department of Defense</p></li>
<li><p>The Secretary of Defense shall:</p></li>
<li><p>Provide technical advice and assistance to the Departments of Commerce and Homeland Security; and</p></li>
<li><p>Assist the Departments of Commerce and Homeland Security in evaluating the vulnerabilities of emerging information technologies.</p></li>
<li><p>Department of Justice</p></li>
<li><p>The Attorney General shall:</p></li>
<li><p>Provide guidance to agencies on legal remedies regarding security incidents and ways to report and work with law enforcement concerning such incidents; and</p></li>
<li><p>Pursue appropriate legal actions when security incidents occur.</p></li>
<li><p>Federal CIO Council</p></li>
<li><p>The Federal CIO Council, in consultation with the Director of the Office of Personnel Management shall:</p></li>
<li><p>Ensure that policies concerning information security training for Federal civilian employees are effective; and</p></li>
<li><p>Assist the Department of Commerce in updating and maintaining guidelines for security and privacy training and education.</p></li>
<li><p>General Services Administration</p></li>
<li><p>The Administrator of General Services shall:</p></li>
<li><p>When working with agencies on information technology acquisitions, ensure that information security requirements are addressed and included as part of the acquisitions, and that the security requirements reinforce government-wide initiatives, policies and standards;</p></li>
<li><p>Facilitate the development of contract vehicles for agencies to use in the acquisition of cost-effective security products and services and, in doing so, ensure these contract vehicles provide for capabilities that are consistent with government-wide requirements;</p></li>
<li><p>Provide security-related services to meet the needs of agencies to the extent that such services are cost-effective and consistent with government-wide requirements;</p></li>
<li><p>Ensure security requirements are implemented in government-wide contracts.</p></li>
<li><p>Maintain a Federal public key infrastructure (FPKI)
framework to allow efficient interoperability among agencies when using digital certificates;</p></li>
<li><p>Ensure effective controls are in place to protect the confidentiality, integrity, availability of the FPKI framework components managed by the agency; and</p></li>
<li><p>Provide oversight of agency compliance with FPKI policy.</p></li>
<li><p>g. Office of Personnel Management</p></li>
<li><p>The Director of the Office of Personnel Management shall determine the minimum investigative requirements for Federal employees and contractors requiring access to Federal facilities, information, and/or information systems.</p></li>
<li><p><strong>Discussion of the Major Provisions in the Appendix</strong></p></li>
</ol>

<h3 id="nist-standards-and-guidelines"><strong>NIST Standards and Guidelines</strong></h3>

<ol>
<li>NIST standards and guidelines associate each information system with an impact level. The standards and guidelines also provide a corresponding starting set of baseline security controls and tailoring guidance to ensure that the set of security controls in the security plan (approved by the authorizing official) and privacy controls in the privacy plan (approved by the SAOP), satisfy the information security, privacy, and mission/business protection needs of the organization.</li>
<li>For non-national security programs and information systems, agencies must apply NIST guidelines unless otherwise stated by OMB. Federal Information Processing Standards (FIPS) are mandatory. There is flexibility within NIST&rsquo;s guidelines (specifically in the 800-series) in how agencies apply those guidelines. Unless specified by additional implementing policy by OMB, the concepts and principles described in NIST guidelines must be applied. However, NIST guidelines generally allow agencies latitude in their application. Consequently, the application of NIST guidelines by agencies can result in different security solutions that are equally acceptable and compliant with the guidelines.</li>
<li>For legacy information systems, agencies are expected to meet the requirements of, and be in compliance, with NIST standards and guidelines within one year of their respective publication dates unless otherwise directed by OMB. The one-year compliance date for revisions to NIST publications applies only to new or updated material in the publications. For information systems under development or for legacy systems undergoing significant changes, agencies are expected to meet the requirements of, and be in compliance with, NIST standards and guidelines immediately upon deployment of the systems.</li>
</ol>

<h3 id="risk-management-framework"><strong>Risk Management Framework</strong></h3>

<ol>
<li>The Risk Management Framework (RMF) provides a disciplined and structured process that integrates information security and risk management activities into the system development life cycle. The RMF requires agencies to categorize each information system and the information processed, stored, and transmitted by that system based on a mission/business impact analysis. Agencies select an initial set of baseline security controls for the information system based on the security categorization and then tailor the security control baseline as needed, based on an organizational assessment of risk and local conditions. After implementing the security controls, agencies assess the controls using appropriate assessment methods as described in NIST Special Publication 800-53A 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.</li>
<li>The authorization to operate the system is based on a determination of the risk to organizational operations and assets, individuals, other organizations, and the Nation resulting from the operation and use of the system and the decision by the authorizing official, that this risk is acceptable. Subsequent to the authorization decision and as part of an information security continuous monitoring strategy and program, agencies monitor the security controls in the system on an ongoing basis. Monitoring includes, but is not limited to, assessing control effectiveness, documenting changes to the system or its environment of operation, conducting security impact analyses of the associated changes, and reporting the security state of the system to designated organizational officials on an ongoing basis.</li>
<li>An effective implementation of the RMF ensures that managing information system-related security risks is consistent with the agency&rsquo;s mission/business objectives and overall risk management strategy, and risk tolerance established by the senior leadership through the risk executive function
as discussed in NIST Special Publication 800-37. It also ensures that the requisite security requirements and controls are integrated into the agency&rsquo;s enterprise architecture and system development life cycle processes. Finally, the RMF supports consistent, well-informed, and ongoing security authorization decisions, transparency of security and risk management information, reciprocity, and information sharing.
4.</li>
</ol>

<h3 id="security-control-baselines"><strong>Security Control Baselines</strong></h3>

<ol>
<li>It is important to achieve adequate security for Federal information and information systems and a consistent level of protection for such information and systems government-wide. To meet this objective, agencies must select an appropriate set of security controls for their information systems that satisfy the minimum security requirements set forth in FIPS Publication 200. The security controls must include one of the three security control baselines from NIST Special Publication 800-53 that are associated with the designated impact levels of their information systems. The security control baselines define the set of minimum security controls for a low-impact, moderate-impact, or high-impact information system and provide a starting point for the tailoring process. Agencies are required to tailor the security control baselines to customize their safeguarding measures for specific missions, business lines, and operational environments—and to do so in a cost-effective, risk-based manner. Tailoring allows agencies to designate common controls; apply scoping considerations; select compensating controls; assign specific values to organization-defined control parameters; supplement baselines with additional controls when necessary; and provide additional specification information for control implementation. Agencies must provide a justification for any tailoring actions that result in changes to the initial security control baselines. Agencies are not permitted to make changes to security control baselines when such changes result in control selections that are inconsistent with security requirements set forth in Federal laws, Executive Orders, regulations, directives, or policies.</li>
<li>Agencies may also develop overlays as part of the security control selection process. Overlays provide a specification of security and/or privacy controls, control enhancements, supplemental guidance, and other supporting information as part of the tailoring process, that is intended to complement (and further refine) security control baselines. The overlay may be more stringent or less stringent than the original security control baseline and can be applied to multiple systems. All selected security controls must be documented in a security plan and implemented. Agencies can use the priority code designations associated with each security control in NIST Special Publication 800-53 to assist in making sequencing decisions for control implementation. This prioritization helps to ensure that the foundational security controls upon which other controls depend are implemented first, thus enabling organizations to deploy controls in a more structured and timely manner in accordance with available resources. Independent evaluations, when conducted, should focus on the effectiveness of the security controls selected and implemented (as documented in agency security plans after all tailoring actions have been completed on the security control baselines) and the justification for any decisions to change the control baselines.</li>
</ol>

<h3 id="security-and-privacy-assessments"><strong>Security and Privacy Assessments</strong></h3>

<ol>
<li>Agencies must ensure that periodic testing and evaluation of the effectiveness of information security and privacy policies, procedures, and practices are performed with a frequency depending on risk, but no less than annually. This requirement does not imply that agencies must assess every selected and implemented security and privacy control at least annually. Rather, agencies must continuously monitor all implemented security and privacy controls (i.e., system-specific, hybrid, and common controls) with a frequency determined by the organization in accordance with the ISCM and PCM strategies. These strategies will define the specific security and privacy controls selected for assessment during any one-year period (i.e., the annual assessment window) with the understanding that all controls may not be formally assessed every year. Rotational assessment of security and privacy controls is consistent with the transition to ongoing authorization and assumes the information system has completed an initial authorization where all controls were formally assessed for effectiveness.</li>
<li>Security and privacy control assessments should ensure that security and privacy controls selected by agencies are implemented correctly, operating as intended, and effective in satisfying security and privacy requirements. The security of information may change over time based on changes in the threat, organizational missions/business functions, personnel, technology, or environments of operation. Consequently, maintaining a capability for real-time or near real-time analysis of the threat environment and situational awareness following an information security incident is paramount. The type, rigor, and frequency of control assessments should be commensurate with the level of awareness necessary for effectively determining information security risk that is established by the organization&rsquo;s risk tolerance and risk management strategy. Technical security tools such as malicious code scanners, vulnerability assessment products (which look for known security weaknesses, configuration errors, and the installation of the latest patches), and penetration testing can assist in the ongoing assessment of information systems.</li>
</ol>

<h3 id="authorizing-official"><strong>Authorizing Official</strong></h3>

<ol>
<li>The authorizing official is a senior agency official or executive with the authority to formally assume responsibility for operating an information system at an acceptable level of risk to organizational operations and assets, individuals, other organizations, and the Nation. Authorizing officials have budgetary oversight for an information system or are responsible for the mission or business operations supported by the system. Through the authorization process, authorizing officials are responsible and accountable for the security risks associated with information system operations. Because information security is closely related to the individual privacy protections required for PII (see <em>Fair Information Practice Principles</em>), authorizing officials are also responsible and accountable for the privacy-related risks that arise from the operation of an information system.Accordingly, authorizing officials must be in management positions with a level of authority commensurate with understanding and accepting such information system-related <em>security</em> and <em>privacy</em> risks. Since the SAOP is the senior official, designated by the head of each agency, who has overall agency-wide responsibility for information privacy, agencies must consider inputs and recommendations submitted by the SAOP in the authorization decision.Additionally, the SAOP has responsibility for reviewing the authorization package to ensure that privacy risks are addressed prior to system authorization.</li>
<li>Agencies can choose from several different approaches when planning for and conducting authorizations. These include an authorization with a single authorizing official, an authorization with multiple authorizing officials, or leveraging an existing authorization (see Section 8, <em>Joint and Leveraged Authorizations</em>). Agencies can, at their discretion, include the CIO or the SAOP as co-authorizing officials with other senior agency officials responsible for the mission or line of business supported by the system being authorized for operation. Regardless of the approach used, the role of authorizing official has inherent U.S. Government authority and is assigned to government personnel only.</li>
</ol>

<h3 id="authorization-to-operate"><strong>Authorization to Operate</strong></h3>

<ol>
<li><p>The authorization to operate an information system and the authorization of organization-designated common controls granted by senior Federal officials provide an important quality control for agencies. The decision to authorize a system to operate should be based on a review of the authorization package and includes an assessment of compliance with applicable requirements and risk to organizational operations (including mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation. As stated above, the decision to authorize a system, or organization-defined common controls, should be made by the appropriate authorizing official – an agency official responsible for the associated missions, business functions, and/or supporting infrastructure. Since the security plan and privacy plan establish the security and privacy controls selected for implementation, those plans are a critical part of the authorization package and should form the basis for the authorization, supplemented by more specific information as needed.</p></li>
<li><p><strong>Ongoing Authorization</strong></p></li>
</ol>

<h3 id="ongoing-authorization">Ongoing authorization</h3>

<p>is a process whereby the authorizing official makes risk determination and risk acceptance decisions subsequent to the initial authorization, taken at agreed-upon and documented frequencies in accordance with the agency&rsquo;s risk tolerance and mission/business requirements. Ongoing authorization is a time-driven or event-driven authorization process whereby the authorizing official is provided with the necessary and sufficient information regarding the near real-time state of the information system and inherited common controls to determine whether or not all applicable security and privacy requirements have been satisfied and the mission/business risk is acceptable. Effective ongoing authorization requires robust ISCM and PCM strategies and effective operational ISCM and PCM programs. Agencies can move from a static, point-in-time authorization process to a dynamic, near real-time ongoing authorization process for information systems and common controls after having satisfied two conditions: the system and/or common controls have been granted an initial authorization to operate by the designated authorizing official; and ISCM and PCM programs are in place to monitor all implemented security and privacy controls with the appropriate degree of rigor and at the appropriate frequencies in accordance with applicable ISCM and PCM strategies and OMB and NIST guidance.
2. Agencies must define and implement a process to specifically designate information systems and/or common controls that have satisfied the two conditions noted in the previous paragraph and have been transitioned to ongoing authorization. The process includes the means for the authorizing official to formally acknowledge that the information system and/or common controls are being managed under an ongoing authorization process and accept the responsibility for ensuring all necessary activities associated with the ongoing authorization process are performed. Until a formal approval is obtained from the authorizing official to transition to ongoing authorization, information systems (and common controls) remain under a static authorization process with specific authorization termination dates enforced by the agency.</p>

<h3 id="reauthorization"><strong>Reauthorization</strong></h3>

<ol>
<li>Reauthorization consists of a review of the information system similar to the review carried out during the initial authorization but conducted during the operations/maintenance phase of the system development life cycle rather than prior to that phase. In general, reauthorization actions may be time-driven or event-driven. However, under ongoing authorization, reauthorization is typically an event-driven action initiated by the authorizing official or directed by the Risk Executive (function) in response to an event that increases information security risk above the previously agreed-upon organizational risk tolerance. Event-driven reauthorization triggers can include, for example: new threat, vulnerability, or impact information; an increased number of findings, weaknesses, or deficiencies from continuous monitoring programs; new missions or business functions; new or modified security requirements; changes in authorizing officials; significant changes in risk assessment findings; significant changes to information systems, common controls, or environments of operation; exceeding agency-designated thresholds; and changes in Federal laws, OMB policies, or NIST standards and guidelines. A significant change is defined as a change that is likely to affect the security state of an information system.</li>
<li>The reauthorization process differs from the initial authorization inasmuch as the authorizing official can initiate: a complete zero-base review of the information system or common controls; or a targeted review based on the type of event that triggered the reauthorization, the assessment of risk related to the event, the risk response of the organization, and the organizational risk tolerance. Reauthorization is a separate activity from the ongoing authorization process, though security- and privacy-related information from the organization&rsquo;s ISCM and PCM programs may still be leveraged to support reauthorization. Note also that reauthorization actions may necessitate a review of and changes to the ISCM or PCM strategy, which may in turn affect ongoing authorization.</li>
</ol>

<h3 id="joint-and-leveraged-authorizations"><strong>Joint and Leveraged Authorizations</strong></h3>

<ol>
<li>Agencies are encouraged to use joint and leveraged authorizations whenever practicable.</li>
</ol>

<p>Joint authorizations can be used when multiple organizational officials either from the same organization or different organizations, have a shared interest in authorizing an information system or common controls. The participating officials are collectively responsible and accountable for the system and the common controls and jointly accept the information security risks that may adversely impact organizational operations and assets, individuals, other organizations, and the Nation. Organizations choosing a joint authorization approach should work together on the planning and the execution of the Risk Management Framework tasks described in NIST Special Publication 800-37 and document their agreement and progress in implementing the tasks. The specific terms and conditions of the joint authorization are established by the participating parties in the joint authorization including, for example, the process for ongoing determination and acceptance of risk. The joint authorization remains in effect only as long as there is mutual agreement among authorizing officials and the authorization meets the requirements established by Federal and/or organizational policies.
2. Leveraged authorizations can be used when an agency chooses to accept some or all of the information in an existing authorization package generated by another agency based on the need to use the same information resources (e.g., information system and/or services provided by the system). The leveraging organization reviews the owning organization&rsquo;s authorization package as the basis for determining risk to the leveraging organization. The leveraging organization considers risk factors such as the time elapsed since the authorization results were produced, differences in environments of operation (if applicable), the impact of the information to be processed, stored, or transmitted, and the overall risk tolerance of the leveraging organization. The leveraging organization may determine that additional security measures are needed and negotiate with the owning organization to provide such measures. To the extent that a leveraged authorization includes an information system that collects, processes, stores, maintains, transmits, or disseminates PII, leveraging organizations must consult their SAOP. The SAOP, may determine that additional measures are required to protect PII prior to leveraging the authorization.</p>

<h3 id="continuous-monitoring"><strong>Continuous Monitoring</strong></h3>

<ol>
<li>Agencies must develop ISCM and PCM and implement ISCM and PCM activities in accordance with applicable laws, directives, policies, instructions, regulations, standards, and guidelines. Agencies have the flexibility to develop an overarching ISCM and PCM strategy (e.g., at the agency, bureau, or component level) that address all information systems, or continuous monitoring strategies that address each agency information system individually. The ISCM and PCM strategies must address all security and privacy controls selected and implemented by agencies, including the frequency of and degree of rigor associated with the monitoring process. ISCM and PCM strategies, which must be approved by the SAOP and appropriate agency authorizing official, must also include all common controls inherited by organizational information systems.</li>
</ol>

<h3 id="critical-infrastructure"><strong>Critical Infrastructure</strong></h3>

<ol>
<li>Agencies that operate information systems that are part of the critical infrastructure must employ organizational assessment and management of risk to ensure that security controls for those systems are appropriately tailored (including the deployment of additional controls, when necessary), thus providing the required level of protection for critical Federal missions and business operations. In addition, organizations must ensure that the privacy controls assigned to critical infrastructure meet all applicable requirements and adequately protect individual privacy. This includes the ongoing monitoring of deployed security and privacy controls in critical infrastructure systems to determine the ongoing effectiveness of those controls against current threats; improving the effectiveness of those controls, when necessary; managing associated changes to the systems and environments of operation; and satisfying specific protection and compliance requirements in statutes, Executive Orders, directives, and policies required for critical infrastructure protection.</li>
</ol>

<h3 id="encryption"><strong>Encryption</strong></h3>

<ol>
<li>When the assessed risk indicates the need, agencies must encrypt Federal information at rest and in transitunless otherwise protected by alternative physical and logical safeguards implemented at multiple layers, including network, systems, and applications and data. Encrypting information at rest and in transit helps to protect the confidentiality, integrity, and availability of such information by making it less susceptible to unauthorized disclosure or modification. Agencies must apply encryption requirements to Federal information categorized as either moderate or high impact in accordance with FIPS Publication 199 unless encrypting such information is technically unfeasible or would demonstrably affect their ability to carry out their respective mission, functions, or operations. In situations where the use of encryption is technically infeasible, for example, due to an aging legacy system, agencies must initiate the appropriate system or system component upgrade or replacement actions at the earliest opportunity to be able to accommodate such safeguarding technologies. Authorizing officials who choose to operate information systems without the use of required encryption technologies must carefully assess the risk in doing so and they must receive approval for the exception from the agency CIO. For high impact information, access to unencrypted content should be managed separately from access to the networks, systems, and applications where the encrypted data resides. Only FIPS-validated and NSA-approved cryptography are approved for use in Federal information systems.</li>
</ol>

<h3 id="digital-signatures"><strong>Digital Signatures</strong></h3>

<ol>
<li>Digital signatures can mitigate a variety of security vulnerabilities by providing authentication and non-repudiation capabilities, and ensuring the integrity of Federal information whether such information is used in day-to-day operations or archived for future use. Additionally, digital signatures can help agencies streamline mission/business processes and transition manual processes to more automated processes to include, for example, online transactions. Because of the advantages provided by this technology, OMB expects agencies to implement digital signature capabilities in accordance with Federal Public Key Infrastructure (PKI) policy, and NIST standards and guidelines. For employees and contractors, agencies must require the use of the digital signature capability of Personal Identity Verification (PIV) credentials when the capability is available.</li>
</ol>

<p>For individuals that fall outside the scope of PIV applicability, agencies should leverage approved Federal PKI credentials when using digital signatures.</p>

<h3 id="identity-assurance"><strong>Identity Assurance</strong></h3>

<ol>
<li>To streamline the process of citizens, businesses, and other partners</li>
</ol>

<p>securely accessing government services online requires a risk-appropriate demand of identity assurance. Identity assurance, in an online context, is the ability of an agency to determine that a claim to a particular identity made by an individual can be trusted to actually be the individual&rsquo;s &ldquo;true&rdquo; identity. Citizens, businesses, and other partners that interact with the Federal Government need to have and be able to present electronic identity credentials to identify and authenticate themselves remotely and securely when accessing Federal information resources. An agency needs to be able to know, to a degree of certainty commensurate with the risk determination, that the presented electronic identity credential truly represents the individual presenting the credential before a transaction is authorized.</p>

<p>To transform processes for citizens, businesses, and other partners accessing Federal services online, OMB expects agencies to use a standards-based federated identity management approach that enables security, privacy, ease-of-use, and interoperability among electronic authentication systems.</p>

<h3 id="unsupported-information-system-components"><strong>Unsupported Information System Components</strong></h3>

<ol>
<li>Unsupported information system components (e.g., when vendors are no longer providing critical software patches) provide a substantial opportunity for adversaries to exploit weaknesses discovered in the currently installed components. Prohibit the use of unsupported information systems and system components, and ensure that systems and components that cannot be appropriately protected or secured are given a high priority for upgrade or replacement. Exceptions to replacing unsupported system components may include, for example, systems that provide critical mission/business capability where newer technologies are not available or where the systems are so isolated that installing replacement components is not an option. For such systems, organizations can establish in-house support, for example, by developing customized patches for critical software components or securing the services of external providers who through contractual relationships, provide ongoing support for the designated unsupported components. Such contractual relationships can include, for example, Open Source Software value-added vendors.</li>
</ol>

<h3 id="fisma-applicability-to-non-federal-entities"><strong>FISMA Applicability to Non-Federal Entities</strong></h3>

<ol>
<li>FISMA describes Federal agency security responsibilities as including &ldquo;information collected or maintained by or on behalf of an agency&rdquo; and &ldquo;information systems used or operated by an agency or by a contractor of an agency or other organization on behalf of an agency.&rdquo; FISMA requires each agency to provide information security for the information and &ldquo;information systems that support the operations and assets of the agency, including those provided or managed by another agency, contractor, or other source.&rdquo; This includes services that are either fully or partially provided, including agency hosted, outsourced, and cloud-based solutions.</li>
<li>Additionally, because FISMA applies to Federal information and information systems, in certain circumstances, its requirements also apply to a specific class of information technology that the Clinger-Cohen Act of 1996 (40 U.S.C. § 1401(3)) did not include, i.e., &ldquo;equipment that is acquired by a Federal contractor incidental to a Federal contract.&rdquo; Therefore, when Federal information is used within incidentally acquired equipment, the agency continues to be responsible and accountable for ensuring that FISMA requirements are met for such information.</li>
</ol>

<h3 id="other-requirements"><strong>Other Requirements</strong></h3>

<ol>
<li>Agencies must adhere to all other applicable information requirements such as the privacy requirements in accordance with the Privacy Act of 1974 and OMB guidance, the Confidential Information Protection and Statistical Efficiency Act of 2002 and OMB implementation guidance, and to laws and regulations pertaining to management of Federal records, and other relevant statutes, Executive Orders, Presidential Directives, and policies.</li>
</ol>

<h3 id="authorities-and-references"><strong>Authorities and References</strong></h3>

<ol>
<li>Privacy Act of 1974 (5 U.S.C. § 552a), December 1974.</li>
<li>E-Government Act of 2002 (44 U.S.C.§ 101), December 2002.</li>
<li>Federal Information Security Modernization Act of 2014 (44 U.S.C. chapter 35), December 2014.</li>
<li>Intelligence Reform and Terrorism Prevention Act of 2004 (50 U.S.C. § 401 note), December 2004.</li>
<li>Executive Order 13556, <em>Controlled Unclassified Information</em>, November 2010.</li>
<li>Executive Order 13636, <em>Improving Critical Infrastructure Cybersecurity</em>, February 2013.</li>
<li>Executive Order 13681, <em>Improving the Security of Consumer Financial Transactions</em>, October 2014.</li>
<li>Homeland Security Presidential Directive 20 (National Security Presidential Directive 51), National Continuity Policy, May 2007.</li>
<li>Federal Continuity Directive 1 (FCD 1), Federal Executive Branch National Continuity Program and Requirements, February 2008.</li>
<li>National Communications System (NCS) Directive 3-10, Minimum Requirements for Continuity Communications Capabilities, July 2007.</li>
<li>National Institute of Standards and Technology Federal Information Processing Standards Publication 199 (as amended), <em>Standards for Security Categorization of Federal Information and Information Systems</em>.</li>
<li>National Institute of Standards and Technology Federal Information Processing Standards Publication 200 (as amended), <em>Minimum</em> <em>Security Requirements for Federal Information and Information Systems</em>.</li>
<li>National Institute of Standards and Technology Federal Information Processing Standards Publication 201 (as amended), <em>Personal Identity Verification of Federal Employees and Contractors</em>.</li>
<li>Committee on National Security Systems Instruction 1253 (as amended), <em>Security Categorization and Control Selection for National Security Systems</em>.</li>
<li>National Institute of Standards and Technology Special Publication 800-18 (as amended), <em>Guide for Developing Security Plans for Federal Information Systems</em>.</li>
<li>National Institute of Standards and Technology Special Publication 800-30 (as amended), <em>Guide for Conducting</em> <em>Risk Assessments</em>.</li>
<li>National Institute of Standards and Technology Special Publication 800-37 (as amended), <em>Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach</em>.</li>
<li>National Institute of Standards and Technology Special Publication 800-39 (as amended), <em>Managing Information Security Risk: Organization, Mission, and Information System View</em>.</li>
<li>National Institute of Standards and Technology Special Publication 800-47 (as amended), <em>Security Guide for Interconnecting Information Technology Systems.</em></li>
<li>National Institute of Standards and Technology Special Publication 800-53 (as amended), <em>Security and Privacy Controls for Federal Information Systems and Organizations</em>.</li>
<li>National Institute of Standards and Technology Special Publication 800-53A (as amended), <em>Guide for Assessing the Security Controls in Federal Information Systems and Organizations: Building Effective Security Assessment Plans</em>.</li>
<li>National Institute of Standards and Technology Special Publication 800-59 (as amended), <em>Guideline for Identifying an Information System as a National Security System</em>.</li>
<li>National Institute of Standards and Technology Special Publication 800-60 (as amended), <em>Guide for Mapping Types of Information and Information Systems to Security Categories</em>.</li>
<li>National Institute of Standards and Technology Special Publication 800-63 (as amended), <em>Electronic Authentication Guideline</em>.</li>
<li>National Institute of Standards and Technology Special Publication 800-122, <em>Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)</em></li>
<li>National Institute of Standards and Technology Special Publication 800-137 (as amended), <em>Information Security Continuous Monitoring for Federal Information Systems and Organizations</em>.</li>
<li>National Institute of Standards and Technology Special Publication 800-160 (as amended), <em>Systems Security Engineering: An Integrated Approach to Building Trustworthy Resilient Systems</em>.</li>
<li>National Institute of Standards and Technology Special Publication 800-161 (as amended), <em>Supply Chain Risk Management Practices for Federal Information Systems and Organizations</em>.</li>
<li>National Institute of Standards and Technology Special Publication 800-162 (as amended), <em>Guide to Attribute Based Access Control (ABAC) Definition and Considerations</em>.</li>
<li>National Institute of Standards and Technology <em>Framework for Improving Critical Infrastructure Cybersecurity</em> (as amended).</li>
<li>National Institute of Standards and Technology <em>Supplemental Guidance on Ongoing Authorization: Transitioning to Near Real-Time Risk Management</em> (as amended).</li>
</ol>

<h3 id="definitions"><strong>Definitions</strong></h3>

<ol>
<li>The terms &lsquo;Federal information,&rsquo; &lsquo;Federal information system,&rsquo; &lsquo;information security,&rsquo; &lsquo;personally identifiable information,&rsquo; and &lsquo;senior agency official for privacy&rsquo; are defined in the main body of this Circular.</li>
<li>&lsquo;Adequate security&rsquo; means security protections commensurate with the risk resulting from the unauthorized access, use, disclosure, disruption, modification, or destruction of information. This includes ensuring that information hosted on behalf of an agency and information systems and applications used by the agency operate effectively and provide appropriate confidentiality, integrity, and availability protections through the application of cost-effective security controls.</li>
<li>&lsquo;Authorization&rsquo; means the official management decision given by a senior Federal official or officials 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 and privacy controls. Authorization also applies to common controls inherited by organizational information systems.</li>
<li>&lsquo;Authorization boundary&rsquo; means 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.</li>
<li>&lsquo;Authorization official&rsquo; means 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 a designated set of common controls at an acceptable level of risk to organizational operations (including mission, functions, image, or reputation), organizational assets, individuals, other organizations, and the Nation.</li>
<li>&lsquo;Authorization package&rsquo; means the essential information that an authorizing official uses to determine whether or not to authorize the operation of an information system or the use of a designated set of common controls. At a minimum, the authorization package includes the security plan, privacy plan, security control assessment, privacy control assessment, and any relevant plans of action and milestones.</li>
<li>&lsquo;Breach&rsquo; means the loss of control, compromise, unauthorized disclosure, unauthorized acquisition, unauthorized access, or any similar term referring to situations where persons other than authorized users and for an other than authorized purpose have access or potential access to personally identifiable information, whether physical or electronic.</li>
<li>&lsquo;Common control&rsquo; means a security or privacy control that is inherited by multiple information systems.</li>
<li>&lsquo;Controlled unclassified information&rsquo; means information that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and government-wide policies, excluding information that is classified under Executive Order 13526, Classified National Security Information, December 29, 2009, or any predecessor or successor order, or the Atomic Energy Act of 1954, as amended.</li>
<li>&lsquo;Critical infrastructure&rsquo; means systems and assets, whether physical or virtual, so vital to the United States that the incapacity or destruction of such systems and assets would have a debilitating impact on security, national economic security, national public health safety, or any combination of those matters (42 U.S.C. § 5195c(e)).</li>
<li>&lsquo;Environment of operation&rsquo; means the physical, technical, and organizational setting in which an information system operates.</li>
<li>&lsquo;Hybrid control&rsquo; means a control that is implemented in an information system in part as a common control and in part as a system-specific control.</li>
<li>&lsquo;Information security architecture&rsquo; means an embedded, integral part of the enterprise architecture that describes the structure and behavior of the enterprise security processes, information security systems, personnel, and organizational subunits, showing their alignment with the enterprise&rsquo;s mission and strategic plans.</li>
<li>&lsquo;Information security continuous monitoring&rsquo; means maintaining ongoing awareness of information security, vulnerabilities, and threats to support organizational risk management decisions.</li>
<li>&lsquo;Information security program plan&rsquo; means a formal document that provides an overview of the security requirements for an organization-wide information security program and describes the program management controls and common controls in place or planned for meeting those requirements. The information security program plan and the privacy program plan may be integrated into one consolidated document.</li>
<li>&lsquo;Information system resilience&rsquo; means the ability of an information system: to operate under adverse conditions or stress, even if in a degraded or debilitated state, while maintaining essential operational capabilities; and to recover to an effective operational posture in a time frame consistent with mission needs.</li>
<li>&lsquo;Initial authorization&rsquo; means the initial (start-up) risk determination and risk acceptance decision based on a zero-base review of the information system conducted prior to its entering the operations/maintenance phase of the system development life cycle. The zero-base review includes an assessment of all security and privacy controls (i.e., system-specific, hybrid, and common controls) contained in a security plan or in a privacy plan and implemented within an information system or the environment in which the system operates.</li>
<li>&lsquo;National security system&rsquo; means any information 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: 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 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 (44 U.S.C. § 3552).</li>
<li>&lsquo;Ongoing authorization&rsquo; means the risk determinations and risk acceptance decisions subsequent to the initial authorization, taken at agreed-upon and documented frequencies in accordance with the organization&rsquo;s mission/business requirements and organizational risk tolerance. Ongoing authorization is a time-driven or event-driven authorization process whereby the authorizing official is provided with the necessary and sufficient information regarding the security and privacy state of the information system to determine whether or not the mission/business risk of continued system operation is acceptable.</li>
<li>&lsquo;Overlay&rsquo; means a specification of security and/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 &ldquo;tailoring&rdquo; definition.)</li>
<li>&lsquo;Privacy continuous monitoring&rsquo; means maintaining ongoing awareness of privacy risks and assessing privacy controls at a frequency sufficient to ensure compliance with applicable requirements and to adequately protect personally identifiable information.</li>
<li>&lsquo;Privacy control&rsquo; means the administrative, technical, and physical safeguards employed within organizations to protect and ensure the proper handling of personally identifiable information or prevent activities that create privacy risk.</li>
<li>&lsquo;Privacy control assessment&rsquo; means the testing or evaluation of privacy controls to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting the privacy requirements for an information system or organization.</li>
<li>&lsquo;Privacy program plan&rsquo; means a formal document that provides an overview of the privacy requirements for an organization-wide privacy program and describes the program management controls and common controls in place or planned for meeting those requirements. The privacy program plan and the information security program plan may be integrated into one consolidated document.</li>
<li>&lsquo;Privacy plan&rsquo; means a formal document that provides an overview of the privacy requirements for an information system or program and describes the privacy controls in place or planned for meeting those requirements. The privacy plan and the security plan may be integrated into one consolidated document.</li>
<li>&lsquo;Reauthorization&rsquo; means the risk determination and risk acceptance decision that occurs after an initial authorization. In general, reauthorization actions may be time-driven or event-driven; however, under ongoing authorization, reauthorization is typically an event-driven action initiated by the authorizing official or directed by the Risk Executive (function) in response to an event that drives information security or privacy risk above the previously agreed-upon organizational risk tolerance.</li>
<li>&lsquo;Resilience&rsquo; means the ability to prepare for and adapt to changing conditions and withstand and recover rapidly from disruption. Resilience includes the ability to withstand and recover from deliberate attacks, accidents, or naturally occurring threats or incidents.</li>
<li>&lsquo;Risk&rsquo; means 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.</li>
<li>&lsquo;Risk management&rsquo; means the program and supporting processes to manage information security and privacy risk to organizational operations (including mission, functions, image, reputation), organizational 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.</li>
<li>&lsquo;Risk response&rsquo; means accepting, avoiding, mitigating, sharing, or transferring risk to organizational operations, organizational assets, individuals, other organizations, or the Nation.</li>
<li>&lsquo;Security category&rsquo; means 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 organizational operations, organizational assets, individuals, other organizations, and the Nation.</li>
<li>&lsquo;Security control&rsquo; means 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.</li>
<li>&lsquo;Security control assessment&rsquo; means the testing or evaluation of security controls 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 an information system or organization.</li>
<li>&lsquo;Security control baseline&rsquo; means the set of minimum security controls defined for a low-impact, moderate-impact, or high-impact information system.</li>
<li>&lsquo;Security plan&rsquo; means a 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 security plan and the privacy plan may be integrated into one consolidated document.</li>
<li>&lsquo;Supply chain&rsquo; means a linked set of resources and processes between multiple tiers of developers that begins with the sourcing of products and services and extends through the design, development, manufacturing, processing, handling, and delivery of products and services to the acquirer.</li>
<li>&lsquo;Supply chain risk management&rsquo; means the process of identifying, assessing, and mitigating the risks associated with the global and distributed nature of information and communications technology product and service supply chains.</li>
<li>&lsquo;System-specific control&rsquo; means a control for an information system that has not been designated as a common control or the portion of a hybrid control that is to be implemented within an information system.</li>
<li>&lsquo;Systems security engineering&rsquo; means a specialty engineering discipline of systems engineering. It applies scientific, mathematical, engineering, and measurement concepts, principles, and methods to deliver, consistent with defined constraints and necessary trade-offs, a trustworthy asset protection capability that: satisfies stakeholder requirements; is seamlessly integrated into the delivered system; and presents residual risk that is deemed acceptable and manageable to stakeholders.</li>
<li>&lsquo;Tailoring&rsquo; means the process by which security control baselines are modified by identifying and designating common controls; applying scoping considerations; 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. The tailoring process may also be applied to privacy controls. (See &ldquo;overlay&rdquo; definition.)</li>
<li>&lsquo;Trustworthiness&rsquo; means the degree to which an information system can be expected to preserve the confidentiality, integrity, and availability of the information being processed, stored, or transmitted by the system across a full range of threats.</li>
<li>&lsquo;Trustworthy information system&rsquo; means a system that is believed to be capable of operating within defined levels of risk despite the environmental disruptions, human errors, structural failures, and purposeful attacks that are expected to occur in its environment of operation.</li>
</ol>


    </article>

  </div>
</div>

<!-- <script>
  (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
  (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
  m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
  })(window,document,'script','https://www.google-analytics.com/analytics.js','ga');

  ga('create', 'UA-48605964-20', 'auto');

  // anonymize user IPs (chops off the last IP triplet)
  ga('set', 'anonymizeIp', true);

  // forces SSL even if the page were somehow loaded over http://
  ga('set', 'forceSSL', true);

  ga('send', 'pageview');
</script>
<!-- Digital Analytics Program roll-up, see https://analytics.usa.gov for data
<script async id="_fed_an_ua_tag" src="/assets/js/Universal-Federated-Analytics-Min.js?agency=GSA"></script> --> -->


</body>
</html>