Comparison Overview
Pulse Healthcare
Pulse Healthcare
9 Appold Street, London, England, GB, EC2A 2AP
Last Update: 29/03/2026
Pulse is a leading UK and international provider of healthcare staffing; we’re unique in our commitment to delivering the highest quality service through placing the best people. We support NHS Trusts and private health sector providers by placing expert and complia...
Randstad USA
3625 Cumberland Park, Blvd, Atlanta, GA, US, 30339
Last Update: 01/04/2026
Randstad North America, Inc. is a wholly-owned subsidiary of Randstad N.V., the world's largest HR services provider. Driven to become the world's most valued 'working life partner', supporting as many people as possible in realizing their true potential throughout thei...
Compliance Ranges Comparison
Pulse Healthcare
Randstad USA
Benchmark & Cyber Underwriting Signals
Incidents vs Staffing and Recruiting Industry Avg (This Year)
No incidents recorded for Pulse Healthcare in 2026.
Incidents vs Staffing and Recruiting Industry Avg (This Year)
No incidents recorded for Randstad USA in 2026.
Incident History - Pulse Healthcare (X = Date, Y = Severity)
Pulse Healthcare cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Randstad USA (X = Date, Y = Severity)
Randstad USA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Pulse Healthcare
Randstad USA
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: *.*.