United States

NIST SP 800-167 Guide to Application Whitelisting

25 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

25 controls 0 frameworks share controls with it United States verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
1Purpose, scope and audience0
2.0Overview of application whitelisting technologies0
2.1Aim application whitelisting at managed hosts where users cannot install software0
2.2.1aNever rely on file path, filename or file size as the only attribute0
2.2.1bBase the whitelist on publisher signatures combined with cryptographic hashes, and keep hashes current0
2.2.2Decide which application resources beyond executables are controlled0
2.2.3Generate the whitelist from a clean baseline or vendor data and maintain it through trusted updaters0
2.3Start in audit mode and move to the enforcement mode that fits each monitored entity0
2.4Use the inventory, file integrity monitoring and incident response capabilities the technology provides0
2.5Analyse the operational environment and assess risk before deciding to deploy0
2.6aPrefer whitelisting built into the operating system; otherwise choose centrally managed third-party products0
2.6bTest any prospective product in monitoring mode, including its reaction to software updates0
2.7Weigh bypass resistance, complexity, cost, performance, mission impact, usability and maintenance when evaluating solutions0
3.1aDefine application whitelisting requirements and capture the decisions in policy0
3.1bDocument requirements for the whitelisting technology itself0
3.1cCover every end user device type, with a waiver and risk process for platforms that cannot be whitelisted0
3.2aUse validated cryptography for hashing, signature validation and management traffic, and plan for algorithm change0
3.2bDesign the centrally managed architecture for placement, redundancy, reliability and interoperability0
3.2cChoose trusted publishers, users and updaters carefully0
3.3aPrototype test functionality, management, logging, performance and the security of the implementation0
3.3bScan for malware and secure the host before installing the whitelisting agent0
3.4Deploy gradually, starting with a small number of hosts, and prepare staff and users0
3.5Operate the solution: update whitelists promptly, patch, manage keys, monitor, test and assess0
AAppendix A: Security and compliance mapping0
BAppendix B: Applying application whitelisting to mobile platforms0

Tell me when NIST SP 800-167 Guide to Application Whitelisting files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for NIST SP 800-167 Guide to Application Whitelisting, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition