What is the difference between a policy, a standard, a procedure, and a guideline?
A policy says what must be done and why, a standard gives the specific mandatory values, a procedure gives the ordered steps, and a guideline is optional advice.

Exam objectiveSummarize elements of effective security governance
Objective 5.1 covers the elements of effective security governance: how an organization decides what security must achieve and makes sure it happens, through written documents, outside rules, oversight structures, and accountability for data.
The document hierarchy. A policy is management's mandatory statement of what must be done and why, such as an acceptable use policy (AUP), information security policies, and business continuity, disaster recovery, incident response, software development lifecycle (SDLC), and change management policies. A standard turns a policy into specific, measurable requirements, such as password, access control, physical security, and encryption standards. A procedure is the detailed, ordered how-to, such as change management, onboarding and offboarding, and playbooks. A guideline is optional advice.
Outside rules and upkeep. External considerations are regulatory, legal, industry, local or regional, national, and global. Regulatory rules carry the force of law, while industry standards usually bind by contract. Monitoring observes how the documents perform, and revision changes them, on a schedule and whenever a new law, major incident, or business change requires it.
Structures and roles. Boards hold ultimate accountability, committees do detailed review and recommend, and government entities have legal authority; governance can be centralized or decentralized. The data owner is accountable and decides classification and access, the custodian carries out the technical protection, and the steward looks after data quality and correct use. In privacy law, the controller decides why data is processed and the processor acts on its behalf.
Exam questions test the difference between a policy, standard, procedure, and guideline, and ask who is accountable for data versus who handles it technically.
This page is the map. Knotch is where you drill it until it sticks.
A policy is management's statement of what must be done and why, without technical detail. A standard turns that into the specific algorithms, lengths, and settings that have to be used.
A standard is mandatory. A guideline is advisory.
An owner is an internal accountability role. A controller is a legal status under privacy law that can belong to an organization, and it is not a synonym for owner.
Centralized governance means one authority decides for the whole organization. Decentralized governance means units decide for themselves within broad guidance, and many organizations mix the two.
The full set of look-alike pairs for this objective is inside Knotch.
A company reviews its security policies every November. In March, a new national law adds duties that the current policy does not cover.
What should the company do about its policy?
Policies are reviewed on a schedule and also whenever a new law, major incident or business change occurs.
NIST CSF 2.0 expects policy to be reviewed and updated as requirements, threats and technology change. A new law, a major incident, an audit finding or a significant business change each justify revision before the next scheduled review.
Why not A: A scheduled review does not replace revision when a new legal requirement appears.
Why not C: The requirement affects what the policy must say, so the policy itself needs to be updated.
Why not D: Informal compliance leaves the policy and the law in conflict and cannot be enforced or audited.
A policy says what must be done and why, a standard gives the specific mandatory values, a procedure gives the ordered steps, and a guideline is optional advice.
The owner is accountable and decides classification, access, and acceptable use. The custodian carries out the technical protection the owner requires, such as backups, encryption, and access control setup.
On its review schedule, and also whenever a new law, a major incident, an audit finding, or a significant business change creates a requirement it does not cover.
