Comparison Overview

Yellowhead Regional Library

VS

Faulkner County Library

Yellowhead Regional Library

433 King St, Spruce Grove, Alberta, T7X 2C6, CA
Last Update: 2025-11-27
Between 750 and 799

Established in 1971, the Yellowhead Regional Library (YRL) is a co-operative library system that provides bibliographic, client and communications services to member public and school libraries within the region. To provide its members with a broader spectrum of services, YRL partners with three other regional libraries in Alberta to form TRAC (The Regional Automation Consortium). This partnership allows for quicker circulation between member libraries and gives patrons access to an online catalogue with nearly 3,000,000 items and more than 800,000 titles. YRL currently serves 261,160 Albertans and 13,136 full-time equivalent students in 54 municipalities and four school divisions. For more information on the services we provide, please visit www.yrl.ab.ca.

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

Faulkner County Library

1900 Tyler St, Conway, 72032-3240, US
Last Update:
Between 750 and 799

Founded in 1954, the Faulkner-Van Buren Regional Library System serves the residents of Faulkner and Van Buren counties with eight branches as well as the main library based out of 1900 Tyler St, Conway, Arkansas, United States. Our mission is to open access to ideas and communities through shared collections, shared spaces, and shared activities.

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/yellowhead-regional-library.jpeg
Yellowhead Regional 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/faulkner-county-library.jpeg
Faulkner County 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
Yellowhead Regional Library
100%
Compliance Rate
0/4 Standards Verified
Faulkner County Library
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Yellowhead Regional Library in 2025.

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Faulkner County Library in 2025.

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

Yellowhead Regional Library cyber incidents detection timeline including parent company and subsidiaries

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

Faulkner County Library cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/yellowhead-regional-library.jpeg
Yellowhead Regional Library
Incidents

No Incident

https://images.rankiteo.com/companyimages/faulkner-county-library.jpeg
Faulkner County Library
Incidents

No Incident

FAQ

Both Yellowhead Regional Library company and Faulkner County Library company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Faulkner County Library company has disclosed a higher number of cyber incidents compared to Yellowhead Regional Library company.

In the current year, Faulkner County Library company and Yellowhead Regional Library company have not reported any cyber incidents.

Neither Faulkner County Library company nor Yellowhead Regional Library company has reported experiencing a ransomware attack publicly.

Neither Faulkner County Library company nor Yellowhead Regional Library company has reported experiencing a data breach publicly.

Neither Faulkner County Library company nor Yellowhead Regional Library company has reported experiencing targeted cyberattacks publicly.

Neither Yellowhead Regional Library company nor Faulkner County Library company has reported experiencing or disclosing vulnerabilities publicly.

Neither Yellowhead Regional Library nor Faulkner County Library holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Yellowhead Regional Library company nor Faulkner County Library company has publicly disclosed detailed information about the number of their subsidiaries.

Faulkner County Library company employs more people globally than Yellowhead Regional Library company, reflecting its scale as a Libraries.

Neither Yellowhead Regional Library nor Faulkner County Library holds SOC 2 Type 1 certification.

Neither Yellowhead Regional Library nor Faulkner County Library holds SOC 2 Type 2 certification.

Neither Yellowhead Regional Library nor Faulkner County Library holds ISO 27001 certification.

Neither Yellowhead Regional Library nor Faulkner County Library holds PCI DSS certification.

Neither Yellowhead Regional Library nor Faulkner County Library holds HIPAA certification.

Neither Yellowhead Regional Library nor Faulkner County 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