Since the consequences of running malicious code as a privileged user are much more severe than an unprivileged user, an application whitelisting implementation should be strictly enforced for system administrators. 14.2.6.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:907] Agencies SHOULD ensure that system administrators are not automatically exempt from application whitelisting policy. 14.2.7. Application whitelisting configuration 14.2.7.R.01. Rationale A decision to execute a routine, application, or other programme should be made based on a validated cryptographic hash as it is more secure than a decision based on the executable’s signature, path or parent folder. 14.2.7.R.02. Rationale In order for application whitelisting to be effective an agency MUST initially gather information on necessary executables and applications in order to ensure that the implementation is fully effective. 14.2.7.R.03. Rationale Different application whitelisting controls, such as restricting execution based on cryptographic hash, filename, pathname or folder, have various advantages and disadvantages. Agencies need to be aware of this when implementing application whitelisting. 14.2.7.R.04. Rationale Application whitelisting based on parent folder or executable path is futile if access control list permissions allow a system user to write to the folders or overwrite permitted executables. 14.2.7.R.05. Rationale Executables may create multiple processes in the course of execution. These may be identified through exanibation of programme specifications, testing ina "sand-boxed" environment before development and logs of any processes spawned or created. 14.2.7.R.06. Rationale Spawned processes may behave in ways that can compromise system security, change security settings and modify access permissions. Clearly this can be undesirable behaviour. 14.2.7.R.07. Rationale Adequate logging information can allow system administrators to further refine the application whitelisting implementation and detect a pattern of deny decisions for a system user. 14.2.7.R.08. Rationale An example of relevant information that could be included in logs for application whitelisting implementations would be decisions to deny execution incorporating information that would present a reviewer with evidence of misuse. 14.2.7.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:934] Agencies SHOULD ensure that the default policy is to deny the execution of software. 14.2.7.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:936] Agencies SHOULD ensure that application whitelisting is used in addition to a strong access control list model and the use of limited privilege accounts. 14.2.7.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:940] Agencies SHOULD plan and test application whitelisting mechanisms and processes thoroughly prior to implementation. 14.2.7.C.04. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:942] Agencies SHOULD restrict the decision whether to run an executable based on the following, in the order of preference shown: 1. validates cryptographic hash; 2. executable absolute path; 3. digital signature; and 4. parent folder. 14.2.7.C.05. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:945] Agencies SHOULD restrict the process creation permissions of any executables which are permitted to run by the application whitelisting controls. 14.2.7.C.06. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:5529] Agencies SHOULD validate executable behaviour, in particular process creation, permission changes and access control modifications through examination, testing, monitoring and restriction of the permissions. 14.2.7.C.07. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:947] Logs from the application whitelisting implementation SHOULD include all relevant information. 14.3. Web Applications Objective 191 Version_3.5__January-2022

Select target paragraph3

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