Comparison Overview

Access Hospital Dayton

VS

Survive First

Access Hospital Dayton

2611 Wayne Avenue, Dayton, OH, 45420, US
Last Update: 2026-01-23
View Profile
Between 750 and 799
http://www.accesshospital.com/

Access Hospital Dayton is a private inpatient mental health and substance abuse treatment facility located in Dayton, Ohio that is licensed by Ohio Mental Health and Addiction Services and accredited by The Joint Commission – the gold standard for health-care! We provide short-term care and long-term solutions for individuals in crisis. We also offer specialized services for: • Older adults • Developmentally disabled adults • Adults with co-occurring drug or alcohol dependence

NAICS: 621
NAICS Definition:
Employees: 86
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Survive First

P.O. Box 320112, Cocoa Beach, 32932, US
Last Update: 2026-01-22
Between 750 and 799
http://www.survivefirst.us

Survive First is a 501(c)3 nonprofit organization, whose mission is to assist first responders and families who need mental health support from the impact of Post Traumatic Stress Disorder, depression, and substance abuse. Through education and appropriate treatment planning and placement,we walk with our brothers and sisters on the road to wellness and recovery. Our vision is to reduce first responder suicide and save lives by ensuring that first responders receive the mental health support they need in order to live healthy and happy lives.

NAICS: 62133
NAICS Definition: Offices of Mental Health Practitioners (except Physicians)
Employees: 12
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/access-hospital-dayton.jpeg
Access Hospital Dayton
—
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/survive-first.jpeg
Survive First
—
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
Access Hospital Dayton
100%
Compliance Rate
0/4 Standards Verified
Survive First
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Mental Health Care Industry Average (This Year)

No incidents recorded for Access Hospital Dayton in 2026.

Incidents vs Mental Health Care Industry Average (This Year)

No incidents recorded for Survive First in 2026.

Incident History — Access Hospital Dayton (X = Date, Y = Severity)

Access Hospital Dayton cyber incidents detection timeline including parent company and subsidiaries

Incident History — Survive First (X = Date, Y = Severity)

Survive First cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/access-hospital-dayton.jpeg
Access Hospital Dayton
Incidents

No Incident

https://images.rankiteo.com/companyimages/survive-first.jpeg
Survive First
Incidents

No Incident

FAQ

Access Hospital Dayton company demonstrates a stronger AI Cybersecurity Score compared to Survive First company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Survive First company has disclosed a higher number of cyber incidents compared to Access Hospital Dayton company.

In the current year, Survive First company and Access Hospital Dayton company have not reported any cyber incidents.

Neither Survive First company nor Access Hospital Dayton company has reported experiencing a ransomware attack publicly.

Neither Survive First company nor Access Hospital Dayton company has reported experiencing a data breach publicly.

Neither Survive First company nor Access Hospital Dayton company has reported experiencing targeted cyberattacks publicly.

Neither Access Hospital Dayton company nor Survive First company has reported experiencing or disclosing vulnerabilities publicly.

Neither Access Hospital Dayton nor Survive First holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Access Hospital Dayton company nor Survive First company has publicly disclosed detailed information about the number of their subsidiaries.

Access Hospital Dayton company employs more people globally than Survive First company, reflecting its scale as a Mental Health Care.

Neither Access Hospital Dayton nor Survive First holds SOC 2 Type 1 certification.

Neither Access Hospital Dayton nor Survive First holds SOC 2 Type 2 certification.

Neither Access Hospital Dayton nor Survive First holds ISO 27001 certification.

Neither Access Hospital Dayton nor Survive First holds PCI DSS certification.

Neither Access Hospital Dayton nor Survive First holds HIPAA certification.

Neither Access Hospital Dayton nor Survive First holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Typemill is a flat-file, Markdown-based CMS designed for informational documentation websites. A reflected Cross-Site Scripting (XSS) exists in the login error view template `login.twig` of versions 2.19.1 and below. The `username` value can be echoed back without proper contextual encoding when authentication fails. An attacker can execute script in the login page context. This issue has been fixed in version 2.19.2.

Published
Date
2026-01-23
Updated
Date
2026-01-23
Risk Information
cvss3
Base: 5.4
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
References
Description

A DOM-based Cross-Site Scripting (XSS) vulnerability exists in the DomainCheckerApp class within domain/script.js of Sourcecodester Domain Availability Checker v1.0. The vulnerability occurs because the application improperly handles user-supplied data in the createResultElement method by using the unsafe innerHTML property to render domain search results.

Published
Date
2026-01-23
Updated
Date
2026-01-23
References
Description

A Remote Code Execution (RCE) vulnerability exists in Sourcecodester Modern Image Gallery App v1.0 within the gallery/upload.php component. The application fails to properly validate uploaded file contents. Additionally, the application preserves the user-supplied file extension during the save process. This allows an unauthenticated attacker to upload arbitrary PHP code by spoofing the MIME type as an image, leading to full system compromise.

Published
Date
2026-01-23
Updated
Date
2026-01-23
References
Description

A UNIX symbolic link following issue in the jailer component in Firecracker version v1.13.1 and earlier and 1.14.0 on Linux may allow a local host user with write access to the pre-created jailer directories to overwrite arbitrary host files via a symlink attack during the initialization copy at jailer startup, if the jailer is executed with root privileges. To mitigate this issue, users should upgrade to version v1.13.2 or 1.14.1 or above.

Published
Date
2026-01-23
Updated
Date
2026-01-23
Risk Information
cvss3
Base: 6.0
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
cvss4
Base: 6.0
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:H/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

An information disclosure vulnerability exists in the /srvs/membersrv/getCashiers endpoint of the Aptsys gemscms backend platform thru 2025-05-28. This unauthenticated endpoint returns a list of cashier accounts, including names, email addresses, usernames, and passwords hashed using MD5. As MD5 is a broken cryptographic function, the hashes can be easily reversed using public tools, exposing user credentials in plaintext. This allows remote attackers to perform unauthorized logins and potentially gain access to sensitive POS operations or backend functions.

Published
Date
2026-01-23
Updated
Date
2026-01-23
References