Comparison Overview
Cobra Perú
Cobra Perú
Calle Amador Merino Reyna, Lima, 0051, PE
Last Update: 02/04/2026
Cobra Perú, pertenece al Grupo Cobra, empresa transnacional española con 77 años de trayectoria internacional dedicada al desarrollo de proyectos de Construcción, energía y servicios industriales. Actualmente tenemos a más de 2,000 personas trabajando con nosotros desa...
Holcim
Grafenauweg 10, Zug, CH, 6300
Last Update: 17/09/2026
Holcim is the leading partner for sustainable construction with net sales of CHF 15.7 billion in 2025, creating value across the built environment from infrastructure and industry to buildings. We have more than 45 000 employees in 43 attractive markets – across Europ...
Compliance Ranges Comparison
Cobra Perú
Holcim
Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Cobra Perú in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Holcim in 2026.
Incident History - Cobra Perú (X = Date, Y = Severity)
Cobra Perú cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Holcim (X = Date, Y = Severity)
Holcim cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Cobra Perú
Holcim
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.