Study guide

1.4 Control Taxonomy and Functional Classification

PECB ISO/IEC 27001 Lead Auditor Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Fundamental Principles and Concepts of an ISMS

1.1 ISO/IEC 27000 Family Overview and Terminology 1.2 Information Security Core Concepts and CIA Triad 1.3 Risk Management Principles and Vocabulary 1.4 Control Taxonomy and Functional Classification 1.5 Emerging Technologies and Regulatory Context

2 Chapter 2: Information Security Management System Requirements (ISO/IEC 27001:2022 Clauses 4-10)

2.1 Context of the Organization and Interested Parties (Clause 4) 2.2 Leadership, Commitment, and Information Security Policy (Clause 5) 2.3 Planning, Risk Assessment, and Risk Treatment (Clause 6) 2.4 Support, Resources, and Documented Information (Clause 7) 2.5 Operation, Performance Evaluation, and Continuous Improvement (Clauses 8-10)

3 Chapter 3: ISO/IEC 27001:2022 Annex A Controls Framework

3.1 Annex A Architecture & Attribute Taxonomy 3.2 Organizational Controls (Theme 5) 3.3 People Controls (Theme 6) 3.4 Physical Controls (Theme 7) 3.5 Technological Controls (Theme 8)

4 Chapter 4: Fundamental Audit Concepts and Principles

4.1 ISO 19011 Audit Principles and Framework 4.2 Audit Types: First, Second, and Third-Party 4.3 Auditor Ethics, Code of Conduct, and Impartiality

5 Chapter 5: Preparing an ISO/IEC 27001 Audit

5.1 Audit Initiation and Feasibility Assessment 5.2 Audit Plan Development and Scope Definition 5.3 Audit Team Selection and Task Assignment 5.4 Working Documents and Checklist Preparation

6 Chapter 6: Conducting an ISO/IEC 27001 Audit

Stage 1 Audit: Documentation Review and Readiness Assessment Stage 2 Audit: Opening Meeting and On-Site Execution Audit Evidence Collection Methods and Interviewing Techniques Audit Sampling Methodologies in ISMS Auditing Generating Audit Findings and Working Paper Documentation

7 Chapter 7: Closing an ISO/IEC 27001 Audit & Nonconformity Management

7.1 Nonconformity Classification Framework 7.2 Synthesizing Audit Findings and Formulating Audit Conclusions 7.3 Closing Meeting and Audit Report Preparation 7.4 Evaluating Corrective Action Plans and Root Cause Analysis 7.5 Follow-up Audits and Verification of Effectiveness

8 Chapter 8: Managing an ISO/IEC 27001 Audit Program & Recertification

8.1 Audit Programme Establishment & Management 8.2 Surveillance Audits, Recertification Cycle & Scope Changes 8.3 Auditor Competence, Evaluation & PECB Requirements

1.4 Control Taxonomy and Functional Classification

Key Takeaways Explain This Topic AI

Information security controls are classified functionally into Preventive (deter/prevent), Detective (identify/alert), and Corrective (remediate/restore) types.

Implementation domains categorize controls into Administrative/Organizational, Technical/Logical, and Physical classifications.

ISO/IEC 27002:2022 introduces a 5-attribute taxonomy system (Control Type, Information Security Properties, Cybersecurity Concepts, Operational Capabilities, Security Domains) for modern control tagging.

Defense-in-depth relies on overlapping, multi-layered control classifications to ensure that the failure of a single control does not cause a security breach.

Lead Auditors evaluate control design suitability (Is the control properly designed to mitigate the target risk?) and operational effectiveness (Is the control operating consistently over time?).

Last updated: July 2026

1.4 Control Taxonomy and Functional Classification

In an Information Security Management System (ISMS), controls are the safeguards, policies, procedures, mechanisms, and countermeasures deployed to modify risk. ISO/IEC 27001 Clause 6.1.3 requires organizations to select controls based on their risk treatment process and compare them against the reference controls in Annex A. To audit, design, or implement controls effectively, Lead Auditors must master control taxonomy —the systematic classification of controls by function, implementation domain, and operational attributes.

Functional Control Classification

Functional classification categorizes controls by when and how they act relative to a security incident: Incident Timeline:

  • ------- Before Incident --------|---- During Incident ----|-------- After Incident --------
  • [ PREVENTIVE CONTROLS ] | [ DETECTIVE CONTROLS ] | [ CORRECTIVE CONTROLS ]
  • Stop threat from materializing | Identify active breach | Remediation & restoration
  • 1. Preventive Controls

Objective: Proactively prevent an unwanted security event, incident, or unauthorized access from occurring.

Mechanism: Acts as a barrier or restriction prior to threat exploitation.

Examples: Multi-factor authentication (MFA), firewall block rules, mandatory security awareness training, physical door locks, biometric access gates, pre-employment background checks.

Audit Value: High efficiency; stopping an incident before execution eliminates direct recovery costs.

2. Detective Controls

Objective: Identify, discover, and alert on unauthorized activities, policy violations, or security incidents as they occur or shortly thereafter.

Mechanism: Monitors system behavior, events, or logs against baseline anomalies or signature patterns.

Examples: Security Information and Event Management (SIEM) alerts, Intrusion Detection Systems (IDS), log reviews, security audits, file integrity monitoring (FIM), motion detectors, CCTV surveillance.

Audit Value: Crucial for visibility; without detective controls, an organization cannot determine if preventive controls have failed.

3. Corrective Controls

Objective: Remediate damage, restore operations, isolate compromised systems, and correct errors following a security incident.

Mechanism: Takes reactive measures to limit impact and bring systems back to a secure operational state.

Examples: Automated system patch deployment, virus/malware quarantine routines, database backup restoration, disaster recovery failover, incident response playbook execution.

Audit Value: Mitigates impact severity after a breach has occurred.

Implementation Classification (Domains)

Controls are also classified by their implementation nature or operational domain:

Domain Primary Description Typical Controls & Safeguards Lead Auditor Evidence

Administrative / Organizational Governance policies, operational procedures, management frameworks, and legal agreements. Information security policies, background checks, NDA agreements, vendor risk management, security awareness training. Approved policy documents, signed NDAs, employee training completion logs, management review minutes.

Technical / Logical Hardware, software, cryptographic mechanisms, and automated controls embedded in IT systems. Firewalls, access control lists (ACLs), AES-256 encryption, anti-malware, network segmentation, zero-trust architecture. Firewall rule configurations, IAM policy exports, cryptographic key rotation logs, vulnerability scan reports.

Physical / Environmental Tangible barriers and physical measures protecting facilities, equipment, and environmental utilities. Security guard forces, keycard access turnstiles, biometric door locks, climate control, UPS batteries, fire suppression systems. Physical access logs, maintenance logs for UPS/HVAC, visitor badges, clean desk inspection records.

ISO/IEC 27002:2022 Control Attributes Taxonomy

ISO/IEC 27002:2022 modernized control management by assigning 5 standardized attribute values to each of the 93 controls. This enables automated filtering, tagging, and cross-mapping across frameworks:

  • Control Type: #Preventive , #Detective , #Corrective
  • Information Security Properties: #Confidentiality , #Integrity , #Availability
  • Cybersecurity Concepts: #Identify , #Protect , #Detect , #Respond , #Recover (aligned with NIST CSF)

Operational Capabilities: #Governance , #Asset_management , #Information_protection , #Human_resource_security , #Physical_security , #System_and_network_security , #Application_security , #Threat_and_vulnerability_management , #Identity_and_access_management , #Continuity , #Supplier_relationships , #Legal_and_compliance , #Information_security_event_management

  • Security Domains: #Governance_and_Ecosystem , #Protection , #Defense , #Resilience
  • Defense-in-Depth and Compensating Controls
  • Defense-in-Depth Architecture

No single security control is foolproof. Defense-in-depth is the practice of layering multiple, redundant control classifications across different domains so that if one control fails, subsequent controls prevent systemic compromise.

Example: Protecting sensitive database records relies on:

  • Physical security locks on data center doors ( Physical Preventive )
  • Firewall access control lists ( Technical Preventive )
  • Database user access permissions ( Administrative & Technical Preventive )
  • SIEM database audit logging ( Technical Detective )
  • Daily encrypted backups stored off-site ( Technical Corrective )
  • Compensating Controls

A compensating control is an alternative safeguard implemented when a primary control recommended by ISO/IEC 27002 cannot be technically or economically implemented.

Audit Requirement: The Lead Auditor must verify that the compensating control achieves the exact same security objective and provides an equivalent risk reduction compared to the standard primary control.

Lead Auditor Verification of Controls

During an ISMS audit, Lead Auditors evaluate controls across two distinct dimensions:

Design Suitability (Design Effectiveness): Is the control appropriately designed to prevent, detect, or correct the specific risk for which it was chosen?

Operational Effectiveness: Is the control operating as intended consistently over the audit period, and is it executed by competent personnel?

An auditor will test controls using four standard methods: Inquiry (interviewing staff), Observation (watching control execution), Inspection (reviewing documented evidence/logs), and Re-performance (independently executing the control procedure).