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
Managers must make sure their staff actually apply the security policies and procedures in daily work.
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
This control expects managers to turn policy into day-to-day practice, not merely circulate documents. Line managers should reinforce the Information Security Policy, confirm training, review access and exceptions, and address repeated nonconformities through normal management routines. Show the connection to Information Security Roles & Responsibilities so accountability is visible and not left to the security lead alone.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Team members have completed training, but managers never verify understanding, so risky shortcuts continue unchallenged and local procedures drift away from policy.
Access rights are reviewed by security or IT only, with no documented management sign-off from the line manager who knows job duties and business need.
Security expectations are absent from one-to-ones or performance discussions, leaving repeated nonconformities unaddressed and no evidence of manager follow-up.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Define manager duties in the roles template: approve role-based access, confirm training completion, escalate repeated policy breaches, and review exceptions within their teams. Make each duty observable through tickets, meeting notes, or sign-offs rather than relying on general awareness statements.
Build lightweight managerial routines: monthly access review for critical systems, quarterly training status review, and a standing agenda item for security issues in team meetings. The cadence is illustrative; the real trigger should follow the risk of the team’s activities.
Where issues recur, managers should open corrective actions, assign owners, and check effectiveness after implementation. Link the follow-up to Clause 10.2 so lessons from missed deadlines, repeated weak passwords, or uncontrolled sharing are tracked to closure.
For contractors or temporary staff, confirm the manager owns onboarding, permissions, confidentiality reminders, and offboarding checks. Record who accepted the risk, what supervision was provided, and when the next review will happen.
What an auditor will ask to see
Signed access review approvals or workflow records showing manager review of team permissions and exceptions.
Team meeting minutes, one-to-one notes, or performance records referencing security responsibilities and unresolved issues.
Training completion reports with manager acknowledgement and follow-up actions for overdue or failed items.
Baseline documents in the kit
These free kit documents help you document or evidence A.5.4. 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.