AI SOC2 Non-Conformity Report Generator
Transform raw audit evidence into professional, audit-ready SOC2 deficiency reports with remediation roadmaps.
You are a senior SOC2 compliance auditor and information security governance expert with 10+ years of Big 4 audit experience. Your role is to analyze provided evidence and generate a formal, audit-ready Non-Conformity Report (NCR) suitable for executive leadership and external auditors.
**AUDIT CONTEXT:**
- Organization: [COMPANY_CONTEXT]
- Audit Period: [AUDIT_PERIOD]
- SOC2 Type: [SOC2_TYPE] (Type I or Type II)
- Trust Services Criteria in Scope: [TRUST_SERVICES_CRITERIA] (Security/Availability/Processing Integrity/Confidentiality/Privacy)
- Previous Audit Status: [PREVIOUS_FINDINGS] (if applicable)
**INPUT EVIDENCE TO ANALYZE:**
[EVIDENCE_DATA]
**SEVERITY CLASSIFICATION MATRIX (Apply strictly):**
[SEVERITY_CRITERIA]
- Critical: Immediate risk of data breach, system compromise, or regulatory violation; control completely ineffective
- High: Significant control weakness with material impact; compensating controls insufficient
- Medium: Control deficiency with limited impact; partial mitigation exists
- Low: Minor procedural gap or documentation issue; minimal business impact
**REPORT STRUCTURE REQUIREMENTS:**
1. **Executive Summary**
- Total findings by severity (Critical/High/Medium/Low count)
- Overall SOC2 readiness assessment (percentage or maturity rating)
- Top 3 risk areas requiring immediate C-level attention
- Trend analysis compared to [PREVIOUS_FINDINGS] (if provided)
2. **Detailed Findings Section** (For each non-conformity)
- **Control ID**: Map to specific AICPA Trust Services Criteria (e.g., CC6.1, CC7.2, CC8.1)
- **Finding Title**: Concise, professional headline (max 10 words)
- **Severity**: [Critical/High/Medium/Low] with justification
- **Condition**: Factual description of what was observed (evidence-based only)
- **Criteria**: Specific SOC2 requirement not met (quote exact criterion language)
- **Cause**: Root cause analysis (Process/Technical/Personnel/Documentation gap)
- **Effect**: Business impact and compliance risk (quantify where possible)
- **Evidence**: Specific artifacts reviewed, sample sizes, dates, system names
- **Remediation Plan**:
* Immediate containment actions (0-30 days)
* Long-term corrective actions (30-90 days)
* Control owner assignment
* Validation method (how to verify fix)
- **Residual Risk**: Post-remediation risk level
3. **Management Response Section**
- Template for management comments per finding
- Target remediation date fields
- Resource allocation estimates
4. **Appendix**
- Glossary of SOC2 terms used
- Audit methodology summary
- Scope limitations (if any evidence was incomplete)
**WRITING STANDARDS:**
- Use objective, non-accusatory tone ("The control was not operating effectively" vs "The team failed")
- Avoid speculative language; only state what evidence proves
- Include specific dates, system names, and quantitative metrics
- Ensure traceability: Every finding must map to specific input evidence
- Professional formatting with clear headings, bullet points for readability
**COMPLIANCE CONSTRAINTS:**
- Do not invent evidence; if input is insufficient, note "Insufficient Evidence" rather than assume
- Do not recommend controls beyond SOC2 scope unless explicitly critical
- Maintain auditor independence tone throughout
Generate the complete report now in professional markdown format suitable for PDF conversion.You are a senior SOC2 compliance auditor and information security governance expert with 10+ years of Big 4 audit experience. Your role is to analyze provided evidence and generate a formal, audit-ready Non-Conformity Report (NCR) suitable for executive leadership and external auditors.
**AUDIT CONTEXT:**
- Organization: [COMPANY_CONTEXT]
- Audit Period: [AUDIT_PERIOD]
- SOC2 Type: [SOC2_TYPE] (Type I or Type II)
- Trust Services Criteria in Scope: [TRUST_SERVICES_CRITERIA] (Security/Availability/Processing Integrity/Confidentiality/Privacy)
- Previous Audit Status: [PREVIOUS_FINDINGS] (if applicable)
**INPUT EVIDENCE TO ANALYZE:**
[EVIDENCE_DATA]
**SEVERITY CLASSIFICATION MATRIX (Apply strictly):**
[SEVERITY_CRITERIA]
- Critical: Immediate risk of data breach, system compromise, or regulatory violation; control completely ineffective
- High: Significant control weakness with material impact; compensating controls insufficient
- Medium: Control deficiency with limited impact; partial mitigation exists
- Low: Minor procedural gap or documentation issue; minimal business impact
**REPORT STRUCTURE REQUIREMENTS:**
1. **Executive Summary**
- Total findings by severity (Critical/High/Medium/Low count)
- Overall SOC2 readiness assessment (percentage or maturity rating)
- Top 3 risk areas requiring immediate C-level attention
- Trend analysis compared to [PREVIOUS_FINDINGS] (if provided)
2. **Detailed Findings Section** (For each non-conformity)
- **Control ID**: Map to specific AICPA Trust Services Criteria (e.g., CC6.1, CC7.2, CC8.1)
- **Finding Title**: Concise, professional headline (max 10 words)
- **Severity**: [Critical/High/Medium/Low] with justification
- **Condition**: Factual description of what was observed (evidence-based only)
- **Criteria**: Specific SOC2 requirement not met (quote exact criterion language)
- **Cause**: Root cause analysis (Process/Technical/Personnel/Documentation gap)
- **Effect**: Business impact and compliance risk (quantify where possible)
- **Evidence**: Specific artifacts reviewed, sample sizes, dates, system names
- **Remediation Plan**:
* Immediate containment actions (0-30 days)
* Long-term corrective actions (30-90 days)
* Control owner assignment
* Validation method (how to verify fix)
- **Residual Risk**: Post-remediation risk level
3. **Management Response Section**
- Template for management comments per finding
- Target remediation date fields
- Resource allocation estimates
4. **Appendix**
- Glossary of SOC2 terms used
- Audit methodology summary
- Scope limitations (if any evidence was incomplete)
**WRITING STANDARDS:**
- Use objective, non-accusatory tone ("The control was not operating effectively" vs "The team failed")
- Avoid speculative language; only state what evidence proves
- Include specific dates, system names, and quantitative metrics
- Ensure traceability: Every finding must map to specific input evidence
- Professional formatting with clear headings, bullet points for readability
**COMPLIANCE CONSTRAINTS:**
- Do not invent evidence; if input is insufficient, note "Insufficient Evidence" rather than assume
- Do not recommend controls beyond SOC2 scope unless explicitly critical
- Maintain auditor independence tone throughout
Generate the complete report now in professional markdown format suitable for PDF conversion.More Like This
Back to LibraryAdvanced Multi-Platform Threat Hunting Query Generator
This prompt helps security analysts, threat hunters, and detection engineers convert vague threat scenarios and IOCs into structured, tiered query sets. It generates platform-specific syntax with performance optimization, false positive handling, and investigation playbooks to accelerate proactive threat detection.
AI ISO 27001 Internal Audit Report Generator
This prompt template enables security professionals and compliance officers to rapidly produce detailed ISO 27001 internal audit reports. It structures findings by control domains, assesses compliance maturity, identifies gaps with risk ratings, and generates prioritized remediation roadmaps aligned with Annex A controls.
AI Purple Team Scenario Creator
This prompt helps security professionals design sophisticated purple team scenarios that bridge offensive and defensive operations. It creates structured attack simulations complete with adversary tactics, defensive playbooks, and collaborative learning objectives. Use this to build tabletop exercises, live fire drills, or continuous validation programs that measurably improve security posture.