Free compliance framework explorer — browse controls, evidence, and implementation guidance.Subscribe for updates →
SOC 247
ITSP.10.17198
ISO 42001soon
ISO 27001soon

Browse

98 controls

03.04.08Authorized software - allow by exceptionITSP.10.171Configuration management

Official Requirement

A. Identify software programs authorized to execute on the system. B. Implement a deny-all, allow-by-exception policy for the execution of software programs on the system. C. Review and update the list of authorized software programs [Assignment: organization-defined frequency].

Source: Canadian Centre for Cyber Security ITSP.10.171 (2025), adapted from NIST SP 800-171 Rev. 3

In Plain English

Rather than trying to block known-bad software, implement an allowlist approach: only explicitly authorized software can run. Everything else is blocked by default. Maintain the approved software list and review it periodically. This is far more effective against malware and unauthorized software.

Help us build what matters.

Vote for the next framework, subscribe for updates, and let us know if you'd contribute.

The Trust Services Criteria referenced in this tool are published by the American Institute of Certified Public Accountants (AICPA) and incorporate principles from the Committee of Sponsoring Organizations of the Treadway Commission (COSO). Criteria descriptions are reproduced for reference purposes. All implementation guidance, evidence recommendations, and control language are original work by Truvo Cyber. ISO 27001 and ISO 42001 are standards published by the International Organization for Standardization (ISO). Framework and standard names are the property of their respective owners. This tool is not affiliated with, endorsed by, or certified by AICPA, COSO, or ISO.

© 2026 Truvo Cyber. All rights reserved.

On-premises implementation and evidence

Application allowlisting

Implementation steps

  1. Deploy application allowlisting using AppLocker or Windows Defender Application Control (WDAC) on all Windows systems
  2. Create policies based on publisher certificates, file hashes, or path rules to allow only authorized executables
  3. Test allowlisting policies in audit mode before switching to enforcement to identify missing authorized applications
  4. Maintain the approved software list and review quarterly; process requests for new software through a formal approval workflow

Tools / systems

Evidence artifacts

Evidence frequency: Continuous enforcement; quarterly software list review