2026-03-24 16:08:09 -07:00
---
title: Prowler
2026-06-08 09:24:32 -07:00
modified: 2026-06-08
2026-03-24 16:08:09 -07:00
last-reviewed: 2026-03-24
tags:
- service
- security
---
# Prowler
CIS Kubernetes Benchmark scanner for compliance posture reporting.
## Quick Reference
| Property | Value |
|----------|-------|
| **Namespace ** | `prowler` |
| **Image ** | `registry.ops.eblu.me/blumeops/prowler` (see `argocd/manifests/prowler/kustomization.yaml` for current tag) |
2026-06-08 09:24:32 -07:00
| **Schedule ** | K8s CIS: Sunday 3am |
| **Reports ** | `sifaka:/volume1/reports/prowler/` (NFS) |
2026-03-24 16:08:09 -07:00
| **Manifests ** | `argocd/manifests/prowler/` |
## What it does
2026-06-08 09:24:32 -07:00
Runs Prowler 5 as a single CronJob:
2026-03-24 16:43:08 -07:00
- **K8s CIS scan** (Sunday) — CIS Kubernetes Benchmark v1.11 checks across pod security, RBAC, apiserver, etcd, kubelet, controller-manager, and scheduler
Reports are written in HTML, CSV, and JSON-OCSF to the NFS share on sifaka.
2026-03-24 16:08:09 -07:00
2026-06-08 09:24:32 -07:00
The **image ** and **IaC ** scans (formerly Saturday CronJobs) were retired in 2026-06 — they generated tens of thousands of un-actioned findings weekly. See [[deploy-prowler#Why only the K8s CIS scan]].
2026-03-24 16:08:09 -07:00
## See also
- [[security]] — security & compliance posture overview
- [[deploy-prowler]] — deployment how-to, ad-hoc scan instructions, check relevance notes
- [[read-compliance-reports]] — how to access and interpret reports