References
14.2.3. Further information on application whitelisting as implemented by Microsoft can be found at:
Reference
Title
Publisher
Using Software Restriction
Policies to Protect Against
Source
Microsoft
http://technet.microsoft.com/enus/library/bb457006.aspx
Microsoft
https://docs.microsoft.com/en-
Unauthorized Software
APPLOCKER
nz/windows/security/threatprotection/applocker/applockeroverview
Implementing Application
ASD
Whitelisting January 2018
http://www.asd.gov.au/publicatio
ns/protect/Application_Whitelisting.p
df
SP 800-167
NIST Special Publication 800-167
- Guide to Application
NIST
Whitelisting
http://nvlpubs.nist.gov/nistpubs/S
pecialPublications/NIST.SP.800167.pdf
Application Whitelisting Using
NSA
Microsoft AppLocker
https://www.iad.gov/iad/library/iaguidance/tech-briefs/applicationwhitelisting-using-microsoftapplocker.cfm
Application Whitelisting
CSE
Explained
https://www.csecst.gc.ca/en/system/files/pdf_docum
ents/itsb95-eng_0.pdf
Guidelines for Application
Whitelisting in Industrial Control
DHS - The Industrial Control Systems
Guidelines for Application
Cyber Emergency Response Team
Whitelisting in Industrial Control
Systems
(ICS-CERT)
Systems
Rationale & Controls
14.2.4.
Application whitelisting
14.2.4.R.01.
Rationale
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.
14.2.4.R.02.
Rationale
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.
14.2.4.R.03.
Rationale
Application whitelisting is considered only one part of a defence-in-depth strategy in order to prevent a successful attack, or to help mitigate
consequences arising from an attack.
14.2.4.C.01.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1234]
Agencies SHOULD implement application whitelisting as part of the SOE for workstations, servers and any other network device.
14.2.5.
System user permissions
14.2.5.R.01.
Rationale
An average system user requires access to only a few applications, or groups of applications, in order to conduct their work. Restricting the
system user’s permissions to execute code to this limited set of applications reduces the attack surface of the system.
14.2.5.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1242]
Agencies MUST ensure that a system user cannot disable the application whitelisting mechanism.
14.2.5.C.02.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1246]
Agencies SHOULD prevent a system user from running arbitrary executables.
14.2.5.C.03.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:896]
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.
14.2.5.C.04.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:898]
Agencies SHOULD ensure that application whitelisting does not replace the antivirus and anti-malware software within a system.
14.2.6.
System administrator permissions
14.2.6.R.01.
190
Rationale
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents