Comparison Overview

Sony

VS

Lucidity

Sony

1-7-1 Konan,, Minato-ku, Tokyo, None, JP, 108-0075
Last Update: 2025-11-20
Between 750 and 799

Sony’s purpose is simple. We aim to fill the world with emotion, through the power of creativity and technology. We want to be responsible for getting hearts racing, stirring ambition, and putting a smile on the faces of our customers. That challenge, combined with our spirit of innovation, motivates us to create groundbreaking technology, entertainment, and services for people worldwide. Our history as a global brand has been built around employees that all have a passion for touching peoples'​ lives, and pride in pushing beyond the status quo to produce truly extraordinary results. We’re uniquely positioned because we operate in many different industries - from movies and music to video games and electronics. And, with offices around the globe, we benefit from a global workforce that learns and grows together through mutual respect. If you're ready to join a diverse team at an innovation-led company with the power to change lives, then we encourage you to read up on the different Sony group companies and check out our Life page. Then, get in touch, and together, let’s make the world say wow.

NAICS: 71
NAICS Definition: Arts, Entertainment, and Recreation
Employees: 23,628
Subsidiaries: 11
12-month incidents
1
Known data breaches
2
Attack type number
5

Lucidity

Federal District, MX
Last Update: 2025-11-21
Between 750 and 799

Lucidity Agency Models, también conocida como Lucidity, es una agencia de modelos establecida en vancouver, Canada, en 2010 por el conglomerado The Ivan Group. Lucidity maneja en la actualidad a más de 800 modelos de los cinco continentes, convirtiéndola en la agencia de modelos más grande del mundo. Ofrece cobertura internacional con 36 agencias en su red.

NAICS: 71
NAICS Definition: Arts, Entertainment, and Recreation
Employees: 10,001
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/sony.jpeg
Sony
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/lucidity.jpeg
Lucidity
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
Sony
100%
Compliance Rate
0/4 Standards Verified
Lucidity
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Entertainment Providers Industry Average (This Year)

Sony has 28.21% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Entertainment Providers Industry Average (This Year)

No incidents recorded for Lucidity in 2025.

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

Sony cyber incidents detection timeline including parent company and subsidiaries

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

Lucidity cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/sony.jpeg
Sony
Incidents

Date Detected: 3/2025
Type:Breach
Blog: Blog

Date Detected: 09/2023
Type:Data Leak
Motivation: Financial Gain
Blog: Blog

Date Detected: 12/2014
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/lucidity.jpeg
Lucidity
Incidents

No Incident

FAQ

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

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

In the current year, Sony company has reported more cyber incidents than Lucidity company.

Sony company has confirmed experiencing a ransomware attack, while Lucidity company has not reported such incidents publicly.

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

Sony company has reported targeted cyberattacks, while Lucidity company has not reported such incidents publicly.

Sony company has disclosed at least one vulnerability, while Lucidity company has not reported such incidents publicly.

Neither Sony nor Lucidity holds any compliance certifications.

Neither company holds any compliance certifications.

Sony company has more subsidiaries worldwide compared to Lucidity company.

Sony company employs more people globally than Lucidity company, reflecting its scale as a Entertainment Providers.

Neither Sony nor Lucidity holds SOC 2 Type 1 certification.

Neither Sony nor Lucidity holds SOC 2 Type 2 certification.

Neither Sony nor Lucidity holds ISO 27001 certification.

Neither Sony nor Lucidity holds PCI DSS certification.

Neither Sony nor Lucidity holds HIPAA certification.

Neither Sony nor Lucidity 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