Comparison Overview
Titan Movements

Titan Movements
#3, Aminity Building,titan-watches, Sipcot Industrial Complex, Hosur, Tamil Nadu , IN, 635126
Last Update: 25/03/2026
The Titan Company Limited (Titan) journey began in 1984, with an objective to create Titan watches for everyone. Over the years, we have gained expertise in Horology and Micro Precision Component Manufacturing with state-of-the-art Manufacturing Technology and R&D Capab...

Richemont
Chemin de la Chênaie 50, Bellevue, Geneva, CH, 1293
Last Update: 05/09/2026
At Richemont, we craft the future. Our unique portfolio includes prestigious Maisons distinguished by their craftsmanship and creativity. Richemont’s ambition is to nurture its Maisons and businesses and enable them to grow and prosper in a responsible, sustainable mann...
Compliance Ranges Comparison

Titan Movements







Richemont






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for Titan Movements in 2026.
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for Richemont in 2026.
Incident History - Titan Movements (X = Date, Y = Severity)
Titan Movements cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Richemont (X = Date, Y = Severity)
Richemont cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Titan Movements

Richemont
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)