Government LRS Deployment Options

LRS for Government

Veracity Learning (our Learning Record Store (LRS)) can be deployed on any common operating system and is supported in several secure hosting environments for U.S. Government (federal, state, and local) organizations. The LRS has been granted Authorities to Operate (ATOs) by multiple government organizations and is available for Federal Risk and Authorization Management Program (FEDRAMP) environments. When software sits on the FedRAMP-authorized infrastructure, it inherits security controls from that environment. More information about each of Veracity’s LRS secure deployment options for U.S. government organizations is provided below.


OPM USAL Government Enclave (FedRAMP Compliant)

The LRS is available as a SaaS offering to any government organization through the USALearning (USAL)'s contract vehicle.
Visit the USALearning website at: https://usalearning.gov/our-services/learning-ecosystem-support


PowerTrain’s Government Enclave (FEDRAMP Compliant)

The LRS is available as a SaaS offering to any government organization through the PowerTrain FedRAMP environment, managed by PowerTrain’s Government Enclave.
Visit the FEDRAMP Marketplace listing: https://marketplace.fedramp.gov/products/F1405214357


Platform One’s Iron Bank

The Iron Bank process centralizes and standardizes application hardening throughout the DoD. The LRS is available as a containerized hardened software offering in Platform One’s DevSecOps process called Iron Bank. A hardened container allows the application/container to run on an ATO'd Kubernetes cluster that meets the DevSecOps Reference Design. Hardened containers do not have a Certificate to Field (CtF) or an Authority to Operate (ATO). To obtain an ATO a container must go through the normal process in the downstream environment as required in each specific DoD program. Iron Bank and Repo1 (GitLab) are completely open to the public (available at IL2). Containers do not receive an ATO or CTF, but the ORA score they receive is intended to help Iron Bank government organizations evaluate the risk involved in using a given container in their environment. It is always the responsibility of the government organization using a given container to evaluate it and accept or reject it based on their own criteria.

Visit the Iron Bank repository: https://repo1.dso.mil/dsop/veracity/lrs


AWS GovCloud (FEDRAMP Compliant)

Government customers can use an on-premises LRS license to deploy to their AWS GovCloud environment. AWS GovCloud (US) gives government organizations and their partners the flexibility to architect secure cloud solutions that comply with the FedRAMP High baseline as well as other compliance requirements, such as the Department of Defense (DoD) Cloud Computing Security Requirements Guide (SRG) for Impact Levels 2, 4 and 5, FIPS 140-2, and IRS-1075.

As a cloud service provider, AWS follows the FedRAMP process to get cloud service offerings authorized for Federal or DoD use.The FedRAMP process issues a Provisional Authority to Operate (PATO). The PATO is a pre-procurement approval for Federal Agencies or the DoD to use AWS cloud service offerings. Government customers can use the PATO and the inherited controls associated with the PATO when they follow the Risk Management Framework (RMF) process to get their own ATO. ATOs are only issued as part of the RMF process and they are issued by a Federal Agency or DoD Authorizing Officers (AOs).

Visit the AWS Govcloud compliance page: https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/govcloud-compliance.html


Microsoft Azure Government (FEDRAMP Compliant)

Government customers can use an on-premises LRS license to deploy to their Azure environment. Like AWS Govcloud, the Azure for U.S. Government environment uses physically isolated datacenters and networks located in the US only, limits access to systems and processes customer data using screened US persons only. Azure for U.S. Government also complies with FEDRAMP and other compliance requirements.

As a cloud service provider, Microsoft Azure follows the FedRAMP process to get cloud service offerings authorized for Federal or DoD use.The FedRAMP process issues a Provisional Authority to Operate (PATO). The PATO is a pre-procurement approval for Federal Agencies or the DoD to use Azure cloud service offerings. Government customers can use the PATO and the inherited controls associated with the PATO when they follow the Risk Management Framework (RMF) process to get their own ATO. ATOs are only issued as part of the RMF process and they are issued by a Federal Agency or DoD Authorizing Officers (AOs).

Visit the Microsoft Azure Govermment page: https://azure.microsoft.com/en-us/explore/global-infrastructure/government/