Comparison Overview

22nd Century Group, Inc.

VS

Regeneron

22nd Century Group, Inc.

500 Seneca Street, Suite 507, Buffalo, NY, US, 14204
Last Update: 2025-11-26
Between 750 and 799

22nd Century Group is a leading agricultural biotechnology company dedicated to improving human health with reduced nicotine tobacco, hemp/cannabis, and hops advanced plant technology. GVB Biopharma is now a 22nd Century company.

NAICS: None
NAICS Definition: Others
Employees: 43
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Regeneron

777 Old Saw Mill River Road, Tarrytown, New York, 10591, US
Last Update: 2025-11-26
Between 800 and 849

At Regeneron we believe that when the right idea finds the right team, powerful change is possible. As we work across our expanding global network to invent, develop and commercialize life-transforming medicines for people with serious diseases, we’re establishing new ways to think about science, manufacturing and commercialization. And new ways to think about health. Connect with us so we can learn more about you, and you can learn more about our biopharmaceutical medicines. And join us, as we build a future we believe in. Please visit www.regeneron.com/social-media-terms for information on how to engage with us on social media. An important note about privacy: Regeneron is committed to your privacy and will not ask for sensitive personal information such as social security number, date of birth or bank account details via email or social media.

NAICS: None
NAICS Definition: Others
Employees: 15,762
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/22nd-century-group.jpeg
22nd Century Group, Inc.
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/regeneron-pharmaceuticals.jpeg
Regeneron
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
22nd Century Group, Inc.
100%
Compliance Rate
0/4 Standards Verified
Regeneron
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Biotechnology Industry Average (This Year)

No incidents recorded for 22nd Century Group, Inc. in 2025.

Incidents vs Biotechnology Industry Average (This Year)

No incidents recorded for Regeneron in 2025.

Incident History — 22nd Century Group, Inc. (X = Date, Y = Severity)

22nd Century Group, Inc. cyber incidents detection timeline including parent company and subsidiaries

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

Regeneron cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/22nd-century-group.jpeg
22nd Century Group, Inc.
Incidents

No Incident

https://images.rankiteo.com/companyimages/regeneron-pharmaceuticals.jpeg
Regeneron
Incidents

No Incident

FAQ

Regeneron company demonstrates a stronger AI Cybersecurity Score compared to 22nd Century Group, Inc. company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Regeneron company has disclosed a higher number of cyber incidents compared to 22nd Century Group, Inc. company.

In the current year, Regeneron company and 22nd Century Group, Inc. company have not reported any cyber incidents.

Neither Regeneron company nor 22nd Century Group, Inc. company has reported experiencing a ransomware attack publicly.

Neither Regeneron company nor 22nd Century Group, Inc. company has reported experiencing a data breach publicly.

Neither Regeneron company nor 22nd Century Group, Inc. company has reported experiencing targeted cyberattacks publicly.

Neither 22nd Century Group, Inc. company nor Regeneron company has reported experiencing or disclosing vulnerabilities publicly.

Neither 22nd Century Group, Inc. nor Regeneron holds any compliance certifications.

Neither company holds any compliance certifications.

Neither 22nd Century Group, Inc. company nor Regeneron company has publicly disclosed detailed information about the number of their subsidiaries.

Regeneron company employs more people globally than 22nd Century Group, Inc. company, reflecting its scale as a Biotechnology.

Neither 22nd Century Group, Inc. nor Regeneron holds SOC 2 Type 1 certification.

Neither 22nd Century Group, Inc. nor Regeneron holds SOC 2 Type 2 certification.

Neither 22nd Century Group, Inc. nor Regeneron holds ISO 27001 certification.

Neither 22nd Century Group, Inc. nor Regeneron holds PCI DSS certification.

Neither 22nd Century Group, Inc. nor Regeneron holds HIPAA certification.

Neither 22nd Century Group, Inc. nor Regeneron 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