Comparison Overview

Egypt

VS

State of Oregon

Egypt

Cairo, EG
Last Update: 2025-11-21
Between 750 and 799

Egypt is a transcontinental country spanning the northeast corner of Africa and the southwest corner of Asia via a land bridge formed by the Sinai Peninsula. It is the world's only contiguous Eurafrasian nation. Egypt is bordered by the Mediterranean Sea to the north, Palestine, and Israel to the northeast, the Red Sea to the east, Sudan to the south, and Libya to the west. The Gulf of Aqaba in the northeast separates Egypt from Jordan and Saudi Arabia. Cairo is the capital and largest city of Egypt, while Alexandria, the second-largest city, is an important industrial and tourist hub on the Mediterranean coast. With approximately 100 million inhabitants, Egypt is the 14th most populated country in the world. The page is a public service initiative by Nastopni.ua

NAICS: 922
NAICS Definition:
Employees: 10,001
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

State of Oregon

Salem, 97301, US
Last Update: 2025-11-21
Between 750 and 799

Official LinkedIn page for the state of Oregon. Oregon is a state in the Pacific Northwest region of the United States. It is located on the Pacific coast, with Washington to the north, California to the south, Nevada on the southeast and Idaho to the east. The Columbia and Snake rivers delineate much of Oregon's northern and eastern boundaries, respectively. The area was inhabited by many indigenous tribes before the arrival of traders, explorers, and settlers who formed an autonomous government in Oregon Country in 1843. The Oregon Territory was created in 1848, and Oregon became the 33rd state on February 14, 1859.

NAICS: 92
NAICS Definition: Public Administration
Employees: 10,454
Subsidiaries: 8
12-month incidents
0
Known data breaches
1
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/egypt.jpeg
Egypt
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/state-of-oregon.jpeg
State of Oregon
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
Egypt
100%
Compliance Rate
0/4 Standards Verified
State of Oregon
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Egypt in 2025.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for State of Oregon in 2025.

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

Egypt cyber incidents detection timeline including parent company and subsidiaries

Incident History — State of Oregon (X = Date, Y = Severity)

State of Oregon cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/egypt.jpeg
Egypt
Incidents

No Incident

https://images.rankiteo.com/companyimages/state-of-oregon.jpeg
State of Oregon
Incidents

Date Detected: 11/2023
Type:Ransomware
Motivation: Data exfiltration and ransom
Blog: Blog

Date Detected: 06/2023
Type:Breach
Blog: Blog

FAQ

Egypt company demonstrates a stronger AI Cybersecurity Score compared to State of Oregon company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

State of Oregon company has historically faced a number of disclosed cyber incidents, whereas Egypt company has not reported any.

In the current year, State of Oregon company and Egypt company have not reported any cyber incidents.

State of Oregon company has confirmed experiencing a ransomware attack, while Egypt company has not reported such incidents publicly.

State of Oregon company has disclosed at least one data breach, while Egypt company has not reported such incidents publicly.

Neither State of Oregon company nor Egypt company has reported experiencing targeted cyberattacks publicly.

Neither Egypt company nor State of Oregon company has reported experiencing or disclosing vulnerabilities publicly.

Neither Egypt nor State of Oregon holds any compliance certifications.

Neither company holds any compliance certifications.

State of Oregon company has more subsidiaries worldwide compared to Egypt company.

State of Oregon company employs more people globally than Egypt company, reflecting its scale as a Government Administration.

Neither Egypt nor State of Oregon holds SOC 2 Type 1 certification.

Neither Egypt nor State of Oregon holds SOC 2 Type 2 certification.

Neither Egypt nor State of Oregon holds ISO 27001 certification.

Neither Egypt nor State of Oregon holds PCI DSS certification.

Neither Egypt nor State of Oregon holds HIPAA certification.

Neither Egypt nor State of Oregon 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