compliance-tracking · 整理审计控制与证据缺口

作者提供的示例，实际效果取决于你的输入和使用工具。

输入

编辑构造材料（未运行）：
内部确认控制 C01：每季度复核权限；负责人甲；证据为 6月30日复核表；审计日10月15日。C02：保留备份恢复演练记录；负责人乙；当前无记录。未提供第三季度 C01 复核。

输出

编辑示例 · 未运行

控制	已有证据	准备状态	下一份材料
C01 季度权限复核	6月30日表	第三季度证据待补	补该季度复核记录或解释未执行原因
C02 恢复演练	未提供	证据缺口	获取真实演练记录及日期；未演练则登记整改

这是一份审计准备表，不是 SOC 2、ISO 或其它认证结论。

---
name: compliance-tracking
description: Track compliance requirements and audit readiness. Trigger with "compliance", "audit prep", "SOC 2", "ISO 27001", "GDPR", "regulatory requirement", or when the user needs help tracking, preparing for, or documenting compliance activities.
---

# Compliance Tracking

Help track compliance requirements, prepare for audits, and maintain regulatory readiness.

## Common Frameworks

| Framework | Focus | Key Requirements |
|-----------|-------|-----------------|
| SOC 2 | Service organizations | Security, availability, processing integrity, confidentiality, privacy |
| ISO 27001 | Information security | Risk assessment, security controls, continuous improvement |
| GDPR | Data privacy (EU) | Consent, data rights, breach notification, DPO |
| HIPAA | Healthcare data (US) | PHI protection, access controls, audit trails |
| PCI DSS | Payment card data | Encryption, access control, vulnerability management |

## Compliance Tracking Components

### Control Inventory
- Map controls to framework requirements
- Document control owners and evidence
- Track control effectiveness

### Audit Calendar
- Upcoming audit dates and deadlines
- Evidence collection timelines
- Remediation deadlines

### Evidence Management
- What evidence is needed for each control
- Where evidence is stored
- When evidence was last collected

### Gap Analysis
- Requirements vs. current state
- Prioritized remediation plan
- Timeline to compliance

## Output

Produce compliance status dashboards, gap analyses, audit prep checklists, and evidence collection plans.

先看看示例

输入

输出

方法说明