Skip to main content

Security report for bep.gov

Bureau of Engraving and Printing · Government · United States

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

Security score

75/100

Risk levelMedium

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

The Bureau of Engraving and Printing (BEP) operates as the official U.S. government agency responsible for the production of United States currency and related security documents. The website serves as a comprehensive resource for the public, providing detailed information on currency production, mutilated currency redemption services, accessibility programs for the visually impaired, visitor center tours, and an online shop for currency-related products. The BEP holds a strong market position as the primary currency producer for the U.S. government, supported by its .gov domain and official branding. Technically, the website is built on Drupal 10, leveraging modern web technologies including Google Analytics and Tag Manager for analytics, and FontAwesome for icons. The site demonstrates good performance, excellent mobile optimization, and strong accessibility features. Hosting appears to be supported by government infrastructure and Akamai CDN, ensuring reliable delivery. SEO and metadata are well implemented, contributing to a professional and user-friendly experience. From a security perspective, the site enforces HTTPS and employs privacy-conscious analytics configurations. While explicit security headers are not evident in the provided data, the site shows no signs of vulnerabilities or exposed sensitive data. The presence of a vulnerability disclosure policy and official .gov domain enhance trust. However, the absence of a cookie consent mechanism and detailed incident response information suggests areas for improvement. Overall, the BEP website is a highly credible, secure, and well-maintained government resource. It effectively balances informative content with technical robustness and user accessibility. Strategic recommendations include enhancing security headers, implementing cookie consent for compliance, publishing incident response details, and adding a security.txt file to facilitate vulnerability reporting.

Scanned

This is an earlier scan of bep.gov. View the latest report

NIS2 and GDPR posture

GDPR outside view
58/ 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 bep.gov

This scan found 19 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
85
Security headers
55
Email security
70
DNS health
80
Network security
100
GDPR outside view
58
Average
75

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

Technical appendix

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

Business context

Business profile

The BEP is positioned as an essential government entity within the U.S. Treasury Department, focusing on currency production and related public services. Its business model is non-commercial, serving the public interest and government needs. The website targets a broad audience including the general public, currency collectors, visually impaired individuals, government employees, and tourists. Key services include currency production education, mutilated currency redemption, accessibility programs, and visitor engagement. The BEP maintains partnerships with other Treasury bureaus and government agencies, reinforcing its authoritative role. The site’s content quality and branding consistency reflect a mature digital presence aligned with government standards, supporting trust and transparency.

Security posture

The BEP website demonstrates a mature security posture with mandatory HTTPS encryption and privacy-aware analytics configurations. No critical vulnerabilities or exposed sensitive information were detected in the HTML content. The site lacks some advanced security headers which could further harden the security posture. The presence of a vulnerability disclosure policy indicates proactive security management. However, the absence of explicit incident response contact information and security policy pages suggests room for improvement in transparency and readiness. Overall, the site aligns well with government security expectations but could benefit from enhanced header policies and formalized incident response documentation.

Recommendations

  1. Implement comprehensive security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to strengthen defense against common web attacks.
  2. Introduce a cookie consent banner or mechanism to comply fully with privacy regulations and enhance user transparency.
  3. Publish detailed incident response and security policy pages to improve transparency and user trust.
  4. Add a security.txt file at the root domain to facilitate responsible vulnerability disclosure and communication.
  5. Regularly audit and update third-party scripts and analytics tools to mitigate potential security risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Bureau of Engraving and Printing
Description
The Bureau of Engraving and Printing (BEP) is the U.S. government agency responsible for producing United States currency and other security documents. The site provides information about currency production, services like mutilated currency redemption, currency reader programs, and visitor centers.
Key services
Currency production information, Mutilated currency redemption, Currency reader program for visually impaired, Visitor center tours, Online shop for currency-related products
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 10, Google Analytics, Google Tag Manager, YouTube iframe API, FontAwesome
Frameworks
Drupal CMS
Platforms
Web
Performance
moderate
Mobile
excellent
Accessibility
excellent
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • IP anonymization in Google Analytics
  • No exposed sensitive data in HTML
  • Use of official .gov domain

Analytics and tracking

Services
Google Analytics, Google Tag Manager, Digital Analytics Program (DAP)
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Akamai Boomerang
Transparency
good

Site quality

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

Key observations

  1. Official U.S. government website with .gov domain
  2. Comprehensive content about currency production and services
  3. Strong branding and consistent design
  4. No signs of malicious or suspicious content
  5. Good use of modern web technologies and analytics
  6. Lack of explicit cookie consent mechanism
  7. WHOIS data unavailable, typical for .gov domains
  8. Social media presence on official government channels
Technical notes

Notes

The website is built on Drupal 10, a modern and widely supported CMS, ensuring a solid foundation for content management and security. Integration with Google Analytics and Tag Manager provides robust analytics capabilities, while the use of FontAwesome enhances visual consistency. Hosting appears to leverage government infrastructure and Akamai CDN, supporting performance and availability. The site is mobile-optimized and accessible, adhering to best practices. Performance is moderate, with potential for improvement through optimization of third-party scripts and caching strategies. The technical stack is well-suited for a government agency, balancing functionality, security, and user experience.
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. 75/100Medium25 findingsView report
Reviews of this site

Share your experience with bep.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 bep.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.