Deep Dive · Risk & Outcomes

Security that reports in verbs, not noise.

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.

The Outcome Framework

Track the response state, not just the alert count.

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.

Contained.

The blast radius stops growing.

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.

Investigated.

The evidence is on the case.

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.

Resolved.

The incident is closed, with its timing.

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.

Time-to-Outcome

Resolution timing grounded in recorded events.

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.

Detected
Incidents recorded in the reporting period
Resolved
Incidents an analyst has resolved
MTTR
Mean time from first analyst action to resolution

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.

The board-ready one-pager

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.

External Review

Exportable evidence with its coverage stated.

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.

What Edg3 keeps for review

External evidence still needs an owner

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.

Compliance Evidence

Mapped checks without implied certification.

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.

CIS BenchmarksConfiguration baselines
Supported Windows, Ubuntu and macOS checks are grouped into platform-specific policy packs. A result describes the state observed on the evaluated host.
NIST 800-53Control mapping
Relevant policy checks carry NIST control annotations so teams can link observed host posture to an evidence-gathering workflow. Applicability remains the customer’s decision.
SOC 2 TSCTrust Services Criteria
TSC annotations help organise technical evidence. They do not constitute an auditor’s opinion or show that non-technical criteria have been assessed.
HIPAA 164.312Technical safeguards
Selected checks are annotated where they may support technical-safeguard evidence. Legal applicability, completeness and risk analysis remain outside the platform score.
PCI DSSPayment security controls
Relevant technical checks carry PCI DSS annotations. The view shows evaluated posture and coverage gaps, not a PCI compliance determination.
CoverageWhat was not assessed
Framework reporting should state the number of applicable, evaluated and unavailable controls. A framework whose posture checks only errored can still show a score; confirm coverage before relying on it.
The Economic Case

Endpoint-tier pricing with no per-GB ingestion fee.

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.

Compare like with like

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.