Last updated: 2026-10-29
Purpose
This document explains how HIAB customers can migrate to On-Premise Scanning, including timelines, limitations, data migration, and support milestones.
Introduction
On-Premise Scanning is aiming to succeed the HIAB platform which is undergoing deprecation. This document describes the migration path for HIAB customers to the On-Premise Scanning platform, what limitations are present compared to the HIAB platform and if and when those gaps will be closed.
Overarching Onboarding Schedule
|
Event |
When |
|---|---|
|
On-Premise Scanning technology preview |
Early November 2026 |
|
On-Premise Scanning public preview |
Q4 2026 |
|
On-Premise Scanning migration blocker gaps resolved We do not expect anyone to be blocked from migrating because of functionality we intend to replace at this point |
Q1 2027 |
|
On-Premise Scanning general availability |
Q1 2027 |
|
HIAB end general of support |
Q1 2027 |
|
HIAB end of extended support |
Q3 2027 |
Major Changes Compared to HIAB
On-Premise Scanning does not have the Classic interface available on it, and all actions that require Classic are therefore not available on On-Premise Scanning.
Migrating to On-Premise Scanning
HIAB and On-Premise Scanning are two completely independent systems. When considering migration to On-Premise Scanning the new system can be deployed and the user can use both in parallel if needed. Data does not transfer between the two systems though, so if you intend on using the same data, it needs to be transferred and then independently maintained in both systems.
When starting out, you should follow the standard installation procedure to get your platform up and running. Once you have the On-Premise Scanning platform up and running you can consider migrating your data.
Installation instructions for On-Premise Scanning can be found at On-Premise Scanning Installation
Data migration will not be available during the initial tech preview
On-Premise Scanning requires RC Scanners. See Installation for instructions on how to set those up.
The RC Scanners needs to be installed from the On-Premise Scanning, and not Outscan. Adapt to the documentation accordingly
Once your On-Premise Scanning is setup with RC Scanners, follow Migrating Data From HIAB to On-Premise Scanning to import your data from the HIAB.
Data migration will not be available during the initial tech preview
On-Premise Scanning vs HIAB Gaps
Since On-Premise Scanning is gradually taking shape, some functionality will not be available in the tech preview. The following table describes in chronological order what will be replaced and when users can expect it to become available.
|
Feature |
Arrival |
|---|---|
|
Proxy supports for online deployments requiring proxy settings to be configured to update and get new vulnerability definitions. |
Q4 2026 |
|
Air-gap support |
Q4 2026 |
|
Data migration from HIAB |
Q4 2026 |
|
Compliance scanning |
Q1 2027 |
|
Single sign-on |
Q1 2027 |
|
LDAP/AD integration |
Q1 2027 |
Obsolete Features
Features that will no longer be needed in On-Premise Scanning.
|
Feature |
Rationale |
|---|---|
|
HIAB “Planning“ / retention management |
On-Premise Scanning is using Portal only, which is using a different data model compared to Classic that does not grow the same way. This plus an improved retention enforcement methodology has removed the need for customer controlled retention management. |
|
HIAB “maintenance settings“ |
On-Premise Scanning utilizes a zero downtime update rollout strategy, removing the need for users to configure their own update scheduler. Postponing an update is not currently supported, but is being evaluated as a future improvement. Offline updates are handled through another method. See Update Air-Gap On-Premise Scanning Deployment |
|
HIAB “Distribution settings“ |
On-Premise Scanning does not support HIAB scanners, only RC Scanners.
|
Gaps that will remain open
Some features that exists in HIAB in Classic will intentionally not be present in Portal regardless of whether its on HIAB, Outscan or On-Premise Scanning.
-
Database integration (report integration)
-
Custom compliance policies