Thursday, September 23, 2021
Thanks first to the Solarwinds attack and then Executive Order 14028 - Improving the Nation’s Cybersecurity, the security of the software supply chain has become the hot topic of the year. The Colonial Pipeline ransomware attack made critical infrastructure security front page news. This talk will look at the intersection of these two challenges - why securing the supply chain for critical OT environments is now an urgent priority for asset owners, suppliers and government agencies. In this session you will learn:
- Why supply chain and ransomware attacks are dramatically increasing
- The new obligations set out in EO14028 that industry will need to follow
- How EO14028 requirements will ripple far beyond government contracts
- How Software Bill of Materials (SBOMs) will help secure software supply chains
- What asset owners should be demanding from their OEM Vendors to secure OT systems
- Why AI will be crucial for locating and prioritizing product vulnerabilities
How do SBOMS currently work (examples)- What are they? Who is currently utilizing them?
How can asset owners use SBOM?
Additional dialogue if time allows:
Are they secure? Is the code being updated upstream?
Who is going to maintain SBOMs?
Who at the facility (asset owner/end user) is responsible for maintaining and monitoring the SBOM?
Concept to Commissioned - A UK NG Case Study Implementing an Innovative Networking Solution called SEL OT SDN (Physical and Virtual)
There are plethora of incredible cyber risk reducing innovative solutions being brought to market. This discussion will highlight the milestones required for an OT system owner and vendor to overcome in order to bring significant risk reducing solutions from innovation, to market, to implementation. Operational Technology Software Defined Networking (OT SDN) will be the backdrop to this story line between UK NG and SEL.
Topics to be discussed in order for innovation to be implemented:
- Innovation requires acceptance into standards and frameworks
- Standard and frameworks require acceptance into regulation
- Regulation is important for acquisition and to become added to specification and designs
- Timing and funding become involved to put innovation into new or legacy projects
- Innovation acceptance additionally involves training, education, experience, and cultural change
- Any innovation also requires careful consideration to not increase operational risk
All of the above compete with adversaries who use the time it take to move from innovation to implementation to find gaps and seams and weaknesses in these system before they are even deployed. This presentation will address ways to reduce the time between milestones to implement innovation faster and safer to ultimately reduce risk?
Friday, September 24, 2021
- OT monitoring
- SOC integration
- Digital Immunity
- 3rd Party Risk
- Remote Access
Panel: Innovation and Security- How can we embrace technology innovation securely (Physical and Virtual)
Technology Maturity - what impacts does this have on the implementation?
How much disruption when integrating into existing processes should be expected and how can we keep that to a minimum?
How can we view "innovation" as a journey rather than a destination-is the environment adaptable? How can it be made adaptable? Are the "innovations" scalable so we are not always starting from scratch?
How do we keep risk to a minimum? What does the process of execution look like?
Is speed of the implementation prioritised and what impacts does it have
- Vanishing divide between IT and OT
- What is the voice of the customer?
- Dealing with the hype and understanding the threats
- Integration of technologies and partnerships
- Beyond OT Cybersecurity to Asset Performance Management
How are we:
Cybersecurity needs to lead the business case
Getting data out of OT?
Using data coming out of OT?
How can we protect it once we have it?
Is it accessible?
How are we using the data?
How can we separate actionable intelligence from white noise?
What is the business case, why are we gathering it?
Further panellists to be announced.
OEMs are taking a more active approach to product security and development, Patching is one of the oldest and most traditional ways to manage risk. It also is a slow and expensive way to manage risk so it is frequently avoided in the OT world. What else should be considered to manage risk?