> For the complete documentation index, see [llms.txt](https://docs.interlynk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interlynk.io/product-guides/security-and-compliance/incident-alerts.md).

# Security Incident Impact Alerts

{% hint style="warning" %}
**Alpha.** Security Incident Impact Alerts are in early access and the workflow may change. To request access, contact <support@interlynk.io>.
{% endhint %}

Security Incident Impact Alerts surface malicious-package supply-chain attacks before a CVE exists. When a campaign like Shai-Hulud is confirmed, Interlynk flags the affected package versions and identifies exactly which products across your organizations contain them, so teams can respond ahead of the CVE process.

***

## How It Works

An incident tracks a malicious-package supply-chain event from confirmation through remediation:

1. **Open an incident** for the confirmed campaign.
2. **Mark affected component versions** — enter them manually or import from a CSV.
3. **Scan SBOMs across organizations** to find the products that contain the affected versions.
4. **Review impact** from the dashboard to see which products are affected.
5. **Suppress findings** that don't apply to your context.
6. **Publish or resolve** the incident as remediation lands.

***

For access or help interpreting impact results, contact <support@interlynk.io>.


---

# 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.interlynk.io/product-guides/security-and-compliance/incident-alerts.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.