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.01Baseline configurationITSP.10.171Configuration management

Official Requirement

A. Develop and maintain under configuration control, a current baseline configuration of the system. B. Review and update the baseline configuration of the system [Assignment: organization-defined frequency] and when system components are installed or modified.

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

In Plain English

Your organization must maintain a documented baseline configuration for all systems -- a known-good reference state that defines the approved software, settings, and patches. The baseline must be version-controlled and updated whenever systems are changed, upgraded, or when required by policy.

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

System baseline configuration management

Implementation steps

  1. Document baseline configurations for each system type (server OS, workstation OS, network device) including software inventory, patch level, and security settings
  2. Use configuration management tools to enforce and monitor compliance with the defined baseline
  3. Maintain baseline documentation in a configuration management database (CMDB) or version-controlled repository
  4. Review and update baselines when OS versions change, patches are applied, or applications are installed/removed

Tools / systems

Evidence artifacts

Evidence frequency: Quarterly baseline review; per-change updates; annual full configuration audit