Discover
Find missing updates and supported vulnerability details across managed endpoints.
Patch and vulnerability management
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.
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
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.
A closed loop
A clear sequence gives every finding somewhere to go, including the work that cannot be closed yet.
Find missing updates and supported vulnerability details across managed endpoints.
Put known exploitation, severity and business deadlines into a useful order.
Agree staged deployments or a scoped, approved alternative where no patch exists.
Review outcomes, keep open work visible and retain dated evidence.
Capability, in practical terms
A managed service built around controlled change and useful visibility, not a catalogue of security jargon.
Coordinate Windows, macOS and supported Linux updates without stitching together separate manual routines.
Manage security and cumulative updates with policies and staged rollout rings.
Identify available updates, select devices for early deployment and schedule wider rollout.
Patch supported Debian, Ubuntu, Red Hat and SUSE distributions within the agreed scope.
Deploy updates for common third-party applications from a curated catalogue rather than relying on ad hoc manual downloads.
Custom and proprietary application packages can be included when their packaging and deployment requirements are agreed.
Identify operating system and application vulnerabilities on Windows and macOS, including cases where no patch is available yet.
Queue supported updates, software deployments and scripts so devices can catch up after they reconnect.
Review successful, failed and pending deployments, missing updates, pending reboots and open vulnerabilities.
Where a supported connection is agreed, correlate existing scanner findings with managed devices to help identify coverage gaps and plan remediation.
Peer-to-peer delivery can share update files between devices on a local network, reducing repeated internet downloads during larger deployments.
Review application names and versions to identify unsupported or unauthorised software and agree what should be updated or removed.
Approved scripts can restrict risky services, local administrator access or removable storage. Changes are scoped and tested before wider deployment.
Distribute approved security tools to enrolled devices and review installations or removals through configured reports and alerts.
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
We confirm operating systems, applications and endpoint scope during onboarding. Support varies by platform and package, so coverage is agreed rather than assumed.
Prioritisation
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
When there is no patch
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
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.
Supports patching, software update and asset inventory controls, with relevant evidence available for your certifier to assess.
Supports Patch Applications and Patch Operating Systems. It can also assist with user application hardening, application-control visibility and restricting local administrator access.
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.
Supports vulnerability identification and risk assessment under ID.RA, and software maintenance and configuration management under PR.PS.
Access and data
Security and residency arrangements are confirmed with you during onboarding, alongside the endpoints and data in scope.
Administrative access is scoped to agreed duties, with multi-factor authentication and audit records supporting accountability.
Endpoint management is designed to work without opening inbound firewall ports. Devices need outbound connectivity to communicate with the service.
Australian and other provider hosting regions are available. The region, data scope and arrangements are confirmed during onboarding.
Connected to CyberGrape
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
Review this evidence alongside your controls. Use the risk register and Action Hub to record decisions and assign follow-up work.
Questions, answered plainly
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.
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.
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.
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.
We can review whether your current scanner can be connected. Supported connections and data scope are agreed during onboarding.
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.
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.
No. Patch and vulnerability management can support relevant controls and provide evidence for review. It does not establish compliance on its own.
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.