1 | Purpose, scope and audience | 0 |
2.0 | Overview of application whitelisting technologies | 0 |
2.1 | Aim application whitelisting at managed hosts where users cannot install software | 0 |
2.2.1a | Never rely on file path, filename or file size as the only attribute | 0 |
2.2.1b | Base the whitelist on publisher signatures combined with cryptographic hashes, and keep hashes current | 0 |
2.2.2 | Decide which application resources beyond executables are controlled | 0 |
2.2.3 | Generate the whitelist from a clean baseline or vendor data and maintain it through trusted updaters | 0 |
2.3 | Start in audit mode and move to the enforcement mode that fits each monitored entity | 0 |
2.4 | Use the inventory, file integrity monitoring and incident response capabilities the technology provides | 0 |
2.5 | Analyse the operational environment and assess risk before deciding to deploy | 0 |
2.6a | Prefer whitelisting built into the operating system; otherwise choose centrally managed third-party products | 0 |
2.6b | Test any prospective product in monitoring mode, including its reaction to software updates | 0 |
2.7 | Weigh bypass resistance, complexity, cost, performance, mission impact, usability and maintenance when evaluating solutions | 0 |
3.1a | Define application whitelisting requirements and capture the decisions in policy | 0 |
3.1b | Document requirements for the whitelisting technology itself | 0 |
3.1c | Cover every end user device type, with a waiver and risk process for platforms that cannot be whitelisted | 0 |
3.2a | Use validated cryptography for hashing, signature validation and management traffic, and plan for algorithm change | 0 |
3.2b | Design the centrally managed architecture for placement, redundancy, reliability and interoperability | 0 |
3.2c | Choose trusted publishers, users and updaters carefully | 0 |
3.3a | Prototype test functionality, management, logging, performance and the security of the implementation | 0 |
3.3b | Scan for malware and secure the host before installing the whitelisting agent | 0 |
3.4 | Deploy gradually, starting with a small number of hosts, and prepare staff and users | 0 |
3.5 | Operate the solution: update whitelists promptly, patch, manage keys, monitor, test and assess | 0 |
A | Appendix A: Security and compliance mapping | 0 |
B | Appendix B: Applying application whitelisting to mobile platforms | 0 |