资源 · 08

网络事件演练:在危机发生前测试决策

构建一个真实的场景,在不中断生产的情况下测试协调、连续性、证据、沟通和服务恢复。

已更新 · 10 min

虚构的无人网络危机演练室:电话、连续性文件夹和玻璃后的服务器 由人工智能生成的编辑插图

本指南有助于实现的目标

  • 明确压力下的决策者
  • 测试备用渠道
  • 验证实际恢复顺序
  • 将差距转化为可验证的行动

快速检查

  • 该场景是否针对特定能力?
  • 是否有离线危机联系人?
  • 谁可以隔离系统?
  • 哪个服务必须首先恢复?
  • 谁通知客户、当局和合作伙伴?

分步指南

  1. 1

    定义目标

    选择两到三个要测试的能力:资格认证、决策、遏制、业务连续性、通知或恢复。 说明哪些内容超出范围。

    交付成果:任务和成功标准。

  2. 2

    构建一个合理的场景

    从真实的资产和依赖关系入手。 逐步添加故障、冲突信息、外部压力和业务限制,避免制造噱头。

    交付成果:保密的主场景。

  3. 3

    准备角色和注入点

    指定演练控制人员、观察员和参与者。 每次注入点都应触发可观察的决策,而不仅仅是传递信息。

    交付成果:时间线和注入点卡片。

  4. 4

    确保演练过程中不会出现人员被困的情况

    解释规则,区分模拟和真实事件,保护生产环境,并允许团队使用其正常流程。

    交付成果:决策和沟通日志。

  5. 5

    进行两次总结

    首先记录观察到的事实,然后分析原因、权衡和依赖关系。 区分文档缺失、权限缺失和技术问题。

    交付成果:已证实的调查结果和经验教训。

  6. 6

    弥合差距

    为每项行动指定负责人、日期和证明。 重放关键步骤或测试恢复情况,而不是仅凭声明结束。

    交付成果:改进计划和确认测试。

虚构示例

示例情境

演习模拟事件发生期间支持工具的丢失。 参与者必须对信号进行评估,联系工具之外的决策者,并决定何时通知受影响人员。

决策及预期证据

记录保存决策和时间戳、缺失信息以及三个已分配的改进项及其复测日期。

管理指标

指标衡量内容首要行动
动员时间组建关键角色所需的时间确定目录和代理人
决策时间合格信号与明确决策之间的延迟明确阈值和权限
恢复顺序根据已批准的业务优先级恢复服务协调技术依赖关系和需求
行动已完成已通过验证证据弥补漏洞重现高风险点

常见错误

  • 编写过于复杂的场景
  • 评估个人而非系统
  • 忽略客户、供应商和监管机构
  • 未进行收尾测试就撰写报告

常见问题解答

演习必须使系统离线吗?

不。桌面演习测试决策,但不涉及实际技术操作。 恢复或故障转移测试需要单独的安全范围。

谁应该参与?

负责决策或执行关键操作的角色,以及在业务连续性取决于其职责时需要的代理人。

应该持续多长时间?

对于特定目标,通常需要两到四个小时,外加准备、总结和行动后续跟进。

安全事件、漏洞或数据泄露:选择合适的联系对象

CSIRT服务于明确的对象范围(constituency),例如一个组织、行业或用户群。所在国家和FIRST成员身份并不能证明您属于其服务对象、团队当前可用或提供所需服务。请在其官方网站核实这三点。

  1. 厘清事实
  2. 核实服务范围
  3. 确认官方渠道

自身系统发生安全事件

联系响应计划中指定的内部团队或服务商。如需外部协调,查找服务范围覆盖您组织的CSIRT。

核实服务对象、报告程序和工作时间;公开表单并不保证即时响应。

查找CSIRT

第三方产品存在漏洞

查看供应商的披露政策或产品安全响应团队(PSIRT)。/.well-known/security.txt文件可能列出联系信息、政策及加密方式。

核实域名、Expires字段和政策范围。security.txt不授权开展测试;发送敏感证据前应商定沟通渠道。

了解漏洞披露

涉及个人数据

除技术响应团队外,还应让数据控制者及已任命的数据保护官参与。

技术协助与可能的监管通知是两套流程。请由相关负责人确定适用的主管机关、条件和期限。

阅读数据治理专题
准备一次有效的首次联系

该清单用于准备沟通,不衡量事件严重程度或是否解决。所选内容仅保留在本页面,不会发送。

参考:FIRST、RFC 9116及CNIL(法国制度)。 FIRST · CSIRT Services Framework 2.1RFC 9116 · security.txtCNIL · Violations de données personnelles

恢复决策演练

此语言版本的详细参考说明以英语提供。

Six injects to test recovery decisions

Fictional tabletop: a supplier hosts a request-processing service. T+ times are facilitation choices, not regulatory deadlines or service levels. Each card introduces an observation and a decision to explain; no real technical action or communication is executed from this page.

T+0 · Uncertain supplier signal

The supplier reports an anomaly; a user reports an outage with no confirmed diagnosis.

Roles to involve
Incident coordinator, service owner and supplier manager.
Decision to make explicit
Who verifies the source, assesses impact and decides whether to activate the plan?
Expected evidence
Initial signal, confirmation channel, case owner and next situation update.
Debrief point
Treating a supplier statement as an established cause.
T+12 · Green backup dashboard

The dashboard shows a completed copy but supplies no candidate checks.

Roles to involve
Backup team, incident response and recovery owner.
Decision to make explicit
Which evidence is needed before authorising this copy’s use?
Expected evidence
Candidate check results, origin and acceptance or rejection decision.
Debrief point
Equating job completion with restoration-asset integrity.
T+25 · Conflicting times

Two logs have different times; one omits its time zone.

Roles to involve
Analyst, supplier operator and log keeper.
Decision to make explicit
How can both observations be retained without inventing a timeline?
Expected evidence
Original times, known or unknown zones, collection time and documented reconciliation.
Debrief point
Silently correcting the source time or erasing the contradiction.
T+40 · Rejected candidate

An integrity check finds a problem in the planned candidate. An older copy exists.

Roles to involve
Recovery owner, data owner and incident coordinator.
Decision to make explicit
Who selects another recovery point and accepts the data consequences?
Expected evidence
Reasoned rejection, new candidate, checks and expected service and data impact.
Debrief point
Skipping integrity checks to meet a demonstration schedule.
T+60 · Screen back, journey failing

Login works but a request cannot be saved in a dependent system.

Roles to involve
Business owner, operations and dependency owner.
Decision to make explicit
Is service usable, degraded or still unavailable under the agreed criteria?
Expected evidence
End-to-end test, blocking dependency, business decision and communicated limits.
Debrief point
Declaring full recovery from one reachable screen.
T+85 · Communication pressure

A public question asks for a definite return time before validation is complete.

Roles to involve
Communications, incident coordination, leadership and critical supplier.
Decision to make explicit
Which approved message states confirmed facts, limits and the next update without promising an unsupported time?
Expected evidence
Message version, approver, intended audience and supplier coordination record.
Debrief point
Presenting a provisional estimate as a verified commitment.

Four questions before closing an exercise observation

Four questions before closing an exercise observation
QuestionEvidence of progressLimit
Was authority clear?A decision actually made by the expected role, with tested cover.An organisation chart does not prove the person can be reached.
Was the check performed?Test evidence and a reviewed result within its scope.A procedure alone is not execution evidence.
Does the gap have an owner?Assigned action, local due date and verification criterion.An overall success percentage does not describe residual risk.
Was the correction replayed?The same situation rerun after correction with comparable evidence.Documentary closure does not replace useful verification.

Explore NIST outcomes and the timeline →

Primary references and limits

Identifiers and outcome meanings come from CSF 2.0; SP 800-61r3 adds incident response and recovery recommendations. Evidence tables, times and scenarios are educational, with no client results, certification or actual notification.

References reviewed

OSINT:证据保全

此语言版本的详细参考说明以英语提供。

Exercise the preservation dossier too

Inject a copy with a different digest, a missing receipt and a time without a timezone. The goal is to recognise evidence limits and choose the next check.

  • Test that redacted derivatives retain lineage without replacing the reference object.
  • Check who can change the object, digest and log together.
  • Expose gaps in the report instead of filling them with assumptions.

See copy lineage and the eight preservation cases →

Sources reviewed on · NIST · Digital Evidence Preservation · NIST IR 8387 · Full report · NIST · SP 800-86 · NIST SP 800-86 · Full report · NIST · FIPS 180-4 · Secure Hash Standard

探索 NIST CSF 2.0 成果

此语言版本的详细参考说明以英语提供。

Assess preparedness, then improve it

An exercise does not replace risk management. It reveals decisions, dependencies and gaps that can inform preparedness.

  • ID.IM-02: identify improvements from tests and exercises.
  • RS.MA: triage, prioritise and coordinate incident management.
  • RC.RP: examine integrity and functionality of the restored service.
  • Assign follow-up actions and check their effect without presenting a fictional scenario as a real incident.

Explore outcomes and evidence to examine →

NIST CSWP 29 · CSF 2.0 · 2024-02-26 · 2026-10-22

官方参考文献

参考文献支持该方法。 请根据您的实际情况调整检查;它们并非认证。 原始参考文献标题和源文档可能使用其他语言。

参考资料查阅日期 .