Skip to Content
Patch management

Patched on a schedule
you approved.

Patching is the maintenance everyone agrees is necessary and nobody has time for, so it slips until an audit or an exploit forces it. We run it as a routine: a known schedule, a tested order, a window you signed off on, and a record of what changed on which host.

Monthly
Baseline cadence for routine updates
Critical
Out-of-band handling for active exploits
Staged
Test tier before anything touches production
Logged
Per-host record of every change applied

Routine patching.
Plus a path for urgent ones.

Most updates can wait for the next window. A few cannot. Treating both the same way is how estates end up either permanently behind or permanently disrupted.


Step 01
Know what you are running

Patching cannot be planned against an unknown inventory. We establish what exists, which distributions and versions are in play, and which hosts carry workloads that constrain the window.

What this covers
  • Host inventory with distribution and version state
  • Package and kernel drift across the estate
  • End-of-life releases flagged for upgrade
  • Dependency and reboot-order mapping
  • Maintenance windows agreed per workload
Infrastructure audits

Step 02
Scheduled, staged rollout

Updates land on a test tier first, then production in an order that respects clusters and dependencies. Reboots are coordinated so a patch never becomes an unplanned outage.

What this covers
  • Test-tier validation ahead of production
  • Cluster-aware ordering and rolling reboots
  • Kernel and live-patch handling where supported
  • Documented rollback position before each window
  • Change records written as the work happens
Linux managed services

Step 03
Urgent CVE response

When something is being actively exploited, the schedule stops mattering. We assess whether it reaches your estate, decide with you, and move out of band when it does.

What this covers
  • Advisory triage against your actual inventory
  • Exposure assessment before anyone panics
  • Out-of-band patching with your approval
  • Mitigations when a patch is not yet available
  • Written follow-up on what was changed and why
Security hardening

What patching solves.
What it doesn't.

Patch management addresses
  • Known vulnerabilities with a vendor fix available
  • Package and kernel drift across the estate
  • End-of-life releases that no longer receive fixes
  • Audit findings about unpatched systems
  • Reboot coordination for clustered services
  • A change record showing what moved and when
Patching is not a substitute for
  • Hardening, since a patched server can still be wide open
  • Backups, because an update can go wrong like anything else
  • High availability, if you cannot afford a reboot window
  • Application-level fixes in code you own

Patching closes known holes on a schedule. Hardening changes the baseline itself, and high availability is what lets you reboot in the middle of the day.

The Crafty Penguins Way

How We Become Part of
Your Team

We don't just hand over a monitoring dashboard and disappear. Here's how we build a lasting partnership.

Step 01

Discovery Call

We learn your environment, pain points, and goals. No scripts, no sales pressure, just an honest conversation about what you need.

Step 02

Onboarding

A structured, practical onboarding process. We set up the services you chose, deploy monitoring where they include it, and tune alert thresholds with you through the first month.

Step 03

Your Services Begin

Whichever services you chose go live, delivered by engineers who already know your systems. From day one, the work keeps your infrastructure healthy and improving.

Step 04

Long-Term Partnership

We become an extension of your team. Strategic input, roadmap planning, and continuous improvement, not just keeping the lights on.

Get Started

To See How Crafty Penguins Can Help,
Please Reach Out Below

Whether you are stabilizing a MariaDB cluster, planning an upgrade, or tightening backups and failover, our engineers can meet you where you are, practical guidance, hands-on implementation, and long-term support when you need it.

Contact Us