Skip to content

Moraph for clients

Sign in

Getting started

Getting started with FedRAMP High Managed Landing Zone

What FedRAMP High Managed Landing Zone is for, who uses it, what you need before you start, and your first steps.

Applies to FedRAMP High Managed Landing Zone as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 2 min readReport a problem
On this page
  1. What it is for
  2. Who uses it
  3. Before you start
  4. Steps to get started
  5. Where to go next

Moraph sets up and operates a landing zone in AWS GovCloud (US) or Azure Government: the account structure, network boundary, identity, logging and guardrails that every application in the cloud depends on, configured against the NIST SP 800-53 High baseline. Moraph maintains the boundary and patches the shared components, and documents which controls the landing zone provides so application teams know what is left for them. Your agency's authorizing official decides what operates; Moraph supports that decision with control mappings and evidence.

What it is for

Agencies moving to the cloud find that each application team ends up building its own network, logging and identity setup, each with its own security documentation. The result is inconsistent configurations, duplicated effort in every authorization package, and a boundary nobody fully owns. Security staff struggle to see across accounts, and application teams wait months for a compliant place to deploy.

  • Each application team builds its own cloud foundation, differently
  • Authorization packages repeat the same control descriptions for shared infrastructure
  • Logging, boundary protection and identity are set up inconsistently across accounts
  • Patching and drift on shared components fall between teams

Who uses it

  • Agency CIO and cloud program offices
  • Application and product teams that deploy to the cloud
  • Information system security officers and authorizing officials
  • Security operations centers that need visibility across cloud accounts
  • Inspectors general and auditors reviewing cloud controls

Before you start

  • Your organization uses FedRAMP High Managed Landing Zone as a managed platform from Moraph, under an agreement that covers it.
  • Licences for AWS/Azure, bought through Moraph or under your own agreement with the vendor.
  • A Moraph account in your organization for each person who works with Moraph on the service.
  • Named technical and security contacts, recorded in the Moraph Portal.

Steps to get started

  1. Agree the scope of the managed service for FedRAMP High Managed Landing Zone with Moraph, including which environments and teams it covers.

  2. Name your administrators, technical contact and security contact in the Moraph Portal under People and access.

  3. Review the configuration baseline Moraph proposes for your regulations, and record any changes you need.

  4. Confirm how users will sign in, through your identity provider where the platform supports it.

  5. Agree the pilot group and the cut-over plan with your Moraph delivery lead.

Where to go next

Was this page helpful?

Report a problem with this page
What’s the problem?
Quote the step or heading if you can. Don’t include passwords or personal records.
Only if you’d like a reply. We use it for this report and nothing else.

Need help with your own setup rather than this page? Raise a support ticket.