Policy principles
- Least privilege: access granted is the minimum required for the role
- Role-based provisioning from defined templates; copying another user's access is prohibited
- Segregation of duties enforced for conflicting functions
Access control policies state least privilege and then leave the mechanics unspecified, which is where it breaks down. This one fixes the approval route, the review cadence, and the privileged-access rules explicitly.
Define who approves what, in a table. The common failure is that nobody knows whether access to a given system needs a manager, the system owner, or security. A matrix removes the ambiguity and speeds up legitimate requests.
Make role-based provisioning the default. State that access is granted from role templates, and that copying another user's permissions is prohibited. That one rule prevents most permission creep.
Set review cadence by sensitivity. Quarterly for privileged and sensitive systems, annually for the rest. A single cadence across everything produces rubber-stamping on the reviews that matter.
Here's a preview. Unlock the free download to get all 3 sections (2 more below).
More free templates IT teams use alongside this one.
An access review where every manager clicks approve is worse than no review, because it manufactures evidence that access was checked. This template is built to produce the two things auditors actually test: a named reviewer who attested, and proof that the revocations they asked for happened.
Remote access is how most intrusions begin, and the policies covering it usually address employees while leaving vendor and contractor access to informal arrangements. This one treats third-party access as a first-class case.
The information security policy is the parent document auditors ask for first. Its job is not to contain every control. It is to state the organisation's position, assign responsibility, and point to the specific policies that implement it.
Least privilege and role-based provisioning principles, an approval matrix mapping access types to approvers, segregation of duties requirements, privileged access rules including break-glass handling, revocation timelines, and review cadence by sensitivity.
Granting elevated rights only for a limited window when needed, rather than holding them permanently. It reduces the value of a compromised account, because most of the time the account has no elevated privilege to steal.
Stored in a sealed vault, excluded from normal conditional access so they work when the identity provider is impaired, alerting on any use, credentials rotated immediately afterwards, and every use reviewed. They exist for the scenario where everything else has failed.