Comparison Overview

Moody's Analytics

VS

KBC Bank & Verzekering

Moody's Analytics

7 World Trade Center, New York, 10007, US
Last Update: 2025-12-15
Between 750 and 799

In an era where risks are multiplying and increasingly interconnected, Moody’s helps organizations make sense of the complexities. By combining data, intelligence, and risk expertise with groundbreaking technologies and a seamless customer experience, we deliver relevant insights on interconnected risk to thousands of organizations worldwide – enabling business and financial leaders to act decisively and thrive amid uncertainty. → Follow Moody’s Corporation for updates about our company, people, careers, and more

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 11,739
Subsidiaries: 5
12-month incidents
0
Known data breaches
0
Attack type number
0

KBC Bank & Verzekering

Havenlaan 2, 1000 Brussel, Brussels, undefined, 1080, BE
Last Update: 2025-12-09
Between 750 and 799

Welkom op de officiële LinkedIn-pagina van KBC! Bekijk onze vacatures op de tab ‘Vacatures’. KBC is een geïntegreerde bank-verzekeraar die zich hoofdzakelijk richt op particulieren en privatebankingcliënten, en op kleine en middelgrote ondernemingen. KBC heeft een leidende positie in zijn thuismarkten in België en Centraal- en Oost-Europa, en is selectief aanwezig in de rest van de wereld.

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 13,115
Subsidiaries: 3
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/moodys-analytics.jpeg
Moody's Analytics
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/kbc-bank-en-verzekering.jpeg
KBC Bank & Verzekering
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
Moody's Analytics
100%
Compliance Rate
0/4 Standards Verified
KBC Bank & Verzekering
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Moody's Analytics in 2025.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for KBC Bank & Verzekering in 2025.

Incident History — Moody's Analytics (X = Date, Y = Severity)

Moody's Analytics cyber incidents detection timeline including parent company and subsidiaries

Incident History — KBC Bank & Verzekering (X = Date, Y = Severity)

KBC Bank & Verzekering cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/moodys-analytics.jpeg
Moody's Analytics
Incidents

No Incident

https://images.rankiteo.com/companyimages/kbc-bank-en-verzekering.jpeg
KBC Bank & Verzekering
Incidents

No Incident

FAQ

Moody's Analytics company demonstrates a stronger AI Cybersecurity Score compared to KBC Bank & Verzekering company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, KBC Bank & Verzekering company has disclosed a higher number of cyber incidents compared to Moody's Analytics company.

In the current year, KBC Bank & Verzekering company and Moody's Analytics company have not reported any cyber incidents.

Neither KBC Bank & Verzekering company nor Moody's Analytics company has reported experiencing a ransomware attack publicly.

Neither KBC Bank & Verzekering company nor Moody's Analytics company has reported experiencing a data breach publicly.

Neither KBC Bank & Verzekering company nor Moody's Analytics company has reported experiencing targeted cyberattacks publicly.

Neither Moody's Analytics company nor KBC Bank & Verzekering company has reported experiencing or disclosing vulnerabilities publicly.

Neither Moody's Analytics nor KBC Bank & Verzekering holds any compliance certifications.

Neither company holds any compliance certifications.

Moody's Analytics company has more subsidiaries worldwide compared to KBC Bank & Verzekering company.

KBC Bank & Verzekering company employs more people globally than Moody's Analytics company, reflecting its scale as a Financial Services.

Neither Moody's Analytics nor KBC Bank & Verzekering holds SOC 2 Type 1 certification.

Neither Moody's Analytics nor KBC Bank & Verzekering holds SOC 2 Type 2 certification.

Neither Moody's Analytics nor KBC Bank & Verzekering holds ISO 27001 certification.

Neither Moody's Analytics nor KBC Bank & Verzekering holds PCI DSS certification.

Neither Moody's Analytics nor KBC Bank & Verzekering holds HIPAA certification.

Neither Moody's Analytics nor KBC Bank & Verzekering holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

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

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

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

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

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

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N