Comparison Overview

Peabody Public Library

VS

Laramie County Library System

Peabody Public Library

1160 E State Road 205, Columbia City, Indiana, US, 46725-9001
Last Update: 2025-11-25
Between 750 and 799

Our Mission: Building Community. Encouraging Exploration. Connecting With The World. Our Values and Beliefs: We believe: - Everyone has the right to library services. - Everyone has the right to privacy and diversity. - The library is more than just books, materials and technology. - The Peabody Public Library will strive for excellence in serving the community with a friendly and inviting environment. - The Library is the community’s center for life-long education. - The library must be responsive to the current and future needs and requests of the community. - We believe in operating as a fiscally responsible organization. - We believe the library is a vital component to the quality of life in the community. Our Vision: The Peabody Public Library will participate fully in promoting the vitality and growth of a community of readers, learners, doers and dreamers by providing access to ever evolving technology, resources and educational opportunities. Our Service Area: The Peabody Public Library is supported by property taxes from Columbia City, Columbia Township, and Thorncreek Township. Memberships and Affiliations The Peabody Public Library is a member of Evergreen Indiana , Northern Indiana Computer Consortium for Libraries and Northeast Indiana Libraries Serving Communities consortia. In addition, the Peabody Public Library holds memberships to the Indiana Library Federation, American Library Association, the Association of Rural and Small Libraries, and the Whitley County Chamber of Commerce. The Peabody Public Library endorses and is guided by the American Library Association’s Library Bill of Rights and Freedom to Read Statement that recognizes the individual’s right to unencumbered access and free exchange of information and ideas vital to an informed citizenry.

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

Laramie County Library System

2200 Pioneer Ave, Cheyenne, WY, 82001, US
Last Update: 2025-11-25
Between 750 and 799

Our mission is to serve the people of Laramie County by encouraging and supporting lifelong learning and adventure. Our vision is to provide opportunities that empower everyone to reach their full potential. Our commitment is to: -Provide free and easy access to the printed word, information and cultural enhancement; -Promote reading and literacy for children and adults; -Offer a dynamic, current, pertinent and uncensored collection of materials in a variety of formats; -Maintain high quality customer service through well-trained professional librarians, managers, staff and volunteers; -Strengthen the library by developing, maintaining and sharing resources in a responsible manner; -Be a focal point for access to information, self-improvement, social interaction, cultural exposure and leisure; -Remain committed to continually utilizing and providing state of the art technology and digital resources; -Provide appropriate facilities to meet the needs of all people of Laramie County; and -Promote the services of the library. Adopted November 22, 2016 by the Laramie County Library System Board of Directors.

NAICS: 51912
NAICS Definition: Libraries and Archives
Employees: 62
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/peabody-public-library.jpeg
Peabody 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/laramie-county-library-system.jpeg
Laramie County 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
Compliance Summary
Peabody Public Library
100%
Compliance Rate
0/4 Standards Verified
Laramie County Library System
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Peabody Public Library in 2025.

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Laramie County Library System in 2025.

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

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

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

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

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/peabody-public-library.jpeg
Peabody Public Library
Incidents

No Incident

https://images.rankiteo.com/companyimages/laramie-county-library-system.jpeg
Laramie County Library System
Incidents

No Incident

FAQ

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

Historically, Laramie County Library System company has disclosed a higher number of cyber incidents compared to Peabody Public Library company.

In the current year, Laramie County Library System company and Peabody Public Library company have not reported any cyber incidents.

Neither Laramie County Library System company nor Peabody Public Library company has reported experiencing a ransomware attack publicly.

Neither Laramie County Library System company nor Peabody Public Library company has reported experiencing a data breach publicly.

Neither Laramie County Library System company nor Peabody Public Library company has reported experiencing targeted cyberattacks publicly.

Neither Peabody Public Library company nor Laramie County Library System company has reported experiencing or disclosing vulnerabilities publicly.

Neither Peabody Public Library nor Laramie County Library System holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Peabody Public Library company nor Laramie County Library System company has publicly disclosed detailed information about the number of their subsidiaries.

Laramie County Library System company employs more people globally than Peabody Public Library company, reflecting its scale as a Libraries.

Neither Peabody Public Library nor Laramie County Library System holds SOC 2 Type 1 certification.

Neither Peabody Public Library nor Laramie County Library System holds SOC 2 Type 2 certification.

Neither Peabody Public Library nor Laramie County Library System holds ISO 27001 certification.

Neither Peabody Public Library nor Laramie County Library System holds PCI DSS certification.

Neither Peabody Public Library nor Laramie County Library System holds HIPAA certification.

Neither Peabody Public Library nor Laramie County Library System 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