Comparison Overview

Coquitlam Public Library

VS

Peoria Public Library

Coquitlam Public Library

575 Poirier St., Coquitlam, BC, CA, V3J 6A9
Last Update: 2025-11-27
View Profile
Between 750 and 799
http://www.coqlibrary.ca

The Coquitlam Public Library features two branches, a Library Link mobile service, and an online branch through our website. Open seven days a week except for holidays. Our collection reflects the needs of our community and includes the French tradition of Maillardville, as well as Chinese, Korean, Farsi and Spanish items. Offering collections and online services to meet most needs, meeting rooms from 2 to 80, two computer labs, Wi-Fi, and silent and collaborative study spaces, plus our Library Lounge full of board games and our Discovery Lab—where customers can peruse a variety of lendable tech and online resources.

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

Peoria Public Library

107 NE Monroe St., Peoria, Illinois, 61602, US
Last Update: 2025-11-27
Between 750 and 799
http://www.peoriapubliclibrary.org

The Peoria Public Library, founded in 1880, is a tax-funded library system serving the city of Peoria, Illinois. A recent $28 million building program created a state-of-the-art library system including five completely renovated or newly-constructed library branch locations. A Bookmobile and Outreach Services provide services to those unable to go to a library location.

NAICS: 519
NAICS Definition:
Employees: 72
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/coquitlam-public-library.jpeg
Coquitlam 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/peoria-public-library.jpeg
Peoria 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
Coquitlam Public Library
100%
Compliance Rate
0/4 Standards Verified
Peoria Public Library
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Coquitlam Public Library in 2025.

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Peoria Public Library in 2025.

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

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

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

Peoria 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/coquitlam-public-library.jpeg
Coquitlam Public Library
Incidents

No Incident

https://images.rankiteo.com/companyimages/peoria-public-library.jpeg
Peoria Public Library
Incidents

No Incident

FAQ

Both Coquitlam Public Library company and Peoria Public Library company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Peoria Public Library company has disclosed a higher number of cyber incidents compared to Coquitlam Public Library company.

In the current year, Peoria Public Library company and Coquitlam Public Library company have not reported any cyber incidents.

Neither Peoria Public Library company nor Coquitlam Public Library company has reported experiencing a ransomware attack publicly.

Neither Peoria Public Library company nor Coquitlam Public Library company has reported experiencing a data breach publicly.

Neither Peoria Public Library company nor Coquitlam Public Library company has reported experiencing targeted cyberattacks publicly.

Neither Coquitlam Public Library company nor Peoria Public Library company has reported experiencing or disclosing vulnerabilities publicly.

Neither Coquitlam Public Library nor Peoria Public Library holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Coquitlam Public Library company nor Peoria Public Library company has publicly disclosed detailed information about the number of their subsidiaries.

Peoria Public Library company employs more people globally than Coquitlam Public Library company, reflecting its scale as a Libraries.

Neither Coquitlam Public Library nor Peoria Public Library holds SOC 2 Type 1 certification.

Neither Coquitlam Public Library nor Peoria Public Library holds SOC 2 Type 2 certification.

Neither Coquitlam Public Library nor Peoria Public Library holds ISO 27001 certification.

Neither Coquitlam Public Library nor Peoria Public Library holds PCI DSS certification.

Neither Coquitlam Public Library nor Peoria Public Library holds HIPAA certification.

Neither Coquitlam Public Library nor Peoria 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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References