SP-04

Partner Findings Lifecycle

AI-native findings return into the partner product with lifecycle state preserved through review, remediation, rescan, and retest.

integration round trip

Normalize • Enrich • Return • Retest

1
Partner finding or scan evidence
Target • Request/response evidence • Workflow observation • Stable issue identity
2
Workbench enrichment
AI-native path • Evidence qualification • Authority context • Validation state • Remediation
3
Partner-native return
Preserved issue identity • Reporting state • Remediation status • Retest condition
4
Rescan or retest
Lifecycle history remains connected to the original issue

Return to stage 1 — lifecycle state preserved

The scanner remains the system of engagement. The OEM Engine adds the selected Workbench analysis behind it and returns the result through the workflow the customer already uses.

About this figure

Partner Findings Lifecycle describes a round-trip integration pattern for scanner providers in which AI-native findings are enriched by Workbench analysis and then returned to the partner product without losing lifecycle state. The flow begins with partner scan context tied to stable repository and finding identifiers, alongside code, configuration, or workflow targets and the partner’s native scan and finding context. Workbench enrichment adds evidence, context, and claim-state signals, optionally incorporating graph or Attack Path Analysis input to improve analysis quality. The resulting finding is then surfaced back in the partner product with preserved remediation state, rescan state, and evidence history, so reviewers can track a finding consistently through triage, fix, validation, and closure. This pattern keeps AI-native analysis useful while remaining aligned with partner-native workflows and state management.

Embed in a route

Citation

Partner Findings Lifecycle (SP-04). AI Security LLC Figure Library. https://aisecurity.llc/publication-dsl/figures/SP-04