Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Use secure authentication technologies and procedures appropriate to the sensitivity of the access.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
Secure authentication breaks down when password rules exist but identity proofing, MFA enrollment, reset requests, and account recovery are inconsistent. Guidance should explain how access sensitivity drives stronger factors, how administrators are separated from standard users, and how support teams verify identity before resets. It should also make the evidence trail clear enough to show who approved what, when, and through which identity platform.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
MFA is enabled for some applications but not enforced for all remote access, administrative portals, or service accounts that can reach sensitive information.
Helpdesk resets rely on weak identity checks, creating a route for impersonation, social engineering, or unauthorized account takeover.
Authentication logs are retained but not reviewed for repeated failures, impossible travel, or stale accounts, limiting the organization’s ability to spot abnormal access patterns.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Set authentication standards by access sensitivity: phishing-resistant MFA for privileged administrators, MFA for remote and cloud access, and step-up authentication for high-risk transactions. Record the factor type, enrollment method, and exceptions in a controlled register approved by the system owner and security lead.
Define identity proofing for new accounts and recovery: validate the requester through HR records, manager confirmation, or pre-registered out-of-band contact methods before reset or re-enrollment. Support staff should use a scripted verification checklist and log the evidence in the ticketing system.
Review privileged and high-risk authentication events on an illustrative weekly cadence, focusing on failed attempts, lockouts, unusual locations, dormant accounts, and changes to authentication methods. Escalate suspicious patterns to incident handling and require account suspension where compromise is plausible.
Tie identity lifecycle actions to joiner-mover-leaver processes. When roles change, revoke old entitlements, reissue only needed authentication methods, and remove inactive accounts after a defined inactivity threshold. Keep approvals, reset tickets, and exception decisions so auditors can trace control operation across the identity platform.
What an auditor will ask to see
Identity provider policy export showing MFA status, factor strength, and conditional access rules by user group.
Helpdesk reset tickets with verification questions, approver details, and timestamps for account recovery actions.
Authentication logs or dashboard screenshots showing lockouts, suspicious sign-ins, and documented follow-up actions.
Baseline documents in the kit
These free kit documents help you document or evidence A.8.5. Each one is tailored to your organization when you build your kit.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.