ujans
Blog
Cyber security

What is patch management? How to set up an update process in a business

Most attacks use flaws that have been known for years and for which patches exist. Applying updates regularly and under control is one of the cheapest and most effective security measures.

ujans team··4 min read

Security flaws are discovered in software and devices all the time, and vendors publish updates (patches) to close them. A system without the patch is like a door whose flaw is publicly known: attackers scan for these flaws with automated tools. Patch management is the process of applying updates in a planned, tested and traceable way.

Why is it so critical?

  • Ransomware and many intrusions start from flaws that had a patch but were not applied; see the ransomware guide.
  • After a flaw is announced, exploit tools spread quickly; the shorter your rollout time, the lower the risk.
  • Updates also bring bug fixes and performance improvements.
  • Regulation and security standards expect regular updating as a measure; see the KVKK compliance checklist.

What does it cover?

  1. Operating systems: Windows, macOS, Linux, mobile devices.
  2. Applications: Browsers, office applications, PDF readers, remote access tools.
  3. Server software and databases.
  4. Network devices: Firewall, router, switch, Wi-Fi access points (firmware); see choosing a firewall and the office network guide.
  5. Till and special devices: POS, camera systems, printers, handheld terminals; see POS security.
  6. Websites and plugins: CMS, libraries, dependencies; see website maintenance and web application security.
  7. Cloud and SaaS settings: The provider patches its own side, but configuration and user side are yours.

The process step by step

1. Inventory

Without knowing what to patch there is no patch management. Devices, operating system versions, installed software, servers, network devices, owners. Unknown ("shadow") devices and software are among the biggest sources of risk.

2. Information gathering and monitoring

Vendor security bulletins, security news sources and alerts from management tools. Determine which patches concern your systems.

3. Risk assessment and prioritisation

For each patch: severity of the flaw, is it known to be exploited, is the system internet-facing, how critical is the system? Prioritisation example:

  • Urgent: Critical flaws actively exploited and on internet-facing systems; within days.
  • High: Critical flaws on internal systems; within a few weeks.
  • Normal: The regular monthly cycle.
  • Low: In a planned maintenance window.

4. Testing

Especially on business-critical systems, try the patch first on a small test group or test environment: compatibility problems, performance, whether business applications work. Do not skip testing on systems such as till and ERP; see cloud ERP.

5. Planned rollout

  • Maintenance window: Outside business hours, with downtime notice where possible.
  • Staged rollout (rings): Pilot first, then the broad group, then critical systems.
  • Rollback plan: Undo the update or recover from backup if a problem arises; see backup strategy.
  • Backup first: Take a system backup before major updates.

6. Verification and reporting

Was the patch really applied? Which devices failed or were skipped? Track indicators such as compliance percentage, pending critical patches and average time to apply; see KPIs and management dashboards.

7. Exception management

Systems that cannot be updated (old till software, an operating system past support, special hardware): isolate from the network, restrict access, add protection, plan renewal. Document these exceptions and tie them to time-limited approval; for a lasting fix see modernising legacy systems.

Automation and tools

  • Operating system: Enabling automatic updates, central update management.
  • Endpoint management: Central reporting with device management and endpoint protection solutions; see endpoint security (EDR).
  • Dependency scanning tools: In software projects.
  • Vulnerability scanning: Regularly scan for missing patches and misconfigurations; also verify with penetration testing; see penetration testing.

In small businesses automatic updating is often a sufficient first step; critical systems need a test and approval cycle. If there is no IT team the process can run under managed IT support.

Sector notes

Together with the other security layers

Patch management is not enough alone but is the foundation of other measures: it works with MFA, least privilege, network segmentation, backup and monitoring; see cyber security basics, zero trust and the incident response plan.

Common mistakes

  • Keeping no inventory and leaving unknown devices,
  • Postponing updates with "it works, do not touch it",
  • Patching all tills at once without testing,
  • Forgetting software on network devices and devices like cameras and printers,
  • Leaving systems past support exposed to the internet,
  • Not verifying that the patch was applied,
  • Doing a major update without a backup,
  • Forgetting exceptions without documenting them.

A starter plan

  1. Build a device and software inventory.
  2. List systems past support.
  3. Turn on automatic updates; set a maintenance window for critical systems.
  4. Write a monthly patch cycle and an emergency patch procedure.
  5. Produce a compliance report.
  6. Document exceptions and plan renewal.

ujans sets up and runs patch management for your business, from inventory to automation, testing and reporting.

Looking for help with this?

Tell us what you need and our team will get back to you within one business day.

Get a quote