Comparison Overview

Health Secure

VS

Takeda

Health Secure

Last Update: 2025-12-17

Spanning more than a decade, Health Secure has been reaching out to the world, enabling patient-care through world-class pharmaceutical manufacturing of its own brands, as well as for other companies. State-of-the-art facilities and highly admired expertise in manufacturing makes Health Secure one of the most sought after contract-manufacturers from India. This expertise in manufacturing provides a sound backing to the strong supply and distribution network, the company has in india for its own brands.

NAICS: 3254
NAICS Definition: Pharmaceutical and Medicine Manufacturing
Employees: 14
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
1

Takeda

Tokyo, JP
Last Update: 2025-12-17
Between 800 and 849

We strive to transform lives. While the science we advance is constantly evolving, our core purpose is enduring. For more than two centuries, our values have guided us to do what’s right for patients and for society. We know that changing lives requires us to do things differently. We start by listening to and addressing what really matters to patients, the people who love them, and those in the healthcare system who provide care. And that’s what inspires us all to be bold, push boundaries and set new standards that open up greater opportunities. Read our community guidelines: https://takeda.info/communityguidelines

NAICS: 3254
NAICS Definition: Pharmaceutical and Medicine Manufacturing
Employees: 33,864
Subsidiaries: 6
12-month incidents
0
Known data breaches
1
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/healthsecure.jpeg
Health Secure
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/takeda-pharmaceuticals.jpeg
Takeda
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Health Secure
100%
Compliance Rate
0/4 Standards Verified
Takeda
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for Health Secure in 2025.

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for Takeda in 2025.

Incident History — Health Secure (X = Date, Y = Severity)

Health Secure cyber incidents detection timeline including parent company and subsidiaries

Incident History — Takeda (X = Date, Y = Severity)

Takeda cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/healthsecure.jpeg
Health Secure
Incidents

Date Detected: 04/2023
Type:Ransomware
Motivation: Financial Gain
Blog: Blog
https://images.rankiteo.com/companyimages/takeda-pharmaceuticals.jpeg
Takeda
Incidents

Date Detected: 1/2024
Type:Breach
Attack Vector: Credential Stuffing
Blog: Blog

FAQ

Takeda company demonstrates a stronger AI Cybersecurity Score compared to Health Secure company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Health Secure and Takeda have experienced a similar number of publicly disclosed cyber incidents.

In the current year, Takeda company and Health Secure company have not reported any cyber incidents.

Health Secure company has confirmed experiencing a ransomware attack, while Takeda company has not reported such incidents publicly.

Takeda company has disclosed at least one data breach, while Health Secure company has not reported such incidents publicly.

Neither Takeda company nor Health Secure company has reported experiencing targeted cyberattacks publicly.

Neither Health Secure company nor Takeda company has reported experiencing or disclosing vulnerabilities publicly.

Neither Health Secure nor Takeda holds any compliance certifications.

Neither company holds any compliance certifications.

Takeda company has more subsidiaries worldwide compared to Health Secure company.

Takeda company employs more people globally than Health Secure company, reflecting its scale as a Pharmaceutical Manufacturing.

Neither Health Secure nor Takeda holds SOC 2 Type 1 certification.

Neither Health Secure nor Takeda holds SOC 2 Type 2 certification.

Neither Health Secure nor Takeda holds ISO 27001 certification.

Neither Health Secure nor Takeda holds PCI DSS certification.

Neither Health Secure nor Takeda holds HIPAA certification.

Neither Health Secure nor Takeda holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

httparty is an API tool. In versions 0.23.2 and prior, httparty is vulnerable to SSRF. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers. This issue has been patched via commit 0529bcd.

Risk Information
cvss4
Base: 8.8
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. In versions 0.15.2 and prior, an RCE vulnerability exists in useMarkdown.ts, where the markdown-it-mermaid plugin is initialized with securityLevel: 'loose'. This configuration explicitly permits the rendering of HTML tags within Mermaid diagram nodes. This issue has not been patched at time of publication.

Risk Information
cvss3
Base: 9.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Description

continuwuity is a Matrix homeserver written in Rust. Prior to version 0.5.0, this vulnerability allows a remote, unauthenticated attacker to force the target server to cryptographically sign arbitrary membership events. The flaw exists because the server fails to validate the origin of a signing request, provided the event's state_key is a valid user ID belonging to the target server. This issue has been patched in version 0.5.0. A workaround for this issue involves blocking access to the PUT /_matrix/federation/v2/invite/{roomId}/{eventId} endpoint using the reverse proxy.

Risk Information
cvss4
Base: 9.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3

Risk Information
cvss3
Base: 8.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Description

LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form dictionaries. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in versions 0.3.81 and 1.2.5.

Risk Information
cvss3
Base: 9.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N