Comparison Overview

Los Angeles Public Library

VS

Do Space

Los Angeles Public Library

undefined, undefined, undefined, undefined, US
Last Update: 2025-11-27
View Profile
Between 750 and 799
http://www.lapl.org

The Los Angeles Public Library provides free and easy access to information, ideas, books and technology that enrich, educate and empower every individual in our city's diverse communities. The Los Angeles Public Library serves the largest and most diverse population in the U.S. through its Central Library, 72 branches, electronic resources at www.lapl.org and programs for all ages. It is a department of the City of Los Angeles and is governed by the Board of Library Commissioners, which sets policies and is a strong library advocate with the public and elected officials.

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

Do Space

5111 N 90th St, Omaha, Nebraska, 68134, US
Last Update: 2025-11-25
Between 750 and 799
http://www.dospace.org

Do Space is a community technology library dedicated to empowering our community through access to technology and innovative learning experiences. Do Space is operated by Community Information Trust, which is a 501c3 nonprofit organization. Community technology libraries are the next step in the democratization of information, learning, and knowledge. Do Space is a technological space for thinkers, makers, learners, and doers. At Do Space, you can do - improve your life, change jobs, learn something, scratch a creative itch, or start a business. This is just the beginning of a movement to tackle the digital divide in our community, boost digital skills, and drive innovation, creativity, and invention in the region.

NAICS: 51912
NAICS Definition: Libraries and Archives
Employees: 24
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/los-angeles-public-library.jpeg
Los Angeles 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/do-space.jpeg
Do Space
—
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
Los Angeles Public Library
100%
Compliance Rate
0/4 Standards Verified
Do Space
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Los Angeles Public Library in 2025.

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Do Space in 2025.

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

Los Angeles Public Library cyber incidents detection timeline including parent company and subsidiaries

Incident History — Do Space (X = Date, Y = Severity)

Do Space cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/los-angeles-public-library.jpeg
Los Angeles Public Library
Incidents

No Incident

https://images.rankiteo.com/companyimages/do-space.jpeg
Do Space
Incidents

No Incident

FAQ

Los Angeles Public Library company demonstrates a stronger AI Cybersecurity Score compared to Do Space company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Do Space company has disclosed a higher number of cyber incidents compared to Los Angeles Public Library company.

In the current year, Do Space company and Los Angeles Public Library company have not reported any cyber incidents.

Neither Do Space company nor Los Angeles Public Library company has reported experiencing a ransomware attack publicly.

Neither Do Space company nor Los Angeles Public Library company has reported experiencing a data breach publicly.

Neither Do Space company nor Los Angeles Public Library company has reported experiencing targeted cyberattacks publicly.

Neither Los Angeles Public Library company nor Do Space company has reported experiencing or disclosing vulnerabilities publicly.

Neither Los Angeles Public Library nor Do Space holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Los Angeles Public Library company nor Do Space company has publicly disclosed detailed information about the number of their subsidiaries.

Los Angeles Public Library company employs more people globally than Do Space company, reflecting its scale as a Libraries.

Neither Los Angeles Public Library nor Do Space holds SOC 2 Type 1 certification.

Neither Los Angeles Public Library nor Do Space holds SOC 2 Type 2 certification.

Neither Los Angeles Public Library nor Do Space holds ISO 27001 certification.

Neither Los Angeles Public Library nor Do Space holds PCI DSS certification.

Neither Los Angeles Public Library nor Do Space holds HIPAA certification.

Neither Los Angeles Public Library nor Do Space 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