Comparison Overview

AbbVie

VS

Novo Nordisk

AbbVie

1 Waukegan Road, None, North Chicago, Illinois, US, 60064
Last Update: 2025-12-11
Between 800 and 849

AbbVie is a global biopharmaceutical company focused on creating medicines and solutions that put impact first — for patients, communities, and our world. We aim to address complex health issues and enhance people's lives through our core therapeutic areas: immunology, oncology, neuroscience, eye care, aesthetics and other areas of unmet need. Learn more about us at www.abbvie.com and review our community guidelines at https://www.abbvie.com/social-media-community-guidelines.html.

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

Novo Nordisk

Novo Alle, Bagsværd, undefined, 2880, DK
Last Update: 2025-12-10
Between 800 and 849

Novo Nordisk is a leading global healthcare company, founded in 1923 and headquartered in Denmark. Our purpose is to drive change to defeat serious chronic diseases, built upon our heritage in diabetes. We do so by pioneering scientific breakthroughs, expanding access to our medicines, and working to prevent and ultimately cure disease. Novo Nordisk employs about 66,000 people in 80 countries and markets its products in around 170 countries. For more information visit novonordisk.com. This page isn’t intended for discussions about products. As such, postings or comments that contain product discussions may be removed. This page is for discussions about Novo Nordisk and its subsidiaries and the initiatives and projects we are involved in. While we welcome everyone to make comments, we reserve the right to remove those that are off-topic, abusive or intended to spam. Any questions specific to products should be made to your healthcare professional. If you wish to file an adverse drug reaction please contact Novo Nordisk’s office in the country you live in: https://www.novonordisk.com/contact-us/find-local-information.html For other customer complaints, please contact us here: https://www.novonordisk.com/contact-us.html Please keep in mind that Novo Nordisk A/S and its subsidiaries work within a highly regulated industry. Therefore, comments that pertain to legal matters or regulatory issues may be removed. Comments contained on this site come from members of the public, and do not necessarily reflect the views of Novo Nordisk A/S. Novo Nordisk A/S does not endorse or approve any content added by other LinkedIn users. Learn more about our privacy disclaimer and community guidelines here: https://www.novonordisk.com/data-privacy-and-user-rights/social-media-privacy-disclaimer.html

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/abbvie.jpeg
AbbVie
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/novo-nordisk.jpeg
Novo Nordisk
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
AbbVie
100%
Compliance Rate
0/4 Standards Verified
Novo Nordisk
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for AbbVie in 2025.

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for Novo Nordisk in 2025.

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

AbbVie cyber incidents detection timeline including parent company and subsidiaries

Incident History — Novo Nordisk (X = Date, Y = Severity)

Novo Nordisk cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/abbvie.jpeg
AbbVie
Incidents

Date Detected: 6/2023
Type:Breach
Attack Vector: Exploitation of Vulnerability
Motivation: Financial gain
Blog: Blog
https://images.rankiteo.com/companyimages/novo-nordisk.jpeg
Novo Nordisk
Incidents

No Incident

FAQ

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

AbbVie company has historically faced a number of disclosed cyber incidents, whereas Novo Nordisk company has not reported any.

In the current year, Novo Nordisk company and AbbVie company have not reported any cyber incidents.

Neither Novo Nordisk company nor AbbVie company has reported experiencing a ransomware attack publicly.

AbbVie company has disclosed at least one data breach, while the other Novo Nordisk company has not reported such incidents publicly.

Neither Novo Nordisk company nor AbbVie company has reported experiencing targeted cyberattacks publicly.

Neither AbbVie company nor Novo Nordisk company has reported experiencing or disclosing vulnerabilities publicly.

Neither AbbVie nor Novo Nordisk holds any compliance certifications.

Neither company holds any compliance certifications.

AbbVie company has more subsidiaries worldwide compared to Novo Nordisk company.

Novo Nordisk company employs more people globally than AbbVie company, reflecting its scale as a Pharmaceutical Manufacturing.

Neither AbbVie nor Novo Nordisk holds SOC 2 Type 1 certification.

Neither AbbVie nor Novo Nordisk holds SOC 2 Type 2 certification.

Neither AbbVie nor Novo Nordisk holds ISO 27001 certification.

Neither AbbVie nor Novo Nordisk holds PCI DSS certification.

Neither AbbVie nor Novo Nordisk holds HIPAA certification.

Neither AbbVie nor Novo Nordisk 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