mitre-attack / mitre-attack/attack-data-model

Missing subtechnique-of relationships for T1053.001 and T1547.011

Open
#64 0 comments 0 reactions 1 assignee View on GitHub

@seansica is already working on this.

Since Jan 26, 2026.

Dominant language
MDX
Stars
93
Forks
25
PR merge metrics
No merged PRs in 30d

Description

Summary

Two subtechniques in enterprise-attack-18.1.json are missing their subtechnique-of relationship objects, making it impossible to programmatically determine their parent techniques using only relationship lookups.

Affected Subtechniques

  • T1053.001 (At - Linux) - Missing relationship to parent T1053 (Scheduled Task/Job)
  • T1547.011 (Plist Modification) - Missing relationship to parent T1547 (Boot or Logon Autostart Execution)

Details

Both objects have:

  • "type": "attack-pattern"
  • "x_mitre_is_subtechnique": true
  • Valid kill_chain_phases arrays

However, no corresponding relationship objects exist with:

  • "relationship_type": "subtechnique-of"
  • "source_ref" pointing to these subtechniques

Impact

Tools parsing the STIX data that rely on relationship objects (rather than inferring from ID format) will fail to associate these subtechniques with their parent techniques.

Expected Behavior

Each subtechnique should have a corresponding relationship object linking it to its parent technique, consistent with the other 477 subtechniques.

Workaround

Parse the technique ID format (split on .) to infer the parent, but this defeats the purpose of explicit relationship modeling in STIX.

Proposed Fix

Add the following two relationship objects to the objects array in enterprise-attack-18.1.json:

For T1053.001 → T1053
{
  "type": "relationship",
  "spec_version": "2.1",
  "id": "relationship--[generate-new-uuid]",
  "created": "[timestamp]",
  "created_by_ref": "identity--c78cb6e5-0c4b-4611-8297-d1b8b55e40b5",
  "object_marking_refs": [
    "marking-definition--fa42a846-8d90-4e51-bc29-71d5b4802168"
  ],
  "modified": "[timestamp]",
  "relationship_type": "subtechnique-of",
  "source_ref": "attack-pattern--6636bc83-0611-45a6-b74f-1f3daf635b8e",
  "target_ref": "attack-pattern--35dd844a-b219-4e2b-a6bb-efa9a75995a9",
  "x_mitre_modified_by_ref": "identity--c78cb6e5-0c4b-4611-8297-d1b8b55e40b5",
  "x_mitre_deprecated": false,
  "x_mitre_attack_spec_version": "3.2.0"
}
For T1547.011 → T1547
{
  "type": "relationship",
  "spec_version": "2.1",
  "id": "relationship--[generate-new-uuid]",
  "created": "[timestamp]",
  "created_by_ref": "identity--c78cb6e5-0c4b-4611-8297-d1b8b55e40b5",
  "object_marking_refs": [
    "marking-definition--fa42a846-8d90-4e51-bc29-71d5b4802168"
  ],
  "modified": "[timestamp]",
  "relationship_type": "subtechnique-of",
  "source_ref": "attack-pattern--6747daa2-3533-4e78-8fb8-446ebb86448a",
  "target_ref": "attack-pattern--1ecb2399-e8ba-4f6b-8ba7-5c27d49405cf",
  "x_mitre_modified_by_ref": "identity--c78cb6e5-0c4b-4611-8297-d1b8b55e40b5",
  "x_mitre_deprecated": false,
  "x_mitre_attack_spec_version": "3.2.0"
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.