Control Purpose
The organization must control how secret authentication information is issued, changed, protected, reset, and handled.
Use A.5.17 Authentication Information for the detailed requirement, implementation guidance, audit checks, evidence expectations, and related ISO 27005 context.
Risk Logic
Detailed Note
Related Risks
No published risk scenario is linked to this control yet. Create or link a risk note under the risk knowledge base before treating this control as fully mapped.
Implementation Activities
See A.5.17 Authentication Information.
Evidence Required
See A.5 Organizational Controls Audit Guide and the relevant audit evidence pack.
Audit Questions
- AQ-ISO27001-A.5.17 Audit Question
- How does the organization prove ISO27001-A.5.17 is implemented and operating?
- What evidence shows ownership, review cadence, exceptions, and corrective action?
- Which failed condition would create an audit finding for this control?
ISO 27005 Link
Map this control to risk scenarios, treatment decisions, residual risk, and review triggers.
ISO 27002 Link
Use ISO/IEC 27002 guidance to interpret implementation activities, evidence expectations, and control review needs.
Software Architecture Mapping
Relevant objects:
- control
- evidence
- risk
- audit_question
- Iso27001
- ISO27002
- Annex a
- Control
- Authentication information
Note Metadata
Aliases: ISO27001-A.5.17
Source: 06-Control-Knowledge-Base/ISO27001-A.5.17-Authentication-Information.md
Control dependency map
How this control connects to work products
Generated from the static research graph. It shows navigation and evidence dependencies; it is not an audit conclusion.
3
links
Requirement context
Primary control text, framework notes, or adjacent controls this note points to.
Audit checks
Audit questions, checklists, or review material connected to the control.
Graph-sourced resources
Templates and evidence
Auditor evidence packs
Evidence collections and audit-facing verification material.