Comparison Overview

Takeda

VS

Teva Pharmaceuticals

Takeda

Tokyo, JP
Last Update: 2025-11-27
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

Teva Pharmaceuticals

124 Dvora hanevi'a, Tel-Aviv, undefined, 6944020, IL
Last Update: 2025-11-27
Between 800 and 849

At Teva, we're proud to be a different kind of global pharmaceutical leader, one that operates across the full spectrum of innovation to reliably deliver medicines to patients worldwide. For over 120 years, our commitment to bettering health has never wavered. Every day, we challenge ourselves to push the boundaries of science, discover life-changing treatments, and deliver quality medicines. If patients have a need, we’re already working to address it. Because here, we are all in for better health. Learn more at www.tevapharm.com. Please note that adverse effects for any of our products should be reported to: [email protected] Product-specific questions should be directed to Teva or Teva Group subsidiaries in your country. Contact details and Teva's Pharmacovigilance Privacy Policy may be found here: http://www.tevapharm.com/contact_us/

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

Compliance Badges Comparison

Security & Compliance Standards Overview

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
https://images.rankiteo.com/companyimages/teva-pharmaceuticals.jpeg
Teva 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
Compliance Summary
Takeda
100%
Compliance Rate
0/4 Standards Verified
Teva Pharmaceuticals
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for Takeda in 2025.

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for Teva Pharmaceuticals in 2025.

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

Takeda cyber incidents detection timeline including parent company and subsidiaries

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

Teva Pharmaceuticals cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/takeda-pharmaceuticals.jpeg
Takeda
Incidents

Date Detected: 1/2024
Type:Breach
Attack Vector: Credential Stuffing
Blog: Blog
https://images.rankiteo.com/companyimages/teva-pharmaceuticals.jpeg
Teva Pharmaceuticals
Incidents

No Incident

FAQ

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

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

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

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

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

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

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

Neither Takeda nor Teva Pharmaceuticals holds any compliance certifications.

Neither company holds any compliance certifications.

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

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

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

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

Neither Takeda nor Teva Pharmaceuticals holds ISO 27001 certification.

Neither Takeda nor Teva Pharmaceuticals holds PCI DSS certification.

Neither Takeda nor Teva Pharmaceuticals holds HIPAA certification.

Neither Takeda nor Teva Pharmaceuticals holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

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