* feat(imports): import CrowdStrike FCS IaC findings locally
Add a crowdstrike file reader for saved FCS CLI 4.x IaC JSON reports
(rule_detections). Each detection becomes one iac or secret finding with
typed rule, configuration and remediation details. Like Tenable, the
reader is local only and binds findings to --source-repository-url,
which must match a fetch remote of the selected checkout.
FCS writes detection paths relative to its working directory, so the
guide asks users to scan from the checkout root. Paths that are absolute
or leave the checkout are excluded. The source finding ID includes the
line, because detections of one rule on one resource can differ only by
line.
* fix(imports): import CrowdStrike reports without a Git checkout
An FCS IaC report describes files relative to the directory where the CLI
ran and names no repository, so requiring a matching Git remote did not
bind the report to anything. Import into any directory instead, and check
that every detection's file exists there. A supplied
--source-repository-url still records the repository, adds typed details
and must match a fetch remote when the directory is a Git checkout.
Detections in registry or Git modules name the calling file with a line
from inside the module. Use the call line that FCS states in
module_remediation, or no line, and include the module path in the
finding ID.
* docs(plugin): describe CrowdStrike FCS imports in the publish-findings skill
Tell Codex when to use --provider crowdstrike, how to run an installed FCS CLI from the import directory, which report to import after a nonzero exit, and to ask for a report instead of installing FCS or passing Falcon credentials.
* fix(imports): read the CrowdStrike module call line in linear time
Search module_remediation for the detection file's exact call phrase instead of a lazy regex. A crafted report could make the regex quadratic: a 2 MB module_remediation took about two minutes to read.
* fix(imports): stop CrowdStrike imports when a scanned file changed
FCS records each scanned file's SHA-256 as file_sha256. Compare it with
the file in the selected directory and stop, naming the file, when they
differ. Before, a report of another commit imported without an error and
could store lines that no longer point at the detected configuration.
The check follows file symlinks, as FCS does, and reads only regular
files.
* docs(imports): add CrowdStrike scan examples and Codex validation steps
Fix the FCS scan command: FCS needs an existing output directory whose
name has no dot. Show a remote git:: scan pinned with ?ref= and a
checkout of the same commit, and note that a //subdir URL gives paths
from that subdirectory. Add a shortened sample report, and show how to
pass imported findings to codex-security validate, for all findings or
for one scan.
* docs(imports): link CrowdStrike imports to the shared imported finding workflow
Other provider pages do not describe validation or patching. Remove the
CrowdStrike validation section and link the readback step to the shared
section on working with imported findings.
* fix(imports): keep CrowdStrike module lines in git:: reports
In a git:: report, FCS writes the detection file, its module_source and
the calling file in module_remediation with a leading slash. The reader
removed the slash from the file before it compared the three, so every
module detection lost its line. Compare them as FCS wrote them. In a
git:: scan of a public Terraform repository, 102 of 396 findings had no
line before this change and none after.
* fix(imports): record and check the repository of CrowdStrike git:: reports
A git:: report names the repository that FCS cloned, but the reader
ignored it. A report of one repository could be saved under another one
whose files were identical. For a git::https:// scan, record that
repository without its //subdirectory and ?ref=, and keep the scan path
in the report and in each finding's source data. When
--source-repository-url is given, it must name the same repository, on
import and on replay. Without it, the scanned repository gives typed
details but does not bind the checkout to a fetch remote, so clones from
self-hosted servers over SSH keep importing. Other git:: URL forms
import as before.
* fix(imports): import CrowdStrike git:: reports of URLs with a user name
When the scanned URL has a user name, FCS writes each detection file,
module source and calling file after the scanned URL instead of after a
slash, and the reader excluded every detection. Remove that prefix. FCS
removes the user name and token from the report's path and keeps them
only in flags.path, which the reader does not read.
* fix(imports): check replayed CrowdStrike locations against the native detection
A replayed preview with cleared or edited locations skipped the file
check, and saved findings without the scanned location. Rebuild the
location from the retained FCS detection, require each finding to show
exactly that location, and check that file and its hash.
Carry forward the reader contributed in #2606. Include it in the SDK package and validate repository claims when preparing an import.
Co-authored-by: dy-armorcode <109572335+dy-armorcode@users.noreply.github.com>
* feat(plugin): guide Codex through scanner acquisition and reviewed publication
* docs(plugin): name the stored publication calls and explain partial imports
* fix(cli): make saved scan selection and matching explicit
* fix(cli): resolve command paths and isolate standalone actions
* fix(cli): preserve updater result and diagnostics
* fix(cli): simplify finding imports and protect export files
* test(plugin): initialize Windows registration fixtures explicitly
* test(cli): distinguish the legacy publish check selector in help
* test(cli): check the requested JSON format in raw CSV diagnostics
* fix(cli): retain suggestions for unknown commands
* style(cli): format argument routing regressions
* test(cli): return worktree selection in authentication fixture
* fix(cli): reject missing global values before command dispatch
* fix(cli): preserve short help before a command
* fix(cli): reject switches as global option values
* fix(cli): identify package updates in generated agent guidance
* fix(cli): validate local inputs and make saved plans and hooks reusable
* fix(cli): bound batch scan spending and follow-up patches
* fix(cli): label total cost arguments in USD
* fix(cli): carry scan overrides into component plan commands
* fix(package): include the batch-cost module in the published SDK
* fix(cli): preserve local path and budget settings during preflight
* docs(cli): format policy and time-limit command references
* test(cli): pass Windows drive path explicitly as literal text
* fix(cli): close hook handles before replacing files on Windows
* fix(cli): bound batch scan spending and follow-up patches
* fix(cli): label total cost arguments in USD
* fix(package): include the batch-cost module in the published SDK
* fix(cli): skip unmetered owner suggestions under a total budget
* feat(cli): expose identifiers for saved scan follow-up
* test(sdk): exercise dedupe representatives in publication
* feat(cli): make project setup and authentication easier to inspect
* docs(cli): distinguish sign-in flows and credential sources
* feat(cli): link interrupted scans and imported evidence to their next commands
* fix(cli): make command help and discovery reflect runnable workflows
* build(sdk): include the command argument helper in package checks
* refactor(cli): reuse shell path quoting for project previews
* docs(cli): identify the shell used for Windows preview commands
* test(cli): account for the internal publication CSV in help coverage
* fix(cli): scope recovery hints to supported sessions and shells
* fix(cli): declare exclusive scan import sources in the schema
* refactor(cli): share credential locking and project preview preparation
* fix(cli): resolve repository arguments consistently during scan discovery
* refactor(cli): simplify the result handoffs and verify PowerShell recovery
* fix(cli): check sign-in from the same directory in every format
* fix(cli): preserve diagnostics when project initialization fails
---------
Co-authored-by: Codex <noreply@openai.com>
* feat(cli): expose identifiers for saved scan follow-up
* test(sdk): exercise dedupe representatives in publication
* feat(cli): link interrupted scans and imported evidence to their next commands
* fix(cli): make command help and discovery reflect runnable workflows
* build(sdk): include the command argument helper in package checks
* test(cli): account for the internal publication CSV in help coverage
* fix(cli): scope recovery hints to supported sessions and shells
* fix(cli): declare exclusive scan import sources in the schema
* fix(cli): resolve repository arguments consistently during scan discovery
* refactor(cli): simplify the result handoffs and verify PowerShell recovery
---------
Co-authored-by: Codex <noreply@openai.com>
* docs: add a local import guide for Semgrep hosted MCP findings
* docs: extend the hosted Semgrep import example through Cloud
* docs: clarify the Semgrep Cloud workspace prerequisite
---------
Co-authored-by: Michael D'Angelo <269034524+mldangelo-oai@users.noreply.github.com>
* fix(publish): explain when Cloud import is unavailable
`publish findings --to cloud` starts with the repository catalog. For a
ChatGPT account or deployment without Codex Security Cloud import, that
request returns 404 and the CLI printed only "Cloud import failed (HTTP
404). Not found", which does not say whether the repository, the file, or
the account was missing.
Keep the server's text and add the same explanation `publish scan` gives
for this case: Cloud import is not available for this account or
deployment. Other statuses and endpoints are unchanged.
* fix(publish): handle an empty catalog error response
* docs(imports): correct AWS Continuum and mktemp guidance
- Name the first AWS CLI v2 release with `aws continuum` (2.38.5); earlier
v2 releases reject the command.
- Say that validation results come with findings Continuum detects, while
findings submitted to Continuum can omit them.
- macOS `mktemp -d` ignores TMPDIR, so the advice to set TMPDIR did not
move report directories there. Suggest a template instead.
* docs(imports): honor temporary report paths and clarify validation evidence
* fix(imports): read Continuum weakness IDs from subCategory
Findings that AWS Continuum detects itself omit cweIds and name their
weakness only in subCategory, for example "CWE-89: Improper
Neutralization ...". The reader mapped weakness_ids from cweIds alone,
so every native Continuum code finding imported without a CWE.
Fall back to the leading CWE ID in subCategory when cweIds is absent.
Explicit cweIds still win, and the previous-release replay projection
keeps reading cweIds only.
* fix(imports): preserve Continuum replay and evidence admission
* fix(cli): point native sign-in hints at codex-security login
After starting browser sign-in, native Codex prints "On a remote or
headless machine? Use `codex login --device-auth` instead." Running that
command signs in to the regular Codex home, not the Codex Security
credential home, so the suggested recovery does not help.
For the sign-in commands that pass native output straight through
(login, login status and logout), forward native stderr through a small
streaming rewrite of `codex login` to `codex-security login`. Stdin and
stdout stay attached to the terminal, other output is unchanged, and only
a possible partial match is held back between chunks.
* fix(cli): forward login hints and reap interrupted sign-ins
* fix(auth): sign in with the credential storage set in Codex config
On macOS, a fresh `codex-security login` could not be used to publish to
Cloud. Scans write `cli_auth_credentials_store = "auto"` into the Codex
Security credential home, so native login saved the token in the system
keyring and removed auth.json, while Cloud publication reads file-backed
credentials only.
The documented fix, setting `cli_auth_credentials_store = "file"` in
Codex config.toml and signing in again, had no effect: `login` used
whatever the last scan wrote, and SDK scans ignored the user's Codex
config for sign-in settings (only skill commands mirrored it).
- Layer the user's Codex config sign-in settings
(cli_auth_credentials_store, forced_login_method,
forced_chatgpt_workspace_id) between the wrapper defaults and explicit
overrides in mergedCodexConfig, so scans, their runtime config and Deep
Scan workers use them. A Codex config that cannot be read or parsed
sets no preference here; the commands that use it still report why.
- Before `login` and `login status`, write the keys that config sets into
the credential home. Native argv is unchanged, so managed policy still
wins. Unset keys and `logout` leave the stored location alone.
- Make the Cloud sign-in error and CLI docs name the setting and command.
* fix(cli): exit interrupted login when stderr stops draining
* fix(auth): keep sign-in, credential cleanup, and Cloud publication consistent
* fix(sdk): cancel queued logins without aborting settled operations
* test(sdk): guard the budget cancellation wait after usage is recorded
---------
Co-authored-by: mldangelo <michael.l.dangelo@gmail.com>
* feat(imports): enable external scanner imports by default
Register collection, publication, and readback commands directly. Keep provider credential checks, repository access checks, and upload confirmation in their existing paths. Clients can remove the retired environment variable.
* docs(imports): make scanner provider guides evergreen
Index the scanner report readers and supported destinations. Use installed CLI examples, distinguish repository helpers from packaged tools, and describe Cloud verification and retry steps from the preview and receipt.
* docs(integrations): clarify connector setup and publication paths
* docs(integrations): simplify publication history and storage guidance
* docs(triage): specify how to exhaust Jira search results
---------
Co-authored-by: Michael D'Angelo <269034524+mldangelo-oai@users.noreply.github.com>
* fix(deep-scan): account for comparison turns and report actual review coverage
* fix(deep-scan): report completed audits and batch consolidation
* fix(deep-scan): include measured usage in the completion receipt
* docs(deep-scan): use the completion receipt for final reporting
* ci: retry managed Code Quality after GitHub installation rate limit
* test(deep-scan): restore the coordinator stop error import
(cherry picked from commit 7630eea34c)
* Remove duplicate coordinator test import after main integration
* fix(deep-scan): report completed audits and batch consolidation
* fix(deep-scan): include measured usage in the completion receipt
* docs(deep-scan): use the completion receipt for final reporting
* ci: retry managed Code Quality after GitHub installation rate limit
* test(deep-scan): restore the coordinator stop error import
(cherry picked from commit 7630eea34c)
* fix(imports): preserve Guardian attribution and Snyk evidence on replay
* fix(imports): match Guardian URLs with local checkout semantics
* fix(imports): verify retained Guardian findings against selection scope
* ci: retry managed Code Quality after GitHub installation rate limit
* Assert the canceled lifecycle emitted by an aborted component scan
* fix(imports): bound remote error bodies and retain HTTP failure context
* ci: retry managed Code Quality after GitHub rate limiting
GitHub rejected direct retries for the managed workflow. Recheck the identical source tree after its installation quota recovered.