Comparison Overview

Symantec

VS

IDEMIA

Symantec

1320 Ridder Park Dr, San Jose, California, US, 95131
Last Update: 2025-11-24

Your backstage pass to the most epic cybersecurity solutions on the market for Endpoint, Network, Data and Cloud security. Featuring worldwide (yet local-to-you) partner experts with the chops to deliver enterprise-grade security, whether you're a solo act or a supergroup. Be first in line to experience defense that goes to 11. Hit us up: https://engage.broadcom.com/ESG-contact-us

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 11,988
Subsidiaries: 15
12-month incidents
0
Known data breaches
1
Attack type number
3

IDEMIA

2 place Samuel Champlain, Courbevoie, Ile de France, 92400, FR
Last Update: 2025-11-20
Between 750 and 799

IDEMIA Group unlocks simpler and safer ways to pay, connect, access, identify, travel and protect public places. With its long-standing expertise in biometrics and cryptography, IDEMIA develops technologies of excellence with an impactful, ethical, and socially responsible approach. Every day, IDEMIA secures billions of interactions in the physical and digital worlds. IDEMIA Group brings together three market-leading businesses that enable mission-critical solutions: • IDEMIA Secure Transactions is the leading technology provider who unlocks safer and easier ways to pay and connect. For more information, visit www.idemia.com/business/idemia-secure-transactions • IDEMIA Public Security is a leading global provider of biometric solutions that unlock convenient and secure travel, access, and protection. For more information, visit www.idemia.com/business/idemia-public-security • IDEMIA Smart Identity leverages the power of cryptographic and biometric technologies to unlock a single trusted identity for all. For more information, visit www.idemia.com/business/idemia-smart-identity With a global team of nearly 15,000 employees, IDEMIA Group is trusted by over 600 governmental organizations and more than 2,400 enterprises in over 180 countries. For more information, visit www.idemia.com and follow @IDEMIAGroup on X.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 13,546
Subsidiaries: 2
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/symantec.jpeg
Symantec
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/idemiagroup.jpeg
IDEMIA
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
Symantec
100%
Compliance Rate
0/4 Standards Verified
IDEMIA
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Symantec in 2025.

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for IDEMIA in 2025.

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

Symantec cyber incidents detection timeline including parent company and subsidiaries

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

IDEMIA cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/symantec.jpeg
Symantec
Incidents

Date Detected: 6/2025
Type:Vulnerability
Attack Vector: Unauthenticated Remote Code Execution (RCE)
Blog: Blog

Date Detected: 6/2025
Type:Ransomware
Attack Vector: Zero-Day Exploit (CVE-2025-61882, CVE-2025-21884), Unauthenticated HTTP Requests, Data Exfiltration
Motivation: Financial Gain (Ransomware Extortion)
Blog: Blog

Date Detected: 5/2025
Type:Ransomware
Attack Vector: supply chain attack, third-party compromise (payroll provider partner)
Motivation: financial gain (ransomware)
Blog: Blog
https://images.rankiteo.com/companyimages/idemiagroup.jpeg
IDEMIA
Incidents

No Incident

FAQ

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

Symantec company has historically faced a number of disclosed cyber incidents, whereas IDEMIA company has not reported any.

In the current year, Symantec company has reported more cyber incidents than IDEMIA company.

Symantec company has confirmed experiencing a ransomware attack, while IDEMIA company has not reported such incidents publicly.

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

Neither IDEMIA company nor Symantec company has reported experiencing targeted cyberattacks publicly.

Symantec company has disclosed at least one vulnerability, while IDEMIA company has not reported such incidents publicly.

Neither Symantec nor IDEMIA holds any compliance certifications.

Neither company holds any compliance certifications.

Symantec company has more subsidiaries worldwide compared to IDEMIA company.

IDEMIA company employs more people globally than Symantec company, reflecting its scale as a Software Development.

Neither Symantec nor IDEMIA holds SOC 2 Type 1 certification.

Neither Symantec nor IDEMIA holds SOC 2 Type 2 certification.

Neither Symantec nor IDEMIA holds ISO 27001 certification.

Neither Symantec nor IDEMIA holds PCI DSS certification.

Neither Symantec nor IDEMIA holds HIPAA certification.

Neither Symantec nor IDEMIA 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