Skip to main content

Security report for escp.eu

ESCP Business School · Education · France

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

Security score

64/100

Risk levelMedium

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

ESCP Business School is a prestigious, top-ranked European business school established in 1819, operating a unique multi-campus model across six European cities. It offers a broad portfolio of degree programs including Bachelor, Master in Management, MBA, Executive MBA, specialized Masters, doctoral programs, and executive education. The school targets students, professionals, and corporate clients seeking high-quality business education and leadership development. Technically, the website is built on Drupal 10, hosted on Amazon AWS infrastructure, and integrates numerous modern web technologies and marketing analytics tools. However, the site lacks a valid SSL certificate, serving content over HTTP only, which significantly impacts its security posture. The site employs extensive tracking and advertising scripts, managed via a consent platform, indicating a mature marketing approach but raising privacy considerations. Overall, the website is professionally designed with excellent content quality and user experience but requires urgent security improvements to enable HTTPS and implement security headers to protect user data and enhance trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
0/ 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

7 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 Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

  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 escp.eu

This scan found 21 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
75
Security headers
40
Email security
85
DNS health
85
Network security
100
GDPR outside view
0
Average
64

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 business model focuses on higher education and executive training with a strong European and international presence. ESCP leverages its historical legacy and accreditations (AACSB, EQUIS, EFMD) to maintain a competitive advantage. The school serves a diverse audience including undergraduate and graduate students, executives, and corporate partners. Its revenue streams likely include tuition fees, executive education programs, corporate partnerships, and donations via its foundation. The website reflects a well-established brand with consistent messaging and trust indicators such as alumni networks and media presence. Partnerships with institutions like CCI Paris and integration with platforms like The Conversation enhance its academic and industry relevance.

Security posture

The current security posture is weak due to the absence of HTTPS and SSL certificate, no security headers, and no visible incident response or security policies. While no critical vulnerabilities or malware are detected, the lack of encryption exposes users to potential data interception risks. The site uses a consent management platform and accessibility tools, indicating some compliance awareness, but lacks explicit GDPR or incident response documentation. The extensive use of third-party scripts increases the attack surface and requires vigilant management. Immediate remediation is needed to secure communications and implement best security practices.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement essential security headers including HSTS, Content Security Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish a dedicated security policy and incident response plan with clear contact channels for security issues.
  4. Regularly audit and update third-party scripts and libraries to mitigate vulnerabilities.
  5. Enhance privacy compliance by clearly documenting data retention policies and user data handling practices.

Contact details published on the site

Addresses
Technical notes

Notes

The website uses Drupal 10 CMS with a modern front-end stack including jQuery, Slick Carousel, and Mustache.js for templating. It integrates multiple analytics and marketing tools such as Google Analytics, Facebook Pixel, LinkedIn Insight, TikTok Pixel, and Microsoft Clarity. Hosting is on Amazon AWS with DNS managed by Gandi. Performance is suboptimal with a large page size (~6MB) and slow load time (~26 seconds). Accessibility is addressed via EqualWeb integration and semantic HTML. SEO is supported by proper meta tags and Open Graph data. The absence of SSL and security headers is a significant technical risk. The site is mobile responsive and well-structured but would benefit from performance optimization 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

Reviews of this site

Share your experience with escp.eu. 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 escp.eu.

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.