Security, data and compliance in Satellite/Geospatial Data Lake

How Satellite/Geospatial Data Lake protects data and supports your compliance obligations.

Security controls

Single sign-on

Users sign in through your identity provider, so your authentication policies, including certificate-based sign-in, apply.

Access by role and holding

What each person can see follows their role and their grants by program and collection; platform operators do not see mission content.

Encryption and keys

Data is encrypted at rest and in transit, with keys Moraph staff cannot use without explicit, time-bound authorization from your organization.

Complete audit trail

Every search, retrieval, grant, change and export is logged with the person and time, and cannot be edited.

Cleared US staff

Federal and defense work is handled only by US citizens with active clearances, and the environment is hosted only in the United States.

Tested releases

Security testing gates every change to Moraph's tooling, and a software bill of materials is kept for the components Moraph supplies.

Requirements it supports

• DoD Instruction 8510.01, Risk Management Framework for DoD Systems
• CNSSI No. 1253, Security Categorization and Control Selection for National Security Systems
• NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations
• Intelligence Community Directive 503, IC Information Technology Systems Security Risk Management
• DoD Manual 5200.01, DoD Information Security Program
• Executive Order 13526, Classified National Security Information

The product supports these requirements; meeting them remains your organization's responsibility.

Where it runs

• On your premises: Built in your data center or enclave, including classified environments, and operated under your organization's authority by cleared Moraph staff where the contract provides for it.
• US government cloud region: Built in a US government cloud region your organization has approved, hosted only in the United States.
• Hybrid: A cloud or central archive combined with storage and compute closer to where data is collected, scoped in the proposal.

Limitations

• Moraph is not the manufacturer of the storage and compute hardware or the cloud provider. Their own service commitments, roadmaps and outages apply, and hardware, software and cloud licences are subject to their terms.
• Moraph does not hold an accreditation or authorization for the environment. Your authorizing official decides whether it operates; Moraph maps controls and supplies evidence to support that decision.
• Work in classified environments happens under your organization's authority and only where the contract provides for it, by US citizens with the required clearances.
• Moraph does not collect or task imagery. Data comes from the government and licensed commercial sources your organization provides, under their terms.
• Model outputs are candidates for analysts to review, not findings. Choosing, validating and interpreting analytic models is your organization's responsibility.
• Ingest and processing throughput depend on network links, hardware, data formats and workloads; they are sized during design rather than guaranteed in advance.
• Moving data between security domains is not included; it uses the cross-domain solution your organization has approved.
• The lake does not replace analysts' exploitation and GIS tools; it provides the storage, catalog and compute those tools draw on.