CyberGrape – cyber security certification and GRC platform for small business

Patch and vulnerability management

Find it.
Fix it.
Prove it.

Find missing operating system and application updates, focus on the vulnerabilities that matter most, and get the work completed with a record of what happened.

Cloud-managed endpoints. No VPN or on-site patch server required.

Illustrative workflow
A remediation cycle
MANAGED SCOPE

Finding reviewed

Severity and exposure considered

Change planned

Owner and deployment window agreed

Outcome recorded

Result retained for follow-up

Conceptual illustration only. No customer data or live service metrics.

The handoff problem

Findings are easy. Follow-through is the work.

Vulnerability lists move from a scanner to a ticket queue to a separate patching tool. Each handoff makes ownership harder to see. Remote devices can miss attention, third-party applications are often updated by hand, and evidence ends up scattered when someone asks what was fixed.

Findings that never become completed work
Remote and hybrid devices that miss updates
Third-party apps updated by hand
No clear record for an assessor or insurer

A closed loop

Four steps from discovery to evidence.

A clear sequence gives every finding somewhere to go, including the work that cannot be closed yet.

01 / 04

Discover

Find missing updates and supported vulnerability details across managed endpoints.

02 / 04

Prioritise

Put known exploitation, severity and business deadlines into a useful order.

03 / 04

Remediate

Agree staged deployments or a scoped, approved alternative where no patch exists.

04 / 04

Verify

Review outcomes, keep open work visible and retain dated evidence.

Capability, in practical terms

The work behind a smaller, clearer queue.

A managed service built around controlled change and useful visibility, not a catalogue of security jargon.

01

Patch across managed operating systems

Coordinate Windows, macOS and supported Linux updates without stitching together separate manual routines.

02

Keep Windows updates controlled

Manage security and cumulative updates with policies and staged rollout rings.

03

Plan macOS updates

Identify available updates, select devices for early deployment and schedule wider rollout.

04

Include supported Linux distributions

Patch supported Debian, Ubuntu, Red Hat and SUSE distributions within the agreed scope.

05

Use a curated application catalogue

Deploy updates for common third-party applications from a curated catalogue rather than relying on ad hoc manual downloads.

06

Scope custom applications

Custom and proprietary application packages can be included when their packaging and deployment requirements are agreed.

07

Detect supported vulnerabilities

Identify operating system and application vulnerabilities on Windows and macOS, including cases where no patch is available yet.

08

Catch up after time offline

Queue supported updates, software deployments and scripts so devices can catch up after they reconnect.

09

Keep deployments observable

Review successful, failed and pending deployments, missing updates, pending reboots and open vulnerabilities.

010

Review existing scanner findings

Where a supported connection is agreed, correlate existing scanner findings with managed devices to help identify coverage gaps and plan remediation.

011

Reduce repeat downloads

Peer-to-peer delivery can share update files between devices on a local network, reducing repeated internet downloads during larger deployments.

012

See installed software

Review application names and versions to identify unsupported or unauthorised software and agree what should be updated or removed.

013

Harden device settings

Approved scripts can restrict risky services, local administrator access or removable storage. Changes are scoped and tested before wider deployment.

014

Deploy security software

Distribute approved security tools to enrolled devices and review installations or removals through configured reports and alerts.

015

Follow up on important changes

Configured alerts can highlight software installations, local administrator changes and removed security tools so the team can investigate.

Powered by Action1, with the service scope and endpoint coverage agreed during onboarding.

Coverage

Clear boundaries make better patch plans.

We confirm operating systems, applications and endpoint scope during onboarding. Support varies by platform and package, so coverage is agreed rather than assumed.

Operating systems

  • Windows workstations and servers
  • macOS
  • Supported Linux distributions, including Debian, Ubuntu, Red Hat and SUSE

Applications

  • Common third-party applications in a curated catalogue
  • Custom or proprietary applications, when scoped

Device locations

  • Office and on-premises
  • Remote and hybrid
  • Intermittently offline devices, when they reconnect

Prioritisation

Not every vulnerability deserves the same urgency.

Start with what is known to be exploited or linked to ransomware. Then consider severity, affected endpoints and the remediation timeframes your business has agreed.

Signals that inform the order

  • 1CVSS severity score, a rating of how serious a vulnerability is
  • 2CISA Known Exploited Vulnerabilities status
  • 3Ransomware association
  • 4Number of affected managed endpoints
  • 5Agreed remediation SLA deadlines, or fix-by dates

When there is no patch

Keep the risk visible while the fix is out of reach.

A vendor may not have released a fix, or a deployment may not pass verification. A compensating control can be considered as scoped, approved work, such as restricting exposure or removing vulnerable software.

That control is not the same as a fixed vulnerability or an accepted risk. Record what was approved and done, keep an owner assigned, and track the residual risk until it is closed or formally accepted by the right business owner.

Supporting evidence

Evidence for the standards you work to.

Patch and vulnerability records support your wider assurance programme. They help demonstrate the work, but do not establish compliance or replace the rest of your controls.

Framework 01

SMB1001:2026

Supports patching, software update and asset inventory controls, with relevant evidence available for your certifier to assess.

Framework 02

ACSC Essential Eight

Supports Patch Applications and Patch Operating Systems. It can also assist with user application hardening, application-control visibility and restricting local administrator access.

Framework 03

ISO/IEC 27001:2022

Provides supporting evidence relevant to Annex A 8.8 technical vulnerabilities, 8.19 operational software installation, 8.9 configuration management and 5.9 asset inventory.

Framework 04

NIST CSF 2.0

Supports vulnerability identification and risk assessment under ID.RA, and software maintenance and configuration management under PR.PS.

Access and data

Know the scope. Know where it is hosted.

Security and residency arrangements are confirmed with you during onboarding, alongside the endpoints and data in scope.

Scoped access

Administrative access is scoped to agreed duties, with multi-factor authentication and audit records supporting accountability.

Outbound connectivity

Endpoint management is designed to work without opening inbound firewall ports. Devices need outbound connectivity to communicate with the service.

Hosting agreed up front

Australian and other provider hosting regions are available. The region, data scope and arrangements are confirmed during onboarding.

Connected to CyberGrape

Your patching picture, alongside your compliance work.

Your CyberGrape platform brings managed-device status, missing updates and vulnerability findings together. Dated records provide supporting evidence for continuous assurance and show what still needs attention.

Snapshots are not instant live data, cover managed endpoints only, and do not prove whole-organisation compliance or that every patch is installed.

What a stored snapshot can include

Endpoint status and missing updates
Vulnerability severity, known-exploited and overdue measures
Deployment and automation results
Software inventory and daily trend data

Review this evidence alongside your controls. Use the risk register and Action Hub to record decisions and assign follow-up work.

Questions, answered plainly

Common questions.

Do we need a VPN or an on-site patch server?

No. The endpoint management approach is cloud-based and can reach enrolled devices without an on-site patch server or VPN. Devices still need connectivity to check in, and supported platforms depend on the agreed scope.

Which operating systems and applications are covered?

Windows workstations and servers, macOS and supported Linux distributions can be included for patching. Common third-party applications are available through a curated catalogue, and custom applications can be scoped. Native vulnerability detection is specifically for Windows and macOS.

How do you reduce the chance of a disruptive update?

Updates can be staged through rings with approvals, maintenance windows, reboot controls and success thresholds where configured. Updates may still fail or need follow-up, so deployment results remain visible for review.

What if there is no patch yet?

A compensating control may be considered as scoped and approved work, such as restricting exposure or removing vulnerable software. It is not the same as fixing the vulnerability or accepting the risk. The remaining risk stays tracked until it is closed or formally accepted by the appropriate owner.

Can you connect our existing vulnerability scanner?

We can review whether your current scanner can be connected. Supported connections and data scope are agreed during onboarding.

What evidence does CyberGrape receive?

For the tenant-mapped organisation, stored snapshots can include endpoint status, missing updates, vulnerability severity and known-exploited or overdue measures, deployment and automation results, software inventory and daily trends. The snapshots have a freshness date and cover the managed scope only. They are supporting evidence for continuous assurance, not a penetration test or proof of whole-organisation compliance.

Where is the data hosted?

Australian and other provider hosting regions are available. The actual region and scope are confirmed during onboarding. This does not mean all CyberGrape data is automatically stored in Australia.

Does this certify us against a framework?

No. Patch and vulnerability management can support relevant controls and provide evidence for review. It does not establish compliance on its own.

Close the gap between finding and fixing.

Tell us what devices you manage, what you need to prove and where the current process gets stuck. We will help shape a practical scope.