Keeping DPI technology available to all
The DPI Consortium is an independent, non-profit, 501(c)(6) tax-exempt organization committed to:
Provide freely available educational resources regarding the history of Deep Packet Inspection technology and development to:
make available hard-to-find historical information relevant to patent validity challenges
encourage innovation in the area of DPI
deter PAE activity
improve patent quality
Encourage interested parties to add to the prior art repository
For many years, automotive software was developed with the thought that the vehicle network and electronic control units (ECUs) were not exposed to or of interest to malicious hackers. Consequently, software developers and cybersecurity engineers had mismatched views and goals when projects began to include cybersecurity requirements.
However, major technological innovation is driving substantial automotive industry changes. Customers are becoming more aware that security is a buying concern and are looking for indications of safer products rather than just exercising brand loyalty. Manufacturers must implement more stringent security management where it is not well standardized or even established at all.
After reviewing a lot of the feedback from our readers, one theme became very clear. People like seeing technical videos and reading articles that contain real troubleshooting scenarios, or tools/features in use.
I get it, when I see a ‘dog and pony’ video where someone clicks around explaining a feature, I often wonder “So what?” or “How could I use that feature”.
When I worked with several vendors and would talk to their clients, the last thing we talked about was products. I would say over 75% or the conversation was focused around what they do, how do they do troubleshoot, roles and responsibilities, training and education, methodology, corporate process, problems that take the longest to close and finally budgetary limits.
Many times, I work with them on existing problems, with existing tools and their staff to better understand their challenges and if we fix a problem or make a break through, awesome.
I took that format and started this series that is comprised of a Scenario, Solution and Example.
I always welcome your feedback so I can determine if I should continue this format.
Cheers
