Relationship Definition Model (RDM)
π― Purpose & Core Concepts
An RDM defines a class of relationships that can exist within a given framework. It specifies:
- The mapping type (e.g., PRODUCT, FEATURE, CONTROL, INTEL)
- The possible relationship traits that can be assigned
- Optional modifiers that allow for more granular variations of a relationship
π Each RDM is identified by its
rdmvalue, which must be unique across all RDMs, not just within its framework. An RDM belongs to one framework (viaroot) and is created against one mapping type.
π§© RDM Structure
| Component | Description | Constraints |
|---|---|---|
model | Declares the model definition | RDM: followed by a semantic version, e.g. RDM:1.0.0 |
root | Root of the framework the RDM applies to | Must match ^[A-Z0-9-]{2,30}$ |
createdOn | Date the RDM was created | ISO 8601 timestamp |
modifiedOn | Date the RDM was last modified | ISO 8601 timestamp |
rdm | Unique identifier for the RDM | Must match ^[A-Z0-9-]{2,30}$ |
type | Mapping type this model applies to | One of: VENDOR, PRODUCT, FEATURE, CONTROL, INTEL, GENERIC |
name | Human-readable name | 3-100 characters |
description | Detailed explanation of the RDM | Required, up to 10,000 characters |
relations | Set of relationship traits | 1-20 traits |
modifiers | Optional variations of relationships | 0-5 modifiers |
π Mapping Types
The mapping type sets what kind of source the mappings made against an RDM refer to:
| Type | Sources on mappings are |
|---|---|
| VENDOR | Vendors |
| PRODUCT | Products |
| FEATURE | Product features |
| CONTROL | Controls |
| INTEL | Intelligence |
| GENERIC | Generic information |
π All of the RDMs currently in production use the PRODUCT type.
π·οΈ Relationship Traits
Traits define the core relationship types that can exist between an entity and a framework node.
public class Trait {
private String value; // e.g., "PROTECT"
private String label; // e.g., "Protect"
private String criteria; // Describes when this trait applies
}
Each trait includes:
- A machine-readable value (e.g.,
PROTECT), up to 20 characters matching^[A-Z][A-Z0-9-]{1,18}[A-Z]$ - A human-readable label (e.g.,
Protect), up to 30 characters - Criteria that define when the trait should be applied, up to 2,000 characters
β‘ Traits are the primary way to express relationships. An entity must have at least one trait relationship to a framework node.
π Relationship Modifiers
Modifiers allow for more nuanced expression of relationships by adding qualifiers.
public class Modifier {
private String key; // e.g., "EFFECTIVENESS"
private String label; // e.g., "Effectiveness"
private String description; // Explains the modifier's purpose
private Boolean required; // Whether this modifier must be specified
private Set<Trait> values; // Possible values for this modifier
}
Each modifier includes:
- A machine-readable key (e.g.,
EFFECTIVENESS), up to 20 characters matching^[A-Z][A-Z0-9-]{1,18}[A-Z]$ - A human-readable label (e.g.,
Effectiveness), up to 30 characters - A description of the modifier's purpose, up to 2,000 characters
- Whether the modifier is required
- A set of 1-20 possible values (traits) that can be assigned
π Example: Cybersecurity Capability RDM
A common RDM for security tooling might define:
Relationship Traits:
IDENTIFY: Tool helps identify assets, risks, or threatsPROTECT: Tool provides protective capabilitiesDETECT: Tool detects security events or anomaliesRESPOND: Tool assists in security incident responseRECOVER: Tool supports recovery from security incidents
Modifiers:
EFFECTIVENESS(Required): How effectively the tool performs the primary function- Values:
SIGNIFICANT,PARTIAL,MINIMAL
- Values:
π This modifier is illustrative. None of the RDMs currently in production define any modifiers.
π Example: MITRE ATT&CK Enterprise RDM
The production RDM for MITRE ATT&CK Enterprise lives at prod-files/mitre/attack/enterprise/rdm_mitre-attck-enterprise.json in data-fdm-converter. The sample below shortens the criteria and shows two of its five traits.
{
"rdm": "MITRE-ENTERPRISE-PRODUCT-RDM",
"model": "RDM:1.0.0",
"root": "MITRE-ATTCK-ENTERPRISE",
"createdOn": "2018-01-17T12:56:55.080Z",
"modifiedOn": "2025-05-06T14:00:00.188Z",
"type": "PRODUCT",
"name": "MITRE ATT&CK Enterprise - NIST-Based Capability Mapping",
"description": "Maps security products to MITRE ATT&CK techniques using NIST CSF functions. ...",
"relations": [
{
"value": "PROTECT",
"label": "Protect",
"criteria": "product enforces controls that proactively prevent or block actions required by the technique ..."
},
{
"value": "DETECT",
"label": "Detect",
"criteria": "product ingests the telemetry required to observe the technique ..."
}
]
}
π‘ Practical Applications
RDMs enable flexible relationship modeling:
- Versioning: Multiple RDMs of a given type can exist, enabling versioning or iterations
- Custom Mappings: Additional RDMs can be defined for existing frameworks
- AI Integration: The trait criteria (and any modifiers) of an RDM are passed to ESPROFILER's AI-powered mapping engine, which uses them to choose a relationship for each node. AI mapping currently supports PRODUCT and FEATURE RDMs
- Standardization: Creates consistent vocabulary across different mapping exercises
π In practice, a framework has a default RDM defined against a type (e.g., PRODUCT). The first RDM created for a type becomes the default, and a different RDM of that type can be made the default later. Products in a capability exchange would then be mapped against this RDM and framework.
Framework Description Model (FDM)
The Framework Description Model (FDM) is a simple, universal JSON/YAML data structure for describing taxonomic frameworks such as MITRE ATT&CK, NIST CSF, and others in a machine-readable, query-efficient format.
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.

