PARTNERS

Add selected Workbench capabilities through bounded OEM and partner integrations

Explore Partner Integrations
aisecurityllc
Sign inScope an AI Security Review
aisecurityllc
Scope an AI Security Review
← Deliverablesexample
example

Figure System Vertical Slice

Three Markdown-authored figures compiled through the Publication DSL.

Public sample
Client deliverable
public-sample
System
Figure System Vertical Slice
Environment
Production pilot

# Figure System Vertical Slice

SP-01

Keep the scanner. Add the finding and evidence plane.

The partner retains the scanner product and customer workflow while SecEng adds evidence depth, validation discipline, and attack-path context.

Three-part flow from a partner scanner through the SecEng OEM engine into a partner-native enriched result.

PARTNERPartner scannerTarget orapplicationExisting scanfindingsCurrentvulnerabilityobjectLifecycle stateENGINESecEng OEM engineAI-nativefindingenrichmentEvidencestrengthValidationqueueAttackPathAnalysislinkageRemediationcontextReteststateRESULTPartner-native resultStructuredfindingEvidenceandprovenanceAttack-pathcontextValidationstatusRemediationguidanceFixed orreopenedsupport
SP-02

From candidate to defensible finding.

Detection is the beginning of the lifecycle, not the publication decision.

A governed finding lifecycle with evidence, validation, analyst review, claim readiness, remediation, and retest.

Primary finding lifecycle
  1. 1
    Detected candidate
  2. 2
    Deduplicated
  3. 3
    Evidence supported
  4. 4
    Validation queued
  5. 5
    Validated
  6. 6
    Analyst accepted
  7. 7
    Reportable finding
Claim-readiness gate
  • Public claim ready
  • Public claim with caveat
  • Internal only
  • Do not claim
SP-03

One representative finding. One measurable OEM pilot.

The pilot proves a product-native round trip rather than ending in a separate SecEng artifact.

A three-stage pilot contract showing partner inputs, SecEng proof work, and the returned partner-native result.

BOUNDED PILOTSecEng maps and validatesNormalize the findingcontractPreserve identifiers andprovenanceMap create and updatebehaviorValidate deduplicationand rescan behaviorProject evidence andremediation statePartner providesSanitized representativefindingTarget and attachment modelExternal identifier behaviorLifecycle statesPreferred ingestion pathPartner receivesPartner-ready findingmappingCreate or update workflowEvidence projectionFixed or reopened lifecyclesupportDocumented production pathPilot successIntegration fit • Lifecycle fit • Evidence preserved •Product-native return