ESProfiler Handbook
Models

Relationship Mapping Model (RMM)

The Relation Mapping Model (RMM) is the concrete implementation that creates actual relationships between sources and framework nodes. It leverages the vocabulary defined in a Relationship Definition Model (RDM) to establish specific, contextual connections.

🎯 Purpose & Core Concepts

An RMM serves as the bridge between sources (e.g., security tools, controls, intelligence) and framework nodes by:

  • Referencing a specific RDM that defines the relationship vocabulary
  • Containing one or more mappings that target specific framework nodes
  • Specifying the exact relationship traits and modifiers from the RDM
  • Providing a rationale that explains each relationship
  • Identifying the sources that participate in the relationship

🔑 While the RDM defines what relationships can exist, the RMM declares what relationships do exist.


🧩 RMM Structure

ComponentDescriptionConstraints
version(Optional) Version of the framework the mappings target (e.g. V17.1)2-30 characters, dot-separated letters, digits and hyphens
rdmReference to the RDM, as an object with an idid is the RDM identifier, e.g. MITRE-ENTERPRISE-PRODUCT-RDM
mappingsSet of specific mappings to framework nodesEach mapping is validated as below

📌 Unlike FDMs and RDMs, an RMM has no model, root, createdOn or modifiedOn fields.


📊 Mapping Structure

Each mapping within an RMM contains:

ComponentDescriptionConstraints
targetFramework node path being mapped toRequired, must be a local path
relationshipThe relationship trait from the RDMRequired, must match a trait defined in the RDM
modifiersKey-value pairs of modifiersUp to 20, must match modifiers defined in the RDM
rationaleExplanation of why the relationship existsRequired, up to 2,000 characters
sourcesSet of sources participating in the mappingAt least one source required

Relationship values and modifier keys and values must match ^[A-Z][A-Z0-9-]{1,18}[A-Z]$.


🏷️ Mapping Components

The core of an RMM is its mappings, which establish specific relationships.

Each mapping includes:

  • A target framework node path (e.g., /TA0001/T1566)
  • A relationship value that must match a trait from the referenced RDM
  • Optional modifiers that qualify the relationship
  • A rationale description explaining the rationale
  • One or more sources that participate in the relationship

🔗 Source References

Sources represent the entities that have relationships with framework nodes and can be extended for additional frontend context.

The source type depends on the mapping type defined in the referenced RDM:

  • For VENDOR mappings: Vendor identifiers
  • For PRODUCT mappings: This is typically one product.
  • For FEATURE mappings: This is typically one or more features from a product.
  • For CONTROL mappings: Control or process identifiers
  • For INTEL mappings: Intelligence or threat identifiers

🚀 Example: Security Tool Capability Mapping

A security tool mapping might look like this.

Copyright © 2026