Comparison Overview

Westerville Public Library

VS

Alameda County Library

Westerville Public Library

126 S. State St., Westerville, Ohio, 43081, US
Last Update: 2025-11-27

Unlock an expansion pack of tools and services to boost your energy, improve your odds, and reboot your life. Take advantage of complimentary Wi-Fi, computer labs, study space, technology training, homework help, home deliveries, learning kits, language learning software, and more. Choose from a collection of over 400,000 items. Place requests online then pick up through the convenient drive thru. Located in the heart of Uptown Westerville near the Ohio to Erie recreational trail. All Ohio residents are welcome to apply for a library card.

NAICS: 519
NAICS Definition:
Employees: 84
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Alameda County Library

2450 Stevenson Blvd., Fremont, California, US, 94538
Last Update: 2025-11-23
Between 700 and 749

Alameda County Library provides library services from ten libraries in the cities of Albany, Dublin, Fremont, Newark, and Union City and the unincorporated communities of Castro Valley and the Eden Area, including San Lorenzo and Cherryland. Alameda County Library also provides additional services through our Equitable Libraries Division via Youth and Family Services, Mobile and Outreach Services, Education and Literacy Services, and Social Justice Services. Our team is dedicated to providing a space for everyone to express and embrace our values of Authenticity, Integrity, Creativity, Curiosity, and Empathy.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/westervillelibrary.jpeg
Westerville 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/alameda-county-library.jpeg
Alameda County 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
Westerville Public Library
100%
Compliance Rate
0/4 Standards Verified
Alameda County Library
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Westerville Public Library in 2025.

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Alameda County Library in 2025.

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

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

Incident History — Alameda County Library (X = Date, Y = Severity)

Alameda County Library cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/westervillelibrary.jpeg
Westerville Public Library
Incidents

No Incident

https://images.rankiteo.com/companyimages/alameda-county-library.jpeg
Alameda County Library
Incidents

Date Detected: 12/2017
Type:Data Leak
Blog: Blog

FAQ

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

Alameda County Library company has historically faced a number of disclosed cyber incidents, whereas Westerville Public Library company has not reported any.

In the current year, Alameda County Library company and Westerville Public Library company have not reported any cyber incidents.

Neither Alameda County Library company nor Westerville Public Library company has reported experiencing a ransomware attack publicly.

Neither Alameda County Library company nor Westerville Public Library company has reported experiencing a data breach publicly.

Neither Alameda County Library company nor Westerville Public Library company has reported experiencing targeted cyberattacks publicly.

Neither Westerville Public Library company nor Alameda County Library company has reported experiencing or disclosing vulnerabilities publicly.

Neither Westerville Public Library nor Alameda County Library holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Westerville Public Library company nor Alameda County Library company has publicly disclosed detailed information about the number of their subsidiaries.

Alameda County Library company employs more people globally than Westerville Public Library company, reflecting its scale as a Libraries.

Neither Westerville Public Library nor Alameda County Library holds SOC 2 Type 1 certification.

Neither Westerville Public Library nor Alameda County Library holds SOC 2 Type 2 certification.

Neither Westerville Public Library nor Alameda County Library holds ISO 27001 certification.

Neither Westerville Public Library nor Alameda County Library holds PCI DSS certification.

Neither Westerville Public Library nor Alameda County Library holds HIPAA certification.

Neither Westerville Public Library nor Alameda County 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.

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
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.

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
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.

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
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.

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
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.

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