SLIDE 1
1
Agenda
➔ Scenario: where are we? ➔ System design ➔ Architecture ➔ Implementation ➔ Demo ➔ What's next?
dradis Dradis Daniel Martn Gmez etd september '07 1 Agenda - - PowerPoint PPT Presentation
dradis Dradis Daniel Martn Gmez etd september '07 1 Agenda - - PowerPoint PPT Presentation
dradis Dradis Daniel Martn Gmez etd september '07 1 Agenda Scenario: where are we? System design Architecture Implementation Demo What's next? scenario: where are we? Penetration testing is about information
SLIDE 2
SLIDE 3
3
scenario: where are we?
Repor2rator
➔ Penetration testing is about information
Information Discovery
✔ port scan ✔ vuln. scan ✔ web app scan ✔ ...
SEMS Exploiting
✔ metasploit ✔ milw0rm ✔ ... ✔ reporterator ✔ word ✔ pdf tools ✔ ...
Reporti ng
SLIDE 4
4
scenario: where are we?
➔ Penetration testing is about information ➔ And what about information sharing?
✔ Each tester writes a “notes” file ✔ Some testers add the stuff straight to reporterator
Problems with this approach:
✔ Exploiting oportunities may be lost ✔ Overlapping ✔ Lack of standarization in the “notes” ✔ Synchronization problems when using reporterator
SLIDE 5
5
scenario: where are we?
➔ Penetration testing is about information ➔ And what about information sharing?
✔ Each tester writes a “notes” file ✔ Some testers add the stuff straight to reporterator
Problems with this approach:
✔ Exploiting oportunities may be lost ✔ Overlapping while testing ✔ Lack of standarization in the “notes” ✔ Synchronization problems when using reporterator
Does this sound anywhere near Quality or Efficiency?
SLIDE 6
6
scenario: where are we?
What is DRADIS?
<
SLIDE 7
Agenda
➔ Scenario: where are we? ➔ System design
SLIDE 8
8
system design
➔ Goals and chalenges
✔ create a system to effectively share information
SLIDE 9
9
system design
➔ Goals and chalenges
✔ create a system to effectively share information ✔ easy to use, easy to be adopted
SLIDE 10
1
system design
➔ Goals and chalenges
✔ create a system to effectively share information ✔ easy to use, easy to be adopted ✔ flexibility => growth ; good design
SLIDE 11
1 1
system design
➔ Goals and chalenges
- create a system to effectively share information
- easy to use, easy to be adopted
- flexibility => growth ; good design
✔ small and portable, so it can be used on site
SLIDE 12
1 2
system design
- Goals and chalenges
- create a system to effectively share information
- easy to use, easy to be adopted
- flexibility => growth ; good design
- small and portable, so it can be used on site
➔ Benefits
➔ information is organized
SLIDE 13
1 3
system design
- Goals and chalenges
- create a system to effectively share information
- easy to use, easy to be adopted
- flexibility => growth ; good design
- small and portable, so it can be used on site
➔ Benefits
➔ information is organized ➔ saves time: while testing and while reporting
SLIDE 14
1 4
system design
- Goals and chalenges
- create a system to effectively share information
- easy to use, easy to be adopted
- flexibility => growth ; good design
- small and portable, so it can be used on site
➔ Benefits
➔ information is organized ➔ saves time: while testing and while reporting ➔ effective knowledge sharing
SLIDE 15
1 5
system design
➔ Goals and chalenges
✔ create a system to effectively share information ✔ easy to use, easy to be adopted ✔ not too restrictive ✔ flexibility => growth ; good design ✔ small and portable, so it can be used on site
➔ Benefits
➔ information is organized ➔ saves time: while testing and while reporting ➔ effective knowledge sharing ➔ it is also good for one man testing
SLIDE 16
Agenda
➔ Scenario: where are we? ➔ System design ➔ Architecture
SLIDE 17
1 7
architecture
➔ Client / Server architecture ➔ Coded in Ruby ➔ Multiple interfaces ➔ Different user profiles
DRADIS
SLIDE 18
1 8
architecture
Database REST Web
SLIDE 19
Agenda
➔ Scenario: where are we? ➔ System design ➔ Architecture ➔ Implementation
SLIDE 20
Agenda
➔ Scenario: where are we? ➔ System design ➔ Architecture ➔ Implementation ➔ Demo
SLIDE 21
Agenda
➔ Scenario: where are we? ➔ System design ➔ Architecture ➔ Implementation ➔ Demo ➔ What's next?
SLIDE 22
2 2
what's next?
➔ Give it a try! ➔ Feature requests ➔ Improve it yourself ➔ It will be released under GPL ➔ Hopefully on sourceforge
<
DRADIS
SLIDE 23
2 3