Compliance

I wrote this for the CIQ blog: an honest look at when community Rocky Linux support covers you and when a production environment needs the vendor support RLC Pro adds.

I wrote this for the CIQ blog: how to choose between RLC Pro AI and RLC Pro Hardened depending on whether you are running AI infrastructure or working under strict compliance.

I wrote this for TuxCare to explain, step by step, how KernelCare applies kernel patches to running memory so teams stay secure without rebooting.

I wrote this for TuxCare as the signed-patch switchover arrived, urging teams still on older KernelCare agents to upgrade to v3 before coverage gaps appear.

I wrote this for TuxCare on building a FIPS and FedRAMP-ready environment on community Linux, and how TES fills the gaps the base OS can’t.

I wrote this for TuxCare to break down the Essential, Enhanced, and Custom support tiers so teams can match coverage to their real risk profile.

I wrote this for TuxCare: a fact-based comparison of TES against Red Hat, SUSE, Canonical, and Oracle across pricing, rebootless patching, and compliance.

I wrote this for TuxCare to announce KernelCare Agent v3, which introduces signed patch validation while keeping live patching disruption-free.

I wrote this for TuxCare on the relaunch of Enterprise Support, which now covers AlmaLinux and Rocky Linux together with 24x7 support and compliance-ready patching.

I wrote this for TuxCare to explain what patch-aware scanning means, why traditional scanners get Linux wrong, and how it makes audits far less painful.

I wrote this for TuxCare to show how ePortal can proxy Radar scans, so locked-down fleets route data through one internal server instead of each host phoning home.

Joel Krooswyk and I compare public sector and government tech work, covering compliance, modernization, AI, and career shifts.