Relationship Mapping Model (RMM)
🎯 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
| Component | Description | Constraints |
|---|---|---|
version | (Optional) Version of the framework the mappings target (e.g. V17.1) | 2-30 characters, dot-separated letters, digits and hyphens |
rdm | Reference to the RDM, as an object with an id | id is the RDM identifier, e.g. MITRE-ENTERPRISE-PRODUCT-RDM |
mappings | Set of specific mappings to framework nodes | Each mapping is validated as below |
📌 Unlike FDMs and RDMs, an RMM has no
model,root,createdOnormodifiedOnfields.
📊 Mapping Structure
Each mapping within an RMM contains:
| Component | Description | Constraints |
|---|---|---|
target | Framework node path being mapped to | Required, must be a local path |
relationship | The relationship trait from the RDM | Required, must match a trait defined in the RDM |
modifiers | Key-value pairs of modifiers | Up to 20, must match modifiers defined in the RDM |
rationale | Explanation of why the relationship exists | Required, up to 2,000 characters |
sources | Set of sources participating in the mapping | At 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.
public static class Mapping {
private NodePath target; // Framework node being mapped to
private String relationship; // e.g., "PROTECT"
private Map<String, String> modifiers; // e.g., {"EFFECTIVENESS": "SIGNIFICANT"}
private String rationale; // Explains the relationship rationale
private Set<Source> sources; // Sources participating in the mapping
}
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.
public class Source {
private UUID id; // Unique identifier for the source
}
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.
{
"version": "V17.1",
"rdm": { "id": "MITRE-ENTERPRISE-PRODUCT-RDM" },
"mappings": [
{
"target": "/TA0001/T1566",
"relationship": "PROTECT",
"modifiers": {
"EFFECTIVENESS": "SIGNIFICANT"
},
"rationale": "Email security gateway blocks 99.8% of phishing attempts through ML-based detection",
"sources": [
{ "id": "550e8400-e29b-41d4-a716-446655440000" }
]
}
]
}
Relationship Definition Model (RDM)
The Relationship Definition Model (RDM) defines a standardized structure for expressing relationships between entities and framework nodes. It creates a consistent vocabulary for mapping capabilities, controls, or intelligence to taxonomic frameworks.
Platform Framework Matrix V2
Backend design for the Platform Framework Matrix view.

