Outpost24 Portal and HIAB Migration FAQ

^{Last updated: 2026-11-02}

General Questions

Why is Outscan Classic and HIAB being retired?

Outscan Classic and the associated HIAB platform are being retired as part of Outpost24's continued investment in a more modern, efficient, and scalable vulnerability and risk management platform.

Outscan Classic was first introduced around 15 years ago and has been at the core of our vulnerability management platform ever since. While it has served customers well for many years, we regularly receive feedback that the interface feels dated, can be slower than expected, and no longer provides the modern user experience customers expect from today's SaaS platforms.

The new Portal addresses these challenges while introducing significant new capabilities, including centralized findings management, improved risk prioritization, automation, integrations, modern APIs, flexible asset management, and a significantly improved user experience. At the same time, the legacy HIAB scanner platform is being replaced with more modern, scalable, and easier-to-manage Portal-native scanning solutions, including RC-Scanners for hybrid-cloud deployments and On-Premise Scanning (OPS) for customers requiring a fully on-premises deployment.

Outscan Classic and the HIAB platform will both reach End of Support on January 31, 2027. After this date, Outpost24 Support will no longer provide fixes, enhancements, or maintenance for either platform.

The Outscan Classic interface will remain accessible, but unsupported, until April 2027, after which customers will need to use the Portal. Customers using HIAB should plan to migrate to the Portal and subsequently transition to RC-Scanners or On-Premise Scanning (OPS), depending on their deployment model.

What are the benefits of moving to the new Portal?

The new Portal introduces a range of enhancements, including:

• Centralized findings and asset management

• Persistent findings with lifecycle tracking

• Enhanced Farsight threat intelligence, EPSS, and CISA KEV integration

• Flexible tagging and dynamic asset groups

• Automation workflows and scheduled actions

• Fully documented REST API, webhooks, and integrations

• Custom notification templates and in-app notifications

• Inbuilt credential vault

• Improved reporting and filtering capabilities

• Support for SSO and role-based access control (RBAC)

• Modern, dynamic user experience

The underlying scanning technology remains the same, while visibility, prioritization, and operational efficiency are significantly improved.

Will my day-to-day scanning process change?

For most customers, the underlying scanning technologies and assessment capabilities will remain familiar. The same proven scanning engines continue to power vulnerability assessments across external, internal, web application, cloud, and agent-based scanning.

The biggest changes are in how assessments are managed, automated, and analyzed.

The Portal introduces persistent findings, where vulnerabilities retain a consistent identity over time instead of being recreated after each scan. This enables clearer tracking of remediation progress, better understanding of historical exposure, and reduced manual comparison between scan results.

The platform also introduces a new asset-centric model, where related identifiers such as IP addresses, hostnames, cloud resources, and other identifiers are grouped into a single asset. Findings from different security assessments are automatically correlated against these assets, providing a centralized view of risk and reducing the need to navigate between multiple records and data sources.

The Portal further enhances this model with asset recomposition, allowing customers to merge assets, split assets, or redistribute identifiers to better reflect real-world ownership, application boundaries, and infrastructure design. This ensures that asset structures and reporting accurately match how the organization operates.

In addition, the Portal introduces Workflows, allowing organizations to automate and orchestrate security activities across the entire assessment lifecycle. For example, a workflow can automatically:

• Discover assets

• Perform network vulnerability assessments

• Launch web application security assessments

• Generate and distribute reports

• Trigger notifications or follow-up actions

This reduces manual coordination, improves consistency, and helps security teams build repeatable security assessment programs.

Combined with centralized findings, asset-centric risk views, asset recomposition, automation, and improved reporting, the Portal enables a more efficient and scalable way of managing vulnerability and risk management activities.

Will I be contacted by Outpost24 to migrate?

Yes.

Outpost24 will proactively contact all customers to discuss migration planning, timelines, and next steps.

If you have not yet been contacted and would like to begin planning sooner, please reach out to your Account Executive, Customer Success Manager, or Outpost24 Support.

What happens if I do not migrate before Outscan Classic and HIAB reach End of Support?

After January 31, 2027, Outscan Classic and the HIAB platform will no longer receive general product updates, bug fixes, maintenance updates, or platform enhancements.

The Classic interface will also remain accessible until April 2027, and vulnerability rule updates will continue to be pushed to Classic and existing HIABs until April 2027. However, customers should complete their migration before the End of Support milestone to ensure continued support and access to new platform capabilities.

If you have concerns about timing, resource availability, or migration planning, please contact your Account Executive, Customer Success Manager, or Outpost24 Support as early as possible.

Migration Process

How do I migrate to the new Portal?

Outpost24 will proactively contact all customers to plan and coordinate their migration to the Portal.

If you would like to begin planning your migration sooner, please reach out to your Customer Success Manager or Account Executive.

If you are unsure who your contact is, you can:

• Create a support ticket at Jira Service Management

• Email support@outpost24.com

Our team will review your environment and help plan and execute the migration.

Will my scans, findings, and configurations be migrated?

Migration planning is performed on a customer-by-customer basis to ensure each customer’s specific setup and requirements are taken into account. Targets, target groups, and findings (assets, asset groups, and vulnerabilities) can be migrated to the Portal, while other configuration, such as scan schedules and notifications, will need to be set up again in the Portal interface. For dynamic target groups in Classic, these will be migrated as static asset groups in the Portal. If dynamic grouping is required, they will need to be recreated as dynamic asset groups using tags in the new Portal UI.

During the migration process, Outpost24 will review your current setup and advise which data and historical information can be migrated and whether any changes are required as part of the move to the new platform.

While data migration of some historical data is possible in many cases, we generally recommend using the move to Portal as an opportunity to start fresh with a clean setup where appropriate. This can be a good chance to simplify your configuration, review your workflows, and take advantage of the new Portal structure from day one.

Please note: PCI ASV scanning follows a different migration approach. There is no automated migration of existing PCI scopes or configurations. Customers should complete any PCI cycle already in progress in Classic and then set up their next cycle in the Portal. Historical PCI data will remain available in Classic until the Classic shutdown, with the previous three years planned to be made available as read-only data.

Your Account Executive or Customer Success Manager will guide you through the details.

Will there be any downtime during migration?

Migration activities are planned collaboratively between Outpost24 and the customer.

The exact process depends on the services being migrated, but our goal is always to minimize disruption and maintain scanning continuity wherever possible.

If you choose to migrate your historical data to the Portal, your Outscan Classic environment will be placed into a read-only state for the duration of the data migration. This ensures data consistency and prevents changes from being made in two environments simultaneously. Once the migration has been completed, your Portal environment will become the primary platform for managing your vulnerability management activities, while the Classic environment will remain in read-only.

Migration planning, timelines, and any expected impact will be discussed with you as part of your migration project.

Can I run Classic and Portal in parallel during the transition?

Yes. In many cases, customers can operate both platforms during a limited transition period, subject to agreement with their Customer Success Manager.

This can provide an opportunity to validate the Portal, onboard users gradually, and prepare for the transition at a pace that suits your organization.

If historical data is migrated into the Portal, Outscan Classic will be placed into a read-only state to ensure data consistency and prevent changes from being made in two environments simultaneously.

Please discuss the most appropriate approach with your Customer Success Manager.

Licensing & Commercial Changes

Do I need to change my contract before moving to the Portal?

No.

Customers can migrate to the Portal while remaining on their existing commercial agreement.

At renewal, customers will transition to Outpost24's new consumption-based OutscanNX licensing model. Your Account Executive will contact you to discuss the commercial details, timing, and any changes applicable to your environment.

The technical migration to the Portal and the commercial transition to OutscanNX are separate activities and do not need to happen at the same time.

What is OutscanNX?

OutscanNX is Outpost24's new consumption-based licensing model.

Rather than purchasing separate licensing for different scanning technologies, OutscanNX provides a flexible pool of scanning capacity that can be allocated across:

• External vulnerability scanning

• Internal vulnerability scanning

• Agent-based scanning

• Threat intelligence capabilities (Farsight exploitability scoring)

This simplifies procurement, improves flexibility, and allows scanning capacity to adapt as your environment evolves.

Product-Specific Questions

Are there any features that are not yet available in the Portal?

The Portal is fully available for customer onboarding today and continues to receive regular enhancements.

Some capabilities are still being introduced, including:

• Compliance scanning with all pre-built policies from Classic — ADSIC, CIS, GDPR, Hardening, HIPAA, NESA and PCI — from the end of January. Custom compliance policies will not be supported in Portal.

• Additional partner administration capabilities (planned for Q1 2027).

Are there any features that will not be made available in the Portal?

Yes. Some Classic and HIAB capabilities will not be migrated to the Portal or to the new scanner architecture.

• Brute Forcer: Custom Brute Force testing using customizable username and password lists will not be migrated to the Portal and is going End of Life. Checking of default credentials during scanning is unaffected by this change.

• Database Integration: HIAB database integration will not be moved to the new On-Premise Scanning (OPS) solution. Customers using this integration should move to a trigger-based integration using webhooks or a fetch-based solution using the REST API.

• Custom Compliance Scanning: Custom compliance policy creation will not be implemented in the Portal and will no longer be available. All Outpost24-created compliance templates, such as CIS and the other pre-built policies from Classic, are planned to be supported in the Portal from the end of January. Custom policies will not be supported moving forward.

• Some HIAB management functionality: Maintenance settings, including backup, planning and updates, as well as the Distribution view, will not be moved to the Portal. These areas will work differently when HIAB deployments are migrated to RC-Scanners and/or OPS. Until all HIABs have been migrated to the new architecture, customers need to manage these settings in Classic, including for Portal-migrated HIABs.

If you rely on any of these capabilities today, please discuss your use case with your Customer Success Manager, Account Executive, or Outpost24 Support as part of migration planning.

Can I migrate if I use PCI ASV scanning?

Yes. PCI ASV functionality was introduced in the Portal as part of the August release, so customers using PCI ASV scanning can now start their next PCI scanning cycle in the Portal.

If you currently have a PCI cycle running in Classic, you should complete that cycle in Classic. Once it is completed, your next PCI cycle should be set up and run in the Portal.

There is no automated migration of the PCI scope or setup from Classic to the Portal. Because PCI scanning is structured around individual scopes and cycles, each new scope is treated as a new process in the Portal. For most customers, this means copying the assets from their existing PCI scope into the Portal when setting up their first cycle there.

Your historical PCI data will not be lost. As part of the overall Classic shutdown process, we plan to make the previous three years of PCI data available as read-only data, either as individual records or as closed reports. Until the Classic shutdown, the historical data will remain accessible in the Classic environment.

If you use PCI alongside other Outpost24 vulnerability management products, your non-PCI services can be migrated to the Portal independently. Your current PCI cycle can remain in Classic until it is completed, after which your next PCI cycle can be started in the Portal.

If you have any questions about your migration timeline or would like to discuss the best approach for your environment, please contact your Customer Success Manager or Account Executive. They will be happy to guide you through the available options and next steps.

I use HIAB with Outscan RC (Hybrid Cloud). What does migration mean for me?

Customers using HIAB together with Outscan RC (Hybrid Cloud) can already migrate to the Portal user interface while continuing to use their existing HIAB scanners.

The HIAB platform will reach End of Support alongside Outscan Classic on January 31, 2027. From this date, HIABs will no longer receive general product updates, bug fixes, improvements, or other product maintenance. However, vulnerability rule updates will continue to be pushed to existing HIABs until April 2027. After April 2027, customers will need to transition to RC-Scanners to continue receiving the latest vulnerability updates.

Customers are therefore encouraged to migrate to the Portal as soon as practical and can continue using their existing HIAB scanners during the transition period. Migrating to the Portal is a prerequisite before migrating HIAB deployments to RC-Scanners or On-Premise Scanning (OPS). As a separate step, they can then transition from HIAB scanners to RC-Scanners, Outpost24's next-generation Portal-native scanning solution, which is available from the August release.

RC-Scanners are the next-generation scanner for customers using the Hybrid scanning model, replacing HIAB Scanners while continuing to use Outscan Portal as the central management and reporting platform.

Portal-native RC-Scanners provide improvements including:

• Native Portal integration with centralized scanner management and visibility

• Simplified deployment and management through the Portal

• Improved scalability and flexibility for distributed scanning environments

• Modernized architecture designed to support ongoing development and future capabilities

We will work with you to understand your current HIAB setup, introduce the applicable replacement solution, and align on a migration timeline.

Your Account Executive or Customer Success Manager will work with you to plan both the Portal migration and the subsequent transition to RC-Scanners at a pace that best suits your environment.

I use HIAB On-Premises. What does migration mean for me?

Customers using HIAB in a fully on-premises deployment can already migrate to the Portal user interface while continuing to use their existing HIAB deployment. Migrating to the Portal is a prerequisite before migrating HIAB deployments to Portal-native RC-Scanners or On-Premise Scanning (OPS).

The HIAB platform will reach End of Support alongside Outscan Classic on January 31, 2027. From this date, HIABs will no longer receive general product updates, bug fixes, improvements, or other product maintenance. However, vulnerability rule updates will continue to be pushed to existing HIABs until April 2027. After April 2027, customers will need to transition to the new solution to continue receiving the latest vulnerability updates.

Customers are therefore encouraged to migrate to the Portal as soon as practical while continuing to use their existing HIAB deployment. On-Premise Scanning (OPS), the HIAB on-premises replacement, is available in Technology Preview now. General availability, including the ability to migrate data from existing HIAB deployments, is planned for the end of January.

Our new solution will preserve the benefits of local scan execution and local data storage while providing a modern architecture aligned with the Portal platform.

General availability for OPS, including migration of full on-premises HIAB deployments, is currently planned for the end of January. Your Account Executive or Customer Success Manager will work with you to plan both the Portal migration and the subsequent transition to OPS at a pace that best suits your environment.

Can I participate in the On-Premise Scanning (OPS) Technology Preview?

Yes. On-Premise Scanning (OPS), the replacement for fully on-premises HIAB deployments, is available in Technology Preview now for customers who want early hands-on experience before general availability.

The Technology Preview is intended for customers who want to test the new solution in a small, separate setup, validate the setup and workflows, review the documentation, and provide feedback to Outpost24 ahead of the general availability release.

The preview is for new OPS installations. Migration of data from existing HIAB deployments is planned for the general availability release at the end of January.

Customers who want to participate should contact their Customer Success Manager or raise a support ticket. We encourage eligible customers to use the Technology Preview as an opportunity to test OPS early and share feedback that can help shape the solution before general availability.

I am running Compliance Scanning in Classic. When can I migrate?

Compliance scanning will be available in Portal from the end of January with all pre-built compliance policies currently available in Classic: ADSIC, CIS, GDPR, Hardening, HIPAA, NESA and PCI (preview). If you use only these standard policies, you can migrate your other scanning activities to the Portal now and plan to move compliance scanning once the end-of-January release is available.

Custom compliance policies will not be supported in Portal. Customers will no longer be able to create, copy, modify, import, or export custom policies. If you rely on a custom policy today, please contact your AE or CSM to discuss the use case, requirements, and business impact so the request can be shared with Product for assessment. However, support for any specific custom policy cannot be committed.

Please note: The end-of-January Portal release and the Classic End of Support date are close together. Customers who need compliance scanning in the Portal should factor this timing into their migration planning to make sure they migrate in time.

Access, Users & Integrations

Will my users need new accounts?

In most cases, users will need to be provisioned in the new Portal environment.

The Portal supports modern identity management capabilities including role-based access control (RBAC), allowing more granular and structured access management than before.

This is also an opportunity to review user access and remove inactive accounts.

Can I continue using the API after migration?

Yes, but integrations must be migrated from the legacy SOAP API to the Portal REST API.

The Portal provides a fully documented REST API and webhook framework with improved performance, automation capabilities, and integration flexibility.

The SOAP API will be deprecated alongside Outscan Classic.

Will my existing integrations continue to work after migration?

Existing integrations will not automatically carry over unchanged, as the new Portal introduces a modern integration layer based on a REST API and webhook framework.

Customers currently using the legacy SOAP API, custom scripts, or SIEM integrations will need to transition these connections to the Portal’s REST API. This provides improved performance, more flexible data access, and better support for automation and workflow-based use cases.

In addition to the REST API, the Portal also supports webhooks, enabling real-time event-driven integrations. Webhooks can be used to trigger external workflows when key events occur in the platform, such as new findings, status changes, or asset updates. This allows organizations to move from scheduled or polling-based integrations to more immediate, responsive automation.

While this does require some adaptation, the new integration model is designed to simplify long-term maintenance and enable deeper integration into security and IT workflows.

Outpost24 will provide documentation and guidance to support the migration of existing integrations, and your Customer Success Manager or Account Executive can assist in planning and validating the transition to ensure continuity of data flows and reporting.

What training and onboarding resources are available?

Outpost24 provides onboarding support, documentation, migration guidance, and Portal introduction sessions.

All Portal documentation is already available in the Outpost24 Knowledge Base, covering setup, configuration, workflows, reporting, administration, and much more.

To ensure a smooth migration, Outpost24 experts provide in-person support and technical training free of charge. These sessions are designed to help your team understand the Portal, prepare for the migration, and make the most of the new capabilities.

For any questions before or during your migration, your Customer Success Manager (CSM) is your primary point of contact and will guide you through the process, as well as coordinate training sessions tailored to you and your team’s needs.

For customers requiring additional assistance, Outpost24 also offers paid migration services through our Managed Services team. These services can provide hands-on support throughout the migration and can be tailored to your specific environment and requirements. Please contact your Customer Success Manager or Account Executive to discuss your requirements and explore a bespoke professional services offering.

You can also always reach out to our Support team, who are ready to assist you with any Portal-related questions or issues.

Partner Questions

I am an MSSP. How does migration work for me?

MSSP partners can already:

• Onboard new customer accounts to the new Portal

• Begin migrating existing end-customer accounts

• Start familiarizing themselves with the new Portal workflows and capabilities

Additional partner administration and account management functionality is still being developed and will continue to be introduced over time.

In the meantime, MSSPs can work directly with Outpost24 Support to enable Portal access for existing end-customer accounts and to onboard new customer accounts into the Portal. Our teams will assist with the required setup and migration activities until the full partner management experience is available.

Outpost24 will proactively contact partners to discuss migration planning, timelines, and next steps. As Outscan Classic reaches End of Support on January 31, 2027, we strongly encourage partners to begin planning the migration of their end customers well in advance to ensure a smooth transition and allow sufficient time to take advantage of the new Portal capabilities.

Partners who are interested in seeing the Portal sooner are encouraged to reach out to their Account Manager to schedule a Portal demonstration, discuss migration planning, and begin the onboarding process. This provides an opportunity to familiarize yourself with the new functionality and prepare for future customer migrations.

Are there any commercial implications for partners when using the Portal?

Partners can start using the Portal immediately without any commercial impact or changes to existing agreements. There is no requirement to update contracts or licensing simply to begin onboarding customers or working within the new platform.

Any commercial topics, including pricing, OutscanNX consumption-based licensing, or contract changes, will be handled separately and should be discussed directly with your Account Manager. This ensures a clear separation between technical migration activities and commercial arrangements.