Comparison Overview
NEC Argentina

NEC Argentina
Avda. Pedro de Mendoza N° 443, Ciudad Autonoma de Buenos Aires, 1156, AR
Last Update: 13/01/2026
En Argentina, NEC ofrece soluciones de TI y telecomunicaciones para operadores, empresas y gobierno. NEC también desarrolla proyectos en el ámbito de la radiodifusión y la seguridad integrada. Con más de 40 años de experiencia en el mercado local, la compañía es una sub...

Indra
Avda. Bruselas, 35, Madrid, 28108, ES
Last Update: 01/07/2026
Indra Group (https://www.indragroup.com/) is the foremost Spanish multinational and one of the leading European companies that focus on defence and advanced technologies. It stands at the forefront of the defence, space, air traffic management, mobility, and Information...
Compliance Ranges Comparison

NEC Argentina







Indra






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for NEC Argentina in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Indra has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - NEC Argentina (X = Date, Y = Severity)
NEC Argentina cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Indra (X = Date, Y = Severity)
Indra cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

NEC Argentina

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