mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-08-31 21:50:50 +03:00
Mahipal
6972fe933e
All 33 container-security skills now carry what it does, an explicit "Use when" trigger, keywords, and a negative trigger naming the nearest neighbour. Six collision clusters resolved by differentiating scope rather than merging, so no skill is removed: - kube-bench: running the tool vs interpreting findings into an audit - Calico: portable upstream NetworkPolicy vs Calico-as-CNI vs Calico-only CRDs (GlobalNetworkPolicy, HostEndpoint, DNS egress) - Falco: deploying and operating it vs authoring escape rules - container escape: tool-agnostic runtime signals vs Falco rule syntax vs static posture audit vs offensive breakout - Trivy: all-target platform and operator vs single-image scan - Docker: images and Dockerfiles vs daemon.json vs the CIS audit script Also replaces the templated "When to Use" boilerplate in these files, including bullets that only restated the skill's own name. Worst pair (Pod Security Standards vs Pod Security Admission) drops from 0.77 cosine to below the 0.45 threshold. Repo-wide: colliding pairs 60 -> 56, skills involved 105 -> 94.
81 lines
3.2 KiB
Markdown
81 lines
3.2 KiB
Markdown
---
|
|
name: performing-container-security-scanning-with-trivy
|
|
description: >-
|
|
Runs Trivy across every target type it supports - container images, filesystems, Git
|
|
repositories, and Kubernetes clusters - for OS and dependency vulnerabilities, IaC
|
|
misconfiguration, exposed secrets, and licences, generating CycloneDX or SPDX SBOMs. Use
|
|
when integrating Trivy into CI/CD, deploying the Trivy Kubernetes operator, scanning
|
|
non-image targets, or triaging results at scale. Keywords: Trivy, trivy k8s, operator, SBOM,
|
|
CycloneDX, SPDX, misconfig, secret scanning. Do not use for a single Docker image scan - use
|
|
scanning-docker-images-with-trivy.
|
|
domain: cybersecurity
|
|
subdomain: container-security
|
|
tags:
|
|
- trivy
|
|
- container-security
|
|
- vulnerability-scanning
|
|
- sbom
|
|
- docker
|
|
- kubernetes
|
|
- devsecops
|
|
- supply-chain
|
|
version: '1.0'
|
|
author: mahipal
|
|
license: Apache-2.0
|
|
nist_csf:
|
|
- PR.PS-01
|
|
- PR.IR-01
|
|
- ID.AM-08
|
|
- DE.CM-01
|
|
mitre_attack:
|
|
- T1610
|
|
- T1611
|
|
- T1609
|
|
- T1525
|
|
- T1195
|
|
---
|
|
|
|
# Performing Container Security Scanning with Trivy
|
|
|
|
## Overview
|
|
|
|
Trivy is an open-source security scanner by Aqua Security that detects vulnerabilities in OS packages and language-specific dependencies, infrastructure-as-code misconfigurations, exposed secrets, and software license issues across container images, filesystems, Git repositories, and Kubernetes clusters. Trivy generates Software Bill of Materials (SBOM) in CycloneDX and SPDX formats for supply chain transparency. This skill covers comprehensive container image scanning, CI/CD pipeline integration, Kubernetes operator deployment, and scan result triage for security operations.
|
|
|
|
|
|
## When to Use
|
|
|
|
- When conducting security assessments that involve performing container security scanning with trivy
|
|
- When following incident response procedures for related security events
|
|
- When performing scheduled security testing or auditing activities
|
|
- When validating security controls through hands-on testing
|
|
|
|
## Prerequisites
|
|
|
|
- Trivy v0.50+ installed (binary, Docker, or Homebrew)
|
|
- Docker daemon access for local image scanning
|
|
- Container registry credentials for remote image scanning
|
|
- CI/CD platform (GitHub Actions, GitLab CI, Jenkins) for pipeline integration
|
|
- Kubernetes cluster for Trivy Operator deployment (optional)
|
|
|
|
## Steps
|
|
|
|
### Step 1: Scan Container Images
|
|
|
|
Run vulnerability and secret scanning against container images from local builds or remote registries. Configure severity thresholds and ignore unfixed vulnerabilities.
|
|
|
|
### Step 2: Generate SBOM
|
|
|
|
Produce CycloneDX or SPDX SBOM documents from scanned images for supply chain compliance and vulnerability tracking across the software lifecycle.
|
|
|
|
### Step 3: Scan IaC and Kubernetes Manifests
|
|
|
|
Detect misconfigurations in Dockerfiles, Kubernetes YAML, Terraform, and Helm charts using built-in policy checks aligned with CIS benchmarks.
|
|
|
|
### Step 4: Integrate into CI/CD
|
|
|
|
Add Trivy scanning as a pipeline gate that blocks builds with critical/high vulnerabilities, generates SARIF reports for GitHub Advanced Security, and produces JUnit XML for test dashboards.
|
|
|
|
## Expected Output
|
|
|
|
JSON/table report listing CVEs with severity, CVSS scores, fixed versions, affected packages, misconfiguration findings, and exposed secrets with file locations.
|