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.01.06Least privilege - privileged accountsITSP.10.171Access control

Official Requirement

A. Restrict privileged accounts on the system to [Assignment: organization-defined personnel or roles]. B. Require that users (or roles) with privileged accounts use non-privileged accounts when accessing non-security functions or non-security information. C. Require any administrative or superuser actions to be performed from a physical workstation which is dedicated to those specific tasks and isolated from all other functions and networks, especially any form of Internet access.

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

In Plain English

Privileged (admin) accounts must be limited to specific authorized personnel. Admins must use standard accounts for everyday tasks like email and web browsing, and only use their privileged accounts for administrative work. Administrative functions should be performed from a dedicated, hardened workstation that is network-isolated.

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

Privileged account restriction and dedicated admin workstations

Implementation steps

  1. Create separate admin accounts (e.g., adm-username) in Active Directory distinct from standard user accounts; document authorized privileged users
  2. Enforce via Group Policy that admin accounts cannot access email, web browsers, or general productivity applications
  3. Deploy dedicated Privileged Access Workstations (PAWs) on a segmented network with no direct Internet access
  4. Monitor privileged account usage and alert on any logon from non-PAW endpoints

Tools / systems

Evidence artifacts

Evidence frequency: Quarterly privileged account review; annual PAW configuration audit