安全事件应急处置方案制定
根据事件线索梳理首小时行动、证据保全、遏制恢复与沟通安排,并提示法律事项需专业确认。
完整提示词
<context>
Under pressure, responders make the same mistakes: they wipe and rebuild a compromised host before capturing evidence, so nobody learns how the attacker got in; they rotate one credential while the attacker holds three others; they coordinate in the same chat or email system the attacker may be reading; they announce containment steps that tip the attacker off before access is cut everywhere; and nobody keeps a log of decisions, which later matters for regulators, insurers and the postmortem. The response follows the familiar phases (detection and analysis, containment, eradication, recovery, lessons learned), but the order of the first actions decides most of the outcome.
</context>
<task>
Plan the response to:
<incident>
{{incident}}
</incident>
{{#environment}}
Environment:
{{environment}}
{{/environment}}
1. **Assess.** Separate what is known from what is assumed. Give a provisional severity (critical, high, medium, low) with the reason: data involved, attacker access still live or not, systems affected. List the three questions whose answers would most change the plan, and how to answer each quickly. If the description is too thin to assess, ask those questions first.
2. **Organise.** Name the roles to fill now: incident lead, technical lead, scribe keeping a timestamped decision log, communications owner. Move coordination to a channel the attacker is unlikely to control if any company accounts may be compromised.
3. **First hour.** An ordered checklist of the actions that limit damage without destroying evidence.
4. **Preserve evidence** before changing systems: disk snapshots, memory capture where feasible, exports of cloud audit logs, identity provider logs and application logs before their retention expires, with hashes and a record of who collected what and when.
5. **Contain.** A table of options (disable accounts, revoke sessions and tokens, rotate keys, isolate hosts or networks, block indicators, take a service offline), each with its effect, its risk of alerting the attacker, and whether it is reversible. Recommend an order, and coordinate credential revocation so all of the attacker's access is cut at once rather than piecemeal.
6. **Eradicate and recover.** Find and close the entry point, remove persistence (new users, keys, scheduled tasks, modified images or CI pipelines), rebuild from known-good sources, restore data from backups taken before the compromise, and watch closely for the attacker returning.
7. **Communicate.** Who must hear what and when: internal leadership, legal counsel and the privacy or data protection officer, customers, the cyber insurer, and law enforcement where appropriate. Flag that personal-data breaches can carry short legal notification deadlines (some regimes require notice within 72 hours) and that counsel decides what applies.
</task>
<constraints>
- Never recommend wiping, reimaging or deleting anything before evidence is preserved, unless lives or critical safety are at stake.
- Do not recommend contacting, paying or negotiating with an attacker; route any ransom question to leadership, counsel, the insurer and law enforcement.
- Do not state legal obligations as settled; name them as questions for legal counsel.
- Mark every inference as an inference. If unsure of a tool's exact command, describe the action instead of guessing syntax.
</constraints>
<output_format>
## Assessment
Known, assumed, provisional severity, the three key questions.
## First hour
Numbered checklist with an owner role per item.
## Preserve evidence
Table: source, how to capture, retention risk, collected by.
## Containment options
Table: action, effect, tip-off risk, reversible, recommended order.
## Eradication and recovery
Numbered steps.
## Communication
Table: audience, what, when, channel, owner.
## Unknowns
Bullets with how to resolve each.
## After the incident
Postmortem, control gaps to fix, and what to keep from the decision log.
</output_format>可替换内容
- {{incident}}
- {{#environment}}
- {{environment}}
- {{/environment}}
分类与标签
编程开发、安全事件响应、证据保全、账号处置、系统恢复、应急沟通