Declaration of Mal(WAR)e


Published on

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Declaration of Mal(WAR)e

  1. 1. DECLARATION of MAL(WAR)EThe good, the bad, and the ugly
  2. 2. Who are we?IT Security Consultants @ NetSPIWe help organizations:• Identify vulnerabilities• Determine impact• Develop remediation plans• Reduce risk
  3. 3. • 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” truthPresentation Overview?
  4. 4. What is Malware?
  5. 5. Wikipedia definition:…“software used or created by attackers todisrupt computer operation, gathersensitive information, or gain access toprivate computer systems”…Our definition:…“software created to do badthings and is generally a pain in the butt”…What is Malware?
  6. 6. Types of Malware• Remote Exploits• Local Exploits• Trojans• Backdoors• Rootkits• Viruses• Worms
  7. 7. Malware Kit
  8. 8. Who would dosuch a thing?
  9. 9. Who is Creating Malware?• Organized crime• Governments• Political activist“hacktivists”• Evil developers• Bored teenagers• You?
  10. 10. Why wouldthey do that?
  11. 11. 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.........
  12. 12. Who’s got the skills?
  13. 13. 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 tocause damage by mistake
  14. 14. The Malware Lifecycle
  15. 15. The Malware LifecycleMalware DevelopmentMalware DeploymentMalware DetectionMalware CorrectionMalware ProtectionBadGuysGoodGuys
  16. 16. Developers!Developers!Developers!
  17. 17. 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
  18. 18. Deploy!Deploy!Deploy!
  19. 19. Malware Deployment69%Of all breaches incorporate malwareAs reported in the Verizon Business – 2012 Data Breach Investigations ReportAvailable at
  20. 20. Malware Deployment79%Of all breaches were targets of opportunityAs reported in the Verizon Business – 2012 Data Breach Investigations ReportAvailable at
  21. 21. 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 etcEmailUsersAppsPassMalwarePackage
  22. 22. Detect!Correct!Protect!
  23. 23. “…the median number of days advancedattackers are on the network beforebeing detected is…”416Detecting Malware?As report by Mandiant in their Annual Threat Report: M-Trends™ 2012
  24. 24. 94%Of organizations learn theyare victims of targetedattacks from anexternal entityDetecting Malware?As report by Mandiant in their Annual Threat Report: M-Trends™ 2012
  25. 25. 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
  26. 26. Detecting Malware!• Challenges:‒Identify signatures related to• undocumented malware• encrypted traffic‒Keeping up with the amountof malware being released‒Creating dependable behavioralbased profiles‒Creating useful statistical rules‒Identifying malware in memory!Detect
  27. 27. Detect!Correct!Protect!
  28. 28. 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• TrainingXCorrect
  29. 29. Correcting Affected Assets!• Challenges:‒Creating patches for exploits beforethey are widely used‒Patching 3rd party software‒Creating and managing secure code‒Legacy and unsupported applications‒Vendor contracts‒Providing adequate trainingXCorrect
  30. 30. Detect!Correct!Protect!
  31. 31. 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 assessmentsPProtect
  32. 32. Protecting Assets!• Challenges:‒Security vs. usability‒Asset inventory‒Managing secure configurations‒Communication/risk related topartners, contractors, and vendors‒Cost / Time / Skills‒Education and trainingPProtect
  33. 33. Putting it AllTogether
  34. 34. The Malware Deployment Cycle
  35. 35. The Malware Deployment CycleExampleTime
  36. 36. Simplified Network Diagram
  37. 37. Gain Access via Exploit
  38. 38. Escalate Privileges via Exploit
  39. 39. Install Backdoor or Bot
  40. 40. Propagate via Worm or Virus
  41. 41. Command and Control: Phone Home
  42. 42. Command and Control: Get Orders
  43. 43. Good Guys Detect
  44. 44. Good Guys Correct
  45. 45. Good Guys Protect
  46. 46. The UglyTruth
  47. 47. The Ugly Truth: Bad GuysBad 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
  48. 48. The Ugly Truth: Good GuysGood 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 oftenThat can start with you…
  49. 49. 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 sensitiveinformationClick the “little lock” in your browser• Don’t create and/or use malware ...…unless it’s for the good guys 
  50. 50. Questions?Questions?Comments?Quarrels?