Comparison Overview
MSCI Private Assets
MSCI Private Assets
250 Greenwich Street, New York, New York, US, NY 10007
Last Update: 03/04/2026
MSCI is the premier independent source of private markets intelligence in the world. Investors partner with us to improve performance benchmarking, risk assessment, and capital allocation decisions across public and private markets. With decision-grade data sourced dire...
BNP Paribas CIB
16 Boulevard des Italiens, Paris, France, FR, 75009
Last Update: 28/03/2026
In a changing world, we aim at anticipating transformation and driving your company for success. We are convinced to have the expertise and networks you need to develop your business. BNP Paribas Corporate and Institutional Banking is a leading global financial partner...
Compliance Ranges Comparison
MSCI Private Assets
BNP Paribas CIB
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for MSCI Private Assets in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for BNP Paribas CIB in 2026.
Incident History - MSCI Private Assets (X = Date, Y = Severity)
MSCI Private Assets cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BNP Paribas CIB (X = Date, Y = Severity)
BNP Paribas CIB cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
MSCI Private Assets
BNP Paribas CIB
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.