Comparison Overview

SciScore

VS

The University of Edinburgh

SciScore

P.O. Box 928191, San Diego, 92122, US
Last Update: 2025-12-23
Between 700 and 749

SciScore scans submitted methods sections for sentences that describe antibodies, cell lines, organisms and tools (e.g., statistical software) then creates a key resources, prototype "STAR table."​ SciScore also tests the percent of key biological resources that should have a research resource identifier, RRID, and the percent that do have an RRID.

NAICS: 5417
NAICS Definition: Scientific Research and Development Services
Employees: None
Subsidiaries: 2
12-month incidents
0
Known data breaches
0
Attack type number
0

The University of Edinburgh

Old College, Edinburgh, undefined, EH8 9YL, GB
Last Update: 2025-12-17
Between 750 and 799

Imagine what you could do at a world-leading university that is globally recognised for its teaching, research and innovation. The University of Edinburgh has been providing students with world-class teaching for more than 425 years, unlocking the potential of some of the world's leading thinkers since 1583. Choose to study with us and you will be investing in an education that will help you build a successful future.

NAICS: 5417
NAICS Definition: Scientific Research and Development Services
Employees: 15,535
Subsidiaries: 17
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/sciscore.jpeg
SciScore
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/university-of-edinburgh.jpeg
The University of Edinburgh
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
SciScore
100%
Compliance Rate
0/4 Standards Verified
The University of Edinburgh
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Research Services Industry Average (This Year)

No incidents recorded for SciScore in 2025.

Incidents vs Research Services Industry Average (This Year)

No incidents recorded for The University of Edinburgh in 2025.

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

SciScore cyber incidents detection timeline including parent company and subsidiaries

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

The University of Edinburgh cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/sciscore.jpeg
SciScore
Incidents

No Incident

https://images.rankiteo.com/companyimages/university-of-edinburgh.jpeg
The University of Edinburgh
Incidents

No Incident

FAQ

The University of Edinburgh company demonstrates a stronger AI Cybersecurity Score compared to SciScore company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, The University of Edinburgh company has disclosed a higher number of cyber incidents compared to SciScore company.

In the current year, The University of Edinburgh company and SciScore company have not reported any cyber incidents.

Neither The University of Edinburgh company nor SciScore company has reported experiencing a ransomware attack publicly.

Neither The University of Edinburgh company nor SciScore company has reported experiencing a data breach publicly.

Neither The University of Edinburgh company nor SciScore company has reported experiencing targeted cyberattacks publicly.

Neither SciScore company nor The University of Edinburgh company has reported experiencing or disclosing vulnerabilities publicly.

Neither SciScore nor The University of Edinburgh holds any compliance certifications.

Neither company holds any compliance certifications.

The University of Edinburgh company has more subsidiaries worldwide compared to SciScore company.

Neither SciScore nor The University of Edinburgh holds SOC 2 Type 1 certification.

Neither SciScore nor The University of Edinburgh holds SOC 2 Type 2 certification.

Neither SciScore nor The University of Edinburgh holds ISO 27001 certification.

Neither SciScore nor The University of Edinburgh holds PCI DSS certification.

Neither SciScore nor The University of Edinburgh holds HIPAA certification.

Neither SciScore nor The University of Edinburgh holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

httparty is an API tool. In versions 0.23.2 and prior, httparty is vulnerable to SSRF. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers. This issue has been patched via commit 0529bcd.

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

5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. In versions 0.15.2 and prior, an RCE vulnerability exists in useMarkdown.ts, where the markdown-it-mermaid plugin is initialized with securityLevel: 'loose'. This configuration explicitly permits the rendering of HTML tags within Mermaid diagram nodes. This issue has not been patched at time of publication.

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

continuwuity is a Matrix homeserver written in Rust. Prior to version 0.5.0, this vulnerability allows a remote, unauthenticated attacker to force the target server to cryptographically sign arbitrary membership events. The flaw exists because the server fails to validate the origin of a signing request, provided the event's state_key is a valid user ID belonging to the target server. This issue has been patched in version 0.5.0. A workaround for this issue involves blocking access to the PUT /_matrix/federation/v2/invite/{roomId}/{eventId} endpoint using the reverse proxy.

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

LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3

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

LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form dictionaries. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in versions 0.3.81 and 1.2.5.

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