Comparison Overview

Space Age Fuel Inc

VS

repsol

Space Age Fuel Inc

11525 SE For Mor Ct, Clackamas, 97015, US
Last Update: 2026-04-04
Between 700 and 749

Space Age Fuel a family owned business was incorporated in 1982. The principals in the business, Harold and Jim Pliska are father and son and have 60 years of petroleum experience between them. Our office and sales staff is very knowledgeable with over 58 years in the industry. With this experience we have witnessed a number of changes in the petroleum industry and are constantly modifying our business to keep up with the ever-changing market. One thing always remains the same…. Our service and loyalty to our customers. Over the years Space Age Fuel Inc. has experienced rapid but controlled growth. Space Age Fuel Inc. is one of the largest independent marketers in the State of Oregon. Space Age Fuel consists of four divisions which are the company operated stations, commercial sales accounts, commercial freight deliveries and home heating oil deliveries. Currently we operate fifteen truck and trailers in the Pacific Northwest. We deliver in the states of Oregon, Washington. We have concentrated on building our own brand. We currently operate twenty-one locations and supply another 100 retail and wholesale fueling facilities. We also transport fuel for other Petroleum companies when the need arises. We sell unbranded products through several providers in the Northwest.

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

repsol

Méndez Álvaro, 44, Madrid, Madrid, ES, 28045
Last Update: 2026-04-02
Between 750 and 799

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/space-age-fuel-inc.jpeg
Space Age Fuel Inc
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/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
Compliance Summary
Space Age Fuel Inc
100%
Compliance Rate
0/4 Standards Verified
repsol
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for Space Age Fuel Inc in 2026.

Incidents vs Oil and Gas Industry Average (This Year)

No incidents recorded for repsol in 2026.

Incident History — Space Age Fuel Inc (X = Date, Y = Severity)

Space Age Fuel Inc cyber incidents detection timeline including parent company and subsidiaries

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

repsol cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/space-age-fuel-inc.jpeg
Space Age Fuel Inc
Incidents

No Incident

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

No Incident

FAQ

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

Historically, repsol company has disclosed a higher number of cyber incidents compared to Space Age Fuel Inc company.

In the current year, repsol company and Space Age Fuel Inc company have not reported any cyber incidents.

Neither repsol company nor Space Age Fuel Inc company has reported experiencing a ransomware attack publicly.

Neither repsol company nor Space Age Fuel Inc company has reported experiencing a data breach publicly.

Neither repsol company nor Space Age Fuel Inc company has reported experiencing targeted cyberattacks publicly.

Neither Space Age Fuel Inc company nor repsol company has reported experiencing or disclosing vulnerabilities publicly.

Neither Space Age Fuel Inc nor repsol holds any compliance certifications.

Neither company holds any compliance certifications.

repsol company has more subsidiaries worldwide compared to Space Age Fuel Inc company.

repsol company employs more people globally than Space Age Fuel Inc company, reflecting its scale as a Oil and Gas.

Neither Space Age Fuel Inc nor repsol holds SOC 2 Type 1 certification.

Neither Space Age Fuel Inc nor repsol holds SOC 2 Type 2 certification.

Neither Space Age Fuel Inc nor repsol holds ISO 27001 certification.

Neither Space Age Fuel Inc nor repsol holds PCI DSS certification.

Neither Space Age Fuel Inc nor repsol holds HIPAA certification.

Neither Space Age Fuel Inc nor repsol 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.

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

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

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.

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

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

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