This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
kb04 [2025/09/27 05:27] ziggi removed |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ==== Trivy ==== | ||
| - | |||
| - | Trivy (pronunciation) is a comprehensive and versatile security scanner. Trivy has scanners that look for security issues, and targets where it can find those issues. | ||
| - | |||
| - | Targets (what Trivy can scan): | ||
| - | |||
| - | * | ||
| - | * | ||
| - | * Git Repository (remote) | ||
| - | * | ||
| - | * | ||
| - | * AWS | ||
| - | |||
| - | Scanners (what Trivy can find there): | ||
| - | |||
| - | * OS packages and software dependencies in use (SBOM) | ||
| - | * Known vulnerabilities (CVEs) | ||
| - | * IaC issues and misconfigurations | ||
| - | * | ||
| - | * | ||
| - | |||
| - | |||
| - | ====Trivy Operator==== | ||
| - | |||
| - | In-cluster Security Scans | ||
| - | |||
| - | The Trivy Operator automatically generates and updates security reports. These reports are generated in response to new workload and other changes on a Kubernetes cluster, generating the following reports: | ||
| - | |||
| - | * Vulnerability Scans: Automated vulnerability scanning for Kubernetes workloads. | ||
| - | * ConfigAudit Scans: Automated configuration audits for Kubernetes resources with predefined rules or custom Open Policy Agent (OPA) policies. | ||
| - | * Exposed Secret Scans: Automated secret scans which find and detail the location of exposed Secrets within your cluster. | ||
| - | * RBAC scans: Role Based Access Control scans provide detailed information on the access rights of the different resources installed. | ||
| - | * K8s core component infra assessment scan Kubernetes infra core components (etcd, | ||
| - | * k8s outdated api validation - a configaudit check will validate if the resource api has been deprecated and planned for removal | ||
| - | * Compliance reports | ||
| - | * NSA, CISA Kubernetes Hardening Guidance v1.1 cybersecurity technical report is produced. | ||
| - | * CIS Kubernetes Benchmark v1.23 cybersecurity technical report is produced. | ||
| - | * Kubernetes pss-baseline, | ||
| - | * Kubernetes pss-restricted, | ||
| - | * SBOM (Software Bill of Materials generations) for Kubernetes workloads | ||
| - | |||
| - | ==== Kyverno ==== | ||
| - | |||
| - | Kyverno (Greek for “govern”) is a policy engine designed specifically for Kubernetes. Some of its many features include: | ||
| - | |||
| - | * | ||
| - | * | ||
| - | * | ||
| - | * | ||
| - | * match resources using label selectors and wildcards | ||
| - | * | ||
| - | * | ||
| - | * block non-conformant resources using admission controls, or report policy violations | ||
| - | * | ||
| - | * | ||
| - | * test policies and validate resources using the Kyverno CLI, in your CI/CD pipeline, before applying to your cluster | ||
| - | * | ||
| - | |||
| - | Kyverno allows cluster administrators to manage environment specific configurations independently of workload configurations and enforce configuration best practices for their clusters. Kyverno can be used to scan existing workloads for best practices, or can be used to enforce best practices by blocking or mutating API requests. | ||
| - | |||