Universal Framework Mapper Vision
- The Problem Today (section 2) has been addressed. The framework revamp replaced the separate MITRE 2D/3D Framework Views and Domains & Categories with a single Frameworks page under Security stack, which works the same way for every framework. The Cyber Defense Matrix is no longer shown in the platform.
- Built: the framework gallery, choosing frameworks in settings, framework coverage on product and vendor pages, filtering coverage by vendors and products, and shared coverage, cost and priority components across frameworks.
- Partly built: node details are a side panel on the Frameworks page rather than a dedicated page. RDMs can be viewed and picked but not created in the UI. AI mapping is an auto-map setting per framework. Modelling products in and out is a product filter rather than a simulation.
- Still to come: choosing frameworks during onboarding, the Framework Builder Tool (uploading custom frameworks), node comments and linked resources, showing or setting sharing levels in the UI (public frameworks can also still be made private again), and what-if, delta and change-over-time modelling.
For how the models work today, see the Framework Description Model, Relationship Definition Model and Relationship Mapping Model pages.
1. Purpose & Vision
The Universal Framework Mapper (UFM) is the next chapter in ESProfiler’s mission to make cyber capability mapping clear, consistent, and actionable.
Our current MITRE-only approach has hit a ceiling:
- Many prospective customers are not yet operating within MITRE, leaving our messaging flat.
- Existing framework mapping features are inconsistent, siloed, and hard to extend.
- Vendor-provided mappings have limited scalability — but AI-assisted mapping has proven promising.
Vision Statement:
A single, universal framework engine that models any taxonomy or framework as a tree, enabling consistent, real-time coverage, cost, and priority analysis across all frameworks — with reusable components, flexible relationship modeling, and AI-powered mapping.
2. The Problem Today
Our platform currently has multiple mapping concepts that don’t align:
- Framework Views: MITRE-based, with 2D and 3D visualizations. Limited cost analysis, inconsistent summaries.
- Domains & Categories: One product per category (limiting), basic coverage counts, cost shown.
- Cyber Defense Matrix: NIST CSF x Asset Class mapping, but products can only sit in one cell.
Each of these was built independently:
- Different data models → poor reusability.
- Separate visual components → inconsistent UX.
- Heavy backend/FE maintenance for each new framework.
3. The Realization
Every framework or taxonomy — whether MITRE ATT&CK, NIST CSF, or a custom category structure — can be modeled as a tree:
- Root: Framework identifier (e.g., MITRE-ATTCK).
- Branches: Hierarchical nodes (depth 1–10).
- Leaves: Lowest-level capabilities, controls, or behaviors.
At any level of the tree, users need to see:
- Coverage (% of nodes mapped)
- Cost (sum of mapped products or controls)
- Priority (customer-defined or AI-derived)
- Changes over time (delta visibility)
4. Framework Types
Every framework fits into one of five categories:
| Type | Description |
|---|---|
| BEHAVIOR | Adversary tactics, techniques, and behaviors |
| DEFENSIVE | Countermeasures, hardening strategies |
| COMPLIANCE | Regulatory controls and obligations |
| ASSESSMENT | Security testing & threat modeling |
| TAXONOMY | Logical groupings or categories |
5. Core Principles
- Multi-Mapping – Any product/feature can map to multiple frameworks and multiple nodes.
- Reusable Components – One set of UI components for coverage, cost, priority, and delta change across any framework.
- Delta Modeling – Standardized "what-if" modeling for adding/removing products or changing mappings.
- AI Integration – Default mappings generated for public frameworks; custom frameworks can trigger AI-based mapping jobs.
- Zones – Coverage can be analyzed at global, organizational, or zone (business unit/site) level.
6. User-Facing Features
6.1 Framework Gallery & Management
- Browse available frameworks (logos, descriptions, type tags).
- Select which frameworks to operate with (onboarding & settings).
- Upload custom frameworks via the Framework Builder Tool.
- Open a dedicated node detail page:
- Related mappings & intelligence
- Discussion/comments
- Linked resources
Framework Sharing Levels:
- Private – Only the creator organization
- Protected – Shared with specific organizations
- Public – Available to all (irreversible once public)
6.2 Relationship Definition Model (RDM)
- Defines how entities relate to a framework (e.g., products, features, controls, intel).
- Contains traits (e.g., PROTECT, DETECT) and optional modifiers (e.g., EFFECTIVENESS).
- Ensures consistent aggregation & filtering across frameworks.
Example:
- Framework: MITRE ATT&CK
- RDM type: PRODUCT (e.g., MITRE-ENTERPRISE-PRODUCT-RDM)
- Traits: IDENTIFY, PROTECT, DETECT, RESPOND, RECOVER
- Modifier: EFFECTIVENESS (SIGNIFICANT, PARTIAL, MINIMAL)
6.3 Framework Mapping
- Public frameworks with default RDMs → prebuilt or AI-generated mappings.
- Custom frameworks → on-demand AI mapping jobs.
- Centralized mapping storage → no duplicate work if frameworks are later made public.
6.4 Profile Pages (Vendors & Products)
- Display mappings to all chosen frameworks.
- Support modeling products in/out to see coverage & cost impact.
6.5 Zones
- Logical subdivisions of an organization.
- Coverage/cost/priority views filtered per zone.
- Identify coverage gaps or overlaps at granular levels.
6.6 Portfolio View
- Consolidates frameworks, domains, and matrices into one navigation point.
- Filter vendors/products and immediately view coverage against any selected framework.
- Use modeling tools to simulate portfolio changes.
7. Technical Foundations
- Framework Description Model (FDM) – Universal JSON/YAML format for representing frameworks as trees.
- Path Conventions – Consistent referencing (local, absolute, version-agnostic).
- PathLookup Engine – High-performance branch/ancestor/family lookups.
- Relationship Definition Model (RDM) – Vocabulary for mapping types, traits, and modifiers.
- Relationship Mapping Model (RMM) – Actual mappings between sources and framework nodes.
8. Why This Matters
With UFM:
- Designers get a single component library for all framework displays.
- Developers integrate once for all frameworks instead of per-framework hacks.
- Customers can map any portfolio to any framework (public, protected, or private).
- AI fills in mapping gaps quickly.
- Portfolio modeling and “what-if” analysis becomes seamless.
9. North Star Outcomes
- Consistent UX – One way to browse, view, and analyze any framework.
- Faster Time-to-Value – AI mappings mean customers can start with meaningful data on day one.
- Extensible Platform – New frameworks added without backend/FE rewrites.
- Data-Driven Decisions – Coverage, cost, and priority visible instantly across all contexts.
This vision creates a universal mapping language for ESProfiler — replacing siloed tools with a single, powerful, reusable engine for cyber capability modeling.

