Comparison Overview

Hikma Pharmaceuticals

VS

Takeda

Hikma Pharmaceuticals

1 New Burlington Place, London, W1S 2HR, GB
Last Update: 2025-12-11
Between 750 and 799

For almost 50 years, we’ve been creating high-quality medicines and making them accessible to the people who need them. We are a trusted, reliable partner and dependable source of over 800* high-quality generic, specialty and branded pharmaceutical products that hospitals, physicians and pharmacists need to treat their patients across North America, MENA and Europe. We have 29 manufacturing plants, 3 R&D hubs and c9,500 employees worldwide. *As of December 2025 Subscribe to our channel on YouTube https://youtube.com/@hikmapharmaceuticals5668 For all product information and enquiries, please contact us at [email protected]

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

Takeda

Tokyo, JP
Last Update: 2025-12-09
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/hikma-pharmaceuticals.jpeg
Hikma Pharmaceuticals
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
Hikma Pharmaceuticals
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 Hikma Pharmaceuticals in 2025.

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for Takeda in 2025.

Incident History — Hikma Pharmaceuticals (X = Date, Y = Severity)

Hikma Pharmaceuticals 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/hikma-pharmaceuticals.jpeg
Hikma Pharmaceuticals
Incidents

No Incident

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 Hikma Pharmaceuticals company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Takeda company has historically faced a number of disclosed cyber incidents, whereas Hikma Pharmaceuticals company has not reported any.

In the current year, Takeda company and Hikma Pharmaceuticals company have not reported any cyber incidents.

Neither Takeda company nor Hikma Pharmaceuticals company has reported experiencing a ransomware attack publicly.

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

Neither Takeda company nor Hikma Pharmaceuticals company has reported experiencing targeted cyberattacks publicly.

Neither Hikma Pharmaceuticals company nor Takeda company has reported experiencing or disclosing vulnerabilities publicly.

Neither Hikma Pharmaceuticals nor Takeda holds any compliance certifications.

Neither company holds any compliance certifications.

Takeda company has more subsidiaries worldwide compared to Hikma Pharmaceuticals company.

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

Neither Hikma Pharmaceuticals nor Takeda holds SOC 2 Type 1 certification.

Neither Hikma Pharmaceuticals nor Takeda holds SOC 2 Type 2 certification.

Neither Hikma Pharmaceuticals nor Takeda holds ISO 27001 certification.

Neither Hikma Pharmaceuticals nor Takeda holds PCI DSS certification.

Neither Hikma Pharmaceuticals nor Takeda holds HIPAA certification.

Neither Hikma Pharmaceuticals nor Takeda holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

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

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

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

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/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

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

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

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N