Locate
Record the detector match and exact source context.
Evidence, Validation & Provenance
Connect findings to exact source, independent validation and an attributable review. Bring software dependencies and cryptographic evidence into the same decision.

Record the detector match and exact source context.
Check the cited evidence against the frozen revision.
Examine assumptions and counter-evidence.
Record the named reviewer’s decision and rationale.
Keep source identity, replay status and counter-evidence beside the finding. Reviewers can see what was checked and record why a claim is accepted, rejected or left open.

Use SBOM and CBOM evidence to identify the software components and cryptographic uses that need attention, then trace them back to their source.
Review direct and transitive software dependencies alongside code-level cryptographic use. Give engineering and security teams a common starting point for upgrades and migration planning.

Use model assistance to understand the flagged code and the reasoning behind the finding.
Give engineering a specific change to review alongside prerequisites and evidence.
Keep model explanations, deterministic checks and the human decision distinguishable.
Start with the ASOC platform overview (PDF), then choose the detail your team needs.
Start with a demonstration repository in a supported language and a frozen revision. Ask a second reviewer to replay the evidence, challenge the finding and assess whether engineering has enough context to act.
Read the Provenance evaluation brief (PDF) →The views use demonstration projects. Source analysis and manifest inventories do not establish runtime reachability or exploitation. Confirm supported languages, source-data handling, model configuration and evaluation readiness before providing customer code. Provenance supplies review evidence and proposed changes; engineers remain responsible for implementing and testing fixes.