Breakwater Provenance

Evidence, Validation & Provenance

Make software risk traceable to its source.

Connect findings to exact source, independent validation and an attributable review. Bring software dependencies and cryptographic evidence into the same decision.

Provenance / Evidence map
Source, software and cryptographic evidence connected to decision paths.
Source, software and cryptographic evidence connected to decision paths.
From finding to accountable review

Give every finding a source,
a review and an owner.

1V

Locate

Record the detector match and exact source context.

2V

Replay

Check the cited evidence against the frozen revision.

3V

Challenge

Examine assumptions and counter-evidence.

4V

Decide

Record the named reviewer’s decision and rationale.

Evidence replay / Human review

Recheck the evidence.
Resolve disputed findings.

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.

Provenance / Validation & review
Evidence replay and an attributable human review in the same finding.
Evidence replay and an attributable human review in the same finding.
Software supply chain / PQC readiness

Know the dependencies.
Locate the cryptography.

Use SBOM and CBOM evidence to identify the software components and cryptographic uses that need attention, then trace them back to their source.

One review, two connected inventories.

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.

Provenance / SBOM + CBOM
Software dependencies and cryptographic uses with their source evidence.
Software dependencies and cryptographic uses with their source evidence.
AI assistance / Evidence remains inspectable

Explain the issue.
Prepare a fix for review.

01

Explain the source context

Use model assistance to understand the flagged code and the reasoning behind the finding.

02

Prepare a proposed fix

Give engineering a specific change to review alongside prerequisites and evidence.

03

Retain the validation record

Keep model explanations, deterministic checks and the human decision distinguishable.

Provenance / Resources

From product understanding to evaluation.

Start with the ASOC platform overview (PDF), then choose the detail your team needs.

Evaluate Provenance

Choose a source finding.
Follow the evidence through review.

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) →

What your evaluation should establish

  • A demonstration source revision and supported analysis scope; confirm readiness before supplying customer code.
  • A finding tied to an exact location and replayable evidence.
  • Visible validation state, assumptions and counter-evidence.
  • A human review record and a clear remediation owner.
Evaluation scope and demo details

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.