Comparison Overview

Pirelli

VS

JLR

Pirelli

Viale Piero e Alberto Pirelli 25, Milano, MI, 20126, IT
Last Update: 2025-12-17
Between 700 and 749

Pirelli was founded in Milan in 1872 and today stands as a global brand known for its cutting-edge technology, high-end production excellence and passion for innovation that draws heavily on its Italian roots. With 18 production plants in 12 countries and a commercial presence in over 160, Pirelli has around 31.200 employees and had a turnover of about 6.8 billion euro (in 2024). It is among the world’s major producers of tyres and associated services and the only one focused solely on the Consumer tyre market, which includes tyres for cars, motorcycles and bicycles. Pirelli’s technological excellence is also nourished by the innovation and competencies derived from sporting competitions, in which it has been active for over 115 years. Currently, the Company participates in over 350 car and motorcycle sport events and, since 2011, it has been the exclusive tyre supplier to the Formula 1© World Championship and will be the sole Global Tyre Partner until 2027. All of this has grown from a strong commitment to Research and Development based on an “Open Innovation” model. In 2024, Pirelli’s investment in R&D equaled around 5.3% of its revenues from High Value products. Pirelli boasts over 2,000 people engaged in R&D, located at its Milan headquarters and 12 local technology centres, and a portfolio of around 6,000 patents. The Pirelli brand is an international icon standing for technology, tastefulness and Italian excellence, synonymous with safety and reliability. Represented by the unmistakable “long P” logo for more than a century, the Pirelli name is associated with exclusivity, luxury and innovation, strengthening its distinctive position as a supplier to luxury car manufacturers. Pirelli continually enhances the reputation and strength of the brand through its involvement in motorsport events and competitions, cultural and artistic projects and initiatives benefitting local communities.

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

JLR

Abbey Road, Whitley, Coventry, West Midlands, GB, CV3 4LF
Last Update: 2025-12-19
Between 0 and 549

Every vehicle. Every innovation. Every bit of momentum in over 170 markets worldwide. None of it would be possible without the expertise, drive and continued ambition of our people. We’re proud of our heritage, but it’s our vision for the future that excites us most. Right across our business, everybody plays a crucial role in the ever-evolving JLR journey. And with exciting new products, cutting-edge facilities and continued growth into new markets, there has never been a more exciting time to join us. We may be renowned for our iconic vehicles, but our drive for excellence covers more than premium design and world-class engineering. Ours is a truly global business, with the opportunities to match. You can learn more about our business areas and current opportunities here on the JLR Linked Company pages. This is also the place to ask any questions you may have, share your experiences and talk to the other talented individuals who are thinking about joining us. We look forward to talking with you.

NAICS: 3361
NAICS Definition: Motor Vehicle Manufacturing
Employees: 41,687
Subsidiaries: 58
12-month incidents
6
Known data breaches
2
Attack type number
3

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/pirelli.jpeg
Pirelli
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/jaguar-land-rover_1.jpeg
JLR
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
Pirelli
100%
Compliance Rate
0/4 Standards Verified
JLR
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Motor Vehicle Manufacturing Industry Average (This Year)

No incidents recorded for Pirelli in 2025.

Incidents vs Motor Vehicle Manufacturing Industry Average (This Year)

JLR has 782.35% more incidents than the average of same-industry companies with at least one recorded incident.

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

Pirelli cyber incidents detection timeline including parent company and subsidiaries

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

JLR cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/pirelli.jpeg
Pirelli
Incidents

Date Detected: 9/2024
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/jaguar-land-rover_1.jpeg
JLR
Incidents

Date Detected: 11/2025
Type:Cyber Attack
Blog: Blog

Date Detected: 11/2025
Type:Cyber Attack
Motivation: Financial Gain, Disruption
Blog: Blog

Date Detected: 10/2025
Type:Cyber Attack
Attack Vector: Phishing Emails, Spoofed Supplier Communications, WhatsApp Scams, Human Error (Misplaced Trust)
Motivation: Financial Gain, Data Theft, Reputational Damage, Exploitation of Human Behavior
Blog: Blog

FAQ

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

JLR company has faced a higher number of disclosed cyber incidents historically compared to Pirelli company.

In the current year, JLR company has reported more cyber incidents than Pirelli company.

JLR company has confirmed experiencing a ransomware attack, while Pirelli company has not reported such incidents publicly.

Both JLR company and Pirelli company have disclosed experiencing at least one data breach.

JLR company has reported targeted cyberattacks, while Pirelli company has not reported such incidents publicly.

Neither Pirelli company nor JLR company has reported experiencing or disclosing vulnerabilities publicly.

Neither Pirelli nor JLR holds any compliance certifications.

Neither company holds any compliance certifications.

JLR company has more subsidiaries worldwide compared to Pirelli company.

JLR company employs more people globally than Pirelli company, reflecting its scale as a Motor Vehicle Manufacturing.

Neither Pirelli nor JLR holds SOC 2 Type 1 certification.

Neither Pirelli nor JLR holds SOC 2 Type 2 certification.

Neither Pirelli nor JLR holds ISO 27001 certification.

Neither Pirelli nor JLR holds PCI DSS certification.

Neither Pirelli nor JLR holds HIPAA certification.

Neither Pirelli nor JLR holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Versa SASE Client for Windows versions released between 7.8.7 and 7.9.4 contain a local privilege escalation vulnerability in the audit log export functionality. The client communicates user-controlled file paths to a privileged service, which performs file system operations without impersonating the requesting user. Due to improper privilege handling and a time-of-check time-of-use race condition combined with symbolic link and mount point manipulation, a local authenticated attacker can coerce the service into deleting arbitrary directories with SYSTEM privileges. This can be exploited to delete protected system folders such as C:\\Config.msi and subsequently achieve execution as NT AUTHORITY\\SYSTEM via MSI rollback techniques.

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

The WP JobHunt plugin for WordPress, used by the JobCareer theme, is vulnerable to unauthorized modification of data due to a missing capability check on the 'cs_update_application_status_callback' function in all versions up to, and including, 7.7. This makes it possible for authenticated attackers, with Candidate-level access and above, to inject cross-site scripting into the 'status' parameter of applied jobs for any user.

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

The WP JobHunt plugin for WordPress, used by the JobCareer theme, is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 7.7 via the 'cs_update_application_status_callback' due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Candidate-level access and above, to send a site-generated email with injected HTML to any user.

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

The FiboSearch – Ajax Search for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's `thegem_te_search` shortcode in all versions up to, and including, 1.32.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This vulnerability requires TheGem theme (premium) to be installed with Header Builder mode enabled, and the FiboSearch "Replace search bars" option enabled for TheGem integration.

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

The Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.11.0 via the ajax_get_members function. This is due to the use of a predictable low-entropy token (5 hex characters derived from md5 of post ID) to identify member directories and insufficient authorization checks on the unauthenticated AJAX endpoint. This makes it possible for unauthenticated attackers to extract sensitive data including usernames, display names, user roles (including administrator accounts), profile URLs, and user IDs by enumerating predictable directory_id values or brute-forcing the small 16^5 token space.

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