Skip to main content

Security report for ccc-muenchen.de

CCC München - Comprehensive Cancer Center · Healthcare · Germany

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

Security score

73/100

Risk levelMedium

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

CCC München is a comprehensive cancer center jointly operated by the Ludwig-Maximilians-Universität München and the Technische Universität München. Established in 2014 and recognized as an oncological excellence center by Deutsche Krebshilfe, it provides advanced cancer patient care, clinical research, and educational events for medical professionals. The website targets patients, healthcare providers, and researchers, offering detailed information about services, events, and collaborations. Technically, the website is built on the Scrivito CMS platform, hosted on AWS infrastructure, and uses modern web technologies including JavaScript, Matomo analytics for privacy-conscious tracking, and Leaflet for interactive maps. The site is mobile-optimized and SEO-friendly, with a moderate performance profile. From a security perspective, the site enforces HTTPS, uses CSRF tokens, and implements cookie consent mechanisms. However, it lacks explicit security headers and published security policies or incident response contacts. No vulnerabilities or exposed sensitive data were detected. Overall, the website is professional, trustworthy, and compliant with GDPR requirements. It effectively supports its healthcare mission but could improve by publishing more detailed security and incident response information.

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 ccc-muenchen.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. 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
67
Security headers
50
Email security
65
DNS health
70
Network security
100
GDPR outside view
83
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

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 ccc-muenchen.de, from OffSeq Breach.

No leaked records found

Breach holds no records for ccc-muenchen.de right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

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

Business context

Business profile

CCC München holds a strong market position as one of Germany's 14 certified oncological excellence centers, leveraging partnerships with major university hospitals LMU and TUM. Its business model focuses on non-profit healthcare delivery and research collaboration in oncology. The center offers patient care, clinical trials, educational webinars, and research projects. The website reflects a mature digital presence with clear branding and trust signals such as certifications and institutional affiliations. The partnership ecosystem includes national and European cancer research networks, enhancing its strategic reach and credibility.

Security posture

The website demonstrates a solid security posture with HTTPS enforcement, CSRF protection, and cookie consent compliance. The use of Matomo analytics aligns with privacy-conscious data collection. However, the absence of explicit security headers (e.g., CSP, X-Frame-Options) and lack of published security policies or vulnerability disclosure mechanisms represent gaps. No incident response contacts or security officer information are provided, which could hinder rapid response to security events. Overall, the security maturity is good but could be enhanced by adopting additional best practices and transparency.

Recommendations

  1. Implement and publish a comprehensive security policy including incident response contacts.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Create and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  4. Include explicit contact information such as company emails and phone numbers for better user trust and support.
  5. Regularly review and update privacy and cookie policies to maintain GDPR compliance and transparency.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
CCC München - Comprehensive Cancer Center
Description
Das CCC München ist das gemeinsame Krebszentrum der beiden Münchner Universitätskliniken (LMU Klinikum und TUM Klinikum Rechts der Isar). Es bündelt Expertise in onkologischer Patientenversorgung und Forschung mit dem Ziel, modernste diagnostische und therapeutische Verfahren anzubieten.
Key services
Oncological patient care, Clinical studies, Patient education and support, Research projects and collaborations, Events and webinars for medical professionals
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Matomo Analytics, Leaflet Maps, FontAwesome
Frameworks
Scrivito CMS
Performance
moderate
Mobile
good
Accessibility
basic
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
Transparency
basic

Site quality

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

Key observations

  1. Website is professionally designed and well-structured.
  2. Content is comprehensive for patients, medical professionals, and researchers.
  3. No visible security or privacy policy documents beyond basic GDPR compliance.
  4. No contact emails or phone numbers explicitly found in the HTML content.
  5. Cookie consent is implemented with clear notice.
  6. No terms of service or vulnerability disclosure policy found.
  7. Use of Matomo analytics indicates privacy-conscious tracking.
  8. No signs of suspicious or malicious content.
Technical notes

Notes

The website uses a modern CMS (Scrivito) and is hosted on AWS, ensuring scalability and reliability. It employs JavaScript frameworks and libraries such as Matomo for analytics and Leaflet for maps, enhancing interactivity and user experience. The site is mobile-optimized and SEO-friendly with appropriate meta tags and structured navigation. Performance is moderate, with potential for optimization. Accessibility features are basic and could be improved. No deprecated or vulnerable libraries were detected. Overall, the technical infrastructure supports the business goals effectively with room for enhancements in accessibility and performance.
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 ccc-muenchen.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 ccc-muenchen.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.