Comparison Overview

Ministry of Health Saudi Arabia

VS

I work for NSW

Ministry of Health Saudi Arabia

-, Riyadh, 11176, SA
Last Update: 2026-01-17
View Profile
Between 750 and 799
http://www.moh.gov.sa

The Ministry of Health (MOH), by way of its objectives, policies and projects included in this strategy, seeks to accomplish a promising future vision; namely, delivering best-quality integrated and comprehensive healthcare services. Carrying health conditions or health status of Saudi inhabitants to the best and highest possible level, in terms of justice and equality in providing healthcare, and in terms of effectiveness and the possibility of incurring the financial burden of the treatment and healthcare. In doing so, the MOH takes as its target meeting citizens’ aspirations in this regard, by providing them with high-quality general and specialized health services, and covering all the population with these services.  Creating a sole and exclusive entity to formulate health policies including health insurance services, etc. (such as operating the recently established Health Services Council.) Adopting a public and national health strategy which focuses of the main morbidity burdens; including non-communicable diseases, nutrition, reproductive health, smoking (tobacco-use), AIDS, traffic accidents, and injuries.   The system must have an effective and fair method for estimating risks and benefits.   Working to diversify sources of revenues to finance the system effectively. These sources must include also public revenues and insurance premiums, in addition to the equally allocated costs and taxes.

NAICS: 92
NAICS Definition: Public Administration
Employees: 28,664
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

I work for NSW

Sydney, 2000, AU
Last Update: 2026-01-18
Between 750 and 799
http://iworkfor.nsw.gov.au/

The NSW public sector includes ten departments and many agencies and organisations working together to develop policy and deliver important services such as health, education, housing, transport and infrastructure across NSW. We are over 300,000 dedicated people who share the same values - making a difference, giving back and responding to the future. Read our community guidelines: bit.ly/PD-community-guidelines

NAICS: 92
NAICS Definition: Public Administration
Employees: 63,341
Subsidiaries: 17
12-month incidents
0
Known data breaches
1
Attack type number
4

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/ministry-of-health-saudi-arabia.jpeg
Ministry of Health Saudi Arabia
—
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/nsw-government.jpeg
I work for NSW
—
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
Ministry of Health Saudi Arabia
100%
Compliance Rate
0/4 Standards Verified
I work for NSW
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Ministry of Health Saudi Arabia in 2026.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for I work for NSW in 2026.

Incident History — Ministry of Health Saudi Arabia (X = Date, Y = Severity)

Ministry of Health Saudi Arabia cyber incidents detection timeline including parent company and subsidiaries

Incident History — I work for NSW (X = Date, Y = Severity)

I work for NSW cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ministry-of-health-saudi-arabia.jpeg
Ministry of Health Saudi Arabia
Incidents

No Incident

https://images.rankiteo.com/companyimages/nsw-government.jpeg
I work for NSW
Incidents

Date Detected: 02/2022
Type:Breach
Attack Vector: Accidental Exposure
Blog: Blog

Date Detected: 07/2021
Type:Cyber Attack
Blog: Blog

Date Detected: 2/2021
Type:Ransomware
Motivation: financial gain, data exfiltration
Blog: Blog

FAQ

I work for NSW company demonstrates a stronger AI Cybersecurity Score compared to Ministry of Health Saudi Arabia company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

I work for NSW company has historically faced a number of disclosed cyber incidents, whereas Ministry of Health Saudi Arabia company has not reported any.

In the current year, I work for NSW company and Ministry of Health Saudi Arabia company have not reported any cyber incidents.

I work for NSW company has confirmed experiencing a ransomware attack, while Ministry of Health Saudi Arabia company has not reported such incidents publicly.

I work for NSW company has disclosed at least one data breach, while Ministry of Health Saudi Arabia company has not reported such incidents publicly.

I work for NSW company has reported targeted cyberattacks, while Ministry of Health Saudi Arabia company has not reported such incidents publicly.

Neither Ministry of Health Saudi Arabia company nor I work for NSW company has reported experiencing or disclosing vulnerabilities publicly.

Neither Ministry of Health Saudi Arabia nor I work for NSW holds any compliance certifications.

Neither company holds any compliance certifications.

I work for NSW company has more subsidiaries worldwide compared to Ministry of Health Saudi Arabia company.

I work for NSW company employs more people globally than Ministry of Health Saudi Arabia company, reflecting its scale as a Government Administration.

Neither Ministry of Health Saudi Arabia nor I work for NSW holds SOC 2 Type 1 certification.

Neither Ministry of Health Saudi Arabia nor I work for NSW holds SOC 2 Type 2 certification.

Neither Ministry of Health Saudi Arabia nor I work for NSW holds ISO 27001 certification.

Neither Ministry of Health Saudi Arabia nor I work for NSW holds PCI DSS certification.

Neither Ministry of Health Saudi Arabia nor I work for NSW holds HIPAA certification.

Neither Ministry of Health Saudi Arabia nor I work for NSW holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g.,  execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/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
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.1
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
References