Comparison Overview
Los Angeles County Department of Health Services
Los Angeles County Department of Health Services
313 N. Figueroa Street, Los Angeles, 90012, US
Last Update: 31/03/2026
Los Angeles County Department of Health Services (DHS; LADHS) is the 2nd largest municipal hospital system in the United States. With an annual operating budget of over $4 billion USD, DHS operates an extensive healthcare network throughout Los Angeles County, including...
Trinity Health
20555 Victor Parkway, Livonia, MI, US, 48152
Last Update: 04/04/2026
Trinity Health is one of the largest not-for-profit, Catholic health care systems in the nation. It is a family of 123,000 colleagues and nearly 27,000 physicians and clinicians caring for diverse communities across 26 states. Nationally recognized for care and experien...
Compliance Ranges Comparison
Los Angeles County Department of Health Services
Trinity Health
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Los Angeles County Department of Health Services in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Trinity Health has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Los Angeles County Department of Health Services (X = Date, Y = Severity)
Los Angeles County Department of Health Services cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Trinity Health (X = Date, Y = Severity)
Trinity Health cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Los Angeles County Department of Health Services
Trinity Health
FAQ
Latest Global CVEs
A vulnerability has been found in SourceCodester Simple Online Food Ordering System 1.0. This affects an unknown function of the file /admin/ajax.php?action=login2. The manipulation of the argument email leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
A flaw was found in the ipa_getkeytab module of the community.general Ansible collection. The module's bind_pw parameter, used to supply the LDAP simple-bind password when retrieving a Kerberos keytab, is not declared with no_log, unlike the sibling password parameter in the same module. As a consequence, the supplied IPA/LDAP bind password is recorded in cleartext in the managed host's system journal/syslog (the module's "Invoked with" record), is included in the module's return values and verbose (-v) output, and is displayed in Automation Controller / AWX job output. The password is additionally passed on the command line to the ipa-getkeytab helper (as --bindpw <value>), exposing it in the process list to local users while the command runs. An attacker able to read these logs, job output, or the process table can obtain the directory bind credential, potentially compromising the accounts and objects that credential can access.
The device metadata import interface /device/instance/{productId}/property-metadata/import of jetlinks community 2.11 is vulnerable to Server-side request forgery (SSRF).
disconf (Distributed Configuration Management Platform) 2.6.36 is vulnerable to Incorrect Access Control. The config-fetching APIs /api/config/item, /api/config/file, /api/config/list and /api/config/simple/list are exposed without authentication. The LoginInterceptor explicitly whitelists these four paths, so any anonymous attacker can read every configuration item and configuration file managed by the config center.
Funiture 1.0.0 is vulnerable to SQL Injection in the backend tool interfaces /sys/tool/select.json and /sys/tool/update.json.