返回提示词目录第 1146 页

制定SOC 2审计准备项目计划

梳理审计范围、控制缺口、负责人及证据收集安排,形成时间表并列出需专业确认事项。

完整提示词

<context>
SOC 2 is an attestation by a licensed CPA firm against the AICPA Trust Services Criteria; security is always in scope and availability, confidentiality, processing integrity and privacy are optional. A Type I report covers control design at a point in time; a Type II report covers operating effectiveness over an observation period, typically three to twelve months, which is why the timeline is driven by when controls start running, not when the audit starts. Small companies underestimate the non-engineering controls (HR onboarding and offboarding, background checks where lawful, security training, vendor management, risk assessment, board or management oversight) and the evidence burden: every control needs proof it ran, every time. Scoping tightly (the production system that customers' data touches) and choosing which optional criteria to include are the biggest levers on effort.

{{> guardrails/professional-limits}}
</context>

<task>
Company: {{company}}
{{#target}}Target: {{target}}{{/target}}

1. Scope and report type: systems, data and teams in scope, which Trust Services Criteria to include and why, Type I versus going straight to Type II, given the customer driver and dates.
2. Gap list: group typical control areas (governance and risk assessment, policies, access management and reviews, onboarding and offboarding, change management and code review, vulnerability management and patching, logging and monitoring, incident response, backups and disaster recovery, vendor management, encryption, endpoint security, security awareness training, availability) and mark each as likely in place, partial or missing based on the input, with what is needed to close it. Say these are typical areas, not the auditor's control list.
3. Workstreams and owners: policies, engineering controls, HR controls, vendor and risk, evidence; each with an owner role and the effort as a range.
4. Timeline: readiness work, controls operating, a readiness assessment (optional), auditor selection and kickoff, Type I fieldwork, the Type II observation window, and report delivery. Show the critical path and whether the target date is realistic.
5. Evidence and tooling: how evidence will be collected (manual with a shared tracker, or a compliance automation platform), trade-offs of each, and the evidence that is easiest to get wrong (access reviews on schedule, offboarding within the stated time, change approvals).
6. Ongoing operation: the recurring control calendar (quarterly access reviews, annual risk assessment and policy review, training, restore tests).
7. What to check with the auditor and advisers: scope, criteria, observation period, and anything legal (background checks, data processing terms).
</task>

<constraints>
- Do not name specific auditor firms or vendors as recommendations; describe the selection criteria.
- Do not claim a control set is what the auditor will require; controls are agreed with the auditor.
- Do not promise pass or timing outcomes; give realistic ranges and dependencies.
{{> output/uncertainty}}
</constraints>

<output_format>
## Scope and report type
## Gap list
Table: Area | Status (in place, partial, missing) | What is needed | Owner.
## Workstreams and owners
## Timeline
Table: Month | Milestone | Depends on.
## Evidence and tooling
## Ongoing operation
Table: Control activity | Frequency | Owner.
## What to check with the auditor
</output_format>

可替换内容

  • {{> guardrails/professional-limits}}
  • {{company}}
  • {{#target}}
  • {{target}}
  • {{/target}}
  • {{> output/uncertainty}}

分类与标签

办公效率、审计准备、项目排期、跨部门协作、证据管理

前往 AI 图片创作