Transactional configuration management for Linux.
Kensa assesses Linux configurations and applies changes through defined mechanisms. Capturable mechanisms support rollback attempts from recorded pre-state.
The transaction model
See a change before it runs and read how it ended.
Where the mechanism supports it, Kensa saves the state a change will touch before making the change. Then it applies the change and validates the result. If a step or validation fails, Kensa reverses the completed steps from that record. Kensa records how each finished transaction ended.
To preview a rule's default change, run kensa plan. It shows the current state, the apply steps, and the rollback plan, and it makes no changes. If a run is cut off, kensa recover reverses its unfinished transactions from the saved record. It reports any it can't restore, changes nothing for them, and keeps them for you to review and retry.
How it works
Four phases, one transaction.
If a phase fails, Kensa restores the captured pre-state and records it. Within the captured boundary, the run ends at the target state or the pre-change state, not stuck halfway.
Capture
Record the precise pre-state of whatever is about to be touched. Typed capture handlers for packages, services, sshd, kernel params, SELinux, PAM, crypto policies, and more.
Apply
Make the change with the corresponding remediation handler. Handlers are declarative and idempotent. Run twice, same result.
Validate
Run the defined checks for the intended effect. Inspect service, config, and dependent-state results where those checks exist.
Commit / Rollback
Passed: record the change. Validation failed: attempt rollback for supported steps. Inspect the outcome for incomplete restoration.
What makes Kensa different
Six things scanners don't do
Scan + Remediate + Rollback
Supported mechanisms capture pre-state and attempt rollback after validation failure. Partial apply or failed restoration requires operator review.
One rule, all frameworks
A single rule maps to CIS, STIG, and NIST 800-53 at once. No duplicate content to maintain.
Structured check evidence
Structured, machine-readable evidence for each check: the command Kensa ran, its output and its exit status. Scan evidence is not signed. Anyone with access to the host can rerun the command to check the result.
YAML rules, not XML
Human-readable, Git-friendly, reviewable by the engineers who manage the systems. Not SCAP.
Adapts to each host
Runtime probes detect capabilities: sshd drop-ins, authselect, crypto policies, FIPS, SELinux. One rule, RHEL 8/9.
Daemonless
No persistent install. An ephemeral helper is staged per run and removed (opt out with KENSA_NO_AGENT=1). Pure SSH, no open ports. Runs across your fleet in parallel.
Quick demo
Three commands to assess and remediate.
Scan to see posture. Dry-run to preview changes. Remediate, then inspect the result. Supported steps attempt rollback after validation failure. Kensa works over SSH without a persistent agent.
# 1 · Scan a host$ kensa check --sudo -H 192.168.1.10 -u admin -r rules/# 2 · Dry-run remediation (see what would change)$ kensa remediate --sudo -H 192.168.1.10 -u admin -r rules/ --dry-run# 3 · Remediate (supported steps attempt rollback on validation failure)$ kensa remediate --sudo -H 192.168.1.10 -u admin -r rules/
Framework coverage
Full coverage on the platforms you run
Coverage is reported per platform, since what matters for an assessment is the OS you actually run.
The deepest reason Kensa matters
As AI agents increasingly modify production (editing configs in CI, applying patches, responding to alerts), every one faces the same problem: how do I know the change didn't break something, and how do I undo it if it did?
An agent needs a defined plan, validation, and a recovery path before changing a host. Kensa records supported starting state and change outcomes. Supported steps attempt rollback after validation failure; partial apply and failed restoration still need operator review. Inspect the log and host before deciding what to do next.
Need a dashboard, scheduling, and history?
OpenWatch turns Kensa from a CLI into continuous infrastructure: the eye, the heartbeat, and the control plane. It remembers every transaction Kensa has ever run, across your whole fleet.
FAQ
Kensa FAQ
What is Kensa?
Kensa scans and remediates Linux configuration and compliance state. Supported mechanisms capture pre-state, apply a change, validate the result, and attempt rollback when validation fails. Review each outcome for partial apply or failed restoration.
How does rollback work?
For capturable mechanisms, Kensa records pre-state and attempts restoration when validation fails. Failed apply steps can leave unresolved changes, and some mechanisms are non-transactional. Review the plan and terminal outcome; rollback is not available for every mechanism.
Which compliance frameworks does Kensa cover?
A single rule maps to CIS, STIG, and NIST 800-53 at once, so one rule set covers multiple frameworks without duplicate content to maintain.
Does Kensa need an agent on the target hosts?
No. Kensa is daemonless and runs over plain SSH. There is no persistent agent to install or maintain on the hosts it manages.