> For the complete documentation index, see [llms.txt](https://docs.cybaops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybaops.com/modules/detect-and-respond-mdr/artefact-enrichment.md).

# Artefact Enrichment

### <mark style="color:$primary;">How artefact enrichment works in Detect & Respond</mark>

When an analyst adds or discovers an artefact during an investigation (for example an IP address, URL, or file hash), the CybaOps automatically enriches that artefact in the background with additional threat intelligence and context. The enrichment results are then displayed directly against the artefact within the case.

#### <mark style="color:$primary;">Enrichment sources</mark>

The following artefacts are are currently checked against threat intelligence data. The returned intelligence is then normalised and added into the Artefact drawer within both the case Management and the Incident pages.

* IP addresses
* URLs
* File hashes

Additional contextual log information that will aid investigation will also be added to the artefact.&#x20;

#### <mark style="color:$primary;">What Analysts will see</mark>

The enriched artefact can contain information such as:

* Threat verdict
* Geolocation information
* Country
* ASN
* Coordinates
* Known threat intelligence indicators
* Associated MITRE tactics and techniques (where available)
* Other contextual intelligence related to the artefact&#x20;

#### <mark style="color:$primary;">Investigation Workflow</mark>

Artefact enrichment is designed to support the investigation process by automatically providing additional context for indicators identified within an incident.

How it fits in a top level overview of the investigation process:

1. Incident is reviewed alongside the alert details.
2. Artefacts are generated from the detection, such as IP addresses, URLs, or file hashes.
   1. Enrichment occurs. The results are available within the artefact drawer. The results are used to better understand the artefact's reputation, associated activity, and potential risk, helping  make informed response decisions.
3. **Investigate** is used to explore related activity and gather additional evidence.
4. Any new supported artefacts discovered during are automatically enriched with available threat intelligence and contextual information.
5. Enrichment results can be reviewed to better understand the artefact's reputation, associated activity, and potential risk, helping make informed response decisions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cybaops.com/modules/detect-and-respond-mdr/artefact-enrichment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.