A board does not want to hear that you processed three billion events last week. They want to hear which incidents mattered, which hosts were contained and when each incident was resolved, with the evidence available for review. Edg3 keeps isolation records, case status and investigation evidence together.
Traditional SIEM reports often stop at events ingested, alerts triggered and rules tuned. Edg3 also records host isolation, case status and each analyst disposition, so teams can tell a detection from a contained host and a resolved incident. Resolution is recorded by an analyst, not inferred from an alert closing.
For a qualifying ransomware verdict on Windows, the agent can isolate the host locally. Any other isolation needs analyst approval, and the approver is recorded. A safety deadman, on by default, lifts any isolation after 30 minutes without the control channel, or after 24 hours unless the console renews an emergency isolation. When the isolated incident belongs to a case, each isolation step is added to the case record automatically.
Analysts group related incidents into a case, move it from open to investigating, add notes and hand-offs, and mark each incident true positive, false positive or benign alongside the AI investigation’s cited evidence.
An analyst resolves the incident. The time from the first analyst action to resolution is recorded and feeds the mean time to resolve in the incident outcome report.
Edg3 records when an analyst first acted on an incident and when it was resolved. The incident outcome report turns those two points into mean time to resolve. Containment, eradication and recovery are not tracked as separate stages, so they are not estimated.
These measures can be grouped for operational reporting where the underlying records have the required timestamps. Teams should validate the source and coverage before using them for external assurance.
Edg3 reports can combine case status, available timings and evidence references. A human owner should review the result before it enters a board, insurer or regulatory pack.
Reviewers need to understand what was observed, what was not collected and what action was taken. Edg3 keeps case history and supports reports and exports, but the contents depend on the telemetry, collection workflow and provider actions enabled for that tenant.
An export can shorten evidence gathering, but it does not determine materiality, satisfy a notification obligation or guarantee an insurance outcome. The accountable owner must validate the record and its coverage before external use.
The current policy library maps evaluated endpoint checks to relevant framework controls. A mapping shows why a check may support a control; it is not a certification.
Edg3 plans use an endpoint allowance and retention period rather than an ingestion-volume fee. Annual prices below are the current plan catalog; month-to-month is also available. Starter, Professional and Enterprise are subscriptions you can buy online, and each renews until you cancel.
| Edition | Annual billing | Month-to-month |
|---|---|---|
| Starter · up to 150 endpoints | $5,748/year | $579/month |
| Professional · up to 500 endpoints | $11,388/year | $1,149/month |
| Enterprise · up to 1,500 endpoints | $22,788/year | $2,299/month |
| Enterprise Plus+ | Contact Sales | Contact Sales |
Annual figures correspond to effective monthly rates of $479, $949 and $1,899. Edition features, retention and configured providers should be confirmed in the order scope rather than inferred from a headline price.
A valid comparison needs endpoint count, retention, hosting, enabled integrations, support and migration effort. Edg3’s no-per-GB model is clear; competitor savings should not be quoted without a documented customer baseline.