mcpField
A
audit-report-writing

audit-report-writing

github.com/mukul975Security32350 installsUpdated 32w ago
Repository

About audit-report-writing

A skill for turning privacy audit fieldwork into structured reports for governance, management, and regulatory stakeholders. It covers report sections, evidence, findings, severity ratings, and quality criteria.

Key features

  1. 01Standard report sections
  2. 02Finding severity classification
  3. 03Evidence referencing
  4. 04Executive summary guidance
  5. 05Report quality criteria

Use cases

  1. 01Drafting a privacy audit report
  2. 02Documenting findings and evidence
  3. 03Summarizing compliance risks
  4. 04Preparing reports for stakeholders

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill audit-report-writing

After installing, type/audit-report-writingin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

assets/
template.md
references/
standards.md
workflows.md
scripts/
process.py

Details

From the project README

Privacy Audit Report Writing

Overview

Privacy audit report writing is the discipline of translating audit fieldwork into a structured, defensible written deliverable that communicates audit objectives, methodology, findings, and recommendations to stakeholders. A well-crafted audit report serves as the primary vehicle for communicating the state of privacy compliance to governance bodies, management, regulators, and data protection authorities.

Under GDPR Article 39(1)(b), the Data Protection Officer must monitor compliance including audits, meaning audit reports are a key instrument of DPO oversight. ISO 19011:2018 (Guidelines for auditing management systems) Section 6.6 provides the international standard framework for audit report content and distribution.

Report Structure

Standard Sections
SectionPurposeTypical Length
Cover PageReport identification, classification, distribution list1 page
Executive SummaryHigh-level findings, overall opinion, critical issues1-2 pages
Table of ContentsNavigation aid1 page
Audit Scope and ObjectivesWhat was audited, boundaries, exclusions1-2 pages
MethodologyAudit approach, sampling, tools used1-2 pages
Findings and ObservationsDetailed findings with evidence, risk rating, root cause5-20 pages
RecommendationsPrioritised corrective actions2-5 pages
Management ResponseAuditee agreement/disagreement, action plans, deadlines2-5 pages
AppendicesEvidence references, sampling details, interview logsVariable

Findings Classification

Severity Ratings
RatingDefinitionResponse Timeline
CriticalMaterial non-compliance creating immediate risk of regulatory enforcement, data breach, or significant harm to data subjectsImmediate remediation; board notification within 24 hours
HighSignificant control weakness or non-compliance that could lead to a breach or regulatory action if not addressedRemediation plan within 14 days; completion within 60 days
MediumControl deficiency that does not currently pose immediate risk but could deteriorateRemediation within 90 days
LowOpportunity for improvement; minor procedural gapRemediation within 180 days or next audit cycle
ObservationGood practice note or suggestion; not a formal findingNo mandatory action

Finding Documentation Format

Each finding should include:

ElementDescription
Finding IDUnique identifier (e.g., AUDIT-2026-001)
TitleConcise descriptive title
ConditionWhat was observed (the current state)
CriteriaWhat was expected (the standard, policy, or regulation)
CauseRoot cause analysis (why the gap exists)
EffectImpact or potential impact of the finding
Risk RatingCritical / High / Medium / Low
RecommendationSpecific corrective action
Management ResponseAuditee's response, action plan, responsible owner, deadline
Evidence ReferenceDocument IDs, screenshots, interview notes

Executive Summary Writing

The executive summary must:

  1. State the audit scope, period, and objectives in one paragraph
  2. Provide an overall compliance opinion (satisfactory, needs improvement, unsatisfactory)
  3. Summarise the distribution of findings by severity
  4. Highlight any critical or high findings requiring immediate attention
  5. Note positive observations and areas of strong compliance
  6. Conclude with the overall risk posture assessment

Evidence Referencing

Evidence Types
TypeExampleReference Format
DocumentaryPolicy documents, procedures, recordsDOC-001: "Data Retention Policy v3.2, dated 15-Jan-2026"
TestimonialInterviews, walkthroughsINT-001: "Interview with DPO, 10-Mar-2026, 14:00-15:00"
AnalyticalData analysis, sampling resultsANA-001: "DSAR response time analysis, Q4 2025"
ObservationalSystem screenshots, process observationOBS-001: "Screenshot of consent banner, captured 12-Mar-2026"

Report Quality Criteria

CriterionStandard
AccuracyAll findings supported by verified evidence; factual errors corrected before issuance
ObjectivityBalanced presentation; positive observations included alongside findings
ClarityPlain language; technical terms defined; avoid jargon
CompletenessAll scope areas addressed; no material omissions
ConstructivenessRecommendations are actionable, specific, and proportionate
TimelinessDraft report issued within 10 business days of fieldwork completion
ConcisenessNo unnecessary repetition; findings are distinct

Distribution and Confidentiality

ClassificationRecipients
Full ReportChief Privacy Officer, DPO, Internal Audit Director, auditee management
Executive Summary OnlyBoard Audit Committee, C-suite
Redacted VersionExternal regulators (on request), external auditors
Finding-Specific ExtractsIndividual finding owners for remediation tracking

GDPR and Regulatory Context

RegulationAudit Report Relevance
GDPR Article 5(2)Accountability principle — audit reports demonstrate compliance monitoring
GDPR Article 24Controller must implement appropriate measures and be able to demonstrate compliance
GDPR Article 28(3)(h)Processor must allow and contribute to audits conducted by the controller
GDPR Article 39(1)(b)DPO must monitor compliance including assignments of responsibilities, awareness-raising, training, and related audits
GDPR Article 47(2)(j)BCRs must include audit mechanisms
ISO 27701:2019 Section 5.2PIMS-specific audit requirements
ISO 19011:2018 Section 6.6Preparing and distributing the audit report

Comments

Markdown supported