Comparison Overview

Aya Healthcare

VS

Kelly

Aya Healthcare

5930 Cornerstone Ct #300, None, San Diego, CA, US, 92121
Last Update: 2025-11-25

Aya Healthcare is the largest healthcare talent software and staffing company in the United States. Aya operates the world’s largest digital staffing platform delivering every component of healthcare-focused labor services, including travel nursing and allied health, per diem, permanent staff hiring, interim leadership, locum tenens and non-clinical professionals. Aya’s software suite, which includes vendor management, float pool technology, provider services and predictive analytics, provides hospital systems greater efficiencies and superior operating results. While technology drives efficiency and scale, Aya employees power the company to deliver unparalleled accountability and exceptional experiences for our clients and clinicians. Due to our passionate employees coupled with our unique corporate culture, we've been recognized as a top workplace by Fortune, Inc. Magazine, Modern Healthcare and the San Diego Union-Tribune. To learn more about Aya Healthcare, visit www.ayahealthcare.com

NAICS: 5613
NAICS Definition: Employment Services
Employees: 22,994
Subsidiaries: 0
12-month incidents
1
Known data breaches
1
Attack type number
1

Kelly

999 W Big Beaver Rd, Troy, Michigan, 48084, US
Last Update: 2025-11-26
Between 750 and 799

We’ve been helping organizations find the people they need longer than any other company in the world. Since inventing the staffing industry in 1946, we have become experts in the many industries and markets we serve. With a network of suppliers and partners around the world, we connect more than 450,000 people with work every year.

NAICS: 5613
NAICS Definition: Employment Services
Employees: 18,776
Subsidiaries: 6
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/ayahealthcare.jpeg
Aya Healthcare
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/kellyservices.jpeg
Kelly
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
Aya Healthcare
100%
Compliance Rate
0/4 Standards Verified
Kelly
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Staffing and Recruiting Industry Average (This Year)

Aya Healthcare has 0.0% fewer incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Staffing and Recruiting Industry Average (This Year)

No incidents recorded for Kelly in 2025.

Incident History — Aya Healthcare (X = Date, Y = Severity)

Aya Healthcare cyber incidents detection timeline including parent company and subsidiaries

Incident History — Kelly (X = Date, Y = Severity)

Kelly cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ayahealthcare.jpeg
Aya Healthcare
Incidents

Date Detected: 1/2025
Type:Breach
Attack Vector: Automated Bot
Motivation: Unknown
Blog: Blog
https://images.rankiteo.com/companyimages/kellyservices.jpeg
Kelly
Incidents

No Incident

FAQ

Kelly company demonstrates a stronger AI Cybersecurity Score compared to Aya Healthcare company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Aya Healthcare company has historically faced a number of disclosed cyber incidents, whereas Kelly company has not reported any.

In the current year, Aya Healthcare company has reported more cyber incidents than Kelly company.

Neither Kelly company nor Aya Healthcare company has reported experiencing a ransomware attack publicly.

Aya Healthcare company has disclosed at least one data breach, while the other Kelly company has not reported such incidents publicly.

Neither Kelly company nor Aya Healthcare company has reported experiencing targeted cyberattacks publicly.

Neither Aya Healthcare company nor Kelly company has reported experiencing or disclosing vulnerabilities publicly.

Neither Aya Healthcare nor Kelly holds any compliance certifications.

Neither company holds any compliance certifications.

Kelly company has more subsidiaries worldwide compared to Aya Healthcare company.

Aya Healthcare company employs more people globally than Kelly company, reflecting its scale as a Staffing and Recruiting.

Neither Aya Healthcare nor Kelly holds SOC 2 Type 1 certification.

Neither Aya Healthcare nor Kelly holds SOC 2 Type 2 certification.

Neither Aya Healthcare nor Kelly holds ISO 27001 certification.

Neither Aya Healthcare nor Kelly holds PCI DSS certification.

Neither Aya Healthcare nor Kelly holds HIPAA certification.

Neither Aya Healthcare nor Kelly 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