Subaru of America Company Cyber Security Posture
subaru.comThe Subaru Family, by our definition, goes far beyond our family of products. It includes one of our greatest assets โ our employees โ as well as our Subaru family of owners, retailers, and business and community partners. We treat each other like family because we are family. Since the early days of the company, we have worked to create a culture where employees are encouraged to be themselves and are supported by everyone around them. The Subaru Love Promise is our vision to show love and respect to all people at every interaction. We believe that our differences make us stronger. These experiences allow us to learn from each other, offer unique ideas, add value as team members, which ultimately, allows us to grow our business opportunity and personal lives.
SA Company Details
subaru-of-america
3720 employees
110282.0
336
Motor Vehicle Manufacturing
subaru.com
Scan still pending
SUB_2462610
In-progress
SA Risk Score (AI oriented)Between 900 and 1000
This score is AI-generated and less favored by cyber insurers, who prefer the TPRM score.
SA Global Score.png)
Subaru of America Company Scoring based on AI Models
| Model Name | Date | Description | Current Score Difference | Score |
|---|---|---|---|---|
| AVERAGE-Industry | 03-12-2025 | This score represents the average cybersecurity rating of companies already scanned within the same industry. It provides a benchmark to compare an individual company's security posture against its industry peers. | N/A | Between 900 and 1000 |
Subaru of America Company Cyber Security News & History
| Entity | Type | Severity | Impact | Seen | Url ID | Details | View |
|---|---|---|---|---|---|---|---|
| Subaru | Breach | 85 | 4 | 1/2025 | SUB000012725 | Link | |
Rankiteo Explanation : Attack with significant impact with customers data leaksDescription: Security researchers discovered web vulnerabilities in Subaru's Starlink service that allowed potential unauthorized access to customer accounts and tracking of customers' movements. While Subaru swiftly patched the flaw following the report, concerns persist about the access Subaru employees have to customer location data historically, which poses a privacy issue. Researchers were able to bypass security questions and gain control of Subaru Starlink developer accounts, leading to the possibility of manipulating vehicle features remotely. | |||||||
| Subaru | Vulnerability | 100 | 5 | 1/2025 | SUB000012425 | Link | |
Rankiteo Explanation : Attack threatening the organizationโs existenceDescription: Subaru encountered web vulnerabilities in its Starlink service that could potentially allow unauthorized access to customer accounts and tracking of customer movements. Researchers Shah and Curry identified the flaw, which Subaru promptly patched. While no customer information was compromised, the incident highlighted a significant privacy concern as the employees of Subaru could access a customer's location history. Subaru confirmed that access to this data is for relevant employees only, protected by privacy and security training, and NDA agreements. Despite quick resolution, the situation raises questions about data privacy and the security of web tools in the automotive industry. | |||||||
Subaru of America Company Subsidiaries
The Subaru Family, by our definition, goes far beyond our family of products. It includes one of our greatest assets โ our employees โ as well as our Subaru family of owners, retailers, and business and community partners. We treat each other like family because we are family. Since the early days of the company, we have worked to create a culture where employees are encouraged to be themselves and are supported by everyone around them. The Subaru Love Promise is our vision to show love and respect to all people at every interaction. We believe that our differences make us stronger. These experiences allow us to learn from each other, offer unique ideas, add value as team members, which ultimately, allows us to grow our business opportunity and personal lives.
Access Data Using Our API
Get company history
Rapid.png)
SA Cyber Security News
Subaruโs poor security left troves of vehicle data easily accessible
Subaru left open a gaping security flaw that, although patched, lays bare modern vehicles' myriad privacy issues. Security researchers Samย ...
Subaru Security Flaws Exposed Its System for Tracking Millions of Cars
Now-fixed web bugs allowed hackers to remotely unlock and start any of millions of Subarus. More disturbingly, they could also access at least aย ...
Subaru Starlink Vulnerability Exposed Cars to Remote Hacking
A vulnerability in Subaru's Starlink connected vehicle service exposed US, Canada, and Japan vehicle and customer accounts.
Subaru of America names chairman and CEO
Subaru of America named Yoichi Hori its chairman and chief executive officer, the company announced in a May 19 press release. He will overseeย ...
Hacker Finds Data Vulnerability in Subaru Starlink, Enabling Remote Control Without Driver Consent
Security researcher and ethical hacker Sam Curry has claimed he discovered a cybersecurity risk in Subaru vehicles, allowing access to sensitiveย ...
Vulnerability discovered in Subaruโs connected vehicle service
Subaru's STARLINK connected vehicle service contains a vulnerability that permits access to user accounts and vehicles.
Exclusive: Subaru of America increases vehicle prices, citing market conditions
The Subaru price increases will add between $750 and $2,055 to vehicles depending on the model and trim, according to a notice posted on aย ...
Cybersecurity Threats To Modern Cars: How Hackers Are Taking Control
Shocking flaws in modern car systems leave them vulnerable to hackers. Discover the risks hiding in your vehicle and how to stay protectedย ...
Subaru Starlink flaw allowed experts to remotely hack cars
Subaru Starlink flaw exposed vehicles and customer accounts in the US, Canada, and Japan to remote attacks. Popular security researcher Samย ...
SA Similar Companies
Automotive Manufacturers Private Limited
Automotive Manufacturers Private Limited (AMPL) was incorporated in the year 1948, under the dynamic leadership of Shri. Manubhai Sanghvi and Shri. P.P Sanghvi. The company started as main dealers of Leyland Motors, UK for marketing their products in the erstwhile states of Bombay, Hyderabad and
Sumitomo Electric Bordnetze SE
Sumitomo Electric Bordnetze SE (SEBN) is a global automotive supplier with over 36,000 employees in 13 countries. SEBN is part of the Japanese group Sumitomo Electric Industries, which has 380 subsidiaries in various industries worldwide. The more than 400-year-old Sumitomo Electric Group employs 28
Toyota UAE
Al-Futtaim Motors operates and manages the Toyota franchise through a nationwide network of state-of-the-art showrooms, workshops, parts, tyres, batteries and accessories operations strategically located throughout the UAE. Starting operations in the UAE in 1955, Al-Futtaim Motors marked the intr
Volkswagen Slovakia
Volkswagen Slovakia je najvโยงฦรงโยฐโโ m automobilovโโฆm producentom v Slovenskej republike. V sโโซฦรงasnosti mโยฐ na Slovensku dva zโยฐvody, situovanโยฉ v Bratislave a Martine. Volkswagen Slovakia s.r.o. bol zaloโรฆenโโฆ v roku 1991, produkcia sa rozbehla zaฦรงiatkom roka 1992. Zโยฐvod v Bratislave je jedine
FORVIA
FORVIA comprises the complementary technology and industrial strengths of Faurecia and HELLA. With over 300 industrial sites and 77 R&D centers, 150,000 people, including more than 35,000 engineers across 40+ countries, FORVIA provides a unique and comprehensive approach to the automotive challenge
Goodyear Germany GmbH
Ein Konzern mit starken Marken Die Goodyear Dunlop Tires Germany GmbH ist Teil des weltweit agierenden Reifenherstellers Goodyear. Rund 70.000 Menschen auf der ganzen Welt arbeiten tรคglich daran, unsere Erfolgsgeschichte fortzuschreiben. In Deutschland betreiben wir an sieben Standorten sechs Pro
Frequently Asked Questions (FAQ) on Cybersecurity Incidents
SA CyberSecurity History Information
Total Incidents: According to Rankiteo, SA has faced 2 incidents in the past.
Incident Types: The types of cybersecurity incidents that have occurred include ['Breach', 'Vulnerability'].
Total Financial Loss: The total financial loss from these incidents is estimated to be {total_financial_loss}.
Cybersecurity Posture: The company's overall cybersecurity posture is described as The Subaru Family, by our definition, goes far beyond our family of products. It includes one of our greatest assets โ our employees โ as well as our Subaru family of owners, retailers, and business and community partners. We treat each other like family because we are family. Since the early days of the company, we have worked to create a culture where employees are encouraged to be themselves and are supported by everyone around them. The Subaru Love Promise is our vision to show love and respect to all people at every interaction. We believe that our differences make us stronger. These experiences allow us to learn from each other, offer unique ideas, add value as team members, which ultimately, allows us to grow our business opportunity and personal lives..
Detection and Response: The company detects and responds to cybersecurity incidents through {description_of_detection_and_response_process}.
Incident Details
Incident 1: Ransomware Attack
Title: {Incident_Title}
Description: {Brief_description_of_the_incident}
Date Detected: {Detection_Date}
Date Publicly Disclosed: {Disclosure_Date}
Date Resolved: {Resolution_Date}
Type: {Type_of_Attack}
Attack Vector: {Attack_Vector}
Vulnerability Exploited: {Vulnerability}
Threat Actor: {Threat_Actor}
Motivation: {Motivation}
Incident 2: Data Breach
Title: {Incident_Title}
Description: {Brief_description_of_the_incident}
Date Detected: {Detection_Date}
Date Publicly Disclosed: {Disclosure_Date}
Date Resolved: {Resolution_Date}
Type: {Type_of_Attack}
Attack Vector: {Attack_Vector}
Vulnerability Exploited: {Vulnerability}
Threat Actor: {Threat_Actor}
Motivation: {Motivation}
Common Attack Types: As of now, the company has not encountered any reported incidents involving common cyberattacks.
Identification of Attack Vectors: The company identifies the attack vectors used in incidents through {description_of_identification_process}.
Impact of the Incidents
Incident 1: Ransomware Attack
Financial Loss: {Financial_Loss}
Data Compromised: {Data_Compromised}
Systems Affected: {Systems_Affected}
Downtime: {Downtime}
Operational Impact: {Operational_Impact}
Conversion Rate Impact: {Conversion_Rate_Impact}
Revenue Loss: {Revenue_Loss}
Customer Complaints: {Customer_Complaints}
Brand Reputation Impact: {Brand_Reputation_Impact}
Legal Liabilities: {Legal_Liabilities}
Identity Theft Risk: {Identity_Theft_Risk}
Payment Information Risk: {Payment_Information_Risk}
Incident 2: Data Breach
Financial Loss: {Financial_Loss}
Data Compromised: {Data_Compromised}
Systems Affected: {Systems_Affected}
Downtime: {Downtime}
Operational Impact: {Operational_Impact}
Conversion Rate Impact: {Conversion_Rate_Impact}
Revenue Loss: {Revenue_Loss}
Customer Complaints: {Customer_Complaints}
Brand Reputation Impact: {Brand_Reputation_Impact}
Legal Liabilities: {Legal_Liabilities}
Identity Theft Risk: {Identity_Theft_Risk}
Payment Information Risk: {Payment_Information_Risk}
Average Financial Loss: The average financial loss per incident is {average_financial_loss}.
Commonly Compromised Data Types: The types of data most commonly compromised in incidents are {list_of_commonly_compromised_data_types}.
Incident 1: Ransomware Attack
Entity Name: {Entity_Name}
Entity Type: {Entity_Type}
Industry: {Industry}
Location: {Location}
Size: {Size}
Customers Affected: {Customers_Affected}
Incident 2: Data Breach
Entity Name: {Entity_Name}
Entity Type: {Entity_Type}
Industry: {Industry}
Location: {Location}
Size: {Size}
Customers Affected: {Customers_Affected}
Response to the Incidents
Incident 1: Ransomware Attack
Incident Response Plan Activated: {Yes/No}
Third Party Assistance: {Yes/No}
Law Enforcement Notified: {Yes/No}
Containment Measures: {Containment_Measures}
Remediation Measures: {Remediation_Measures}
Recovery Measures: {Recovery_Measures}
Communication Strategy: {Communication_Strategy}
Adaptive Behavioral WAF: {Adaptive_Behavioral_WAF}
On-Demand Scrubbing Services: {On_Demand_Scrubbing_Services}
Network Segmentation: {Network_Segmentation}
Enhanced Monitoring: {Enhanced_Monitoring}
Incident 2: Data Breach
Incident Response Plan Activated: {Yes/No}
Third Party Assistance: {Yes/No}
Law Enforcement Notified: {Yes/No}
Containment Measures: {Containment_Measures}
Remediation Measures: {Remediation_Measures}
Recovery Measures: {Recovery_Measures}
Communication Strategy: {Communication_Strategy}
Adaptive Behavioral WAF: {Adaptive_Behavioral_WAF}
On-Demand Scrubbing Services: {On_Demand_Scrubbing_Services}
Network Segmentation: {Network_Segmentation}
Enhanced Monitoring: {Enhanced_Monitoring}
Incident Response Plan: The company's incident response plan is described as {description_of_incident_response_plan}.
Third-Party Assistance: The company involves third-party assistance in incident response through {description_of_third_party_involvement}.
Data Breach Information
Incident 2: Data Breach
Type of Data Compromised: {Type_of_Data}
Number of Records Exposed: {Number_of_Records}
Sensitivity of Data: {Sensitivity_of_Data}
Data Exfiltration: {Yes/No}
Data Encryption: {Yes/No}
File Types Exposed: {File_Types}
Personally Identifiable Information: {Yes/No}
Prevention of Data Exfiltration: The company takes the following measures to prevent data exfiltration: {description_of_prevention_measures}.
Handling of PII Incidents: The company handles incidents involving personally identifiable information (PII) through {description_of_handling_process}.
Ransomware Information
Incident 1: Ransomware Attack
Ransom Demanded: {Ransom_Amount}
Ransom Paid: {Ransom_Paid}
Ransomware Strain: {Ransomware_Strain}
Data Encryption: {Yes/No}
Data Exfiltration: {Yes/No}
Ransom Payment Policy: The company's policy on paying ransoms in ransomware incidents is described as {description_of_ransom_payment_policy}.
Data Recovery from Ransomware: The company recovers data encrypted by ransomware through {description_of_data_recovery_process}.
Regulatory Compliance
Incident 1: Ransomware Attack
Regulations Violated: {Regulations_Violated}
Fines Imposed: {Fines_Imposed}
Legal Actions: {Legal_Actions}
Regulatory Notifications: {Regulatory_Notifications}
Incident 2: Data Breach
Regulations Violated: {Regulations_Violated}
Fines Imposed: {Fines_Imposed}
Legal Actions: {Legal_Actions}
Regulatory Notifications: {Regulatory_Notifications}
Regulatory Frameworks: The company complies with the following regulatory frameworks regarding cybersecurity: {list_of_regulatory_frameworks}.
Ensuring Regulatory Compliance: The company ensures compliance with regulatory requirements through {description_of_compliance_measures}.
Lessons Learned and Recommendations
Incident 1: Ransomware Attack
Lessons Learned: {Lessons_Learned}
Incident 2: Data Breach
Lessons Learned: {Lessons_Learned}
Incident 1: Ransomware Attack
Recommendations: {Recommendations}
Incident 2: Data Breach
Recommendations: {Recommendations}
Key Lessons Learned: The key lessons learned from past incidents are {list_of_key_lessons_learned}.
Implemented Recommendations: The company has implemented the following recommendations to improve cybersecurity: {list_of_implemented_recommendations}.
References
Additional Resources: Stakeholders can find additional resources on cybersecurity best practices at {list_of_additional_resources}.
Investigation Status
Incident 1: Ransomware Attack
Investigation Status: {Investigation_Status}
Incident 2: Data Breach
Investigation Status: {Investigation_Status}
Communication of Investigation Status: The company communicates the status of incident investigations to stakeholders through {description_of_communication_process}.
Stakeholder and Customer Advisories
Incident 1: Ransomware Attack
Stakeholder Advisories: {Stakeholder_Advisories}
Customer Advisories: {Customer_Advisories}
Incident 2: Data Breach
Stakeholder Advisories: {Stakeholder_Advisories}
Customer Advisories: {Customer_Advisories}
Advisories Provided: The company provides the following advisories to stakeholders and customers following an incident: {description_of_advisories_provided}.
Initial Access Broker
Incident 1: Ransomware Attack
Entry Point: {Entry_Point}
Reconnaissance Period: {Reconnaissance_Period}
Backdoors Established: {Backdoors_Established}
High Value Targets: {High_Value_Targets}
Data Sold on Dark Web: {Yes/No}
Incident 2: Data Breach
Entry Point: {Entry_Point}
Reconnaissance Period: {Reconnaissance_Period}
Backdoors Established: {Backdoors_Established}
High Value Targets: {High_Value_Targets}
Data Sold on Dark Web: {Yes/No}
Monitoring and Mitigation of Initial Access Brokers: The company monitors and mitigates the activities of initial access brokers through {description_of_monitoring_and_mitigation_measures}.
Post-Incident Analysis
Incident 1: Ransomware Attack
Root Causes: {Root_Causes}
Corrective Actions: {Corrective_Actions}
Incident 2: Data Breach
Root Causes: {Root_Causes}
Corrective Actions: {Corrective_Actions}
Post-Incident Analysis Process: The company's process for conducting post-incident analysis is described as {description_of_post_incident_analysis_process}.
Corrective Actions Taken: The company has taken the following corrective actions based on post-incident analysis: {list_of_corrective_actions_taken}.
Additional Questions
General Information
Ransom Payment History: The company has {paid/not_paid} ransoms in the past.
Last Ransom Demanded: The amount of the last ransom demanded was {last_ransom_amount}.
Last Attacking Group: The attacking group in the last incident was {last_attacking_group}.
Incident Details
Most Recent Incident Detected: The most recent incident detected was on {most_recent_incident_detected_date}.
Most Recent Incident Publicly Disclosed: The most recent incident publicly disclosed was on {most_recent_incident_publicly_disclosed_date}.
Most Recent Incident Resolved: The most recent incident resolved was on {most_recent_incident_resolved_date}.
Impact of the Incidents
Highest Financial Loss: The highest financial loss from an incident was {highest_financial_loss}.
Most Significant Data Compromised: The most significant data compromised in an incident was {most_significant_data_compromised}.
Most Significant System Affected: The most significant system affected in an incident was {most_significant_system_affected}.
Response to the Incidents
Third-Party Assistance in Most Recent Incident: The third-party assistance involved in the most recent incident was {third_party_assistance_in_most_recent_incident}.
Containment Measures in Most Recent Incident: The containment measures taken in the most recent incident were {containment_measures_in_most_recent_incident}.
Data Breach Information
Most Sensitive Data Compromised: The most sensitive data compromised in a breach was {most_sensitive_data_compromised}.
Number of Records Exposed: The number of records exposed in the most significant breach was {number_of_records_exposed}.
Ransomware Information
Highest Ransom Demanded: The highest ransom demanded in a ransomware incident was {highest_ransom_demanded}.
Highest Ransom Paid: The highest ransom paid in a ransomware incident was {highest_ransom_paid}.
Regulatory Compliance
Highest Fine Imposed: The highest fine imposed for a regulatory violation was {highest_fine_imposed}.
Most Significant Legal Action: The most significant legal action taken for a regulatory violation was {most_significant_legal_action}.
Lessons Learned and Recommendations
Most Significant Lesson Learned: The most significant lesson learned from past incidents was {most_significant_lesson_learned}.
Most Significant Recommendation Implemented: The most significant recommendation implemented to improve cybersecurity was {most_significant_recommendation_implemented}.
References
Most Recent Source: The most recent source of information about an incident is {most_recent_source}.
Most Recent URL for Additional Resources: The most recent URL for additional resources on cybersecurity best practices is {most_recent_url}.
Investigation Status
Current Status of Most Recent Investigation: The current status of the most recent investigation is {current_status_of_most_recent_investigation}.
Stakeholder and Customer Advisories
Most Recent Stakeholder Advisory: The most recent stakeholder advisory issued was {most_recent_stakeholder_advisory}.
Most Recent Customer Advisory: The most recent customer advisory issued was {most_recent_customer_advisory}.
Initial Access Broker
Most Recent Entry Point: The most recent entry point used by an initial access broker was {most_recent_entry_point}.
Most Recent Reconnaissance Period: The most recent reconnaissance period for an incident was {most_recent_reconnaissance_period}.
Post-Incident Analysis
Most Significant Root Cause: The most significant root cause identified in post-incident analysis was {most_significant_root_cause}.
Most Significant Corrective Action: The most significant corrective action taken based on post-incident analysis was {most_significant_corrective_action}.
What Do We Measure?
Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.
These are some of the factors we use to calculate the overall score:
Identify exposed access points, detect misconfigured SSL certificates, and uncover vulnerabilities across the network infrastructure.
Gain visibility into the software components used within an organization to detect vulnerabilities, manage risk, and ensure supply chain security.
Monitor and manage all IT assets and their configurations to ensure accurate, real-time visibility across the company's technology environment.
Leverage real-time insights on active threats, malware campaigns, and emerging vulnerabilities to proactively defend against evolving cyberattacks.
