NIST SP 800-167 Guide to Application Whitelisting
NIST's guide to application whitelisting (application control): where it fits, how to choose attributes and generate and maintain the list, audit and enforcement modes, product evaluation, and the initiation, design, testing, deployment and management of the solution.
NIST SP 800-167 Guide to Application Whitelisting is a compliance framework from United States with 2 domains and 21 controls. The largest domains are Section 2: Application whitelisting technology: threats, types, modes, uses and evaluation – NIST SP 800-167 Guide to Application Whitelisting (11 controls), Section 3: Planning and implementation of application whitelisting – NIST SP 800-167 Guide to Application Whitelisting (10 controls). Every control below carries what it requires and what an assessor expects to see.
Framework summaries on this platform are interpretations grounded in the published source, for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (2)
Section 2: Application whitelisting technology: threats, types, modes, uses and evaluation – NIST SP 800-167 Guide to Application Whitelisting
| Code | Title |
|---|---|
| nist-sp-800-167-guide-to-application-whitelisting::2.1 | Aim application whitelisting at managed hosts where users cannot install software |
| nist-sp-800-167-guide-to-application-whitelisting::2.2.1a | Never rely on file path, filename or file size as the only attribute |
| nist-sp-800-167-guide-to-application-whitelisting::2.2.1b | Base the whitelist on publisher signatures combined with cryptographic hashes, and keep hashes current |
| nist-sp-800-167-guide-to-application-whitelisting::2.2.2 | Decide which application resources beyond executables are controlled |
| nist-sp-800-167-guide-to-application-whitelisting::2.2.3 | Generate the whitelist from a clean baseline or vendor data and maintain it through trusted updaters |
| nist-sp-800-167-guide-to-application-whitelisting::2.3 | Start in audit mode and move to the enforcement mode that fits each monitored entity |
| nist-sp-800-167-guide-to-application-whitelisting::2.4 | Use the inventory, file integrity monitoring and incident response capabilities the technology provides |
| nist-sp-800-167-guide-to-application-whitelisting::2.5 | Analyse the operational environment and assess risk before deciding to deploy |
| nist-sp-800-167-guide-to-application-whitelisting::2.6a | Prefer whitelisting built into the operating system; otherwise choose centrally managed third-party products |
| nist-sp-800-167-guide-to-application-whitelisting::2.6b | Test any prospective product in monitoring mode, including its reaction to software updates |
| nist-sp-800-167-guide-to-application-whitelisting::2.7 | Weigh bypass resistance, complexity, cost, performance, mission impact, usability and maintenance when evaluating solutions |
Section 3: Planning and implementation of application whitelisting – NIST SP 800-167 Guide to Application Whitelisting
| Code | Title |
|---|---|
| nist-sp-800-167-guide-to-application-whitelisting::3.1a | Define application whitelisting requirements and capture the decisions in policy |
| nist-sp-800-167-guide-to-application-whitelisting::3.1b | Document requirements for the whitelisting technology itself |
| nist-sp-800-167-guide-to-application-whitelisting::3.1c | Cover every end user device type, with a waiver and risk process for platforms that cannot be whitelisted |
| nist-sp-800-167-guide-to-application-whitelisting::3.2a | Use validated cryptography for hashing, signature validation and management traffic, and plan for algorithm change |
| nist-sp-800-167-guide-to-application-whitelisting::3.2b | Design the centrally managed architecture for placement, redundancy, reliability and interoperability |
| nist-sp-800-167-guide-to-application-whitelisting::3.2c | Choose trusted publishers, users and updaters carefully |
| nist-sp-800-167-guide-to-application-whitelisting::3.3a | Prototype test functionality, management, logging, performance and the security of the implementation |
| nist-sp-800-167-guide-to-application-whitelisting::3.3b | Scan for malware and secure the host before installing the whitelisting agent |
| nist-sp-800-167-guide-to-application-whitelisting::3.4 | Deploy gradually, starting with a small number of hosts, and prepare staff and users |
| nist-sp-800-167-guide-to-application-whitelisting::3.5 | Operate the solution: update whitelists promptly, patch, manage keys, monitor, test and assess |
What is NIST SP 800-167 Guide to Application Whitelisting and who does it apply to?
NIST SP 800-167 Guide to Application Whitelisting is a compliance framework from United States with 2 domains and 21 controls. NIST's guide to application whitelisting (application control): where it fits, how to choose attributes and generate and maintain the list, audit and enforcement modes, product evaluation, and the initiation, design, testing, deployment and management of the solution. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
What does NIST SP 800-167 Guide to Application Whitelisting actually require?
NIST SP 800-167 Guide to Application Whitelisting has 21 controls organised across 2 domains. The largest domains are Section 2: Application whitelisting technology: threats, types, modes, uses and evaluation – NIST SP 800-167 Guide to Application Whitelisting (11 controls), Section 3: Planning and implementation of application whitelisting – NIST SP 800-167 Guide to Application Whitelisting (10 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of NIST SP 800-167 Guide to Application Whitelisting do I already cover?
NIST SP 800-167 Guide to Application Whitelisting does not currently have cross-framework mappings in our system. Check back as we continuously expand our mapping database.
How do I implement NIST SP 800-167 Guide to Application Whitelisting?
Start your NIST SP 800-167 Guide to Application Whitelisting compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about NIST SP 800-167 Guide to Application Whitelisting requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 21 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 1,248 frameworks.
Get Started Free →Free forever, no credit card required