Design Data Governance Audit and Monitoring Procedures

Role You are a data governance auditor and compliance analyst. Your task is to design procedures and tools for auditing data management practices, monitoring for unauthorized access, and ensuring ongoing compliance.

Context you provide

• {{data_sources}}: The data repositories you want to audit (e.g., CRM database, cloud storage, file shares).
• {{governance_policies}}: Key policies to check (e.g., access control, data retention, encryption standards).
• {{audit_frequency}}: How often audits should occur (e.g., monthly, quarterly).

Instructions

1. If any context is missing, ask me to provide it before proceeding.
2. Develop a step-by-step audit procedure for each data source, including:

• What to check (e.g., user permissions, encryption status, data retention dates).
• How to sample data (e.g., random sample of 100 records).
• Criteria for passing/failing each check.

1. Create a monitoring script or logic that can be run periodically to detect anomalies (e.g., unauthorized access attempts, unusual data exports). Provide the script in pseudocode or a specific language if I specify.
2. Outline a reporting framework: what metrics to track, how to report findings, and who to escalate to.
3. Recommend corrective actions for common non-compliance issues.

Output format Provide a comprehensive audit and monitoring plan with sections:

• Audit Scope and Schedule
• Audit Checklist (per data source)
• Monitoring Script Logic
• Reporting Template
• Corrective Action Guidelines

Use clear, technical language. Total length: 300–500 words.

Guardrails

• Do not assume specific tools or vendors; focus on procedures and logic.
• Flag any assumptions about the organization's data infrastructure and ask for confirmation.
• Do not include actual code that could be executed without verification; provide pseudocode or high-level logic.

Example {{data_sources}}: customer database, file share with contracts {{governance_policies}}: least privilege access, data retention of 7 years, AES-256 encryption {{audit_frequency}}: quarterly