Upgrade, Update & Patch
Every piece of software ships with defects, and every defect is a potential opening for an attacker. The single most effective thing an organisation can do is keep software current: identify what is vulnerable, test the fix, and roll it out before someone else rolls out an exploit. This lesson defines the vocabulary precisely, walks the patch process, and shows the exact Cisco IOS commands to back up and upgrade a device.
Vulnerability, exploit, threat — and why software becomes vulnerable
These three words are used loosely in everyday speech and precisely in security exams. Learn the canonical definitions now, because the whole discipline is built on them.
Put them in one sentence: a threat uses an exploit to take advantage of a vulnerability. The three combine into risk, the likelihood and impact of loss. A common way to express it is risk = (threat × vulnerability) × impact: remove the vulnerability (patch it), and the risk from that threat drops to near zero even if the threat still exists. That is exactly why patching is the highest-value defensive activity available.
| Term | Plain meaning | Example |
|---|---|---|
| Threat | What might cause harm (an actor or an event). | A remote attacker, or a worm spreading on the Internet. |
| Vulnerability | The weakness that makes harm possible. | A buffer overflow in an old IOS release; a default password left in place. |
| Exploit | The concrete method that abuses the weakness. | Crafted packets that trigger the overflow and grant remote code execution. |
| Risk | The chance and size of the loss if it happens. | A high-CVSS flaw exposed to the Internet on an unpatched edge router. |
Why software becomes vulnerable
Software is written by humans, and humans make mistakes. The main sources of weakness are:
- Programming bugs. Buffer overflows, use-after-free errors, integer overflows, missing input validation, and injection flaws all let an attacker send data the developer never expected.
- Design flaws. Some weaknesses are architectural — a protocol that authenticates but does not encrypt, or a default that is insecure rather than secure.
- Misconfiguration. A perfectly patched device with Telnet enabled, a default
password, and
ip http serverleft on is still easy to compromise. - Weak or default credentials. Vendor default logins and reused passwords are a persistent favourite of attackers.
- Age and neglect. This is the big one for network devices.
EOL is not the same as “broken”. An EOL device may still forward packets perfectly well, which is exactly why it lingers in production for years while slowly accumulating unpatched, publicly documented flaws. From a security standpoint, an EOL device is an unpatchable device, and an unpatchable device should be replaced on a managed schedule.
The vulnerability and patch lifecycle
A vulnerability is not a single event; it moves through recognisable stages. The period between a fix being available and that fix being applied is the patch gap (also called the window of exposure) — the time an attacker can still win.
| Stage | What happens | Defender action |
|---|---|---|
| 1. Introduction | The defect ships in the code. Nobody knows it is there. | Buy from supported vendors; track versions. |
| 2. Discovery | A researcher or attacker finds the flaw. | Maintain asset inventory so you can react fast. |
| 3. Disclosure | A CVE is assigned and the vendor publishes a security advisory. | Subscribe to Cisco PSIRT advisories and CVE feeds. |
| 4. Exploitation | An exploit or proof of concept appears; attacks begin. | Prioritise by CVSS score and exposure; apply mitigations. |
| 5. Patch release | The vendor ships a fixed release or patch. | Test in the lab; plan the maintenance window. |
| 6. Patch deployment | Administrators apply the fix across the estate. | Deploy in stages; back up first; verify after. |
| 7. Verification / closure | The flaw is confirmed fixed and recorded. | Re-scan, update the CMDB, close the ticket. |
The Cisco IOS software lifecycle
Cisco IOS does not have one version; it has hundreds, organised in a hierarchy you must be able to read. A release train (or just “train”) is a sequence of releases built on the same code base and intended for a particular role. Within a train, individual releases add maintenance fixes and new rebuilds.
| Part | Meaning |
|---|---|
| 15 | Major version. |
| 2 | Minor version (the feature set of the train). |
| (4) | Maintenance rebuild number within the train. |
| M | The train letter. M = mainline (extended maintenance); T = technology; other letters mark special-purpose trains. |
| 2 | Rebuild of that maintenance release. Earlier = earlier in the train. |
Cisco publishes a latest suggested release (also called the recommended or “validated” release) for every platform and train. Cisco’s guidance is to run the latest validated release for your platform rather than the absolute newest image: it has the most fixed bugs and enough field exposure to be trusted. The Cisco IOS Software Checker maps your running version to known advisories and tells you the suggested fixed release.
| Lifecycle milestone | What it means |
|---|---|
| End of Sale (EoS) | The product or release can no longer be ordered. Support continues for a while. |
| End of Software Maintenance | No new bug fixes or security patches are produced for that release. |
| Last Date of Support (LDoS) | All support ends; the device is fully EOL. |
Patch management: the six-step process
Patching is a process, not an event. The standard lifecycle has six steps.
- Identify — know what you have and what is vulnerable. Keep an up-to-date asset inventory, scan for software versions, read Cisco PSIRT advisories and CVE feeds, and match them against your estate.
- Test — validate the fix in a lab, development, or pilot ring before it touches production. Confirm the device still forwards traffic, routing protocols stay up, and you have a tested rollback.
- Schedule — plan a maintenance window. Prioritise by risk: a high CVSS score on an Internet-facing device goes first; an internal, unreachable flaw can wait.
- Deploy — apply in stages (a pilot group, then the rest), and for network devices always take a configuration backup immediately before the change.
- Verify — confirm the new version is running, services are healthy, and the vulnerability has actually gone. Monitor logs for regressions.
- Document — record what was patched, when, by whom, and why; update the configuration management database (CMDB) and the ticket.
Backing up and upgrading Cisco IOS
Before changing anything, look at what the device already has. The two commands you
start with are show version (which image is running and the config register) and
show flash: (what images and files are stored).
R1# show version Cisco IOS Software, C1900 Software (C1900-UNIVERSALK9-M), Version 15.4(3)M2 System image file is "flash0:c1900-universalk9-mz.SPA.154-3.M2.bin" Configuration register is 0x2102 R1# show flash: System CompactFlash directory: File Length Name/status 1 49703812 c1900-universalk9-mz.SPA.154-3.M2.bin [49703976 bytes used, 62248984 available, 111952960 total]
show flash: to see what is in flash, copy tftp:
flash: to pull an image into the device, and
copy running-config startup-config to make the configuration (and the
new boot system statement) permanent. A configuration that is not copied to
startup-config is lost on reload.show flash: shows too little free space for the new image, delete the old one
after you have a working copy elsewhere: delete flash:<old-image>. On
some flash types you must run squeeze flash: to reclaim the space. Never delete the
image you are currently booted from before the replacement is verified.Image storage, boot, disaster recovery and licensing
Understanding where IOS lives turns an upgrade from a mystery into a checklist. These locations appear throughout IOS commands and exam questions.
| Location | Name in IOS | Holds |
|---|---|---|
| ROM | rommon / ROM monitor | A tiny bootstrap program (and, on some devices, a mini IOS). Survives a wipe; used for recovery. |
| Flash | flash: | The full IOS image file (.bin) and often the startup configuration copy. Non-volatile. |
| RAM | running-config | The active configuration and the running image. Volatile — lost on reload. |
| NVRAM | startup-config | The saved configuration. Small and non-volatile. |
| External | tftp:, usbflash0: | Backups and images held off-device. |
0x2142,
reloading, and then copying the startup-config back lets an administrator recover from a lost
privileged password. An attacker with physical access could do the same — which is why
physical security of the device is itself a hardening control (Lesson 4).Device backup and disaster recovery
- Back up the configuration on every change. At minimum
copy running-config startup-configkeeps the device itself whole; a scheduledcopy running-config tftp:(or to a USB stick withcopy running-config usbflash0:backup.cfg) keeps a copy that survives device loss. - Store backups off-device, versioned, and access-controlled. A configuration can contain hashed secrets, SNMP community strings, and network topology. Treat a config backup as sensitive data, not a text file.
- Protect stored passwords.
service password-encryptionobscures the plain-text passwords with the weak type-7 scheme; where supported, the AES type-6 scheme (key config-key password-encryptfollowed bypassword encryption aes) is stronger.enable secretis already hashed and is never affected by either. - Know both restore paths. Restoring a config is
copy tftp: running-config, or the cleaner atomic methodconfigure replace tftp://192.168.1.100/R1-backup.cfg. Restoring a missing or corrupt IOS image uses ROMmon and thetftpdnldcommand to pull an image back into flash. - Test restores. A backup that has never been restored is a hope, not a backup. Practise recovery in the lab and record how long it takes.
startup-config) and
software (restore the IOS image). Keep both offsite, keep the image that matches
your validated release, and document the exact steps so recovery does not depend on one
engineer’s memory.Licensing: perpetual, subscription, Smart Licensing
Cisco’s licensing has moved from a one-off purchase to a managed, reported model, and the
distinction affects whether you can even legally download the patched image. A
perpetual licence (the classic Cisco IOS feature-set model, for example
universalk9) is bought once and owned forever; it is tied to the image you run and never
expires. A subscription licence (for example Cisco DNA Essentials or Advantage)
grants the right to use software for a fixed term — typically one, three, or five years —
and must be renewed; when it lapses you lose access to the features and to updates.
Smart Licensing (today largely Smart Licensing Using Policy) is the
mechanism that manages both kinds: the device registers with the Cisco Smart Software Manager
(CSSM), reports its usage to a virtual account, and the network stays compliant with the
entitlements you own or lease. The practical consequence for this lesson is simple:
you can only obtain and run a patched release if your entitlement and support contract are
current, so licensing is a security-maintenance dependency, not just an accounting detail.
Inspect the state of a device with show license, show license summary, and
show license status.
Review
Check what you have learned with these review questions.
Sources & references
- Cisco. CCNA (200-301) Exam Topics, Domain 5.0 (Security Fundamentals) and domain 4 (IP services) for device management. cisco.com.
- Cisco. Cisco IOS Configuration Fundamentals Command Reference (
copy,show flash:,boot system, and the configuration register). cisco.com. - Cisco. Cisco Security Advisories and the Cisco IOS Software Checker (PSIRT). sec.cloudapps.cisco.com.
- Cisco. Cisco Product & Software End-of-Life and End-of-Support Policies. cisco.com.
- Cisco. Smart Licensing Using Policy configuration guide. cisco.com.
- NIST. SP 800-40 Rev. 4: Guide to Enterprise Patch Management Planning (2022). csrc.nist.gov.
- FIRST. Common Vulnerability Scoring System (CVSS) Specification. first.org/cvss.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.