Comparison Overview

UNICEF

VS

International Rescue Committee

UNICEF

3 United Nations Plaza, New York, New York, US, 10017
Last Update: 2025-11-23
Between 800 and 849

UNICEF works in some of the world’s toughest places, to reach the world’s most disadvantaged children. To save their lives. To defend their rights. To help them fulfill their potential. Across 190 countries and territories, we work for every child, everywhere, every day, to build a better world for everyone. And we never give up.

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

International Rescue Committee

122 E 42st , New York, NY, 10168, US
Last Update: 2025-11-24
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: 14,263
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/unicef.jpeg
UNICEF
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
UNICEF
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 UNICEF in 2025.

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

No incidents recorded for International Rescue Committee in 2025.

Incident History — UNICEF (X = Date, Y = Severity)

UNICEF 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/unicef.jpeg
UNICEF
Incidents

Date Detected: 09/2019
Type:Data Leak
Attack Vector: Misconfigured Email
Blog: Blog
https://images.rankiteo.com/companyimages/international-rescue-committee.jpeg
International Rescue Committee
Incidents

No Incident

FAQ

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

UNICEF 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 UNICEF company have not reported any cyber incidents.

Neither International Rescue Committee company nor UNICEF company has reported experiencing a ransomware attack publicly.

Neither International Rescue Committee company nor UNICEF company has reported experiencing a data breach publicly.

Neither International Rescue Committee company nor UNICEF company has reported experiencing targeted cyberattacks publicly.

Neither UNICEF company nor International Rescue Committee company has reported experiencing or disclosing vulnerabilities publicly.

Neither UNICEF nor International Rescue Committee holds any compliance certifications.

Neither company holds any compliance certifications.

UNICEF company has more subsidiaries worldwide compared to International Rescue Committee company.

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

Neither UNICEF nor International Rescue Committee holds SOC 2 Type 1 certification.

Neither UNICEF nor International Rescue Committee holds SOC 2 Type 2 certification.

Neither UNICEF nor International Rescue Committee holds ISO 27001 certification.

Neither UNICEF nor International Rescue Committee holds PCI DSS certification.

Neither UNICEF nor International Rescue Committee holds HIPAA certification.

Neither UNICEF nor International Rescue Committee holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

Risk Information
cvss4
Base: 6.2
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:L/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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

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

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.