Comparison Overview

Do Space

VS

Berkshire Athenaeum

Do Space

5111 N 90th St, Omaha, Nebraska, 68134, US
Last Update: 2025-11-25
Between 750 and 799

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

Berkshire Athenaeum

None
Last Update: 2025-11-25

The Berkshire Athenaeum, Pittsfield's public library, exists to initiate, nurture and feed a passion for knowledge and learning. The library offers people of all ages the materials and services necessary to satisfy an appetite for information about popular cultural and social trends and their desire for enjoyable recreational experiences; enables older children and adults to explore personal, historical and cultural heritage; supplies the means for individuals to continue to learn throughout their lives; and provides the sophisticated information services needed to answer their questions; all in a welcoming setting for people to engage with others and discuss a variety of community issues.

NAICS: 51912
NAICS Definition: Libraries and Archives
Employees: 30
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/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
https://images.rankiteo.com/companyimages/berkshire-athenaeum.jpeg
Berkshire Athenaeum
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
Do Space
100%
Compliance Rate
0/4 Standards Verified
Berkshire Athenaeum
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Do Space in 2025.

Incidents vs Libraries Industry Average (This Year)

No incidents recorded for Berkshire Athenaeum in 2025.

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

Do Space cyber incidents detection timeline including parent company and subsidiaries

Incident History — Berkshire Athenaeum (X = Date, Y = Severity)

Berkshire Athenaeum cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

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

No Incident

https://images.rankiteo.com/companyimages/berkshire-athenaeum.jpeg
Berkshire Athenaeum
Incidents

No Incident

FAQ

Berkshire Athenaeum company demonstrates a stronger AI Cybersecurity Score compared to Do Space company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Berkshire Athenaeum company has disclosed a higher number of cyber incidents compared to Do Space company.

In the current year, Berkshire Athenaeum company and Do Space company have not reported any cyber incidents.

Neither Berkshire Athenaeum company nor Do Space company has reported experiencing a ransomware attack publicly.

Neither Berkshire Athenaeum company nor Do Space company has reported experiencing a data breach publicly.

Neither Berkshire Athenaeum company nor Do Space company has reported experiencing targeted cyberattacks publicly.

Neither Do Space company nor Berkshire Athenaeum company has reported experiencing or disclosing vulnerabilities publicly.

Neither Do Space nor Berkshire Athenaeum holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Do Space company nor Berkshire Athenaeum company has publicly disclosed detailed information about the number of their subsidiaries.

Berkshire Athenaeum company employs more people globally than Do Space company, reflecting its scale as a Libraries.

Neither Do Space nor Berkshire Athenaeum holds SOC 2 Type 1 certification.

Neither Do Space nor Berkshire Athenaeum holds SOC 2 Type 2 certification.

Neither Do Space nor Berkshire Athenaeum holds ISO 27001 certification.

Neither Do Space nor Berkshire Athenaeum holds PCI DSS certification.

Neither Do Space nor Berkshire Athenaeum holds HIPAA certification.

Neither Do Space nor Berkshire Athenaeum 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