audit-sampling-methods
Guides privacy audit sampling methodology including statistical and non-statistical sampling, sample size determination, stratification techniques, attribute sampling for compliance testing, confidence level selection, tolerable deviation rates, and extrapolation of results to the population. Keywords: audit sampling, statistical sampling, attribute testing, sample size, confidence level, stratified sampling, privacy audit.
- Installs
- 46
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill audit-sampling-methods- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads audit-sampling-methods automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Privacy Audit Sampling Methods
Overview
Audit sampling is the application of audit procedures to less than 100% of items within a population to form a conclusion about the entire population. In privacy auditing, sampling is used to test compliance of processing activities, DSAR responses, consent records, vendor contracts, and other privacy controls without examining every individual record.
ISA 530 (International Standard on Auditing — Audit Sampling) and IIA Practice Advisory 2320-3 (Audit Sampling) provide the authoritative frameworks. For privacy audits, sampling must account for the heightened regulatory scrutiny of personal data processing and the potential for significant harm from individual non-compliant records.
Sampling Approaches
| Approach | Description | When to Use |
|---|---|---|
| Statistical Sampling | Uses probability theory to select samples and evaluate results; allows quantification of sampling risk | When audit conclusions must be defensible to regulators; large populations; need to extrapolate results |
| Non-Statistical (Judgemental) Sampling | Auditor uses professional judgement to select items | Small populations; targeted testing of known risk areas; supplementary to statistical sampling |
Statistical Sampling Methods
Attribute Sampling
Used to estimate the rate of deviation (non-compliance) in a population.
| Parameter | Description | Typical Privacy Audit Values |
|---|---|---|
| Population Size | Total items in the auditable population | e.g., 1,000 DSARs, 500 vendor contracts |
| Confidence Level | Probability that sample results reflect the population | 90% (standard); 95% (regulatory-facing) |
| Tolerable Deviation Rate | Maximum acceptable non-compliance rate | 5% (standard); 2% (critical controls) |
| Expected Deviation Rate | Estimated actual non-compliance rate | Based on prior audits or risk assessment |
| Sample Size | Number of items to test | Calculated from above parameters |
Sample Size Reference Table (Attribute Sampling)
| Population | 90% Confidence / 5% Tolerable | 95% Confidence / 5% Tolerable | 95% Confidence / 2% Tolerable |
|---|---|---|---|
| 100 | 38 | 45 | 64 |
| 250 | 42 | 50 | 100 |
| 500 | 44 | 54 | 131 |
| 1,000 | 45 | 57 | 154 |
| 5,000 | 46 | 59 | 176 |
| 10,000+ | 46 | 59 | 181 |
Stratified Sampling
Divides the population into subgroups (strata) and samples proportionally or disproportionately from each.
| Stratification Factor | Example Strata | Rationale |
|---|---|---|
| Business Unit | EU, US, APAC | Different regulatory requirements per jurisdiction |
| Data Sensitivity | Standard, sensitive, special category | Higher-risk data categories warrant more testing |
| Processing Purpose | Marketing, HR, customer service | Different compliance requirements per purpose |
| Time Period | Q1, Q2, Q3, Q4 | Detect seasonal patterns or deterioration |
| Vendor Tier | Tier 1 (high volume), Tier 2, Tier 3 | Focus sampling on highest-risk vendors |
Non-Statistical Sampling Methods
| Method | Description | Application |
|---|---|---|
| Haphazard Selection | Items selected without structured method but avoiding bias | Quick preliminary testing |
| Block Selection | All items in a specific period or location | Testing a specific time window (e.g., all DSARs in March) |
| Judgemental Selection | Auditor selects items based on risk factors | Targeting high-value items, known exceptions, or anomalies |
Privacy-Specific Sampling Considerations
| Consideration | Guidance |
|---|---|
| Individual harm threshold | Even a single non-compliant record can cause significant harm; auditors must not dismiss isolated findings |
| Regulatory expectations | Supervisory authorities may expect higher confidence levels for critical controls (breach notification, consent) |
| Special category data | Apply lower tolerable deviation rates (2%) for processing involving special category data under Article 9 |
| Automated processing | For fully automated processes, increase sample to verify algorithmic consistency across edge cases |
| Cross-border transfers | Stratify by destination country to verify adequacy/safeguard mechanism for each transfer route |
Evaluating Sample Results
| Scenario | Sample Deviation Rate | Conclusion |
|---|---|---|
| Rate below tolerable deviation | e.g., 2% observed vs 5% tolerable | Population likely compliant; no material finding |
| Rate equals tolerable deviation | e.g., 5% observed vs 5% tolerable | Borderline; consider expanding sample or raising as medium finding |
| Rate exceeds tolerable deviation | e.g., 12% observed vs 5% tolerable | Material non-compliance; formal finding required |
| Zero deviations found | 0% observed | Strong evidence of compliance (but does not guarantee 100%) |
Extrapolation
When sample results show deviations, the auditor must project findings to the full population:
| Element | Calculation |
|---|---|
| Point estimate | (Deviations found / Sample size) × Population size |
| Upper deviation limit | Calculated using statistical tables at the selected confidence level |
| Projected monetary impact | Point estimate × average impact per deviation |
FAQ
What does the audit-sampling-methods skill do?
Guides privacy audit sampling methodology including statistical and non-statistical sampling, sample size determination, stratification techniques, attribute sampling for compliance testing, confidence level selection, tolerable deviation rates, and extrapolation of results to the population. Keywords: audit sampling, statistical sampling, attribute testing, sample size, confidence level, stratified sampling, privacy audit.
How do I install audit-sampling-methods?
Run npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill audit-sampling-methods in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/audit-sampling-methods/ (personal) or .claude/skills/audit-sampling-methods/ (project).
Which AI agents can use audit-sampling-methods?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is audit-sampling-methods safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains audit-sampling-methods?
It is published by mukul975 in mukul975/privacy-data-protection-skills. It has 46 recorded installs.
More from mukul975/privacy-data-protection-skills
brazil-lgpd
mukul975/privacy-data-protection-skills
Open the skill to read its SKILL.md instructions.
analytics-cookie-consent
mukul975/privacy-data-protection-skills
Open the skill to read its SKILL.md instructions.
audit-report-writing
mukul975/privacy-data-protection-skills
Open the skill to read its SKILL.md instructions.
conducting-gdpr-dpia
mukul975/privacy-data-protection-skills
Open the skill to read its SKILL.md instructions.
gdpr-compliance-audit
mukul975/privacy-data-protection-skills
Open the skill to read its SKILL.md instructions.
backup-retention-erasure
mukul975/privacy-data-protection-skills
Open the skill to read its SKILL.md instructions.
Popular security skills
azure-compliance
microsoft/azure-skills
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
firebase-security-rules-auditor
firebase/agent-skills
Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.
audit
pbakaus/impeccable
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
competitors
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.