Comparison Overview

Alameda County Library

VS

Baltimore County Public Library

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

Baltimore County Public Library

320 York Rd, Towson, 21204, US
Last Update: 2025-11-22
Between 750 and 799

Mission Statement: Providing opportunities to explore, learn, create, and connect. Vision: Empowered and engaged individuals in an inclusive and connected Baltimore County community. We Value: - Customers & communities - Equal access & intellectual freedom - Flexibility & collaboration - Continuous improvement We are one of the nation's top library systems that is dedicated to serving the large, diverse community of Baltimore County and Maryland. With 19 branches around the county, as well as 4 roaming bookmobiles, we offer a large number of new and popular books, as well as older fiction and non-fiction, videos and DVDs, audiobooks, CDs, foreign language titles, magazines, comic books, video games, and more.

NAICS: 51912
NAICS Definition: Libraries and Archives
Employees: 516
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/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
https://images.rankiteo.com/companyimages/bcpl.jpeg
Baltimore County 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
Alameda County Library
100%
Compliance Rate
0/4 Standards Verified
Baltimore County Public Library
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Alameda County Library in 2025.

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Baltimore County Public Library in 2025.

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

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

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

Baltimore County 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/alameda-county-library.jpeg
Alameda County Library
Incidents

Date Detected: 12/2017
Type:Data Leak
Blog: Blog
https://images.rankiteo.com/companyimages/bcpl.jpeg
Baltimore County Public Library
Incidents

No Incident

FAQ

Baltimore County 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 Baltimore County Public Library company has not reported any.

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

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

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

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

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

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

Neither company holds any compliance certifications.

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

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

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

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

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

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

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

Neither Alameda County Library nor Baltimore County Public Library holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

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

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.