Problem Statement
Organizations need a structured, privacy‑safe process for defining logging rules across their systems. Teams must ensure logs are useful for debugging and auditing while preventing exposure of sensitive or unnecessary data. This workflow guides users from inventorying existing logs to implementing redaction, retention, and rollout plans aligned with least‑privilege principles.
Steps
Ingest Logging Context
INGESTCollect system descriptions, data types handled, compliance constraints, and known logging gaps. Consolidate them into a unified view for further processing.
Classify Data Types
EXECUTEAnalyze the provided systems and data types to categorize information into PII, sensitive, operational, and safe-to-log categories. This classification enables least‑privilege logging decisions.
Define Redaction and Logging Rules
EXECUTEGenerate actionable logging do/don’t lists and PII redaction rules based on the data classification and compliance constraints. Ensure guidance remains general and avoids legal advice.
Recommend Retention Policies
EXECUTEProvide retention windows aligned with privacy principles, risk posture, and operational needs. Include constraints for minimizing long‑term storage of sensitive fields.
Produce Rollout and Audit Guidance
EXECUTEGenerate a practical rollout checklist and recurring audit steps to verify correct implementation and ongoing compliance with least‑privilege logging standards.
Prompt Configurations
Logging Rules Generation
You are an expert privacy‑minded logging advisor. Using the provided system descriptions, data types, compliance constraints, and logging gaps, produce: 1. Logging do/don’t rules. 2. PII redaction guidelines. 3. Three examples of strong, privacy‑safe log events. 4. Retention policy recommendations. 5. A rollout checklist. Tone: firm, practical, and responsible. Constraints: - Keep all content high-level and general. - Do not provide legal advice. - Apply least‑privilege principles. - Do not invent system details; only use what is provided.
Example Inputs/Outputs
Systems: customer support portal, authentication service. Data types: names, emails, session IDs, error traces. Compliance: GDPR, internal privacy rules. Gaps: sensitive fields appear in auth logs.
Generated logging do/don’t list emphasizing least‑privilege use; PII redaction rules (mask emails, truncate session IDs); example log events showing structured, redacted entries; retention guidance recommending short windows for auth logs; rollout checklist including developer updates, QA validation, and quarterly audits.