17.2. Application Whitelisting Objective Mandatory Control 01: Recommended Control 01: Recommended Control 02: Recommended Control 03: Recommended Control 04: Recommended Control 05: Recommended Control 06: Recommended Control 07: Recommended Control 08: Recommended Control 09: Recommended Control 10: Recommended Control 11: Only approved applications are used on operating systems Agencies must ensure that a system user cannot disable the application whitelisting mechanism Agencies should implement application whitelisting as part of the SOE for workstations, servers and any other network device Agencies should prevent a system user from running arbitrary executables Agencies should restrict a system user’s rights in order to permit them to only execute a specific set of predefined executables as required for them to complete their duties Agencies should ensure that application whitelisting does not replace the antivirus software within a system Agencies should ensure that system administrators are not automatically exempt from application whitelisting policy Agencies should ensure that the default policy is to deny the execution of software Agencies should ensure that application whitelisting is used in addition to a strong access control list model and the use of limited privilege accounts Agencies should plan and test application whitelisting mechanisms and processes thoroughly prior to implementation Agencies should restrict the decision whether to run an executable based on the following, in the order of preference shown: validates cryptographic hash executable absolute path digital signature parent folder Agencies should restrict the process creation permissions of any executables which are permitted to run by the application whitelisting controls Logs from the application whitelisting implementation should include all relevant information Application whitelisting can be an effective mechanism to prevent the successful compromise of an agency system resulting from the exploitation of a vulnerability in an application or the execution of malicious code. Defining a list of trusted executables, a whitelist, is a practical and secure method of securing a system rather than relying on a list of bad executables (black list) to be prevented from running. Application whitelisting is considered a part of a defense‐in‐depth strategy in order to prevent a successful attack, or to help mitigate consequences arising from an attack. 74

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents