Glossary of Compliance

Compliance Glossary

Our list of curated compliance glossary offers everything you to know about compliance in one place.

Glossary » NIST » NIST 800-172

NIST 800-172

NIST Special Publication 800-172 Enhanced Security Requirements for Protecting Controlled Unclassified Information (CUI) in Nonfederal Systems and Organizations is an extension of the existing NIST SP 800-171. Current version specifically focus on sensitive but unclassified information dealt by organizations on behalf of the federal government and puts forward additional security requirements and practices pertaining to it.

Main features of NIST 800-172 are:

  1. Additional Requirements for Safety: The book offers better controls that are grouped into 14 categories of controls:
  • Access Control
  • Awareness and Training
  • Audit and Accountability
  • Configuration Management
  • Identification and Authentication
  • Incident Response
  • Maintenance
  • Media Protection
  • Personnel Security
  • Physical Protection
  • Risk Assessment
  • Security Assessment
  • System and Communications Protection
  • System and Information Integrity
  1. Proactive Controls: Under NIST 800-172, proactive control includes threat hunting, encryption as well as continuous monitoring all of which will provide a workaround for future risks.
  2. Implementation Guidance: Publication details customised security requirements based on the varying risk levels of CUI. In that case, it also leaves room for adoption.

NIST SP 800-172 aims at assisting in bolstering the non-federal systems’ cybersecurity posture. In this case, the developed publication applies to sectors of critical infrastructure where preventing unauthorized access and disclosure as well as other advanced persistent threats is crucial.

Additional reading

How long did your initial SOC 2 Type 2 implementation take before attestation?

The initial SOC 2 Type 2 implementation typically takes 4 to 12 months before reaching attestation, depending on factors like organizational readiness, scope, existing controls, and available resources. Smaller startups with simpler environments and automated tools may complete it closer to the 4-month mark, while mid-size or enterprise companies with complex systems might take up…

9 Common Compliance Issues and How to Overcome Them

TL;DR Top compliance issues include inconsistent processes, lack of awareness, or vendor non-compliance, leading to costly penalties and eroding trust. A good compliance program hinges on empowering your team and using the right tools. The most successful companies don’t wait for compliance gaps to expose them. Instead, they focus on forward-thinking strategies like internal audits,…

How the Unified Compliance Framework solves framework commonalities?

TL, DR: The Unified Compliance Framework is the most comprehensive library of compliance documents that is integrated into a unified set of controls The UCF’s key components include Common Control Hub, Authority documents, UCF mapping, Compliance dictionary, UCF Research and Integration capabilities The Secure Controls Framework is different from UCF in essence that it is…

Sprinto: Your growth superpower

Use Sprinto to centralize security compliance management – so nothing
gets in the way of your moving up and winning big.