资源 · 21
对网络安全事件进行分类并保存早期证据。
将混乱的信号转化为时间线、假设、决策和适当的升级。
已更新 · 16 min
本指南有助于实现的目标
- 接收有用信号
- 保留上下文
- 评估影响
- 组织决策
快速检查
- 谁在何时何地看到了什么?
- 哪些来源或痕迹可能会消失?
- 哪些服务、账户和数据可能会受到影响?
- 谁授权采取紧急措施?
- 何时重新评估?
分步指南
- 1
建立一份案例记录
记录初始信号、时间、观察者、受影响的系统和报告渠道。 指定案例负责人和副负责人。
交付成果:带时间戳的事件记录。
- 2
区分事实和假设
列出可验证的观察结果、来源和置信度。 陈述可能的场景,而不假设其来源或范围。
交付成果:事实时间线和可检验的假设。
- 3
保存易燃易爆材料
识别有用的日志、警报、消息和系统状态;根据内部程序保留副本并记录访问权限。 避免任何会破坏痕迹的更改。
交付成果:初始证据清单和处理记录。
- 4
评估范围和影响
绘制可能受影响的资产、账户、数据和业务流程图。 记录已确认、已排除或未知的内容以及等待成本。
交付成果:范围图和暂定影响级别。
- 5
决策和升级
根据适用要求,选择适当的保护措施、专家和利益相关者进行通报。 记录决策者和决策理由。
交付成果:决策日志和沟通计划。
- 6
重新评估和学习
设定下一次情况更新,添加新的证据,并将原因和差距与结案后的纠正工作联系起来。
交付成果:带有日期的更新和经验教训。
理解、计算与判断
假阳性:判断告警前先数清案例
虚构示例:10,000条观测中有100条阳性案例。参考标签已知,每条观测仅产生一个二元判断:告警或不告警。
集合含90条真阳性、99条假阳性、10条假阴性和9,801条真阴性。召回率以阳性案例为分母,精确率以告警为分母。这些结果不能确定实际告警的概率。
一个集合,不同分母
| 指标 | 计算 | 解释 |
|---|---|---|
| 参考阳性案例 | 100 / 10,000 · 1 % | 此集合中设定的比例。 |
| 检出的阳性案例 | 90 / 100 · 90 % | 召回率:分母为阳性案例。 |
| 阴性案例产生的告警 | 99 / 9,900 · 1 % | 假阳性率:分母为阴性案例。 |
| 告警中的阳性案例 | 90 / 189 · 47.62 % | 精确率:分母为告警。 |
| 未产生告警的阴性案例 | 9,801 / 9,900 · 99 % | 特异度:分母为阴性案例。 |
改变假设
哪些条件会改变结论
改变一个条件,然后指出哪些结论仍有依据。
- 定义范围
固定单位、时间段、标签和规则版本。
- 统计四种结果
参考集合也要保留未告警案例。
- 研判信号
查找实际案例的证据并记录决定。
虚构演练:不处理任何真实告警。
如果阳性案例增至10%?
- 新增信息
- 第二个集合在10,000条中含1,000条阳性,假设召回率和假阳性率不变。
- 对决策的影响
- 990条告警中有900条阳性,精确率约为90.91%。总体改变会影响结果;这些比率保持不变只是教学假设。
如果只核查了告警?
- 新增信息
- 未告警案例没有参考标签。
- 对决策的影响
- 假阴性数量未知,不能声称已测得召回率。请记录标签覆盖范围,并检查适当的案例范围。
如果调优减少了告警?
- 新增信息
- 新规则产生更少通知。
- 对决策的影响
- 这本身不能证明改善。重放同一批已标注案例,同时比较漏检、延迟和研判工作量。
管理指标
| 指标 | 衡量内容 | 首要行动 |
|---|---|---|
| 分类评估时间 | 从收到信号到首次记录范围的时间 | 明确升级流程 |
| 决策跟踪 | 包含时间、负责人和理由的决策 | 完成日志 |
| 证据覆盖范围 | 识别并保存关键信息源 | 弥补信息收集缺口 |
| 重新评估 | 在约定的检查点重新审视假设 | 更新范围 |
常见错误
- 过早采取行动导致抹杀痕迹
- 在验证之前公布原因
- 保留相互矛盾的时间线
- 未对决策进行日期标注或未重新审视假设
常见问题解答
每个警报都是事件吗?
否。初步评估决定观察结果是否需要正式响应,并可能随着证据的进展而改变。
是否必须等到所有情况都明朗后才采取保护措施?
否。在调查进行期间,采取适当的措施可以限制损害,前提是记录这些措施对证据和服务的影响。
最初可以传达哪些信息?
已确认的事实、已知影响、当前行动和下次更新。 在确定之前,原因和范围仍为暂定。
安全事件、漏洞或数据泄露:选择合适的联系对象
CSIRT服务于明确的对象范围(constituency),例如一个组织、行业或用户群。所在国家和FIRST成员身份并不能证明您属于其服务对象、团队当前可用或提供所需服务。请在其官方网站核实这三点。
- 厘清事实
- 核实服务范围
- 确认官方渠道
自身系统发生安全事件
联系响应计划中指定的内部团队或服务商。如需外部协调,查找服务范围覆盖您组织的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
参考资料:数据、用途与局限
文档核查日期 .
此语言版本的详细参考说明以英语提供。
| 来源与目的 | 已核实的数据或指标 | 使用方法 | 需要保留的局限 |
|---|---|---|---|
| NIST · SP 800-61 Rev. 3 Prepare incident response within cybersecurity risk management. |
Revision 3 was published in April 2025 and supersedes Revision 2. It is a CSF 2.0 Community Profile. | Rehearse containment decisions, evidence preservation, communication and recovery. Compare planned actions with evidence produced during the exercise. | Reading the guide does not validate a local plan. Contacts, emergency access and dependencies need local testing. |
网络事件:恢复决策与证据
此语言版本的详细参考说明以英语提供。
From alert to recovery: make decisions verifiable
Qualifying a signal, preserving investigative material and restoring a service answer different questions. CSF 2.0 distinguishes recovery initiation, integrity of restoration assets, validation of restored assets and the end of recovery. These are outcomes to document, not certification or one mandatory procedure.
The twelve entries below are a selected, paraphrased part of CSF 2.0. Evidence columns, timelines and injects are original teaching proposals. They do not replace a local plan and imply no universal timing, severity level or authority. SP 800-61 Revision 3 has been final since April 2025 and supersedes Revision 2.
RS.MA-05: apply initiation criteria. RC.RP-03: verify restoration assets before use. RC.RP-05: check restored assets and service operation. RC.RP-06: declare completion against criteria and finish documentation. These are decision points, not a mandatory sequence; investigation and monitoring may continue.
Twelve NIST outcomes and useful local evidence
| Reference and paraphrased meaning | Useful local record | Conclusion to avoid |
|---|---|---|
RS.MA-02Triage and validate incident reports. | Received signal, verified source, timestamps and reason for the provisional assessment. | An alert is not automatically a confirmed incident. |
RS.MA-03Categorise and prioritise incidents. | Suspected or confirmed type, affected service, impact, urgency and review date. | Alert volume alone does not establish business severity. |
RS.MA-04Escalate or elevate as needed. | Resource need, contacted role, required authority and next reassessment. | Adding responders does not mean a decision has been obtained. |
RS.MA-05Apply criteria for initiating recovery. | Local criteria, known facts and assumptions, action risks, decision maker and authorised scope. | A backup’s existence alone is insufficient to initiate restoration. |
RS.AN-06Record investigative actions while preserving record integrity and provenance. | Action, actor, time, reason, observed effect and protected access to the log. | A rewritten account without history does not establish decision order. |
RS.AN-07Collect incident data and metadata while preserving integrity and provenance. | Origin, collection, timestamps, custodian and retention rules; access limited to authorised staff. | A hash alone does not establish full origin or all collection circumstances. |
RC.RP-01Execute recovery procedures when initiated from incident response. | Plan and version, authorisations, assigned people and operation start. | Recovery can run during or after response rather than always being a wholly separate phase. |
RC.RP-02Select, scope, prioritise and perform recovery actions. | Target services and dependencies, order, resources, assumptions and scope changes. | Restoring everything in one fixed order may not reflect priorities. |
RC.RP-03Verify backups and other restoration assets before using them. | Planned checks for corruption, compromise indicators, consistency and origin of the selected candidate. | A successful backup job does not by itself validate the copy. |
RC.RP-04Consider critical mission functions and cyber risk when establishing post-incident operating norms. | Accepted normal or degraded operation, limitations, business owner and appropriate monitoring. | Degraded operation should not be described as complete recovery without qualification. |
RC.RP-05Verify restored assets, restore services and confirm operation. | Integrity checks, root causes addressed within scope, tested business journey and owner validation. | Copied files or a reachable screen do not demonstrate journey recovery. |
RC.RP-06Declare recovery completion against criteria and finish incident documentation. | Closure decision, criteria met, residual risks, review and assigned actions. | Service return does not automatically close every investigation or corrective action. |
No outcome matches. Remove a filter or refine the search.
A fictional timeline that preserves uncertainty
Teaching case: a request-processing application shows unusual service-account activity. T+0 is 08:00 UTC for this exercise; these durations are not NIST targets. No affected-record count or data disclosure is assumed without evidence.
| Exercise time | Observation or decision | Evidence and limit |
|---|---|---|
| T+0 · 08:00 UTC | An alert reports an unusual export. | Retain the event and its source; the alert alone does not prove exfiltration. |
| T+7 · 08:07 UTC | The alert source is validated; the overnight backup is marked completed. | Two different facts: job status does not establish backup integrity. |
| T+12 · 08:12 UTC | The lead declares an incident under the plan and has a sensitive journey paused. | Record authority, known scope and business effects; extent remains provisional. |
| T+25 · 08:25 UTC | Targeted access restrictions are authorised and recorded. | Trace what actually changed; this does not prove absence of other access or persistence. |
| T+40 · 08:40 UTC | A restoration-candidate check reveals corruption. | Do not use that candidate; document rejection and evaluate another recovery point. |
| T+60 · 09:00 UTC | Another candidate passes the defined checks; isolated restoration is authorised. | Keep results and check scope. Passing is not a guarantee of absence of compromise. |
| T+90 · 09:30 UTC | Files are restored but a dependency causes the business journey to fail. | Service validation has not passed; the case stays open. |
| T+120 · 10:00 UTC | The critical journey is tested in a business-approved degraded mode. | Record limits and monitoring. Closure still awaits the planned criteria and decision. |
Six fields for each important decision
- Observed fact
- Source, event time, collection time and time zone.
- Assumption
- What is assumed, why and how it will be checked.
- Chosen action
- Exact scope, decision maker and assigned executor.
- Observed effect
- Actual result, deviation and remaining unknowns.
- Retained evidence
- Protected reference, provenance, integrity and authorised access.
- Next review
- Condition or date, owner and blocking dependency.
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.
- NIST · SP 800-61 Rev. 3 · Final · 2025-04-03
Community Profile CSF 2.0 ; remplace / supersedes Rev. 2 - NIST · SP 800-61r3 — recommandations détaillées / detailed recommendations · April 2025
Pages imprimées / printed pages 27–29, 34–35 : RS.MA, RS.AN, RC.RP, RC.CO - NIST · Cybersecurity Framework 2.0 · 2024-02-26 · NIST CSWP 29
Appendix A, printed pages 22–23 : official outcome identifiers - NIST · SP 800-184 — Guide for Cybersecurity Event Recovery · Final · 2016-12-22
Recovery planning, playbooks, testing and improvement
References reviewed
STIX 指标与 TLP 共享
此语言版本的详细参考说明以英语提供。
Connect the indicator to observations and retirement
An indicator match opens an analytical lead. To assess its significance, preserve observed events, technical context, sensor coverage and alternative hypotheses.
- Distinguish Indicator, Observed Data and Sighting; an intelligence assertion does not replace observed data.
- Do not equate a DNS resolution with execution or a Sighting count=0 with worldwide threat absence.
- Assign an owner and a mechanism for retiring derived rules after expiry or revocation.
Read the STIX, observations and TLP sharing reference →
Sources checked on · OASIS · STIX 2.1
OSINT:证据保全
此语言版本的详细参考说明以英语提供。
Preserve context before confusing a copy with proof
Incident response must connect retained traces to their source, scope and handling actions. A digest protects a content comparison; it does not reconstruct undocumented custody.
- Use distinct identifiers for the preserved reference and working copies.
- Record handovers, receipts and clock uncertainty.
- Preserve an observed discrepancy and its reference before investigating cause.
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
syslog代码与采集证据
此语言版本的详细参考说明以英语提供。
A syslog code cannot qualify an incident alone
During triage, preserve the raw value, source and normalisation rule. Informational severity may document a sign-in or action relevant to an investigation; Emergency remains a sender declaration.
- Connect the message to a known asset and exposure context.
- Compare the raw event with the value displayed in the SIEM.
- Connect alerts to decisions and state collection gaps.
Read syslog codes and try the PRI calculation →
IANA · syslog Parameters · Registry updated 2016-04-26 · consulted 2026-10-23
ASD ACSC and partners · Best practices for event logging and threat detection · Published and reviewed 2024-08-22 · consulted 2026-10-23
官方参考文献
参考文献支持该方法。 请根据您的实际情况调整检查;它们并非认证。 原始参考文献标题和源文档可能使用其他语言。
参考资料查阅日期 .
- NIST SP 800-61 Rev. 3 — incident response recommendations
- Stefan Axelsson — The Base-Rate Fallacy and the Difficulty of Intrusion Detection (2000)
- Google SRE — Alerting on SLOs: precision and recall
- 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
- IANA · syslog Parameters
- IETF · R. Gerhards · RFC 5424 · The Syslog Protocol
- ASD ACSC and partners · Best practices for event logging and threat detection
- OASIS · STIX 2.1
- NIST · SP 800-61r3 — recommandations détaillées / detailed recommendations
- NIST · Cybersecurity Framework 2.0
- NIST · SP 800-184 — Guide for Cybersecurity Event Recovery
