shc scan
shc scan
Section titled “shc scan”scan app and deployment images for vulnerabilities
Synopsis
Section titled “Synopsis”Scan images by sha256 digest using the local vulnerability database. Deployment scope follows inspect through -t, -e and -s, with prod as the default environment. Use shc scan -s app or shc scan -s db for deployments named app or db.
-o accepts
Exit codes: 0 complete with no threshold finding, 4 threshold finding, 1 failed or incomplete.
Every resolved image stays in the report, including unscanned images and their reasons.
Images are pulled from registries with Docker credentials, using linux/amd64 for index digests.
A missing database or one older than five days refreshes from its last source.
If refresh fails, import an archive with shc scan db update
shc scan [deployment] [flags]Options
Section titled “Options” --fail-on string exit 4 at or above critical, high, medium, low or negligible -h, --help help for scanOptions inherited from parent commands
Section titled “Options inherited from parent commands” --config stringArray extra YAML config file to layer on top of auto-discovered config; repeatable, later files win -d, --debug enable debug mode (default: $SHC_DEBUG) -e, --environment string environment name (default: "prod", or "default" on an estate with no licence and no trial; $SHC_ENVIRONMENT and shc ctx -e override it, and the "master" tenant is always "default") --exclude string comma-separated dotted paths to drop --fields string comma-separated columns/keys to show (and their order) --filter string comma-separated dotted paths to keep (drops everything else) -o, --output string output format: tty|text|json|yaml (default: $SHC_OUTPUT) -s, --stack string stack name (default: $SHC_STACK) -t, --tenant string tenant name (default: $SHC_TENANT) -v, --verbose verbose output (default: $SHC_VERBOSE)SEE ALSO
Section titled “SEE ALSO”- shc - Selfhosted Cloud CLI
- shc scan app - scan every runtime image of a local or catalog app
- shc scan db - manage the vulnerability database