Comparison Overview

Porsche Japan

VS

Li Auto

Porsche Japan

港区, JP
Last Update: 2025-11-21

「私は自らが理想とする車を探したが、どこにも見つからなかった。だから自分で造ることにした。」 ポルシェAGの創始者フェルディナンド・ポルシェの長男であるフェリー・ポルシェが残したこの言葉から、夢への熱烈な信念はポルシェのミッションとなっています。 ポルシェジャパンは、ポルシェ本社100%出資の子会社として1995年に設立しました。911をアイコンにモデルレンジを拡充しながら、2021年10月に、千葉県木更津市へ世界で9箇所目となるポルシェのブランド体験施設として開設した「ポルシェ・エクスペリエンスセンター東京」は、様々な方がポルシェブランドの魅力を体験できる場所となっています。さらに2022年4月には日本初の都市型コンセプトストア「ポルシェスタジオ日本橋」をオープン。同年8月にはポルシェ公認レストランが併設する「ポルシェスタジオ銀座」を国内2店舗目のポルシェスタジオとしてオープンしました。 このように常に進化し続けることを通じ、夢を追う人のためのブランドとして今日もあくなき努力と挑戦を続け、自動車業界を先導しています。ポルシェジャパンでは、この想いやミッションに共感し、ともに夢を追い続けてくれる人材を歓迎します。

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

Li Auto

Number 11 of Wenliang Street, Shunyi District, None, Beijing, Beijing, CN, 101399
Last Update: 2025-11-26
Between 750 and 799

Li Auto Inc. is a leader in China's new energy vehicle market. The Company designs, develops, manufactures, and sells premium smart electric vehicles. Its mission is: Create a Mobile Home, Create Happiness (创造移动的家,创造幸福的家). Through innovations in product, technology, and business model, the Company provides families with safe, convenient, and comfortable products and services. Li Auto is a pioneer in successfully commercializing extended-range electric vehicles in China. While firmly advancing along this technological route, it builds platforms for battery electric vehicles in parallel. The Company leverages technology to create value for users. It concentrates its in-house development efforts on proprietary range extension systems, innovative electric vehicle technologies, and smart vehicle solutions. The Company started volume production in November 2019. Its current model lineup includes Li MEGA, a high-tech flagship family MPV, Li L9, a six-seat flagship family SUV, Li L8, a six-seat premium family SUV, Li L7, a five-seat flagship family SUV, and Li L6, a five-seat premium family SUV. The Company will continue to expand its product lineup to target a broader user base.

NAICS: 3361
NAICS Definition: Motor Vehicle Manufacturing
Employees: 1,666
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/porschejapan.jpeg
Porsche Japan
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/理想汽车.jpeg
Li Auto
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 Japan
100%
Compliance Rate
0/4 Standards Verified
Li Auto
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 Japan in 2025.

Incidents vs Motor Vehicle Manufacturing Industry Average (This Year)

No incidents recorded for Li Auto in 2025.

Incident History — Porsche Japan (X = Date, Y = Severity)

Porsche Japan cyber incidents detection timeline including parent company and subsidiaries

Incident History — Li Auto (X = Date, Y = Severity)

Li Auto cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/porschejapan.jpeg
Porsche Japan
Incidents

Date Detected: 6/2000
Type:Data Leak
Blog: Blog
https://images.rankiteo.com/companyimages/理想汽车.jpeg
Li Auto
Incidents

No Incident

FAQ

Li Auto company demonstrates a stronger AI Cybersecurity Score compared to Porsche Japan company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Porsche Japan company has historically faced a number of disclosed cyber incidents, whereas Li Auto company has not reported any.

In the current year, Li Auto company and Porsche Japan company have not reported any cyber incidents.

Neither Li Auto company nor Porsche Japan company has reported experiencing a ransomware attack publicly.

Neither Li Auto company nor Porsche Japan company has reported experiencing a data breach publicly.

Neither Li Auto company nor Porsche Japan company has reported experiencing targeted cyberattacks publicly.

Neither Porsche Japan company nor Li Auto company has reported experiencing or disclosing vulnerabilities publicly.

Neither Porsche Japan nor Li Auto holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Porsche Japan company nor Li Auto company has publicly disclosed detailed information about the number of their subsidiaries.

Li Auto company employs more people globally than Porsche Japan company, reflecting its scale as a Motor Vehicle Manufacturing.

Neither Porsche Japan nor Li Auto holds SOC 2 Type 1 certification.

Neither Porsche Japan nor Li Auto holds SOC 2 Type 2 certification.

Neither Porsche Japan nor Li Auto holds ISO 27001 certification.

Neither Porsche Japan nor Li Auto holds PCI DSS certification.

Neither Porsche Japan nor Li Auto holds HIPAA certification.

Neither Porsche Japan nor Li Auto holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

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

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.