Comparison Overview

The British Library

VS

Bibliothèque de l'EPFL

The British Library

96 Euston Road, London, NW1 2DB, GB
Last Update: 2026-01-10
Between 700 and 749

We are the UK’s national library. We give access to the world’s most comprehensive collection of over 170 million items - a living collection that grows every single day. Dating back 3,000 years, the collection includes Shakespeare’s First Folio, Magna Carta, a rare recording of Florence Nightingale and even Sylvia Pankhurst’s poems written on toilet paper from prison… But the collection also includes this morning’s newspapers, blogs and tweets, as well as a copy of every UK domain website. Our collection helps to open up a world of ideas. It can inspire people to start businesses. Spark new works of art and literature. Make scientific discoveries. Visit bl.uk to start your journey of discovery.

NAICS: 51912
NAICS Definition: Libraries and Archives
Employees: 1,310
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
2

Bibliothèque de l'EPFL

Station 20, Lausanne, 1015, CH
Last Update: 2026-01-16
Between 750 and 799

Welcoming more than one million visitors per year, the EPFL Library is an empowering and supporting institution located at the heart of the Rolex Learning Center. The EPFL Library aims to facilitate excellence in teaching and research, by providing rich collections and tailored services. Implementing these innovative services, on site and online, the Library participates to the EPFL global move to support Open Science.

NAICS: 51912
NAICS Definition: Libraries and Archives
Employees: None
Subsidiaries: 22
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/the-british-library.jpeg
The British Library
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/epfllibrary.jpeg
Bibliothèque de l'EPFL
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
The British Library
100%
Compliance Rate
0/4 Standards Verified
Bibliothèque de l'EPFL
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for The British Library in 2026.

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Bibliothèque de l'EPFL in 2026.

Incident History — The British Library (X = Date, Y = Severity)

The British Library cyber incidents detection timeline including parent company and subsidiaries

Incident History — Bibliothèque de l'EPFL (X = Date, Y = Severity)

Bibliothèque de l'EPFL cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/the-british-library.jpeg
The British Library
Incidents

Date Detected: 10/2023
Type:Cyber Attack
Motivation: Financial (ransom demand), Disruption
Blog: Blog

Date Detected: 6/2023
Type:Ransomware
Attack Vector: malvertising, spoofed ads, fake download pages, .LNK file abuse
Motivation: financial gain, ransomware deployment, data theft
Blog: Blog
https://images.rankiteo.com/companyimages/epfllibrary.jpeg
Bibliothèque de l'EPFL
Incidents

No Incident

FAQ

Bibliothèque de l'EPFL company demonstrates a stronger AI Cybersecurity Score compared to The British Library company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

The British Library company has historically faced a number of disclosed cyber incidents, whereas Bibliothèque de l'EPFL company has not reported any.

In the current year, Bibliothèque de l'EPFL company and The British Library company have not reported any cyber incidents.

The British Library company has confirmed experiencing a ransomware attack, while Bibliothèque de l'EPFL company has not reported such incidents publicly.

Neither Bibliothèque de l'EPFL company nor The British Library company has reported experiencing a data breach publicly.

The British Library company has reported targeted cyberattacks, while Bibliothèque de l'EPFL company has not reported such incidents publicly.

Neither The British Library company nor Bibliothèque de l'EPFL company has reported experiencing or disclosing vulnerabilities publicly.

Neither The British Library nor Bibliothèque de l'EPFL holds any compliance certifications.

Neither company holds any compliance certifications.

Bibliothèque de l'EPFL company has more subsidiaries worldwide compared to The British Library company.

Neither The British Library nor Bibliothèque de l'EPFL holds SOC 2 Type 1 certification.

Neither The British Library nor Bibliothèque de l'EPFL holds SOC 2 Type 2 certification.

Neither The British Library nor Bibliothèque de l'EPFL holds ISO 27001 certification.

Neither The British Library nor Bibliothèque de l'EPFL holds PCI DSS certification.

Neither The British Library nor Bibliothèque de l'EPFL holds HIPAA certification.

Neither The British Library nor Bibliothèque de l'EPFL holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Gradle is a build automation tool, and its native-platform tool provides Java bindings for native APIs. When resolving dependencies in versions before 9.3.0, some exceptions were not treated as fatal errors and would not cause a repository to be disabled. If a build encountered one of these exceptions, Gradle would continue to the next repository in the list and potentially resolve dependencies from a different repository. An exception like NoHttpResponseException can indicate transient errors. If the errors persist after a maximum number of retries, Gradle would continue to the next repository. This behavior could allow an attacker to disrupt the service of a repository and leverage another repository to serve malicious artifacts. This attack requires the attacker to have control over a repository after the disrupted repository. Gradle has introduced a change in behavior in Gradle 9.3.0 to stop searching other repositories when encountering these errors.

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

Gradle is a build automation tool, and its native-platform tool provides Java bindings for native APIs. When resolving dependencies in versions before 9.3.0, some exceptions were not treated as fatal errors and would not cause a repository to be disabled. If a build encountered one of these exceptions, Gradle would continue to the next repository in the list and potentially resolve dependencies from a different repository. If a Gradle build used an unresolvable host name, Gradle would continue to work as long as all dependencies could be resolved from another repository. An unresolvable host name could be caused by allowing a repository's domain name registration to lapse or typo-ing the real domain name. This behavior could allow an attacker to register a service under the host name used by the build and serve malicious artifacts. The attack requires the repository to be listed before others in the build configuration. Gradle has introduced a change in behavior in Gradle 9.3.0 to stop searching other repositories when encountering these errors.

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

node-tar is a Tar for Node.js. The node-tar library (<= 7.5.2) fails to sanitize the linkpath of Link (hardlink) and SymbolicLink entries when preservePaths is false (the default secure behavior). This allows malicious archives to bypass the extraction root restriction, leading to Arbitrary File Overwrite via hardlinks and Symlink Poisoning via absolute symlink targets. This vulnerability is fixed in 7.5.3.

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

Microsoft Edge Elevation Service exposes a privileged COM interface that inadequately validates the privileges of the calling process. A standard (non‑administrator) local user can invoke the IElevatorEdge interface method LaunchUpdateCmdElevatedAndWait, causing the service to execute privileged update commands as LocalSystem. This allows a non‑administrator to enable or disable Windows Virtualization‑Based Security (VBS) by modifying protected system registry keys under HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard. Disabling VBS weakens critical platform protections such as Credential Guard, Hypervisor‑protected Code Integrity (HVCI), and the Secure Kernel, resulting in a security feature bypass.

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

Improper authorization in Microsoft Power Apps allows an authorized attacker to execute code over a network.

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