Comparison Overview
Hyatt Regency Indianapolis

Hyatt Regency Indianapolis
One South Capitol Avenue, Indianapolis, Indiana, 46204, US
Last Update: 31/10/2025
Beautifully designed and refined, Hyatt Regency is a contemporary downtown Indianapolis hotel conveniently connected to the Convention Center and just steps from Lucas Oil Stadium. The modern amenities at our hotel blend effortlessly with classic design elements, creati...

Hilton
7930 Jones Branch Drive, McLean, 22102, US
Last Update: 26/09/2026
Hilton (NYSE: HLT) is a leading global hospitality company with a portfolio of 27 world-class brands comprising more than 9,100 properties and over 1.3 million rooms, in 143 countries and territories. Dedicated to fulfilling its founding vision to fill the earth with th...
Compliance Ranges Comparison

Hyatt Regency Indianapolis







Hilton






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Hyatt Regency Indianapolis in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Hilton in 2026.
Incident History - Hyatt Regency Indianapolis (X = Date, Y = Severity)
Hyatt Regency Indianapolis cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hilton (X = Date, Y = Severity)
Hilton cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Hyatt Regency Indianapolis

Hilton
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)