Comparison Overview

I95 BUSINESS

VS

Leya

I95 BUSINESS

1242 Paper Mill Road, Cockeysville, MD, 21030, US
Last Update: 2025-11-22
Between 750 and 799

I95 BUSINESS/Baltimore - We tell stories successful businesses and the people who run them. We write about our vibrant economically diverse area, supported by a wide range of businesses, from large to small. Business services, entrepreneurial ventures, manufacturing, education, health and healthcare, financial services, wealth management and insurance, defense, gaming companies and lots of innovators. I95 BUSINESS is delivered by direct mail and digital subscriptions to well-educated, well-employed, regional and local decision makers, including C-Level executives, presidents, owners, business development, human resources, restaurants, hotels and more. I95 BUSINESS is published by Stone House Media Group, a local, woman-owned publishing company. Visit the website to subscribe.

NAICS: 511
NAICS Definition:
Employees: 11
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Leya

Rua Cidade de Cordova 2, Amadora, 2610-038, PT
Last Update: 2025-11-21
Between 750 and 799

A LeYa nasceu em 2008 como grupo editorial no qual se integram algumas das mais prestigiadas editoras de língua portuguesa. Líder do mercado editorial português, angolano e moçambicano, a LeYa está também presente no Brasil onde atua no setor do ensino a distância / e-learning. A força das marcas que integram a LeYa, os autores com que temos o privilégio de trabalhar e a qualidade do que, em conjunto, criamos fazem da LeYa uma empresa forte e coesa nos seus objetivos gerais e diversificada nos seus programas editoriais, bem como nas suas atividades na área da Educação. Graças à integração de empresas e de profissionais profundamente enraizados nos respetivos mercados, a LeYa conta hoje com um capital humano extraordinário e detentor de um sólido e diversificado know-how nos meios Editorial, Educativo e Tecnológico. Nos mercados onde opera, a LeYa apresenta-se com objetivos concretos de vir a ser protagonista, nomeadamente pelo papel que desempenha no mundo de língua portuguesa.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 581
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/i95-business.jpeg
I95 BUSINESS
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/grupo-leya.jpeg
Leya
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
I95 BUSINESS
100%
Compliance Rate
0/4 Standards Verified
Leya
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for I95 BUSINESS in 2025.

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for Leya in 2025.

Incident History — I95 BUSINESS (X = Date, Y = Severity)

I95 BUSINESS cyber incidents detection timeline including parent company and subsidiaries

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

Leya cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/i95-business.jpeg
I95 BUSINESS
Incidents

No Incident

https://images.rankiteo.com/companyimages/grupo-leya.jpeg
Leya
Incidents

No Incident

FAQ

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

Historically, Leya company has disclosed a higher number of cyber incidents compared to I95 BUSINESS company.

In the current year, Leya company and I95 BUSINESS company have not reported any cyber incidents.

Neither Leya company nor I95 BUSINESS company has reported experiencing a ransomware attack publicly.

Neither Leya company nor I95 BUSINESS company has reported experiencing a data breach publicly.

Neither Leya company nor I95 BUSINESS company has reported experiencing targeted cyberattacks publicly.

Neither I95 BUSINESS company nor Leya company has reported experiencing or disclosing vulnerabilities publicly.

Neither I95 BUSINESS nor Leya holds any compliance certifications.

Neither company holds any compliance certifications.

Neither I95 BUSINESS company nor Leya company has publicly disclosed detailed information about the number of their subsidiaries.

Leya company employs more people globally than I95 BUSINESS company, reflecting its scale as a Book and Periodical Publishing.

Neither I95 BUSINESS nor Leya holds SOC 2 Type 1 certification.

Neither I95 BUSINESS nor Leya holds SOC 2 Type 2 certification.

Neither I95 BUSINESS nor Leya holds ISO 27001 certification.

Neither I95 BUSINESS nor Leya holds PCI DSS certification.

Neither I95 BUSINESS nor Leya holds HIPAA certification.

Neither I95 BUSINESS nor Leya 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.