Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
Transcript of SCADA
decide now if the system is a good target but before we jump in Map out the packet frame MODBUS DNP3 or a proprietary version is it a flavor of: What frames are the most traffic? These are critical to daily operation Target these if: immediate change Noticeable Could cause significant upset of operations What frames are
the least traffic? These are probably
the commands that
modify and reprogram
the system Target these
if: Logical, subtle change Could cause drastic
propagated effects Ultimately changes
of the unit Begin to analyze the frame specifically bit by bit Which blocks are changing? CRC? How can we correctly form a packet Look at specific values data values trigger an alarm? cause a change? What does each packet DO Requires complex computation But this won't stop a dedicated attacker... What kind of packet is it? Solicit a reply? If not... ability to try out commands But can a vector ever really KNOW? No, consider the halting problem But that didn't stop automated cyber attacks Metasploit for SCADA? Its already underway... Ultimately Consider automated SCADA attack vectors NOW targeted at protocol because its a weak link but its becoming more well understood difficulty of the problem has never stopped attackers before Stuxnet x 10 so what have we shown? Automated attack vectors ARE worth considering Protocols have generic features Common vulnerabilities Though its a challenging task... Standardized though they do have standards and focus on SCADA specifics timestamp? parity? what is the range? Recurring? flags? Questions? Why is this important? How can we attack it?