Comparison Overview

Porter County Public Library System

VS

BC Libraries Cooperative

Porter County Public Library System

None
Last Update: 2025-11-21
View Profile
Between 750 and 799
http://pcpls.org

We believe that libraries can change people’s lives and are a cornerstone of our democracy. The mission of the Porter County Public Library System is to provide all residents of the library district with a comprehensive collection of materials in a variety of media that records human knowledge, ideas, and culture and to organize these materials for ready access. The library encourages the love of reading and the joy of learning, and offers the assistance people need to find, evaluate, and use electronic and print information resources that help them live successful and rewarding lives. PCPLS has served porter county since 1905. Today, it consists of 5 branches and nearly 100 staff members, and has the third largest genealogy collection in the state of Indiana.

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

BC Libraries Cooperative

undefined, Vancouver, BC, undefined, CA
Last Update: 2025-11-27
Between 750 and 799
https://bc.libraries.coop/

The BC Libraries Coop is a community service cooperative with over 200 Canadian member organizations. We specialize in open-source technology, accessible publishing for people with print disabilities, and library advocacy. Our mission is to provide libraries and related organizations with essential services, cost savings, and support to amplify their impact in Canadian communities. Sign up for our quarterly newsletter: https://bc.libraries.coop/subscribe/

NAICS: 519
NAICS Definition:
Employees: 17
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
Porter County Public Library System
—
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/bc-libraries-cooperative.jpeg
BC Libraries Cooperative
—
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
Porter County Public Library System
100%
Compliance Rate
0/4 Standards Verified
BC Libraries Cooperative
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Porter County Public Library System in 2025.

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for BC Libraries Cooperative in 2025.

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

Porter County Public Library System cyber incidents detection timeline including parent company and subsidiaries

Incident History — BC Libraries Cooperative (X = Date, Y = Severity)

BC Libraries Cooperative 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
Porter County Public Library System
Incidents

No Incident

https://images.rankiteo.com/companyimages/bc-libraries-cooperative.jpeg
BC Libraries Cooperative
Incidents

No Incident

FAQ

Porter County Public Library System company demonstrates a stronger AI Cybersecurity Score compared to BC Libraries Cooperative company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, BC Libraries Cooperative company has disclosed a higher number of cyber incidents compared to Porter County Public Library System company.

In the current year, BC Libraries Cooperative company and Porter County Public Library System company have not reported any cyber incidents.

Neither BC Libraries Cooperative company nor Porter County Public Library System company has reported experiencing a ransomware attack publicly.

Neither BC Libraries Cooperative company nor Porter County Public Library System company has reported experiencing a data breach publicly.

Neither BC Libraries Cooperative company nor Porter County Public Library System company has reported experiencing targeted cyberattacks publicly.

Neither Porter County Public Library System company nor BC Libraries Cooperative company has reported experiencing or disclosing vulnerabilities publicly.

Neither Porter County Public Library System nor BC Libraries Cooperative holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Porter County Public Library System company nor BC Libraries Cooperative company has publicly disclosed detailed information about the number of their subsidiaries.

Porter County Public Library System company employs more people globally than BC Libraries Cooperative company, reflecting its scale as a Libraries.

Neither Porter County Public Library System nor BC Libraries Cooperative holds SOC 2 Type 1 certification.

Neither Porter County Public Library System nor BC Libraries Cooperative holds SOC 2 Type 2 certification.

Neither Porter County Public Library System nor BC Libraries Cooperative holds ISO 27001 certification.

Neither Porter County Public Library System nor BC Libraries Cooperative holds PCI DSS certification.

Neither Porter County Public Library System nor BC Libraries Cooperative holds HIPAA certification.

Neither Porter County Public Library System nor BC Libraries Cooperative 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