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
- 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.
- Unmitigated first. Re-run with
mitigation_state: "NOT_MITIGATED".
Those are threats Acronis didn't stop, and they come before everything
else regardless of severity.
- Then by severity.
severity: "or(HIGH,CRITICAL)" next, then the rest.
- Page. Use
limit and cursor. Keep every other parameter exactly the
same between pages or the cursor is rejected.
- Read one incident.
acronis_fetch_incident with path.incident_id,
customer_id, and with_detections, with_activities and
with_incident_actions set to true. Detections say what was seen,
activities say what happened on the machine, and incident actions say what
was done about it.
- Check a response action. If someone isolated the machine or killed a
process from the console, call
acronis_fetch_response_action_status with
the incident ID and the action's activity_id from step 5.
Deciding the Outcome
| Situation |
Typical investigation state |
| Auto-mitigated known malware, nothing else on the machine |
TRIAGED, then CLOSED after a quick check |
| Not mitigated, or malicious verdict with unexpected activity |
INVESTIGATING; open a PSA ticket and escalate |
| Legitimate admin tool or line-of-business software flagged |
FALSE_POSITIVE, with a comment naming the software and who confirmed it |
| Same detection across many machines at once |
Treat as one event; investigate the common source before closing any |
Updating the Investigation (write, off by default)
acronis_update_investigation_state changes an incident's investigation
state, adds a comment, or links an external ticket. Body fields: state,
comment, ticket_id, ticket_subject, assignee, assignee_id, and
priority (LOW, MEDIUM, HIGH, CRITICAL). Pass customer_id in
query with a partner-level API client.
- It's off by default. If it isn't in the tool list, writes are turned
off for the Acronis connector; tell the operator to update the incident in
the console.
- When writes are on, Conduit puts it at the write tier (not admin).
- Put the PSA ticket number in
ticket_id so the incident and the ticket
point at each other.
- Never set
FALSE_POSITIVE or CLOSED on an unmitigated incident without
the operator's explicit confirmation.
- Send an
Idempotency-Key header when retrying after a network error, so a
retry doesn't add the same comment twice.
What This Connector Can't Do
Starting a response action (isolating a machine, killing a process,
quarantining a file, rolling back) is not available through this
connector. Say so, and point the operator to the incident in the Acronis
console. Reading the status of an action started there is available.
Gotchas
incident_id filtering on acronis_fetch_incidents only works for a
single customer, so pass customer_id with it.
- Multi-workload incidents span several machines. Pass
with_multi_workload: true to get the workloads list; without it you
see one machine.
- Incidents that were merged into another are hidden unless you pass
with_transferred: true.
- Incident dates use
range(from, to) and ge(from), not the nanosecond
operators that alerts use.
Related Skills
1---2name: acronis-edr-incidents3description: >4 Endpoint Detection and Response (EDR) incident review in Acronis Cyber5 Protect Cloud: listing open incidents across customers, reading an6 incident's detections, activities and response actions, checking the7 status of a response action started in the console, and updating the8 investigation state or adding a comment (off by default, write tier in9 Conduit). Starting response actions is not available.10when_to_use: >-11 When an MSP needs to review Acronis EDR or Cyber Protect security incidents,12 triage open incidents by severity, read what happened on an endpoint,13 check whether an isolation or other response action finished, or record an14 investigation decision. Use when: acronis incident, acronis edr, acronis15 malware detected, cyber protect incident, acronis investigation state,16 acronis isolate status, or security incident review.17metadata:18 source: https://skillmd.com/skills/wyre-ai/acronis-edr-incidents19---2021# Acronis EDR Incidents2223## Overview2425Acronis EDR groups related detections on an endpoint into an incident. Each26incident has a severity, a verdict, a mitigation state (was the threat27stopped) and an investigation state (has a person looked at it). An MSP's job28is to make sure every incident that isn't auto-mitigated gets looked at, and29that the investigation state reflects reality.3031## Anti-triggers3233- **Backup failures and missed backups** — those are alerts, not incidents.34 Use `acronis-backup-health`.3536## Key Concepts3738| Field | Values |39|-------|--------|40| `severity` | `LOW`, `MEDIUM`, `HIGH`, `CRITICAL` |41| `verdict` | `SUSPICIOUS`, `MALICIOUS` |42| `mitigation_state` | `NOT_MITIGATED`, `MITIGATED`, `AUTO_MITIGATED` |43| `state` (investigation) | `NOT_STARTED`, `INVESTIGATING`, `TRIAGED`, `FALSE_POSITIVE`, `CLOSED` |44| `incident_category` | Such as `MALWARE_DETECTED`, `PROCESS_DETECTED`, `URL_BLOCKED`, `MS_DEFENDER` |4546`is_mitigated` is a simple true/false filter on whether the threat was47stopped. `positivity` is a confidence score from 0 to 10 that you can filter48with `range(min, max)`.4950## Workflow: Daily Incident Review51521. **Open incidents for a customer.** Call `acronis_fetch_incidents` with53 `customer_id`, `state: "or(NOT_STARTED,INVESTIGATING)"` and54 `created_at: "ge(<start date>)"`. With a partner-level API client, always55 pass `customer_id`; without it the call uses the API client's own tenant.562. **Unmitigated first.** Re-run with `mitigation_state: "NOT_MITIGATED"`.57 Those are threats Acronis didn't stop, and they come before everything58 else regardless of severity.593. **Then by severity.** `severity: "or(HIGH,CRITICAL)"` next, then the rest.604. **Page.** Use `limit` and `cursor`. Keep every other parameter exactly the61 same between pages or the cursor is rejected.625. **Read one incident.** `acronis_fetch_incident` with `path.incident_id`,63 `customer_id`, and `with_detections`, `with_activities` and64 `with_incident_actions` set to `true`. Detections say what was seen,65 activities say what happened on the machine, and incident actions say what66 was done about it.676. **Check a response action.** If someone isolated the machine or killed a68 process from the console, call `acronis_fetch_response_action_status` with69 the incident ID and the action's `activity_id` from step 5.7071## Deciding the Outcome7273| Situation | Typical investigation state |74|-----------|-----------------------------|75| Auto-mitigated known malware, nothing else on the machine | `TRIAGED`, then `CLOSED` after a quick check |76| Not mitigated, or malicious verdict with unexpected activity | `INVESTIGATING`; open a PSA ticket and escalate |77| Legitimate admin tool or line-of-business software flagged | `FALSE_POSITIVE`, with a comment naming the software and who confirmed it |78| Same detection across many machines at once | Treat as one event; investigate the common source before closing any |7980## Updating the Investigation (write, off by default)8182`acronis_update_investigation_state` changes an incident's investigation83state, adds a comment, or links an external ticket. Body fields: `state`,84`comment`, `ticket_id`, `ticket_subject`, `assignee`, `assignee_id`, and85`priority` (`LOW`, `MEDIUM`, `HIGH`, `CRITICAL`). Pass `customer_id` in86`query` with a partner-level API client.8788- It's **off by default**. If it isn't in the tool list, writes are turned89 off for the Acronis connector; tell the operator to update the incident in90 the console.91- When writes are on, Conduit puts it at the **write** tier (not admin).92- Put the PSA ticket number in `ticket_id` so the incident and the ticket93 point at each other.94- Never set `FALSE_POSITIVE` or `CLOSED` on an unmitigated incident without95 the operator's explicit confirmation.96- Send an `Idempotency-Key` header when retrying after a network error, so a97 retry doesn't add the same comment twice.9899## What This Connector Can't Do100101Starting a response action (isolating a machine, killing a process,102quarantining a file, rolling back) is **not available** through this103connector. Say so, and point the operator to the incident in the Acronis104console. Reading the status of an action started there is available.105106## Gotchas107108- `incident_id` filtering on `acronis_fetch_incidents` only works for a109 single customer, so pass `customer_id` with it.110- Multi-workload incidents span several machines. Pass111 `with_multi_workload: true` to get the `workloads` list; without it you112 see one machine.113- Incidents that were merged into another are hidden unless you pass114 `with_transferred: true`.115- Incident dates use `range(from, to)` and `ge(from)`, not the nanosecond116 operators that alerts use.117118## Related Skills119120- [api-patterns](../api-patterns/SKILL.md) - Headers, pagination and errors121- [tenants-and-usage](../tenants-and-usage/SKILL.md) - Find the customer tenant UUID