Comparison Overview
Planned Parenthood Northern California
Planned Parenthood Northern California
2185 Pacheco Street, Concord, 94520, US
Last Update: 09/03/2026
Planned Parenthood Northern California is an equal opportunity employer and works affirmatively to include diversity among its staff and does not discriminate on the basis of race, color, ethnicity, religion, sex/gender identity, sexual orientation, national origin, age...
Philips
Amstelplein 2, Amsterdam, 1096 BC, NL
Last Update: 05/04/2026
Over the past decade we have transformed into a focused leader in health technology. At Philips, our purpose is to improve people’s health and well-being through meaningful innovation. We aim to improve 2.5 billion lives per year by 2030, including 400 million in under...
Compliance Ranges Comparison
Planned Parenthood Northern California
Philips
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Planned Parenthood Northern California in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Philips has 4.76% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Planned Parenthood Northern California (X = Date, Y = Severity)
Planned Parenthood Northern California cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Philips (X = Date, Y = Severity)
Philips cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Planned Parenthood Northern California
Philips
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: *.*.