Posts

NIS2: 1. Perform a gap analysis

05/03/2024/in Educational

We wrote here https://www.sorinmustaca.com/how-to-nis2-eu-directive/ that the first step in implementing NIS2 requirements is to perform a gap analysis.

The most critical part when performing a gap analysis is to define upfront against which standard or security framework are you comparing the existing situation.

It is usual when performing a gap analysis of security maturity to compare against ISO 27000 standard, the ISO 27001 in particular.

Performing a gap analysis on the security stance of a company following ISO 27001 involves comparing its current security measures and practices against the requirements specified in the ISO 27001 standard.

This analysis helps identify areas where the company’s security posture aligns with the standard (compliance) and areas where there are gaps or deficiencies (non-compliance). Here’s a technical breakdown of the process:

Familiarize with ISO 27001
Understand the ISO 27001 standard and its security requirements. This includes studying the Annex A controls, which represent a comprehensive set of security best practices.
Define the Scope
Determine the scope of the analysis, starting with which areas of the organization’s security management system (SMS) will be assessed, such as specific departments, processes, assets, or locations.
Then focus on which parts of the company’s operations will be assessed. This could include networks, systems, applications, physical security, personnel, and other relevant components.
Keep in mind that usually the goal of the company is not reaching ISO 27001 compliance but to see their maturity level and see how prepared they are cybersecurity events and incidents.
This means that the parallel to ISO 27001 controls (see below) should not be extremely strict, unless the goal really is achieving the ISO 27001 certification.
Conduct Interviews and Gather Information
Collaborate with key stakeholders, security personnel, and IT staff to collect relevant documentation.
Relevant documentation is anything related to the company’s security practices, policies, procedures, risk assessments, and controls.
This includes also security manuals, configuration details, system logs, incident reports, risk assessments, and other related documents.
Create a Gap Analysis Checklist
Develop a detailed checklist that maps the ISO 27001 controls to the company’s existing security controls and practices. The checklist should include relevant information for each control, such as descriptions, implementation status, supporting evidence, and any gaps or deviations. Always keep in mind what was decided in “2. Define the scope”, because this will give you the depth of the analysis.
Assess Current Security Controls for Non-Compliance
For each control in the checklist, assess whether the company has implemented the control as specified by ISO 27001. Evaluate the effectiveness of the existing controls in meeting the standard’s requirements. Identify gaps and areas where the company’s security measures do not meet the standard’s expectations. These gaps may include missing controls, insufficient implementation, inadequate documentation, or deviations from best practices.
Prioritize and Rate the Gaps
Classify the identified gaps based on their severity and potential impact on security. Assign a risk rating to each gap to help prioritize remediation efforts.
Propose Remediation Measures
For each identified gap, suggest specific remediation measures to address the deficiencies. These measures should align with ISO 27001 requirements and aim to improve the company’s security posture.
Create an Action Plan
Create a detailed action plan that outlines the steps to be taken to address each identified gap. This plan should include timelines, responsibilities, and resources required for implementation.
Reassess and Update
Periodically repeat the gap analysis process to assess the company’s security stance and ensure continuous improvement. Regularly review and update the action plan based on new threats, changes in the organization’s structure, or updates to the ISO 27001 standard.
Monitor and Review Progress
Once the action plan is underway, monitor the progress of each remediation effort and periodically review the improvements made. Track the status of the gaps and ensure that the company is moving towards full compliance with ISO 27001.

References:

The post NIS2: 1. Perform a gap analysis first appeared on Sorin Mustaca on Cybersecurity.

How-To: NIS2 EU Directive

04/03/2024/in Educational

The NIS2 Directive is a European Union legislative text on cybersecurity that supersedes the first NIS (Network and Information Security) Directive, adopted in July 2016.

NIS vs. NIS2

While the first NIS (Network and Information Security) Directive increased the Member States’ cybersecurity capabilities, its implementation proved difficult, resulting in fragmentation at different levels across the internal market. To respond to the growing threats posed with digitalisation and the surge in cyber-attacks, the Commission has submitted a proposal to replace the NIS Directive and thereby strengthen the security requirements, address the security of supply chains, streamline reporting obligations, and introduce more stringent supervisory measures and stricter enforcement requirements, including harmonised sanctions across the EU.

NIS2 strengthens security requirements in the EU by expanding the NIS scope to more sectors and entities, taking into account

the security of supply chains,
streamlining reporting obligations,
introducing monitoring measures,
introducing more stringent enforcement requirements,
adding the concept of “management bodies” accountability within companies, and
harmonizing and tightening sanctions in all Member States.

To achieve the above mentioned goals, NIS2 requires member states to take a number of measures that forces them to work together:

Establish or improve information sharing between member states and a common incident response plan that coordinates with other member state plans
Establish a national Computer Emergency Response Team
Strengthen cooperation between public and private sector entities

In a nutshell, companies can stay compliant with the NIS2 Directive by

establishing an effective monitoring system that can detect intrusions, detect suspicious activities, and alert the authorities when necessary
developing comprehensive plans that detail how they will respond to an attack and what steps they will take to recover from it.

The official website of the EU for the NIS2 Directive has prepared an FAQ with many good questions and answers.

However, what the website is not saying (for good reasons) is how should companies start to prepare for implementing the directive.

How to start the compliance path

In order to successfully start implementing the requirements, the following steps should be implemented in this order. We will publish articles about pretty much each of these topics.

1.Conduct a gap analysis

Assess your company’s current cybersecurity practices, policies, and infrastructure against the requirements of the NIS2 directive.

Identify any gaps or areas that need improvement to comply with the directive.

Dedicated article: https://www.sorinmustaca.com/nis2-1-perform-a-gap-analysis/

2.Designate a responsible person or team

Appoint an individual or a team responsible for overseeing the implementation of the NIS2 directive within your company. This could be a dedicated cybersecurity team or an existing department with relevant expertise.

Dedicated article: https://www.sorinmustaca.com/nis2-2-designate-a-responsible-person-or-team/

3.Establish a cybersecurity framework

Develop or update your company’s cybersecurity framework to align with the NIS2 directive. This framework should include policies, procedures, and technical controls to protect your network and information systems effectively.

Dedicated article: https://www.sorinmustaca.com/nis2-3-establish-a-cybersecurity-framework/

4.Perform a risk assessment

Conduct a comprehensive risk assessment of your company’s network and information systems. Identify potential threats, vulnerabilities, and risks that may impact the availability, integrity, and confidentiality of critical systems and data. This assessment will help you prioritize security measures and allocate appropriate resources. Risk management and assessments are an ongoing process. Once one risk assessment is carried out, it is important to schedule regular updates to ensure all steps are maintained.

Dedicated article: https://www.sorinmustaca.com/nis2-perform-a-risk-assessment/

5.Implement security measures

Based on the risk assessment findings, implement appropriate security measures to mitigate identified risks. This may include network segmentation, access controls, intrusion detection systems, incident response procedures, encryption, employee training, and regular security updates, among others.

Dedicated article:

6.Establish incident response capabilities

Develop an incident response plan and establish procedures for detecting, responding to, and recovering from cybersecurity incidents. Ensure the assigned employees are trained on how to recognize and report security breaches promptly. Business continuity is a very complex topic, which must be planned with a lot of time in advance and it requires extra resources (both human and financial).

Dedicated article:

7.Continuously Monitor and review

Implement mechanisms to continuously monitor and assess your network and information systems for potential threats. Regularly review and update your cybersecurity measures to adapt to emerging risks and changes in the threat landscape.

Dedicated article:

8. Maintain documentation and records

Keep comprehensive documentation of your cybersecurity measures, risk assessments, incident response activities, and any other relevant information. This documentation will serve as evidence of compliance and may be required for regulatory audits or investigations. A good record might save your company legal and regulatory repercussions in case of a major incident (cyber related or not).

Dedicated article:

9.Engage with regulatory authorities

Stay informed about any reporting or notification obligations outlined in the NIS2 directive. Establish communication channels with the relevant regulatory authorities and comply with any reporting requirements or inquiries they may have. NIS2 strives to improve EU-wide communication and sharing of cyber events in order to better prepare answers and reactions. Communication has never been more important than now.

Dedicated article:

10. Define KPIs for cybersecurity and measures taken based on them

In order to measure the effectiveness of the cybersecurity, you need to define metrics that allow identifying and quantifying changes. Example of metrics are number of incidents, types of incidents, how many trainings have been made, how many people were trained, how many pentests were made and how many issues were identified, and many more.

Dedicated article:

The post How-To: NIS2 EU Directive first appeared on Sorin Mustaca on Cybersecurity.

Implementing secure over-the-air (OTA) updates in embedded devices

02/03/2024/in Educational

This is a follow up article related to Secure Booting and Secure Flashing. It is the 5th article related to Strengthening the Security of Embedded Devices

Implementing secure over-the-air (OTA) updates in embedded devices requires careful consideration of various security aspects.

Here are some key steps to implement secure OTA updates:

1. Secure Communication Channel
– Use secure protocols such as HTTPS or MQTT over TLS/SSL to establish an encrypted communication channel between the device and the update server.
– Authenticate the server using certificates to ensure the device is communicating with a trusted source.
– Employ strong encryption algorithms to protect the confidentiality and integrity of the update data during transmission.

2. Code and Firmware Integrity
– Digitally sign the firmware updates using a private key and verify the signature using a corresponding public key on the device.
– Implement mechanisms such as checksums or hash functions to verify the integrity of the received update files.
– Use secure boot techniques to ensure that only trusted and authenticated firmware updates are installed on the device.

3. Access Control and Authorization
– Authenticate and authorize the device before allowing it to download and install updates.
– Implement access control mechanisms to ensure that only authorized devices or users can initiate or perform updates.
– Employ secure user authentication methods such as username/password, certificates, or tokens to validate the device’s identity.

4. Incremental Updates and Rollbacks
– Support incremental updates to reduce the data transfer size and minimize the update time, especially for large firmware files.
– Implement mechanisms to handle update failures or rollbacks in case of errors or compatibility issues during the update process.

5. Secure Storage
– Store the downloaded update files securely on the device to prevent unauthorized access or tampering.
– Use encryption and access control mechanisms to protect the firmware updates from extraction or modification by unauthorized entities.

6. Logging and Auditing
– Maintain logs of OTA update activities, including details such as update versions, timestamps, and device identification.
– Implement auditing mechanisms to track and monitor update processes, detecting any suspicious or unauthorized activities.

7. Regular Security Updates and Patch Management
– Continuously monitor for security vulnerabilities and release patches or updates as needed.
– Implement a robust patch management system to ensure timely deployment of security updates to the embedded devices.

8. Testing and Validation
– Conduct thorough testing and validation of the OTA update process, including functional, security, and compatibility testing.
– Perform vulnerability assessments and penetration testing to identify potential weaknesses in the OTA update implementation.

Last, but not least:

You need to have a secure backend that serves the updates. Make sure that you have configured the server correctly, secure and that it is always updated to the latest version.

Follow these best practices to establish a secure OTA update mechanism, ensuring that devices receive timely and secure firmware updates while mitigating the risk of unauthorized access, tampering, or exploitation during the update process.

The post Implementing secure over-the-air (OTA) updates in embedded devices first appeared on Sorin Mustaca on Cybersecurity.

How to convince Top Management to invest in cybersecurity and secure software development

27/02/2024/in Educational

I’ve heard many times IT people and Software Developers complaining that they have difficulties to sensibilize their managers to invest more in cybersecurity.

Also some employees of my customers in the cybersecurity consulting area show sometimes frustration when we are talking about priorities of their top management – cybersecurity is almost neveve one until it is too late.

When I talk to C-Level of the organizations that book us for consulting, I am telling them that organizations face an increasing number of cyber threats these days compared to 10-20 years ago (yes, we are so old).

They have a lot of risks like data breaches, ransomware attacks, and intellectual property theft and their only chance to survive these is to investing early in robust cybersecurity measures and secure software development practices.

However, convincing top management to allocate resources and invest in these areas is a challenging task for everyone, me included.

Unfortunately, investing in cybersecurity is a bit like investing in a optional insurance: you want it so that you can stay relaxed, but you know you are not forced to buy it, so you try to find the cheapest one that covers more or less your risks. Additionally, you don’t even want to invest much in finding the right one that suits you, because you considered even this time almost a waste. In the end, you do something just for the sake of being able to sleep better, but deep down in your mind you know that you don’t actually know if it will help you if something happens, so you just tell yourself: this will not happen to me. Sounds familiar, right?

Here are some thoughts that you can expand if you want, that can help you persuade your management to invest in cybersecurity and secure software development.

Understand the Risks and Consequences: Before making your case to top management, thoroughly comprehend the risks associated with inadequate cybersecurity and insecure software. Research recent cyber-attacks and data breaches to present real-life examples of the devastating consequences that organizations have faced. Emphasize the financial, reputational, and legal ramifications that can result from such incidents.
Communicate in Business Terms: Top management is primarily concerned with the organization’s success and business continuity and growth. To effectively persuade them, it is essential to frame your argument in terms of business impact. Highlight how cybersecurity and secure software development directly contribute to the organization’s profitability, customer trust, regulatory compliance, and competitive advantage.
Showcase the ROI of the investment: Present a compelling return on investment (ROI) analysis to demonstrate the financial benefits of investing in cybersecurity and secure software development. Calculate potential cost savings by comparing the expenses associated with preventing a breach to the financial implications of recovering from an attack. Additionally, highlight the positive impact on productivity, customer retention, and brand value that can result from a strong cybersecurity posture.
Address Regulatory Compliance: Many industries (medicine, automotive, software development) have stringent data protection regulations and privacy laws. Highlight the legal and financial risks of non-compliance, such as substantial fines and damage to the organization’s reputation. Explain how investing in cybersecurity and secure software development aligns with regulatory requirements, safeguarding the organization against potential penalties and legal repercussions.
Present Industry Benchmarks and Best Practices: Illustrate industry benchmarks and best practices to establish a standard of excellence in cybersecurity and secure software development. Share case studies of organizations in the same industry that have suffered cyber-attacks or data breaches, emphasizing how investing in security measures could have prevented or mitigated the damage. Highlight recognized frameworks and certifications, such as ISO 27001 and PCI DSS, to demonstrate the organization’s commitment to security.
Present the Threat Landscape: Explain the main cyber threats and the need for investment in cybersecurity. Highlight risks such as ransomware, social engineering, and zero-day vulnerabilities. Illustrate the importance of regular security assessments, penetration testing, and employee training to stay ahead of new threats. Explain that cybersecurity is not a one-time investment but an ongoing process that requires continuous attention.
Come up with a Step-By-Step Plan: Explain how a plan in several steps will help to mitigate the problems without causing too much disruption in the daily business. If business people want to hear anything more often , than it is that it won’t cost too much.
Tailoring the solution in many steps and matching your company’s needs will also allow controlling the costs involved with the implementation.

Convincing top management to invest in cybersecurity and secure software development requires a strategic step-by-step approach. No business can go all-in because cybersecurity is hard to implement, even harder to maintain and expensive..

Remember to tailor your arguments and plans to the specific needs and priorities of your organization.

With a well-structured and persuasive approach, you can encourage top management to prioritize and allocate resources to safeguard the organization’s digital assets and ensure its long-term success in the face of evolving cyber threats.

If you need help to talk to your management, you can book the consulting services of Endpoint Cybersecurity here.

The post How to convince Top Management to invest in cybersecurity and secure software development first appeared on Sorin Mustaca on Cybersecurity.

The Importance of Training Employees in Cybersecurity

26/02/2024/in Educational

In today’s increasingly interconnected world, cyber threats pose a significant risk to businesses of all sizes.

As technology advances, cybercriminals become more sophisticated, making it imperative for organizations to prioritize cybersecurity measures.

While investing in robust infrastructure and advanced tools is crucial, one often overlooked aspect is the training of employees.

This article aims to

convince managers of the importance of training employees about cybersecurity
provide material for employees to convince their managers to invest in training
highlight the significant benefits it brings to the organization

There are

Human Error: The Weakest Link
Despite technological advancements, employees remain the weakest link in an organization’s cybersecurity defense. Studies consistently show that human error is the leading cause of security breaches. Employees are vulnerable to social engineering attacks, phishing attempts, and inadvertently downloading malware. By training employees, you can minimize the risks associated with human error, empowering them to recognize and respond appropriately to potential threats.
Cybersecurity training serves as a powerful tool to enhance employees’ understanding of potential threats and the implications of their actions.
Employees are at the forefront of an organization’s defense against cyber threats. By providing comprehensive cybersecurity training, managers empower their employees to actively contribute to the organization’s security posture.
When employees are aware of their role in protecting sensitive data, they become vigilant in their interactions with technology and more likely to report suspicious activities promptly.
This collective effort transforms every employee into an essential component of the organization’s defense mechanism.
Enhanced Threat Awareness
Cyber threats are constantly evolving, making it crucial for employees to stay informed about the latest trends and attack vectors. Cybersecurity training equips employees with the knowledge to identify warning signs, suspicious activities, and potential vulnerabilities. It cultivates a culture of vigilance, enabling employees to report and address security incidents promptly, reducing the likelihood of successful cyber attacks.
By creating awareness about these attack vectors,employees develop a proactive mindset in identifying and thwarting potential attacks. Awareness training equips them with the knowledge to recognize warning signs, suspicious emails, and malicious websites, thus significantly reducing the risk of falling victim to cybercriminals.
Safeguarding Sensitive Information
Every organization possesses sensitive information, whether it’s customer data, intellectual property, or financial records. A single data breach can lead to severe financial and reputational damage. Training employees about cybersecurity best practices creates a security-conscious workforce. They understand the value of data protection and the potential consequences of mishandling sensitive information. Consequently, they become more proactive in implementing security measures and adhering to established protocols.
Compliance and Regulatory Requirements
Numerous industries are subject to strict regulations regarding data protection and privacy. Non-compliance can result in substantial penalties and legal repercussions. By providing cybersecurity training, organizations ensure that employees understand and comply with relevant regulations. Training programs can address specific industry requirements, such as handling personally identifiable information (PII) or protected health information (PHI), reducing the risk of non-compliance and associated penalties. Cybersecurity training ensures that employees are aware of their responsibilities in handling sensitive data. By instilling a comprehensive understanding of compliance regulations and data privacy best practices, organizations can avoid costly penalties and maintain the trust of their customers and stakeholders.
Incident Response and Mitigation
Even with strong preventative measures, it’s essential to have an effective incident response plan in place. Cybersecurity training equips employees with the knowledge and skills to respond promptly and effectively to security incidents. Training covers topics such as incident reporting, containment procedures, and communication protocols. Well-prepared employees can limit the scope and impact of security breaches, reducing downtime and potential financial losses.
Fostering a Security Culture
Training employees in cybersecurity sends a clear message: protecting digital assets is a collective responsibility. By prioritizing cybersecurity training, managers foster a culture of security within the organization. When employees recognize that cybersecurity is integral to their roles, they become proactive participants in maintaining a secure environment. This cultural shift significantly enhances the organization’s overall security posture and resilience against cyber threats.

In today’s digital landscape, no organization can afford to neglect cybersecurity training for its employees. By investing in comprehensive training programs, managers empower their workforce to become the first line of defense against cyber threats.

Training enhances threat awareness, mitigates human error, safeguards sensitive information, ensures compliance, and fosters a security-conscious culture.

By prioritizing cybersecurity training, organizations bolster their resilience and reduce the risks associated with cyber attacks, safeguarding their reputation, finances, and future success.

The post The Importance of Training Employees in Cybersecurity first appeared on Sorin Mustaca on Cybersecurity.

Preventing Attacks and Securing the Supply Chain in the Security Software Industry

25/02/2024/in Educational

The security software industry plays a vital role in safeguarding sensitive data and protecting digital infrastructure.

However, the industry itself faces a significant threat from supply chain attacks.

Supply chain attacks occur when cybercriminals target vulnerabilities within the supply chain to compromise software or hardware products before they reach the end-users.

By infiltrating the supply chain, attackers can inject malicious code, backdoors, or vulnerabilities, thereby compromising the security of the software.

Such attacks can have far-reaching consequences, as they can compromise the confidentiality, integrity, and availability of critical systems and data.

These attacks have the potential to undermine the integrity and trustworthiness of security software, leading to severe consequences for individuals, organizations, and even nations.

This article examines the damaging impact of supply chain attacks on the security software industry, while also delving into preventive measures and strategies to secure the supply chain.

Impact:

Loss of Trust: Supply chain attacks erode trust in security software products and the industry as a whole. When high-profile incidents occur, customers may lose confidence in the ability of software vendors to protect their assets and data.
Financial Loss: The costs associated with supply chain attacks are staggering. Companies suffer significant financial losses due to reputational damage, legal consequences, customer compensation, and the costs of investigating and mitigating the attack.
Weakened Defenses: A compromised security software product can result in weakened defenses for individuals, organizations, and governments, leaving them vulnerable to further cyberattacks. This situation can have severe consequences, particularly when critical infrastructure or national security is at stake.

Preventing Attacks:

Enhanced Vendor Due Diligence: Organizations should thoroughly vet and assess the security practices of their software vendors and suppliers. This includes scrutinizing their security measures, incident response plans, and third-party audits.
Secure Development Practices: Implementing secure software development practices, such as code review, vulnerability testing, and penetration testing, can help identify and rectify potential weaknesses in software products.
Strong Authentication and Encryption: Implementing robust authentication mechanisms and encryption protocols helps protect the integrity and confidentiality of software and its supply chain components.
Regular Updates and Patching: Ensuring timely and regular updates and patches are applied to software products and their supply chain components helps address known vulnerabilities and protect against emerging threats.

Mitigations:

End-to-End Visibility: Organizations must have comprehensive visibility into their supply chain, including the identification of all suppliers and the ability to monitor their security practices throughout the software development lifecycle.
Supply Chain Risk Assessment: Conducting a thorough risk assessment helps identify potential vulnerabilities and risks within the supply chain. This assessment should encompass all stages, from design to distribution, and involve evaluating suppliers, their security practices, and their access controls.
Supplier Contracts and Agreements: Organizations should establish clear contractual agreements with suppliers that define security requirements, incident response protocols, and breach notification obligations. Regular audits and assessments can help ensure compliance.
Incident Response Planning: Developing and regularly testing an incident response plan specific to supply chain attacks enables organizations to respond swiftly and effectively, mitigating the impact of any potential breach.

Supply chain attacks pose a significant threat to the security software industry, compromising the integrity and trustworthiness of software products. The damaging consequences include loss of trust, financial losses, and weakened defenses. However, by implementing preventive measures, such as enhanced vendor due diligence, secure development practices, and regular updates, organizations can bolster their defenses against supply chain attacks. Additionally, securing the supply chain through end-to-end visibility, risk assessments, supplier contracts, and incident response planning.

If you want to know how to address Supply Chain issues, you can contact Endpoint Cybersecurity for a free consultation.

Supply Chain Management

The post Preventing Attacks and Securing the Supply Chain in the Security Software Industry first appeared on Sorin Mustaca on Cybersecurity.

The Automotive industry’s inadequate approach towards software (in the cars)

23/02/2024/in Educational

Introduction

The automotive industry has witnessed a paradigm shift with the increasing integration of software in vehicles.

Modern cars are no longer just mechanical devices with a motor, wheels and steering; they are now sophisticated machines having dozens of CPUs (called ECU), entire computers, high speed network to connect them (called CAN-bus) and relying on complex highly distributed software systems.

In my opinion, the industry fails to adapt to this new reality and fully embrace the concept of cars as hardware running software has significant consequences.

This may sound contradictory at first, on one side they have these complex systems, on the other side they fail to adapt to this reality.

In this article, I will explore how the automotive industry is not dealing correctly with this transformation and its potential implications.

Limited Focus on Software Development and Updates

Traditionally, the automotive industry has primarily focused on hardware design and manufacturing, treating software as a necessary mean to make the hardware work.

This approach results in a lack of emphasis on software development practices and updates capabilities.

While cars are becoming more connected and dependent on software for various functionalities, manufacturers often overlook the importance of continuous software improvements and security updates.

How often do you update the software of your car? Maybe once a year in the best case, usually once every several years or not at all.

It’s not all bad, but think of how many times does Open SSL get updated in a year. Theoretically you should see an update every few months.

Insufficient Over-the-Air (OTA) Update Capabilities

Related to updates, Over-the-Air (OTA) updates have gained prominence in the software industry as an efficient means of delivering software fixes, updates, and new features directly to users.

However, the automotive industry has been slow to adopt OTA capabilities on a widespread scale out of their own will.

Limited OTA functionality not only hampers the ability to address software vulnerabilities promptly but also restricts the potential for delivering new features and enhancements to vehicles post-purchase.

Fortunately, there are many initiatives to solve this and even legislation (UNECE R 155 and R 156) that started to make software updates mandatory for releasing new car types.

Slow Adoption of Agile SW Development Processes

Agile software development methodologies have become the norm in the software industry due to their flexibility and iterative nature.

However, the automotive industry lags behind in adopting these practices. And this is politically correct formulated.

The OEMs are still working with the V-Model, despite the fact that you hear them talking about sprints, iterations, Scrum, XP programming. All these are actually implemented with small V runs and have little to nothing to do with agility.

The slow pace of development and release cycles in the automotive sector hinders the quick implementation of software fixes and feature enhancements.

This delay not only frustrates customers but also puts their safety at risk by keeping potentially critical issues unresolved for extended periods.

Lack of Consumer Education and Awareness

The general public’s understanding of cars as hardware running software is limited. First when TESLA became an important OEM, the entire world started to understand how important software is in a car.

Immediately after has the automotive industry started to feel threatened by it and they started to invest more in software, more particularly, in improving the user experience of their cars.

If I make a comparison with the mobile phones in the early 2000, the TESLA is the iPhone while the other OEMs were Nokia and the others. We all know what happened to Nokia because they did not move faster.

Consumers must continue to push the OEMs to enhance the software of their cars, but this is a slow process, because the cars with good software are expensive, and people with money usually don’t look first at the software capabilities of their cars.

Inadequate Cybersecurity Measures

As cars become increasingly connected and autonomous, they become vulnerable to cyber threats.

Unfortunately, the automotive industry has been sluggish in implementing robust cybersecurity measures to protect vehicles from potential attacks.

Insufficient attention to software security leaves vehicles open to hacking, which can lead to unauthorized access, data breaches, or even physical harm.

The industry must prioritize cybersecurity and invest in proactive measures to safeguard vehicles and their occupants.

Because cybersecurity is hard to implement, very expensive and requires specialized personnel, no OEM was willing improving their cybersecurity.

This is the reason why the UNECE R155 requires now a Cybersecurity Management System (CSMS) audit in order to allow new vehicle types.

If you are an OEM or subcontractor (Tier 1-N) then you may want to know that Endpoint Cybersecurity is offering consulting on how to implement such a CSMS and make it auditable.

Lack of standards

Same as for computers, the IT industry started to exponentially increase only after there were good reasons to use computers. Only after the Internet became main stream have businesses, regular people and families started to buy computers. So communication or inter-communication was and still is a main factor to buy hardware.

The same is happening with cars: people start to see the need for software in cars and now they start asking for better software. This can only happen if there is a market for software, but to create a market you need standards.

Android Auto and Apple Car are standards that allow 3rd parties to create apps for the cars, but the offer is extremely small and not really relevant.

In my opinion, only when cars can exchange data either directly (Vehicle to Vehicle communication – V2V) or through some infrastructure (V2I) on a large scale will we see a significant increase in software demand.
Unfortunately, the lack of standards for communication between vehicles is making this process extremely slow.

Conclusion

The automotive industry’s failure to fully embrace the concept of cars as hardware running very complex software has far-reaching consequences on the long term.

By neglecting software development, cybersecurity, and collaboration with software experts, OEMs put customer safety and satisfaction at risk. Classical OEMs have started to see too late that better software means more sales and more satisfied customers and reacted too slow to find solutions.

The limited adoption of agile development processes and inadequate OTA update capabilities further hinder progress in this domain.

To address these challenges, the industry must prioritize software as an integral part of vehicle design and manufacturing, invest in cybersecurity measures, foster collaboration with software experts, and educate consumers about the software-driven nature of modern cars.

Only through a comprehensive and proactive approach can the automotive industry truly unlock the potential of cars as hardware running software.

The post The Automotive industry’s inadequate approach towards software (in the cars) first appeared on Sorin Mustaca on Cybersecurity.