Comparison Overview
Kadlec | PS&D Provider Recruitment
Kadlec | PS&D Provider Recruitment
N/A
Last Update: 25/03/2026
Provider Solutions & Development is Kadlec’s exclusive recruiting partner for physician and advanced practice clinician roles. Kadlec includes Kadlec Regional Medical Center in Richland, Washington, and Kadlec Clinic, a network of primary and specialty care clinics in ...
Philips
Amstelplein 2, Amsterdam, 1096 BC, NL
Last Update: 14/08/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
Kadlec | PS&D Provider Recruitment
Philips
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Kadlec | PS&D Provider Recruitment in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Philips has 191.26% more incidents than the average of all companies with at least one recorded incident.
Incident History - Kadlec | PS&D Provider Recruitment (X = Date, Y = Severity)
Kadlec | PS&D Provider Recruitment 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
Kadlec | PS&D Provider Recruitment
Philips
FAQ
Latest Global CVEs
OpenStack Ironic through 38.0.0 may send a username and password to an unexpected remote host when Image Service is configured for HTTP(S) Basic Authentication.
An issue was discovered in OpenStack Keystone before 29.0.3. Tokens obtained via delegated authentication methods (EC2 credentials, application credentials, OAuth1 access tokens, and trusts) are not blocked from creating, modifying, or deleting credentials via the /v3/credentials API. EC2-derived tokens can additionally read credential blobs, exposing TOTP MFA seeds and other secrets. Also, PATCH /v3/credentials does not validate the requested post-update project_id, allowing any delegated token to move a credential to an unauthorized project. All Keystone deployments using delegated authentication are affected.
The administrative password is hashed using a comparatively weak, fast algorithm for the credential store backing one authentication path, and the file containing that hash is written with permissions allowing it to be read by any local user. This is inconsistent with a separate, stronger hashing algorithm used for the same password on another authentication path. A party able to read this file, including a local user or a party with access to a configuration backup, could feasibly recover the underlying password through offline computation, compromising the administrative credential across every path that accepts it.
An example environment-configuration file for a bundled inventory-management component ships with a fixed, publicly-known administrative password. A deployment that copies this example file into active configuration without running the setup routine that regenerates credentials will expose that component's administrative interface to anyone aware of the default value.
A prior update that raised a bundled HTTP client library to a version remediating known vulnerabilities was later reverted, reintroducing the earlier, vulnerable version into a log-processing component. The only code path in that component using the library issues a request to a single fixed, trusted vendor URL at initialization and does not process attacker-controlled input through the library, limiting practical exploitability of the reintroduced version in this context.