Skip to main content

Security report for oenb.at

Oesterreichische Nationalbank · Finance · Austria

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

Security score

73/100

Risk levelMedium

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

The Oesterreichische Nationalbank (OeNB) serves as Austria's central bank, playing a critical role in monetary policy implementation, financial market supervision, and economic research within Austria and the Eurosystem. The website reflects a mature digital presence with comprehensive financial data, publications, and educational resources targeting financial professionals, researchers, policymakers, and the general public interested in Austrian and European financial matters. Technically, the site employs modern web technologies such as jQuery, Highcharts, and Matomo analytics, combined with a consent management platform to ensure privacy compliance. Security posture is strong with HTTPS enforced, valid SPF and DMARC records, and no detected vulnerabilities, though improvements like enabling HSTS and OCSP stapling could enhance security further. Overall, the site demonstrates high professionalism, trustworthiness, and compliance with GDPR, making it a reliable source of financial information and services.

Scanned

This is an earlier scan of oenb.at. View the latest report

NIS2 and GDPR posture

GDPR outside view
18/ 100 · Critical
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

4 findings rated critical or high. Fix these first.

  1. GDPR outside view

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

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

  2. 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';…

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

Keep watching oenb.at

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. See sample alerts.

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
92
Security headers
70
Email security
70
DNS health
85
Network security
100
GDPR outside view
18
Average
73

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

OeNB holds a key market position as Austria's national central bank and a member of the Eurosystem, providing essential services including monetary policy execution, financial stability oversight, and statistical data dissemination. Its business model is that of a public institution focused on regulatory and economic functions rather than commercial revenue generation. The website's extensive content and structured navigation indicate a strategic emphasis on transparency and public engagement. The bank maintains a broad partnership ecosystem reflected in its DNS and hosting infrastructure, and it actively engages with stakeholders via multiple social media channels. Growth indicators include ongoing publication of financial reports and research, as well as educational initiatives. The digital infrastructure supports these objectives with a moderate performance profile and good mobile and accessibility features.

Security posture

The OeNB website exhibits a robust security posture with mandatory HTTPS enabled using modern TLS protocols (1.3 and 1.2), strict SPF and DMARC email authentication policies, and no signs of subdomain takeover or vulnerable SSL/TLS configurations. The absence of HSTS and OCSP stapling represents areas for enhancement to prevent downgrade attacks and improve certificate validation efficiency. No critical vulnerabilities or exposed sensitive data were detected. The use of a consent management platform and Matomo analytics indicates attention to privacy and data protection. However, additional HTTP security headers such as Content-Security-Policy and X-Frame-Options would further harden the site against common web attacks. Incident response and security policy documentation are not explicitly found on the site, suggesting potential gaps in public-facing security governance transparency.

Recommendations

  1. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload to enforce HTTPS and protect against protocol downgrade attacks.
  2. Implement OCSP stapling to improve SSL certificate revocation checking performance and reliability.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate cross-site scripting, clickjacking, and MIME sniffing attacks.
  4. Publish a clear security policy and incident response information to enhance transparency and stakeholder trust.
  5. Regularly review and update third-party libraries and scripts to ensure no vulnerabilities are introduced.
Technical notes

Notes

The website is built on a custom or proprietary CMS platform utilizing well-established JavaScript libraries including jQuery and Highcharts for interactive data visualization. It integrates a consent management platform to comply with privacy regulations and uses Matomo for analytics, indicating a preference for privacy-respecting tools. DNS infrastructure is robust with multiple authoritative name servers and no DNSSEC enabled. SSL/TLS configuration is modern but could be improved with additional features like HSTS and OCSP stapling. Performance is moderate with a page load time of approximately 5.8 seconds and a moderate number of resources. Accessibility and mobile optimization are good, supported by ARIA roles and responsive design elements. SEO is well addressed with proper meta tags and structured navigation. Overall, the technical infrastructure supports the bank's mission effectively but has room for modernization and security hardening.
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. 72/100Medium27 findingsView report
Reviews of this site

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

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.