ESProfiler Handbook
Models

Universal Framework Mapper Vision

Why ESProfiler is moving to a single framework engine that models any framework as a tree, and what it enables.
Status (October 2026). This page is the original vision. The separate MITRE views, Domains & Categories and the Cyber Defense Matrix have been replaced by one Frameworks page. The dropdown has what is built, partly built and still to come.

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:

TypeDescription
BEHAVIORAdversary tactics, techniques, and behaviors
DEFENSIVECountermeasures, hardening strategies
COMPLIANCERegulatory controls and obligations
ASSESSMENTSecurity testing & threat modeling
TAXONOMYLogical groupings or categories

5. Core Principles

  1. Multi-Mapping – Any product/feature can map to multiple frameworks and multiple nodes.
  2. Reusable Components – One set of UI components for coverage, cost, priority, and delta change across any framework.
  3. Delta Modeling – Standardized "what-if" modeling for adding/removing products or changing mappings.
  4. AI Integration – Default mappings generated for public frameworks; custom frameworks can trigger AI-based mapping jobs.
  5. Zones – Coverage can be analyzed at global, organizational, or zone (business unit/site) level.

6. User-Facing Features

  • 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

  1. Consistent UX – One way to browse, view, and analyze any framework.
  2. Faster Time-to-Value – AI mappings mean customers can start with meaningful data on day one.
  3. Extensible Platform – New frameworks added without backend/FE rewrites.
  4. 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.

Copyright © 2026