Access Control Policy template (free, plain-language starter)

Free access control policy template for small companies: full text, the controls it supports and the decisions to make. Not legal advice or a certification.

Template · Updated · by the Controlkeep team

In short

How access to systems is requested, approved, reviewed and removed, including admin access. This free starter covers 6 controls and leaves 5 decisions for you; it is original text, not a standard’s wording, and adopting it is not a certification.

How access to systems is requested, approved, reviewed and removed, including admin access. Customers and auditors ask for it in auditors testing joiners, movers and leavers; write it once you have more than a handful of systems.

Starter policies are original templates written by Controlkeep. They are a starting point, not legal advice, and adopting them is not a certification or an audit opinion. Adapt every rule to how your company really works, and have a qualified adviser review policies with legal effect (privacy, employment, contracts).

Controls it supports

RefControlStarter framework
TC-ACC-01Access is granted on request and approvalSOC 2-style common criteria starter
TC-ACC-02Access is reviewedSOC 2-style common criteria starter
TC-ACC-03Leavers lose access promptlySOC 2-style common criteria starter
TC-ACC-04Strong authenticationSOC 2-style common criteria starter
IS-ORG-02Roles and segregation of dutiesISO 27001-style Annex A starter
IS-TEC-02Privileged accessISO 27001-style Annex A starter

Decisions to make before approving

  • [request channel, e.g. a ticket or a message in #access-requests]
  • [3 months]
  • [12 months]
  • [5 working days]
  • [24 hours]

The policy text

Purpose

To make sure that only the right people have access to [Company] systems and data, with no more access than their role needs.

Scope

All systems that store or process company or customer data, including SaaS applications, cloud accounts, servers, databases, code repositories and network devices.

Granting access

  1. Access is requested through [request channel, e.g. a ticket or a message in #access-requests] and approved by the system owner or the person's manager.
  2. Approvals are recorded (who asked, who approved, what access, when).
  3. Access is based on the role. Where possible, use groups or roles rather than individual permissions.
  4. New starters receive access on or after their start date, never before their contract is signed.

Privileged access

  1. Administrative access is limited to the people who need it to do their job, and listed by [Policy Owner].
  2. Admin accounts are separate from everyday accounts where the system allows it.
  3. Multi-factor authentication is required for all administrative access and for any system holding customer data.
  4. Shared admin credentials are not allowed except for break-glass accounts, which are stored in the password manager, used only in emergencies, and reviewed after each use.

Reviews

  1. System owners review who has access to critical systems at least every [3 months], and to other systems at least every [12 months].
  2. Unneeded access found in a review is removed within [5 working days]. Reviews are recorded as evidence.

Changes and leavers

  1. When someone changes role, access they no longer need is removed within [5 working days].
  2. When someone leaves, their accounts are disabled within [24 hours] of their last working day (immediately for dismissals), company devices are returned and shared secrets they knew are rotated.
  3. Contractor access has an end date and is removed when the engagement ends.

Service accounts and keys

Service accounts and API keys have a named owner, the minimum permissions needed, and are rotated when someone with access leaves or when a key may have been exposed.

Exceptions

Exceptions to this policy must be requested in writing, approved by [Policy Owner], recorded with a reason and an end date, and reviewed when they expire.

Enforcement

Breaking this policy may lead to loss of access and to disciplinary action in line with employment contracts and local law. Contractors may have their engagement ended.

Review

[Policy Owner] owns this policy and reviews it at least every [Review Period], and after any major incident or change in how [Company] works. Questions go to [Security Contact].

Adopt it

  1. Copy the policy below, or create it from the starter library in Controlkeep, where [Company], [Policy Owner], [Security Contact] and [Review Period] are filled from a form.
  2. Decide the 5 remaining bracketed items so the rules match how you actually work.
  3. Approve it, ask staff to acknowledge it, and link it to the controls it supports so auditors can follow the trail.

Related: collecting audit evidence, policies help, Password and Authentication Policy, Data Retention and Deletion Policy.

Questions and answers

How often should access be reviewed?

The starter control suggests every 90 days for critical systems; pick a schedule you will actually keep and record each review as evidence.

Does adopting this access control policy make us SOC 2 or ISO 27001 compliant?

No. Policies are one part of a programme; an auditor tests whether you follow them over time. Controlkeep helps you keep the evidence, but it is not a certification or an audit opinion.

Try Controlkeep free

A working control register: owners, evidence, policies and reviews in one place, with exports your auditor can read. The Free plan needs no card; you can export or delete your data any time.