Comparison Overview

Porsche Cars North America

VS

MAHLE

Porsche Cars North America

One Porsche Drive, Atlanta, GA, US, 30354
Last Update: 2025-11-27
Between 800 and 849

At Porsche Cars North America, we thrive on a foundation of precision engineering fueled by the American entrepreneurial spirit; we carry on the vision of our founder, Ferry Porsche, by delivering impassioned experiences as legendary as the cars we build, and we do it every day. We are fueling Porsche Passion as an unprecedented brand built on the idea that we are better together as a diverse and gifted workforce united in the desire to be the world’s most aspirational brand and most empowering employer. As an extension of the Porsche family, each of our team members brings a unique perspective and master craft to our workforce. We boast the brightest engineers, brand builders and marketing minds, business development leaders, analytical aficionados and corporate professionals in the automotive business – not because we want to lead our industry in performance and customer satisfaction, but because we do.

NAICS: 3361
NAICS Definition: Motor Vehicle Manufacturing
Employees: 7,032
Subsidiaries: 12
12-month incidents
0
Known data breaches
0
Attack type number
1

MAHLE

Pragstrasse 26-46, Stuttgart, DE, D-70376
Last Update: 2025-11-26

MAHLE is a leading international development partner and supplier to the automotive industry with customers in both passenger car and commercial vehicle sectors. Founded in 1920, the technology group is working on the climate-neutral mobility of tomorrow, with a focus on the strategic areas of electrification and thermal management as well as further technology fields to reduce CO2 emissions, such as fuel cells or highly efficient combustion engines that also run on hydrogen or synthetic fuels. Today, one in every two vehicles globally is equipped with MAHLE components. For privacy statement and imprint follow the website link below.

NAICS: 3361
NAICS Definition: Motor Vehicle Manufacturing
Employees: 21,435
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/porsche.jpeg
Porsche Cars North America
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/mahle.jpeg
MAHLE
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
Porsche Cars North America
100%
Compliance Rate
0/4 Standards Verified
MAHLE
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Motor Vehicle Manufacturing Industry Average (This Year)

No incidents recorded for Porsche Cars North America in 2025.

Incidents vs Motor Vehicle Manufacturing Industry Average (This Year)

No incidents recorded for MAHLE in 2025.

Incident History — Porsche Cars North America (X = Date, Y = Severity)

Porsche Cars North America cyber incidents detection timeline including parent company and subsidiaries

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

MAHLE cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/porsche.jpeg
Porsche Cars North America
Incidents

Date Detected: 7/2024
Type:Vulnerability
Motivation: Regulatory compliance and strategic shift toward electrification
Blog: Blog
https://images.rankiteo.com/companyimages/mahle.jpeg
MAHLE
Incidents

No Incident

FAQ

Porsche Cars North America company demonstrates a stronger AI Cybersecurity Score compared to MAHLE company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Porsche Cars North America company has historically faced a number of disclosed cyber incidents, whereas MAHLE company has not reported any.

In the current year, MAHLE company and Porsche Cars North America company have not reported any cyber incidents.

Neither MAHLE company nor Porsche Cars North America company has reported experiencing a ransomware attack publicly.

Neither MAHLE company nor Porsche Cars North America company has reported experiencing a data breach publicly.

Neither MAHLE company nor Porsche Cars North America company has reported experiencing targeted cyberattacks publicly.

Porsche Cars North America company has disclosed at least one vulnerability, while MAHLE company has not reported such incidents publicly.

Neither Porsche Cars North America nor MAHLE holds any compliance certifications.

Neither company holds any compliance certifications.

Porsche Cars North America company has more subsidiaries worldwide compared to MAHLE company.

MAHLE company employs more people globally than Porsche Cars North America company, reflecting its scale as a Motor Vehicle Manufacturing.

Neither Porsche Cars North America nor MAHLE holds SOC 2 Type 1 certification.

Neither Porsche Cars North America nor MAHLE holds SOC 2 Type 2 certification.

Neither Porsche Cars North America nor MAHLE holds ISO 27001 certification.

Neither Porsche Cars North America nor MAHLE holds PCI DSS certification.

Neither Porsche Cars North America nor MAHLE holds HIPAA certification.

Neither Porsche Cars North America nor MAHLE holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

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