Skip to main content

Security report for heritage-kbf.be

King Baudouin Foundation · Non-profit · Belgium

Medium risk. 6 critical or high findings in GDPR outside view, Security headers and 1 other check.

Security score

63/100

Risk levelMedium

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

The King Baudouin Foundation's Heritage KBF website serves as a platform to promote and conserve Belgium's cultural heritage through its Heritage Fund and associated philanthropic activities. The site targets a general audience including cultural institutions, philanthropists, and the public interested in heritage preservation. It offers information on collections, loans, publications, and current projects, positioning itself as a reputable non-profit organization within Belgium's cultural sector. Technically, the website is built on Drupal 7 with common JavaScript libraries and integrates Google Analytics and Tag Manager for user tracking. While the site is accessible and professionally designed, it shows signs of aging technology and lacks some modern security headers and cookie consent mechanisms. The security posture is adequate with HTTPS enforced but could be improved by implementing additional security best practices and updating the CMS. WHOIS data is restricted, typical for .be domains, but the website's branding and content strongly support its legitimacy. Overall, the site is trustworthy and functional but would benefit from technical modernization and enhanced privacy compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
28/ 100 · High
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

6 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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 heritage-kbf.be

This scan found 24 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
65
Security headers
40
Email security
85
DNS health
60
Network security
100
GDPR outside view
28
Average
63

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 King Baudouin Foundation operates as a medium-sized non-profit entity focused on heritage conservation and philanthropy in Belgium. Its business model revolves around acquiring, promoting, and lending cultural heritage assets, supported by patrons' funds. The foundation maintains partnerships with related heritage sites and offers philanthropic project support, indicating a diversified service portfolio within the cultural sector. The website reflects a stable market position with consistent branding and a clear mission. Growth opportunities may include expanding digital engagement and improving technical infrastructure. The absence of direct contact emails and phone numbers suggests a preference for controlled communication channels via contact forms. The foundation's ecosystem includes partner domains for multilingual outreach, enhancing its regional influence.

Security posture

The website enforces HTTPS, ensuring encrypted communications, and uses reputable third-party analytics services with basic privacy considerations. However, it lacks important security headers such as Content-Security-Policy and X-Frame-Options, which are recommended to mitigate common web vulnerabilities. The use of Drupal 7, an outdated CMS version, poses potential security risks due to limited support and patches. No exposed sensitive data or known vulnerabilities were detected in the HTML content. The absence of a published security policy or incident response contacts indicates room for improvement in transparency and preparedness. Overall, the security posture is moderate but could be significantly enhanced by updating the CMS, adding security headers, and implementing formal security policies.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common attacks.
  2. Introduce a cookie consent banner or mechanism to comply fully with GDPR and improve user privacy transparency.
  3. Upgrade the website CMS from Drupal 7 to a supported and secure version or alternative platform to reduce security risks and technical debt.
  4. Publish a clear security policy and incident response contact information to improve trust and readiness for security incidents.
  5. Conduct regular security audits of third-party scripts and libraries to ensure no vulnerable components are in use.

Contact details published on the site

Addresses
Legal name
King Baudouin Foundation
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
King Baudouin Foundation
Description
The King Baudouin Foundation conserves and protects Belgium’s heritage through its Heritage Fund, acquiring masterpieces and testimonies, promoting them and making them accessible to the public. It also manages patrons' funds active in the heritage field.
Key services
Heritage Fund acquisitions, Promotion and communication of heritage, Loans of artworks for exhibitions, Support for philanthropic projects
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Drupal 7, Google Analytics, Google Tag Manager, Colorbox, Views Slideshow, Nice Menus
Frameworks
Drupal 7
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of Google Analytics with privacy considerations

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is professionally presented and relevant to heritage conservation.
  3. No direct company contact emails or phone numbers found; contact is via form.
  4. No cookie consent mechanism detected despite GDPR relevant content.
  5. WHOIS data is restricted, limiting domain registration transparency.
  6. Use of Drupal 7 CMS indicates potential technical debt and security risk.
  7. Google Analytics and Tag Manager are used for tracking with basic privacy.
  8. No security headers detected; opportunity for security hardening.
Technical notes

Notes

The website is built on Drupal 7 CMS, utilizing jQuery and several Drupal contributed modules such as Views Slideshow, Nice Menus, and Colorbox for UI enhancements. Google Analytics and Google Tag Manager are integrated for analytics and tracking purposes. The site loads multiple CSS and JS assets from its own domain and partner domains, indicating a modular but somewhat complex front-end architecture. Performance is moderate with no explicit optimization indicators. Mobile optimization and accessibility are basic but functional. The site lacks modern meta tags for SEO and accessibility enhancements. Hosting provider details are not discernible from the content. The use of Drupal 7 suggests potential technical debt and a need for modernization to maintain security and performance standards.
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

Reviews of this site

Share your experience with heritage-kbf.be. 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 heritage-kbf.be.

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.