The change is a move away from treating a runtime detection engine as the sole solution toward building a shared security baseline that captures expected workload behavior and enforcement decisions. Engineers care because without that shared definition every alert becomes a question of intent, leading to wasted time, stalled work, and false confidence in the tool.
From Tool‑First to Baseline‑First
Teams often rush to install a DaemonSet such as Falco, expose a dashboard, and celebrate visible progress. The missing piece is a documented agreement on what constitutes normal activity, which workloads may run, and which actions should be blocked versus reported. When that agreement lives in another team, the original team proceeds without the answers it needs, creating a new kind of silo: autonomy that masks self‑sufficiency.
Components of a Practical Baseline
A baseline is not a policy document; it is a concise, testable set of answers that map directly to cluster configuration. Typical questions include:
- Location in the cluster: where the baseline artifacts are stored.
- Ownership: which team must approve each element.
- Workload constraints: allowed security contexts, Pod Security Standards, and image provenance requirements.
- Enforcement mode: whether a rule should block, audit, or merely report (e.g., Kyverno enforce vs. audit, Gatekeeper deny vs. dry‑run).
- Exception process: how and when an exception can be granted and its expiration.
- Logging and retention: audit policy levels, retention periods, and responsible readers.
No single team owns all rows; the baseline must be co‑owned across platform, security, and application groups.
Architectural and Operational Implications
Treating the baseline as code makes it reachable. Store the baseline alongside admission policies, Falco rules, and audit policies in a version‑controlled repository. This approach gives the following benefits:
- Visibility: changes are reviewed through existing pull‑request workflows.
- Traceability: ownership and approval history are captured in Git metadata.
- Automation: CI pipelines can validate that new workloads conform to the baseline before they are merged.
- Exception handling: a defined
PolicyExceptionresource can be versioned and have an expiry date baked into the code.
Operationally, teams must allocate time for early cross‑team conversations to agree on baseline items. Security teams should design approval processes that avoid turning every question into a long‑running review queue; otherwise engineering teams will work around the controls, defeating the purpose.
Related CloudNinjas coverage: hands-on guides.
What This Means For Practitioners
Actionable steps:
- Initiate a baseline definition workshop that includes platform, security, and application owners.
- Create a dedicated Git repository for baseline artifacts and link it to your CI/CD pipelines.
- Map each baseline question to a concrete configuration object (e.g.,
PodSecurityPolicy,Kyvernorule, Falco macro). - Establish a lightweight approval process for exceptions that records owner, justification, and expiration.
- Instrument alert handling to reference the baseline so that operators can quickly decide if an event is expected.
By embedding the baseline in the same workflow used to ship code, teams keep the conversation alive, reduce noisy alerts, and prevent the hidden silo that turns autonomy into self‑sufficiency.

