HIPAA access control means systems holding electronic health information let in only the people and software that have been granted access, with a unique ID for every user and a way to reach the data in an emergency. ISO 27001 access control asks for documented rules on access, managed identities and authentication, regular review of access rights, and tight control of privileged access. Neither one names a product. Neither requires single sign-on.
This post explains what each asks for, in plain language, and how a small team can meet the common core. It is not legal or compliance advice. Your auditor, assessor or counsel decides whether what you do is enough for your organization, and their view beats anything written here.
HIPAA's access control requirement
HIPAA's Security Rule applies to covered entities (health plans, health care clearinghouses, and health care providers that conduct certain transactions electronically) and their business associates, for electronic protected health information (ePHI). Its technical safeguards are in 45 CFR 164.312. The access control standard, 164.312(a)(1), asks you to implement technical policies and procedures so that only people or software programs granted access rights can use systems that hold ePHI.
It comes with four implementation specifications, two required and two "addressable":
| Specification | Status | In plain words |
|---|---|---|
| Unique user identification | Required | Every user has their own name or number, so activity can be traced to a person |
| Emergency access procedure | Required | A way to get at necessary ePHI during an emergency |
| Automatic logoff | Addressable | Sessions end after a set period of inactivity |
| Encryption and decryption | Addressable | A mechanism to encrypt and decrypt ePHI |
"Addressable" does not mean optional. Under 164.306(d)(3), you assess whether the specification is reasonable and appropriate for you; if it is, you implement it, and if not, you document why and implement an equivalent alternative where reasonable.
The access control standard points to the administrative safeguards in 164.308, which is where most of the day-to-day work lives.
Workforce security, 164.308(a)(3). Workforce members get appropriate access to ePHI, and those who should not have it do not. Its addressable specifications cover authorization and supervision, workforce clearance, and termination procedures: ending access when employment, or another arrangement such as a contract, ends.
Information access management, 164.308(a)(4). Policies for authorizing access, and for establishing, documenting, reviewing and modifying each user's access. In small-company terms, that is onboarding, role changes and the periodic review, written down.
Information system activity review, 164.308(a)(1)(ii)(D). Required: regularly review records such as audit logs, access reports and security incident tracking reports.
Log-in monitoring and password management, 164.308(a)(5). Both are addressable specifications under security awareness and training: monitoring log-in attempts and reporting discrepancies, and procedures for creating, changing and safeguarding passwords.
Two more technical standards sit next to access control. Audit controls, 164.312(b), are mechanisms that record and examine activity in systems with ePHI. Person or entity authentication, 164.312(d), means procedures to verify that whoever seeks access is who they claim to be.
The parts small teams miss
Three requirements outside the access control section shape it more than people expect.
Someone has to own it. 164.308(a)(2) requires you to identify the security official responsible for the policies and procedures. In a 10-person practice or startup, that is usually the operations lead. Name them in writing.
The risk analysis comes first. 164.308(a)(1)(ii)(A) makes an accurate and thorough risk analysis required. It is also where your addressable decisions come from: whether automatic logoff is reasonable on a given system is a conclusion of that analysis, and the analysis is what you show when someone asks why.
Emergency access is a plan, not a password in a drawer. The emergency access procedure in 164.312(a) sits alongside the contingency plan standard in 164.308(a)(7), which includes a required emergency mode operation plan. For a small team, that means knowing in advance how you reach necessary ePHI if your usual admin is unreachable or a system is down, and writing it down.
Does HIPAA require SSO? No. The rule is deliberately technology-neutral: 164.306(b) lets you use any security measures that reasonably and appropriately implement the standards, taking into account your size, complexity, capabilities, technical infrastructure, costs, and the probability and criticality of risks. SSO can help you meet unique identification and authentication, but so can individual accounts with strong passwords and MFA in each system. SSO vs MFA covers the difference.
A note on timing. In January 2025 HHS published a proposed rule to strengthen the Security Rule. A proposal is not law. As we read the official eCFR text on 27 October 2026, section 164.312 was last amended in 2013, and we found no final rule in the Federal Register. Check the status before you plan around either version. HHS's Office for Civil Rights, which enforces HIPAA, publishes guidance on its Security Rule pages.
ISO 27001's access control controls
ISO/IEC 27001:2022, the current edition according to ISO's page (published October 2022, with one amendment in 2024 on climate action changes), is a standard for an information security management system. Its clauses set requirements for how you run security: scope, risk assessment, risk treatment, internal audit, management review. Its Annex A is a reference list of controls. You choose which apply through risk treatment (clause 6.1.3) and justify the choice.
ISO says the 2022 text was aligned with ISO/IEC 27002:2022, which explains each control. The full texts are paid, so here are the access-related controls by number and title, as listed in ISO's public preview of ISO/IEC 27002:2022, with our plain-language reading of what each covers:
| Control | Title | Our plain-language reading |
|---|---|---|
| 5.3 | Segregation of duties | Conflicting duties are split between people |
| 5.15 | Access control | Rules for who can access what, written down and applied |
| 5.16 | Identity management | Identities managed across their whole life, one per person |
| 5.17 | Authentication information | Passwords and other secrets issued and handled properly |
| 5.18 | Access rights | Access granted, reviewed, changed and removed in a controlled way |
| 6.5 | Responsibilities after termination or change of employment | What still applies after someone leaves or moves |
| 8.2 | Privileged access rights | Admin access restricted and managed |
| 8.3 | Information access restriction | Access to information limited according to the access rules |
| 8.4 | Access to source code | Source code and development tools protected |
| 8.5 | Secure authentication | Sign-in methods appropriate to the risk |
| 8.16 | Monitoring activities | Systems watched for unusual behavior |
Our readings are summaries of the titles, not the standard's wording. Your certification body assesses against the actual text, so buy the standard, or work with someone who has it, before you write controls you will be audited on.
What they have in common
Put side by side, the two frameworks ask a small team for the same core.
One account per person. HIPAA requires unique user identification; ISO 27001 has identity management. Shared accounts on systems in scope are hard to square with either.
Access granted by a defined process, based on the job. HIPAA's access authorization; ISO's access control rules and access rights. Role-based access control is the usual way to make "based on the job" concrete.
Access changed when jobs change, and ended when people leave. HIPAA's termination procedures and access modification; ISO's access rights and post-employment responsibilities. The joiners, movers and leavers process covers all three moments.
Fewer, controlled admins. ISO names privileged access rights outright; under HIPAA it follows from granting only the access people need. Least privilege covers how.
Proper sign-in. HIPAA's person or entity authentication; ISO's secure authentication and authentication information.
Logs, and someone reading them. HIPAA's audit controls and activity review; ISO's monitoring.
Periodic review. Both expect you to check access, not just set it once. The user access review is the process and template.
Evidence
How do you show compliance? With documents that describe what you do and records that prove you did it. Start with a written access control policy, with an owner and a review date; the access control policy template is a starting point. Add a list of systems in scope: for HIPAA, every system that creates, receives, maintains or transmits ePHI.
Then come the records. Keep access requests and approvals, and the role matrix they follow. Keep leaver records: for each departure, when access was removed from each system. Keep access reviews with reviewer sign-off, which is what access certification means. Keep admin lists per system, with reasons. And keep logs, with evidence that someone reviews them: a dated note is enough to show the review happened.
HIPAA has its own retention rule: documentation the Security Rule requires is kept for six years from its creation or the date it was last in effect, whichever is later (164.316(b)(2)). The same section requires you to make documentation available to the people who implement it, and to review and update it periodically. For ISO 27001, your certification body tells you what it needs to see.
A small-team setup
For a company of 5 to 50 people on Google Workspace, a workable setup looks like this.
Your directory is the source of truth. Everyone has a Google Workspace account, and nobody has access to an in-scope system without one, except named contractors with an end date.
MFA is enforced in Google Workspace and in every in-scope system that supports it. The Google Workspace security checklist has the settings.
Access comes in role-based bundles. Each job gets a defined set of systems and roles; anything else needs the system owner's approval, recorded.
Each in-scope system has two named admins, and nobody else holds admin there.
Leavers lose access the same day in every system, and the removal is recorded with a date.
Access reviews happen every quarter for in-scope systems, and the reviewer signs them off.
Automatic logoff and encryption are checked in each in-scope system, with a note where a system cannot do it and what you do instead. That note is your addressable-specification documentation.
Vendor agreements are in place. Under HIPAA, 164.308(b) requires satisfactory assurances, documented in a written contract or other arrangement, from business associates that create, receive, maintain or transmit ePHI for you, and from subcontractors if you are a business associate yourself. In practice that agreement is called a business associate agreement. Ask your counsel which of your tools are in scope.
A worked example
A 15-person clinic-software startup holds ePHI in its production database, its support tool and a shared drive. Its in-scope list has those three plus Google Workspace, because that is how people sign in. The operations lead is the security official. Engineers get the database and source code; support gets the support tool; nobody gets all three by default. When a support agent leaves, the removal from the support tool and the drive is logged that day. Each quarter, the operations lead exports each system's user list, the team leads confirm or remove each person, and the signed list goes into the evidence folder. None of that needs an identity provider. Whether it is enough is the assessor's call.
Where SmashSSO fits
SmashSSO can help with the first three items of the common core and with periodic review: it reads your people from Google Workspace with read-only access, shows who has an account in each tool and with which role, flags accounts that match nobody, alerts you when someone is suspended and shows where they still have access, and records every invite, role change and removal in an audit log. Changes run through a tool's member API where you have added a token, or through an agent in your own Chrome otherwise.
Be clear about what it is not. It is not SSO and does not enforce how anyone signs in. SmashSSO has no SOC 2 or ISO 27001 report (security), and its site does not mention a HIPAA business associate agreement, so don't assume one. Whether it belongs anywhere near your ePHI systems is a question for your assessor or counsel. It costs a flat fee from $199 a month, billed annually (pricing).