Home / Solutions / Network Patch Management

Network Patch Management

Know which advisories matter, by the next morning.

Every network vendor publishes security advisories on its own schedule and in its own version format. AotoNet collects them daily, checks them against the running version of every device, and tracks each finding until the fix is verified.

Network Patch Management
Patch overview with devices to action per vendor and the list of advisories

The challenge

Why the traditional approach breaks down

Network patching is usually handled by engineers working through vendor portals, mailing lists and spreadsheets.

Too many sources

Each vendor has its own portal, format and publishing rhythm; nothing arrives in one place.

Version formats differ

10.2.9-h1, 9.18(4)29, R81.20 Take 89 and 22.4R3-S2 cannot be compared with a spreadsheet formula.

Stale inventory

Matching advisories to an old export misses devices and flags ones already patched.

Conditions get ignored

Advisories that apply only when a feature is enabled lead to over-patching or missed exposure.

Deadlines slip

Without consistent risk scoring and SLA dates, exploited vulnerabilities wait like routine ones.

"Patched" is an assumption

Closure is rarely verified, so the audit question "how do you know?" has no good answer.

Two ways to do the job

From manual effort to an automated pipeline

Traditional approach

How it is done today

Network patching is usually handled by engineers working through vendor portals, mailing lists and spreadsheets.

  1. Watch every vendorCheck each OEM security portal and mailing list for new advisories.
  2. Read each advisoryWork out the affected trains, fixed releases, models and feature conditions.
  3. Pull the inventoryExport device versions, often from a source that is weeks out of date.
  4. Compare by handLine up versions per train and per model, and guess whether the vulnerable feature is enabled.
  5. Prioritise and trackAssign priority by judgement and track deadlines in a sheet.
  6. Patch and hopeApply the upgrade in a change window; confirmation that it worked is rarely recorded.
With AotoNet

How AotoNet automates it

AotoNet turns patching into a daily, evidence-based pipeline.

  1. Collect advisories dailyOEM security feeds and national CERT advisories via CSAF, RSS and vendor APIs.
  2. Normalise the advisoryProduct, affected trains, fixed releases, conditions, CVSS and exploitation status in one format.
  3. Match to real devicesVendor-aware version comparison against the reconciled inventory, not a stale export.
  4. Decide applicabilityApplicable, Not Applicable or Ambiguous for every advisory and device, with the reason and the target version.
  5. Score risk and set the SLASeverity, known exploitation, internet exposure and asset criticality give a priority and a due date.
  6. Drive the workflowChange requests, exceptions with expiry and compensating controls, and approvals.
  7. Verify the fixThe running version is re-checked after the window; a finding closes only on evidence.
  8. Report complianceStatus by vendor, platform and site, SLA ageing and a daily validation report.

Side by side

What changes, point by point

AspectTraditional approachWith AotoNet
Advisory intakeManual checks of each vendor portal and mailing listCollected daily from vendor feeds and CERT advisories
Affected devicesEngineer judgement against an old exportMatched to the current reconciled inventory
Version logicSpreadsheet comparisons that break on vendor formatsVendor-aware comparison per release train and model
Unclear casesSilently assumed applicable or ignoredMarked Ambiguous with the reason, for an analyst decision
PrioritisationSeverity alone, or gut feelRisk score from CVSS, exploitation, exposure and criticality, with an SLA date
ClosureAssumed after the change windowVerified by re-checking the running version
AuditAssembled by hand when askedDaily compliance reports and a full decision history

Capabilities

What Network Patch Management includes

Multi-vendor advisory collection

Firewalls, routers, switches, load balancers, VPN gateways and NAC from vendors such as Palo Alto Networks, Fortinet, Cisco, Check Point, Juniper, F5 and Ivanti.

Three-state applicability

Applicable, Not Applicable and Ambiguous, each with current and target version and a written reason.

Configurable risk and SLA policy

Weights for exploitation, exposure and criticality, and SLA days per priority, set to your policy.

Exceptions with expiry

Risk acceptance with justification, compensating control, approver and an end date.

Change workflow

Change requests pre-filled with implementation, back-out and test plans.

Compliance reporting

By vendor, platform and site, with SLA ageing and an exportable daily report.

Applicability
Every advisory–device pair with priority, risk score, current and target versions and due date.
Every advisory–device pair with priority, risk score, current and target versions and due date.

Benefits of automation

What your team gains

Smaller exposure window

Exploited, internet-facing vulnerabilities rise to the top on the day they are published.

Effort where it counts

Engineers work on applicable findings, not on reading every advisory.

Regulatory deadlines met

SLA dates and ageing make overdue patches visible before they become findings.

Proof of patching

Every closure is backed by the version actually running on the device.

Connects to

OEM security advisory feeds (CSAF, RSS, APIs)National CERT advisoriesNetwork monitoring & observabilityDevice & firewall managersITSM change management

See Network Patch Management on your own network.

Book a 30-minute walkthrough, then run a pilot on a sample of your own data.