Skip to main content

Security report for sparkassen-mediacenter.de

Sparkassen-Finanzgruppe (implied) · Finance · Germany

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

Security score

60/100

Risk levelMedium

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

The website sparkassen-mediacenter.de serves as a centralized media management platform primarily targeting the Sparkassen-Finanzgruppe, a major financial group in Germany. It offers a suite of services including video content management, podcasts, interactive videos, and playlist creation, aimed at enhancing digital content distribution within the group's online platforms. The platform is positioned as an internal tool to streamline media content handling and ensure secure access to both public and internal video assets. Technically, the site is built on a traditional Apache server with standard HTML, CSS, and JavaScript assets. However, it lacks modern security infrastructure, notably missing a valid SSL/TLS certificate and HTTPS support, which significantly undermines its security posture. The site includes multiple JavaScript libraries and CSS bundles but does not leverage modern frameworks or CMS platforms. Security headers are partially implemented, but critical HTTPS and TLS configurations are absent. Privacy compliance is minimal, with a privacy policy present but no cookie consent mechanism or GDPR compliance indicators. Contact information is limited to a phone number and support ticket instructions, with no email addresses or social media presence. Overall, the site demonstrates moderate business credibility and good content relevance but suffers from critical security shortcomings that must be addressed to protect user data and maintain trust.

Scanned

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

5 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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 sparkassen-mediacenter.de

This scan found 15 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
50
Security headers
55
Email security
50
DNS health
85
Network security
100
GDPR outside view
18
Average
60

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 platform is a specialized internal media center for the Sparkassen-Finanzgruppe, focusing on video and podcast content management. Its business model revolves around providing secure, centralized media distribution and management for internal and external digital channels. The target audience includes internal users and administrators within the financial group. The site’s market position is niche, serving a defined internal user base rather than the general public. The lack of visible certifications or advanced security policies suggests a need for improved compliance and governance. The partnership with dbc-gmbh.com for mail services indicates reliance on external providers for infrastructure. Growth potential lies in expanding interactive video capabilities and enhancing security and compliance frameworks to meet regulatory requirements.

Security posture

The current security posture is weak due to the absence of a valid SSL certificate and HTTPS support, exposing users to potential data interception risks. While some security headers like X-XSS-Protection and X-Content-Type-Options are present, critical protections such as HSTS are not effectively enabled due to missing TLS. No evidence of vulnerability disclosure policies or incident response contacts was found, indicating limited readiness for security incidents. The login form lacks visible anti-CSRF tokens, which could be a risk vector. The site does not implement modern TLS protocols or session resumption mechanisms, further reducing security and performance. Immediate remediation is required to install a valid SSL certificate, enable HTTPS, and enhance security headers and policies to protect user credentials and data.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable and configure modern TLS protocols (TLS 1.2 or TLS 1.3) and disable legacy protocols.
  3. Implement a comprehensive cookie policy and consent mechanism to comply with GDPR.
  4. Add security.txt and vulnerability disclosure information to improve transparency and incident response.
  5. Enhance login form security by adding CSRF protection and input validation.
  6. Enable HSTS with includeSubDomains and preload directives once HTTPS is active.
  7. Conduct regular security audits and penetration testing to identify and mitigate vulnerabilities.
  8. Improve privacy compliance by detailing data protection officer contact and data retention policies.
  9. Consider adding structured data (JSON-LD) and Open Graph tags to improve SEO and social sharing.
  10. Expand contact information with verified company emails and physical addresses to increase trust.
Technical notes

Notes

The website runs on an Apache server serving static HTML with multiple JavaScript and CSS assets. No CMS or modern web frameworks are detected. DNS configuration lacks DNSSEC and CAA records, which could improve domain security. SSL/TLS is not configured, resulting in no HTTPS support and no secure cipher suites. Performance metrics are missing, but the presence of multiple JS and CSS files suggests potential for optimization. Mobile optimization appears good based on responsive design elements in the HTML. Accessibility features are basic, with no ARIA roles or landmarks detected. SEO optimization is minimal, lacking meta description, Open Graph, or structured data. Hosting provider details are not explicitly identified. Overall, the technical infrastructure is functional but outdated and lacking modern security and performance best practices.
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 sparkassen-mediacenter.de. 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 sparkassen-mediacenter.de.

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.