Difference between revisions of "Keeping Infrastructure as Code Secure (KICS)"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
* https://kics.io/ | * https://kics.io/ | ||
* <code>[[brew install kics]]</code> | * <code>[[brew install kics]]</code> | ||
| − | + | * <code>[[kics --help]]</code> | |
| − | + | * <code>[[kics scan]]</code> | |
| − | |||
Scan a directory: | Scan a directory: | ||
Revision as of 18:58, 27 February 2024
Scan a directory:
docker run -t -v {path_to_host_folder_to_scan}:/path checkmarx/kics:latest scan -p /path -o "/path/"
Scan a single file:
docker run -t -v {path_to_host_folder}:/path checkmarx/kics:latest scan -p /path/{filename}.{extension} -o "/path/"
uses: checkmarx/kics-github-action
- Integrated with GitLab 14.5 (2022)
- GitHub
- Checkmarx
- KICS execution example
- Hardeneks
See also
kics [ scan | analyze | --help ]- Keeping Infrastructure as Code Secure (KICS), execution example
- IaC: Terraform, Chef, cdist, capistrano, Harrow, puppet, Ansible, CFEngine, Cloud Deployment Manager, pulumi, juju, SaltStack, Azure Resource Manager (ARM), Google Deployment Manager, AWS CloudFormation, Pulumi, Heat, Spacelift, Oracle Cloud Resource Manager, KICS, Troposphere, CaC, IaC scanning
Advertising:
