Comparison Overview

University of Washington Libraries

VS

Lawrence Public Library

University of Washington Libraries

US
Last Update: 2025-11-23
View Profile
Between 800 and 849
https://www.lib.washington.edu/

The UW Libraries is one of the largest and most innovative libraries in North America with extensive collections in print, electronic, and other formats. Providing services to three campuses, the UW Libraries also plays a significant leadership role regionally and throughout the profession. The UW Libraries is recognized for its excellent service, innovative learning and research spaces, collaborative approaches, extensive assessment efforts and diverse award-winning staff. The Libraries welcomes over 5 million users annually, is an integral part of the university’s education, clinical care, and research mission, and serves the general public with physical and online collections including archival collections documenting the history of regional groups and cultures.

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

Lawrence Public Library

707 Vermont Street, Lawrence, KS, 66044, US
Last Update: 2025-11-27
Between 750 and 799
http://www.lplks.org

Lawrence Public Library (LPL for short) is a community hub that believes in the power of connecting with each other through shared knowledge and resources. Located in the heart of Downtown Lawrence, Kansas — and on the road with our bookmobile, Dottie — we're committed to providing a space where everyone can learn, connect, create, and grow through access to our vast collections, resources, services, programs, and knowledgeable staff. The library is supported by tax dollars, the LPL Friends & Foundation's record-breaking book sales and philanthropic efforts, and dedicated efforts of more than 300 volunteers.

NAICS: 51912
NAICS Definition: Libraries and Archives
Employees: 84
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-washington-libraries.jpeg
University of Washington Libraries
—
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/lawrence-public-library.jpeg
Lawrence Public 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
Compliance Summary
University of Washington Libraries
100%
Compliance Rate
0/4 Standards Verified
Lawrence Public Library
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for University of Washington Libraries in 2025.

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Lawrence Public Library in 2025.

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

University of Washington Libraries cyber incidents detection timeline including parent company and subsidiaries

Incident History — Lawrence Public Library (X = Date, Y = Severity)

Lawrence Public Library 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-washington-libraries.jpeg
University of Washington Libraries
Incidents

No Incident

https://images.rankiteo.com/companyimages/lawrence-public-library.jpeg
Lawrence Public Library
Incidents

No Incident

FAQ

University of Washington Libraries company demonstrates a stronger AI Cybersecurity Score compared to Lawrence Public Library company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Lawrence Public Library company has disclosed a higher number of cyber incidents compared to University of Washington Libraries company.

In the current year, Lawrence Public Library company and University of Washington Libraries company have not reported any cyber incidents.

Neither Lawrence Public Library company nor University of Washington Libraries company has reported experiencing a ransomware attack publicly.

Neither Lawrence Public Library company nor University of Washington Libraries company has reported experiencing a data breach publicly.

Neither Lawrence Public Library company nor University of Washington Libraries company has reported experiencing targeted cyberattacks publicly.

Neither University of Washington Libraries company nor Lawrence Public Library company has reported experiencing or disclosing vulnerabilities publicly.

Neither University of Washington Libraries nor Lawrence Public Library holds any compliance certifications.

Neither company holds any compliance certifications.

Neither University of Washington Libraries company nor Lawrence Public Library company has publicly disclosed detailed information about the number of their subsidiaries.

University of Washington Libraries company employs more people globally than Lawrence Public Library company, reflecting its scale as a Libraries.

Neither University of Washington Libraries nor Lawrence Public Library holds SOC 2 Type 1 certification.

Neither University of Washington Libraries nor Lawrence Public Library holds SOC 2 Type 2 certification.

Neither University of Washington Libraries nor Lawrence Public Library holds ISO 27001 certification.

Neither University of Washington Libraries nor Lawrence Public Library holds PCI DSS certification.

Neither University of Washington Libraries nor Lawrence Public Library holds HIPAA certification.

Neither University of Washington Libraries nor Lawrence Public Library 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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References