kics
Run Checkmarx KICS for Infrastructure as Code security scanning. Use when analyzing Terraform, CloudFormation, Kubernetes, Ansible, Dockerfile, or other IaC for misconfigurations and security issues.
What this skill does
# Checkmarx KICS (Keeping Infrastructure as Code Secure)
## When to Use KICS
**Ideal scenarios:**
- Infrastructure as Code (IaC) security scanning
- Cloud configuration analysis (AWS, Azure, GCP, Oracle)
- Kubernetes manifest security review
- Dockerfile security hardening
- Terraform/OpenTofu security assessment
- Ansible playbook security validation
- CI/CD pipeline IaC security gates
- Compliance checking (CIS, PCI-DSS, NIST, SOC2)
**Complements other tools:**
- Use alongside application security scanners (Semgrep, CodeQL)
- Combine with SARIF Issue Reporter for detailed findings
- Use with cloud posture management tools
## When NOT to Use
Do NOT use this skill for:
- Application source code vulnerability scanning (use Semgrep or CodeQL)
- Secrets detection (use Gitleaks)
- Dependency vulnerability scanning (use OSV-Scanner or Depscan)
- Runtime cloud posture assessment (use CSPM tools)
- Binary or compiled code analysis
## Installation
```bash
# Binary download (Linux)
wget https://github.com/Checkmarx/kics/releases/latest/download/kics_linux_amd64.tar.gz
tar -xzf kics_linux_amd64.tar.gz
sudo mv kics /usr/local/bin/
# Binary download (macOS)
wget https://github.com/Checkmarx/kics/releases/latest/download/kics_darwin_amd64.tar.gz
tar -xzf kics_darwin_amd64.tar.gz
sudo mv kics /usr/local/bin/
# Homebrew
brew install kics
# Docker
docker pull checkmarx/kics:latest
# Verify
kics version
```
## Core Workflow
### 1. Quick Scan
```bash
# Scan current directory
kics scan -p .
# Scan specific path
kics scan -p /path/to/iac
# Scan with minimal output
kics scan -p . --silent
# No color output (for CI)
kics scan -p . --no-color
```
### 2. SARIF Output
```bash
# Generate SARIF report
kics scan -p /path/to/iac \
--report-formats sarif \
--output-path results.sarif
# Multiple formats (JSON + SARIF)
kics scan -p /path/to/iac \
--report-formats json,sarif \
--output-path .
# Named output
kics scan -p /path/to/iac \
--report-formats sarif \
--output-name kics-results
# All formats
kics scan -p /path/to/iac \
--report-formats all \
--output-path ./reports
```
### 3. Platform-Specific Scans
```bash
# AWS CloudFormation
kics scan -p ./cloudformation --type CloudFormation
# Terraform
kics scan -p ./terraform --type Terraform
# Kubernetes manifests
kics scan -p ./k8s --type Kubernetes
# Dockerfile
kics scan -p ./docker --type Dockerfile
# Ansible
kics scan -p ./ansible --type Ansible
# Azure Resource Manager
kics scan -p ./arm --type AzureResourceManager
# Google Deployment Manager
kics scan -p ./gdm --type GoogleDeploymentManager
# Helm charts
kics scan -p ./charts --type Helm
```
### 4. Severity Filtering
```bash
# Only high and critical
kics scan -p . --minimal-ui --fail-on high,critical
# Exclude info findings
kics scan -p . --exclude-severities info
# Specific severities in SARIF
kics scan -p . \
--fail-on high,critical \
--report-formats sarif \
--output-path results.sarif
```
## Configuration
### Config File
Create `.kics.yml` or `kics.config`:
```yaml
# Paths to scan
path: ./infrastructure
# Query selection
exclude-queries:
- 487f4be7-3fd9-4506-a07a-96c39d0b30ad # Specific query ID
# Severity settings
fail-on:
- high
- critical
# Output settings
output-path: ./kics-results
report-formats:
- sarif
- json
- html
# Exclude paths
exclude-paths:
- "./tests/**"
- "./examples/**"
- "**/.terraform/**"
# Exclude results by similarity ID
exclude-results:
- abc123def456
# Platform filters
type:
- Terraform
- Kubernetes
- Dockerfile
# CI mode
ci: true
no-color: true
minimal-ui: true
```
Use config:
```bash
kics scan --config .kics.yml
```
### Inline Suppressions
```hcl
# Terraform - suppress specific finding
resource "aws_s3_bucket" "example" {
# kics-scan ignore-line
bucket = "my-bucket"
acl = "public-read" # Suppressed above
}
# Suppress entire block
# kics-scan ignore-block
resource "aws_security_group" "example" {
ingress {
from_port = 0
to_port = 0
protocol = "-1"
cidr_blocks = ["0.0.0.0/0"]
}
}
```
```yaml
# Kubernetes - suppress finding
apiVersion: v1
kind: Pod
metadata:
name: example
spec:
# kics-scan ignore-line
hostNetwork: true # Suppressed
containers:
- name: app
image: nginx:latest # kics-scan ignore-line
```
## CI/CD Integration (GitHub Actions)
```yaml
name: KICS IaC Scan
on:
push:
branches: [main]
paths:
- '**.tf'
- '**.yaml'
- '**.yml'
- 'Dockerfile*'
pull_request:
paths:
- '**.tf'
- '**.yaml'
- '**.yml'
- 'Dockerfile*'
jobs:
kics:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Run KICS
uses: checkmarx/[email protected]
with:
path: .
output_path: kics-results
output_formats: 'sarif,json,html'
fail_on: high,critical
enable_comments: true # PR comments
exclude_paths: 'tests/**,examples/**'
- name: Upload SARIF
if: always()
uses: github/codeql-action/upload-sarif@v3
with:
sarif_file: kics-results/results.sarif
category: kics
- name: Upload Results
if: always()
uses: actions/upload-artifact@v4
with:
name: kics-results
path: kics-results/
```
## Common Use Cases
### 1. Terraform Security Audit
```bash
# Comprehensive Terraform scan
kics scan -p ./terraform \
--type Terraform \
--report-formats sarif,html \
--output-path ./security-audit \
--fail-on high,critical
# Review HTML report
open ./security-audit/results.html
# Process SARIF with other tools
sarif summary ./security-audit/results.sarif
```
### 2. Kubernetes Hardening
```bash
# Scan all K8s manifests
kics scan -p ./k8s \
--type Kubernetes \
--report-formats sarif \
--output-name k8s-security
# Focus on critical issues
kics scan -p ./k8s \
--type Kubernetes \
--fail-on high,critical \
--exclude-severities low,medium,info
```
### 3. Multi-Cloud Infrastructure
```bash
# Scan mixed IaC
kics scan -p ./infrastructure \
--type Terraform,CloudFormation,AzureResourceManager \
--report-formats sarif,json \
--output-path ./reports
```
### 4. Dockerfile Security
```bash
# Scan all Dockerfiles
kics scan -p . \
--type Dockerfile \
--report-formats sarif \
--output-name dockerfile-scan
# Include docker-compose
kics scan -p . \
--type Dockerfile,DockerCompose \
--report-formats sarif
```
## Understanding Output
### SARIF Structure
KICS SARIF v2.1.0 includes:
- **Rules**: Each query/check (1500+ built-in queries)
- **Results**: Specific IaC misconfigurations found
- **Properties**:
- Severity: HIGH, MEDIUM, LOW, INFO
- Category: Security, Best Practices, etc.
- Platform: Terraform, K8s, Dockerfile, etc.
- CWE mapping
- Remediation guidance
### Result Categories
| Category | Examples |
|----------|----------|
| **Access Control** | Overly permissive IAM, public resources |
| **Encryption** | Unencrypted storage, weak TLS |
| **Networking** | Open security groups, exposed ports |
| **Secret Management** | Hardcoded credentials, exposed secrets |
| **Resource Configuration** | Missing logging, backup disabled |
| **Best Practices** | Missing tags, resource limits |
| **Insecure Defaults** | Default passwords, debug mode |
## Advanced Features
### Custom Queries
Create custom query in `custom-queries/`:
```rego
# custom-queries/require_tags.rego
package Cx
CxPolicy[result] {
resource := input.document[i].resource.aws_instance[name]
not resource.tags
result := {
"documentId": input.document[i].id,
"searchKey": sprintf("aws_instance[%s]", [name]),
"issueType": "MissingAttribute",
"keyExpectedValue": "Tags should be defined",
"keyActualValue": "Tags are not defined"
}
}
```
Use custom queries:
```bash
kics scan -p ./terraform \
--queries-path ./custom-queries \
--reportRelated in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.