FrameworkMapper
Transparent by Design

How We Determine What to Fix First

Every priority ranking in your assessment results is produced by the Universal Control Prioritization Algorithm (UCPA) — a deterministic, seven-factor scoring model developed by Midwest Cyber, LLC.

Start an Assessment

Frameworks Tell You What. We Tell You What First.

CIS Controls v8.1 has 153 safeguards. NIST SP 800-53 has 1,189 controls. CMMC Level 2 requires 110 practices. Organizations subject to multiple frameworks can face a combined control universe exceeding 1,500 requirements.

Frameworks are intentionally silent on implementation order — context matters. But that leaves most organizations without actionable guidance. The UCPA fills that gap with a transparent, reproducible scoring model that turns a compliance checklist into an implementation roadmap.

153
CIS Controls v8.1 safeguards
1,189
NIST SP 800-53 Rev. 5 controls
110
CMMC Level 2 practices
1
Deterministic priority sequence

The Priority Score Formula

Every control receives a composite Priority Score (P) computed from seven weighted factors. Each factor is normalized to a 0–100 scale before weighting, and the weights always sum to 1.0.

P = (Wt × T) + (Wd × D) + (We × E) + (Wb × B) + (Wr × R) + (Wc × C) + (Wa × A)
T — Threat Relevance
D — Dependency Score
E — Effort-to-Value
B — Blast Radius
R — Regulatory Criticality
C — Coverage Breadth
A — Asset Exposure

The Seven Factors Explained

Each factor draws from empirical, publicly available data sources — not vendor claims or consultant opinion.

T
Threat Relevance
How actively exploited is this attack vector?

Controls that mitigate techniques appearing in active campaigns score higher than those addressing theoretical or rarely observed threats.

Data Sources
  • CISA Known Exploited Vulnerabilities (KEV) Catalog
  • Verizon Data Breach Investigations Report (DBIR)
  • MITRE ATT&CK technique prevalence data
  • MS-ISAC advisories (K-12 & SLTT focus)
  • CISA #StopRansomware joint advisories
D
Dependency Score
How many other controls depend on this one?

Computed from a Directed Acyclic Graph (DAG) of control relationships. Controls with high out-degree — those that unlock or amplify other controls — are prioritized as foundational infrastructure.

Relationship Types Modeled
  • Hard prerequisite (B cannot be done without A)
  • Enabler (A makes B functional)
  • Amplifier (A increases B's effectiveness)
  • Policy foundation (A provides governance basis for B)
E
Effort-to-Value Ratio
Defensive value gained relative to implementation cost

Particularly important for resource-constrained organizations. Scores are calibrated to three resource profiles: Minimal (volunteer IT), Moderate (small IT team), and Well-resourced (dedicated security staff).

Sub-factors
  • Implementation cost (licensing, hardware, staffing)
  • Implementation time to operational status
  • Skill requirement & maintenance burden
  • Breadth and depth of defensive value
B
Blast Radius
Severity of impact if this control is absent during an incident

Distinct from Threat Relevance: T measures probability, B measures magnitude. Together they approximate classic risk (likelihood × impact), decomposed into independently scored components.

Sub-factors
  • Data exposure potential
  • Operational disruption to mission continuity
  • Lateral movement enablement
  • Recovery complexity & regulatory penalty exposure
R
Regulatory Criticality
Compliance weight: audit findings, fines, contract eligibility

Scored on a rubric tied to real-world consequence: automatic audit failure scores highest; best-practice recommendations score lowest. The vertical weight profile determines R's influence — it matters most for defense contractors (CMMC) and least for churches.

Score Rubric
  • 81–100: Automatic audit failure or loss of certification
  • 61–80: Commonly tested, appears in POA&Ms
  • 41–60: Referenced in regulation, not individually assessed
  • 0–40: Recommended or no direct mandate
C
Coverage Breadth
How many frameworks require or reference this control?

Cross-framework consensus is a strong signal of foundational importance. When CIS, NIST CSF, NIST 800-53, CMMC, and HIPAA all require access control enforcement, that convergence speaks for itself.

Score Thresholds
  • 81–100: Referenced by 6 or more frameworks
  • 61–80: Referenced by 4–5 frameworks
  • 41–60: Referenced by 2–3 frameworks
  • 0–40: Unique to a single framework
A
Asset Exposure
Relevance to the organization's actual attack surface

The only factor that varies by individual organization rather than by vertical. A control protecting cloud workloads is irrelevant to an organization with no cloud presence. Asset Exposure personalizes the priority sequence to your actual environment.

Each control is pre-tagged with relevant environment factors. Your assessment responses activate or deactivate relevance flags, producing an A score of 0 (irrelevant), 50 (partially relevant), or 100 (directly applicable).

Environment Factors Evaluated
  • Cloud service usage (IaaS, PaaS, SaaS)
  • Remote workforce percentage
  • Bring-your-own-device (BYOD) policies
  • Operational technology (OT/IoT) presence
  • Internet-facing service exposure
  • Third-party integration density

Tuned to Your Industry

The seven factor weights are not one-size-fits-all. Each industry vertical has a default weight profile that reflects its operational reality — threat exposure, resource constraints, and compliance obligations.

Factor K-12 Defense Church SLTT Gov SMB
T Threat Relevance 0.20 0.15 0.15 0.20 0.20
D Dependency Score 0.20 0.15 0.20 0.15 0.15
E Effort-to-Value 0.20 0.05 0.25 0.15 0.25
B Blast Radius 0.15 0.15 0.10 0.15 0.10
R Regulatory Criticality 0.05 0.30 0.05 0.20 0.05
C Coverage Breadth 0.10 0.10 0.15 0.10 0.15
A Asset Exposure 0.10 0.10 0.10 0.05 0.10
Total 1.00 1.00 1.00 1.00 1.00
K-12 School Districts

Elevated ransomware exposure, minimal IT staff, limited budgets. Threat Relevance, Dependency, and Effort-to-Value share equal priority at 0.20 each. Regulatory weight is low — most K-12 cybersecurity compliance is voluntary.

Defense Contractors

CMMC certification is binary — pass or fail. Regulatory Criticality dominates at 0.30. Effort-to-Value drops to 0.05 because required controls must be implemented regardless of cost.

Churches & Faith-Based

Volunteer IT, near-zero budgets, no regulatory mandates. Effort-to-Value leads at 0.25, ensuring recommended actions are achievable with available resources.

Fully Deterministic

Given identical inputs, the algorithm always produces an identical priority sequence — essential for audit defensibility. An assessor reviewing results at any point in time can reproduce the exact sequence from documented inputs.

Tiebreaking Cascade
  1. Higher Dependency Score (foundational controls first)
  2. Higher Effort-to-Value (quicker wins preferred)
  3. Higher Threat Relevance (active threats break ties)
  4. Alphabetical by control identifier (final fallback)

Every Score Is Explainable

Every Priority Score decomposes into its seven constituent factor scores and applied weights. This decomposition is preserved and surfaced as plain-language rationale in your assessment report:

"This control is ranked #3 because it scores 95 on Dependency (it is a prerequisite for 8 other controls), 88 on Effort-to-Value (it can be implemented in under 4 hours at no cost), and 72 on Threat Relevance (the attack vector it mitigates appears in 6 active CISA advisories)."

Cited Data Sources

Every T score traces back to specific KEV entries, DBIR frequency data, and advisory references. Every D score traces back to a documented dependency in the control DAG. Every R score traces back to a specific audit checklist item or enforcement action.

This audit trail is maintained as structured metadata and is available for inspection at any time — supporting grant applications, audit responses, and organizational leadership briefings.

Kept Current

Threat intelligence data (Factor T) refreshes quarterly from CISA KEV and MS-ISAC, and annually following the Verizon DBIR publication. Factor weights and blast radius scores are reviewed annually. Coverage Breadth (C) and Asset Exposure (A) update automatically.

The ATT&CK technique intermediary layer reduces the quarterly maintenance surface from 1,000+ individual control scores to approximately 200 technique prevalence scores.

Primary Data Sources

CISA Known Exploited Vulnerabilities (KEV)
Machine-readable feed of confirmed actively exploited vulnerabilities
Verizon Data Breach Investigations Report (DBIR)
Annual statistical analysis of tens of thousands of real security incidents
MITRE ATT&CK Knowledge Base
Observed adversary technique frequency across real-world intrusion data
MS-ISAC Advisories
Sector-specific threat reporting for K-12 and SLTT organizations
CISA #StopRansomware Advisories
Ransomware campaign reporting reflecting the dominant threat class for target verticals
CIS Controls v8.1 / NIST SP 800-53 Rev. 5 / CMMC / HIPAA
Authoritative framework specifications and audit checklists

The UCPA was developed by Midwest Cyber, LLC and is implemented as a scoring engine within the FrameworkMapper platform. © 2026 Midwest Cyber, LLC. All rights reserved.

See the Algorithm in Action

Run an assessment and receive a prioritized implementation roadmap with full factor-level explanations for every control recommendation.