Skip to main content

Security report for roche.pl

Roche Polska · Healthcare · Poland

Medium risk. 5 critical or high findings in GDPR outside view, Security headers and 1 other check.

Security score

71/100

Risk levelMedium

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

Roche Polska is a leading healthcare company in Poland, providing innovative solutions in health protection. The website reflects a professional and consistent brand image aligned with Roche's global identity. The target audience includes healthcare professionals and patients within Poland. Technically, the site is built using modern frameworks such as Gatsby and React, offering good mobile optimization and accessibility. However, there is a lack of visible privacy and cookie policies, security headers, and explicit contact information, which are areas for improvement. The security posture is moderate with no detected blocking or WAF interference, but the absence of security best practices lowers the overall security score. Overall, the website is credible and trustworthy but could enhance compliance and security transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
33/ 100 · High
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"

  3. 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 SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching roche.pl

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
75
Security headers
60
Email security
70
DNS health
85
Network security
100
GDPR outside view
33
Average
71

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

Roche Polska operates in the healthcare sector as an essential entity under the Roche parent company. It holds a strong market position as a leader in innovative healthcare solutions in Poland. The business model focuses on delivering pharmaceutical and diagnostic products. The website content is relevant and professionally presented, targeting healthcare professionals and patients. There is no evidence of direct e-commerce or affiliate marketing. The company maintains a consistent branding strategy and leverages social media presence, notably on Twitter. The lack of WHOIS data is typical for privacy protection and does not detract from the company's legitimacy. No suspicious domains or partners were identified.

Security posture

The website uses HTTPS, but no explicit security headers were detected in the provided content. There are no visible forms or input fields, reducing attack surface, but also no published security or incident response policies. No vulnerability disclosure or security.txt files were found. The absence of privacy and cookie policies indicates potential compliance gaps with GDPR. No contact channels for security incidents are provided. Overall, the security posture is moderate but could be significantly improved by implementing security headers, publishing policies, and providing clear contact information for incident response.

Recommendations

  1. Implement comprehensive privacy and cookie policies with clear GDPR compliance statements and consent mechanisms.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-XSS-Protection to enhance security posture.
  3. Publish a security policy and incident response contact information to improve transparency and readiness.
  4. Include verified company contact emails and phone numbers to enhance trust and user support.
  5. Regularly audit and update technical infrastructure to maintain performance, security, and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Roche Polska
Description
Roche Polska jest liderem wśród firm dostarczających innowacyjne rozwiązania w obszarze ochrony zdrowia.
Key services
Innovative healthcare solutions, Pharmaceutical products, Diagnostics
Content quality
good
Branding
consistent

Technology

Stack
React, Gatsby, CSS, JavaScript
Frameworks
Gatsby
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
50/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

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-branded consistent with Roche corporate identity.
  2. Content is in Polish targeting healthcare sector in Poland.
  3. No WHOIS data available from NASK registry, indicating privacy protection or registry restrictions.
  4. No explicit privacy, cookie, or terms of service policies found in the provided HTML content.
  5. No contact emails or phone numbers explicitly found in the provided content.
  6. No security headers or explicit security policies detected in the HTML content.
  7. No forms detected in the provided HTML snippet.
  8. No analytics or tracking scripts explicitly detected in the provided HTML snippet.
  9. No advertising or affiliate marketing detected.
  10. No adult or questionable content detected.
Technical notes

Notes

The website is built on a modern React-based framework (Gatsby), indicating a contemporary technical infrastructure. CSS and JavaScript are used extensively for styling and interactivity. The site appears mobile-optimized and accessible with proper semantic HTML elements. Performance is moderate, with potential for optimization in loading times and resource management. No CMS or hosting provider details were identified from the content. The absence of analytics or tracking scripts suggests minimal user tracking, which aligns with privacy best practices but may limit marketing insights. Technical debt appears low, but security and compliance features need enhancement.
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 roche.pl. 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 roche.pl.

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.