Study guide

Policies, Procedures, Standards, Laws, and Regulations

ISC2 Certified in Cybersecurity CC

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

Official 2026 CC Exam Facts and Timeline CAT Format and Beginner Security Judgment Domain Map and Time Allocation 30, 60, and 90 Day Study Plan with Readiness Thresholds

2 Domain 1: Security Principles (24%)

CIA Triad as a Practical Decision Tool Authentication, Authorization, Accounting, and Non-Repudiation Privacy in the CC Outline Beginner Security Decision Scenarios AI Security in Security Principles

3 Domain 1: Risk Management and Security Controls

Risk Identification in Business Context Risk Management Processes Risk Treatment Decisions Security Controls: Technical, Administrative, and Physical

4 Domain 1: Governance, Ethics, Policy, and Privacy

Governance and the ISC2 Code of Ethics Policies, Procedures, Standards, Laws, and Regulations Privacy and AI Governance Due Care, Due Diligence, and Governance Decisions

5 Domain 1: Physical Security Controls

Physical Controls and Their Monitoring Tailgating and Physical Penetration Testing

6 Domain 2: Security Governance - Business Continuity

Business Continuity (BC)

7 Domain 2: Security Governance - Disaster Recovery

Disaster Recovery (DR) Redundancy in Business Continuity and Disaster Recovery

8 Domain 2: GRC Planning

GRC Planning: Purpose, Importance, and Tools

9 Domain 2: Measuring Cybersecurity Effectiveness

Security Metrics, KRIs, and Dashboards AI Security in Governance, Awareness, and Continuity

10 Domain 2 and Domain 5: Security Awareness and Triage

Security Awareness and Organizational Culture Phishing and Password Protection Security Event Triage and Human Review

11 Domain 3: Identity Lifecycle Management

Identification, Authentication, Authorization, and Accountability Multi-Factor Authentication and Password Protection Provisioning, Deprovisioning, and Access Reviews Service Accounts and AI Bots in Identity Management AI Bots and Service Accounts in Identity Management

12 Domain 3: Logical Access Controls

Least Privilege and Separation of Duties DAC, MAC, RBAC, and ABAC

13 Domain 4: Networking Fundamentals

Network Models and IP Addressing Firewalls: Ports and Applications Virtual Private Networks (VPN) Wireless Networks and Embedded Systems

14 Domain 4: Network Security Architecture and Cloud Security

Network Segmentation Defense in Depth and Zero Trust Cloud Characteristics and Shared Security Model Cloud Service Models, Deployment Models, and Shared Security AI in Network Security and Cloud Hosting

15 Domain 5: Incident Response

Incident Response (IR) and the Incident Response Plan Preparing the Incident Response Plan Incident Response Exercises and Tabletops AI in Security Operations and Incident Response

16 Domain 5: Security Monitoring

Logging and Monitoring Security Events

17 Domain 5: Threat Actors and Threat Intelligence

Threat Actors, Threat Intelligence, and Frameworks

18 Domain 5: Data Security

Encryption and Hashing for Data Security Data Handling: Classification, Labeling, Masking, and Sanitization Security of the AI Workspace

19 Domain 5: Asset Protection

Configuration and Change Management Change Management and Asset Protection Asset Lifecycle and End-of-Life Management

20 Domain 5: Data Handling Policy

Data Handling Policy and Classification

21 Domain 5: Security Testing

Security Readiness, Application, and Physical Testing

22 Integrated CC Scenario Labs

Risk and Control Selection Drill Continuity, Recovery, and Response Drill Access Control Design Drill Segmentation and Triage Drill

23 Final 14-Day Review and Exam Readiness

CAT Pacing and 100-125 Item Strategy Missed-Question Notebook and Domain Repair Exam Day Logistics and Rescheduling After Passing: AMF and CPE

Policies, Procedures, Standards, Laws, and Regulations

Key Takeaways Explain This Topic AI

Policy states management intent at a high level; standards make policy mandatory and measurable; procedures give step-by-step instructions; guidelines are recommendations.

A handy mnemonic: policy = WHAT/WHY, standard = MUST (specific rule), procedure = HOW, guideline = SHOULD.

Policies and standards are mandatory, procedures are mandatory when invoked, and a guideline is mandatory only when policy or a standard adopts it.

Laws and regulations come from government authorities; when policy and law conflict, escalate to legal or compliance.

When policy conflicts with law, contract, or regulation, escalate to legal, compliance, or authorized leadership rather than improvising.

Last updated: October 2026

Key Concepts

Governance runs on clear documents. Questions frequently describe a document and ask its type, or describe a problem and ask which document should guide the response. Separate three things: authority (who approved it), requirement (is it mandatory), and instruction (how detailed it is).

A policy is a high-level statement approved by management that says what must happen and why . An acceptable use policy may state that company systems are for authorized business use and that users must protect confidential information. A policy rarely lists individual commands or screens.

A standard is a mandatory requirement that supports a policy and makes it measurable . If policy says data must be protected, a standard might require AES-256 encryption for stored confidential data, approved multi-factor authentication (MFA) methods for remote access, or a hardened server baseline. Standards turn vague intent into testable rules.

A procedure gives step-by-step instructions. When policy requires account termination and a standard defines the controls, the procedure tells the administrator how to disable the account, revoke tokens, remove group memberships, collect equipment, and record completion. Procedures drive consistency and cut mistakes.

A guideline is recommended advice that adds flexibility, such as suggested secure-travel practices or naming conventions. A guideline is mandatory only if a policy or standard makes it so.

A quick exam mnemonic: policy = WHAT/WHY, standard = MUST, procedure = HOW, guideline = SHOULD .

  • Document type Main question it answers Mandatory? Example
  • Policy What does management require, and why? Yes Remote access must use approved secure methods
  • Standard What specific rule must be met? Yes MFA is required for all remote access
  • Procedure How is the task performed? Yes (when invoked) Steps to enroll a user in MFA
  • Guideline What is recommended? No (unless adopted) Suggested secure-travel practices
  • Laws, regulations, and contracts

Laws and regulations come from governments and regulators. They may mandate breach notification, privacy protections, retention periods, accessibility, or sector-specific duties (the outline names regulations and laws as a category; study the category rather than individual statutes). Contracts create binding obligations too, such as security clauses with a customer or vendor.

When a policy and a law conflict, escalate to legal, compliance, or authorized leadership.

Exam Application

Scenario: Company policy says confidential information must be protected. Auditors ask how laptops are configured. The relevant standard might require full-disk encryption, a 10-minute screen lock, endpoint protection, and approved patch levels; the procedure shows technicians how to configure and verify those settings. The policy alone does not tell the auditor the encryption algorithm.

Scenario: A user asks whether they may upload customer records into a new web tool. The best first move is not a personal guess. Check the data classification policy, acceptable use policy, vendor risk process, privacy requirements, and any applicable contracts or laws. If the tool is unapproved, escalate for review rather than inventing an informal exception.

Policy items also test enforcement consistency . If an executive wants out of MFA because it is inconvenient, the right answer is the documented exception process, which may approve a temporary compensating control or deny the request. An undocumented bypass for a senior person is always wrong.

Finally, mind the document lifecycle : policies and standards should be approved, communicated, reviewed, updated, and enforced. A 10-year-old password standard may not reflect current threats, and a procedure that no one can follow should be fixed rather than treated as a working paper control. For each question, decide whether the issue is management direction, a mandatory technical rule, task instruction, optional advice, or legal obligation, then pick the document or escalation path with the right authority.

Reading the hierarchy in a question

Questions often chain the documents together. A clean way to keep them straight is the flow from broad to specific: a regulation (external, mandatory) shapes a policy (internal intent), which is enforced by a standard (specific mandatory rule), which is carried out by a procedure (exact steps), while a guideline offers optional help on the side. When a stem says "management has decided that...", you are looking at a policy. When it says "all systems must use...", you are looking at a standard. When it lists numbered steps or screen clicks, it is a procedure. When it says "it is recommended that...", it is a guideline.

Worked example: a stem reads, "A privacy regulation requires breach notification; the company therefore states that all incidents must be reported; remote logins must use approved MFA; the on-call analyst follows ten steps to revoke a token." Map them in order: the privacy regulation is the source of the duty, the reporting statement is policy, the MFA requirement is a standard, and the token-revocation steps are a procedure. Questions that ask "which of these is the standard?" are testing exactly this separation, and the wrong options usually swap two adjacent layers.

  • Phrase in the stem Document it signals
  • "The law requires..." Law or regulation
  • "Management has determined..." Policy
  • "All systems must..." Standard
  • "Follow these steps..." Procedure
  • "It is recommended..." Guideline

Finally, remember that documents have owners and review cycles . If a stem says a control exists only on paper and everyone ignores it, the governance answer is to fix or retire the document and re-communicate it, not to punish workers for an unworkable rule.

Source: ISC2 CC Exam Outline effective September 1, 2026 (v01/2026), subdomain 1.3 (regulations and laws; frameworks; policies, standards, procedures), checked 2026-10-22.