Comparison Overview

Health Secure

VS

Novo Nordisk

Health Secure

Last Update: 2025-12-17

Spanning more than a decade, Health Secure has been reaching out to the world, enabling patient-care through world-class pharmaceutical manufacturing of its own brands, as well as for other companies. State-of-the-art facilities and highly admired expertise in manufacturing makes Health Secure one of the most sought after contract-manufacturers from India. This expertise in manufacturing provides a sound backing to the strong supply and distribution network, the company has in india for its own brands.

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

Novo Nordisk

Novo Alle, Bagsværd, undefined, 2880, DK
Last Update: 2025-12-18
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/healthsecure.jpeg
Health Secure
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
Health Secure
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 Health Secure in 2025.

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for Novo Nordisk in 2025.

Incident History — Health Secure (X = Date, Y = Severity)

Health Secure 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/healthsecure.jpeg
Health Secure
Incidents

Date Detected: 04/2023
Type:Ransomware
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 Health Secure company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Health Secure 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 Health Secure company have not reported any cyber incidents.

Health Secure company has confirmed experiencing a ransomware attack, while Novo Nordisk company has not reported such incidents publicly.

Neither Novo Nordisk company nor Health Secure company has reported experiencing a data breach publicly.

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

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

Neither Health Secure nor Novo Nordisk holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Health Secure company nor Novo Nordisk company has publicly disclosed detailed information about the number of their subsidiaries.

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

Neither Health Secure nor Novo Nordisk holds SOC 2 Type 1 certification.

Neither Health Secure nor Novo Nordisk holds SOC 2 Type 2 certification.

Neither Health Secure nor Novo Nordisk holds ISO 27001 certification.

Neither Health Secure nor Novo Nordisk holds PCI DSS certification.

Neither Health Secure nor Novo Nordisk holds HIPAA certification.

Neither Health Secure nor Novo Nordisk holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

httparty is an API tool. In versions 0.23.2 and prior, httparty is vulnerable to SSRF. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers. This issue has been patched via commit 0529bcd.

Risk Information
cvss4
Base: 8.8
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/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

5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. In versions 0.15.2 and prior, an RCE vulnerability exists in useMarkdown.ts, where the markdown-it-mermaid plugin is initialized with securityLevel: 'loose'. This configuration explicitly permits the rendering of HTML tags within Mermaid diagram nodes. This issue has not been patched at time of publication.

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

continuwuity is a Matrix homeserver written in Rust. Prior to version 0.5.0, this vulnerability allows a remote, unauthenticated attacker to force the target server to cryptographically sign arbitrary membership events. The flaw exists because the server fails to validate the origin of a signing request, provided the event's state_key is a valid user ID belonging to the target server. This issue has been patched in version 0.5.0. A workaround for this issue involves blocking access to the PUT /_matrix/federation/v2/invite/{roomId}/{eventId} endpoint using the reverse proxy.

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

LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3

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

LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form dictionaries. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in versions 0.3.81 and 1.2.5.

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