Automated Security Helper
Scan code, infrastructure, secrets, and dependencies.
ash --mode container
Scan example
Reports readyFiles 01
Scanners 02
Findings 03
Example data · Scanner coverage depends on configuration.
Built-in scanners
Install and scan
Install ASH
Use pipx, uvx, or pip with Python 3.10+.
Select a mode
Container, local, or pre-commit.
Review results
Open the HTML report or run ash inspect findings.
pipx install git+https://github.com/awslabs/automated-security-helper.git@v3.7.0uvx --from git+https://github.com/awslabs/automated-security-helper.git@v3.7.0 ash --helppip install git+https://github.com/awslabs/automated-security-helper.git@v3.7.0ash --mode containerRun enabled scanners in an isolated container. Requires an OCI-compatible runtime.
.ash/ash_output/Scanners
Bandit
Python security checks
PythonSemgrep
Pattern-based code checks
Multiple languagesOpengrep
Pattern-based code checks
Multiple languagesCheckov
Infrastructure policy checks
Terraform, Kubernetes, CloudFormationCDK-Nag
NagPack policy checks
CloudFormationCFN-Nag
Template security checks
CloudFormationdetect-secrets
Secret detection
Text filesGrype
Vulnerability matching
Packages and container imagesnpm audit
Dependency vulnerability checks
Node.jsSyft
Software inventory
SBOM generationShowing all 10 scanners.
Do I need an AWS account?
No. Core ASH scanning runs locally or in a container. An AWS account is needed only for optional integrations with services such as Security Hub or S3.
Which scan mode should I use?
Use container for a consistent environment with all scanner dependencies, local for your development machine, and precommit for a faster subset before commits. Compare execution modes.
Can I customize the rules and reports?
Set scanners, thresholds, ignore paths, and suppressions in .ash.yaml. Configuration reference.
Does ASH replace a security review?
No. Coverage depends on enabled scanners, language, file type, and configuration.