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 globally recognized leader in generic and biosimilar medicines, providing a wide range of pharmaceutical products and services. The website reflects a mature enterprise with a strong market position and comprehensive business information targeting healthcare professionals, investors, and patients. Technically, the site leverages modern frameworks such as Next.js and Drupal CMS, hosted on Amazee.io with Fastly CDN integration, indicating a modern digital infrastructure. However, the absence of a valid SSL certificate and lack of TLS protocol support represent significant security vulnerabilities, exposing users to potential risks. Privacy compliance is partially addressed with a comprehensive privacy policy but lacks cookie consent mechanisms. Overall, the domain registration is consistent and trustworthy, supporting the legitimacy of the business. Strategic improvements in security posture and privacy compliance are recommended to enhance trust and protect users.

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.

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 with a focus on generics and biosimilars, serving a global market. Their business model centers on pharmaceutical manufacturing, quality supply, and B2B services. The company demonstrates strong governance and ethical standards, with dedicated sections for corporate assurance, ethics, and compliance. The website content is professional and targeted, supporting investor relations and corporate communications. The mature domain age and strong registrar protections reinforce the company's established market presence. No direct evidence of revenue streams or detailed partnership ecosystems was found in the content, but the site indicates a broad operational scope and strategic market positioning.

Security posture

The website's security posture is currently weak due to the lack of a valid SSL certificate and disabled TLS protocols, which are fundamental for secure web communications. While some security headers like X-XSS-Protection and X-Frame-Options are present, the absence of HTTPS severely undermines overall security. No incident response or vulnerability disclosure information is provided, limiting transparency in security management. The site does not implement cookie consent mechanisms, which may affect GDPR compliance. Immediate remediation of SSL/TLS issues and enhancement of privacy controls are critical to mitigate risks and improve user trust.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS and secure user data transmission.
  2. Enable modern TLS protocols (TLS 1.2 or higher) and disable insecure protocols to strengthen encryption.
  3. Implement a cookie consent banner to comply with privacy regulations and inform users about tracking.
  4. Publish clear incident response and vulnerability disclosure policies to enhance security transparency.
  5. Regularly audit and update security headers and mechanisms to align with best practices.
Technical notes

Notes

The website uses a modern tech stack including Next.js for frontend rendering and Drupal CMS for content management, hosted on Amazee.io with Fastly CDN for performance optimization. The site is mobile-optimized with responsive images and structured navigation. However, performance metrics are not available, and SSL/TLS misconfiguration poses a risk to secure operations. The site architecture supports multilingual content and has a well-organized menu structure. Technical debt appears low, but security misconfigurations represent a significant technical risk that should be prioritized.
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.