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.05.03Multi-factor authenticationITSP.10.171Identification and authentication

Official Requirement

Implement strong multi-factor authentication (MFA) for access to privileged and non-privileged accounts.

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

In Plain English

All accounts -- both admin and regular user -- must use multi-factor authentication (MFA). MFA requires at least two different factors: something you know (password), something you have (phone, security key), or something you are (biometric). Phishing-resistant MFA (FIDO2 security keys, passkeys) is strongly preferred.

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

Multi-factor authentication for all accounts

Implementation steps

  1. Deploy an MFA solution integrated with Active Directory and VPN for all user authentication
  2. Require MFA for all remote access (VPN, RDP gateway) and privileged account logons
  3. Extend MFA to local console access for servers and critical systems where feasible
  4. Distribute hardware tokens or enroll authenticator apps for all users; track enrollment completion

Tools / systems

Evidence artifacts

Evidence frequency: Continuous enforcement; monthly MFA coverage reporting