How can you navigate conflicting priorities between system functionality and cybersecurity measures?

Balancing system functionality and cybersecurity measures is a challenge, but attainable. It starts by identifying critical functionality and assessing vulnerabilities, then prioritizing the security measures. Protecting the critical functionality first is key, then sufficient security for the less critical functionality can be implemented. Tradeoffs will need to be considered in the process with an impact evaluation to guarantee the security measures do not sway an efficient system too much.

This is the balance on managing cyber risk to the enterprise. You must understand the possibility versus probability and the cost in any architecture’s applied cyber controls. Last, accept that the cyber controls need to be revisited, this is never a “one and done” activity.

"Need Aspects Assessment" between System Functionality -Vs- Cybersecurity(CS), has now become a subject matter of debates,conflicts,and tug-of war between the different engineering delivery groups ,in an organization. for the End user performance,flexibility,freedom from snooping -are prime, conflicted by the need to ensure data security, hacking prevention, dissecting & preventing IP port/address mirroring (to name a few) the (CS) teams tasks! Above issues imply proper System design& capacity studies for IT infra, in conjunction with the CyberSecurity, at the initial stages itself! (CS) rides on the IT fabric ,both in OS+Hardware, hence,"Flexible" IT infra by design is a good start point, to get both to stay in peace in 1 place!!

In the automotive industry, balancing system functionality with cybersecurity starts with a comprehensive needs assessment. Identify the core functionalities critical to the vehicle’s performance (e.g., ADAS, infotainment) and assess how these interact with cybersecurity requirements. Prioritize safety-critical systems, understanding that security breaches in these areas can lead to catastrophic failures. Create a risk-based approach, focusing on the highest-risk entry points, while ensuring minimal performance trade-offs. Collaboration across teams engineers, cybersecurity experts, and stakeholders is key to aligning goals.

Prioritizing functionality and security is a necessary balancing act:?This statement highlights the core challenge in cybersecurity. It's not about choosing one over the other, but finding the sweet spot where both function and security are optimized. A system that's overly secure might be cumbersome to use, while one with weak security is vulnerable.

As a crucial step, conducting a Cybersecurity Risk Assessment is essential to determine the appropriate Security Levels according to industry standards, such as IEC 62443. This process helps identify potential threats and vulnerabilities, allowing for the implementation of tailored security measures that align with operational needs and regulatory requirements. By embedding this assessment early in the design phase, you ensure that security is not just an afterthought but a fundamental aspect of system development and deployment.

Risk Analysis(RA)- Need Aspects &Practices- is a Dynamic and periodic activity for a Robust IT infra. Any IT infra team,which stays static to RA,may pay a serious price! RA needs updation based upon 1.Dynamics,aggregation of critical data and info,applications in a IT infra( resident user activity driven) - 2.External Cyberthreat dynamics, which are ever changing. "RA" updation leads to a better anticipation and readiness to prevent/mitigate/counteract to present& future Cyberthreat, keeping the Management in loop, thus preventing disruption & chaos. Best IT practices ,include both flexible IT HW,Intra net/Internet isolation,Data archival,isolation as practices.For CyberAttacks - frontblock,fabric layer, outgoing traffic curation are good

In the automotive context, risk analysis for conflicting priorities between system functionality and cybersecurity involves identifying potential threats, vulnerabilities, and their impacts on both vehicle safety and performance. Use frameworks like ISO/SAE 21434 to systematically assess risks. Prioritize high-impact risks, such as vulnerabilities in critical ECUs (Electronic Control Units) or connected vehicle interfaces, which could be exploited remotely. Weigh the consequences of cyber breaches (e.g., vehicle control loss) against the impact of functionality degradation, aiming to strike a balance between security and user experience.

Risk analysis begins in the beginning of a program. You must live with the analysis on a day to day basis. One issue is that “new” (actually these could be overlooked as much as new) Risks. We have had several interesting Risks that have shown up with automation of aircraft for Airbus and Boeing, in gear metal softness that was a surprise given the testing requirements, training in manufacturing, software distribution, chip issues, etc. All you need to do is read the news papers, accident reports, watch YouTube, the number of data breaches, etc.

Realize uma análise de risco para avaliar as possíveis consequências de comprometer a seguran?a ou a funcionalidade. Isso envolve identificar amea?as potenciais, vulnerabilidades e o impacto de possíveis falhas. A análise vai ajudar a priorizar quais áreas precisam de maior prote??o sem comprometer a usabilidade do sistema.

There are many aspects of cyber security, especially for the web applications applicable OWASP topics should be taken as requirements not as consideration. Although the design phase covers many issues it is a continuous process to keep the implementation in alignment with the design.

During the design phase in automotive systems engineering, integrating cybersecurity with system functionality requires a security-by-design approach. Incorporate cybersecurity measures early, embedding them into the architecture alongside functional requirements. Use threat modeling and security requirements engineering to ensure critical systems, such as autonomous driving features or vehicle-to-everything (V2X) communication, are protected without compromising performance. Employ secure software development practices, redundancy for critical safety functions, and ensure hardware (e.g., ECUs) can support cryptographic functions without impeding system responsiveness or reliability.

Again, the DFSS has a process but it is rarely or truly followed. The team must be dedicated to continuous improvement of the processes. An issue in all phases of development is the change in requirements that cause delays, cost and general unhappiness with the program and turnover. Additionally, fresh look at the program can find overlooked items from familiarity with a project.

Durante o projeto do sistema, integre medidas de seguran?a desde o início, procurando solu??es que mantenham a funcionalidade necessária sem sacrificar a prote??o. Use práticas de desenvolvimento seguro, como o princípio do menor privilégio e a defesa em profundidade, para garantir que o sistema seja funcional e seguro. A colabora??o entre desenvolvedores e especialistas em seguran?a é fundamental.

To maintain good quality and security, this requires lots of testing and iteration using different methods. You need to assess what your goals are in the models. From there, building upon the first principles (basics) you'll be able to apply changes to get to your goals. Once you have you have a solid learning strategy, you can find ways for ongoing integrations. It's important to have small tests to make sure new features and training work in the model updates. Build a small proof of concept to showcase the technology, that'll solidify your understanding and help you communicate it to others. Important to not dwell too long on development, need to release versions as soon as possible when ready.

In the automotive industry, continuous review is essential for maintaining the balance between system functionality and cybersecurity as vehicles evolve. Implement a robust lifecycle management process that includes regular security assessments, software updates, and vulnerability scans throughout the vehicle’s life. Use over-the-air (OTA) updates to patch vulnerabilities without disrupting system functionality. Establish feedback loops from real-world data, monitoring for emerging threats. Collaboration with third-party cybersecurity firms and industry standards (like ISO/SAE 21434) ensures that security measures remain up to date, even as new vehicle functionalities are introduced.

DFSS requires continuous review and should be integral to your program. Problem is when everyone shows up to the meeting. I had working teams that provided continuous update in the program and quantify every aspect of a program by exception - new risk found, risk level went up, sudden cost change, scheduling, design issues, etc. That way I could assign the correct people to review, access, and correct the issues beginning with the people doing the work, the customer, etc. Example: A drawing had to be modified and instead of modifying and releasing, my designer would walk to the line and find out how the task is really done and to correct drawings to include those and new changes with manufacturing input!

Mantenha uma revis?o contínua do sistema para ajustar e melhorar as medidas de seguran?a conforme novas amea?as surgem e o sistema evolui. Atualize regularmente as práticas de seguran?a e teste a eficácia das medidas implementadas. Isso garante que o equilíbrio entre funcionalidade e seguran?a seja mantido ao longo do tempo.

Educate the functionality team about the importance of security and vice versa. Sometimes conflicts arise from a lack of understanding of the other side’s priorities. Foster a culture where security is seen as an enabler of functionality, not a blocker. By positioning security as a key component of successful system functionality, you can help reduce conflicts.

From a systems perspective, track all of your relevant policies as requirements, mapped to the functions then components that support compliance. If your teams focused on the sub-system and component level design find there are required security solutions / capabilities that make their design impossible, just like any other requirement that impacts system development, work with stakeholders to: 1. Ensure understanding of the intent of the policy 2. Determine if there are ways to meet the policy through system user and organizational implemented policies 3. Identify ways the policies have been adopted successfully in other systems Finally, leverage Internal Research and Development resources to provide a novel solution to the policy.

In the automotive industry, user training is critical to ensuring the effectiveness of cybersecurity measures without hindering system functionality. Train both end-users (drivers) and service technicians on best practices for cybersecurity, such as recognizing phishing attempts through connected vehicle systems or safely managing OTA updates. For technicians, provide guidance on secure handling of diagnostic tools and firmware updates. This helps prevent unintended security breaches while maintaining vehicle performance. Clear, accessible documentation and in-vehicle prompts can also guide users in maintaining cybersecurity without overwhelming them or impairing usability.

The news has shown the importance of training. Pilots being trained using cockpits not like what they will be operating. Processes not followed nor manufacturing processes not following and no paper trail. Training and proper methods must be developed and followed. Continuous improvement, updated testing, refresh training, etc, need to be improved. Again, review is important.

Treine os usuários do sistema sobre práticas de seguran?a cibernética e como utilizar as funcionalidades de maneira segura. Isso ajuda a mitigar riscos e a garantir que as medidas de seguran?a implementadas sejam efetivamente utilizadas. O treinamento contínuo mantém os usuários atualizados sobre novas amea?as e práticas recomendadas.

Garanta que as políticas de seguran?a cibernética da organiza??o estejam alinhadas com as necessidades funcionais do sistema. Defina diretrizes claras que equilibrem seguran?a e usabilidade, permitindo flexibilidade onde necessário. O alinhamento de políticas ajuda a evitar conflitos entre diferentes prioridades, criando um caminho claro para o desenvolvimento e a opera??o do sistema.

In the automotive industry, aligning policies with both system functionality and cybersecurity is crucial for seamless integration. Ensure that company policies reflect industry standards like ISO/SAE 21434 and UNECE WP.29, establishing a governance structure that prioritizes both security and performance. This includes creating clear guidelines for secure software development, data privacy, and third-party supplier compliance. Policies should also support cross-functional collaboration, enabling teams to address security concerns without sacrificing critical vehicle functionalities, such as safety or user experience. Regular audits ensure policies remain effective and aligned with evolving technology.