Comparison Overview

Tri-Cities Chaplaincy

VS

International Rescue Committee

Tri-Cities Chaplaincy

Last Update: 2025-12-14
Between 700 and 749

The team from Tri-Cities Chaplaincy focuses on the entire person – their physical, emotional, and spiritual needs. We guide, comfort, and care for people experiencing serious illness, end of life, loss, and grief. Our heritage of compassion began in 1971 when a group of local churches in the Tri-Cities area established a program with one chaplain to provide outreach to people not being served in jails and nursing homes, and people coping with dying or the loss of a loved one. Incorporated in 1974, we added more chaplains and volunteers during the next decade and, in 1981, we accepted our first hospice patient. Chaplaincy Health Care has continually honed our medical expertise with a significant number of board-certified clinical team members and a high ratio of RNs, social workers and chaplains to provide guidance, care and comfort with the highest standards of excellence. Our desire is for our entire community – patients, families and other healthcare providers – to know Chaplaincy Health Care as the vast resource and partner we are for hospice services, chaplain services and grief support. Chaplaincy Health Care is a nonprofit organization and assists all individuals in need throughout our service area in the Mid-Columbia region of southeast Washington. Our work is supported by individuals, businesses, foundations, local service clubs and communities of faith.

NAICS: 8135
NAICS Definition: Others
Employees: 66
Subsidiaries: 0
12-month incidents
0
Known data breaches
1
Attack type number
1

International Rescue Committee

122 E 42st , New York, 10168, US
Last Update: 2025-12-18
Between 800 and 849

The International Rescue Committee responds to the world’s worst humanitarian crises and help people to survive, recover, and gain control of their future. Founded in 1933 at the request of Albert Einstein, the IRC offers lifesaving care and life-changing assistance to refugees and displaced people forced to flee from war or disaster. At work today in over 50+ countries and in 28 U.S. cities, the IRC restores safety, dignity and hope to millions who are uprooted and struggling to endure.

NAICS: 8135
NAICS Definition: Others
Employees: 13,319
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/chaplaincy-health-care.jpeg
Tri-Cities Chaplaincy
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/international-rescue-committee.jpeg
International Rescue Committee
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
Tri-Cities Chaplaincy
100%
Compliance Rate
0/4 Standards Verified
International Rescue Committee
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Non-profit Organizations Industry Average (This Year)

No incidents recorded for Tri-Cities Chaplaincy in 2025.

Incidents vs Non-profit Organizations Industry Average (This Year)

No incidents recorded for International Rescue Committee in 2025.

Incident History — Tri-Cities Chaplaincy (X = Date, Y = Severity)

Tri-Cities Chaplaincy cyber incidents detection timeline including parent company and subsidiaries

Incident History — International Rescue Committee (X = Date, Y = Severity)

International Rescue Committee cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/chaplaincy-health-care.jpeg
Tri-Cities Chaplaincy
Incidents

Date Detected: 1/2019
Type:Breach
Attack Vector: Phishing
Motivation: Gaining more email contacts
Blog: Blog
https://images.rankiteo.com/companyimages/international-rescue-committee.jpeg
International Rescue Committee
Incidents

No Incident

FAQ

International Rescue Committee company demonstrates a stronger AI Cybersecurity Score compared to Tri-Cities Chaplaincy company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Tri-Cities Chaplaincy company has historically faced a number of disclosed cyber incidents, whereas International Rescue Committee company has not reported any.

In the current year, International Rescue Committee company and Tri-Cities Chaplaincy company have not reported any cyber incidents.

Neither International Rescue Committee company nor Tri-Cities Chaplaincy company has reported experiencing a ransomware attack publicly.

Tri-Cities Chaplaincy company has disclosed at least one data breach, while the other International Rescue Committee company has not reported such incidents publicly.

Neither International Rescue Committee company nor Tri-Cities Chaplaincy company has reported experiencing targeted cyberattacks publicly.

Neither Tri-Cities Chaplaincy company nor International Rescue Committee company has reported experiencing or disclosing vulnerabilities publicly.

Neither Tri-Cities Chaplaincy nor International Rescue Committee holds any compliance certifications.

Neither company holds any compliance certifications.

International Rescue Committee company has more subsidiaries worldwide compared to Tri-Cities Chaplaincy company.

International Rescue Committee company employs more people globally than Tri-Cities Chaplaincy company, reflecting its scale as a Non-profit Organizations.

Neither Tri-Cities Chaplaincy nor International Rescue Committee holds SOC 2 Type 1 certification.

Neither Tri-Cities Chaplaincy nor International Rescue Committee holds SOC 2 Type 2 certification.

Neither Tri-Cities Chaplaincy nor International Rescue Committee holds ISO 27001 certification.

Neither Tri-Cities Chaplaincy nor International Rescue Committee holds PCI DSS certification.

Neither Tri-Cities Chaplaincy nor International Rescue Committee holds HIPAA certification.

Neither Tri-Cities Chaplaincy nor International Rescue Committee holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Zerobyte is a backup automation tool Zerobyte versions prior to 0.18.5 and 0.19.0 contain an authentication bypass vulnerability where authentication middleware is not properly applied to API endpoints. This results in certain API endpoints being accessible without valid session credentials. This is dangerous for those who have exposed Zerobyte to be used outside of their internal network. A fix has been applied in both version 0.19.0 and 0.18.5. If immediate upgrade is not possible, restrict network access to the Zerobyte instance to trusted networks only using firewall rules or network segmentation. This is only a temporary mitigation; upgrading is strongly recommended.

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

Open Source Point of Sale (opensourcepos) is a web based point of sale application written in PHP using CodeIgniter framework. Starting in version 3.4.0 and prior to version 3.4.2, a Cross-Site Request Forgery (CSRF) vulnerability exists in the application's filter configuration. The CSRF protection mechanism was **explicitly disabled**, allowing the application to process state-changing requests (POST) without verifying a valid CSRF token. An unauthenticated remote attacker can exploit this by hosting a malicious web page. If a logged-in administrator visits this page, their browser is forced to send unauthorized requests to the application. A successful exploit allows the attacker to silently create a new Administrator account with full privileges, leading to a complete takeover of the system and loss of confidentiality, integrity, and availability. The vulnerability has been patched in version 3.4.2. The fix re-enables the CSRF filter in `app/Config/Filters.php` and resolves associated AJAX race conditions by adjusting token regeneration settings. As a workaround, administrators can manually re-enable the CSRF filter in `app/Config/Filters.php` by uncommenting the protection line. However, this is not recommended without applying the full patch, as it may cause functionality breakage in the Sales module due to token synchronization issues.

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

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Model Context Protocol (MCP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious MCP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered automatically without any user interaction besides opening the project in the IDE. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

Risk Information
cvss3
Base: 7.7
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Description

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Language Server Protocol (LSP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious LSP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered when a user opens project file for which there is an LSP entry. A concerted effort by an attacker to seed a project settings file (`./zed/settings.json`) with malicious language server configurations could result in arbitrary code execution with the user's privileges if the user opens the project in Zed without reviewing the contents. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

Risk Information
cvss3
Base: 7.7
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Description

Storybook is a frontend workshop for building user interface components and pages in isolation. A vulnerability present starting in versions 7.0.0 and prior to versions 7.6.21, 8.6.15, 9.1.17, and 10.1.10 relates to Storybook’s handling of environment variables defined in a `.env` file, which could, in specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by the `storybook build` command. When a built Storybook is published to the web, the bundle’s source is viewable, thus potentially exposing those variables to anyone with access. For a project to potentially be vulnerable to this issue, it must build the Storybook (i.e. run `storybook build` directly or indirectly) in a directory that contains a `.env` file (including variants like `.env.local`) and publish the built Storybook to the web. Storybooks built without a `.env` file at build time are not affected, including common CI-based builds where secrets are provided via platform environment variables rather than `.env` files. Storybook runtime environments (i.e. `storybook dev`) are not affected. Deployed applications that share a repo with your Storybook are not affected. Users should upgrade their Storybook—on both their local machines and CI environment—to version .6.21, 8.6.15, 9.1.17, or 10.1.10 as soon as possible. Maintainers additionally recommend that users audit for any sensitive secrets provided via `.env` files and rotate those keys. Some projects may have been relying on the undocumented behavior at the heart of this issue and will need to change how they reference environment variables after this update. If a project can no longer read necessary environmental variable values, either prefix the variables with `STORYBOOK_` or use the `env` property in Storybook’s configuration to manually specify values. In either case, do not include sensitive secrets as they will be included in the built bundle.

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