Connect the evidence
Bring supplied observations and relevant context into a case your team can inspect.
Controlled Response & Verification
Bring evidence, competing explanations and response options into one case. Use AI investigation and digital rehearsal to prepare a proposal with explicit scope, recovery and human authority.

Bring supplied observations and relevant context into a case your team can inspect.
Use reasoning roles to test the attack story, preserve dissent and identify missing evidence.
State the target, scope, expected effect and recovery needs so operations can assess the proposed intervention.
See the network scenario, the Council’s reasoning and the proposed response together. Follow these three parts of the product view to understand how the investigation reaches a human decision.

Follow the systems and relationships involved in the scenario. See the scope behind the attack story.
Read how the five roles assess the scenario, including the Skeptic’s alternative explanation.
Inspect the proposed containment and its scope. The decision remains with a human before operational change.
A response proposal should make its consequences understandable to security and operations. Review the intervention, rehearse the scenario and identify who can authorize the next step.
Compare the modeled effect and recovery assumptions.
Check the target, permissions, risk and named approvers.
Define who carries out the change and what evidence the team will collect afterwards.

Plan the supported imports and read-only integrations that bring relevant observations into the case. Keep the original systems available for deeper investigation.
Establish the approvers, change process, recovery owner and follow-up evidence before the proposed action moves into operations.
Start with the ASOC platform overview (PDF), then choose the detail your team needs.
Use a reproducible case with known observations. Compare the Council’s explanations, missing-evidence questions and response proposal against your current investigation process.
Read the Response evaluation brief (PDF) →Council recordings and response views use scripted scenarios; the recordings do not demonstrate live containment. Rehearsal uses a modeled environment. Model configuration, integrations, approval policy and execution responsibilities are established for the selected evaluation. Historical product names may remain in recordings.