Comparison Overview

St. Louis Public Library

VS

Howell Carnegie District Library

St. Louis Public Library

St. Louis Public Library, St. Louis, MO, 63103, US
Last Update: 2025-11-25
Between 750 and 799

The St. Louis Public Library provides learning resources and information services that support and improve individual, family and community life. Visit slpl.org for more information on our offerings. To support this mission, the Library organizes and prudently manages its resources to: Ensure that the Library's resources are available to all Promote use of the Library Assist children and adults with life-long learning Promote literacy for all ages Assist individuals in finding jobs and educational opportunities Assist businesses with their development and growth Provide current information Provide recreational reading resources, media materials, and programs Promote public use of modern information technology

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

Howell Carnegie District Library

314 W Grand River, Howell, Michigan, 48843, US
Last Update: 2025-11-27
Between 750 and 799

Our Mission: to create opportunities that transform lives through knowledge for every age at any stage, one exceptional experience at a time Description: The library unites the old and new in its structure, as well as its contents. The original Carnegie building was completed in 1906 with money from philanthropist Andrew Carnegie and some local funds. The renovation and addition project were completed in 1991 and made possible through a bond issue. The new facility quadrupled the space available to meet the needs of our growing community.

NAICS: 519
NAICS Definition:
Employees: 25
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/st.-louis-public-library.jpeg
St. Louis 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/howell-carnegie-district-library.jpeg
Howell Carnegie District 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
St. Louis Public Library
100%
Compliance Rate
0/4 Standards Verified
Howell Carnegie District Library
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for St. Louis Public Library in 2025.

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Howell Carnegie District Library in 2025.

Incident History — St. Louis Public Library (X = Date, Y = Severity)

St. Louis Public Library cyber incidents detection timeline including parent company and subsidiaries

Incident History — Howell Carnegie District Library (X = Date, Y = Severity)

Howell Carnegie District Library cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/st.-louis-public-library.jpeg
St. Louis Public Library
Incidents

No Incident

https://images.rankiteo.com/companyimages/howell-carnegie-district-library.jpeg
Howell Carnegie District Library
Incidents

No Incident

FAQ

Howell Carnegie District Library company demonstrates a stronger AI Cybersecurity Score compared to St. Louis Public Library company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Howell Carnegie District Library company has disclosed a higher number of cyber incidents compared to St. Louis Public Library company.

In the current year, Howell Carnegie District Library company and St. Louis Public Library company have not reported any cyber incidents.

Neither Howell Carnegie District Library company nor St. Louis Public Library company has reported experiencing a ransomware attack publicly.

Neither Howell Carnegie District Library company nor St. Louis Public Library company has reported experiencing a data breach publicly.

Neither Howell Carnegie District Library company nor St. Louis Public Library company has reported experiencing targeted cyberattacks publicly.

Neither St. Louis Public Library company nor Howell Carnegie District Library company has reported experiencing or disclosing vulnerabilities publicly.

Neither St. Louis Public Library nor Howell Carnegie District Library holds any compliance certifications.

Neither company holds any compliance certifications.

Neither St. Louis Public Library company nor Howell Carnegie District Library company has publicly disclosed detailed information about the number of their subsidiaries.

St. Louis Public Library company employs more people globally than Howell Carnegie District Library company, reflecting its scale as a Libraries.

Neither St. Louis Public Library nor Howell Carnegie District Library holds SOC 2 Type 1 certification.

Neither St. Louis Public Library nor Howell Carnegie District Library holds SOC 2 Type 2 certification.

Neither St. Louis Public Library nor Howell Carnegie District Library holds ISO 27001 certification.

Neither St. Louis Public Library nor Howell Carnegie District Library holds PCI DSS certification.

Neither St. Louis Public Library nor Howell Carnegie District Library holds HIPAA certification.

Neither St. Louis Public Library nor Howell Carnegie District 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