Skip to main content

Security report for sandoz.com

Sandoz · Healthcare · N/a

Medium risk. 6 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

51/100

Risk levelMedium

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

Sandoz is a global leader in generic and biosimilar medicines, providing affordable healthcare solutions worldwide. The website reflects a mature enterprise with comprehensive information on its business operations, corporate governance, and investor relations. The technical infrastructure leverages modern web technologies including React, Next.js, and Drupal CMS, hosted on a reputable platform with CDN support. However, the website suffers from a critical security issue due to the absence of a valid SSL certificate, resulting in no HTTPS protection. This significantly impacts the security posture and user trust. Privacy compliance is well addressed with a comprehensive privacy policy and cookie consent mechanism. Overall, the site is professional and content-rich but requires urgent security improvements to protect user data and enhance trust.

Scanned

This is an earlier scan of sandoz.com. View the latest report

NIS2 and GDPR posture

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

6 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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • 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. 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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. 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 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 sandoz.com

This scan found 15 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
0
Security headers
55
Email security
50
DNS health
85
Network security
100
GDPR outside view
15
Average
51

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 sandoz.com, from OffSeq Breach.

Total records
237
Employees
0
Customers
23
Third parties
214
Weak passwords
0%

6 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 sandoz.com.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)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

Sandoz operates in the healthcare sector focusing on generic and biosimilar pharmaceuticals. It targets healthcare professionals, investors, and patients, offering a broad portfolio of products and services including manufacturing and B2B solutions. The company maintains strong corporate governance and compliance frameworks, supported by ISO 27001 certification. The website's content and structure indicate a large enterprise with a global market presence and a commitment to sustainability and ethical practices. The absence of direct contact emails or phone numbers suggests a controlled communication approach, likely to ensure compliance and security.

Security posture

The current security posture is weak due to the lack of a valid SSL certificate and absence of HTTPS enforcement. Although the site implements a Content-Security-Policy and shows no known SSL vulnerabilities, the missing SSL certificate is a critical flaw that exposes users to potential data interception risks. No HSTS or other common security headers are present, and there is no evidence of a vulnerability disclosure program or security.txt file. Privacy policies and compliance measures are strong, but the technical security controls need immediate enhancement to meet industry standards and protect sensitive information.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload options.
  3. Implement additional security headers such as X-Frame-Options and X-Content-Type-Options.
  4. Establish a vulnerability disclosure policy and publish a security.txt file.
  5. Regularly audit and update all security configurations and certificates to maintain compliance and trust.
Technical notes

Notes

The website uses a modern technology stack including React and Next.js for frontend rendering, with Drupal as the backend CMS. Hosting is provided by Amazee.io with Fastly CDN for content delivery. Despite the advanced stack, the site suffers from slow performance with a high load time (~22.5 seconds) and large page size (~1.8 MB). Mobile optimization and accessibility are good, and SEO practices are well implemented with proper meta tags and structured navigation. There is an opportunity to improve performance by optimizing resources and enabling caching mechanisms. Security configurations require urgent attention to prevent potential business risks.
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

Earlier scans of this domain

  1. 78/100 −3Low25 findingsView report
  2. 81/100 +30Low21 findingsView report
  3. 51/100Medium23 findingsView report
Reviews of this site

Share your experience with sandoz.com. 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 sandoz.com.

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.

sandoz.com security report: 51/100, medium risk | Guard