Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Rehost
Cyber Security

Rehost

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Cyber Security

Rehost is a migration strategy that moves an application to cloud infrastructure with no code or architecture changes. Often called lift and shift, it preserves the existing workload design and operating practices. It is fast, but it does not automatically deliver cloud optimisation, cost reduction, or process change.

What Rehost Means in Cloud Migration

Rehost is the most direct cloud migration pattern: you move an application to cloud infrastructure and keep the workload, architecture, and operating model largely intact. Because the application is not redesigned, rehost is usually the fastest path to the cloud, but it also preserves the same technical constraints, dependencies, and inefficiencies you already had.

In practice, that makes rehost a transition strategy rather than an optimisation strategy. It can reduce datacentre dependence quickly, but it does not by itself modernise the application, improve resilience, or change how teams provision, secure, or operate it.

Why Rehost Is Used

Organisations usually choose rehost when speed matters more than transformation. It is common for legacy applications, time-sensitive datacentre exits, and workloads that are difficult to refactor without introducing delivery risk. The main value is reduced migration complexity, because the team can preserve the current application design while relocating the runtime environment.

That simplicity is also the reason rehost is often the first stage in a broader cloud journey. It gets the workload moved, then gives the organisation time to decide whether the application should later be replatformed, refactored, retired, or left as-is.

What Rehost Does Not Change

Rehosting changes where the application runs, but not the application’s underlying architecture. Existing bottlenecks, technical debt, weak modularity, and operational dependencies remain in place. If the original workload was tightly coupled, manually operated, or difficult to scale, those characteristics usually move with it.

It also does not automatically reset security design, application efficiency, or cost structure. A rehosted system may still need the same identity, access, logging, patching, and network assumptions it used before the move, which means cloud placement alone is not a substitute for engineering change.

How Rehost Is Evaluated After Migration

Once the workload is running in cloud infrastructure, the important question becomes whether the migration merely relocated risk or also improved the operating model. Teams typically review whether the application is now easier to observe, recover, scale, and govern, and whether the cloud environment has introduced new dependencies, cost patterns, or control gaps.

That post-migration review is where rehost often proves its limits. If the workload still requires the same manual processes and still carries the same design constraints, the organisation may have achieved cloud presence without yet realising cloud advantage.

Risk and Threat Considerations

Rehost can create a false sense of modernisation if teams assume cloud placement alone will improve security or resilience. A lifted application may inherit the same exposure patterns as the original system, while also introducing new cloud misconfiguration, connectivity, and access-management risk.

Failure mechanism: The organisation moves the workload without redesigning weak trust boundaries, privileged access patterns, monitoring, or dependency handling, so existing flaws persist in a new environment and may be harder to notice.

Impact: Attackers can still exploit the same application weaknesses, while the business may also face cloud-specific exposure, unexpected cost growth, and slower remediation if operational ownership was not updated with the move.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST CSF 2.0, CIS Controls v8 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0GV.OC-01 — Organizational ContextRehost decisions depend on business context and migration objectives.
ID.AM-01 — Physical Devices and Systems InventoriedRehosting depends on knowing what applications and dependencies are moving.
PR.PS-01 — Configuration ManagementRehost preserves existing workload design, so configuration control remains critical.
Recommendation — Define the business reason for rehosting before selecting it as a migration path. Inventory workloads and dependencies before relocating them to cloud infrastructure. Carry forward secure configuration management when moving unchanged workloads.
CIS Controls v8CIS-1 — Enterprise Asset InventoryRehost requires knowing which assets, services, and dependencies are in scope.
CIS-4 — Secure Configuration of Enterprise Assets and SoftwareLift-and-shift workloads often retain old configuration weaknesses.
Recommendation — Maintain an accurate asset inventory before and after migration. Harden the migrated environment even when the application code is unchanged.
NIST SP 800-53 Rev 5CM-2 — Baseline ConfigurationRehost keeps the workload design intact, making baseline control essential.
CA-7 — Continuous MonitoringRehosted systems need ongoing visibility to catch inherited and cloud-specific issues.
Recommendation — Establish and maintain secure baselines for the rehosted environment. Continuously monitor rehosted workloads for drift, exposure, and control gaps.
ISO/IEC 27001:2022A.8.9 — Configuration managementRehost preserves operating practices, so configuration governance remains material.
Recommendation — Control configuration changes carefully when workloads are moved unchanged.

Practitioner Guidance

Why practitioners should care: Rehost is a migration tactic, not an end state. Treat it as a controlled relocation that should be followed by explicit decisions about whether the workload will remain stable, be optimised, or be retired.

Common misunderstanding: Teams sometimes equate “in cloud” with “cloud-native.” That is not the same thing. A rehosted system usually needs separate work on architecture, reliability, security controls, and operating processes before it can deliver the benefits people expect from cloud adoption.

Practitioner takeaway: Use rehost to move quickly, but measure success by what changes after the move, not by the move itself.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org