Appearance
← CISSP syllabus chapters

Domain 1 · Objective reference 1.6 · Chapter 6 of 62

Policies, standards, procedures and guidance

About 5 minutes · Current ISC2 outline effective 15 April 2024; the announced 15 April 2027 replacement requires separate mapping

Session only. Enable saving or download a backup from this course’s hub.

Completion is self-reported and does not certify understanding.

See it · Try it · Recall it

Picture the topic

Remember this: What must happen differs from how to perform it.

CISSP · 1.6Policy and authority pyramid
Policy and authority pyramidRead from direction toward implementation. The width of a tier is visual emphasis, not a count of controls or authority. Policy: State management intent and authority. Standard: Set mandatory measurable requirements. Procedure: Describe repeatable implementation stepsPolicyStandardProcedure
Read from direction toward implementation. The width of a tier is visual emphasis, not a count of controls or authority.
Visual preferences

Reduced-motion preferences are respected. Highlights guide attention; they do not represent measured traffic or elapsed time.

Explore the anchors

State management intent and authority.

Concept matching activity

Match this task or description to its concept:

Set mandatory measurable requirements.

Choose a concept before checking the explanation.

A quick way to study this topic
  1. Hide the explanation and redraw these three anchors from memory.
  2. Explain the difference between the anchors in your own words.
  3. Apply the distinction to the worked example below. Check the full lesson for assumptions and exceptions.
  4. Recall it again tomorrow, then after a few days. A memory hint is a retrieval cue, not a replacement for understanding.

Original academy illustrations and fictional exercises. These are learning simulations, not a real virtual machine, network assessment or measure of job readiness. Activities reset when you leave or reload; they do not change quiz scores.

What this chapter explains

Concepts and mechanisms

Policy states management direction and required outcomes. Standards set mandatory implementation conditions; procedures explain execution; guidance supports choices where discretion is allowed. Their relationship should be coherent. A remote-access policy may require protected access, a standard may define approved authentication and device conditions, and a procedure may explain enrollment, review and revocation.

Design, evidence and tradeoffs

Assign ownership, approval, version control, communication and review triggers. Test usability against actual workflows and exception conditions. A document without resources or an escalation route can produce informal bypass. Exceptions need rationale, scope, exposure, safeguards, authorized approval and expiry. Incorporate requirements into acquisition and development rather than leaving them in a security-only library.

Worked example

A temporary incompatibility uses a documented exception with an owner and expiry instead of disabling the requirement permanently.

Check your understanding

Why is policy acknowledgment not enough to establish operating effectiveness?

Show explanation

It records receipt or agreement, not whether the process and controls performed as required during the relevant period.

Source and study boundary

Official syllabus source. The reference identifies the topic being taught. Explanations and examples are original academy material; a topic link does not establish independent approval or sufficient exam mastery.