Comparison Overview

Health Resources in Action (HRiA)

VS

Maine Family Planning

Health Resources in Action (HRiA)

2 Boylston St, None, Boston, Massachusetts, US, None
Last Update: 2025-11-28
Between 700 and 749

Health Resources in Action is a non-profit organization working to improve and reimagine public health. We connect, consult, and collaborate to solve complex challenges of access and equity in our health and social systems. Together with our partners, clients, and collaborators, we create actionable solutions so that all people can thrive.

NAICS: 92312
NAICS Definition: Administration of Public Health Programs
Employees: 257
Subsidiaries: 4
12-month incidents
0
Known data breaches
1
Attack type number
1

Maine Family Planning

PO BOX 587, Augusta, 04330, US
Last Update:

Maine Family Planning is the state’s first and largest reproductive rights organization, providing leadership in four key areas: ensuring affordable quality reproductive health care services statewide, providing abortion care services and training for residents and physicians, building a statewide voice for family planning, and developing evidence-based programs that prevent unintended pregnancy.

NAICS: 92312
NAICS Definition: Administration of Public Health Programs
Employees: 59
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/health-resources-in-action.jpeg
Health Resources in Action (HRiA)
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/family-planning-association-of-maine.jpeg
Maine Family Planning
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
Health Resources in Action (HRiA)
100%
Compliance Rate
0/4 Standards Verified
Maine Family Planning
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for Health Resources in Action (HRiA) in 2025.

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for Maine Family Planning in 2025.

Incident History — Health Resources in Action (HRiA) (X = Date, Y = Severity)

Health Resources in Action (HRiA) cyber incidents detection timeline including parent company and subsidiaries

Incident History — Maine Family Planning (X = Date, Y = Severity)

Maine Family Planning cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/health-resources-in-action.jpeg
Health Resources in Action (HRiA)
Incidents

Date Detected: 3/2024
Type:Breach
Attack Vector: Unauthorized Access (Email & SharePoint)
Blog: Blog
https://images.rankiteo.com/companyimages/family-planning-association-of-maine.jpeg
Maine Family Planning
Incidents

No Incident

FAQ

Maine Family Planning company demonstrates a stronger AI Cybersecurity Score compared to Health Resources in Action (HRiA) company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Health Resources in Action (HRiA) company has historically faced a number of disclosed cyber incidents, whereas Maine Family Planning company has not reported any.

In the current year, Maine Family Planning company and Health Resources in Action (HRiA) company have not reported any cyber incidents.

Neither Maine Family Planning company nor Health Resources in Action (HRiA) company has reported experiencing a ransomware attack publicly.

Health Resources in Action (HRiA) company has disclosed at least one data breach, while the other Maine Family Planning company has not reported such incidents publicly.

Neither Maine Family Planning company nor Health Resources in Action (HRiA) company has reported experiencing targeted cyberattacks publicly.

Neither Health Resources in Action (HRiA) company nor Maine Family Planning company has reported experiencing or disclosing vulnerabilities publicly.

Neither Health Resources in Action (HRiA) nor Maine Family Planning holds any compliance certifications.

Neither company holds any compliance certifications.

Health Resources in Action (HRiA) company has more subsidiaries worldwide compared to Maine Family Planning company.

Health Resources in Action (HRiA) company employs more people globally than Maine Family Planning company, reflecting its scale as a Public Health.

Neither Health Resources in Action (HRiA) nor Maine Family Planning holds SOC 2 Type 1 certification.

Neither Health Resources in Action (HRiA) nor Maine Family Planning holds SOC 2 Type 2 certification.

Neither Health Resources in Action (HRiA) nor Maine Family Planning holds ISO 27001 certification.

Neither Health Resources in Action (HRiA) nor Maine Family Planning holds PCI DSS certification.

Neither Health Resources in Action (HRiA) nor Maine Family Planning holds HIPAA certification.

Neither Health Resources in Action (HRiA) nor Maine Family Planning 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