Last updated: 2026-10-20
Introduction
On-Premise Scanning (OPS) provides a large portion of the scan and detect functionality similar to Outscan SaaS through an on-premise deployment, allowing full data sovereignty while retaining vulnerability scanning capabilities.
Usage Overview
On-Premise Scanning is deployed as an open box appliance that gives the owner direct control over the appliance VM while providing some on-VM utilities for easier management of OPS specific configuration.
In general, the owner of the appliance is responsible for the virtual machine, its operating system, and general uptime, whereas Outpost24 is responsible for the software delivered by Outpost24, running in the Kubernetes cluster.
For deploying an OPS, follow the guides located at On-Premise Scanning Installation. Choose the deployment type appropriate for your needs, deploy, and enroll.
At this point, OPS is ready to be used. You can refer to the Portal documentation for how to interact with the solution
OPS requires a RC Scanner to do the actual scanning. Deploy RC Scanners in the networks you need to scan and enroll it to your OPS and get started. See RC-Scanners.
Unlike HIAB, where the scheduler is able to run scans on its own, OPS architecture does not include “local“ scanning capabilities. A separate RC Scanner deployment is needed.
Work in progress and roadmap
On-Premise Scanning is a platform in the process of being rolled out as part of an initiative to succeed the HIAB platform which is currently undergoing deprecation.
Related Articles