acronis-edr-incidentslisted
Install: claude install-skill WYRE-AI/msp-claude-plugins
# Acronis EDR Incidents
## Overview
Acronis EDR groups related detections on an endpoint into an incident. Each
incident has a severity, a verdict, a mitigation state (was the threat
stopped) and an investigation state (has a person looked at it). An MSP's job
is to make sure every incident that isn't auto-mitigated gets looked at, and
that the investigation state reflects reality.
## Anti-triggers
- **Backup failures and missed backups** — those are alerts, not incidents.
Use `acronis-backup-health`.
## Key Concepts
| Field | Values |
|-------|--------|
| `severity` | `LOW`, `MEDIUM`, `HIGH`, `CRITICAL` |
| `verdict` | `SUSPICIOUS`, `MALICIOUS` |
| `mitigation_state` | `NOT_MITIGATED`, `MITIGATED`, `AUTO_MITIGATED` |
| `state` (investigation) | `NOT_STARTED`, `INVESTIGATING`, `TRIAGED`, `FALSE_POSITIVE`, `CLOSED` |
| `incident_category` | Such as `MALWARE_DETECTED`, `PROCESS_DETECTED`, `URL_BLOCKED`, `MS_DEFENDER` |
`is_mitigated` is a simple true/false filter on whether the threat was
stopped. `positivity` is a confidence score from 0 to 10 that you can filter
with `range(min, max)`.
## Workflow: Daily Incident Review
1. **Open incidents for a customer.** Call `acronis_fetch_incidents` with
`customer_id`, `state: "or(NOT_STARTED,INVESTIGATING)"` and
`created_at: "ge(<start date>)"`. With a partner-level API client, always
pass `customer_id`; without it the call uses the API client's own tenant.
2. **Unmitigated first.** Re-run with `mitigation_state: "NO