50
DECLARATION of MAL(WAR)E The good, the bad, and the ugly

Declaration of malWARe

Embed Size (px)

DESCRIPTION

This presentation will take a high level look at the malware life cycle and the role that both hackers and IT professionals play in it. It should be interesting to IT professionals as well as individuals interested in learning more about the general approach used by hackers to gain unauthorized access to systems, applications, and sensitive data. More security blogs by the authors can be found @ https://www.netspi.com/blog/

Citation preview

Page 1: Declaration of malWARe

DECLARATION of MAL(WAR)E The good, the bad, and the ugly

Page 2: Declaration of malWARe

Who are we?

IT Security Consultants @ NetSPI

We help organizations:

• Identify vulnerabilities

• Determine impact

• Develop remediation plans

• Reduce risk

Page 3: Declaration of malWARe

• What is malware?

• Who creates malware?

• Why do they create malware?

• What skill level is required?

• The malware lifecycle

‒The “good” guy’s role

‒The “bad” guy’s role

• The “ugly” truth

Presentation Overview?

Page 4: Declaration of malWARe

What is Malware?

Page 5: Declaration of malWARe

Wikipedia definition:

…“software used or created by attackers to disrupt computer operation, gather sensitive information, or gain access to private computer systems”…

Our definition:

…“software created to do bad

things and is generally a pain in the butt”…

What is Malware?

Page 6: Declaration of malWARe

Types of Malware

• Remote Exploits

• Local Exploits

• Trojans

• Backdoors

• Rootkits

• Viruses

• Worms

Page 7: Declaration of malWARe

Malware Kit

Page 8: Declaration of malWARe

Who would do such a thing?

Page 9: Declaration of malWARe

Who is Creating Malware?

• Organized crime

• Governments

• Political activist

“hacktivists”

• Evil developers

• Bored teenagers

• You?

Page 10: Declaration of malWARe

Why would they do that?

Page 11: Declaration of malWARe

Why are they Creating Malware?

• Sell, sell, sell

• Steal money

• Steal information

• Strategic position

• Denial of Service

• Political gain

• Hacking as a hobby

• Internal employees

. . .

. .

. . .

.

Page 12: Declaration of malWARe

Who’s got the skills?

Page 13: Declaration of malWARe

What skill level is required?

• Malware Developers = Programmers ‒ More advanced programming skillset ‒ Create custom malware

• Less likely to be noticed • Personal use or sold to specific group

‒ Commoditized malware kits • More likely to be noticed • Free and commercial

• Malware Kit Users ‒ Don’t require advanced skillset ‒ Much more likely to cause damage by mistake

Page 14: Declaration of malWARe

The Malware Lifecycle

Page 15: Declaration of malWARe

The Malware Lifecycle

Malware Development

Malware Deployment

Malware Detection

Malware Correction

Malware Protection

Bad Guys

Good Guys

Page 16: Declaration of malWARe

Developers! Developers! Developers!

Page 17: Declaration of malWARe

Malware Development

• Professional Malware Development ‒ Often work like software companies ‒ Often produce very secure malware

• Create different types of malware ‒ Remote exploits ‒ Local exploits ‒ Backdoors, “bots”, and/or rootkits ‒ Worms or viruses ‒ Command and control ‒ Update functions

Page 18: Declaration of malWARe

Deploy! Deploy! Deploy!

Page 19: Declaration of malWARe

Malware Deployment

69% Of all breaches incorporate malware

As reported in the Verizon Business – 2012 Data Breach Investigations Report

Available at www.verizonenterprise.com

Page 20: Declaration of malWARe

Malware Deployment

79% Of all breaches were targets of opportunity

As reported in the Verizon Business – 2012 Data Breach Investigations Report

Available at www.verizonenterprise.com

Page 21: Declaration of malWARe

Malware Deployment

• Malware is often deployed via: ‒ Social engineering – email, phone, physical ‒ Default passwords on management applications ‒ Web application issues ‒ “Water holing” web applications

• Web Browser Issues etc

Email

Users

Apps

Pass Malware Package

Page 22: Declaration of malWARe

Detect! Correct! Protect!

Page 23: Declaration of malWARe

“…the median number of days advanced attackers are on the network before being detected is…”

416

Detecting Malware?

As report by Mandiant in their Annual Threat Report: M-Trends™ 2012

Page 24: Declaration of malWARe

94% Of organizations learn they

are victims of targeted

attacks from an

external entity

Detecting Malware?

As report by Mandiant in their Annual Threat Report: M-Trends™ 2012

Page 25: Declaration of malWARe

Detecting Malware!

• Where threats being detected: ‒ Networks ‒ Servers ‒ Workstations ‒ Applications / Databases ‒ People

• How are threats being detected: ‒ Behavioral / Anomaly based analysis ‒ Signature based analysis ‒ SIEM / Statistics based analysis ‒ Canaries / Honey pots

! Detect

Page 26: Declaration of malWARe

Detecting Malware!

• Challenges: ‒ Identify signatures related to

• undocumented malware • encrypted traffic

‒Keeping up with the amount of malware being released ‒Creating dependable behavioral based profiles ‒Creating useful statistical rules ‒ Identifying malware in memory

! Detect

Page 27: Declaration of malWARe

Detect! Correct! Protect!

Page 28: Declaration of malWARe

Correcting Affected Assets!

• Where does correction occur: ‒ Networks ‒ Servers ‒ Workstations ‒ Applications / Databases ‒ People

• How does correction occur: ‒ Incident response ‒ Patch systems and applications ‒ Code applications securely ‒ Securely configure

• Firewalls • Servers • Applications • User accounts • Training

X Correct

Page 29: Declaration of malWARe

Correcting Affected Assets!

• Challenges: ‒Creating patches for exploits before

they are widely used ‒Patching 3rd party software ‒Creating and managing secure code ‒Legacy and unsupported applications ‒Vendor contracts ‒Providing adequate training

X Correct

Page 30: Declaration of malWARe

Detect! Correct! Protect!

Page 31: Declaration of malWARe

Protecting Assets!

• Where are assets protected: ‒ Networks ‒ Servers ‒ Workstations ‒ Applications / Databases ‒ People

• How are assets being protected:

‒ Build/manage secure configurations ‒ Build/manage secure applications ‒ Network Access Control &

Intrusion Prevention Systems ‒ Proactive exploit development ‒ Proactive vulnerability identification ‒ Development of signatures ‒ 3rd Party Risk assessments

P Protect

Page 32: Declaration of malWARe

Protecting Assets!

• Challenges: ‒Security vs. usability ‒Asset inventory ‒Managing secure configurations ‒Communication/risk related to

partners, contractors, and vendors ‒Cost / Time / Skills ‒Education and training

P Protect

Page 33: Declaration of malWARe

Putting it All Together

Page 34: Declaration of malWARe

The Malware Deployment Cycle

Page 35: Declaration of malWARe

The Malware Deployment Cycle

Example

Time

Page 36: Declaration of malWARe

Simplified Network Diagram

Page 37: Declaration of malWARe

Gain Access via Exploit

Page 38: Declaration of malWARe

Escalate Privileges via Exploit

Page 39: Declaration of malWARe

Install Backdoor or Bot

Page 40: Declaration of malWARe

Propagate via Worm or Virus

Page 41: Declaration of malWARe

Command and Control: Phone Home

Page 42: Declaration of malWARe

Command and Control: Get Orders

Page 43: Declaration of malWARe

Good Guys Detect

Page 44: Declaration of malWARe

Good Guys Correct

Page 45: Declaration of malWARe

Good Guys Protect

Page 46: Declaration of malWARe

The Ugly

Truth

Page 47: Declaration of malWARe

The Ugly Truth: Bad Guys

Bad guys are creating Malware that is:

• Not going away

• Getting more advanced

• Getting harder to detect

• Getting easier to use

• Getting used by more people

Page 48: Declaration of malWARe

The Ugly Truth: Good Guys

Good guys need to: • Continue to fight the good fight! • Continue to develop new methods of detection,

correction, and prevention • Develop better security policies that make attacks:

• Harder to execute • Easier to detect • Easier to respond to and contain

• Focus on proactive vulnerability identification • Get rid of unnecessary sensitive data • Encrypt remaining sensitive data • Educate more users more often That can start with you…

Page 49: Declaration of malWARe

What’s Next?

What can I do?

• Don’t visit sketchy web sites

• Don’t open mail from unknown senders

• Review links before clicking them in emails

• Patch your systems and software

• Validate website before providing sensitive information

Click the “little lock” in your browser

• Don’t create and/or use malware ...

…unless it’s for the good guys

Page 50: Declaration of malWARe

Questions?

Questions?

Comments?

Quarrels?