Comparison Overview

Howe Library

VS

Maryland State Library for the Blind and Physically Handicapped

Howe Library

13 South Street, Hanover, New Hampshire, 03755, US
Last Update: 2025-11-27
Between 750 and 799

The Howe Library was established as Hanover, New Hampshire’s public library in 1900 through a gift from Emily Howe to the newly-formed non-profit Howe Library Corporation. Miss Howe dedicated the first Howe Library in her former family home on West Wheelock Street with “a prayer that this library may prove a blessing to this community to the remotest generation.” The Howe Library Corporation managed the library and its operating budget until 1973 when Hanover residents voted to assume responsibility for the operating budget and the library became a department of the town. At the same time, the library was outgrowing its home on West Wheelock Street and plans began for a new building. Constructed on town land in 1973, this new facility was financed by The Howe Library Corporation with a loan from the town and donations. A large addition was completed in 2005, almost doubling the size. The Howe Library continues to be a partnership between the Howe Library Corporation and the Town of Hanover.

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

Maryland State Library for the Blind and Physically Handicapped

21201, US
Last Update: 2025-11-27
Between 800 and 849

The library is part of the National Library Service of the Library of Congress. We are the regional library for the state of Maryland and serve all eligible people with print disabilities. We have digital books, cassettes, Braille and large print. We provide programs, training, readers advisory. We serve the entire state.

NAICS: 51912
NAICS Definition: Libraries and Archives
Employees: 21
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/howe-library.jpeg
Howe 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/defaultcompany.jpeg
Maryland State Library for the Blind and Physically Handicapped
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
Howe Library
100%
Compliance Rate
0/4 Standards Verified
Maryland State Library for the Blind and Physically Handicapped
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Howe Library in 2025.

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Maryland State Library for the Blind and Physically Handicapped in 2025.

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

Howe Library cyber incidents detection timeline including parent company and subsidiaries

Incident History — Maryland State Library for the Blind and Physically Handicapped (X = Date, Y = Severity)

Maryland State Library for the Blind and Physically Handicapped cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/howe-library.jpeg
Howe Library
Incidents

No Incident

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Maryland State Library for the Blind and Physically Handicapped
Incidents

No Incident

FAQ

Maryland State Library for the Blind and Physically Handicapped company demonstrates a stronger AI Cybersecurity Score compared to Howe Library company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Maryland State Library for the Blind and Physically Handicapped company has disclosed a higher number of cyber incidents compared to Howe Library company.

In the current year, Maryland State Library for the Blind and Physically Handicapped company and Howe Library company have not reported any cyber incidents.

Neither Maryland State Library for the Blind and Physically Handicapped company nor Howe Library company has reported experiencing a ransomware attack publicly.

Neither Maryland State Library for the Blind and Physically Handicapped company nor Howe Library company has reported experiencing a data breach publicly.

Neither Maryland State Library for the Blind and Physically Handicapped company nor Howe Library company has reported experiencing targeted cyberattacks publicly.

Neither Howe Library company nor Maryland State Library for the Blind and Physically Handicapped company has reported experiencing or disclosing vulnerabilities publicly.

Neither Howe Library nor Maryland State Library for the Blind and Physically Handicapped holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Howe Library company nor Maryland State Library for the Blind and Physically Handicapped company has publicly disclosed detailed information about the number of their subsidiaries.

Howe Library company employs more people globally than Maryland State Library for the Blind and Physically Handicapped company, reflecting its scale as a Libraries.

Neither Howe Library nor Maryland State Library for the Blind and Physically Handicapped holds SOC 2 Type 1 certification.

Neither Howe Library nor Maryland State Library for the Blind and Physically Handicapped holds SOC 2 Type 2 certification.

Neither Howe Library nor Maryland State Library for the Blind and Physically Handicapped holds ISO 27001 certification.

Neither Howe Library nor Maryland State Library for the Blind and Physically Handicapped holds PCI DSS certification.

Neither Howe Library nor Maryland State Library for the Blind and Physically Handicapped holds HIPAA certification.

Neither Howe Library nor Maryland State Library for the Blind and Physically Handicapped 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