Vultron offers two deployment options: Customer Azure Government Cloud Deployment and Onsite Deployment.

The Customer Azure Government Cloud Deployment model provides high security, scalability, and minimal maintenance, utilizing managed cloud services within the customer's Cloud Service Provider (CSP) account.

The Onsite Deployment model offers the ability to deploy within the customer's onsite infrastructure and requires the customer to manage hardware and compliance controls.

Both options offer robust security, data control and support the secure processing of Controlled Unclassified Information (CUI), aligning with the [DFARS 252.204-7012](https://www.acquisition.gov/dfars/252.204-7012-safeguarding-covered-defense-information-and-cyber-incident-reporting.) requirements (see comparison table).


Customer Azure Government Cloud Deployment

Vultron will assist in creating, setting up, and using cloud resources within the customer’s Azure Government CSP account, and will assist in creating and setting up these accounts if the customer does not have one. Customers opt for the cloud deployment model to meet their CUI and security requirements, such as those outlined in [DFARS 252.204-7012](https://www.acquisition.gov/dfars/252.204-7012-safeguarding-covered-defense-information-and-cyber-incident-reporting.).

This deployment model offers robust security, high reliability, minimal ongoing maintenance, scalability, standardized deployment, and cost efficiency — see Pricing Comparison for more details.

The customer will always have the most privileged level of control over all hosted cloud resources.

Deployment Diagram

Azure Government Architecture

Vultron Network Diagram (14).png

Deployment Security

Vultron supports the customer’s security and compliance objectives by ensuring that the application fulfills the controls required to meet NIST 800-171 requirements for CMMC Level 2 compliance. All data, including CUI, will reside in Azure Government, a FedRAMP High authorized CSP, hosted in secure data centers within the U.S. CUI data will never leave the CUI Authorization Boundary.