修复平均时间并非一种部署模型:企业漏洞管理的节奏审计
Mean Time to Remediate Is Not a Fielding Model: A Cadence Audit for Enterprise Vulnerability Management
AI总结:
介绍企业漏洞管理的修复节奏审计,记录多方面指标,与连续同均值捷径比较,给出本地容量判定和日历折扣,揭示不同发布节奏消耗容量情况,避免仅用MTTR/SLA作部署证据。
摘要:
企业安全团队常用修复平均时间等指标总结修复情况,但这些指标会掩盖修复实际到达资产的方式。本文引入企业漏洞管理的修复节奏审计,记录常规平均滞后、发布周期等多项内容,比较连续同均值捷径与记录的发布日历,得出相关判定和折扣,通过实例说明其重要性,还指出发布几何检查的结果等。
英文摘要:
Enterprise security teams commonly summarize remediation through mean time to remediate (MTTR), SLA compliance, dwell time, or detection delay. These metrics are useful, but they can hide how fixes actually reach the estate: continuously, through scheduled maintenance windows, in deployment rings, or through emergency bypass paths. This paper introduces a remediation-cadence audit for enterprise vulnerability management. The audit records routine mean lag, release period, release fraction, cohort geometry, emergency/routine split, non-fielding delay, local residual-pressure evidence, and declared rate scenario. It compares a continuous same-mean shortcut with the recorded release calendar and reports a local capacity verdict plus a calendar discount: the fraction of mean-only local capacity consumed by calendarized fielding. Worked notional packets with the same 30-day mean lag show why this matters. Under the normalized screening scenario, a two-month release train consumes 17.4\% of mean-only capacity, a monthly train 5.2\%, and a two-week screen 1.3\%; across a 16-fold attacker-adjustment rate band, the two-month discount remains at least about 12\% and the monthly discount stays in the resolution-sensitive 3--8\% range. The audit therefore turns cadence assessment into an evidence-resolution question: when the discount is material relative to residual-pressure uncertainty or claimed headroom, MTTR/SLA should not be used alone as fielding evidence. Release-geometry checks show that deployment rings do not automatically recover the continuous benchmark, and cohort staggering can help or hurt near capacity. The result is a reproducible governance diagnostic, not a breach predictor or CVE prioritizer.
机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。