Comparison Overview

repsol

VS

TechnipFMC

repsol

Méndez Álvaro, 44, Madrid, Madrid, ES, 28045
Last Update: 2026-04-02
View Profile
Between 750 and 799
http://www.repsol.com

What do you do with the energy that drives you every day? We strive to turn it into something useful for you—your decisions and your next steps. We are a company that explores multi-energy solutions through innovation, technology, and the curiosity of our team. With over 25,000 colleagues and presence in 27 countries, we deliver real solutions to the challenges of mobility, home, and industry. And we do it the way we know best: #AllOurEnergy.

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 25,536
Subsidiaries: 3
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

TechnipFMC

Hadrian House, Wincomblee Road, Newcastle Upon Tyne, NE6 3PL, GB
Last Update: 2026-04-04
Between 750 and 799
http://technipfmc.com

TechnipFMC is a leading technology provider to the traditional and new energies industry, delivering fully integrated projects, products, and services. With our proprietary technologies and comprehensive solutions, we are transforming our clients’ project economics, helping them unlock new possibilities to develop energy resources while reducing carbon intensity and supporting their energy transition ambitions. Organized in two business segments — Subsea and Surface Technologies — we will continue to advance the industry with our pioneering integrated ecosystems (such as iEPCI™, iFEED™ and iComplete™), technology leadership and digital innovation. Each of our approximately 20,000 employees is driven by a commitment to our clients’ success, and a culture of strong execution, purposeful innovation, and challenging industry conventions. To learn more about us and how we are enhancing the performance of the world’s energy industry, go to TechnipFMC.com.

NAICS: 211
NAICS Definition: Oil and Gas Extraction
Employees: 38,099
Subsidiaries: 3
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/repsol.jpeg
repsol
—
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/technipfmc.jpeg
TechnipFMC
—
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
repsol
100%
Compliance Rate
0/4 Standards Verified
TechnipFMC
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for repsol in 2026.

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for TechnipFMC in 2026.

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

repsol cyber incidents detection timeline including parent company and subsidiaries

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

TechnipFMC cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/repsol.jpeg
repsol
Incidents

No Incident

https://images.rankiteo.com/companyimages/technipfmc.jpeg
TechnipFMC
Incidents

No Incident

FAQ

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

Historically, TechnipFMC company has disclosed a higher number of cyber incidents compared to repsol company.

In the current year, TechnipFMC company and repsol company have not reported any cyber incidents.

Neither TechnipFMC company nor repsol company has reported experiencing a ransomware attack publicly.

Neither TechnipFMC company nor repsol company has reported experiencing a data breach publicly.

Neither TechnipFMC company nor repsol company has reported experiencing targeted cyberattacks publicly.

Neither repsol company nor TechnipFMC company has reported experiencing or disclosing vulnerabilities publicly.

Neither repsol nor TechnipFMC holds any compliance certifications.

Neither company holds any compliance certifications.

Both TechnipFMC company and repsol company have a similar number of subsidiaries worldwide.

TechnipFMC company employs more people globally than repsol company, reflecting its scale as a Oil and Gas.

Neither repsol nor TechnipFMC holds SOC 2 Type 1 certification.

Neither repsol nor TechnipFMC holds SOC 2 Type 2 certification.

Neither repsol nor TechnipFMC holds ISO 27001 certification.

Neither repsol nor TechnipFMC holds PCI DSS certification.

Neither repsol nor TechnipFMC holds HIPAA certification.

Neither repsol nor TechnipFMC holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 5.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
References
Description

PraisonAI is a multi-agent teams system. Prior to version 1.5.95, FileTools.download_file() in praisonaiagents validates the destination path but performs no validation on the url parameter, passing it directly to httpx.stream() with follow_redirects=True. An attacker who controls the URL can reach any host accessible from the server including cloud metadata services and internal network services. This issue has been patched in version 1.5.95.

Published
Date
2026-04-03
Updated
Date
2026-04-03
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
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validate_token() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities. This issue has been patched in version 4.5.97.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, the PraisonAI Gateway server accepts WebSocket connections at /ws and serves agent topology at /info with no authentication. Any network client can connect, enumerate registered agents, and send arbitrary messages to agents and their tool sets. This issue has been patched in version 4.5.97.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.90, MCPToolIndex.search_tools() compiles a caller-supplied string directly as a Python regular expression with no validation, sanitization, or timeout. A crafted regex causes catastrophic backtracking in the re engine, blocking the Python thread for hundreds of seconds and causing a complete service outage. This issue has been patched in version 4.5.90.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 6.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
References