Skip to main content

Security report for lmu-klinikum.de

LMU Klinikum · Healthcare · Germany

Medium risk. 3 critical or high findings in Security headers and SSL/TLS.

Security score

72/100

Risk levelMedium

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

LMU Klinikum is a leading university hospital in Munich, Germany, recognized for its extensive medical services, research, and education. It operates two main campuses and serves approximately 500,000 patients annually. The website reflects a mature digital presence with comprehensive content, clear navigation, and professional design. Technically, it uses modern web technologies including Scrivito CMS and Matomo analytics, hosted on AWS infrastructure. Security posture is strong with HTTPS and CSRF protections, though some security headers and explicit incident response policies are absent. Privacy compliance is well addressed with clear cookie consent and a detailed privacy policy. Overall, the site demonstrates high business credibility and trustworthiness.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 100 · Low
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 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';…
  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching lmu-klinikum.de

This scan found 22 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
67
Security headers
50
Email security
70
DNS health
60
Network security
100
GDPR outside view
83
Average
72

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 lmu-klinikum.de, from OffSeq Breach.

Total records
7
Employees
0
Customers
7
Third parties
0
Weak passwords
0%

3 subdomains affected

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 lmu-klinikum.de.

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

The LMU Klinikum holds a prominent market position as one of Germany's largest university hospitals, integrating patient care, research, and teaching. Its partnerships with academic and research institutions strengthen its ecosystem. The business model focuses on healthcare delivery, medical research, and education. The website targets patients, visitors, healthcare professionals, and researchers, providing extensive information and services. The presence of multiple social media channels and newsletters indicates active engagement and communication strategies.

Security posture

The website enforces HTTPS and includes CSRF tokens, indicating attention to secure data handling. However, the absence of explicit security headers like Content-Security-Policy and lack of published security or incident response policies suggest room for improvement. No vulnerabilities or exposed sensitive data were detected. The use of Matomo analytics aligns with privacy-conscious tracking. Overall, the security maturity is good but could be enhanced by adopting additional best practices and transparency measures.

Recommendations

  1. Implement and publish a formal security policy and incident response contact information.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection.
  3. Consider publishing a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  4. Maintain and regularly update privacy and cookie policies to ensure ongoing GDPR compliance.
  5. Enhance monitoring and auditing of third-party scripts and libraries to prevent potential vulnerabilities.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
LMU Klinikum
Description
Das LMU Klinikum München zählt zu den größten und forschungsstärksten Universitätsklinika in Deutschland und Europa mit zwei Standorten, Campus Großhadern und Campus Innenstadt. Es betreut jährlich rund 500.000 Patienten in 28 Fachkliniken, 14 Instituten, 6 Abteilungen und 62 interdisziplinären Zentren. Herausragende Einrichtungen sind das Onkologische Spitzenzentrum CCC München, Bayerns größtes Transplantationszentrum TxM, das Deutsche Schwindel- und Gleichgewichtszentrum, das Tropeninstitut und das Center for International Health (CIH).
Key services
Medizinische Versorgung, Forschung, Lehre, Notfallversorgung, Patientenservice
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Matomo Analytics, Leaflet (maps), FontAwesome, CSS, Scrivito CMS
Frameworks
Scrivito
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • CSRF tokens present in meta tags
  • Cookie consent mechanism implemented

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Matomo
Marketing tools
Matomo Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content in German language.
  2. Strong focus on healthcare, research, and education.
  3. Multiple social media channels linked.
  4. Cookie consent and privacy policy implemented.
  5. No visible security policy or incident response contact.
  6. No terms of service page detected.
  7. Use of Matomo analytics indicates privacy-conscious tracking.
  8. No suspicious or malicious content detected.
Technical notes

Notes

The website is built on the Scrivito CMS platform, leveraging JavaScript, CSS, and modern web standards. It uses Matomo for analytics, indicating a preference for privacy-friendly tools. Hosting is on AWS, providing scalable and reliable infrastructure. The site is mobile-optimized with good accessibility and SEO practices. Performance is moderate, with potential for optimization. The technical stack is modern and well-maintained, supporting a professional 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

Reviews of this site

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