← Back to blog

ISO 27001

ISO 27001 A.8.5 Secure Authentication: Where Does MFA Need to Be Phishing-Resistant?

ISO 27001 A.8.5 Secure Authentication

/Arbnor Mustafa/9 min read

Your identity provider (IdP) reports 98% multi-factor authentication (MFA) enrollment, and the dashboard is green. Then a password-spraying campaign succeeds anyway, through an older mail protocol that still accepts a username and password with no second factor. Nothing was misconfigured in the IdP. The exposure sat in a path nobody had counted. MFA coverage is measured by the weakest door that still accepts a password, not by the percentage of users enrolled.

Short answer Purpose: Make authentication strength match the risk of what sits behind the login. Key decision: Which access gets phishing-resistant MFA, and how you handle systems that can't enforce MFA at all. Common gap: Legacy protocols, service accounts, and break-glass accounts outside MFA enforcement.

What A.8.5 asks for

A.8.5 asks you to implement secure authentication technologies and procedures. The strength you choose should follow your information access restrictions and your access control policy. In practice, that means stronger authentication where the information or privilege is more sensitive.

It is an Annex A control. You select it through risk treatment and record and justify that decision in your Statement of Applicability (SoA). It applies to almost any organization with systems people log in to.

ISO/IEC 27002 adds guidance on the log-on procedure itself, such as:

  • not revealing which part of a failed log-on was wrong,
  • protecting against brute-force attempts,
  • logging successful and failed attempts,
  • not transmitting passwords in clear text,
  • ending inactive sessions.

That guidance is recommended, not mandatory. Requiring MFA for critical access is a common risk treatment, and 27002 points to stronger authentication where the information warrants it. ISO does not mandate MFA for every system.

Boundary: A.8.5 covers the mechanism (factors, log-on procedure, sessions). A.5.17 covers authentication information: how passwords and tokens are issued, reset, and protected, including identity checks before a reset. A.8.5 says log-on attempts should be logged; watching those logs for attacks belongs to A.8.16.

Depends on:

  • A.8.3 Information access restriction: it defines what is restricted, which sets the strength A.8.5 needs.
  • A.5.15 Access control: the policy that A.8.5's choices must follow.

Decide your A.8.5 scope

ProfileWhat is in scopeHow the authentication matrix changesWhen to review scope
Cloud-first organization, one IdP, mostly SaaSIdP, SaaS apps (federated or not), cloud consoles, admin roles, service accountsFew rows; most apps inherit IdP policy, so effort goes to apps with local logins and to admin rolesWhen a new SaaS app is adopted or an app drops off single sign-on (SSO)
Hybrid estate with on-premises directory, VPN, legacy appsEverything above plus directory, VPN, servers, legacy apps and protocolsAdds rows for systems that can't do MFA, each with compensating controls and an exception expiryWhen a legacy system is retired or a remote access method changes
SaaS provider whose product login is in ISMS scopeInternal access plus customer-facing authentication and the admin console for your productSeparate rows for customer authentication options and for your staff's support access to customer tenantsWhen authentication features ship or support access processes change

What to exclude, minimize, or deprioritize

  • Apps that authenticate only through your IdP. You can review the IdP policy once instead of each app separately, as long as the app has no local login left enabled.
  • Customer-facing authentication. Leave it out if your product is outside the ISMS scope.
  • Low-risk internal tools holding no sensitive data. These can stay on standard SSO with MFA rather than stronger methods.

Minimizing is inappropriate for:

  • privileged access,
  • anything reachable from the internet with a password alone,
  • systems holding information your A.8.3 restrictions classify as sensitive.

What good looks like for A.8.5

A. Artifact: authentication standard matrix

Adapt this to your environment. All values are illustrative.

Access typeRequired authenticationSession / idle timeoutBrute-force protectionExceptions
Privileged access (IdP admins, cloud console admins, production servers)Phishing-resistant MFA, e.g., FIDO2 security key or platform authenticator15 minutes idle; re-authenticate for elevation (illustrative)Lockout or throttling plus alert on repeated failuresBreak-glass accounts only, recorded in the Exception register
Remote access to sensitive data (VPN, remote desktop, sensitive SaaS)MFA through the IdP; phishing-resistant where feasible30–60 minutes idle (illustrative)Throttling; risk-based sign-in checks where availableNamed, time-limited, with compensating control
Standard workforce appsSSO with MFA through the IdP; local logins disabledPer app riskInherited from IdPApps that can't federate, listed with owner and retirement or mitigation plan
Service and machine accountsNo interactive login; credentials vaulted and rotated, or workload identityn/aRestrict by network or source where possibleEach account in the Service account register
Legacy systems unable to enforce MFAReachable only via an MFA-protected path (e.g., VPN or jump host)Short sessionsThrottling at the access pathException register entry with expiry date

A matrix records your design. It does not prove anything is enforced. That proof comes from policy exports and sign-in logs (see C).

B. Weak vs. effective

WeakEffective
"MFA is enabled for all users.""The IdP policy requires MFA for interactive sign-ins to federated apps, and legacy authentication protocols are blocked. Two break-glass accounts are excluded. Their credentials are stored offline, sign-ins raise an alert, and access is tested quarterly (illustrative)."

The weak version describes enrollment. The effective version describes enforcement, the bypass paths closed, and the exceptions that remain, with how they're watched.

C. Measures and evidence

MeasureWhy it mattersWhat sufficient looks likeEvidence that proves it
MFA enforcement by access tierEnrollment without enforcement leaves passwords as the only barrierPrivileged access requires phishing-resistant MFA; other tiers require MFA per the matrix; exceptions named, compensated, and expiringDesign: Authentication standard matrix. Operational: IdP policy export; MFA registration report
Legacy and bypass paths closedOne password-only protocol undoes the MFA policyProtocols and local logins that skip MFA are disabled, or limited to Exception register entriesOperational: IdP policy export; Sign-in log extract showing no successful legacy sign-ins outside exceptions
Brute-force protectionPassword spraying and credential stuffing are routineThrottling or lockout on internet-facing logins; repeated failures raise an event for monitoring (A.8.16)Design: lockout and throttling settings. Operational: Sign-in log extract
Service accounts controlledNon-human accounts often sit outside MFA policy by designInteractive login blocked; credentials vaulted or replaced by workload identity; each has an ownerDesign: Service account register. Operational: Sign-in log extract showing no interactive sign-ins
Break-glass accountsNeeded for IdP outages, dangerous if unwatchedFew accounts; strong credentials stored securely; each sign-in alerts; access tested periodicallyOperational: Break-glass test record; alert configuration
Session managementUnattended sessions extend access beyond the log-onIdle timeouts tiered per the matrix; re-authentication for privileged actionsOperational: IdP policy export; app session settings

The example values are starting points, not requirements specified by ISO.

D. How to validate it yourself

  1. Legacy sign-in hunt.
    • Inspect: Query 30 days of sign-in logs for authentication without MFA (illustrative window).
    • Success: Each result maps to an Exception register entry.
    • Record: Sign-in log extract with exceptions annotated.
    • Limit: Logs only show attempts that reached the IdP. Apps with local logins need check 2.
  2. Federation gap check.
    • Inspect: Compare your application inventory against apps federated to the IdP, and confirm local logins are disabled on the federated ones.
    • Success: Each app is either federated without a local login or listed as an exception.
    • Record: The comparison, attached to the Authentication standard matrix.
  3. Privileged method check.
    • Inspect: Export holders of admin roles and the authentication methods each can use.
    • Success: Each can sign in only with a phishing-resistant method, not merely has one registered.
    • Record: MFA registration report filtered to admins, plus the IdP policy export.
  4. Break-glass test.
    • Inspect: Sign in with a break-glass account under controlled conditions.
    • Success: Sign-in works and the alert reaches the right people.
    • Record: Break-glass test record with the alert timestamp.

Independent review adds value when your estate mixes identity systems or carries many legacy exceptions, because gaps between systems are easy to miss from the inside. It isn't required unless a contract or regulator says so.

Common A.8.5 implementation mistakes

SSO is on, but the old login page still works.

  • Symptom: Users can still sign in to a SaaS app with a local password, bypassing the IdP and its MFA.
  • Why it matters: The MFA policy protects the front door while the side door stays open.
  • Fix: Disable local logins where the app allows it, or record the app as an exception with an owner and a plan.

Admins approve push prompts they didn't start.

  • Symptom: An admin reports a burst of MFA prompts and admits approving one "to make them stop."
  • Why it matters: Push approval without context is weak for high-value accounts.
  • Fix: Move privileged roles to phishing-resistant methods, and enable number matching or similar where your IdP supports it for everyone else.

A "service account" is used by a person.

  • Symptom: The sign-in log shows interactive browser sessions from an account that's exempt from MFA because it's "for an integration."
  • Why it matters: An exemption granted for a machine is being used by a person, who gets password-only access.
  • Fix: Block interactive sign-in for service accounts, and give the person their own MFA-protected account.

Exceptions never expire.

  • Symptom: The Exception register lists systems excused from MFA two years ago "until migration," with no date.
  • Why it matters: Nobody re-checks whether the exception is still needed or still safe.
  • Fix: Give each exception an owner, a compensating control, and an expiry date reviewed alongside access reviews.
  • A.5.15 Access control: the policy A.8.5's strength choices must follow; A.8.5 depends on it.
  • A.8.3 Information access restriction: defines what's sensitive, which drives the tiers in your matrix.
  • A.5.16 Identity management: makes sure each account belongs to an identifiable person or owned service before authentication matters.
  • A.5.17 Authentication information: issuing, resetting, and protecting passwords and tokens, including identity verification before an MFA reset.
  • A.8.2 Privileged access rights: decides who holds admin roles; A.8.5 decides how strongly they authenticate.
  • A.8.16 Monitoring activities: consumes the sign-in logs A.8.5 produces and acts on suspicious patterns.
  • A.6.7 Remote working: sets the conditions for remote access whose authentication A.8.5 covers.

If you have one afternoon

  1. Run the legacy sign-in hunt (check D1).
    • Do: Query your sign-in logs for authentication without MFA, then block or record each path you find.
    • Output: A Sign-in log extract and the first entries in your Exception register.
  2. Check your admins (check D3).
    • Do: Export admin role holders and their allowed methods, and move any that can still use password-only or SMS sign-in to a stronger method.
    • Output: An updated MFA registration report for privileged roles.
  3. Draft the top two rows of the matrix.
    • Do: Write the privileged access and remote access rows of the authentication standard matrix, with their exceptions.
    • Output: A first version of the Authentication standard matrix that covers the access most worth attacking.

This won't complete A.8.5, but it closes the paths attackers try first and gives you evidence to build on.

Join the conversation!

Subscribe to our newsletter.

We'll email you new articles. Unsubscribe any time. See our Privacy Policy.