
Policy Guide: Access Control
Access control is the policy most businesses think they already have. Everyone has a login, there is a password, and the important folders have permissions. But ask who decides what access a new hire gets, who approves a change, and when anyone last checked whether people still need what they have, and the answers get vague.
This guide walks through writing an access control policy that is short enough for managers to follow and specific enough to hold up against the frameworks your business answers to.
What the frameworks expect
Most frameworks express the same core idea: people should have access only to what they need to do their jobs, that access should be approved, and it should be reviewed and removed when it is no longer needed.
- NIST Cybersecurity Framework 2.0, PR.AA covers identity management, authentication, and access control, including managing access permissions with least privilege and separation of duties.
- CIS Controls v8.1, Control 5 (Account Management) and Control 6 (Access Control Management) cover keeping an inventory of accounts, disabling dormant accounts, restricting admin privileges, establishing an access granting process, and an access revoking process.
- NIST SP 800-171, family 3.1 (Access Control) begins with 3.1.1, limiting system access to authorized users, and 3.1.2, limiting access to the types of transactions and functions authorized users are permitted to execute. Requirement 3.1.5 calls for least privilege. Manufacturers handling CUI under DFARS 252.204-7012 will recognize these.
- HIPAA requires access control under 45 CFR 164.312(a) and information access management under 164.308(a)(4).
- FTC Safeguards Rule 314.4(c)(1) requires implementing and periodically reviewing access controls to limit users to the customer information they need.
The policy does not need to quote each of these. It needs to commit the business to practices that satisfy all of them.
The parts of a good access control policy
1. Purpose and scope
One paragraph. The policy covers all accounts on company systems, including cloud services, line of business applications, shared drives, and vendor accounts, for employees, contractors, and service providers.
2. Principles
Keep this to a few lines:
- Access is based on job role and need.
- Every person uses their own account. Shared accounts are not allowed except where documented and approved.
- Administrator privileges are separate from everyday accounts.
- Access is approved by the person responsible for the data or system, not just by IT.
3. Roles and owners
This is the section most templates skip and most businesses need. For each important system or data set, name an owner. The owner is a business person, not a technician. The controller owns the accounting system. The practice manager owns the EHR. The F&I director owns lender portals. IT implements what the owner approves.
4. Granting access
Describe the process in steps:
- The hiring manager requests access for a new person based on their role.
- The system owner approves.
- IT creates the account using a role template where possible.
- The request and approval are recorded in a ticket or form.
Role templates make this practical. Define what a typical front desk person, salesperson, or shop supervisor gets, and the manager only needs to request exceptions.
5. Changing access
When someone changes roles, access for the old role should be removed, not just added to. People who have been with a company for years often accumulate access from every job they have held. The policy should say that role changes trigger a review.
6. Removing access
Departures need same day removal for most accounts. We covered that in detail in our post on same day offboarding. The policy should require it and name who is responsible.
7. Privileged access
Administrator accounts deserve their own section:
- Admin rights are granted only to people who need them for their job.
- Admins use a separate account for admin work and a normal account for email and browsing. Removing local admin rights from everyday users is part of this, and our post on removing local admin rights walks through it.
- Admin accounts require MFA.
- The list of admin accounts is reviewed more often than ordinary accounts.
8. Periodic review
Set a review schedule based on risk. Owners of sensitive systems review who has access on a regular cycle, and confirm in writing that each person still needs it. The frameworks generally do not set an exact frequency, so choose one that your business will actually keep, and review high risk systems more often than low risk ones.
9. Vendor and service provider access
Vendors with access to your systems should have named accounts, MFA, and access limited to what they support. Remote access tools should be enabled on demand where possible rather than always on. Our vendor management policy guide covers how to keep that list current.
10. Exceptions
Some things will not fit. A legacy application might only support one shared login. A piece of equipment might require a default account. The policy should allow exceptions with a documented reason, a compensating control, an owner, and a review date.
Writing it so managers can approve it
Managers will not read a policy full of technical terms, and they should not have to. A few tips:
- Use the names of your actual systems.
- Write approvals in terms of roles and data, not permissions and groups.
- Keep the policy to two or three pages, and put the role templates and system owner list in an appendix that can change without rewriting the policy.
- Have the owner or senior leadership sign it, so managers know it carries weight.
Evidence you will want
A policy is only as good as the evidence that it is followed. Keep:
- Access requests and approvals
- The list of system owners
- Role templates
- Review records, signed or acknowledged by the owner
- The list of admin accounts and when it was last reviewed
- Documented exceptions
That evidence is what auditors, assessors, and insurance carriers ask for, and it is what lets you answer confidently when someone asks who has access to what.
Getting started
Begin with the three or four systems that hold your most sensitive data. Name owners, list current users, and ask each owner to confirm or remove access. That first review almost always turns up accounts that should have been disabled long ago, and it gives you a baseline for the policy.
Our NIST framework page explains how CSF 2.0 and SP 800-171 fit together, and the compliance checklist includes the access control items most frameworks look for. If you want help drafting your policy around your own systems, book your free risk review.