Security Incident Impact Alerts
Alpha. Security Incident Impact Alerts are in early access and the workflow may change. To request access, contact [email protected].
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:
Open an incident for the confirmed campaign.
Mark affected component versions — enter them manually or import from a CSV.
Scan SBOMs across organizations to find the products that contain the affected versions.
Review impact from the dashboard to see which products are affected.
Suppress findings that don't apply to your context.
Publish or resolve the incident as remediation lands.
For access or help interpreting impact results, contact [email protected].
Last updated