Comparison Overview
ANDRITZ Technologies - India

ANDRITZ Technologies - India
Andritz Technologies Private Ltd., The Lords, Block - I, Plot No. 1 &2,(NP), III Floor, Thiru-Vi-Ka Industrial Estate, Jawaharlal Nehru Road, Ekkatuthangal, Guindy, Chennai, 600032, IN
Last Update: 19/03/2026
ANDRITZ Technologies Pvt. Ltd. (ATPL) in India, came into presence with the establishment of Metals division in Bangalore in 1998, marking ANDRITZ's inaugural presence in the country. Over time, the organization expanded with the introduction of the Pulp and Paper divis...

ALTEN
221 bis boulevard Jean jaurès, Boulogne-Billancourt Cedex, Ile-de-France, FR, 92514
Last Update: 02/04/2026
𝐀 𝐰𝐨𝐫𝐥𝐝 𝐥𝐞𝐚𝐝𝐞𝐫 𝐢𝐧 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐢𝐧𝐠 𝐚𝐧𝐝 𝐈𝐓 𝐒𝐞𝐫𝐯𝐢𝐜𝐞𝐬 ALTEN is committed to meeting the expectations of its stakeholders and anticipating their requirements in the fields of innovation, R&D, and technological information systems. Founded...
Compliance Ranges Comparison

ANDRITZ Technologies - India







ALTEN






Benchmark & Cyber Underwriting Signals
Incidents vs Engineering Services Industry Avg (This Year)
No incidents recorded for ANDRITZ Technologies - India in 2026.
Incidents vs Engineering Services Industry Avg (This Year)
No incidents recorded for ALTEN in 2026.
Incident History - ANDRITZ Technologies - India (X = Date, Y = Severity)
ANDRITZ Technologies - India cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ALTEN (X = Date, Y = Severity)
ALTEN cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

ANDRITZ Technologies - India

ALTEN
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.