Comparison Overview
BCG on Health Care
BCG on Health Care
200 Pier 4 Boulevard, Boston, 02210, US
Last Update: 02/04/2026
BCG partners with clients across the health care industry in all regions to identify their highest-value opportunities, address their most critical challenges, and transform their enterprises. Our customized and collaborative approach ensures that our clients achieve su...
Jacobs
1999 Bryan Street, Suite 1200, Dallas, 75201, US
Last Update: 30/03/2026
At Jacobs, we're challenging today to reinvent tomorrow – delivering outcomes and solutions for the world's most complex challenges. With a team of approximately 45,000, we provide end-to-end services in advanced manufacturing, cities & places, energy, environmental, li...
Compliance Ranges Comparison
BCG on Health Care
Jacobs
Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for BCG on Health Care in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Jacobs in 2026.
Incident History - BCG on Health Care (X = Date, Y = Severity)
BCG on Health Care cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Jacobs (X = Date, Y = Severity)
Jacobs cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BCG on Health Care
Jacobs
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: *.*.