Comparison Overview

Thales

VS

Amentum

Thales

6, Rue de la Verrerie, Meudon, Île-de-France, FR, 92190
Last Update: 2025-12-09
Between 700 and 749

Thales (Euronext Paris: HO) is a global leader in advanced technologies for the Defence, Aerospace, and Cyber & Digital sectors. Its portfolio of innovative products and services addresses several major challenges: sovereignty, security, sustainability and inclusion. The Group invests more than €4 billion per year in Research & Development in key areas, particularly for critical environments, such as Artificial Intelligence, cybersecurity, quantum and cloud technologies. Thales has more than 83,000 employees in 68 countries. In 2024, the Group generated sales of €20.6 billion.

NAICS: 336414
NAICS Definition: Guided Missile and Space Vehicle Manufacturing
Employees: 67,535
Subsidiaries: 10
12-month incidents
0
Known data breaches
1
Attack type number
4

Amentum

4800 Westfields Blvd, Chantilly, Virginia, 20151, US
Last Update: 2025-12-09
Between 750 and 799

Amentum is a global leader in advanced engineering and innovative technology solutions, trusted by the United States and its allies to address their most significant and complex challenges in science, security and sustainability. Our people apply undaunted curiosity, relentless ambition and boundless imagination to challenge convention and drive progress. Our commitments are underpinned by the belief that safety, inclusion and well-being are integral to success. Headquartered in Chantilly, Virginia, we have more than 53,000 employees in approximately 80 countries across all 7 continents.

NAICS: 336414
NAICS Definition: Guided Missile and Space Vehicle Manufacturing
Employees: 34,277
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/thales.jpeg
Thales
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/amentumcorp.jpeg
Amentum
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
Thales
100%
Compliance Rate
0/4 Standards Verified
Amentum
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Defense and Space Manufacturing Industry Average (This Year)

No incidents recorded for Thales in 2025.

Incidents vs Defense and Space Manufacturing Industry Average (This Year)

No incidents recorded for Amentum in 2025.

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

Thales cyber incidents detection timeline including parent company and subsidiaries

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

Amentum cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/thales.jpeg
Thales
Incidents

Date Detected: 04/2023
Type:Cyber Attack
Attack Vector: Malicious Code Injection
Motivation: National Security Disruption, Economic Instability
Blog: Blog

Date Detected: 11/2022
Type:Ransomware
Motivation: Data theft and extortion
Blog: Blog

Date Detected: 11/2022
Type:Breach
Attack Vector: Unknown
Motivation: Extortion
Blog: Blog
https://images.rankiteo.com/companyimages/amentumcorp.jpeg
Amentum
Incidents

No Incident

FAQ

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

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

In the current year, Amentum company and Thales company have not reported any cyber incidents.

Thales company has confirmed experiencing a ransomware attack, while Amentum company has not reported such incidents publicly.

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

Thales company has reported targeted cyberattacks, while Amentum company has not reported such incidents publicly.

Neither Thales company nor Amentum company has reported experiencing or disclosing vulnerabilities publicly.

Neither Thales nor Amentum holds any compliance certifications.

Neither company holds any compliance certifications.

Thales company has more subsidiaries worldwide compared to Amentum company.

Thales company employs more people globally than Amentum company, reflecting its scale as a Defense and Space Manufacturing.

Neither Thales nor Amentum holds SOC 2 Type 1 certification.

Neither Thales nor Amentum holds SOC 2 Type 2 certification.

Neither Thales nor Amentum holds ISO 27001 certification.

Neither Thales nor Amentum holds PCI DSS certification.

Neither Thales nor Amentum holds HIPAA certification.

Neither Thales nor Amentum holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

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

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

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

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/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

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

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

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N