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.11Information locationITSP.10.171Configuration management

Official Requirement

A. Identify and document the location of specified information and the system components on which the information is processed and stored. B. Document changes to the system or system component location where specified information is processed and stored.

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

In Plain English

You must know exactly where your sensitive data lives -- which systems process it, which databases store it, and which locations host those systems. When data moves to a new location or system, that change must be documented. This is essential for incident response, data protection, and regulatory compliance.

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

Information location tracking

Implementation steps

  1. Conduct a data inventory to identify systems that process or store specified information and their physical locations
  2. Document data locations in a data flow diagram and register, including server names, database instances, file shares, and physical site locations
  3. Update the data location register whenever systems are migrated, data is moved, or new systems are deployed
  4. Review the data location register periodically and after significant infrastructure changes

Tools / systems

Evidence artifacts

Evidence frequency: Per-change updates; quarterly review; annual comprehensive data mapping