Comparison Overview

Astro

VS

Lucidity

Astro

All Asia Broadcast Centre, Technology Park Malaysia, Bukit Jalil, Kuala Lumpur, MY, 57000
Last Update: 2025-11-26

At Astro Malaysia Holdings Berhad 201101004392 (932533-V), we believe in the power of stories to bring people together. For decades, we have been at the heart of Malaysian homes, creating moments of joy, laughter and connection. Today, we are proud to serve 5.3 million homes—reaching 65% of Malaysian TV households—alongside 9,100 businesses, 17.1 million weekly audio listeners on FM and online, and 13.5 million monthly visitors across our digital platforms. For any customer service assistance, feel free to reach out to us via our official Astro Malaysia Facebook or @astroonline on X for the time being. We appreciate your patience and look forward to assisting you there.

NAICS: 71
NAICS Definition: Arts, Entertainment, and Recreation
Employees: 5,547
Subsidiaries: 6
12-month incidents
0
Known data breaches
1
Attack type number
1

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/astro.jpeg
Astro
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
Astro
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)

No incidents recorded for Astro in 2025.

Incidents vs Entertainment Providers Industry Average (This Year)

No incidents recorded for Lucidity in 2025.

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

Astro 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/astro.jpeg
Astro
Incidents

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

No Incident

FAQ

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

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

In the current year, Lucidity company and Astro company have not reported any cyber incidents.

Neither Lucidity company nor Astro company has reported experiencing a ransomware attack publicly.

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

Neither Lucidity company nor Astro company has reported experiencing targeted cyberattacks publicly.

Neither Astro company nor Lucidity company has reported experiencing or disclosing vulnerabilities publicly.

Neither Astro nor Lucidity holds any compliance certifications.

Neither company holds any compliance certifications.

Astro company has more subsidiaries worldwide compared to Lucidity company.

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

Neither Astro nor Lucidity holds SOC 2 Type 1 certification.

Neither Astro nor Lucidity holds SOC 2 Type 2 certification.

Neither Astro nor Lucidity holds ISO 27001 certification.

Neither Astro nor Lucidity holds PCI DSS certification.

Neither Astro nor Lucidity holds HIPAA certification.

Neither Astro nor Lucidity holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

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

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.