IPv6, HTTPS, and DNSSEC
Here’s what cloud.gov does to support relevant federal standards and recommendations, for applications on
*.app.cloud.gov and custom domains.
cloud.gov ensures all applications are accessible over IPv6. You don’t have to take any action.
cloud.gov ensures all applications are accessible only over HTTPS with HTTP Strict Transport Security (HSTS) headers in accordance with the HTTPS-Only Standard. Any HTTP requests are permanantly redirected to HTTPS. You don’t have to take any action.
Strict-Transport-Security headers for all applications by default, and has added the
cloud.gov domain/subdomains to the HSTS preload list for most major browsers.
You are responsible for setting up HSTS preloading for your custom domain. cloud.gov doesn’t set this up for you. If you need HSTS preloading, follow the guidance from the maintainers of the HSTS preload list. The HTTPS-Only Standard encourages HSTS preloading.
Additional details are available in the cloud.gov FedRAMP P-ATO documentation package, including in System Security Plan controls SC-8, SC-12, and SC-20.
cloud.gov does not currently support DNSSEC on
cloud.gov domains. For example, an application at
*.app.cloud.gov would not support DNSSEC.
If you need DNSSEC for your custom domain, you are responsible for configuring DNSSEC in your DNS system. cloud.gov can’t configure DNSSEC for you because cloud.gov does not have access to your DNS system.
cloud.gov supports mapping your DNSSEC-enabled custom domain to your applications hosted on cloud.gov – see DNSSEC support.
Additional details are available the cloud.gov System Security Plan, including controls SC-20, SC-21, SC-22, and SC-23.