Comparison Overview
Nova Scotia Health Authority

Nova Scotia Health Authority
1276 South Park Street, Halifax, B3H 2Y9, CA
Last Update: 01/04/2026
We are Nova Scotia Health. We are rural and urban. We are in hospitals, health centres and community. We serve individuals and communities from Yarmouth to Cape Breton, from Amherst to Halifax, and everything in between. We are researchers and learners, looking for new...

Ardent Health
340 Seven Springs Way, Suite 100, Nashville, Tennessee, US, 37027
Last Update: 03/09/2026
Ardent Health is a leading provider of healthcare in growing mid-sized urban communities across the U.S. With a focus on people and investments in innovative services and technologies, Ardent is passionate about making healthcare better and easier to access. Through its...
Compliance Ranges Comparison

Nova Scotia Health Authority







Ardent Health






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Nova Scotia Health Authority in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Ardent Health in 2026.
Incident History - Nova Scotia Health Authority (X = Date, Y = Severity)
Nova Scotia Health Authority cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ardent Health (X = Date, Y = Severity)
Ardent Health cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Nova Scotia Health Authority

Ardent Health
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.