Comparison Overview
InterMountain Management

InterMountain Management
2390 Tower Dr., Monroe, 71201, US
Last Update: 28/03/2026
As one of North America's largest hotel management and development companies, InterMountain Management specializes in the select-service and extended-stay hotel segments. For over 42 years, InterMountain Management's dedication to success is proven in the results as a h...

Rotana Hotels
Abu Dhabi, Abu Dhabi, AE, P.O. Box 95100
Last Update: 02/04/2026
Since inception, Rotana has grown to be the region’s largest hospitality management company, and a brand that is widely recognized and admired. Rotana currently manages a portfolio of over 100 properties throughout the Middle East, Africa, Eastern Europe and Türkiye o...
Compliance Ranges Comparison

InterMountain Management







Rotana Hotels






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

InterMountain Management

Rotana Hotels
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.