Comparison Overview
CENTRELEC Maroc
CENTRELEC Maroc
34, Bd Moulay Slimane, Casablanca, 20290, MA
Last Update: 19/03/2026
Avec 33 ans d'expérience, CENTRELEC Maroc, société anonyme au capital de 27.777.700 Dirhams (2,6 Millions €), dont la mission principale est de contribuer à l’efficience des installations de ses clients, en leur offrant des solutions innovantes et conformes à leurs beso...
McKinsey & Company
US
Last Update: 18/09/2026
McKinsey & Company is a global management consulting firm. We are the trusted advisor to the world's leading businesses, governments, and institutions. We work with leading organizations across the private, public and social sectors. Our scale, scope, and knowledge ...
Compliance Ranges Comparison
CENTRELEC Maroc
McKinsey & Company
Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for CENTRELEC Maroc in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
McKinsey & Company has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - CENTRELEC Maroc (X = Date, Y = Severity)
CENTRELEC Maroc cyber incidents detection timeline including parent company and subsidiaries.
Incident History - McKinsey & Company (X = Date, Y = Severity)
McKinsey & Company cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
CENTRELEC Maroc
McKinsey & Company
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.