资源 · 02
网络风险评估:优先级清单
清点可见风险,将风险暴露与业务资产关联起来,并将评估结果转化为可验证的风险降低计划。
已更新 · 6 min
本指南有助于实现的目标
- 查找被遗忘的资产
- 区分风险暴露和实际风险
- 首先处理可信的攻击路径
- 证明已完成评估
快速检查
- 每个域都有所有者吗?
- 管理员是否使用防钓鱼的多因素身份验证 (MFA)?
- 测试服务是否暴露?
- 是否已测试恢复功能?
- 所有例外情况是否都会过期?
分步指南
- 1
定义授权范围
列出实体、域、范围、云应用程序和排除项。 商定允许的技术、时间安排和紧急联系人。
交付成果:范围和操作规则。
- 2
从外部进行清点
关联 DNS、证书、已发布服务、可见技术、公共存储库和官方帐户。 为每个资产分配所有者。
交付成果:带日期的清单。
- 3
审查身份和访问权限
检查 MFA 覆盖范围、孤立帐户、现有权限、恢复机制和已泄露的密钥。
交付成果:关键访问控制图。
- 4
关联漏洞和上下文
当漏洞可访问、可利用、与关键数据或功能相关且未被充分检测时,该漏洞就成为优先事项。
交付成果:风险场景。
- 5
验证弹性及检测能力。
审查备份、恢复、日志记录、警报、依赖关系和危机处理流程。 未经测试的备份仍视为假设。
交付成果:测试证据。
- 6
管理补救措施。
为每项措施指定负责人、日期、预期证据和剩余风险。 修复后进行外部重新验证。
交付成果:优先级排序的待办事项列表。
虚构示例
示例情境
子公司在搜索结果中发现一个旧的子域名。 在扫描之前,它会确认所有权、托管、用途以及是否可能仍然存在真实数据。
决策及预期证据
风险敞口记录区分已批准的资产、已废弃的服务和未知的第三方,并为每项资产提供所有者和关闭证明。
管理指标
| 指标 | 衡量内容 | 首要行动 |
|---|---|---|
| 库存覆盖率 | 已识别的资产及其所有者和重要性 | 优先处理无所有者资产 |
| 关键风险敞口 | 可从互联网访问的敏感服务 | 减少访问权限、分段或增加强控制措施 |
| 补救时间 | 从已验证的发现到最终确认的时间 | 解除高影响、低投入行动的阻碍 |
| 剩余风险 | 已接受的风险敞口及其所有者和到期日 | 过期例外情况,而不是将其保留 |
常见错误
- 未经授权或未定义窗口进行扫描
- 仅按技术评分排名
- 忽略 SaaS 和历史子域名
- 未经确认测试就关闭行动
常见问题解答
风险敞口审查是否等同于渗透测试?
否。它使用非侵入式或明确授权的方法对可见的风险敞口进行映射和评估。 渗透测试在单独的范围内验证选定的场景。
应该多久重复一次盘点?
重大变更后以及定期进行。 外部资产变化迅速,因此盘点频率应与您的部署节奏保持一致。
为什么要测试备份?
文件或作业的成功并不能证明完整性或在预期时间内恢复服务的能力。
参考资料:数据、用途与局限
文档核查日期 .
此语言版本的详细参考说明以英语提供。
| 来源与目的 | 已核实的数据或指标 | 使用方法 | 需要保留的局限 |
|---|---|---|---|
| NIST · Cybersecurity Framework Structure the outcomes expected from a cybersecurity programme. |
CSF 2.0 has six functions: Govern, Identify, Protect, Detect, Respond and Recover. It does not prescribe a single way to achieve outcomes. | Describe current and target profiles with evidence, gaps and owners. Connect each priority to the services it helps protect. | Mapping to the framework is neither certification nor proof that every control works. |
security.txt 与漏洞披露
此语言版本的详细参考说明以英语提供。
Check that an external report reaches a team
Cyber exposure also includes the ability to receive a useful report. A security.txt file can make the contact discoverable, but its presence alone establishes neither channel availability nor case follow-through.
- Check /.well-known/security.txt, HTTPS, Contact fields and exactly one Expires.
- Preserve the exact host, redirects and policy link; do not extend scope to subdomains by default.
- Assign a publication owner and a report handler; distinguish receipt, assessment and remediation.
Read the security.txt reference and disclosure cases →
Sources checked on · IETF · RFC 9116 · §2.5, §3, §5
CVSS、EPSS、KEV 与 VEX
此语言版本的详细参考说明以英语提供。
Preserve the facts justifying remediation order
An exposure review is more useful when each vulnerability connects to an instance and decision. Keep generic scores identifiable and dated, then relate them to the exposed service.
- Separate CVSS severity, EPSS probability, KEV listing and VEX applicability assertions.
- Establish product, version, access paths and owner before declaring local exposure.
- Record decision, interim control and verification evidence; an available patch is not a deployed fix.
Read the CVSS, EPSS, KEV and VEX reference →
Sources checked on · FIRST · CVSS 4.0 Specification · FIRST · EPSS Frequently Asked Questions · CISA · KEV official data schema · OpenVEX · Specification v0.2.0
浏览 CISA KEV 目录
此语言版本的详细参考说明以英语提供。
Connect an exposure to an official entry
Start with a CVE or product in the dated catalogue, then check the vendor advisory, deployed version and access path. KEV adds a known-exploitation signal; it does not replace analysis of your environment.
- Keep the entry and catalogue version.
- Document the product/version match and remaining uncertainty.
- Separate remediation, mitigation and investigation.
CISA KEV · 2026.11.06 · Documentary review : 2026-11-07
探索 NIST CSF 2.0 成果
此语言版本的详细参考说明以英语提供。
Connect exposure findings to expected outcomes
An inventory or vulnerability list describes part of the situation. CSF 2.0 also supports discussion of responsibility, protection, detection and recovery.
- ID.AM: reconcile observed assets, data, services and owners.
- ID.RA: describe a risk scenario and business consequences.
- PR.PS: examine maintenance and actual platform state.
- Document evidence and scope; do not turn a finding count into a compliance score.
Explore outcomes and evidence to examine →
NIST CSWP 29 · CSF 2.0 · 2024-02-26 · 2026-10-22
TLS 证书与开源情报
此语言版本的详细参考说明以英语提供。
CT: a discovery lead requiring qualification
Public logs help examine certificates associated with a scope. A CT result is documentary evidence, not a finding of an exploitable vulnerability.
- Match each name to an authorised inventory.
- Do not count duplicates across logs as separate assets.
- Separate issuance, deployment, expiry and observed exposure.
Read the CT dossier and dated log list →
Google Chrome · Certificate Transparency for Site Operators · Domain Privacy · consulted 2026-10-23
官方参考文献
参考文献支持该方法。 请根据您的实际情况调整检查;它们并非认证。 原始参考文献标题和源文档可能使用其他语言。
参考资料查阅日期 .
- NIST — Cybersecurity Framework 2.0
- NIST — SP 800-53A, Assessing Security and Privacy Controls
- NIST · Cybersecurity Framework
- IETF · RFC 6962 · Certificate Transparency
- Google Chrome · Certificate Transparency for Site Operators
- NIST (2024) · The NIST Cybersecurity Framework (CSF) 2.0
- CISA · KEV official snapshot
- CISA · Current KEV JSON in the official repository
- CISA · KEV data schema
- CISA · Official mirror and reuse terms
- CISA · KEV licence
- FedRAMP · Response to CISA BOD 26-04
- FIRST · CVSS
- FIRST · EPSS
- FIRST · CVSS 4.0 Specification
- FIRST · EPSS Frequently Asked Questions
- CISA · KEV official data schema
- OpenVEX · Specification v0.2.0
- IETF · RFC 9116 · security.txt
