Comparison Overview

Zydus Group

VS

EMS

Zydus Group

Zydus Corporate Park, Ahmedabad, Gujarat, 382481, IN
Last Update: 2025-12-10
Between 750 and 799

The Zydus Group with an overarching purpose of empowering people with freedom to live healthier and more fulfilled lives, is an innovative, global life-sciences company that discovers, develops, manufactures, and markets a broad range of healthcare therapies. The group employs over 27000 people worldwide and is driven by its mission to unlock new possibilities in life-sciences through quality healthcare solutions that impact lives. The group aspires to transform lives through pathbreaking discoveries.

NAICS: 325
NAICS Definition:
Employees: 18,313
Subsidiaries: 2
12-month incidents
0
Known data breaches
0
Attack type number
0

EMS

Rodovia Jorn. Francisco Aguirre Proenca, Hortolandia, SP, 13186-525, BR
Last Update: 2025-12-09
Between 750 and 799

EMS is the leading pharmaceutical company in Brazil. Established since 45 years and with 100% national capital, the company has two industrial plants strategically placed in São Bernardo do Campo and Hortolândia, in the state of São Paulo. With a work based on daring, simplicity, excellence and responsibility, the company reached the top of the ranking, but not by chance. The strength of the brand belongs on the constant investments in structure and research, in the continuous expansion of the products line and in the pioneer attitude. As the first Brazilian laboratory to export medicine products to Europe and to produce, in the country, medicine products in fractioned packing and generics, EMS is definitively reinventing the pharmaceutical market.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/zyduscadila.jpeg
Zydus Group
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/ems.jpeg
EMS
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
Zydus Group
100%
Compliance Rate
0/4 Standards Verified
EMS
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for Zydus Group in 2025.

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for EMS in 2025.

Incident History — Zydus Group (X = Date, Y = Severity)

Zydus Group cyber incidents detection timeline including parent company and subsidiaries

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

EMS cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/zyduscadila.jpeg
Zydus Group
Incidents

No Incident

https://images.rankiteo.com/companyimages/ems.jpeg
EMS
Incidents

Date Detected: 12/2017
Type:Ransomware
Motivation: Financial
Blog: Blog

FAQ

Zydus Group company demonstrates a stronger AI Cybersecurity Score compared to EMS company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

EMS company has historically faced a number of disclosed cyber incidents, whereas Zydus Group company has not reported any.

In the current year, EMS company and Zydus Group company have not reported any cyber incidents.

EMS company has confirmed experiencing a ransomware attack, while Zydus Group company has not reported such incidents publicly.

Neither EMS company nor Zydus Group company has reported experiencing a data breach publicly.

Neither EMS company nor Zydus Group company has reported experiencing targeted cyberattacks publicly.

Neither Zydus Group company nor EMS company has reported experiencing or disclosing vulnerabilities publicly.

Neither Zydus Group nor EMS holds any compliance certifications.

Neither company holds any compliance certifications.

Zydus Group company has more subsidiaries worldwide compared to EMS company.

Zydus Group company employs more people globally than EMS company, reflecting its scale as a Pharmaceutical Manufacturing.

Neither Zydus Group nor EMS holds SOC 2 Type 1 certification.

Neither Zydus Group nor EMS holds SOC 2 Type 2 certification.

Neither Zydus Group nor EMS holds ISO 27001 certification.

Neither Zydus Group nor EMS holds PCI DSS certification.

Neither Zydus Group nor EMS holds HIPAA certification.

Neither Zydus Group nor EMS 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