A. Establish, rules that describe the responsibilities and expected behaviour for system usage and protecting specified information. B. Provide rules to individuals who require access to the system. C. Receive a documented acknowledgement from individuals indicating that they have read, understand, and agree to abide by the rules of behaviour before authorizing access to specified information and the system. D. Review and update the rules of behaviour [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
Your organization must define rules of behaviour that explain user responsibilities and expected conduct when using systems that process sensitive information. Every user must receive these rules, acknowledge them in writing before getting access, and the rules must be reviewed and updated regularly.
These are typical controls and implementation steps. Your systems and environment may differ.
Typical Control Rules of behaviour management
Implementation Steps
Develop rules of behaviour defining user responsibilities, acceptable use, data handling expectations, and consequences for violations
Distribute rules of behaviour to all individuals requiring system access as part of the onboarding process
Require and collect documented acknowledgement (electronic or physical signature) before granting system access
Review and update rules of behaviour at the defined frequency (e.g., annually) and redistribute for re-acknowledgement when significant changes are made
Tools / Systems
Policy management platform (PolicyTree, PowerDMS, GRC platform)Electronic signature and acknowledgement system (DocuSign, GRC platform)Onboarding workflow with rules of behaviour gateAcknowledgement tracking and compliance reporting
Typical Control Rules of behaviour management
Evidence Artifacts
Rules of behaviour document with current effective date
Signed acknowledgement records for all system users
Rules of behaviour review and update records with revision history
📅Per-event acknowledgement at onboarding; annual review and update; re-acknowledgement upon significant changes
Cross-framework mappings coming in v1.1
When we add ISO 42001 and ISO 27001, you'll see which controls map to this criterion.
ISO
ISO 42001
AI Management Systems
ISO
ISO 27001
Information Security
Mapping data will appear here automatically when the frameworks are published.