Comparison Overview

Concord

VS

Indra

Concord

509 2nd Avenue South, Minneapolis, MN, 55343, US
Last Update: 2025-12-17
Between 700 and 749

Concord is a technology consultancy building connected customer experiences backed by powerful AI & analytics and underpinned by secure IT foundations. Digital Experience | Data & Analytics | Engineering & Applications

NAICS: 5415
NAICS Definition: Computer Systems Design and Related Services
Employees: 563
Subsidiaries: 0
12-month incidents
0
Known data breaches
1
Attack type number
1

Indra

Avda. Bruselas, 35, Alcobendas, Madrid, Madrid, ES, 28108
Last Update: 2025-12-17
Between 750 and 799

Indra (www.indracompany.com) is one of the leading global defence, aerospace and technology companies, and a world leader in digital transformation and information technologies in Spain and Latin America through its subsidiary, Minsait. Its business model is based on a comprehensive range of proprietary products, with high-value approach and a significant innovative component, making it the technological partner for the digitalization and key operations of its clients around the world. Sustainability forms part of its strategy and culture in order to overcome current-day and future social and environmental challenges. In the 2023 fiscal year, Indra achieved revenue totaling €4.343 billion, with more than 57,000 employees, a local presence in 46 countries and business operations in over 140 countries.

NAICS: 5415
NAICS Definition: Computer Systems Design and Related Services
Employees: 38,194
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/concord.jpeg
Concord
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/indra.jpeg
Indra
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Concord
100%
Compliance Rate
0/4 Standards Verified
Indra
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs IT Services and IT Consulting Industry Average (This Year)

No incidents recorded for Concord in 2025.

Incidents vs IT Services and IT Consulting Industry Average (This Year)

No incidents recorded for Indra in 2025.

Incident History — Concord (X = Date, Y = Severity)

Concord 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

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/concord.jpeg
Concord
Incidents

Date Detected: 6/2019
Type:Breach
Attack Vector: Physical Theft
Blog: Blog
https://images.rankiteo.com/companyimages/indra.jpeg
Indra
Incidents

No Incident

FAQ

Indra company demonstrates a stronger AI Cybersecurity Score compared to Concord company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Concord company has historically faced a number of disclosed cyber incidents, whereas Indra company has not reported any.

In the current year, Indra company and Concord company have not reported any cyber incidents.

Neither Indra company nor Concord company has reported experiencing a ransomware attack publicly.

Concord company has disclosed at least one data breach, while the other Indra company has not reported such incidents publicly.

Neither Indra company nor Concord company has reported experiencing targeted cyberattacks publicly.

Neither Concord company nor Indra company has reported experiencing or disclosing vulnerabilities publicly.

Neither Concord nor Indra holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Concord company nor Indra company has publicly disclosed detailed information about the number of their subsidiaries.

Indra company employs more people globally than Concord company, reflecting its scale as a IT Services and IT Consulting.

Neither Concord nor Indra holds SOC 2 Type 1 certification.

Neither Concord nor Indra holds SOC 2 Type 2 certification.

Neither Concord nor Indra holds ISO 27001 certification.

Neither Concord nor Indra holds PCI DSS certification.

Neither Concord nor Indra holds HIPAA certification.

Neither Concord nor Indra holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

httparty is an API tool. In versions 0.23.2 and prior, httparty is vulnerable to SSRF. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers. This issue has been patched via commit 0529bcd.

Risk Information
cvss4
Base: 8.8
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. In versions 0.15.2 and prior, an RCE vulnerability exists in useMarkdown.ts, where the markdown-it-mermaid plugin is initialized with securityLevel: 'loose'. This configuration explicitly permits the rendering of HTML tags within Mermaid diagram nodes. This issue has not been patched at time of publication.

Risk Information
cvss3
Base: 9.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Description

continuwuity is a Matrix homeserver written in Rust. Prior to version 0.5.0, this vulnerability allows a remote, unauthenticated attacker to force the target server to cryptographically sign arbitrary membership events. The flaw exists because the server fails to validate the origin of a signing request, provided the event's state_key is a valid user ID belonging to the target server. This issue has been patched in version 0.5.0. A workaround for this issue involves blocking access to the PUT /_matrix/federation/v2/invite/{roomId}/{eventId} endpoint using the reverse proxy.

Risk Information
cvss4
Base: 9.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3

Risk Information
cvss3
Base: 8.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Description

LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form dictionaries. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in versions 0.3.81 and 1.2.5.

Risk Information
cvss3
Base: 9.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N