Skip to content

OpenAI's Codex Security CLI and TypeScript SDK for finding, validating, and fixing security vulnerabilities. npm: https://www.npmjs.com/package/@openai/codex-security

docs(imports): show how to retrieve selected scanner evidence (#2210)

Michael D'Angelof369ffd4aae8
diff --git a/docs/scanner-imports/blackduck.md b/docs/scanner-imports/blackduck.md
index 5ee4c1555..d64398a0d 100644
--- a/docs/scanner-imports/blackduck.md
+++ b/docs/scanner-imports/blackduck.md
@@ -47,6 +47,12 @@ repository ownership.
### Export the BOM-6 collection
+The [Black Duck SCA MCP](https://github.com/blackducksoftware/sca-mcp#capabilities)
+can locate the project version with `search_projects_versions`. Its
+`fetch_project_vulnerabilities` tool returns a summary and CSV. Use the REST
+export below for BOM rows. The MCP’s `scan` starts a new scan. Coverity and
+Polaris reports use different formats.
+
Request the project version’s `vulnerable-components` relation with media type
`application/vnd.blackducksoftware.bill-of-materials-6+json`. The importer
requires BOM-6. If the deployment only serves BOM-8 or another inventory format,
diff --git a/docs/scanner-imports/endor.md b/docs/scanner-imports/endor.md
index 034914c77..8ee628268 100644
--- a/docs/scanner-imports/endor.md
+++ b/docs/scanner-imports/endor.md
@@ -51,9 +51,11 @@ available. See the [Endor CLI API](https://docs.endorlabs.com/developers-api/cli
and [Finding model](https://github.com/endorlabs/endorlabs-sdk/blob/8a41756890c2dee3bb089fee881cae4f2adbde03/src/endorlabs/generated/models/finding_service.py).
The [Endor Labs Agent Kit for Codex](https://github.com/endorlabs/ai-plugins/tree/main/plugins/codex/endor-labs-agent-kit)
-can help with setup or investigation. Findings Browser summaries, counts, and
-field-masked results omit fields needed for import. Codex Security reads the
-saved export offline. It does not change findings in Endor.
+can identify UUIDs. For a fresh export, append `and uuid in ["UUID_A","UUID_B"]`
+to the project and context filter above, using the requested UUIDs. For a saved
+export, select their complete objects from `list.objects`. Before import, verify
+the preview contains each requested UUID once, no other IDs, and no exclusions.
+[Endor filter syntax](https://docs.endorlabs.com/developers-api/rest-api/using-the-rest-api/filters#values)
### SARIF and repeat imports
diff --git a/docs/scanner-imports/inspector.md b/docs/scanner-imports/inspector.md
index ba72afe16..88ae3d376 100644
--- a/docs/scanner-imports/inspector.md
+++ b/docs/scanner-imports/inspector.md
@@ -55,6 +55,16 @@ repository. Project names can match several integrations. With
`inspector2:ListFindings` permission, replace the example Region, account ID, and
repository resource ID in this export.
+For ARNs selected with the [AWS Codex plugin](https://github.com/aws/agent-toolkit-for-aws#codex),
+keep the Region, account, and repository filters below. Add a `findingArn` array
+with one `{"comparison":"EQUALS","value":"FINDING_ARN"}` per ARN, up to
+[10 per request](https://docs.aws.amazon.com/inspector/v2/APIReference/API_FilterCriteria.html#inspector2-Type-FilterCriteria-findingArn).
+Combine the native `findings` arrays from all fully paginated batches into one
+`{"findings":[...]}` report. From a saved scoped export, select those rows locally.
+If the selected rows cannot establish the repository together, request a native
+capture of those same ARNs with the missing evidence. Before import, verify the
+preview contains each requested ARN once, no other ARNs, and no exclusions.
+
```bash
set -eu
umask 077
diff --git a/docs/scanner-imports/semgrep.md b/docs/scanner-imports/semgrep.md
index 56093a801..3a51a4114 100644
--- a/docs/scanner-imports/semgrep.md
+++ b/docs/scanner-imports/semgrep.md
@@ -84,10 +84,17 @@ Request `issue_type=sast` and save the original project lookup and findings
pages as response text. Pass each findings page separately. The SDK checks
every row on pages that contain a selected ID for conflicting product evidence.
When a page contains only fields shared by several products, the original
-request filter identifies the product. Guardian and MCP return different
-records. [Semgrep Web API](https://docs.semgrep.dev/semgrep-appsec-platform/semgrep-api),
-[Guardian for Codex](https://docs.semgrep.dev/semgrep-guardian/ide-setup/codex),
-[Semgrep MCP](https://github.com/semgrep/semgrep/blob/fe209763a4a2ccfcdf6434e6c332edc24a2f586e/cli/src/semgrep/mcp/server.py)
+request filter identifies the product.
+
+To find existing Code findings in Codex, sign in to Guardian and ask for the
+deployment, project and full ref you want to inspect. Guardian returns a
+selection for review. For this SDK import, confirm the candidate findings in
+the original Web API results and use the IDs from those records. The SDK also
+accepts saved responses from an authorized operator. Fetching new responses
+directly requires Web API read access.
+[Guardian sign-in](https://docs.semgrep.dev/semgrep-guardian/quickstart) ·
+[Query existing findings](https://semgrep.dev/products/product-updates/query-your-semgrep-findings-by-asking-guardian/) ·
+[Findings Web API](https://docs.semgrep.dev/api-reference/v1/findingsservice/list-code-supply-chain-or-ai-powered-detection-findings)
Use the full ref from the findings, such as `refs/heads/main` or
`refs/tags/v1`. Supply the credential-free HTTP(S) repository URL you verified
diff --git a/docs/scanner-imports/snyk.md b/docs/scanner-imports/snyk.md
index fb2994e3b..dfcb7da62 100644
--- a/docs/scanner-imports/snyk.md
+++ b/docs/scanner-imports/snyk.md
@@ -46,6 +46,10 @@ same source key for subsequent exports in this format.
## Reference
+Use the saved report for an earlier scan. `snyk test` and the Studio plugin’s
+`snyk-findings-export` scan the current workspace. Evo MCP’s `query_issues`
+retrieves AI asset policy violations. [Studio export scope](https://github.com/snyk/studio-recipes/blob/3752dd05a462184dcce44af3c247f287b41e35de/plugins/codex/skills/snyk-findings-export/SKILL.md#L15-L20) · [Evo MCP tools](https://docs.snyk.io/agent-security/evo-by-snyk/platform-surfaces/evo-mcp-server#policies-and-issues)
+
### Native CLI JSON
To create a report, run the authenticated Snyk CLI with the project's package
diff --git a/docs/scanner-imports/veracode.md b/docs/scanner-imports/veracode.md
index f70b68a16..d105bd2ae 100644
--- a/docs/scanner-imports/veracode.md
+++ b/docs/scanner-imports/veracode.md
@@ -37,9 +37,10 @@ static analysis path, line, and module. The importer does not verify that the
path exists in the checkout or infer a column or Git commit.
Imported findings start unassessed. Replaying an upstream resolution does not
-verify a fix. Omitted findings remain stored. Pipeline Scan JSON, sandbox
-findings, SCA, DAST, policy pass/fail summaries, and the findings converter’s
-SARIF output use other formats.
+verify a fix. Omitted findings remain stored. `veracode static scan <package>`
+runs a new Pipeline Scan with different flaw IDs. Retrieve existing policy
+flaws with the Findings API export below. Sandbox, SCA, DAST, policy summaries,
+and converted SARIF also use other formats. [Veracode static scan](https://docs.veracode.com/r/veracode_static_scan)
For SDK replay with the Veracode provider, keep each finding’s original
`source_finding_id` and `evidence.source_data` so the SDK can verify its
diff --git a/docs/scanner-imports/wiz.md b/docs/scanner-imports/wiz.md
index 54a786ca9..d31bb4d0f 100644
--- a/docs/scanner-imports/wiz.md
+++ b/docs/scanner-imports/wiz.md
@@ -6,8 +6,9 @@ repository package vulnerability CSV, including gzip-compressed files.
## Quick start
-For a package vulnerability export, select the repository in Wiz **Vulnerability
-Findings**, choose **Save as → Report**, then select **Repository Branch**,
+For package vulnerabilities, apply the requested repository, branch or build,
+and finding filters where available in Wiz **Vulnerability Findings**. Choose
+**Save as → Report**, then **Repository Branch**,
**JSON** and **Detailed** columns. Download the completed report outside the
checkout. From the destination checkout root, set the path and replace `TENANT_ID`
with your stable Wiz tenant identifier.
@@ -22,12 +23,18 @@ codex-security publish findings "$report" \
## Import and verify
+For an explicit selection, proceed only if the JSON preview's `excluded` array
+is empty and `findings[].source_finding_id` lists each requested occurrence ID
+exactly once, with its family prefix where applicable, and no other IDs.
Check that the preview covers the intended assets or builds and review excluded
records. Reuse the source key for the same tenant and finding family across
exports and project filters. [Save or publish and verify](README.md#save-or-publish-and-verify).
## Reference
+- **Connected Wiz account.** List findings for the repository and family, then
+ retrieve the selected records by Wiz finding ID. If a shared pull request scan
+ event cannot identify each occurrence, request a scoped native capture.
- **Native JSON.** Package vulnerabilities accept individual records or
`data.vulnerabilityFindings.nodes`. SAST, repository secrets and IaC require
the named `data.sastFindings.nodes`, `data.secretInstances.nodes` or