Comparison Overview

R1 RCM

VS

Nova Scotia Health Authority

R1 RCM

434 W Ascension Way, 6th Floor, Murray, Utah, US, 84123
Last Update: 2025-11-22
Between 750 and 799

R1 is the leader in healthcare revenue management, helping providers achieve new levels of performance through smart orchestration. A pioneer in the industry, R1 created the first Healthcare Revenue Operating System: a modular, intelligent platform that integrates automation, AI, and human expertise to strengthen the entire revenue cycle. With more than 20 years of experience, R1 partners with 1,000 providers, including 95 of the top 100 U.S. health systems, and handles over 270 million payer transactions annually. This scale provides unmatched operational insight to help healthcare organizations unlock greater long-term value. To learn more, visit: https://www.r1rcm.com.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 21,172
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
1

Nova Scotia Health Authority

1276 South Park Street, Halifax, Nova Scotia, CA, B3H 2Y9
Last Update: 2025-11-27
Between 700 and 749

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 ways to prevent and treat disease and maintain health. We are partners – with community groups, schools, government, foundations and auxiliaries, community health boards and, most importantly, with you. Most of all, we are a community of caring, compassionate people who care deeply about health, healing and learning. Together with you, we will create a healthier Nova Scotia. Mission: Working together to achieve excellence in health, healing and learning Vision: Healthy people, healthy communities – for generations

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 10,255
Subsidiaries: 0
12-month incidents
0
Known data breaches
3
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/r1-rcm.jpeg
R1 RCM
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/nsha.jpeg
Nova Scotia Health Authority
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
R1 RCM
100%
Compliance Rate
0/4 Standards Verified
Nova Scotia Health Authority
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Hospitals and Health Care Industry Average (This Year)

No incidents recorded for R1 RCM in 2025.

Incidents vs Hospitals and Health Care Industry Average (This Year)

No incidents recorded for Nova Scotia Health Authority in 2025.

Incident History — R1 RCM (X = Date, Y = Severity)

R1 RCM cyber incidents detection timeline including parent company and subsidiaries

Incident History — Nova Scotia Health Authority (X = Date, Y = Severity)

Nova Scotia Health Authority cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/r1-rcm.jpeg
R1 RCM
Incidents

Date Detected: 08/2020
Type:Ransomware
Blog: Blog
https://images.rankiteo.com/companyimages/nsha.jpeg
Nova Scotia Health Authority
Incidents

Date Detected: 08/2020
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

Date Detected: 06/2019
Type:Breach
Attack Vector: Phishing
Blog: Blog

Date Detected: 07/2017
Type:Breach
Blog: Blog

FAQ

R1 RCM company demonstrates a stronger AI Cybersecurity Score compared to Nova Scotia Health Authority company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Nova Scotia Health Authority company has faced a higher number of disclosed cyber incidents historically compared to R1 RCM company.

In the current year, Nova Scotia Health Authority company and R1 RCM company have not reported any cyber incidents.

R1 RCM company has confirmed experiencing a ransomware attack, while Nova Scotia Health Authority company has not reported such incidents publicly.

Nova Scotia Health Authority company has disclosed at least one data breach, while R1 RCM company has not reported such incidents publicly.

Neither Nova Scotia Health Authority company nor R1 RCM company has reported experiencing targeted cyberattacks publicly.

Neither R1 RCM company nor Nova Scotia Health Authority company has reported experiencing or disclosing vulnerabilities publicly.

Neither R1 RCM nor Nova Scotia Health Authority holds any compliance certifications.

Neither company holds any compliance certifications.

Neither R1 RCM company nor Nova Scotia Health Authority company has publicly disclosed detailed information about the number of their subsidiaries.

R1 RCM company employs more people globally than Nova Scotia Health Authority company, reflecting its scale as a Hospitals and Health Care.

Neither R1 RCM nor Nova Scotia Health Authority holds SOC 2 Type 1 certification.

Neither R1 RCM nor Nova Scotia Health Authority holds SOC 2 Type 2 certification.

Neither R1 RCM nor Nova Scotia Health Authority holds ISO 27001 certification.

Neither R1 RCM nor Nova Scotia Health Authority holds PCI DSS certification.

Neither R1 RCM nor Nova Scotia Health Authority holds HIPAA certification.

Neither R1 RCM nor Nova Scotia Health Authority holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H