Comparison Overview

Waterloo Public Library

VS

Spokane Public Library

Waterloo Public Library

undefined, undefined, undefined, 50701, US
Last Update: 2025-11-22
View Profile
Between 750 and 799
http://www.waterloo.lib.ia.us

Waterloo has one central public library, the Waterloo Public Library. For the fiscal year ending June 30, 2008, 259,144 patron visits resulted in circulation of 413,525 items. The total collection consisted of 210,135 items. The library’s reference services, supported by seven Full-time equivalent librarians, answered 78,400 questions. Staff members and patrons regularly post reviews of books on the library's blog, Lost in the Stacks. The library’s 43 public access computers provided over 87,688 sessions for patrons.[11] The library is governed by a board of trustees, nominated by the city mayor and confirmed by the city council: Robert Griffin, John Wood, Troyce Vich, Cindy Wells, and Sue Smith.[12] The library is directed by Sheryl Groskurth, MLS.[13] The Waterloo Public Library is located in a renovated Great Depression era building that served as a post office and federal building. The building was renovated in the late 1970s for use as a library.[14] Two New Deal-funded murals by artist Edgar Britton are on display at the library. "Exposition" is an image of the National Cattle Congress, and "Holiday" is of a picnic."[14]

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

Spokane Public Library

906 W Main Ave, Spokane, Washington, 99201, US
Last Update: 2025-11-26
Between 750 and 799
http://www.spokanelibrary.org

Spokane Public Library aims to inspire a thriving city through cultural and educational opportunities. An award-winning library that spans six branches and houses nearly half-a-million items, Spokane Public Library circulates nearly two million items and welcomes one million visitors annually. Customers can enjoy traditional library media and can also access digital downloads, databases, historical collections, art exhibits and interesting free programming. For general information about the library, please visit spokanelibrary.org or call us at 509-444-5300. Land Acknowledgement All Spokane Public Library buildings sit on the traditional homelands of the four bands of the Spokane Tribe of Indians: Sntútʔulixʷi, Snxʷmeneʔi, Sc̓qesciłni, and Sčewíleʔ (Upper Band, Middle Band, Lower Band, Chewelah Band). Since time immemorial, the Spokane Tribe of Indians has lived and cared for these grounds. Identifying themselves as “sqélixʷ,” or “Flesh of the Earth.” We pay our respects to their Elders – past, present, and emerging. We show gratitude to the land, river, and peoples who have been fishing, hunting, harvesting, and gathering here for generations. May we learn from one another’s stories, so that we may nurture the relationship of the People of the Spokane Tribe and to all those who share this land.

NAICS: 519
NAICS Definition:
Employees: 87
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/waterloo-public-library.jpeg
Waterloo 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
https://images.rankiteo.com/companyimages/spokane-public-library.jpeg
Spokane 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
Waterloo Public Library
100%
Compliance Rate
0/4 Standards Verified
Spokane Public Library
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Waterloo Public Library in 2025.

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Spokane Public Library in 2025.

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

Waterloo Public Library cyber incidents detection timeline including parent company and subsidiaries

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

Spokane 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/waterloo-public-library.jpeg
Waterloo Public Library
Incidents

No Incident

https://images.rankiteo.com/companyimages/spokane-public-library.jpeg
Spokane Public Library
Incidents

No Incident

FAQ

Spokane Public Library company demonstrates a stronger AI Cybersecurity Score compared to Waterloo Public Library company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Spokane Public Library company has disclosed a higher number of cyber incidents compared to Waterloo Public Library company.

In the current year, Spokane Public Library company and Waterloo Public Library company have not reported any cyber incidents.

Neither Spokane Public Library company nor Waterloo Public Library company has reported experiencing a ransomware attack publicly.

Neither Spokane Public Library company nor Waterloo Public Library company has reported experiencing a data breach publicly.

Neither Spokane Public Library company nor Waterloo Public Library company has reported experiencing targeted cyberattacks publicly.

Neither Waterloo Public Library company nor Spokane Public Library company has reported experiencing or disclosing vulnerabilities publicly.

Neither Waterloo Public Library nor Spokane Public Library holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Waterloo Public Library company nor Spokane Public Library company has publicly disclosed detailed information about the number of their subsidiaries.

Spokane Public Library company employs more people globally than Waterloo Public Library company, reflecting its scale as a Libraries.

Neither Waterloo Public Library nor Spokane Public Library holds SOC 2 Type 1 certification.

Neither Waterloo Public Library nor Spokane Public Library holds SOC 2 Type 2 certification.

Neither Waterloo Public Library nor Spokane Public Library holds ISO 27001 certification.

Neither Waterloo Public Library nor Spokane Public Library holds PCI DSS certification.

Neither Waterloo Public Library nor Spokane Public Library holds HIPAA certification.

Neither Waterloo Public Library nor Spokane 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