Join our Newsletter — 33% off our NHI Course
Home› Glossary› Architecture & Implementation› Public Cloud Migration
Architecture & Implementation

Public Cloud Migration

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Architecture & Implementation

Public cloud migration is the move of applications, data, and infrastructure from on-premises or private environments to a public cloud service. It usually involves replatforming, refactoring, or lifting workloads into provider-managed compute, storage, and networking, with security controls then shifting to shared-responsibility settings, identity policies, and cloud configuration.

What cloud migration changes in security

Moving into public cloud changes the security model from perimeter-heavy control to shared responsibility, provider-native services, and policy-driven access. The biggest shift is that misconfiguration, overly broad permissions, and weak identity design can become the main exposure points, even when the infrastructure itself is more resilient than the old environment.

That is why migration planning should treat security as part of the migration design, not a separate post-cutover task. In practice, the question is not only whether a workload can run in cloud, but what must change in controls, operating model, and ownership when it does.

Common migration patterns and their security trade-offs

Public cloud migration is often described as the “7 Rs”, but from a security perspective the important distinction is how much the workload changes during the move. A simple rehost can preserve old weaknesses, while refactoring or replatforming may allow better segmentation, logging, and identity enforcement, but also introduces new implementation risk.

Lift-and-shift migrations are especially prone to carrying forward legacy trust assumptions, such as flat network access, hard-coded secrets, and static administrative access. More transformative migrations create an opportunity to remove those patterns, but only if the target design is deliberately built around cloud-native controls rather than copied from on-premises habits. NHIMG’s Cloud Migration Security guide covers the core decision points.

A well-run migration therefore balances speed against redesign. The technical destination matters, but so does the path there, because cutover windows, temporary bridges, and coexistence states often create the highest risk period.

Security control areas that usually move with the workload

Identity and access controls usually change first, because cloud access is policy-driven and heavily reliant on IAM roles, federated sign-in, service permissions, and workload credentials. Data protection also changes shape, since encryption, key handling, and data transfer controls must be re-established in the new environment rather than assumed by location alone.

Operational visibility matters just as much. Logging, asset inventory, configuration baselines, and policy enforcement need to follow the workload into the new platform so that security teams can still see who accessed what, which resources are exposed, and where drift has appeared. NHIMG’s Cloud Migration Security Checklist is useful where teams need a structured go-no-go view across discovery, landing zone readiness, identity, data transfer, cutover, and decommissioning.

Networking also changes materially. Public cloud exposes new patterns for east-west traffic, public endpoints, and service-to-service trust, so controls such as segmentation, private connectivity, and exposure review need to be designed around the cloud architecture rather than inherited from the data center.

What can go wrong during and after migration

Migration risk is rarely about the cloud platform itself. It is usually about inherited exposure, rushed configuration, and gaps between the old and new control planes. A workload can be live in the cloud while still carrying old admin paths, stale secrets, permissive firewall rules, or weak storage controls from the source environment.

That is why teams should assume that misconfiguration, secret leakage, and privilege creep are more likely during migration than after steady-state operation. NHIMG’s Cloud Misconfiguration Guide is relevant here because it focuses on public storage, open ports, wildcard IAM, static keys, guardrails, and drift detection.

Post-migration, the main failure mode is often incomplete decommissioning. If the old environment, certificates, keys, snapshots, or access paths remain active, attackers may use the leftover path as the easiest route back into the estate. For that reason, the end of migration is also a control event, not just an infrastructure cleanup task.

Where public exposure becomes part of the migration plan, the risk increases further. NHIMG’s audit cloud resource policies for public access runbook is especially useful for finding unintended public grants on buckets, queues, keys, secrets, and functions.

Why migrations need a security cutover plan

The safest migration programs treat cutover as a controlled change, not a one-time technical handoff. That means the target environment must be ready for access control, logging, rollback, and decommissioning before business traffic fully depends on it. Security teams also need a clear view of what must be rotated or invalidated when the move is complete.

For cloud-native key and certificate dependencies, the migration itself can create a key lifecycle decision, especially when data is re-encrypted, signing keys are moved, or old material must be retired. NHIMG’s Cloud key management service migration playbook helps explain why dual-key periods, rewrapping, and key destruction need explicit planning.

Migration is also a governance exercise. Teams need named owners for the target landing zone, policy exceptions, identity changes, and retirement of the old stack, otherwise temporary choices become permanent exceptions.

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 provides the primary governance reference for this term.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0GV.RM-01 — Risk Management StrategyPublic cloud migration needs explicit risk decisions for rehost, refactor, and cutover choices.
PR.AA-05 — Identity Management, Authentication and Access ControlCloud migration shifts access to policy-driven identity and role controls.
PR.DS-01 — Data-at-rest is protectedData transfer and stored data protection remain central during cloud migration.
Recommendation — Define migration risk tolerance before selecting target patterns and cutover timing. Enforce least-privilege access for migrated workloads, users, and service identities. Protect migrated data with cloud-native encryption and verified key handling.

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 November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org