text stringlengths 51 3.17k | embedding listlengths 1.54k 1.54k | example_idx int64 0 994 |
|---|---|---|
According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:
NIST SP 800-172, Enhanced Security Requirements for Protecting Controlled Unclassified Information provides enhanced security requirements to help protect CUI associated with critical programs or high value assets in nonfederal systems and organizations from the advanced persistent threat (APT). The SP 800-172 enhanced security requirements are designed to protect confidentiality, integrity and availability of information.
| Access Control | Maintenance | Security Assessment and Monitoring |
|-----------------------------------|---------------------|--------------------------------------|
| Awareness and Training | Media Protection | System and Communications Protection |
| Audit and Accountability | Personnel Security | System and Information Integrity |
| Configuration Management | Physical Protection | Planning |
| Identification and Authentication | Risk Assessment | System and Services Acquisition |
| Incident Response | | Supply Chain Risk Management |
- An understanding of the need for security (why is cybersecurity important to our business mission?).
- Specific actions required of users to maintain security (required use of multi-factor authentication, not sharing passwords, etc.).
- How to respond to confirmed or suspected incidents.
- How to securely handle CUI (training should be provided to staff before authorizing access to the system or CUI).
- How to recognize and report insider threats, social engineering, and social mining. | [
-0.027711315,
0.021571606,
0.060914047,
0.027075734,
0.038516186,
-0.007379091,
0.0059903474,
0.040473774,
-0.0056534894,
0.02641473,
0.046397384,
0.0041503413,
-0.016575942,
-0.013016691,
0.029973982,
-0.02405037,
-0.011662904,
0.021724146,
-0.035058625,
0.011770953,
0.04627... | 0 |
According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:
| Table 1. Security Requirement Families .......................................................................................................4 |
|----------------------------------------------------------------------------------------------------------------------------------------------------------|
| Table 2. Security Control Tailoring Criteria.................................................................................................93 |
| Table 3. Access Control (AC) .......................................................................................................................93 |
| Table 4. Awareness and Training (AT).........................................................................................................94 |
| Table 5. Audit and Accountability (AU).......................................................................................................95 |
| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |
| Table 7. Configuration Management (CM).................................................................................................96 |
| Table 8. Contingency Planning (CP) ............................................................................................................96 |
| Table 9. Identification and Authentication (IA) ..........................................................................................97 |
| Table 10. Incident Response (IR).................................................................................................................98 |
| Table 11. Maintenance (MA) ......................................................................................................................98 |
| Table 12. | [
-0.00629847,
0.05169411,
0.06691708,
-0.010437464,
0.0360979,
0.017622385,
-0.007844761,
-0.0008131358,
-0.022927763,
0.024287434,
0.03500483,
-0.019875173,
0.026007015,
0.025327181,
0.014823066,
-0.056892846,
0.046921935,
0.024727326,
-0.020368386,
0.034258343,
0.02940619,
... | 1 |
## Summary of NIST SP 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations
Kelley Dempsey Computer Security Division Information Technology Laboratory
Greg Witte Doug Rike G2, Inc. Annapolis Junction, MD
February 19, 2014
<!-- image -->
## Abstract
This white paper provides an overview of NIST Special Publication (SP) 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations , which was published April 30, 2013. ## Keywords
assurance; computer security; FIPS Publication 199; FIPS Publication 200, FISMA; Privacy Act; Risk Management Framework; security controls; security requirements
## Disclaimer
Any mention of commercial products or reference to commercial organizations is for information only; it does not imply recommendation or endorsement by NIST, nor does it imply that the products mentioned are necessarily the best available for the purpose. ## Additional Information
For additional information on NIST's Computer Security Division programs, projects and publications, visit the Computer Security Resource Center, csrc.nist.gov. Information on other efforts at NIST and in the Information Technology Laboratory (ITL) is available at www.nist.gov and www.nist.gov/itl. | [
0.0025568528,
-0.0031894115,
0.030262616,
0.017924586,
-0.011273325,
-0.02269696,
-0.0050949166,
0.0127012795,
-0.0067076283,
-0.009876685,
0.018550882,
-0.015807707,
-0.024826366,
-0.015181411,
0.021281533,
-0.0037922212,
0.019001815,
0.013214842,
0.00548322,
0.051030584,
-0... | 2 |
According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:
The NIST Risk Management Framework (RMF), described in NIST Special Publication 800-37 Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems: a Security Life Cycle Approach, is a methodology for implementing risk management at the information systems tier. The RMF (depicted in Figure 2) identifies six distinct steps that provide a disciplined and structured process to integrate information security risk management activities into the system development life cycle. The RMF addresses security concerns of organizations related to the design, development, implementation, operation, and disposal of information systems and the environments in which those systems operate. | [
-0.018804658,
0.044273976,
0.04562037,
0.0071751666,
0.0104962755,
-0.010081137,
0.026546434,
0.03287449,
-0.017671442,
0.054394383,
-0.009918448,
0.014484973,
-0.015775269,
0.01864758,
0.037115637,
-0.032133974,
0.00605878,
0.008869381,
-0.0018470865,
0.03689124,
0.032986693... | 3 |
team oversees incident response, allocates funding, and may have decision-making authority on high-impact response actions, such as shutting down or rebuilding critical services. - Incident handlers.
Incident handlers verify that an incident has occurred, collect and analyze data and evidence, prioritize incident response activities, and act appropriately to limit damage, find root causes, and restore operations. Incident handlers also often provide input to others on mitigating cybersecurity issues and improving resiliency. An organization's incident handlers might be:
- o On staff (e.g., an incident response team),
- o On contract (e.g., outsourcing a security operations center [SOC] to a managed security services provider [MSSP] or leveraging a cloud service provider's incident response team when an incident occurs within that provider's cloud), and/or
- o Available when needed (e.g., from a parent organization, a cybersecurity services provider, a business partner, or a law enforcement agency). Many organizations may use more than one of these approaches, such as internally performing basic incident response and engaging third-party resources for assistance with certain incidents. Larger organizations may have multiple incident response teams, with each team responsible for a particular logical or physical segment of the organization. When this model is employed, the teams should be part of a single coordinated entity (e.g., a federation) to ensure that incident response processes, procedures, and training are consistent across the organization and that information is shared among teams. - Technology professionals. Cybersecurity, privacy, system, network, cloud, and other technology architects, engineers, and administrators, as well as software developers, may be involved in incident response and recovery efforts. - Legal. | [
-0.015856141,
0.0027793464,
0.06019305,
0.0034334876,
0.019449396,
-0.020679303,
-0.015217073,
0.049775023,
-0.008120997,
0.041310374,
0.06048244,
-0.015530578,
0.0104300855,
-0.011485152,
0.0034063575,
0.009652351,
-0.02442931,
-0.0064871516,
-0.054067634,
0.017073989,
0.001... | 4 |
According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:
| Access Control | Maintenance | Security Assessment and Monitoring |
|-----------------------------------|---------------------|--------------------------------------|
| Awareness and Training | Media Protection | System and Communications Protection |
| Audit and Accountability | Personnel Security | System and Information Integrity |
| Configuration Management | Physical Protection | Planning |
| Identification and Authentication | Risk Assessment | System and Services Acquisition |
| Incident Response | | Supply Chain Risk Management |
## Family: Access Control
## Getting Started with Access Control | [
0.0024122677,
0.039233364,
0.06147799,
0.006042283,
0.029624108,
0.0016134322,
-0.019112328,
0.02795178,
-0.010989589,
-0.0002886758,
0.033924382,
-0.0013703805,
-0.004452907,
0.021050107,
0.01056487,
-0.03846356,
-0.016856011,
0.01868761,
-0.008998721,
0.05038222,
0.04448925... | 5 |
itado que los titulares de registros de patentes cuyo uso pueda ser necesario para el cumplimiento de las orientaciones o requisitos de esta publicación comuniquen dichos registros de patentes al ITL.
Sin embargo, los titulares de patentes no están obligados a responder a las solicitudes de patentes del ITL y el ITL no ha realizado una búsqueda de patentes para identificar cuáles, si las hubiera, pueden aplicarse a esta publicación. Tras la convocatoria del ITL para la identificación de reclamaciones de patentes cuyo uso pueda ser necesario para el cumplimiento de las orientaciones o requisitos de esta publicación, se ha recibido notificaciones de una o más de dichas reclamaciones. Mediante la publicación, el ITL no adopta posición alguna con respecto a la validez o el alcance de cualquier reivindicación de patente o de cualquier derecho relacionado con ella. No obstante, el o los titulares conocidos de patentes han facilitado a NIST una carta de garantía en la que declaran o bien (1) una renuncia general en el sentido de que no poseen y no tienen actualmente la intención de poseer ninguna reivindicación esencial de patente, o bien (2) que negociarán licencias libres de cánones o que devenguen cánones con otras partes sobre una base no discriminatoria demostrable con términos y condiciones razonables. Para más detalles se puede consultar en zerotrust-arch@nist.gov . No se declara ni se da a entender que esta sea la única licencia necesaria para evitar la infracción de patentes en el uso de esta publicación. | [
0.032497592,
0.046622686,
0.025064632,
-0.021595094,
-0.00792067,
-0.013779374,
-0.05748814,
0.010396266,
-0.05030212,
-0.034917627,
0.05146275,
0.010050547,
-0.005701278,
-0.010599993,
-0.0040097237,
0.03575723,
0.014384382,
-0.052302353,
-0.04190609,
0.040424436,
0.02943550... | 6 |
According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:
| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |
|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|
| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |
| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |
| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |
| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |
| 2.1 | ASSESSMENT PROCEDURES................................................................................................................ | [
0.03428543,
0.038844522,
0.05217921,
-0.014217516,
0.035945676,
0.011424084,
-0.009348775,
-0.00733276,
-0.028461387,
0.021438276,
0.03344213,
-0.0151267,
-0.0030009632,
0.028197855,
0.03136023,
-0.028224207,
0.016655182,
0.024179002,
-0.013222686,
0.018526254,
0.023889117,
... | 7 |
parameters that organizations define, providing them with the ability to tailor security controls based on specific security requirements, environments of operation, and organizational risk tolerance.
Parameters assigned and/or selected by organizations for a given base control also apply to all control enhancements associated with that control. The first security control in each family (referred to as the dash-1control) addresses policies and procedures needed for effective implementation of all the other controls within each family. Therefore, requirements to develop policies and procedures are not repeated in individual controls. Many security controls and enhancements include supplemental guidance. The supplemental guidance provides additional information about a control or enhancement to help organizations define, develop, and/or implement security controls but does not include any additional requirements. SP 800-53 Rev. 4 includes many changes from SP 800-53 Rev. 3 - 295 controls and control enhancements were added while approximately 100 controls and control enhancements were withdrawn or incorporated into others. Of the eighteen security control families in SP 800-53 Rev. 4, seventeen families are described in the security control catalog in Appendix F, and are closely aligned with the seventeen minimum security requirements for federal information and information systems in FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . One additional family, the Program Management (PM) family, provides controls for information security programs themselves. This family is described in Appendix G of SP 800-53 Rev. 4. While it is not specifically referenced in FIPS 200, the PM section provides security controls at the organization level rather than the information system level. The PM controls are typically implemented at the organization level and not directed at individual organizational information systems. | [
0.010864979,
0.0039596953,
0.061008636,
0.0008292269,
-0.0076073576,
0.0021140217,
-0.0013596825,
0.0131802615,
-0.0013050769,
0.038841832,
0.010852498,
-0.01965806,
-0.004689852,
0.02040694,
-0.009292334,
-0.022678537,
0.043260217,
0.0070956238,
-0.0022981209,
0.013417407,
0... | 8 |
...103 |
| Appendix D. Organization-Defined Parameters...............................................................................107 |
| Appendix E.
Change Log .................................................................................................................112 |
## List of Tables
| Table 1. Security Requirement Families ..............................................................................................3 |
|------------------------------------------------------------------------------------------------------------------------------------------|
| Table 2. Summary of Assessment Preparation Phase.......................................................................104 |
| Table 3. Summary of Assessment Plan Development Phase.............................................................105 |
| Table 4. Summary of Assessment Execution Phase..........................................................................106 |
| Table 5. Summary of Assessment Analysis, Documentation, and Reporting Phase ...........................106 |
| Table 6. Organization-Defined Parameters......................................................................................107 |
Table 7. Change Log ....................................................................................................................... 113
## Acknowledgments
The authors gratefully acknowledge and appreciate the significant contributions from individuals and organizations in the public and private sectors whose constructive comments improved the overall quality, thoroughness, and usefulness of this publication. | [
0.02891047,
0.033823695,
0.06413056,
-0.0065940693,
-0.0015046761,
-0.010990116,
-0.0020105448,
0.0024873216,
-0.010472934,
0.0038950262,
0.027384782,
-0.035013214,
0.012496408,
-0.016317088,
0.05694173,
0.04344328,
0.059579354,
0.023001665,
0.023105102,
0.035245948,
0.040805... | 9 |
..................................................... 50 | APPENDIX C MAPPINGTABLES ....................................................................................................
50 |
| APPENDIXD ADVERSARY EFFECTS............................................................................................... 68 | APPENDIXD ADVERSARY EFFECTS............................................................................................... 68 |
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
## Errata
This table contains changes that have been incorporated into Special Publication 800-172. Errata updates can include corrections, clarifications, or other minor changes in the publication that are either editorial or substantive in nature. Any potential updates for this document that are not yet published in an errata update or revision-including additional issues and potential corrections-will be posted as they are identified; see the SP 800-172 publication details. | DATE | TYPE | CHANGE | PAGE |
|--------|--------|----------|--------|
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
## CHAPTER ONE
## INTRODUCTION
THE NEED TO PROTECT CONTROLLED UNCLASSIFIED INFORMATION
oday, more than at any time in history, the Federal Government relies on external service providers to help carry out a wide range of federal missions and business functions using information systems. | [
-0.005506949,
0.020429783,
0.08193955,
0.012198633,
0.020526215,
0.021545637,
0.013541792,
0.0005346803,
-0.028323421,
0.029480603,
0.037222706,
-0.0259264,
0.0137346545,
0.0099255955,
0.039895248,
-0.007356375,
0.026601423,
0.01114477,
0.015084702,
0.014134158,
0.0051522176,... | 10 |
According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:
............................................ 5 |
| 2.1 DEVELOPMENTAPPROACH ......................................................................................................
| 5 |
| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |
| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |
| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |
| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |
| 3.2 AWARENESSANDTRAINING | ................................................................................................... | [
0.017687652,
0.02863843,
0.05150623,
-0.015889363,
0.06081976,
0.006411439,
-0.010736057,
0.015379401,
-0.041172776,
0.016801927,
0.024437947,
-0.0016137635,
0.008192953,
0.03070512,
0.014775498,
-0.017942633,
0.04538668,
0.004952006,
-0.033093892,
0.03231553,
0.038112998,
... | 11 |
| help you take |
1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui.
ht ps:/
csrc.nist.gov/projects/protecting-control ed-unclas ified-information
## Overview
## Audience
<!-- image -->
<!-- image -->
Pages 2-6 provide a general overview of SP 800-171, R3 -helpful to business leaders or those new to SP 800-171. Pages 7-27 are for those who are tasked with managing the implementation SP 800-171. It is not all-encompassing, but it does provide tips and resources to help with getting started. This section serves as a bridge to the larger SP 800-171 publication. ## Key Term: Confidentiality
<!-- image -->
Confidentiality refers to the protection of information from unauthorized access and disclosure . *Definitions in this document are intended as plain language. View the official definition within 32 CFR Part 2002 "Controlled Unclassified Information."
## A Suite of Guidance
NIST's suite of CUI guidance (shown in the table below) focuses on protecting the confidentiality 2 of CUI in nonfederal systems and organizations and recommends specific security requirements to achieve that objective. This guide will focus on SP 800-171, Revision 3 . <!-- image -->
<!-- image -->
<!-- image -->
NIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Systems is a set of recommended security requirements for protecting the confidentiality of CUI. NIST SP 800-171A, Assessing Security Requirements for Controlled Unclassified Information provides assessment procedures and a methodology to conduct assessments of the CUI security requirements in SP 800-171. | [
-0.034264933,
0.00019542543,
0.053950164,
-0.0049048592,
0.008789929,
-0.0051581617,
0.004464047,
0.0025905948,
-0.0010189672,
0.033238564,
0.015132363,
0.02329068,
-0.01497446,
0.0026136222,
0.0005781549,
-0.021566907,
0.002118531,
0.018816764,
-0.003013314,
0.027633011,
0.0... | 12 |
| ........................................................................................................
22 |
| 3.13 SYSTEMANDCOMMUNICATIONSPROTECTION ..................................................................... | 23 |
| 3.14 SYSTEMANDINFORMATIONINTEGRITY ................................................................................ | 27 |
| REFERENCES .................................................................................................................................. 32 | REFERENCES .................................................................................................................................. 32 |
| APPENDIXA GLOSSARY................................................................................................................ 38 | APPENDIXA GLOSSARY................................................................................................................ 38 |
| APPENDIX B ACRONYMS.............................................................................................................. 48 | APPENDIX B ACRONYMS.............................................................................................................. 48 |
| APPENDIX C MAPPINGTABLES .................................................................................................... 50 | APPENDIX C MAPPINGTABLES .................................................................................................... | [
0.018712983,
0.018425753,
0.046157733,
-0.017851295,
-0.018009271,
0.011273746,
0.01239394,
-0.022432601,
-0.02302142,
-0.008609695,
0.008286563,
-0.006275958,
0.009485744,
-0.0148066655,
0.030072898,
-0.00017985485,
0.021700166,
0.033404756,
-0.008810756,
0.045611996,
0.0144... | 13 |
According to Security and Privacy Controls for Information Systems and Organizations:
In working with the Office of Management and Budget to develop standards and guidelines
required by FISMA, NIST consults with federal agencies, state, local, and tribal governments, and
private sector organizations to improve information security and privacy, avoid unnecessary and
costly duplication of effort, and help ensure that its publications are complementary with the
standards and guidelines used for the protection of national security systems. In addition to a
comprehensive and transparent public review and comment process, NIST is engaged in a
collaborative partnership with the Office of Management and Budget, Office of the Director of
National Intelligence, Department of Defense, Committee on National Security Systems, Federal
CIO Council, and Federal Privacy Council to establish a Risk Management Framework (RMF) for
information security and privacy for the Federal Government. This common foundation provides
the Federal Government and their contractors with cost-effective, flexible, and consistent ways
to manage security and privacy risks to organizational operations and assets, individuals, other
organizations, and the Nation. The framework provides a basis for the reciprocal acceptance of
security and privacy control assessment evidence and authorization decisions and facilitates
information sharing and collaboration. NIST continues to work with public and private sector
entities to establish mappings and relationships between the standards and guidelines
developed by NIST and those developed by other organizations. NIST anticipates using these
mappings and the gaps they identify to improve the control catalog. CHAPTER ONE INTRODUCTION ...................................................................................................... 1
1.1 PURPOSE AND APPLICABILITY ................................................................................................... | [
0.008601245,
0.022809137,
0.06431507,
0.016281994,
0.023203636,
-0.0047070743,
-0.023179727,
-0.021087693,
-0.038278226,
0.011350773,
0.0015421272,
0.0070650945,
-0.04566609,
-0.011171456,
0.013269466,
-0.008398018,
-0.01239679,
-0.015182182,
0.018254483,
-0.010693277,
0.0488... | 14 |
According to Security and Privacy Controls for Information Systems and Organizations:
s of computing platforms, including
general purpose computing systems, cyber-physical systems, cloud systems, mobile systems,
industrial control systems, and Internet of Things (IoT) devices.
Safeguarding measures include
both security and privacy controls to protect the critical and essential operations and assets of
organizations and the privacy of individuals. The objective is to make the systems we depend on
more penetration resistant to attacks, limit the damage from those attacks when they occur,
and make the systems resilient, survivable, and protective of individuals’ privacy. | [
0.008451067,
0.004665633,
0.05978454,
0.05205259,
0.035230998,
-0.00017591409,
-0.0067309383,
0.019421922,
-0.016315334,
0.0021329022,
0.016246298,
-0.01771905,
0.012069666,
-0.028787706,
-0.022125803,
-0.031134905,
0.010694713,
0.015233782,
0.035323042,
0.0063454914,
0.03334... | 15 |
According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:
ne or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control.
- Applying scoping considerations - these, when applied in conjunction with risk management guidance, can eliminate unnecessary security controls from the initial security control baselines and help ensure that organizations select only those controls needed to provide the appropriate level of protection for information systems. When scoping considerations are applied, compensating controls may need to be selected to provide alternative means to achieve security requirements. - Supplementing baselines - additional security controls and control enhancements are selected if needed to address specific threats and vulnerabilities. | [
0.0039408454,
0.02045858,
0.08589222,
0.024529487,
0.035714723,
-0.011998119,
0.005703171,
0.0012079406,
-0.025804084,
0.015373199,
-0.005706422,
-0.0003314521,
-0.011965604,
0.028249228,
0.0031897437,
-0.070076816,
0.030824434,
-0.0056023737,
-0.011165729,
0.019678215,
0.049... | 16 |
tect audit record content. - Ask internal information security staff, or your security vendor, what audit log information, if any, the system currently captures and how it is protected and maintained.
## Questions to Ask:
- Do audit records contain information that establishes type of event, when the event occurred, where the event occurred, the source of the event, outcome, and the identity of the individual associated with the event? - Who within the business should be alerted when there are, for instance, software and hardware errors, failures in audit log capturing mechanisms, or reaching or exceeding audit log storage capacity? - Are we retaining audit records for a period consistent with the business records retention policy? Note that some industries and types of data (e.g., financial, employee, and medical records) have regulatory specifications. - How are audit information and audit logging tools being protected from unauthorized access, modification, and deletion? - Is access to management of audit logging functionality authorized to only a subset of privileged users or roles? - How frequently are these records reviewed? ## Related Resources:
- View all SP 800-171 Audit and Accountability Requirements and Assessment Procedures
- NIST Log Management resources
ht ps:/
csrc.nist.gov/projects/protecting-control ed-unclas ified-information
<!-- image -->
- Logging Made Easy, Cybersecurity and Infrastructure Security Agency (CISA)
## Getting Started with Configuration Management
## Family: Configuration Management
Description: Establishing and maintaining baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation); and establishing and enforcing security configuration settings for information technology products employed in organizational systems. | [
0.024958262,
0.03161294,
0.07475894,
-0.035474457,
-0.011964262,
0.020054137,
0.014146019,
-0.020491777,
0.00011996844,
0.009602302,
0.043454923,
-0.042708363,
0.017840203,
-0.013824225,
0.016282724,
-0.008282951,
-0.029321775,
0.029244544,
-0.0072918287,
0.014841092,
0.03277... | 17 |
According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:
Advanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |
|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |
| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |
| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |
| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | [
0.015054227,
0.009209796,
0.063402444,
0.010847521,
0.031136045,
0.0067307292,
-0.032471914,
-0.00036768537,
-0.05078875,
0.02336488,
0.03460417,
-0.01975546,
-0.028078958,
0.009569453,
0.042054214,
-0.0139881,
0.0463701,
0.021027107,
-0.0051604398,
0.017225016,
0.04218266,
... | 18 |
According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:
In addition to the responsibility to protect organizational assets from the threats that exist in today's environment, organizations have a responsibility to consider and manage the risks to individuals when information systems process personally identifiable information (PII). 6 7 The information security and privacy programs implemented by organizations have complementary objectives with respect to managing the confidentiality, integrity, and availability of PII. While many privacy risks arise from unauthorized activities that lead to the loss of confidentiality, integrity, or availability of PII, other privacy risks result from authorized activities involving the creation, collection, use, processing, storage, maintenance, dissemination, disclosure, or disposal of PII that enables an organization to meet its mission or business objectives. For example, organizations could fail to provide appropriate notice of PII processing depriving an individual of knowledge of such processing or an individual could be embarrassed or stigmatized
Executing the RMF requires close collaboration between information security programs and privacy programs. While information security programs and privacy programs have different objectives, those objectives are overlapping and complementary. Information security programs are responsible for protecting information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction (i.e., unauthorized system activity or behavior) in order to provide confidentiality, integrity, and availability. Privacy programs are responsible for ensuring compliance with applicable privacy requirements and for managing the risks to individuals associated with the creation, collection, use, processing, dissemination, storage, maintenance, disclosure, or disposal (collectively referred to as 'processing') of PII. | [
0.017954508,
0.048456103,
0.08670599,
0.032561563,
0.05777278,
-0.0039502257,
0.04531933,
0.04553001,
-0.022261716,
0.007853634,
0.023162954,
-0.017650194,
0.022905458,
0.0033152634,
-0.014361265,
-0.0511247,
0.009632698,
0.025140991,
-0.0021258066,
0.023677945,
0.021021053,
... | 19 |
According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:
| Access Control | Maintenance | Security Assessment and Monitoring |
|-----------------------------------|---------------------|--------------------------------------|
| Awareness and Training | Media Protection | System and Communications Protection |
| Audit and Accountability | Personnel Security | System and Information Integrity |
| Configuration Management | Physical Protection | Planning |
| Identification and Authentication | Risk Assessment | System and Services Acquisition |
| Incident Response | | Supply Chain Risk Management |
## Updates to the Security Requirements and Families
- It is important to identify permitted and prohibited actions regarding software installation when users have the ability to install software on organizational systems. Permitted software installations could include updates and security patches to existing software and downloading new applications from organizationapproved 'app stores.' Companies might prohibit employees from downloading certain programs, services, software versions, etc . | [
-0.0061866627,
0.031211993,
0.07013518,
-0.00091636047,
0.017900996,
-0.020104196,
0.011540568,
0.025494166,
-0.023369651,
0.023592595,
0.045952447,
-0.005429313,
-0.022071337,
0.026018737,
0.025717108,
-0.024943365,
0.0025490886,
0.010753712,
-0.029008793,
0.034306962,
0.042... | 20 |
According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:
| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |
|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|
| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |
| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |
| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |
| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |
| 2.1 | ASSESSMENT PROCEDURES................................................................................................................ | [
0.03428341,
0.038842235,
0.05220249,
-0.0142298555,
0.035969913,
0.011469527,
-0.0093350485,
-0.0073059765,
-0.028512415,
0.02147654,
0.03344016,
-0.015125809,
-0.0029941988,
0.028222546,
0.031384736,
-0.028222546,
0.016641025,
0.02417758,
-0.013248259,
0.018525163,
0.0239008... | 21 |
TS
SP 800-171A [84] provides a set of procedures to assess the security requirements described in this publication. The assessment procedures are based on the procedures described in SP 800-53A [57].
15 With few exceptions, the security controls in SP 800-53 are policy-, technology-, and sector-neutral, meaning that the controls focus on the fundamental measures necessary to protect information across the information life cycle. ## 3. The Security Requirements
This section describes 17 families of security requirements for protecting the confidentiality of CUI in nonfederal systems and organizations. When used in the context of the requirements in Sec. 3, the term system is defined to be nonfederal systems or system components that process, store, or transmit CUI or that provide protection for such systems or components. Not all security requirements mention CUI explicitly. However, the requirements are included because they directly affect the protection of CUI during processing, while in storage, and when in transmission between different locations. Some systems, including specialized systems (e.g., industrial/process control systems, medical devices, computer numerical control machines), may have limitations on the application of certain security requirements. To accommodate such issues, the system security plan - as reflected in requirement 03.15.02 - is used to describe any enduring exceptions to the security requirements. Individual, isolated, or temporary deficiencies are managed though plans of action and milestones, as reflected in requirement 03.12.02. ## SCOPE AND APPLICABILITY OF SECURITY REQUIREMENTS
The security requirements in this section are only applicable to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. ## 3.1. Access Control
## 03.01.01 Account Management
- a. Define the types of system accounts allowed and prohibited. - b. | [
-0.013670656,
0.017516352,
0.0780202,
-0.007612369,
0.014566229,
-0.02227079,
-0.0068155727,
0.012156084,
-0.0004979978,
0.019715773,
0.024470212,
-0.031002624,
0.0048532146,
0.026972547,
-0.014526718,
-0.049309187,
0.028605651,
0.020585006,
0.002250456,
0.0064270524,
0.03708... | 22 |
According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:
....................................................................................... | 63 |
| A.1.1.
C-SCRM Controls Summary........................................................................................................63 | |
| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |
| A.1.2. Selecting, Tailoring, and Implementing C-SCRM Security Controls ...........................................67 | |
| A.2.3. FAMILY: ACCESS CONTROL.........................................................................................................69 | |
| A.2.4. FAMILY: AWARENESS AND TRAINING........................................................................................76 | |
| A.2.5. FAMILY: AUDIT AND ACCOUNTABILITY......................................................................................79 | |
| A.2.6. FAMILY: ASSESSMENT, AUTHORIZATION, AND MONITORING..................................................84 | |
| A.2.7. | [
0.014118211,
0.03545788,
0.072630204,
0.009215153,
0.037561975,
-0.0034256468,
0.0051303525,
0.005104376,
-0.048887715,
0.050264467,
-0.0011892352,
-0.0234048,
0.001886541,
0.018560188,
0.023430776,
-0.029924892,
0.036367055,
0.021807246,
-0.019326493,
0.031249693,
0.06774663... | 23 |
According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:
<!-- image -->
<!-- image -->
Howard Lutnick, Secretary of Commerce
<!-- image -->
Protecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer
## Purpose of this Primer
This guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:
- An overview of foundational components of SP 800-171
- A list of frequently asked questions and their answers
- Tips for getting started
- Related resources
## What is Controlled Unclassified Information (CUI)?*
CUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI. | [
-0.029982954,
-0.012517091,
0.02689492,
0.02363533,
0.017736396,
-0.031091478,
-0.009640206,
0.03977492,
-0.014358034,
0.012748034,
0.038771972,
0.002870287,
-0.026789347,
-0.007093238,
0.011560329,
-0.0057768654,
-0.012761231,
-0.0023374695,
-0.00986455,
0.027449183,
0.03322... | 24 |
According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:
| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |
|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |
| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |
| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |
| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |
| 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | [
0.02867414,
0.007869022,
0.055200994,
-0.015305968,
0.042841,
0.0015891889,
-0.024628337,
0.011666054,
-0.052241925,
0.017374696,
0.016248679,
0.0011963925,
-0.011711881,
0.024143888,
0.024667617,
-0.014638214,
0.03294253,
0.013839528,
-0.026042404,
0.02346304,
0.02809804,
... | 25 |
| Implementación basada en enclaves....................................................................................................26 | | | 3.2.3 | Despliegue basado en un portal de recursos........................................................................................27 | | | 3.2.4 | Entorno de pruebas (sandbox) para aplicaciones en dispositivos........................................................28 | | | 3.3 | ALGORITMOS DE CONFIANZA .............................................................................................................................29 | | | 3.3.1 | Variaciones del algoritmo de confianza................................................................................................31 | | | 3.4 | COMPONENTES DE LA RED Y EL ENTORNO ............................................................................................................33 | | | 3.4.1 | Requisitos de la red para admitir una ZTA............................................................................................33 | | | ESCENARIOS DE IMPLEMENTACIÓN Y CASOS DE USO......................................................................................35 | ESCENARIOS DE IMPLEMENTACIÓN Y CASOS DE USO......................................................................................35 | | | 4.1 | E MPRESA CON INSTALACIONES SATÉLITES .............................................................................................................35 | | | 4.2 | E MPRESA MULTINUBE O NUBE A NUBE ................................................................................................................36 | | | 4.3 | E MPRESA CON SERVICIOS CONTRATADOS O ACCESO DE PERSONAL EXTERNO ................................................................37 | | | 4.4 | COLABORACIÓN MÁS ALLÁ DE LOS LÍMITES DE LA EMPRESA ......................................................................................39 | | | 4.5 | E MPRESA CON SERVICIOS ORIENTADOS AL PÚBLICO O AL CLIENTE ..............................................................................40 | | | 5 AMENAZAS ASOCIADAS A LA ARQUITECTURA DE CONFIANZA CERO..............................................................41 | 5 AMENAZAS ASOCIADAS A LA ARQUITECTURA DE CONFIANZA CERO..............................................................41 | | | 5.1 | S UBVERSIÓN DEL PROCESO DE DECISIONES DE LA ZTA............................................................................................41 | [
-0.0008761691,
0.024131345,
0.06911102,
0.007183089,
0.040234886,
-0.0029280523,
0.00712318,
0.0072729527,
-0.03520253,
0.027773812,
0.012293327,
-0.020932205,
0.01604363,
-0.025233671,
0.0014782546,
0.015863903,
0.017960718,
-0.008093706,
-0.019793933,
0.0127246715,
0.011149... | 26 |
According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:
There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The NIST Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, implementations, proofs of concept, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. The purpose of this publication is to describe procedures for assessing the enhanced security requirements in [SP 800-172]. 3 Compliance with the security requirements is addressed in CUI guidance and the CUI Federal Acquisition Regulation (FAR) or as supplemented by federal agencies (e.g., Department of Defense Federal Acquisition Regulation). Organizations can use the assessment procedures to generate evidence to support the assertion that the enhanced security requirements have been satisfied. | [
-0.011995599,
0.008788983,
0.049592193,
-0.03336438,
0.017629895,
0.016305706,
0.009652303,
0.011846303,
-0.016669208,
0.0012162746,
0.025549067,
0.0043360717,
-0.02509469,
0.012144895,
0.0031303451,
-0.029755317,
-0.004449666,
-0.007114273,
-0.02434172,
0.013423647,
0.030274... | 27 |
According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:
Advanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |
|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |
| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |
| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |
| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | [
0.015054227,
0.009209796,
0.063402444,
0.010847521,
0.031136045,
0.0067307292,
-0.032471914,
-0.00036768537,
-0.05078875,
0.02336488,
0.03460417,
-0.01975546,
-0.028078958,
0.009569453,
0.042054214,
-0.0139881,
0.0463701,
0.021027107,
-0.0051604398,
0.017225016,
0.04218266,
... | 28 |
According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:
| Access Control | Maintenance | Security Assessment and Monitoring |
|-----------------------------------|---------------------|--------------------------------------|
| Awareness and Training | Media Protection | System and Communications Protection |
| Audit and Accountability | Personnel Security | System and Information Integrity |
| Configuration Management | Physical Protection | Planning |
| Identification and Authentication | Risk Assessment | System and Services Acquisition |
| Incident Response | | Supply Chain Risk Management |
- A business champion: Someone who is responsible for developing and maintaining the incident response plan.
- Who to call: List all the individuals who may be part of the incident response efforts. Include their contact information, roles, and responsibilities.
- What/when/how to report: List the business' communications/reporting responsibilities as required by laws, regulations, contracts, agreements, or policies.
- Also, most federal contracts will include specific reporting and notification requirements that should be included in the Incident Response Plan
Description: Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of the systems; and employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems. | [
-0.023050858,
0.021448392,
0.052462276,
0.022841305,
-0.0024745774,
-0.016776588,
-0.016640995,
0.049725756,
0.005907553,
0.005926043,
0.03249308,
-0.007260404,
0.010274273,
-0.02101696,
0.039617892,
0.015580901,
-0.034563962,
0.027587071,
-0.02625579,
0.028055483,
0.03219724... | 29 |
However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication.
As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
## CAUTIONARY NOTE
The generalized assessment procedures described in this publication provide a framework and starting point for developing specific procedures to assess the enhanced security requirements in NIST Special Publication 800-172. The assessment procedures can be used to help generate and evaluate the relevant evidence needed to determine if the security safeguards employed by organizations are implemented correctly, operating as intended, and satisfy the enhanced security requirements. Organizations have the flexibility to tailor the assessment procedures by selecting the assessment methods and objects needed to achieve the assessment objectives. There is no expectation that every assessment method and object in an assessment procedure will be used for every assessment. In addition, there is significant flexibility in the scope of the assessment and the degree of rigor applied during the assessment process. The assessment procedures can support self-assessments, third-party assessments, or assessments conducted by sponsoring organizations (e.g., government agencies). Such approaches may be specified in contracts or in agreements by participating parties. | [
0.015165179,
0.028894916,
0.06262781,
-0.039820224,
-0.018620873,
-0.02647593,
-0.008439868,
-0.0026615488,
-0.014952521,
-0.001348219,
0.05013414,
-0.02046834,
-0.0018408215,
-0.005907907,
-0.0024256313,
-0.01610885,
0.013091763,
-0.014168344,
-0.040165793,
0.019165808,
0.01... | 30 |
According to Zero Trust Architecture:
3.2.4 | Entorno de pruebas (sandbox) para aplicaciones en dispositivos... 3.2.4 Entorno de pruebas ( sandbox ) para aplicaciones en dispositivos
Otra variación del modelo de despliegue de agente y puerta de enlace es hacer que las aplicaciones o procesos examinados se ejecuten en compartimentos independientes dentro de los activos. | [
0.003100072,
0.049888976,
0.071523525,
0.01339567,
0.030868804,
-0.0030386103,
0.007321447,
0.015242521,
-0.002920184,
0.030988729,
-0.020807061,
-0.0077112047,
0.019631792,
-0.01948788,
-0.010235635,
0.000120768644,
0.010319582,
0.0039275577,
-0.036121536,
0.013119841,
0.036... | 31 |
ets. By achieving the above objectives, organizations can simplify RMF execution, employ innovative approaches for managing risk, and increase the level of automation when carrying out specific tasks.
Organizations implementing the RMF will be able to:
- -Use the tasks and outputs of the Organization-Level and System-Level Prepare step to promote a consistent starting point within organizations to execute the RMF;
- -Maximize the use of common controls at the organization level to promote standardized, consistent, and cost-effective security and privacy capability inheritance;
- -Maximize the use of shared or cloud-based systems, services, and applications to reduce the number of authorizations needed across the organization;
- -Employ organizationally-tailored control baselines to increase the speed of security and privacy plan development and the consistency of security and privacy plan content;
- -Employ organization-defined controls based on security and privacy requirements generated from a systems security engineering process;
- -Maximize the use of automated tools to manage security categorization; control selection, assessment, and monitoring; and the authorization process;
- -Decrease the level of effort and resource expenditures for low-impact systems if those systems cannot adversely affect higher-impact systems through system connections;
- -Maximize the reuse of RMF artifacts (e.g., security and privacy assessment results) for standardized hardware/software deployments, including configuration settings;
- -Reduce the complexity of the IT/OT infrastructure by eliminating unnecessary systems, system components, and services - employing the least functionality principle; and
- -Make the transition to ongoing authorization a priority and use continuous monitoring approaches to reduce the cost and increase the efficiency of security and privacy programs. | [
0.026789874,
0.072729364,
0.08830374,
0.023728874,
0.0040986794,
-0.015696809,
-0.016211057,
0.049318835,
0.014105089,
0.061856695,
0.023361554,
0.00872385,
0.0077259648,
0.015709054,
0.008619777,
-0.024071706,
0.014203041,
0.020202601,
0.018231317,
0.0060883295,
0.04339274,
... | 32 |
According to Zero Trust Architecture:
3.1.1 | ZTA basada en una gobernanza de la identidad mejorada... 3.1.1 ZTA basada en una gobernanza de la identidad mejorada
Para desarrollar una ZTA, el enfoque de la gobernanza de la identidad mejorada utiliza la identidad de los actores como el componente clave de la creación de las políticas. | [
0.019888585,
0.026578588,
0.03936897,
0.034493204,
0.04898443,
-0.019128874,
-0.02039884,
0.052658264,
-0.032792356,
-0.004025341,
0.015194245,
0.012280124,
0.0064235367,
-0.045242563,
0.0055872863,
0.022621281,
-0.012586277,
-0.020319467,
-0.006559605,
0.034130353,
-0.008600... | 33 |
According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:
## NIST Special Publication 800-172
## Enhanced Security Requirements for Protecting Controlled Unclassified Information
A Supplement to NIST Special Publication 800-171
RON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART
DEB BODEAU
This publication is available free of charge from:
https://doi.org/10.6028/NIST.SP.800-172
<!-- image -->
## NIST Special Publication 800-172
## Enhanced Security Requirements for Protecting Controlled Unclassified Information
A Supplement to NIST Special Publication 800-171
## RON ROSS VICTORIA PILLITTERI
Computer Security Division
National Institute of Standards and Technology
## GARY GUISSANIE RYAN WAGNER
Institute for Defense Analyses
RICHARD GRAUBART DEB BODEAU
The MITRE Corporation
This publication is available free of charge from:
https://doi.org/10.6028/NIST.SP.800-172
## February 2021
<!-- image -->
U.S. Department of Commerce Wynn Coggins, Acting Secretary
National Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
## Authority
This publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems. | [
-0.020219872,
0.032804854,
0.042565208,
-0.029392926,
0.03722358,
-0.009180046,
-0.005243743,
0.005666738,
-0.043348275,
-0.012396208,
0.022792801,
0.005852017,
-0.028889528,
0.009215004,
0.027197545,
0.009110129,
0.006121196,
0.0017173258,
-0.013808522,
0.03442692,
-0.000581... | 34 |
| help you take |
1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui.
ht ps:/
csrc.nist.gov/projects/protecting-control ed-unclas ified-information
## Overview
## Audience
<!-- image -->
<!-- image -->
Pages 2-6 provide a general overview of SP 800-171, R3 -helpful to business leaders or those new to SP 800-171. Pages 7-27 are for those who are tasked with managing the implementation SP 800-171. It is not all-encompassing, but it does provide tips and resources to help with getting started. This section serves as a bridge to the larger SP 800-171 publication. ## Key Term: Confidentiality
<!-- image -->
Confidentiality refers to the protection of information from unauthorized access and disclosure . *Definitions in this document are intended as plain language. View the official definition within 32 CFR Part 2002 "Controlled Unclassified Information."
## A Suite of Guidance
NIST's suite of CUI guidance (shown in the table below) focuses on protecting the confidentiality 2 of CUI in nonfederal systems and organizations and recommends specific security requirements to achieve that objective. This guide will focus on SP 800-171, Revision 3 . <!-- image -->
<!-- image -->
<!-- image -->
NIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Systems is a set of recommended security requirements for protecting the confidentiality of CUI. NIST SP 800-171A, Assessing Security Requirements for Controlled Unclassified Information provides assessment procedures and a methodology to conduct assessments of the CUI security requirements in SP 800-171. | [
-0.034264933,
0.00019542543,
0.053950164,
-0.0049048592,
0.008789929,
-0.0051581617,
0.004464047,
0.0025905948,
-0.0010189672,
0.033238564,
0.015132363,
0.02329068,
-0.01497446,
0.0026136222,
0.0005781549,
-0.021566907,
0.002118531,
0.018816764,
-0.003013314,
0.027633011,
0.0... | 35 |
| ........................................................................................................
22 |
| 3.13 SYSTEMANDCOMMUNICATIONSPROTECTION ..................................................................... | 23 |
| 3.14 SYSTEMANDINFORMATIONINTEGRITY ................................................................................ | 27 |
| REFERENCES .................................................................................................................................. 32 | REFERENCES .................................................................................................................................. 32 |
| APPENDIXA GLOSSARY................................................................................................................ 38 | APPENDIXA GLOSSARY................................................................................................................ 38 |
| APPENDIX B ACRONYMS.............................................................................................................. 48 | APPENDIX B ACRONYMS.............................................................................................................. 48 |
| APPENDIX C MAPPINGTABLES .................................................................................................... 50 | APPENDIX C MAPPINGTABLES .................................................................................................... | [
0.018712983,
0.018425753,
0.046157733,
-0.017851295,
-0.018009271,
0.011273746,
0.01239394,
-0.022432601,
-0.02302142,
-0.008609695,
0.008286563,
-0.006275958,
0.009485744,
-0.0148066655,
0.030072898,
-0.00017985485,
0.021700166,
0.033404756,
-0.008810756,
0.045611996,
0.0144... | 36 |
However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication.
As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents
| 1. Introduction...................................................................................................................................1 |
|-------------------------------------------------------------------------------------------------------------------------------------------------------|
| 2. The Fundamentals..........................................................................................................................3 |
| 3. The Procedures ..............................................................................................................................7 |
| B. Glossary .....................................................................................................................101 |
| Appendix A. Acronyms...................................................................................................................100 |
| Appendix |
| Appendix C. Security Requirement Assessment...............................................................................103 |
| Appendix D. Organization-Defined Parameters...............................................................................107 |
| Appendix E. | [
-0.019765142,
0.021252533,
0.06121187,
-0.039072625,
-0.014831007,
-0.0404456,
-0.039473075,
0.010740681,
-0.031034991,
-0.016003758,
0.045565657,
-0.024255918,
0.021481361,
-0.01073353,
0.0017323103,
-0.014595027,
0.06538801,
-0.013179145,
-0.044507325,
0.051429413,
0.005313... | 37 |
According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:
The National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |
|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... | [
-0.0055062273,
-0.01550315,
0.0562983,
-0.015664643,
0.046633676,
-0.026708152,
-0.019565275,
0.016372718,
-0.06385112,
-0.009260897,
0.018882042,
0.027130514,
-0.043428697,
-0.00453728,
0.031602576,
-0.015850978,
-0.0070000202,
0.012708112,
-0.0057888366,
0.038633652,
0.0465... | 38 |
..........30 |
| 2.3.4. Level 3 -Operational................................................................................................................32 |
| 2.3.5.
C-SCRM PMO..............................................................................................................................33 |
| Critical Success Factors...................................................................................................................37 |
| 3. |
| 3.1.2. The Role of C-SCRM in the Acquisition Process .........................................................................40 |
| 3.4.1. Foundational Practices ...............................................................................................................46 |
| 3.4.3. Enhancing Practices....................................................................................................................49 | |
|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|
| 3.5.1. Measuring C-SCRM Through Performance Measures................................................................52 | |
| References.........................................................................................................................................57 | |
| Appendix A. C-SCRM Security Controls............................................................................................... | [
0.031596992,
0.04263212,
0.105905496,
-0.020283999,
0.033026002,
0.014343023,
0.005312476,
-0.01241783,
-0.013112487,
0.03551354,
0.015031065,
-0.060441818,
-0.00511731,
0.02037662,
0.05499041,
0.018338958,
0.018974073,
-0.0135491295,
0.0078000114,
0.04294968,
0.07965406,
0... | 39 |
According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:
........................................................................ | CHAPTERONE INTRODUCTION......................................................................................................
|
|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |
| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |
| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |
| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |
| 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | [
0.024662834,
0.011386939,
0.05403475,
-0.014752472,
0.044270717,
-0.00014643141,
-0.02617932,
0.012018808,
-0.052571476,
0.0170272,
0.017386366,
0.001578009,
-0.00804136,
0.025926571,
0.023252768,
-0.015244664,
0.03474613,
0.011998855,
-0.028999448,
0.022853693,
0.028733399,
... | 40 |
tems (including hardware, software, firmware, and documentation); and establishing and enforcing security configuration settings for information technology products employed in organizational systems.
## Getting Started with Configuration Management
<!-- image -->
Changes to a system can have potentially significant effects on the security of the system. Configuration management helps establish processes for initializing, changing and monitoring configurations to the hardware, software, or firmware components of the system or the operational procedures related to the system storing CUI. ## Limit who can make changes to the system containing CUI. - Permit only qualified and authorized individuals to access the system for the purpose of initiating changes. Access restrictions include physical and logical access controls, software libraries, workflow automation, media libraries, abstract layers (i.e., changes implemented into external interfaces rather than directly into the system), and change windows (i.e., changes occur only during specified times). ## Authorized software -allow by exception. - It is important to identify permitted and prohibited actions regarding software installation when users have the ability to install software on organizational systems. Permitted software installations could include updates and security patches to existing software and downloading new applications from organizationapproved 'app stores.' Companies might prohibit employees from downloading certain programs, services, software versions, etc . ## Locate CUI. - Identify the location of CUI and the system components on which the information is processed and stored. Identify who within the business has access to CUI. Again, remember to restrict this access to only those who need it. Foundational Concept -Least Functionality: Systems (databases, email systems, network drives, etc.) provide a variety of functions and services. | [
0.012264149,
0.033847723,
0.06886536,
0.01403896,
0.017920947,
-0.02322544,
0.015860304,
0.02685483,
-0.008495167,
0.03320959,
0.021537043,
-0.0077174404,
-0.011891904,
0.015235463,
0.037596762,
0.0043339976,
0.0024046374,
0.030683639,
-0.002667203,
0.015514648,
0.0449619,
... | 41 |
ed as independent, third-party assessments or as government-sponsored assessments. The assessments can be applied with various degrees of rigor based on customer-defined depth and coverage attributes.
## Keywords
assessment; assessment method; assessment object; assessment procedure; assurance; Controlled Unclassified Information; coverage; FISMA; NIST Special Publication 800-171; NIST Special Publication 800-53A; nonfederal organization; nonfederal system; security assessment; security requirement. ## Reports on Computer Systems Technology
The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. | [
-0.025152372,
-0.006919191,
0.07157243,
-0.02091453,
0.022392543,
-0.023177328,
-0.03759122,
-0.04444501,
0.023726678,
0.00699113,
0.025309328,
-0.010136811,
-0.036309402,
-0.025636323,
0.02039134,
0.013073216,
-0.03544614,
-0.0036786816,
-0.011327069,
0.014662407,
0.01506787... | 42 |
According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:
| FAMILY | FAMILY |
|-----------------------------------|--------------------------------------|
| Access Control | Media Protection |
| Awareness and Training | Personnel Security |
| Audit and Accountability | Physical Protection |
| Configuration Management | Risk Assessment |
| Identification and Authentication | Security Assessment |
| Incident Response | System and Communications Protection |
| Maintenance | System and Information Integrity |
The assessment methods described above have associated attributes of depth and coverage , which affect the level of effort for the assessment. These attributes provide a means to define the rigor and scope of the assessment to obtain the assurance needed for enhanced security requirements. A description of assessment methods and objects is provided in Appendix C. Figure 1 illustrates an example of an assessment procedure for the CUI enhanced security requirement 3.1.3e from [SP 800-172].
## 3.1 ACCESS CONTROL | [
0.010063917,
0.046926316,
0.075669326,
0.012903449,
0.02691438,
0.010817262,
-0.006689962,
-0.006023541,
0.004767966,
0.020964885,
0.04646272,
-0.0019026792,
0.006735034,
0.012961399,
0.010096112,
-0.041904014,
0.009181796,
0.0021473553,
-0.034022868,
0.026862869,
0.02339877,... | 43 |
parameters that organizations define, providing them with the ability to tailor security controls based on specific security requirements, environments of operation, and organizational risk tolerance.
Parameters assigned and/or selected by organizations for a given base control also apply to all control enhancements associated with that control. The first security control in each family (referred to as the dash-1control) addresses policies and procedures needed for effective implementation of all the other controls within each family. Therefore, requirements to develop policies and procedures are not repeated in individual controls. Many security controls and enhancements include supplemental guidance. The supplemental guidance provides additional information about a control or enhancement to help organizations define, develop, and/or implement security controls but does not include any additional requirements. SP 800-53 Rev. 4 includes many changes from SP 800-53 Rev. 3 - 295 controls and control enhancements were added while approximately 100 controls and control enhancements were withdrawn or incorporated into others. Of the eighteen security control families in SP 800-53 Rev. 4, seventeen families are described in the security control catalog in Appendix F, and are closely aligned with the seventeen minimum security requirements for federal information and information systems in FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . One additional family, the Program Management (PM) family, provides controls for information security programs themselves. This family is described in Appendix G of SP 800-53 Rev. 4. While it is not specifically referenced in FIPS 200, the PM section provides security controls at the organization level rather than the information system level. The PM controls are typically implemented at the organization level and not directed at individual organizational information systems. | [
0.011079969,
0.003910761,
0.060874287,
0.0006324166,
-0.007634255,
0.0021535715,
-0.0013896779,
0.013258509,
-0.0011735404,
0.038901616,
0.010817795,
-0.019625591,
-0.004650466,
0.020511989,
-0.009119907,
-0.02272174,
0.04334609,
0.007153603,
-0.0021832222,
0.013508199,
0.034... | 44 |
According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:
| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |
|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |
| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |
| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |
| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |
| 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | [
0.02867414,
0.007869022,
0.055200994,
-0.015305968,
0.042841,
0.0015891889,
-0.024628337,
0.011666054,
-0.052241925,
0.017374696,
0.016248679,
0.0011963925,
-0.011711881,
0.024143888,
0.024667617,
-0.014638214,
0.03294253,
0.013839528,
-0.026042404,
0.02346304,
0.02809804,
... | 45 |
According to Assessing Security and Privacy Controls in Information Systems and Organizations:
NTROL ASSESSMENTS ..................................................... 30
3.4 ANALYZE ASSESSMENT REPORT RESULTS .....................................................................................
32
3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34
CHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37
4.1 ACCESS CONTROL............................................................................................................................ 40
4.2 AWARENESS AND TRAINING ........................................................................................................ 118
4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128
4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160
4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177
4.6 CONTINGENCY PLANNING ............................................................................................................ 215
4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243
4.8 INCIDENT RESPONSE ............................................................................................................... 275
4.9 MAINTENANCE ........................................................................................................................ 298
4.10 MEDIA PROTECTION .............................................................................................................. 316
4.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ....................................................................... | [
-0.001266238,
0.046408955,
0.052468646,
0.017035274,
0.022401387,
0.0151857305,
0.013056321,
0.0015575108,
-0.004794213,
0.022948949,
0.035043992,
-0.02944669,
0.034435593,
-0.0009384611,
-0.0015210067,
-0.042150136,
0.012885968,
0.040592626,
0.02181732,
0.018203408,
0.023216... | 46 |
According to Control Baselines for Information Systems and Organizations:
........................................................ 1 | CHAPTERONE INTRODUCTION......................................................................................................
1 |
|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|
| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |
| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |
| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ......................................................................................... | [
-0.017479543,
0.01870018,
0.07294535,
-0.008745874,
0.019920819,
-0.04242939,
-0.026121661,
-0.015001646,
-0.045114797,
0.023961132,
0.029075606,
-0.024620276,
-0.0111505315,
-0.01967669,
0.026780806,
-0.0050778557,
0.014586629,
0.0023512547,
0.012249107,
0.027098173,
0.02130... | 47 |
blication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations.
## Audience
This publication serves a diverse group of individuals and organizations in the public and private sectors, including individuals with:
- System development life cycle responsibilities (e.g., program managers, mission/business owners, information owners/stewards, system designers and developers, system/security engineers, systems integrators)
- Acquisition or procurement responsibilities (e.g., contracting officers)
- System, security, or risk management and oversight responsibilities (e.g., authorizing officials, chief information officers, chief information security officers, system owners, information security managers)
- Security assessment and monitoring responsibilities (e.g., auditors, system evaluators, assessors, independent verifiers/validators, analysts)
The above roles and responsibilities can be viewed from two perspectives:
- Federal perspective : The entity establishing and conveying security assessment requirements in contractual vehicles or other types of agreements
- Nonfederal perspective : The entity responding to and complying with the security assessment requirements set forth in contracts or agreements
## Patent Disclosure Notice
NOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. | [
-0.0023717494,
-0.00066400575,
0.07907177,
-0.031677153,
0.0022035402,
-0.029066546,
-0.021315467,
0.011061436,
-0.02831297,
-0.010846128,
0.043734387,
-0.022688054,
0.017857086,
-0.036252443,
0.036979105,
0.0040033786,
0.041177608,
-0.0013246473,
-0.01990251,
0.045241542,
0.... | 48 |
## Control Baselines for Information Systems and Organizations
JOINT TASK FORCE
This publication is available free of charge from:
https://doi.org/10.6028/NIST.SP.800-53B
<!-- image -->
## NIST Special Publication 800-53B
## Control Baselines for Information Systems and Organizations
## JOINT TASK FORCE
This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B
## October 2020
INCLUDES UPDATES AS OF 12-10-2020; SEE PAGE XI
<!-- image -->
U.S. Department of Commerce Wilbur L. Ross, Jr., Secretary
National Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
## Authority
This publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems. Such information security standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. | [
-0.042390596,
0.008133696,
0.07089827,
-0.016161416,
-0.009339179,
-0.006345343,
-0.028905088,
-0.017645087,
-0.020837627,
0.015167885,
0.018598875,
0.008656955,
-0.0214205,
-0.0015747445,
0.013737204,
0.018731346,
-0.009988285,
-0.00784226,
0.023738734,
0.007047437,
0.000844... | 49 |
According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:
- Authority and Purpose (AP);
- Accountability, Audit, and Risk Management (AR);
- Data Quality and Integrity (DI);
- Data Minimization and Retention (DM);
- Individual Participation and Redress (IP);
- Security (SE);
- Transparency (TR); and,
- Use Limitation (UL). | [
-0.018334901,
0.035024703,
0.056676336,
0.021227092,
0.018334901,
-0.0037213746,
-0.04062335,
0.016119324,
-0.012948526,
0.013379701,
0.03136303,
-0.0111110555,
-0.027860558,
0.01565498,
0.010142569,
-0.038261835,
0.014965099,
0.020895418,
0.009591992,
0.023336533,
0.03635139... | 50 |
vant -based on the systems that personnel have authorized access to, contextualized to the work environments of personnel (e.g., telework, shop floor), and tailored to the specific roles of personnel.
The content should include:
- An understanding of the need for security (why is cybersecurity important to our business mission?). - Specific actions required of users to maintain security (required use of multi-factor authentication, not sharing passwords, etc.). - How to respond to confirmed or suspected incidents. - How to securely handle CUI (training should be provided to staff before authorizing access to the system or CUI). - How to recognize and report insider threats, social engineering, and social mining. Examples of security awareness techniques include displaying posters, offering supplies inscribed with security reminders, generating email advisories or notices from leadership, and conducting awareness events -such as a lunch-and-learn or workshop. There are many resources that are free and open to the public that can be incorporated into awareness and training, such as videos, online courses, and awareness posters. The resources will likely need to be customized to meet your own unique business needs, but they offer a starting point. Resources can be found in the resources box below. | [
-0.020306952,
0.044211593,
0.0818674,
0.034857605,
0.024584204,
-0.042479374,
-0.0028148582,
0.058149304,
0.027822124,
0.041386742,
0.040827103,
-0.018281588,
-0.0046003778,
-0.037762403,
0.042506024,
0.0063226046,
0.013318109,
0.011026249,
-0.06598427,
-0.0037409298,
0.03637... | 51 |
parameters that organizations define, providing them with the ability to tailor security controls based on specific security requirements, environments of operation, and organizational risk tolerance.
Parameters assigned and/or selected by organizations for a given base control also apply to all control enhancements associated with that control. The first security control in each family (referred to as the dash-1control) addresses policies and procedures needed for effective implementation of all the other controls within each family. Therefore, requirements to develop policies and procedures are not repeated in individual controls. Many security controls and enhancements include supplemental guidance. The supplemental guidance provides additional information about a control or enhancement to help organizations define, develop, and/or implement security controls but does not include any additional requirements. SP 800-53 Rev. 4 includes many changes from SP 800-53 Rev. 3 - 295 controls and control enhancements were added while approximately 100 controls and control enhancements were withdrawn or incorporated into others. Of the eighteen security control families in SP 800-53 Rev. 4, seventeen families are described in the security control catalog in Appendix F, and are closely aligned with the seventeen minimum security requirements for federal information and information systems in FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . One additional family, the Program Management (PM) family, provides controls for information security programs themselves. This family is described in Appendix G of SP 800-53 Rev. 4. While it is not specifically referenced in FIPS 200, the PM section provides security controls at the organization level rather than the information system level. The PM controls are typically implemented at the organization level and not directed at individual organizational information systems. | [
0.010864979,
0.0039596953,
0.061008636,
0.0008292269,
-0.0076073576,
0.0021140217,
-0.0013596825,
0.0131802615,
-0.0013050769,
0.038841832,
0.010852498,
-0.01965806,
-0.004689852,
0.02040694,
-0.009292334,
-0.022678537,
0.043260217,
0.0070956238,
-0.0022981209,
0.013417407,
0... | 52 |
.......................................................................... 424
APPENDIX C CONTROL SUMMARIES ..........................................................................................
428
xiii
T
h
s
i
p
u
b
l
i
c
a
t
i
o
n
i
s
a
v
a
i
l
l
a
b
e
f
r
e
e
o
f
c
h
a
r
g
e
f
r
o
m
:
h
t
t
p
s
:
/
/
d
o
i
. o
r
g
/
1
0
. 6
0
2
8
/
N
S
T
S
P
. 8
0
0
-
5
3
r
5
. I
NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS
_________________________________________________________________________________________________
Executive Summary
As we push computers to “the edge,” building an increasingly complex world of connected
information systems and devices, security and privacy will continue to dominate the national
dialogue. In its 2017 report, Task Force on Cyber Deterrence [DSB 2017], the Defense Science
Board (DSB) provides a sobering assessment of the current vulnerabilities in the U.S. critical
infrastructure and the information systems that support mission-essential operations and assets
in the public and private sectors. “…The Task Force notes that the cyber threat to U.S. critical infrastructure is outpacing
efforts to reduce pervasive vulnerabilities, so that for the next decade at least the United States
must lean significantly on deterrence to address the cyber threat posed by the most capable
U.S. adversaries. It is clear that a more proactive and systematic approach to U.S. cyber
deterrence is urgently needed…”
There is an urgent need to further strengthen the underlying information systems, component
products, and services that the Nation depends on in every sector of the critical infrastructure—
ensuring that those systems, components, and services are sufficiently trustworthy and provide
the necessary resilience to support the economic and national security interests of the United
States. | [
0.03676339,
0.009441927,
0.053968973,
0.043846488,
0.051246736,
0.013822611,
-0.013981189,
0.038877748,
-0.00037352272,
0.022782201,
0.02730164,
-0.022914348,
-0.008285638,
-0.026099099,
0.01053875,
0.005959845,
0.035574064,
-0.00021071306,
0.034067582,
0.006858447,
0.0160559... | 53 |
According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:
The security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs. Organizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include: | [
-0.03500365,
0.009512632,
0.11119918,
-0.009660251,
0.0119336,
-0.012695318,
-0.0036964044,
-0.0049186978,
0.009766538,
0.025296161,
0.0037643095,
0.0002415432,
-0.012057601,
0.001684344,
0.007274713,
-0.04728563,
0.03568861,
0.012896081,
-0.011213214,
0.0074341423,
0.0252725... | 54 |
following components: (i) a control section; (ii) a supplemental guidance section; (iii) a control enhancements section; (iv) a references section; and (v) a priority and baseline allocation section.
Figure 2: The Risk Management Framework
<!-- image -->
## 3 Control Baselines and Tailoring
To assist organizations in making the appropriate selection of security controls for information systems, the concept of security control baselines is introduced. Security control baselines are the starting point for the security control selection process and are chosen based on the security category and associated impact level of information systems determined in accordance with FIPS Publication 199 and FIPS Publication 200, respectively (Step One of the RMF). SP 800-53 Rev. 4 states that 'the security controls and control enhancements listed in the initial baselines are not a minimum- but rather a proposed starting point from which controls and controls enhancements may be removed or added.' Appendix D provides a listing of baseline security controls corresponding to the low-impact, moderate-impact, and high-impact information systems, using the high water mark defined in FIPS Publication 200. The security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs. | [
-0.027147004,
0.033233777,
0.10722458,
-0.02702527,
0.003813363,
-0.019489845,
-0.0067319702,
0.018747259,
0.009172766,
0.06588323,
-0.00097007933,
-0.012721354,
-0.025540097,
0.0017088613,
0.03661802,
-0.048304625,
0.018138582,
0.008527568,
0.01329351,
0.018162929,
0.0038742... | 55 |
According to Control Baselines for Information Systems and Organizations:
| CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |
|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|
| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |
| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |
| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ......................................................................................... | [
-0.016269423,
0.0185118,
0.068733744,
-0.0020199677,
0.021205092,
-0.045676254,
-0.030052733,
-0.01697626,
-0.03726734,
0.020912608,
0.025129251,
-0.026591672,
-0.011473904,
-0.019620802,
0.026347935,
-0.0071171112,
0.013344583,
0.0049052006,
0.012710868,
0.026079824,
0.02851... | 56 |
According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:
ource code. | CUI//SP-CTI |
| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications.
| CUI//PROPIN |
| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |
| Access Control | Maintenance | Security Assessment and Monitoring |
|-----------------------------------|---------------------|--------------------------------------|
| Awareness and Training | Media Protection | System and Communications Protection |
| Audit and Accountability | Personnel Security | System and Information Integrity |
| Configuration Management | Physical Protection | Planning |
| Identification and Authentication | Risk Assessment | System and Services Acquisition |
| Incident Response | | Supply Chain Risk Management | | [
-0.008124537,
0.008853749,
0.048705943,
-0.002142924,
0.023472412,
-0.031204823,
-0.0016802863,
0.02098208,
-0.015327238,
0.0024920518,
0.0517879,
0.008922543,
-0.0069791214,
0.017528636,
0.024229143,
-0.014900716,
-0.00090377725,
-0.007842482,
-0.03769895,
0.012465419,
0.043... | 57 |
According to Zero Trust Architecture:
| | | 3.2.2. | [
0.0068728575,
0.043250676,
0.04080759,
0.008040706,
0.03130372,
-0.0070205163,
-0.033263557,
0.013712156,
-0.021048125,
0.028887479,
-0.0016015972,
-0.0029716382,
0.0006971856,
0.012993996,
-0.0043861447,
-0.009819326,
0.04913019,
-0.016242495,
-0.016819708,
0.036243584,
0.01... | 58 |
According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:
............................................ 5 |
| 2.1 DEVELOPMENTAPPROACH ......................................................................................................
| 5 |
| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |
| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |
| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |
| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |
| 3.2 AWARENESSANDTRAINING | ................................................................................................... | [
0.017715218,
0.028639602,
0.051454652,
-0.015903434,
0.060768563,
0.0064553176,
-0.010763337,
0.01538003,
-0.0412013,
0.016789194,
0.024465788,
-0.0016071191,
0.008179868,
0.030706376,
0.014802943,
-0.017916527,
0.045388535,
0.004989115,
-0.033095248,
0.032343693,
0.03808772,... | 59 |
According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:
The target audience for this publication includes cybersecurity program leadership, cybersecurity personnel, and others who are responsible for preparing for, detecting, responding to, or recovering from cybersecurity incidents. This publication is intended for use by most organizations, regardless of sector, size, or other factors.
At that time, incidents were relatively rare, the scope of most incidents was narrow and welldefined, and incident response and recovery was usually completed within a day or two. Under those conditions, it was realistic to treat incident response as a separate set of activities performed by a separate team of personnel and to depict all incident response activities as part of a circular life cycle. Formal post-incident activities would identify needed improvements and feed them into the preparation stage, thus starting the cycle again. Incident response activities were typically intermittent rather than continuous.
(e.g., detecting the presence of a new threat and characterizing its behavior) and communicate those lessons to the appropriate personnel so that the organization's incident response and other cybersecurity risk management policies, processes, and practices can be adjusted as needed. | [
-0.015239611,
-0.004197243,
0.057758126,
0.0034098632,
0.023799194,
-0.0075563076,
0.012826673,
0.051128898,
0.0023192784,
0.09301243,
0.042493116,
-0.0353559,
0.011264613,
-0.0034955859,
0.018605025,
0.0035590844,
0.015811097,
-0.0005841851,
-0.048004776,
0.010731227,
0.0036... | 60 |
According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:
| Access Control | Maintenance | Security Assessment and Monitoring |
|-----------------------------------|---------------------|--------------------------------------|
| Awareness and Training | Media Protection | System and Communications Protection |
| Audit and Accountability | Personnel Security | System and Information Integrity |
| Configuration Management | Physical Protection | Planning |
| Identification and Authentication | Risk Assessment | System and Services Acquisition |
| Incident Response | | Supply Chain Risk Management |
Below is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:
## Family: Incident Response | [
-0.045868356,
0.03636945,
0.049533695,
-0.004878514,
0.011454184,
-0.01963021,
0.0060303854,
0.03162,
-0.0030361651,
0.027077043,
0.051624488,
0.0008929423,
0.0122350035,
0.013783738,
0.017487796,
-0.029322708,
0.0151001625,
0.026083272,
-0.035388585,
0.040086415,
0.06391112,... | 61 |
According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:
| | When provided as part of a government contract, examples include: | Marking 1 |
|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |
| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | [
0.010481475,
0.006414983,
0.03987097,
-0.0038296415,
0.017760463,
-0.018774584,
-0.023244722,
0.0242455,
-0.04120534,
-0.0037829385,
0.042539712,
0.0051206443,
-0.0007026291,
-0.0019131528,
0.023538284,
0.013617245,
-0.014891568,
-0.018134085,
-0.040538155,
-0.0008756802,
0.0... | 62 |
According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:
t of Defense Federal Acquisition Regulation). Organizations can use the assessment procedures to generate evidence to support the assertion that the enhanced security requirements have been satisfied.
The assessment procedures are typically used as part of an assessment process. An assessment process is an information-gathering and evidenceproducing activity to determine the effectiveness of the safeguards implemented to meet the set of security requirements specified in [SP 800-172]. The information gathered and evidence produced can be used by an organization to: | [
0.022073518,
0.029854128,
0.048830036,
0.010347724,
0.03373224,
0.04702513,
-0.012914837,
0.026366267,
-0.005417768,
0.040634785,
0.03380541,
-0.011768478,
0.01095749,
-0.0067623015,
0.018463705,
-0.031610254,
-0.01670758,
-0.017561251,
-0.040537223,
-0.005262278,
0.039732333... | 63 |
According to Assessing Security and Privacy Controls in Information Systems and Organizations:
CHAPTER ONE INTRODUCTION ............................................................................................................... 1
1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1
1.2 TARGET AUDIENCE ............................................................................................................................ 4
1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4
1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5
CHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6
2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6
2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7
2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8
2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11
CHAPTER THREE THE PROCESS ............................................................................................................. 19
3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19
3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23
3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30
3.4 ANALYZE ASSESSMENT REPORT RESULTS ..................................................................................... | [
-0.001046523,
0.01816868,
0.051043686,
0.022105807,
0.01711492,
-0.0054193386,
-0.021503659,
-0.00070274813,
-0.010022303,
0.024155429,
0.030871704,
-0.0376343,
0.02406279,
-0.0054367087,
0.01286514,
-0.025591321,
0.027351448,
0.03221496,
0.032400236,
0.006913131,
0.032956064... | 64 |
According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:
SP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy.
The criteria for whether a security control is assurance- or functionality-related is based on the overall characteristics of the control. In general, assurance-related controls are controls that: (i) define processes, procedures, techniques, or methodologies for designing and developing information systems and system components; (ii) provide supporting operational processes including improving the quality of systems, components, or processes; (iii) produce security evidence from developmental or operational activities; (iv) determine security control effectiveness or risk; or (v) improve personnel skills, expertise, and understanding. | [
-0.012614118,
0.006695367,
0.047491215,
0.019109448,
0.023145495,
-0.008913428,
0.015708813,
-0.010666696,
0.021156888,
0.033347398,
0.014037914,
0.0018194572,
-0.02586365,
0.021768767,
-0.02586365,
-0.048856173,
0.023027826,
-0.005471609,
0.027252143,
-0.001123739,
0.0262637... | 65 |
..................................................... 50 | APPENDIX C MAPPINGTABLES ....................................................................................................
50 |
| APPENDIXD ADVERSARY EFFECTS............................................................................................... 68 | APPENDIXD ADVERSARY EFFECTS............................................................................................... 68 |
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
## Errata
This table contains changes that have been incorporated into Special Publication 800-172. Errata updates can include corrections, clarifications, or other minor changes in the publication that are either editorial or substantive in nature. Any potential updates for this document that are not yet published in an errata update or revision-including additional issues and potential corrections-will be posted as they are identified; see the SP 800-172 publication details. | DATE | TYPE | CHANGE | PAGE |
|--------|--------|----------|--------|
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
## CHAPTER ONE
## INTRODUCTION
THE NEED TO PROTECT CONTROLLED UNCLASSIFIED INFORMATION
oday, more than at any time in history, the Federal Government relies on external service providers to help carry out a wide range of federal missions and business functions using information systems. | [
-0.005496149,
0.020427067,
0.081928805,
0.012198349,
0.0205649,
0.021571092,
0.013549128,
0.0005315241,
-0.028338766,
0.029469008,
0.03724287,
-0.025885312,
0.013700745,
0.0099447565,
0.039889295,
-0.007339685,
0.02660205,
0.011130133,
0.015106657,
0.014114249,
0.005127442,
... | 66 |
According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:
............................................ 5 |
| 2.1 DEVELOPMENTAPPROACH ......................................................................................................
| 5 |
| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |
| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |
| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |
| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |
| 3.2 AWARENESSANDTRAINING | ................................................................................................... | [
0.017698973,
0.028635034,
0.051500123,
-0.015874062,
0.06086622,
0.006450934,
-0.010721365,
0.015390996,
-0.04119473,
0.016799936,
0.02444847,
-0.001623636,
0.008198691,
0.030728318,
0.014787164,
-0.017953925,
0.04535446,
0.004968192,
-0.03308997,
0.03228486,
0.038135316,
0... | 67 |
| ........................................................................................................
22 |
| 3.13 SYSTEMANDCOMMUNICATIONSPROTECTION ..................................................................... | 23 |
| 3.14 SYSTEMANDINFORMATIONINTEGRITY ................................................................................ | 27 |
| REFERENCES .................................................................................................................................. 32 | REFERENCES .................................................................................................................................. 32 |
| APPENDIXA GLOSSARY................................................................................................................ 38 | APPENDIXA GLOSSARY................................................................................................................ 38 |
| APPENDIX B ACRONYMS.............................................................................................................. 48 | APPENDIX B ACRONYMS.............................................................................................................. 48 |
| APPENDIX C MAPPINGTABLES .................................................................................................... 50 | APPENDIX C MAPPINGTABLES .................................................................................................... | [
0.018712983,
0.018425753,
0.046157733,
-0.017851295,
-0.018009271,
0.011273746,
0.01239394,
-0.022432601,
-0.02302142,
-0.008609695,
0.008286563,
-0.006275958,
0.009485744,
-0.0148066655,
0.030072898,
-0.00017985485,
0.021700166,
0.033404756,
-0.008810756,
0.045611996,
0.0144... | 68 |
.................................................................................. 4
1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ...............................................................
4
1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5
CHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6
2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6
2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7
2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8
2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11
CHAPTER THREE THE PROCESS ............................................................................................................. 19
3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19
3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23
3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30
3.4 ANALYZE ASSESSMENT REPORT RESULTS ..................................................................................... 32
3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34
CHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37
4.1 ACCESS CONTROL............................................................................................................................ | [
0.018476287,
0.006189848,
0.06984852,
-0.006434644,
0.016063295,
0.021600354,
0.0016582031,
0.0031969224,
0.0030220677,
-0.0043043336,
0.03886432,
-0.049052503,
0.009039976,
-0.021052476,
0.008690266,
-0.0073497156,
0.032965895,
0.031263977,
0.033129092,
-0.0019219419,
0.0155... | 69 |
n the risk tolerance of the organizations or communities of interest developing the overlays. General guidance on overlays is provided in section 3.3 and an overlay template is provided in Appendix I.
The template is included as an example only-organizations may choose to use other formats or modify the format in this appendix based on organizational needs and the type of overlay being developed. The level of detail included in the overlay is at the discretion of the organization initiating the overlay but should be of sufficient breadth and depth to provide an appropriate rationale and justification for the resulting tailored baseline developed, including any risk-based decisions made during the overlay development process. The sample overlay template consists of eight sections:
- Identification;
- Overlay Characteristics;
- Applicability;
- Overlay Summary;
- Detailed Overlay Control Specifications;
- Tailoring Considerations;
- Definitions; and
- Additional Information or Instructions. ## 9 Privacy
Federal agencies are required to ensure that privacy protections are incorporated into information security planning. To that end, SP 800-53 Rev. 4 features eight new families of privacy controls that are based on the internationally accepted Fair Information Practice Principles (FIPPs). The proliferation of social media, Smart Grid, mobile, and cloud computing, as well as the transition from structured to unstructured data and metadata environments, have added significant complexities and challenges for federal organizations in safeguarding privacy. These challenges extend well beyond the traditional information technology security view of protecting privacy, which focused primarily on ensuring confidentiality. The families of controls are described in a similar manner to those of Appendix F (Security Controls) and Appendix G (Information Security Programs Organization-Wide Information Security Program Management Controls). SP 800-53 Rev. | [
0.0027670853,
-0.0044724997,
0.057323493,
0.004071424,
-0.011391898,
-0.013393906,
0.014465689,
-0.032490503,
-0.008446182,
0.003835497,
-0.0032878097,
0.0080619585,
0.007697957,
-0.0021519903,
0.016717104,
-0.015112802,
0.07021184,
-0.020087488,
0.020208823,
0.026477737,
-0.... | 70 |
nformation, including inconsistent markings, inadequate safeguarding, and needless restrictions, both by standardizing procedures and by providing common definitions through a CUI Registry [NARA CUI].
The CUI Registry is the online repository of information, guidance, policy, and requirements on handling CUI, including issuances by the National Archives and Records Administration (NARA) CUI Executive Agent. The CUI Registry identifies approved CUI categories, provides general
1 An information system is a discrete set of information resources organized expressly for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information. Information systems also include specialized systems, such as industrial and process control systems, cyber-physical systems, IoT systems, embedded systems, and devices. The term system is used throughout this publication to represent all types of computing platforms that can process, store, or transmit CUI. 2 A federal information system is a system that is used or operated by an executive agency, a contractor of an executive agency, or another organization on behalf of an executive agency. A system that does not meet such criteria is a nonfederal system . 3 Controlled Unclassified Information is any information that law, regulation, or government-wide policy requires to have safeguarding or disseminating controls, excluding information that is classified under [EO 13526] or any predecessor or successor order, or [ATOM54], as amended. 4 Established by Executive Order 13556, the CUI Program standardizes the way that the Executive branch handles unclassified information that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and government-wide policies. 5 [EO 13556] designated the National Archives and Records Administration (NARA) as the Executive Agent to implement the CUI Program. | [
-0.012287515,
0.019476263,
0.03390552,
0.037347835,
0.020731542,
0.014610432,
0.021339772,
-0.024704441,
-0.0073634507,
0.037347835,
0.031317312,
-0.0028162934,
-0.026037369,
-0.010106951,
0.0035102565,
-0.0061275815,
0.0053025903,
-0.0027952641,
0.0031834953,
0.0059658187,
0... | 71 |
According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:
............................................ 5 |
| 2.1 DEVELOPMENTAPPROACH ......................................................................................................
| 5 |
| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |
| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |
| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |
| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |
| 3.2 AWARENESSANDTRAINING | ................................................................................................... | [
0.017687652,
0.02863843,
0.05150623,
-0.015889363,
0.06081976,
0.006411439,
-0.010736057,
0.015379401,
-0.041172776,
0.016801927,
0.024437947,
-0.0016137635,
0.008192953,
0.03070512,
0.014775498,
-0.017942633,
0.04538668,
0.004952006,
-0.033093892,
0.03231553,
0.038112998,
... | 72 |
According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:
Information technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security .
ISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products). Since many of the technical security controls defined in Appendix F are implemented in hardware, software, and firmware components of information systems, organizations can obtain significant benefit from the acquisition and employment of information technology products evaluated against the requirements of ISO/IEC 15408. The use of such products can provide evidence that certain security controls are implemented correctly, operating as intended, and producing the desired effect in satisfying stated security requirements. | [
-0.04415619,
0.0071929963,
0.01652334,
-0.0060303733,
0.04035124,
-0.0075864093,
0.014268557,
0.017662477,
-0.0026981076,
0.008420209,
0.016311955,
-0.007968078,
-0.040867962,
-0.0057191662,
0.011450076,
-0.045166146,
-0.0106749935,
0.0034937412,
-0.0027259989,
0.0020199108,
... | 73 |
description of assessment methods and objects is provided in Appendix C. Figure 1 illustrates an example of an assessment procedure for the CUI enhanced security requirement 3.1.3e from [SP 800-172].
FIGURE 1: ASSESSMENT PROCEDURE FOR CUI ENHANCED SECURITY REQUIREMENT
<!-- image -->
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Organizations are not expected to use all of the assessment methods and objects contained within the assessment procedures identified in this publication. Rather, organizations have the flexibility to establish the level of effort needed and the assurance required for an assessment (e.g., which assessment methods and objects are deemed to be the most useful in obtaining the desired results). The decision on level of effort is made based on how the organization can accomplish the assessment objectives in the most cost-effective and efficient manner and with sufficient confidence to support the determination that the CUI enhanced security requirements have been satisfied. ## ORGANIZATION-DEFINED PARAMETERS
Selected enhanced security requirements contain selection and assignment operations to give organizations flexibility in defining variable parts of those requirements. Selection operations require organizations to select from a list of predefined items. Assignment operations require organizations to define specific parameter values. Determination statements for organizationdefined parameters (ODP) are listed first in the assessment objective section followed by the list of determination statements for the assessment objective. Determination statements for ODPs are noted in bold italics . The ODP values are used in the appropriate determination statements in the assessment procedure, also noted in bold italics . | [
-0.0025200052,
0.016067302,
0.07124007,
-0.0021189828,
0.008152473,
-0.011453069,
0.0039112065,
-0.021612303,
0.03482789,
0.046604417,
0.03870939,
-0.038102083,
0.0171631,
-0.0018483339,
0.013189183,
-0.019103851,
0.010330866,
0.006604493,
-0.022774113,
0.020767352,
0.0211370... | 74 |
According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:
<!-- image -->
## NIST Special Publication 800 NIST SP 800-171r3
## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations
Ron Ross Victoria Pillitteri
This publication is available free of charge from:
https://doi.org/10.6028/NIST.SP.800-171r3
<!-- image -->
## NIST Special Publication 800 NIST SP 800-171r3
## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations
Ron Ross Victoria Pillitteri Computer Security Division
Information Technology Laboratory
This publication is available free of charge from:
https://doi.org/10.6028/NIST.SP.800-171r3
May 2024
<!-- image -->
U.S. Department of Commerce Gina M. Raimondo, Secretary
Certain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. | [
-0.029872952,
-0.008530106,
0.020337235,
-0.014043381,
0.03282649,
0.006888078,
-0.004940148,
0.016666407,
-0.025625478,
-0.012608805,
0.038677316,
0.010667907,
-0.0056715007,
-0.017439952,
0.02478161,
-0.0007616794,
-0.005973887,
0.00741198,
-0.02694754,
0.04660968,
-0.00026... | 75 |
traditional Information Technology (IT) systems, Operational Technology (OT) systems, Internet of Things
6 [32 CFR 2002] was issued on September 14, 2016, and went into effect on November 14, 2016.
7 The definition of a critical program may vary from organization to organization. For example, the Department of Defense defines a critical program as a program which significantly increases capabilities and mission effectiveness or extends the expected effective life of an essential system/capability [DOD ACQ]. 8 See [OMB M-19-03] and [OCIO HVA]. CHAPTER ONE PAGE 2
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
(IoT) systems, and Industrial IoT (IIoT) systems. The convergence of these types of systems has brought forth a new class of systems known as cyber-physical systems , many of which are in sectors of U.S. critical infrastructure, including energy, transportation, defense, manufacturing, healthcare, finance, and information and communications. Therefore, CUI that is processed, stored, or transmitted by any of the above systems related to a critical program or high value asset requires additional protection from the APT. | [
-0.014965037,
-0.005012132,
0.039825212,
0.005188831,
0.04507181,
-0.0027965999,
-0.008005819,
0.0024313089,
0.007407761,
0.026504835,
0.034442693,
-0.0062014516,
-0.03900968,
-0.03033784,
0.029821336,
0.012865039,
0.006639801,
-0.015766978,
-0.017887365,
0.029196095,
0.02335... | 76 |
According to Assessing Security Requirements for Controlled Unclassified Information:
The purpose of this publication is to provide procedures for assessing the security requirements in NIST Special Publication (SP) 800-171, Protecting Controlled Unclassified Information (CUI) in Nonfederal Systems and Organizations [3]. Organizations can use the assessment procedures to generate evidence that the security requirements have been satisfied. The scope of the security assessments conducted using the procedures described in this publication is guided and informed by the system security plans for systems that process, store, or transmit CUI. The assessment procedures offer the flexibility to customize assessments based on organizational policies and requirements, known threat and vulnerability information, system and platform dependencies, operational considerations, and tolerance for risk. 1
| Access Control | Maintenance | Security Assessment and Monitoring |
|-----------------------------------|---------------------|--------------------------------------|
| Awareness and Training | Media Protection | System and Communications Protection |
| Audit and Accountability | Personnel Security | System and Information Integrity |
| Configuration Management | Physical Protection | Planning |
| Identification and Authentication | Risk Assessment | System and Services Acquisition |
| Incident Response | | Supply Chain Risk Management |
A.03.02.01.a.03[01]: security literacy training is provided to system users on recognizing indicators of insider threat. | [
-0.014503748,
0.045798704,
0.050942406,
0.0035641135,
0.034225382,
0.008315234,
0.024729323,
0.027523736,
0.01732289,
0.010794349,
0.037638027,
-0.014380101,
0.013168364,
0.021032289,
0.04203985,
-0.048716765,
0.0071467743,
0.0277463,
-0.040704466,
0.016865399,
0.04463643,
... | 77 |
According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:
ance. The decision to select a particular set of enhanced security requirements will be based on the mission and business needs of federal agencies and guided and informed by ongoing risk assessments.
The enhanced security requirements for nonfederal systems processing, storing, or transmitting CUI associated with critical programs or high value assets will be conveyed to nonfederal organizations by federal agencies in a contract, grant, or other agreement. The application of the enhanced security requirements to subcontractors will also be addressed by federal agencies in consultation with nonfederal organizations. | [
-0.028788645,
-0.0015861555,
0.057873826,
0.017841546,
0.043368302,
0.018953554,
-0.008092945,
0.00072550785,
-0.03521358,
0.019867871,
0.014900904,
-0.018558174,
-0.030320745,
0.026811743,
0.019843161,
-0.017680923,
0.01664305,
-0.015073882,
-0.04465329,
0.003277334,
0.04247... | 78 |
ed security services provider (MSSP), talk to others in your industry to get their perspective on vendors they have worked with and always thoroughly review any contract or agreement prior to signing.
A helpful resource, assembled by member company participants of the National Defense Information Sharing& Analysis Center (ND-ISAC), is the Defense Industrial Base Managed Service Provider Shopping Guide for Small & Medium-Sized Businesses. You may also explore the CyberAB Marketplace to find a consulting firm to assist in NIST 800-171 implementation.* |
| Review NIST SP 800-171A to help you understandhow the security requirements in SP 800-171 can be self-assessed or are assessed by independent, third-party entities or by the | Review NIST SP 800-171A to help you understandhow the security requirements in SP 800-171 can be self-assessed or are assessed by independent, third-party entities or by the |
* We provide links to non-NIST sites throughout this publication because they may have information of interest to readers. NIST does not necessarily endorse the views expressed or the facts presented on those sites. | [
-0.03928658,
-0.039415475,
0.068416394,
-0.021898918,
0.00500427,
-0.01781301,
-0.031707674,
0.017684117,
0.03967326,
0.03727585,
0.027943999,
-0.028691579,
0.0056616245,
-0.020648656,
0.01470669,
-0.00016796366,
-0.01578939,
0.0058517414,
-0.0352909,
-0.023432745,
0.02688707... | 79 |
According to Assessing Security Requirements for Controlled Unclassified Information:
<!-- image -->
## NIST Special Publication 800 NIST SP 800-171Ar3
## Assessing Security Requirements for Controlled Unclassified Information
Ron Ross Victoria Pillitteri
This publication is available free of charge from:
https://doi.org/10.6028/NIST.SP.800-171Ar3
<!-- image -->
## NIST Special Publication
## NIST SP 800-171Ar3
## Assessing Security Requirements for Controlled Unclassified Information
Ron Ross Victoria Pillitteri Computer Security Division
Information Technology Laboratory
This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-171Ar3
May 2024
<!-- image -->
U.S. Department of Commerce Gina M. Raimondo, Secretary
National Institute of Standards and Technology
Certain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at
Organizations are encouraged to review all draft publications during public comment periods and provide feedback https://csrc.nist.gov/publications. | [
-0.02332809,
0.010972947,
0.045809936,
-0.029646702,
0.041042767,
0.0037587278,
0.0039843926,
-0.008525895,
-0.013025085,
-0.008342543,
0.030126238,
0.0051761842,
-0.010451097,
0.0011741617,
0.024315372,
-0.0036670514,
-0.0021508667,
0.002505231,
-0.020662425,
0.045330398,
0.... | 80 |
According to Assessing Security and Privacy Controls in Information Systems and Organizations:
NTROL ASSESSMENTS ..................................................... 30
3.4 ANALYZE ASSESSMENT REPORT RESULTS .....................................................................................
32
3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34
CHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37
4.1 ACCESS CONTROL............................................................................................................................ 40
4.2 AWARENESS AND TRAINING ........................................................................................................ 118
4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128
4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160
4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177
4.6 CONTINGENCY PLANNING ............................................................................................................ 215
4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243
4.8 INCIDENT RESPONSE ............................................................................................................... 275
4.9 MAINTENANCE ........................................................................................................................ 298
4.10 MEDIA PROTECTION .............................................................................................................. 316
4.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ....................................................................... | [
-0.0012594354,
0.046386164,
0.052470393,
0.017023673,
0.0224143,
0.015198404,
0.013032419,
0.0015697312,
-0.004806541,
0.022961881,
0.035045158,
-0.029423332,
0.0344124,
-0.0009301265,
-0.0015271415,
-0.042175878,
0.012886398,
0.04056964,
0.021805877,
0.018191844,
0.02321742,... | 81 |
According to Zero Trust Architecture:
forma estricta antes de permitir el acceso . Se trata de un ciclo constante de acceso, escaneo y evaluación de amenazas, adaptación y reevaluación continua de la confianza en permanente comunicación.
Así, se espera que la empresa que implemente una ZTA cuente con una gestión de la identidad, credenciales y acceso (ICAM, por su nombre en inglés Identity, Credential, and Access Management) y sistemas establecidos de gestión de activos. Entre ellos, se incluye el uso de la autenticación multifactor (MFA, por su denominación en inglés multifactor authentication ) para el acceso a algunos o todos los recursos de la empresa. La supervisión continua con posibles reautenticación y reautorización se produce a lo largo de las transacciones de los usuarios, según lo definido y aplicado por la política (por ejemplo, basada en el tiempo, modificación o nuevo recurso solicitado, actividad anómala de sujeto detectada), la cual procura establecer un equilibrio entre la seguridad, la disponibilidad, la usabilidad y la rentabilidad. 7. La empresa recopila toda la información posible sobre el estado actual de los activos, la infraestructura de la red y las comunicaciones, y la utiliza para mejorar la postura de seguridad. Una empresa debe reunir y procesar los datos sobre la postura de seguridad de sus bienes, el tráfico de red y las solicitudes de acceso. Además, tomará cualquier información obtenida para mejorar la creación y la aplicación de las políticas. Estos datos también servirán como contexto para las solicitudes de acceso de los sujetos (consultar la sección 3.3.1). | [
0.022867287,
0.05811036,
0.05020102,
0.02322786,
0.037243668,
-0.0077406815,
-0.014899794,
0.04747928,
-0.033568155,
0.026217123,
-0.0072754263,
0.009287654,
0.008037281,
-0.023041757,
-0.0035068602,
0.0036057269,
-0.011067255,
0.0051265294,
-0.024449155,
-0.0044170152,
-0.00... | 82 |
According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:
There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. | [
-0.0057982365,
-0.00015926437,
0.054595124,
-0.00024796117,
0.014559532,
-0.009818639,
0.010816721,
0.042717937,
-0.015457805,
-0.011577759,
-0.011215954,
0.0002906526,
-0.022768762,
0.0036086927,
-0.028420404,
-0.003755286,
0.0039455458,
-0.03972369,
-0.004825106,
0.02572558,
... | 83 |
According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:
SP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. | [
-0.010951821,
0.0129095595,
0.05177643,
0.017239617,
0.015754038,
-0.0012358226,
0.014533332,
-0.0006996037,
-0.0073472783,
0.016571682,
0.003126624,
0.0067369244,
-0.04240232,
0.034364074,
-0.009132275,
-0.04260961,
0.039868776,
0.0043444526,
0.0096217105,
0.00882134,
-0.005... | 84 |
According to Security and Privacy Controls for Information Systems and Organizations:
............................................................. 16
3.1 ACCESS CONTROL ..................................................................................................................
18
3.2 AWARENESS AND TRAINING ................................................................................................... 59
3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65
3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83
3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96
3.6 CONTINGENCY PLANNING .................................................................................................... 115
3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131
3.8 INCIDENT RESPONSE ............................................................................................................ 149
3.9 MAINTENANCE .................................................................................................................... 162
3.10 MEDIA PROTECTION .......................................................................................................... 171
3.11 PHYSICAL AND ENVIRONMENTAL PROTECTION .................................................................... 179
3.12 PLANNING ........................................................................................................................ 194
3.13 PROGRAM MANAGEMENT ................................................................................................. 203
3.14 PERSONNEL SECURITY ........................................................................................................ 222
3.15 PERSONALLY IDENTIFIABLE INFORMATION PROCESSING AND TRANSPARENCY ....................... | [
-0.003994667,
0.032690182,
0.06019809,
0.00016307058,
0.03098893,
0.0017863129,
0.01858289,
0.015730023,
-0.010443061,
0.023581948,
0.04768736,
-0.013976427,
0.019760678,
-0.0031538566,
0.019734506,
-0.026317036,
0.02160588,
0.033946488,
0.024000717,
0.024118496,
0.0160441,
... | 85 |
According to Security and Privacy Controls for Information Systems and Organizations:
CHAPTER ONE INTRODUCTION ...................................................................................................... 1
1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2
1.2 TARGET AUDIENCE .................................................................................................................. 3
1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3
1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5
1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5
1.6 PUBLICATION ORGANIZATION .................................................................................................. 5
CHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7
2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7
2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8
2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11
2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13
2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14
CHAPTER THREE THE CONTROLS ................................................................................................. 16
3.1 ACCESS CONTROL .................................................................................................................. | [
-0.0026053197,
0.001176266,
0.04933011,
0.013922314,
0.035629902,
-0.0145652415,
-0.013910624,
0.018679982,
-0.036471553,
0.025202777,
0.016575852,
-0.041124012,
0.014156106,
-0.012367597,
0.013314455,
-0.016529094,
0.047506534,
0.041357804,
0.025226157,
0.036985897,
0.033782... | 86 |
According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:
| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |
|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |
| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |
| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |
| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |
| 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | [
0.02862907,
0.007844837,
0.05521508,
-0.015349164,
0.042825736,
0.0015871389,
-0.024582235,
0.011682128,
-0.052229065,
0.017352937,
0.016265923,
0.0012130685,
-0.011708321,
0.02415005,
0.024647718,
-0.014615756,
0.032950934,
0.013856156,
-0.026009759,
0.02345593,
0.028105209,... | 87 |
According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:
| Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 |
|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Introduction ...................................................................................................................... | Introduction ...................................................................................................................... | 2 |
| | Background - Zero Trust Principles and Zero Trust Architecture................................ | [
0.0023762074,
0.008735113,
0.04566983,
0.022240136,
0.06293014,
-0.029389165,
-0.04359393,
0.024817519,
-0.019371193,
0.023651281,
-0.035826795,
-0.029179243,
0.0069274465,
-0.004906941,
-0.029482465,
-0.0049011097,
0.009125803,
-0.007889592,
0.005280137,
0.045040064,
0.02428... | 88 |
Romine Thomas Michelli Director, Information Technology Laboratory Chair-Defense Community Donna Dodson Susan Dorr-Intelligence Community Co-Chair Cybersecurity Advisor, Information Technology Laboratory Matt Scholl Vicki Michetti Tri-Chair-Defense Community Chief, Computer Security Division Kevin Stine Chris Johnson Chief, Applied Cybersecurity Division Tri-Chair-Intelligence Community Ron Ross Paul Cunningham FISMA Implementation Project Leader Tri-Chair-Civil Agencies ## Joint Task Force Working Group | Ron Ross | Kevin Dulany | Peter Duspiva | Kelley Dempsey | |--------------------|----------------------------------|------------------------------------|----------------------| | NIST, JTF Leader | DoD | Intelligence Community | NIST | | Taylor Roberts OMB | Ellen Nadeau NIST | Victoria Pillitteri NIST | Naomi Lefkovitz NIST | | Jordan Burris OMB | Charles Cutshall OMB | Kevin Herms OMB | Carol Bales OMB | | Jeff Marron NIST | Kaitlin Boeckl NIST | Kirsten Moncada OMB | Jon Boyens NIST | | Dorian Pappas CNSS | Dominic Cussatt Veterans Affairs | Esten Porter The MITRE Corporation | Celia Paulsen NIST | | | Christina Sames | Julie Snyder | Martin Stanley | | Daniel Faigin | | | | | The Aerospace | The MITRE Corporation | The MITRE | Homeland Security | | Corporation | | Corporation | | \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ The authors also wish to recognize Matt | [
-0.010415895,
0.00724584,
0.06040087,
-0.018425945,
0.017732495,
0.00018364472,
0.0028569414,
0.044267554,
-0.01152683,
-0.008010049,
0.034191307,
0.020817637,
0.043220304,
0.0065736184,
0.009984258,
0.023251787,
-0.02626617,
-0.019826995,
-0.010826304,
0.025799153,
0.0063047... | 89 |
According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:
| Access Control | Maintenance | Security Assessment and Monitoring |
|-----------------------------------|---------------------|--------------------------------------|
| Awareness and Training | Media Protection | System and Communications Protection |
| Audit and Accountability | Personnel Security | System and Information Integrity |
| Configuration Management | Physical Protection | Planning |
| Identification and Authentication | Risk Assessment | System and Services Acquisition |
| Incident Response | | Supply Chain Risk Management |
| Identify the role(s) responsible for security and provide the necessary resources. | Whether it is just one person or multiple people within the business, ensure roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk. | [
-0.007580421,
0.025086107,
0.074637994,
0.012865624,
0.015545446,
-0.007791333,
0.0029775794,
0.026723776,
0.007890586,
0.014937524,
0.050643664,
0.004075562,
0.0066933506,
-0.00088939676,
0.024006734,
-0.015706731,
-0.040768027,
0.026847841,
-0.014093876,
0.028758455,
0.0377... | 90 |
According to Assessing Security and Privacy Controls in Information Systems and Organizations:
NTROL ASSESSMENTS ..................................................... 30
3.4 ANALYZE ASSESSMENT REPORT RESULTS .....................................................................................
32
3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34
CHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37
4.1 ACCESS CONTROL............................................................................................................................ 40
4.2 AWARENESS AND TRAINING ........................................................................................................ 118
4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128
4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160
4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177
4.6 CONTINGENCY PLANNING ............................................................................................................ 215
4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243
4.8 INCIDENT RESPONSE ............................................................................................................... 275
4.9 MAINTENANCE ........................................................................................................................ 298
4.10 MEDIA PROTECTION .............................................................................................................. 316
4.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ....................................................................... | [
-0.0012396731,
0.04641093,
0.052470874,
0.017048167,
0.02239017,
0.015174207,
0.013056876,
0.0015378031,
-0.004800501,
0.022998597,
0.03506982,
-0.029472278,
0.034437053,
-0.0009970622,
-0.001514987,
-0.042151928,
0.012886516,
0.040570013,
0.021806078,
0.018192014,
0.02319329... | 91 |
According to Assessing Security Requirements for Controlled Unclassified Information:
blication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations.
- System development life cycle responsibilities (e.g., program managers, mission/business owners, information owners/stewards, system designers and developers, system/security engineers, systems integrators)
- Acquisition or procurement responsibilities (e.g., contracting officers)
- System, security, or risk management and oversight responsibilities (e.g., authorizing officials, chief information officers, chief information security officers, system owners, information security managers)
- Security assessment and monitoring responsibilities (e.g., auditors, system evaluators, assessors, independent verifiers/validators, analysts) | [
-0.0005125435,
0.0063250046,
0.0818574,
-0.03641707,
0.008886164,
-0.012724788,
0.01086156,
-0.0012977165,
-0.017597847,
0.0037233403,
0.042773236,
-0.018669669,
0.011827447,
-0.021461396,
0.02062637,
-0.037289485,
-0.0025580437,
0.015528977,
-0.04820713,
0.028789677,
0.02642... | 92 |
According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:
- Sidecar - Beside each application instance to intercept all traffic into and out of the application and handles east-west internal communication between services in the infrastructure. This is the primary use case of the service mesh.
- Ingress gateway - Controls how applications in the cluster are exposed outside (e.g., managing what names, certificates, ports, protocols, and application endpoints are served to the world outside of the cluster). Think of this as the service mesh control plane that manages a traditional reverse proxy similar to Spring Cloud Gateway, NGINX, or HAProxy.
- Egress gateway - Controls how applications in the cluster communicate with the outside world. This can be used for traditional egress filtering and logging, like a Squid proxy, but can also implement an identity-based policy for what is allowed to call out and perform credential exchange , or present a set of credentials (e.g., an mTLS certificate for a partner API), on behalf of the application so that the application does not need to handle them (e.g., communicating via mTLS with the partner API). Think of this as a nextgeneration identity-aware Squid proxy.
- Edge gateway - Accepts external traffic before the ingress gateway and performs finegrained load balancing across clusters or sites. It is used to terminate external traffic, enable infrastructure-level failover, deploy blue-green clusters, and facilitate ingressgateway-per-team deployments without requiring each of those teams to have publicly routable ingress gateways. Think of this as a modern software-based local traffic manager, like F5, that can apply policy per-request rather than per-connection. | [
-0.01393048,
0.0028824303,
0.07094091,
0.019692302,
0.039870832,
-0.037974536,
-0.058833793,
0.019011581,
0.00075859425,
0.011329152,
0.013626587,
-0.0124353245,
0.0011601136,
-0.014343776,
-0.0616053,
-0.010855078,
-0.007117187,
0.008849381,
-0.02155213,
0.050178904,
0.02209... | 93 |
According to Zero Trust Architecture:
CDM System (sistema CDM). Industry Compliance (cumplimiento de la industria). Threat Intelligence (inteligencia sobre amenazas). Activity Logs (registros de actividades). Control Plane (plano de control). Policy Engine (motor de políticas). Policy Administrator (administrador de políticas). Policy Decision Point (punto de decisión de políticas). Data plane (plano de datos). Subject (sujeto). System (sistema). Untrusted (no confiable). Policy Enforcement Point (punto de aplicación de políticas). Trusted (confiable). Enterprise Resource (recurso de la empresa). Date Access Policy (política de acceso a los datos). PKI, public key infrastructure (infraestructura de clave pública). ID Management (gestión de identidades). SIEM System (sistemas de seguridad de la información y gestión de eventos).
Access Request (solicitud de acceso). Subject Database and History (datos e historial del sujeto). Asset Database (datos del activo). Resource Policy Requirements (requerimientos de la política de recursos). Threat Intelligence and Logs (inteligencia de amenazas y registros). Trust Algorithm (algoritmo de confianza). | [
0.016921269,
0.027687082,
0.059411347,
0.0068283174,
0.015413556,
0.003856504,
-0.037555747,
0.024771342,
-0.01870311,
0.024995629,
0.028459629,
-0.017058333,
0.024958247,
-0.02154409,
0.008205195,
0.013257901,
-0.03396714,
0.01698357,
0.0072644325,
0.029954882,
0.033369042,
... | 94 |
According to Assessing Security Requirements for Controlled Unclassified Information:
| Access Control | Maintenance | Security Assessment and Monitoring |
|-----------------------------------|---------------------|--------------------------------------|
| Awareness and Training | Media Protection | System and Communications Protection |
| Audit and Accountability | Personnel Security | System and Information Integrity |
| Configuration Management | Physical Protection | Planning |
| Identification and Authentication | Risk Assessment | System and Services Acquisition |
| Incident Response | | Supply Chain Risk Management |
A.03.01.10.b: the device lock is retained until the user reestablishes access using established identification and authentication procedures.
[SELECT FROM: access control policy and procedures; procedures for session lock and identification and authentication; system design documentation; system configuration settings; display screen with session lock activated; system security plan; other relevant documents or records] | [
0.021735502,
0.082242444,
0.028384322,
-0.008023978,
0.04331079,
0.030440385,
0.011688841,
0.014539288,
0.03305719,
-0.025700763,
0.042483028,
0.003075747,
0.017943805,
0.005370458,
0.008003952,
-0.038771436,
-0.03025347,
0.020453801,
-0.04750302,
0.028010493,
0.027503153,
... | 95 |
scribed in a similar manner to those of Appendix F (Security Controls) and Appendix G (Information Security Programs Organization-Wide Information Security Program Management Controls). SP 800-53 Rev.
4 reminds readers to view the privacy controls in Appendix J from the same perspective as the Program Management controls in Appendix G-that is, the controls are implemented for each organizational information system irrespective of the FIPS 199 categorization for that system. Appendix J defines controls, control enhancements, guidance, and references for the following new families:
- Authority and Purpose (AP);
- Accountability, Audit, and Risk Management (AR);
- Data Quality and Integrity (DI);
- Data Minimization and Retention (DM);
- Individual Participation and Redress (IP);
- Security (SE);
- Transparency (TR); and,
- Use Limitation (UL). The use of these standardized privacy controls will provide a more disciplined and structured approach for satisfying federal privacy requirements and demonstrating compliance with those requirements. Organizations should decide when to apply control enhancements to support their particular missions and business functions. Specific overlays for privacy can also be considered to facilitate the tailoring of the security control baselines in Appendix D with the requisite privacy controls to ensure that both security and privacy requirements can be satisfied by organizations. | [
-0.0006034462,
0.017487327,
0.046980098,
0.0036947348,
-0.011530177,
-0.0017838896,
0.004091878,
0.0055307085,
0.014609665,
0.007669423,
0.0084702205,
-0.004186281,
0.008626473,
0.034427766,
0.010149941,
-0.023281712,
0.06817844,
0.006058063,
0.030859986,
0.019661848,
0.03346... | 96 |
According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:
3.1.6. 3.1.6. | [
-0.0050110924,
0.018847138,
0.05055526,
-0.000022684335,
0.060330592,
-0.01827938,
-0.0040452844,
0.012972064,
-0.033349685,
0.026339091,
0.0016353935,
-0.00051877456,
-0.0052764583,
-0.025117176,
0.007886916,
-0.0042551085,
0.045445424,
-0.01095405,
-0.043445926,
0.0022432662,... | 97 |
rses, and awareness posters. The resources will likely need to be customized to meet your own unique business needs, but they offer a starting point. Resources can be found in the resources box below.
## Related Resources:
- View all SP 800-171 Awareness and Training Requirements and Assessment Procedures
- NIST Free and Low-Cost Online Cybersecurity Learning Content
ht ps:/
csrc.nist.gov/projects/protecting-control ed-unclas ified-information
- NARA CUI training
- Center for Development of Security Excellence Security Awareness Hub
81&/$66,),('GLYPH<c=3,font=/BCDOEE+Wingdings-Regular>,1)250$7,21GLYPH<c=3,font=/BCDOEE+Wingdings-Regular>,1
<!-- image -->
## Getting Started with Audit and Accountability
## Family: Audit and Accountability
Description: Creating, protecting, and retaining system audit records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful, unauthorized, or inappropriate system activity; and ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. ## Getting Started with Audit and Accountability
<!-- image -->
Understand and track who is performing actions within business system(s), what those actions are, and when those actions are taken. Having the ability to review system activity and analyze records, generate reports, resolve audit log process failures, and protect audit data gives the business insight into potential unauthorized activity and improves the ability to respond quickly and appropriately. Consider automated tools for conducting audit and logging activities. Products range from free, open-source tools to commercially available ones. ## Define, maintain, and protect audit record content. - Ask internal information security staff, or your security vendor, what audit log information, if any, the system currently captures and how it is protected and maintained. | [
-0.028131064,
0.042316332,
0.062826514,
-0.00005381545,
0.006053743,
-0.022778131,
0.008599907,
0.03620272,
0.036850706,
0.03417424,
0.05648751,
-0.030539881,
0.00833226,
-0.022735871,
0.04482376,
-0.0042506503,
-0.004211912,
0.030877963,
-0.030004589,
0.043358743,
0.02608849... | 98 |
According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:
ent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.
Examples of CUI include:
<!-- image -->
| | When provided as part of a government contract, examples include: | Marking 1 |
|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |
| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |
| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |
1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui. | [
-0.008680649,
0.0029951967,
0.045077033,
0.015640076,
0.018513298,
-0.011296364,
-0.0037812663,
0.022660492,
-0.04431807,
0.012116316,
0.049088698,
0.02134586,
3.2426433e-7,
-0.0222268,
0.016697206,
-0.0052890293,
-0.01431189,
-0.008253732,
-0.031876482,
0.012814292,
0.047760... | 99 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.