Comparison Overview

University of Essex

VS

Ain Shams University

University of Essex

Wivenhoe Park, Essex, east england, CO4 3SQ, GB
Last Update: 2025-11-27
Between 700 and 749

We are proud to promote our ethos of excellence in education and excellence in research as one of the UK's top 20 universities for research excellence. "We are an internationally oriented, research intensive university with a commitment to excellence in research and research-led teaching, to the personal development of all our students, and to offering an outstanding campus-based student experience."​ Professor Anthony Forster, Vice-Chancellor. Our alumni are invited to join our University of Essex Alumni and Friends official group for professional networking opportunities.

NAICS: 6113
NAICS Definition: Colleges, Universities, and Professional Schools
Employees: 4,149
Subsidiaries: 10
12-month incidents
0
Known data breaches
1
Attack type number
1

Ain Shams University

Abbasid, Cairo, Cairo, EG, 11566
Last Update: 2025-11-27
Between 800 and 849

Ain Shams University, as the third Egyptian university, was founded in July 1950 under the name of "Ibrahim Pasha University". It participated with the two earlier universities, "Cairo University" (Fua'd the 1st ) and "Alexandria University" (Farouk the 1st) in fulfilling the message of universities and meeting the increasing demand of youth for higher education. When it was first established, Ain Shams University comprised a number of distinguished faculties and academic institutes, which were later developed into university.

NAICS: 6113
NAICS Definition: Colleges, Universities, and Professional Schools
Employees: 12,687
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/university-of-essex.jpeg
University of Essex
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/ain-shams-university.jpeg
Ain Shams University
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
University of Essex
100%
Compliance Rate
0/4 Standards Verified
Ain Shams University
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Higher Education Industry Average (This Year)

No incidents recorded for University of Essex in 2025.

Incidents vs Higher Education Industry Average (This Year)

No incidents recorded for Ain Shams University in 2025.

Incident History — University of Essex (X = Date, Y = Severity)

University of Essex cyber incidents detection timeline including parent company and subsidiaries

Incident History — Ain Shams University (X = Date, Y = Severity)

Ain Shams University cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/university-of-essex.jpeg
University of Essex
Incidents

Date Detected: 05/2022
Type:Breach
Attack Vector: Email
Blog: Blog
https://images.rankiteo.com/companyimages/ain-shams-university.jpeg
Ain Shams University
Incidents

No Incident

FAQ

Ain Shams University company demonstrates a stronger AI Cybersecurity Score compared to University of Essex company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

University of Essex company has historically faced a number of disclosed cyber incidents, whereas Ain Shams University company has not reported any.

In the current year, Ain Shams University company and University of Essex company have not reported any cyber incidents.

Neither Ain Shams University company nor University of Essex company has reported experiencing a ransomware attack publicly.

University of Essex company has disclosed at least one data breach, while the other Ain Shams University company has not reported such incidents publicly.

Neither Ain Shams University company nor University of Essex company has reported experiencing targeted cyberattacks publicly.

Neither University of Essex company nor Ain Shams University company has reported experiencing or disclosing vulnerabilities publicly.

Neither University of Essex nor Ain Shams University holds any compliance certifications.

Neither company holds any compliance certifications.

University of Essex company has more subsidiaries worldwide compared to Ain Shams University company.

Ain Shams University company employs more people globally than University of Essex company, reflecting its scale as a Higher Education.

Neither University of Essex nor Ain Shams University holds SOC 2 Type 1 certification.

Neither University of Essex nor Ain Shams University holds SOC 2 Type 2 certification.

Neither University of Essex nor Ain Shams University holds ISO 27001 certification.

Neither University of Essex nor Ain Shams University holds PCI DSS certification.

Neither University of Essex nor Ain Shams University holds HIPAA certification.

Neither University of Essex nor Ain Shams University 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.