32
AMI THREATS INTRUSION DETECTION REQUIREMENTS DEPLOYMENT RECOMMENDATIONS David Grochocki et al

AMI Threats Intrusion detection requirements deployment recommendations

  • Upload
    kizzy

  • View
    33

  • Download
    4

Embed Size (px)

DESCRIPTION

AMI Threats Intrusion detection requirements deployment recommendations. David Grochocki et al. Why security?. Lures Potential attackers Smartmeters do two way communication Millions of Meters has to be replaced Serious damages just a click away. Paper description. Survey Various Threats. - PowerPoint PPT Presentation

Citation preview

Page 1: AMI Threats Intrusion detection requirements  deployment recommendations

AMI THREATSINTRUSION DETECTION

REQUIREMENTS DEPLOYMENT

RECOMMENDATIONSDavid Grochocki et al

Page 2: AMI Threats Intrusion detection requirements  deployment recommendations

WHY SECURITY? Lures Potential attackers Smartmeters do two way

communication Millions of Meters has to be replaced Serious damages just a click away

Page 3: AMI Threats Intrusion detection requirements  deployment recommendations

PAPER DESCRIPTION

Survey Various Threats

Identify Common Attack Techniques

Decompose the data to form a Attack Tree

Identify the required information which would detech the

attacks

Model an IDS

Page 4: AMI Threats Intrusion detection requirements  deployment recommendations

AMI ARCHITECTURE

Page 5: AMI Threats Intrusion detection requirements  deployment recommendations

AMI ARCHITECTURE Communication between NAN and

Gateway (DCU) – Mostly 802.15.4 or sometimes 802.11

Communication between Gateway (DCU) and Utility company – 3G, Edge, WiMax.

NAN Mesh offers reliability and robustness

But., Complicates Security Monitoring

Solution Few smart meter vendors distribute

meters which can report to the utility company directly through user’s home internet.

Page 6: AMI Threats Intrusion detection requirements  deployment recommendations

ATTACK MOTIVATION Access to a communication

infrastructure other than Internet Access to millions of low computation

devices Access to sensitive customer

information High visibility and Impact Financial Value of Consumption data

Page 7: AMI Threats Intrusion detection requirements  deployment recommendations

ATTACK SURVEY 5 Attack motivations 30 Unique attack techniques Relevant ones to AMI are alone

considered

Page 8: AMI Threats Intrusion detection requirements  deployment recommendations

PAPER DESCRIPTION

Survey Various Threats

Identify Common Attack Techniques

Decompose the data to form a Attack Tree

Identify the required information which would detech the

attacks

Model an IDS

Page 9: AMI Threats Intrusion detection requirements  deployment recommendations

DECOMPOSED ATTACK CASES DDoS attack Stealing Customer Information Remote Disconnection

Page 10: AMI Threats Intrusion detection requirements  deployment recommendations

DDOS AGAINST DCU Why? Results in data outage for many

Meters How? Install malware on meter or remote

network exploit Co-ordinate DDoS among

compromised meters Flood DCU with large packets

Page 11: AMI Threats Intrusion detection requirements  deployment recommendations

STEALING CUSTOMER INFO Why? Eavesdropping, Social Engineering How? Stealing encryption keys of the

smart meter by physically tampering or bruteforcing the cryptosystem

Capture AMI traffic Decrypt to obtain clear text

information

Page 12: AMI Threats Intrusion detection requirements  deployment recommendations

REMOTE DISCONNECT Why? Distrupt Business, Inflict loss How? Installing malware on the DCU

through physical tampering or by exploiting a network vulnerability

Identify the meters with corresponding address information

Use that information to disconnect targeted users

Page 13: AMI Threats Intrusion detection requirements  deployment recommendations

ATTACK TREE

Page 14: AMI Threats Intrusion detection requirements  deployment recommendations

PAPER DESCRIPTION

Survey Various Threats

Identify Common Attack Techniques

Decompose the data to form a Attack Tree

Identify the required information which would detech the

attacks

Model an IDS

Page 15: AMI Threats Intrusion detection requirements  deployment recommendations

INFORMATION REQUIRED System Information CPU Usage, Battery Level,

Firmware Intergrity, Clock Synchronisation

Network Information NAN Collision rate, Packet loss Policy Information Authorized AMI devices,

Authorized Updates, Address Mappings, Authorized services

Page 16: AMI Threats Intrusion detection requirements  deployment recommendations

INFORMATION REQUIRED

Page 17: AMI Threats Intrusion detection requirements  deployment recommendations

PAPER DESCRIPTION

Survey Various Threats

Identify Common Attack Techniques

Decompose the data to form a Attack Tree

Identify the required information which would detech the

attacks

Model an IDS

Page 18: AMI Threats Intrusion detection requirements  deployment recommendations

IDS MODELS Centralized IDS Model

Utility Company IDS DCU

Page 19: AMI Threats Intrusion detection requirements  deployment recommendations

CENTRALIZED IDS Can detect attacks against Utility

network But, will miss attacks against smart

meters

Page 20: AMI Threats Intrusion detection requirements  deployment recommendations

EMBEDDED IDS

DCU

Meter + IDS

Meter + IDS

Meter

Meter

MeterMeter

+IDS

Page 21: AMI Threats Intrusion detection requirements  deployment recommendations

EMBEDDED IDS Will have access to meter specific

information But., Attacks on DCU cannot be detected Functioning both as a meter and IDS can

be resource intensive Keys of all other meters have to be

stored in Meter + IDS devices to inspect data

Not a good idea to store some one’s decryption key on some one else’s meter

Page 22: AMI Threats Intrusion detection requirements  deployment recommendations

DEDICATED IDS SENSORS

DCU

Meter IDS

Meter

Meter

MeterIDS

Page 23: AMI Threats Intrusion detection requirements  deployment recommendations

DEDICATED IDS SENSORS More processing power Less number of IDS sensors required So less number of places where keys are

stored But still, Attacks on DCU are not

detected

Page 24: AMI Threats Intrusion detection requirements  deployment recommendations

HYBRID SENSORS

DCU

Meter IDS

Meter

Meter

MeterIDS

Utility Company

IDS

Page 25: AMI Threats Intrusion detection requirements  deployment recommendations

HYBRID SENSORS Either Centralized + Embedded or

Centralized + Dedicated sensors Can detect both attacks at both (DCS

and NAN) ends

Page 26: AMI Threats Intrusion detection requirements  deployment recommendations

ANYTHING ELSE? According to the architecure discussed

in this paper, DCU is the device which is more likely to have a Public IP address

Smart meter vendors or third parties may soon start integrating 802.11 or GSM/3G into smart meters

But, why?

Page 27: AMI Threats Intrusion detection requirements  deployment recommendations

HOME PANEL

Page 28: AMI Threats Intrusion detection requirements  deployment recommendations

SO WHAT? Banner Grabbing! SHODAN – Exponse Online Devices Ipv4 computer search engine Webcams, Routers, Power Plants,

iPhones, Wind Turbines, Refrigerators, VoIP Phones

Page 29: AMI Threats Intrusion detection requirements  deployment recommendations

SCHNEIDER PLC GATEWAY

Page 30: AMI Threats Intrusion detection requirements  deployment recommendations

SIEMENS SIMATIC HMI

Page 31: AMI Threats Intrusion detection requirements  deployment recommendations

IPV6 INDEXING

Page 32: AMI Threats Intrusion detection requirements  deployment recommendations

QUESTIONS?