Security update

Also known as: security patch

On this page 7

A security update is a software change released by an operating system vendor to close a known vulnerability, so that a flaw which could let attackers run code, raise privileges or read protected data can no longer be exploited. In OS security, it is the primary corrective control: built-in protections such as memory protection and exploit mitigation make attacks harder, while security updates remove the underlying defect itself.

The term is often used interchangeably with security patch. Desktop operating systems such as Windows, macOS and Linux distributions deliver these fixes through their own update channels, typically on a predictable monthly cadence for routine issues and immediately for flaws that are already being exploited.

How a security update moves from flaw to fix

Every security update follows a vulnerability lifecycle that begins with discovery and ends when the fix is installed on each machine. The gap between public disclosure and installation is the exposure window, and shortening it is the main goal of update management.

StageWhat happensWho acts
DiscoveryA researcher, vendor or attacker finds the flawSecurity researchers, vendors
Coordinated disclosureThe vendor is told privately and given time to fixResearcher and vendor
Identifier assignmentA CVE identifier and severity score are issuedVendor or CVE authority
Fix developmentCode is corrected and tested for regressionsVendor engineering
ReleaseThe update and an advisory are publishedVendor
DeploymentSystems download and install the updateUsers and administrators
Stages of the security update lifecycle

Release publishes the fix, but it also reveals where the flaw lies. Attackers routinely compare patched and unpatched files, a technique called patch diffing, and can build working exploits within days. Unpatched systems therefore become more exposed after release, not less.

Types of security updates and their urgency

Vendors classify security updates by severity and delivery method, and the classification decides how quickly administrators must act. Severity is commonly expressed with the Common Vulnerability Scoring System, which rates flaws from 0.0 to 10.0.

CategoryTypical triggerExpected response time
Out-of-band emergency fixFlaw exploited in the wildHours to a few days
Critical cumulative updateRemote code execution without user actionWithin days
Important routine updatePrivilege escalation or information disclosureWithin one to two weeks
Rapid security responseSmall urgent fix outside the full releaseAs soon as offered
Microcode or firmware updateProcessor or boot-level flawPlanned maintenance window
Common categories of security updates

Modern desktop systems mostly ship cumulative updates, in which each release contains all earlier fixes. This simplifies deployment because a machine needs only the latest package, but it also means that skipping one problematic update usually requires skipping later security fixes as well.

A special case is the zero-day vulnerability, a flaw exploited before any fix exists. Until the vendor releases an update, defenders depend on mitigations such as disabling a vulnerable feature, tightening the host-based firewall or applying hardening settings.

Not every update improves security, and not every security improvement comes as an update. The distinction matters because organizations often apply different approval rules to each kind of change.

Change typeMain purposeTypical sizeRisk of disruption
Security updateFix a specific vulnerabilitySmall to mediumLow to moderate
Bug fix updateCorrect functional defectsSmall to mediumLow
Feature updateAdd capabilities or new versionsLargeModerate to high
Driver updateImprove hardware supportVariesModerate
Configuration hardeningReduce attack surface by settingsNo new codeDepends on scope
How security updates differ from neighboring concepts

Security updates also differ from exploit mitigations such as ASLR or control-flow integrity. Mitigations raise the cost of exploiting a whole class of bugs, while an update eliminates one particular bug. A well-defended system needs both, because mitigations buy time and updates remove the target.

Deploying security updates on desktop systems

Effective deployment balances speed against stability. Home users benefit most from automatic installation, whereas organizations usually test updates on a small group before releasing them widely, a practice known as ring-based deployment.

  • Pilot ring: a few IT staff machines receive updates on release day.
  • Early adopters: a representative tenth of devices follows after several days.
  • Broad deployment: the remaining fleet updates once no regressions appear.
  • Exception group: specialized systems wait for vendor certification, with compensating controls.

Installation often requires a restart, because files in use by the kernel or running services cannot be replaced safely while loaded. Some systems apply kernel fixes through live patching, but desktops still rely mainly on reboots. Updates must be cryptographically signed by the vendor; the operating system refuses unsigned packages, which protects the update channel itself from tampering.

Verification closes the loop. Administrators confirm installation through compliance reports or vulnerability scanners rather than assuming success, since failed installations and pending restarts are common reasons why a supposedly patched machine remains vulnerable.

Risks and common mistakes in security patching

Most successful attacks on desktops exploit flaws for which a fix already existed. The problems usually lie in process rather than technology, as the following table summarizes.

MistakeTypical causeRemedy
Indefinite deferralFear of breaking applicationsTime-limited deferral with testing rings
Unsupported systemsOperating system past end of lifeUpgrade or isolate the device
Pending restartsUsers postpone rebootsEnforced restart deadlines
Third-party gapsOnly the OS is patchedInclude browsers, runtimes and drivers
No verificationAssumed success after deploymentScan and report patch compliance
Patching mistakes, their causes and remedies

Updates themselves occasionally cause regressions, such as boot failures or broken drivers. The correct response is a tested rollback plan and quick reporting to the vendor, not abandoning updates, because the risk of a known unpatched flaw almost always outweighs the risk of a faulty patch.

Understanding it simply

Think of a computer’s operating system as a large building with thousands of doors and windows. Sometimes someone discovers that one lock can be opened with a simple trick. A security update is the replacement lock sent by the building’s maker.

Once the fix is public, burglars also learn which lock was weak. That is why installing security updates promptly matters so much: the longer a computer waits, the more people know exactly how to get in.

Applied in practice

An accounting firm with 120 Windows laptops receives the monthly cumulative update on its regular release day. The advisory lists a critical remote code execution flaw in a networking component, rated 9.8 on the CVSS scale, and notes that exploitation is considered likely.

The IT administrator sends the update to a pilot ring of eight devices the same afternoon and checks the tax software, the document scanner drivers and the VPN client. After two days without problems, the update goes to all remaining laptops with a 48-hour restart deadline.

On day five, the compliance report shows 117 machines patched. Three laptops belong to staff on leave, so the administrator blocks them from the VPN until they update. The result is full coverage within one week, well before public exploit code appears for the flaw.