Skip to main content

Security report for hecstories.fr

HEC Stories · Media · France

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

Security score

43/100

Risk levelHigh

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

HEC Stories is an online media platform dedicated to the alumni and students of HEC Paris, offering inspiring stories, interviews, and insights on business, sustainable development, and entrepreneurship. The website serves a niche audience connected to the HEC ecosystem and provides content in multiple formats including articles, podcasts, videos, and newsletters. The business model appears to be based on content publishing with subscription and advertising revenue streams. Technically, the site is built on WordPress with WooCommerce and uses popular plugins such as Yoast SEO and Cookiebot for SEO and privacy compliance. Hosting is provided by OVH, a reputable French hosting provider. However, a critical security weakness is the lack of a valid SSL certificate and proper HTTPS support, which undermines user trust and data security. The site implements cookie consent mechanisms and integrates Google Analytics for user tracking, indicating moderate privacy compliance. Social media presence is strong, enhancing community engagement and trust. Overall, the site is professionally designed with good content quality but requires urgent security improvements to meet modern standards.

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 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 hecstories.fr

This scan found 18 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
50
Security headers
30
Email security
50
DNS health
85
Network security
40
GDPR outside view
0
Average
43

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

HEC Stories occupies a specialized media niche targeting the HEC Paris community and business professionals interested in innovation and entrepreneurship. Its competitive advantage lies in its focused content and strong alumni network connections. The platform leverages multiple content channels to engage its audience, including articles, podcasts, and videos, supported by newsletter subscriptions. Partnerships with HEC Alumni and related entities strengthen its ecosystem. The business model likely combines advertising, subscriptions, and event promotions. Growth indicators include active content updates and multimedia integration. The site’s strategic positioning as a trusted source for HEC-related news and stories supports its market presence, though expansion opportunities exist through enhanced digital security and broader marketing efforts.

Security posture

The website’s security posture is currently weak due to the absence of a valid SSL certificate and lack of HTTPS support, exposing users to potential data interception risks. While some security headers like HSTS are present, they are ineffective without proper TLS configuration. No advanced security policies or vulnerability disclosures are published, and no incident response contacts are available. The site uses standard WordPress plugins, which require regular updates to mitigate vulnerabilities. Cookie consent is managed appropriately, but the lack of secure transport undermines privacy protections. Overall, the security maturity level is low, posing business risks related to user trust, compliance, and data protection.

Recommendations

  1. Install and configure a valid SSL/TLS certificate to enable HTTPS across the entire site immediately.
  2. Enable modern TLS protocols (TLS 1.2 or TLS 1.3) and strong cipher suites to secure communications.
  3. Implement additional security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  4. Publish a clear security policy and vulnerability disclosure document to enhance transparency and trust.
  5. Regularly update WordPress core, themes, and plugins to reduce exposure to known vulnerabilities.
Technical notes

Notes

The website is built on a WordPress CMS platform using the Fusion theme and WooCommerce for e-commerce capabilities. It integrates several plugins including Yoast SEO for search engine optimization and Cookiebot for cookie consent management. The site uses jQuery and Google Analytics for frontend interactivity and analytics tracking. Hosting is provided by OVH, a major French hosting provider. Performance metrics are not available, but the site structure and assets suggest moderate loading speeds. Mobile optimization is good with responsive design elements. Accessibility features are basic but present. The lack of HTTPS and modern TLS support is a significant technical deficiency that impacts security and user trust. SEO is well managed with proper meta tags and structured data in JSON-LD format. Overall, the technical infrastructure is standard for a content-driven WordPress site but requires security upgrades and performance monitoring.
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 hecstories.fr. 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 hecstories.fr.

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.