Comparison Overview

AstraZeneca

VS

Novartis

AstraZeneca

1 Francis Crick Avenue, Cambridge, CB2 0AA, GB
Last Update: 2025-12-11
Between 800 and 849

We're transforming the future of healthcare by unlocking the power of what science can do for people, society and the planet. For more information, visit www.astrazeneca.com. Community Guidelines: bit.ly/2MgAcio

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

Novartis

Novartis Campus, Basel, Baselstadt, 4002, CH
Last Update: 2025-12-09
Between 800 and 849

Novartis is an innovative medicines company. Every day, working to reimagine medicine to improve and extend people’s lives so that patients, healthcare professionals and societies are empowered in the face of serious disease. Our medicines reach more than 250 million people worldwide. Find out more at https://www.novartis.com See our community guidelines: https://go.novartis.social/3Nboxki

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/astrazeneca.jpeg
AstraZeneca
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/novartis.jpeg
Novartis
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
AstraZeneca
100%
Compliance Rate
0/4 Standards Verified
Novartis
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for AstraZeneca in 2025.

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for Novartis in 2025.

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

AstraZeneca cyber incidents detection timeline including parent company and subsidiaries

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

Novartis cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/astrazeneca.jpeg
AstraZeneca
Incidents

Date Detected: 6/2021
Type:Breach
Attack Vector: Exposed Credentials
Blog: Blog
https://images.rankiteo.com/companyimages/novartis.jpeg
Novartis
Incidents

Date Detected: 06/2022
Type:Cyber Attack
Motivation: Financial Gain
Blog: Blog

FAQ

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

AstraZeneca and Novartis have experienced a similar number of publicly disclosed cyber incidents.

In the current year, Novartis company and AstraZeneca company have not reported any cyber incidents.

Neither Novartis company nor AstraZeneca company has reported experiencing a ransomware attack publicly.

AstraZeneca company has disclosed at least one data breach, while the other Novartis company has not reported such incidents publicly.

Novartis company has reported targeted cyberattacks, while AstraZeneca company has not reported such incidents publicly.

Neither AstraZeneca company nor Novartis company has reported experiencing or disclosing vulnerabilities publicly.

Neither AstraZeneca nor Novartis holds any compliance certifications.

Neither company holds any compliance certifications.

Novartis company has more subsidiaries worldwide compared to AstraZeneca company.

Novartis company employs more people globally than AstraZeneca company, reflecting its scale as a Pharmaceutical Manufacturing.

Neither AstraZeneca nor Novartis holds SOC 2 Type 1 certification.

Neither AstraZeneca nor Novartis holds SOC 2 Type 2 certification.

Neither AstraZeneca nor Novartis holds ISO 27001 certification.

Neither AstraZeneca nor Novartis holds PCI DSS certification.

Neither AstraZeneca nor Novartis holds HIPAA certification.

Neither AstraZeneca nor Novartis 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