Skip to main content

Security report for cloud.gov

U.S. General Services Administration · Government · United States

Low risk. 3 critical or high findings in Security headers and GDPR outside view.

Security score

78/100

Risk levelLow

0–100, higher is better. How it is calculated

Cloud.gov is a U.S. government-operated platform-as-a-service designed to enable federal agencies to deploy secure, compliant digital services efficiently. Developed and maintained by the General Services Administration's Technology Transformation Services, it offers modern application hosting, compliant federal public websites, and DevSecOps workspaces tailored for government needs. The platform is FedRAMP Moderate authorized, ensuring adherence to stringent federal security standards and compliance mandates. Its business model leverages Interagency Agreements to simplify procurement and accelerate deployment timelines for government teams. Technically, Cloud.gov employs a modern tech stack including Astro for static site generation, the U.S. Web Design System for accessibility and design consistency, and is hosted on Amazon Web Services. The site demonstrates excellent performance, mobile optimization, and accessibility. Analytics are implemented via the Digital Analytics Program and Google Tag Manager, though a cookie consent mechanism is absent. From a security perspective, Cloud.gov exhibits strong practices including HTTPS enforcement, continuous monitoring, vulnerability scanning, incident reporting, and alignment with NIST and Zero Trust frameworks. The platform's FedRAMP Moderate authorization and GSA affiliation provide high trust and legitimacy. Minor improvements include enabling DNSSEC, publishing a security.txt file, and adding explicit data protection officer contact details. Overall, Cloud.gov presents a highly professional, secure, and trustworthy government cloud platform with excellent content quality and technical implementation. The platform effectively balances compliance, security, and usability to serve federal agencies' digital transformation needs.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

3 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…
  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

Need hands-on remediation? Email guard@offseq.com

Keep watching cloud.gov

This scan found 18 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
95
Security headers
55
Email security
85
DNS health
80
Network security
100
GDPR outside view
53
Average
78

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention cloud.gov, from OffSeq Breach.

Total records
35
Employees
0
Customers
35
Third parties
0
Weak passwords
11%

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for cloud.gov.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Cloud.gov occupies a unique position as a government-operated cloud platform, differentiating itself from commercial cloud providers by eliminating traditional procurement barriers such as RFPs and multi-year contracts. Its Interagency Agreement model with GSA streamlines acquisition for federal agencies, enabling rapid onboarding and flexible usage. The platform's FedRAMP Moderate certification and compliance with federal mandates position it as a trusted solution for government digital services. Cloud.gov's partnership ecosystem includes GSA and related federal entities, with a focus on serving federal teams of varying sizes and complexities. The business model emphasizes mission alignment over profit, fostering long-term government collaboration and continuous platform adaptation. Growth indicators include ongoing platform enhancements, expanded service offerings, and active community engagement through documentation and support channels.

Security posture

Cloud.gov demonstrates a mature security posture aligned with federal standards and best practices. The platform's FedRAMP Moderate authorization confirms compliance with rigorous security controls, including continuous monitoring, monthly vulnerability scanning, and incident response capabilities. Security measures such as encrypted isolated networking, short-lived credentials, and centralized logging support a robust defense-in-depth strategy. The absence of DNSSEC is a minor gap but does not critically impact overall security. Incident response readiness is supported by clear contact channels and a published vulnerability disclosure policy. Data protection practices are strong, though explicit data protection officer contact information is not provided. Overall, Cloud.gov's security culture is proactive and well-integrated with federal compliance requirements, minimizing risk for its government customers.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish a security.txt file at the root domain to facilitate vulnerability reporting.
  3. Implement a visible cookie consent banner or mechanism to improve privacy compliance.
  4. Provide explicit contact information for a Data Protection Officer or privacy lead.
  5. Regularly audit and publicly document security headers and configurations for transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
U.S. General Services Administration
Description
Cloud.gov is a platform-as-a-service built for government agencies to deploy secure, compliant sites and applications without managing infrastructure. It is developed and maintained by a federal team within GSA’s Technology Transformation Services.
Key services
Modern application hosting, Compliant federal public websites, DevSecOps workspaces
Content quality
excellent
Branding
consistent

Technology

Stack
Astro v5.13.7, Google Fonts (Inter), USWDS (U.S. Web Design System), Google Tag Manager, Digital Analytics Program (DAP), GitLab (for DevSecOps workspace)
Frameworks
USWDS
Platforms
AWS (inferred from AWS DNS nameservers)
Performance
fast
Mobile
excellent
Accessibility
excellent
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • FedRAMP Moderate Authorization
  • Continuous monitoring and vulnerability scanning
  • Incident reporting and POA&M updates
  • Encrypted isolated networking
  • Short-lived credentials and granular access policies
  • Centralized logging and incident alerting

Analytics and tracking

Services
Digital Analytics Program (DAP), Google Analytics (via GTM)
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
Digital Analytics Program (DAP)
Transparency
good

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is a U.S. government service platform operated by GSA.
  2. Content is comprehensive, well-structured, and professionally presented.
  3. Strong emphasis on federal compliance and security certifications.
  4. No signs of suspicious or malicious content.
  5. No cookie consent mechanism detected despite analytics usage.
  6. No visible phone contact numbers; communication primarily via email and web forms.
  7. DNSSEC is not enabled, which is a minor security gap.
  8. No security.txt file found for vulnerability disclosure.
Technical notes

Notes

The website is built using modern technologies including Astro for static site generation and the U.S. Web Design System for consistent, accessible design. Hosting on AWS provides scalable and reliable infrastructure. Performance is fast with good mobile optimization and accessibility compliance. Analytics are integrated via government-standard tools like the Digital Analytics Program and Google Tag Manager. The site uses multiple AWS nameservers and has a long domain registration history consistent with its government affiliation. Minor technical improvements include enabling DNSSEC and adding a security.txt file. Overall, the technical implementation supports a secure, performant, and user-friendly platform suitable for federal government use.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Earlier scans of this domain

  1. 78/100Low20 findingsView report
  2. 78/100Low24 findingsView report
Reviews of this site

Share your experience with cloud.gov. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review cloud.gov.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.