Cyber Resilience

← Exposures · the misconfiguration (M) surface across OS, Identity, and Data

Configuration exposure

Exposure as control gaps and misconfiguration — where your defenses structurally miss, where host and cloud posture drift, and the weakness classes that are really authorization and configuration mistakes. Same rigor as the CVE lens, applied to the configuration layer.

Last updated: 12 August 2026 00:47 UTC . Analysis from public framework and vulnerability data — not a posture-scanning product.

Control gaps by actor

For each of the most active actors, the NIST 800-53 controls that mitigate the largest share of their ATT&CK techniques — and how much of their playbook even the best single control leaves uncovered.

ActorStart-here controls Best coverageUncovered share
Kimsuky171 techniquesSI-4CM-6CM-250%50%
APT28129 techniquesCM-6SI-4CM-261%39%
Lazarus Group128 techniquesSI-4CM-2CM-660%40%
APT41115 techniquesSI-4CM-6CM-264%36%
Mustang Panda114 techniquesSI-4CM-2CM-661%39%
Sandworm Team109 techniquesSI-4CM-6CM-259%41%
Magic Hound109 techniquesSI-4CM-6CM-258%42%
APT32106 techniquesSI-4CM-6CM-267%33%

Coverage = the share of an actor's ATT&CK techniques that our cross-walks map the control as mitigating. How actor data is built.

Misconfiguration & host posture

Cloud-posture control data (AWS Trusted Advisor, Azure Secure Score) is on the roadmap, not built yet — those collections exist but currently hold zero records, so we do not show a cloud picture we cannot back. What we do hold is host-configuration hardening: the DISA STIG baselines below, cross-walked to NIST 800-53 via CCIs.

Hardening baseline Hardening rules
Oracle Linux 9455
RHEL 9452
Oracle Linux 8373
RHEL 8369
Windows Server 2019275
Windows Server 2022275
Windows Server 2016273
Windows 10261
Windows 11258
RHEL 7244
Ubuntu 24 04194
Ubuntu 22 04187

3,616 host-hardening rules across 12 DISA STIG baselines — the configuration checks that keep a built system from drifting into an exploitable state. Browse them at /hardening/. Cloud-posture control ingest is tracked as future work.

The weaknesses that are really misconfigurations

11,276 CVEs (distinct) cite a configuration-, permission-, privilege-, or access-control weakness — flaws that are authorization and configuration mistakes rather than code bugs. This is the bridge back to the vulnerability lens: a misconfiguration is an exposure whether or not it carries a CVE.

Weakness class (CWE)CVEs In CISA KEV
CWE-284Improper Access Control6,32533
CWE-269Improper Privilege Management3,13320
CWE-732Incorrect Permission Assignment for Critical Resource1,7174
CWE-16Configuration3180

Cohort = CVEs whose NVD weaknesses include CWE-16, CWE-732, CWE-269, or CWE-284. KEV = confirmed exploited-in-the-wild. Browse all weakness classes at /cwes.html.