NIST SP 800-167 Guide to Application Whitelisting
Section 3: Planning and implementation of application whitelisting – NIST SP 800-167 Guide to Application Whitelisting

NIST SP 800-167 Guide to Application Whitelisting 3.5: Operate the solution: update whitelists promptly, patch, manage keys, monitor, test and assess

What does 3.5 require?

Ongoing management covers keeping the whitelist current as applications are added or updated, patching the whitelisting software itself after testing, extending it to further platforms, performing key management, adapting policy as requirements change, watching the components for operational and security problems, periodically testing that whitelisting still works, and running regular vulnerability assessments. Administrators stay ready to make quick manual whitelist changes to counter emerging threats and correct false positives and negatives, and greylists are monitored and their entries moved to the whitelist or blacklist.

Maintained by Gerard Blokdyk

Other controls in Section 3: Planning and implementation of application whitelisting – NIST SP 800-167 Guide to Application Whitelisting

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.