Study guide
Audit Sampling Methodologies in ISMS Auditing
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
Audit Sampling Methodologies in ISMS Auditing
Key Takeaways Explain This Topic AI
Audit sampling involves evaluating less than 100% of a population of items (e.g., access tickets, firewall changes) to form a reasonable conclusion about the entire population.
ISO 19011 Annex 3 recognizes two main sampling approaches: Judgemental (non-statistical) sampling based on auditor knowledge/risk, and Statistical sampling based on mathematical probability.
Sample size determination depends on control execution frequency, population volume, inherent security risk, and tolerable error thresholds.
Sampling risk represents the possibility that the auditor's conclusion based on a sample differs from the conclusion that would be reached if the entire population were audited.
Multi-site sampling formulas (such as y = x y = \sqrt{x} y = x under IAF MD 1) allow certification bodies to audit a representative sample of sites while ensuring full ISMS scope coverage.
Last updated: July 2026
Audit Sampling Methodologies in ISMS Auditing
In modern organizations, information security processes generate vast volumes of operational data. A large enterprise may process 50,000 user identity requests, implement 10,000 firewall change tickets, and generate millions of event log entries annually. Auditing 100% of these records is physically impossible and economically unfeasible. Therefore, auditors rely on audit sampling to gather sufficient, representative evidence to draw valid audit conclusions.
Governed by ISO 19011:2018 (Annex 3) , audit sampling is defined as the application of audit procedures to less than 100% of the items within a population of audit relevance. To maintain audit credibility, the Lead Auditor must select sampling methodologies that minimize sampling risk —the risk that the auditor's sample-based conclusion is different from the conclusion that would be reached if the entire population were subjected to the same audit procedure.
1. Judgemental vs. Statistical Sampling
ISO 19011 categorizes audit sampling into two primary approaches: Judgemental (Non-Statistical) Sampling and Statistical Sampling .
Comparison of Sampling Methodologies
Attribute Judgemental (Non-Statistical) Sampling Statistical Sampling
Selection Basis Auditor knowledge, professional judgement, risk assessment, and contextual experience. Random selection based on mathematical probability theory (e.g., simple random, systematic).
Sample Representativeness Focused on high-risk, complex, or historically problem-prone items. Scientifically representative of the entire numerical population.
Quantifiable Sampling Risk Cannot be mathematically measured or expressed in statistical confidence intervals. Quantifiable using mathematical formulas (e.g., 95% confidence level with 5% margin of error).
Best Used When Evaluating qualitative controls, complex policy compliance, or small populations. Auditing large, homogeneous populations of quantitative records (e.g., 100,000 access logs).
Primary Limitation Susceptible to auditor bias; findings cannot be mathematically extrapolated to the full population. Requires larger sample sizes; may miss qualitative context or deliberate high-risk anomalies.
2. Sample Size Selection Guidelines
When conducting judgemental sampling of operational control execution, auditors determine sample sizes based on control frequency and risk level . The table below represents the standard sample size guidance accepted under PECB Lead Auditor guidelines and international auditing practices:
Control Execution Frequency Total Annual Population Volume Recommended Minimum Sample Size (Low/Moderate Risk) Recommended Minimum Sample Size (High Risk / Critical Control)
- Annual (e.g., Strategy review, annual penetration test) 1 1 (100% testing) 1 (100% testing)
- Quarterly (e.g., Access reviews, firewall rule reviews) 4 2 4 (100% testing)
- Monthly (e.g., Patch management cycles, backup restores) 12 2–3 5–6
- Weekly (e.g., Vulnerability scans, facility inspections) 52 5 10–15
- Daily (e.g., Media disposal logs, visitor entries) ~250–365 15–20 25–40
- Automated / Continuous (e.g., Identity creation, change tickets) 1,000+ 25–30 45–60
- 3. Multi-Site Sampling Framework (IAF MD 1 / ISO/IEC 17021-1)
When an organization operates multiple operational locations under a single centralized ISMS (e.g., a retail chain with 100 branch offices or a logistics provider with 50 warehouses), certification bodies apply multi-site sampling rules defined in IAF MD 1 .
Eligibility Criteria for Multi-Site Sampling
All sites operate under a single, centrally managed and administered ISMS.
All sites are subject to central management review and internal audit programs.
All sites follow uniform security policies, procedures, and control frameworks.
Mathematical Sampling Formulas
For a normal risk profile, the minimum number of sites to be sampled per audit cycle is calculated using the square-root formula: Sample Size ( y ) = x \text{Sample Size } (y) = \sqrt{x} Sample Size ( y ) = x
Where x x x is the total number of operational sites.
Normal Risk : y = x y = \sqrt{x} y = x (rounded up to the next whole number).
High Risk / Complex Operations : y = 1.2 x y = 1.2 \sqrt{x} y = 1.2 x .
Low Risk / Simplified Operations : y = 0.6 x y = 0.6 \sqrt{x} y = 0.6 x .
Example : For an organization with x = 49 x = 49 x = 49 identical branch offices operating under a single central ISMS, the Lead Auditor must sample at least y = 49 = 7 y = \sqrt{49} = 7 y = 49 = 7 sites during the certification audit.
4. Managing Sampling Risk and Exception Handling
Sampling risk manifests in two dangerous forms:
Risk of Incorrect Acceptance (Beta Risk) : The auditor concludes a control is effective based on a sample when, in reality, the population contains unacceptable nonconformities. (High security impact).
Risk of Incorrect Rejection (Alpha Risk) : The auditor concludes a control is ineffective based on an unrepresentative bad sample when the overall population is compliant. (Efficiency impact).
The Auditor's Exception Rule
If an auditor selects a sample of 25 items and encounters one single nonconformity (exception), the auditor must NOT simply ignore it as an anomaly. The Lead Auditor must take one of two actions:
Expand the Sample : Double the sample size (e.g., test an additional 25 items) to determine whether the exception was an isolated incident or systemic failure.
Investigate Root Cause : Require the auditee to explain the specific breakdown before determining whether to issue a Minor or Major Nonconformity.
- 5. Worked Scenario: Sampling User Off-Boarding Access Revocations
- Background
Lead Auditor Nathan was evaluating Annex A 6.5 (Responsibilities after termination or change of employment) and Annex A 8.2 (Privileged access rights) at Global Logistics Corp. The HR termination log showed that 400 employees departed the company during the 12-month audit period.
Sampling Plan Execution
Determining Sample Size : Applying the sample size matrix for continuous/frequent manual controls, Nathan selected a initial sample size of 30 terminated employee records using systematic random sampling across all four quarterly HR termination reports.
Audit Requirement : Company policy mandated that all network, VPN, and application access must be revoked within 24 hours of the employee's official termination date.
Testing Results & Sample Expansion
Out of the 30 sampled records, 27 records showed full access revocation executed within 12 to 18 hours.
However, records #14 and #22 showed that access to the production ERP system remained active for 14 days and 30 days post-termination, respectively. Record #22 belonged to a departed IT Administrator who had logged into the ERP system 5 days after leaving the company.
Auditor Decision
Because two severe exceptions were identified in the initial sample of 30, Nathan expanded the sample by an additional 30 records (totaling 60 records).
In the expanded sample of 30 additional records, Nathan identified 5 additional instances of delayed access revocation exceeding 15 days.
Conclusion
The expanded sample proved that the exception was not an isolated error, but a systemic control breakdown between HR notification and IT access management. Nathan documented a Major Nonconformity against Clause 8.1 (Operational planning and control) and Annex A 6.5 , citing a 11.6% failure rate across the total sample of 60 records.