scanning-container-security

name	scanning-container-security
description	Execute use when you need to work with security and compliance. This skill provides security scanning and vulnerability detection with comprehensive guidance and automation. Trigger with phrases like "scan for vulnerabilities", "implement security controls", or "audit security".
allowed-tools	Read, Write, Edit, Grep, Glob, Bash(docker:*), Bash(kubectl:*)
version	1.27.0
author	Jeremy Longshore <[e-mail]>
license	MIT
tags	["devops","security","compliance","audit"]
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw

Scanning Container Security

Overview

Scan container images and Dockerfiles for vulnerabilities, misconfigurations, and compliance violations using Trivy, Grype, Snyk Container, and Hadolint. Analyze base images, OS packages, application dependencies, and runtime configurations to produce actionable security reports with remediation guidance.

Prerequisites

• Container scanning tool installed: trivy, grype, snyk, or docker scout
• Dockerfile linter: hadolint for Dockerfile best practice validation
• Docker daemon running for local image scanning
• Access to the container images to scan (local, registry, or tar archive)
• jq for parsing JSON scan results

Instructions

1. Identify target images for scanning: production images, base images, and CI-built images
2. Lint Dockerfiles with hadolint Dockerfile to catch misconfigurations before build (privileged instructions, pinned versions, shell best practices)
3. Scan built images for OS-level vulnerabilities: trivy image <image:tag> or grype <image:tag>
4. Scan for application dependency vulnerabilities: check language-specific packages (npm, pip, Maven, Go modules) embedded in the image
5. Check for secrets accidentally baked into image layers: trivy image --scanners secret <image:tag>
6. Evaluate image against CIS Docker Benchmark: verify non-root user, read-only filesystem capability, health checks defined
7. Generate a security report with severity classification (Critical, High, Medium, Low) and CVE identifiers
8. Produce remediation steps: upgrade base image, pin package versions, replace vulnerable dependencies
9. Integrate scanning into CI/CD pipeline: fail builds on Critical/High vulnerabilities, generate SARIF output for GitHub Security tab

Output

• Vulnerability scan report in JSON, table, or SARIF format
• Hadolint report with Dockerfile improvement recommendations
• Remediation Dockerfile patches (updated base image, pinned package versions)
• CI/CD pipeline step configuration for automated image scanning
• Security policy document defining acceptable risk thresholds

Error Handling

Error	Cause	Solution