SCP-8592
Unknown
~
medium confidence
SCP-8592
Expected annual
$447K
One-time setup
$2.9M
Annual recurring
$438K
Personnel
3
Upfront one-time tooling and isolation (sandbox VMs, dev work, UI changes) are modest but a worst-case full network rebuild can push costs into the millions; baseline annual operations are dominated by staffing, SIEM/logging, and research/backup costs.
One-Time Capital Costs
Total: $2.9M
Annual Recurring Costs
Total: $438K/yr
Cost Scenarios
📊
Baseline
(baseline)
$438K/yr
Normal year with no major incidents: ongoing monitoring, rule tuning, backups, staffing, SIEM, and small research/honeypot operations.
no incidents
routine operations
🚨
Minor Incident
$503K/yr
Single investigatory incident requiring extra forensics, legal work, and limited PR/response; no full rebuild.
isolated compromise or unusual manifestations
one-off forensic investigation
legal/internal inquiry
🚨
Major Breach
$3.4M/yr
Severe event requiring full network rebuild/migration and major legal/PR response.
decision to rebuild or excise SCP-8592 from production
widespread data corruption or public leak
Personnel
3 total
| Role | Count | Notes |
|---|---|---|
| Sysadmin / Incident Handler | 1 | [#5] 0.5–1.0 FTE monitoring and incident triage (represented as one assigned role in headcount). |
| Security Analyst | 1 | [#5] ~0.2 FTE security analyst for filter/script maintenance (represented as one shared analyst in headcount). |
| Administrative Staff | 1 | [#7] HR/records admin (0.25–0.75 FTE) for auditing and manual corrections; represented as one staff member in headcount. |
Confidence Notes
Estimates are drawn from analyst-provided ranges; midpoints were used where ranges were wide (notably the network rebuild contingency). SCP behavior and trigger frequency are described but have uncertainty, and high-impact events have broad ranges, yielding medium confidence.