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.02Configuration settingsITSP.10.171Configuration management

Official Requirement

A. Establish, document, and implement the following configuration settings for the system that reflect the most restrictive mode consistent with operational requirements: [Assignment: organization-defined configuration settings]. B. Identify, document, and approve any deviations from established configuration settings.

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

In Plain English

All system components must be configured to the most restrictive (hardened) settings that still allow the system to function. Use industry-standard benchmarks (like CIS Benchmarks) as your baseline. Any deviation from the hardened configuration must be documented with a business justification and formally approved.

Cross-framework mappings:ISO 42001 · coming soonISO 27001 · coming soon
View in Map →

Help us build what matters.

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

Truvo CyberTruvo CyberBuilt and maintained by Truvo Cyber
Authors·Connect with us
Updated: Mar 22, 2026Reviewed: Mar 22, 2026v1.0.0
Share this tool

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

Security hardening configuration settings

Implementation steps

  1. Apply CIS Benchmarks or DISA STIGs as the hardening standard for all operating systems, databases, and network devices
  2. Use Group Policy (Windows) or configuration management tools (Ansible, Puppet) to enforce hardened settings
  3. Scan systems periodically with configuration assessment tools (CIS-CAT, Nessus compliance scans) and remediate findings
  4. Maintain a deviation register documenting approved exceptions with justification and compensating controls

Tools / systems

Evidence artifacts

Evidence frequency: Quarterly compliance scans; annual hardening standard review