multi-player metasploit: tag team pen testing and reporting

19
Multiplayer Metasploit Tag-Team Pen Testing and Reporting Ryan Linn Defcon 18

Upload: sussurro

Post on 29-Jan-2018

1.460 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

Multiplayer MetasploitTag-Team Pen Testing and Reporting

Ryan LinnDefcon 18

Page 2: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

Outline

• Description of Problem

• Discussion of current solutions

• Overview of XMLRPC database integration

• Discussion of types of objects

• Demos

Page 3: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

What’s the problem?

• Pen testing/security audit teams need to share information

• How do you plan further action?

• What about deltas from previous tests?

• No easy way to automate reporting

Page 4: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

Analysis of current solutions

• Dradis - best alternative, imports data great, but hard to further actions, no integration with other tools

• Leo - geared toward one person and logging/reporting only

• Wiki - multi-user but arbitrary organization, hard to convert to further action or reporting

Page 5: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

overview of solution

• Metasploit is readily available

• Extend XMLRPC to facilitate DB transactions

• XMLRPC extension allows central logging

• All information is actionable

• Data can be added real time

Page 6: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

Types of Objects

• workspaces - separate spaces for data

• hosts • services

• vulns

• notes - general purpose data storage

• events - log of commands executed• loots - phat loots lives here

• clients - web clients

• users - users + credentials

Page 7: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

Workspaces

• Values:

• name

• created_at

• updated_at

• boundary

• description

Page 8: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

Hosts

• created_at• updated_at• address• address6• mac• comm• name• state

• os_name• os_flavor• os_sp• os_lang• arch• purpose• info• comments

Page 9: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

Services

• host

• port

• proto

• state

• name

• info

Page 10: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

Vulns

• host

• service

• name

• info

Page 11: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

Notes

• ntype

• service

• host

• critical

• seen

• data

Page 12: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

Events

• host

• name

• seen

• critical

• username

• info

Page 13: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

loots

• host• service

• ltype• path• data

• content_type• name• info

Page 14: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

Clients

• host

• ua_string

• ua_name

• ua_ver

Page 15: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

Users

• username

• crypted_password• password_salt

• persistance_token• fullname

• email• phone

• company• prefs

Page 16: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

Demos

• Service Startup

• Launching Nmap with Nsploit

• Storing BeEF data in Metasploit

• External report generation

• Diffing workspaces

Page 17: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

Thanks

• Defcon staff and attendees for a great conference

• Heather Pilkington, Scott Hilbert, Jonathan Cran, HD Moore, Egypt, anyone else I’ve forgotten

• Fyodor, Wade Alcorn for Nmap and BeEF

Page 18: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

Contact Information

• IRC: sussurro

• Twitter: @sussurro

• Blog: blog.happypacket.net

Page 19: Multi-Player Metasploit: Tag Team Pen Testing and Reporting

Questions?