Skip to main content

Security report for sjm.com

Abbott · Healthcare · United States

Medium risk. 4 critical or high findings in GDPR outside view and SSL/TLS.

Security score

60/100

Risk levelMedium

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

Abbott Cardiovascular's website serves as a comprehensive corporate portal providing detailed information on cardiac and vascular medical devices and therapies. The site targets healthcare professionals and patients, offering product details, educational resources, and patient support. The business is positioned as a global leader in healthcare technology, supported by consistent branding and professional content. Technically, the site leverages Adobe Experience Manager CMS, Amazon CloudFront hosting, and integrates advanced analytics and consent management tools. However, the absence of a valid SSL certificate and enabled TLS protocols significantly undermines the security posture, despite well-configured security headers and privacy policies. Overall, the site is professional and trustworthy but requires urgent remediation of SSL/TLS issues to ensure secure user interactions and compliance.

Scanned

NIS2 and GDPR posture

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

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

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

Keep watching sjm.com

This scan found 16 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
0
Security headers
85
Email security
70
DNS health
85
Network security
100
GDPR outside view
18
Average
60

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

Total records
14,420
Employees
5
Customers
398
Third parties
14,017
Weak passwords
1%

Latest record dated 2026-06-14 · 71 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 sjm.com.

Select it in the checkout above.

Masked preview

  • –left.sjm.com2026-06-14
  • –left.sjm.com2026-05-25
  • –left.sjm.com2025-11-13
  • –left.sjm.com2025-07-19
  • –left.sjm.com2025-04-14

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

Abbott Cardiovascular operates within the healthcare sector, focusing on cardiovascular medical devices and solutions. The website reflects an enterprise-level organization with a global footprint, supported by a parent company Abbott Laboratories. The business model centers on product innovation, healthcare professional education, and patient engagement. The site integrates partner services for consent management and analytics, indicating a mature digital ecosystem. The absence of direct contact emails or phone numbers suggests a preference for controlled communication channels via contact forms. The company maintains a strong social media presence, enhancing brand visibility and stakeholder engagement.

Security posture

The website demonstrates partial adherence to security best practices, including the implementation of key HTTP security headers such as Content Security Policy, X-Frame-Options, and HSTS. However, the critical failure to deploy a valid SSL certificate and enable modern TLS protocols exposes the site to significant risks, including data interception and user trust erosion. The lack of OCSP stapling and session resumption further detracts from security and performance. No evidence of incident response policies or vulnerability disclosure mechanisms was found, indicating potential gaps in security governance. Immediate action is recommended to install and maintain proper SSL/TLS configurations and enhance incident response readiness.

Recommendations

  1. Install a valid SSL certificate and enable TLS 1.2 or TLS 1.3 protocols to secure all communications.
  2. Enable OCSP stapling and session resumption to improve security and user experience.
  3. Implement and publicize a vulnerability disclosure policy and incident response contact channels.
  4. Regularly audit and update third-party scripts and libraries to mitigate vulnerabilities.
  5. Enhance transparency by providing direct contact information for security and privacy inquiries.
Technical notes

Notes

The website is built on Adobe Experience Manager CMS and hosted on Amazon CloudFront, indicating a robust and scalable infrastructure. It employs modern JavaScript libraries and integrates third-party services for analytics (New Relic) and consent management (TrustArc). The site is mobile-optimized with good accessibility and SEO practices. However, performance metrics are unavailable, and the lack of SSL/TLS undermines secure data transmission. The technical stack is mature but requires updates to security configurations to align with industry standards and ensure compliance.
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 sjm.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 sjm.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.