← ISO 27001 · A.5 — Organisational

A.5.1 — Policies for information security

high policy-governance

Requirement

Information security policy and topic-specific policies shall be defined, approved by management, published, communicated to and acknowledged by relevant personnel, and reviewed at planned intervals.

What the engine looks for

Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.

Required element 1 — any one of
information security policysecurity policypolicy
Required element 2 — any one of
approvedmanagementreviewedpublished
Supporting terms — specificity signals
annual reviewversionowneracknowledgetopic-specificeffective date
Contradiction markers

Finding any of these outranks coverage — a policy that admits the gap is worse than silence.

no policy policy is out of date never reviewed

Equivalent controls elsewhere

Matched on shared topics. Satisfying this control usually moves these too.

FrameworkControlTitleShared topics
GDPR Art.24 Responsibility of the controller policy-governance
GDPR Art.31 Cooperation with the supervisory authority policy-governance
SOC 2 CC5.1 Selection and development of control activities policy-governance
SOC 2 CC5.3 Deployment through policies and procedures policy-governance
PCI DSS 4.0.1 12.1 Information security policy policy-governance
HIPAA 164.308(a)(1)(ii)(C) Sanction policy (R) policy-governance
NIST CSF 2.0 GV.PO-01 Cybersecurity policy is established and communicated policy-governance
GDPR Art.5(2) Accountability policy-governance