Embed Trivy, Syft, and TruffleHog into every commit with a single workflow file. Semgrep remains available when you provide local or customer-owned rules. 対象: DevOps engineers, platform engineers, and security engineers. 一般的な設定時間: 2 minutes.
Start herejourney
Use this if
Embed Trivy, Syft, and TruffleHog into every commit with a single workflow file. Semgrep remains available when you provide local or customer-owned rules.
Audience
DevOps engineers, platform engineers, and security engineers
Typical time
2 minutes
Start here
Step 3 of 6
Recommended
1
2
3
4
5
6
開始前に
Create an ingestion API key in Settings → API Keys with Ingestion scope only.
Confirm your CI runner can pull images from public.ecr.aws and reach your API URL.
For TruffleHog secret scanning: ensure fetch-depth: 0 is set in your checkout step so the local checkout includes full history.
Do this now
ステップ 1
Create an ingestion API key
Generate a scoped key for the pipeline scanner and store it in your CI secret manager.
Open Settings → API Keys → New Key.
Set scope to Ingestion only.
Name it after the repository or pipeline (e.g. pipeline-my-repo).
Add BLACKSHIELD_API_KEY as a masked CI secret and BLACKSHIELD_API_URL as a CI variable.
What success looks like
Add BLACKSHIELD_API_KEY as a masked CI secret and BLACKSHIELD_API_URL as a CI variable.
This configuration is designed for ease of use. To deploy scanner clients at scale, please plan your deployment architecture accordingly or contact us for enterprise best practices.
Get the source bundle
Download the exact source files referenced on this page, or run the one-command installer to write them locally before following the deployment steps.
GitHub Actions workflow
Writes `.github/workflows/security-scan.yml` with Trivy, Syft, and TruffleHog defaults plus an optional local-rule Semgrep job.