/mitre_attack/groups/search

POST /api/mitre_attack/groups/search

Price: 20 credits

Search MITRE ATT&CK adversary groups by name, alias, description and matrix

How to use it

This is where a vendor name resolves to an ATT&CK id: query matches the aliases as well as the name and description, so 'FANCY BEAR' and 'Sofacy' both reach G0007. Matching is a literal substring, so try one distinctive token rather than a full sentence, and expect several groups to share an alias when vendors disagree.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Free-text match against the group name, its aliases and its description (examples: "APT28", "Lazarus", "Iranian")
• domain string nullable — ATT&CK matrix to search, or every matrix when omitted (one of: "enterprise", "mobile", "ics")
• count integer required — Max result count (examples: 20; min: 1)

Response

• @type string (default: "MitreAttackGroup")
• id string required
• stix_id string nullable
• name string nullable
• description string nullable
• web_url string nullable
• domains array (default: [])
• version string nullable
• created_at string nullable
• modified_at string nullable
• contributors array (default: [])
• references array (default: [])
  • @type string (default: "MitreAttackReference")
  • source_name string nullable
  • description string nullable
  • url string nullable
• aliases array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.