Comparison Overview

Friedman Place

VS

Community Action Partnership of Utah

Friedman Place

5527 North Maplewood Avenue, Chicago, 60625, US
Last Update: 2025-11-21
Between 750 and 799

Friedman Place is a non-profit Supportive Living Community for blind and visually impaired adults in Chicago. Our building has been designed with the needs of the blind and visually impaired in mind. Each resident has a private studio or one-bedroom apartment, with a kitchenette and bathroom. A full range of services and activities is provided so that residents’ days are healthy, dignified, and stimulating.

NAICS: 923
NAICS Definition: Administration of Human Resource Programs
Employees: 40
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Community Action Partnership of Utah

875 E Highway 193, Layton, Utah, 84040, US
Last Update: 2025-11-21
Between 750 and 799

Community Action Partnership of Utah (CAP Utah) is the statewide association of the Community Action Agencies in Utah. The Community Action Agencies in Utah envision an end to poverty. Our member agencies work toward this vision every day as we provide services to low-income families and individuals across the state. CAP Utah advocates for, supports, and provides training and technical assistance to Utah's CSBG funded agencies, utilizing our collective strength to address the causes of poverty. Our advocacy focuses on low-income housing and work supports. The Promise of Community Action: Community Action changes people’s lives, embodies the spirit of hope, improves communities, and makes America a better place to live. We care about the entire community, and we are dedicated to helping people help themselves and each other. See if you qualify for free or discounted internet through the Affordable Connectivity Program: https://bit.ly/3SccCpo Let us do a poverty simulation for you: https://bit.ly/46JOVtc Help us fulfill our mission through a donation: https://bit.ly/495di6b Volunteer: https://bit.ly/470MjH2

NAICS: 923
NAICS Definition:
Employees: 9
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/friedman-place.jpeg
Friedman Place
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/community-action-partnership-of-utah.jpeg
Community Action Partnership of Utah
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
Friedman Place
100%
Compliance Rate
0/4 Standards Verified
Community Action Partnership of Utah
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Health and Human Services Industry Average (This Year)

No incidents recorded for Friedman Place in 2025.

Incidents vs Health and Human Services Industry Average (This Year)

No incidents recorded for Community Action Partnership of Utah in 2025.

Incident History — Friedman Place (X = Date, Y = Severity)

Friedman Place cyber incidents detection timeline including parent company and subsidiaries

Incident History — Community Action Partnership of Utah (X = Date, Y = Severity)

Community Action Partnership of Utah cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/friedman-place.jpeg
Friedman Place
Incidents

No Incident

https://images.rankiteo.com/companyimages/community-action-partnership-of-utah.jpeg
Community Action Partnership of Utah
Incidents

No Incident

FAQ

Friedman Place company demonstrates a stronger AI Cybersecurity Score compared to Community Action Partnership of Utah company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Community Action Partnership of Utah company has disclosed a higher number of cyber incidents compared to Friedman Place company.

In the current year, Community Action Partnership of Utah company and Friedman Place company have not reported any cyber incidents.

Neither Community Action Partnership of Utah company nor Friedman Place company has reported experiencing a ransomware attack publicly.

Neither Community Action Partnership of Utah company nor Friedman Place company has reported experiencing a data breach publicly.

Neither Community Action Partnership of Utah company nor Friedman Place company has reported experiencing targeted cyberattacks publicly.

Neither Friedman Place company nor Community Action Partnership of Utah company has reported experiencing or disclosing vulnerabilities publicly.

Neither Friedman Place nor Community Action Partnership of Utah holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Friedman Place company nor Community Action Partnership of Utah company has publicly disclosed detailed information about the number of their subsidiaries.

Friedman Place company employs more people globally than Community Action Partnership of Utah company, reflecting its scale as a Health and Human Services.

Neither Friedman Place nor Community Action Partnership of Utah holds SOC 2 Type 1 certification.

Neither Friedman Place nor Community Action Partnership of Utah holds SOC 2 Type 2 certification.

Neither Friedman Place nor Community Action Partnership of Utah holds ISO 27001 certification.

Neither Friedman Place nor Community Action Partnership of Utah holds PCI DSS certification.

Neither Friedman Place nor Community Action Partnership of Utah holds HIPAA certification.

Neither Friedman Place nor Community Action Partnership of Utah 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