Skip to content

Developer portal

Convert workflow

Convert maps cryptographic risk into prioritized work, executes changes, and verifies outcomes.

Last updated: 2026-06-09

From backlog to action

Convert starts after assessment. Pull recommendations for a specific scan, align owners and deadlines, and push bounded changes into engineering systems.

1) Build a remediation plan

  • Fetch actions: GET /tenant/scans/{scan_id}/remediation
  • Update status and owner: PATCH /tenant/scans/{scan_id}/remediation
  • Pull supporting rationale: GET /tenant/scans/{scan_id}/remediation/intelligence

2) Automate where safe

Launch automation with POST /tenant/scans/{scan_id}/remediation/automate. Use POST /tenant/scans/{scan_id}/integrations/push to mirror accepted actions to ticketing or CLM systems.

3) Simulate and de-risk changes

Use POST /tenant/scans/{scan_id}/remediation/simulate to compare rollback windows, blast radius, and policy impact before promoting runbooks.

4) Re-verify and publish evidence

Complete the cycle with POST /tenant/scans/{scan_id}/remediation/verify and a new POST /pqc/scan if inventory changed. Publish updated evidence through GET /tenant/scans/{scan_id}/report.