Comparison Overview

Athenaeum of Philadelphia

VS

Boyle County Public Library

Athenaeum of Philadelphia

219 South 6th Street, Philadelphia, PA, 19106, US
Last Update: 2025-11-25

Established in 1814 as a subscription library, the Athenaeum of Philadelphia is now a library and museum, with a lending collection for members plus research and museum collections open to the public. Housed in a National Historic Landmark building, the Athenaeum includes a collection of paintings, sculpture, and decorative arts primarily from the mid-19th century. Its gallery often features its own collections, but it also reaches out to contemporary arts. The Athenaeum is open 9 am to 7 pm on Mondays; 9 am to 5 pm Tuesday, Thursday, and Friday, 10 am to 5 pm on Wednesdays; and Saturdays from 10 am to 3 pm. The Athenaeum also features an active archival scanning facility, designed to scan archival and precious materials in a safe environment.

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

Boyle County Public Library

307 West Broadway, Danville, KY, 40422, US
Last Update: 2025-11-27
Between 750 and 799

The Boyle County Public Library finished a major expansion & renovation of the downtown building on January 10th, 2010. Thanks to generous donors from the The Campaign for the Library and especially those members of the Benjamin Franklin Circle, we are able to provide a state of the art 21st century library to our patrons and the Danville-Boyle County community. We are now located at our original address of 307 West Broadway in historic downtown Danville, KY. Hours for the grand opening week (January 10th-16th) are revised on our hours page. See what great things are happening at the new Library here!

NAICS: 519
NAICS Definition:
Employees: 28
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/athenaeum-of-philadelphia.jpeg
Athenaeum of Philadelphia
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/boyle-county-public-library.jpeg
Boyle 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
Athenaeum of Philadelphia
100%
Compliance Rate
0/4 Standards Verified
Boyle 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 Athenaeum of Philadelphia in 2025.

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Boyle County Public Library in 2025.

Incident History — Athenaeum of Philadelphia (X = Date, Y = Severity)

Athenaeum of Philadelphia cyber incidents detection timeline including parent company and subsidiaries

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

Boyle 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/athenaeum-of-philadelphia.jpeg
Athenaeum of Philadelphia
Incidents

No Incident

https://images.rankiteo.com/companyimages/boyle-county-public-library.jpeg
Boyle County Public Library
Incidents

No Incident

FAQ

Boyle County Public Library company demonstrates a stronger AI Cybersecurity Score compared to Athenaeum of Philadelphia company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Boyle County Public Library company has disclosed a higher number of cyber incidents compared to Athenaeum of Philadelphia company.

In the current year, Boyle County Public Library company and Athenaeum of Philadelphia company have not reported any cyber incidents.

Neither Boyle County Public Library company nor Athenaeum of Philadelphia company has reported experiencing a ransomware attack publicly.

Neither Boyle County Public Library company nor Athenaeum of Philadelphia company has reported experiencing a data breach publicly.

Neither Boyle County Public Library company nor Athenaeum of Philadelphia company has reported experiencing targeted cyberattacks publicly.

Neither Athenaeum of Philadelphia company nor Boyle County Public Library company has reported experiencing or disclosing vulnerabilities publicly.

Neither Athenaeum of Philadelphia nor Boyle County Public Library holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Athenaeum of Philadelphia company nor Boyle County Public Library company has publicly disclosed detailed information about the number of their subsidiaries.

Boyle County Public Library company employs more people globally than Athenaeum of Philadelphia company, reflecting its scale as a Libraries.

Neither Athenaeum of Philadelphia nor Boyle County Public Library holds SOC 2 Type 1 certification.

Neither Athenaeum of Philadelphia nor Boyle County Public Library holds SOC 2 Type 2 certification.

Neither Athenaeum of Philadelphia nor Boyle County Public Library holds ISO 27001 certification.

Neither Athenaeum of Philadelphia nor Boyle County Public Library holds PCI DSS certification.

Neither Athenaeum of Philadelphia nor Boyle County Public Library holds HIPAA certification.

Neither Athenaeum of Philadelphia nor Boyle County 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.

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