Comparison Overview

Cary Library

VS

Camas Public Library

Cary Library

107 Main St, Houlton, Maine, US, 04730-2196
Last Update: 2025-11-27
View Profile
Between 750 and 799
http://www.cary.lib.me.us

The Cary Library in Houlton, Maine is a cultural and intellectual center for the community. It provides, at a reasonable cost and in a friendly atmosphere, universal access to knowledge and lifelong learning through print, electronic resources, cultural activities, programs and services. The library collaborates with other community groups to meet the educational, informational and recreational needs of the entire community.

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

Camas Public Library

625 NE 4th Ave, Camas, Washington, 98607, US
Last Update: 2025-11-22
Between 750 and 799
http://www.camaslibrary.org

Camas Public Library is the only independent, municipal library in Clark County, Washington. While its jurisdiction extends to the city limits of Camas, through reciprocal borrowing agreements the Library serves patrons throughout the region. Likewise, Camas residents enjoy borrowing privileges at most Pacific Northwest libraries. The Library prides itself on being a community hub in the bustling downtown Camas core, and hosts many organizations' meetings and events in addition to their own programs. The gorgeous building, renovated in 2002 thanks to a taxpayer-approved bond, is approximately 35,000 square feet and held 96,742 volumes at the end of 2020.

NAICS: 519
NAICS Definition:
Employees: 13
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/defaultcompany.jpeg
Cary 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/camas-public-library.jpeg
Camas 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
Cary Library
100%
Compliance Rate
0/4 Standards Verified
Camas Public Library
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Cary Library in 2025.

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Camas Public Library in 2025.

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

Cary Library cyber incidents detection timeline including parent company and subsidiaries

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

Camas 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/defaultcompany.jpeg
Cary Library
Incidents

No Incident

https://images.rankiteo.com/companyimages/camas-public-library.jpeg
Camas Public Library
Incidents

No Incident

FAQ

Cary Library company demonstrates a stronger AI Cybersecurity Score compared to Camas Public Library company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

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

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

Neither Camas Public Library company nor Cary Library company has reported experiencing a ransomware attack publicly.

Neither Camas Public Library company nor Cary Library company has reported experiencing a data breach publicly.

Neither Camas Public Library company nor Cary Library company has reported experiencing targeted cyberattacks publicly.

Neither Cary Library company nor Camas Public Library company has reported experiencing or disclosing vulnerabilities publicly.

Neither Cary Library nor Camas Public Library holds any compliance certifications.

Neither company holds any compliance certifications.

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

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

Neither Cary Library nor Camas Public Library holds SOC 2 Type 1 certification.

Neither Cary Library nor Camas Public Library holds SOC 2 Type 2 certification.

Neither Cary Library nor Camas Public Library holds ISO 27001 certification.

Neither Cary Library nor Camas Public Library holds PCI DSS certification.

Neither Cary Library nor Camas Public Library holds HIPAA certification.

Neither Cary Library nor Camas 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