1 / 22

May06-11: ISEAGE Attack Tool Repository and Player

May06-11: ISEAGE Attack Tool Repository and Player. Jeremy Brotherton, Timothy Hilby, Brett Mastbergen, Jasen Stoeker. Agenda. Problem introduction Basic solution architecture Technology considerations Detailed design. Project Introduction. Problem

kathy
Download Presentation

May06-11: ISEAGE Attack Tool Repository and Player

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. May06-11: ISEAGE Attack Tool Repository and Player Jeremy Brotherton, Timothy Hilby, Brett Mastbergen, Jasen Stoeker

  2. Agenda • Problem introduction • Basic solution architecture • Technology considerations • Detailed design

  3. Project Introduction • Problem • Growing dependency on computer technology • Auditing systems is complex and time consuming • Solution • Central repository of exploit code • Searchable through web interface • Launch attacks from web interface

  4. Design Objectives • Web based user interface • Searchable database of attack tools • Attack player • Attack download capability • Database update tools

  5. Basic Solution Architecture

  6. Database Technologies Considered • PostgreSQL • Oracle • SQL Server 2005 • MySQL

  7. SQL Server 2005 Pros • Best integration of any solution. • Most extensive tools. • Fast and scalable. • Large amount of prewritten functions and objects. • Interacts well with the Visual Studio IDE.

  8. SQL Server 2005 Cons • Microsoft licensing issues. • Future release date. • New release means additional likelihood of major bugs. • Database tied to Microsoft platforms.

  9. MySQL Pros • Large amount of online examples and a large online user community. • Current version mature and well tested. • Open source license will be easiest to work with. • Able to be used on most major platforms. • Relatively easy to learn.

  10. MySQL Cons • Not as much code comes with the database as with SQL Server 2005. • Not as well integrated with other products as SQL Server 2005 is with .Net products.

  11. Web Technologies • ASP .NET 2005 • PHP

  12. ASP .NET 2005 Pros • Extremely well integrated with SQL Server 2005. • Ability to drag and drop graphical web interface. • Large MSDN documentation library. • Very large amount of built in objects and functions. • Excellent IDE and graphical debugger.

  13. ASP .NET 2005 Cons • Microsoft licensing issues. • Future release date. • New release means additional likelihood of major bugs. • A server for ASP .NET would be tied to Microsoft platforms. • Already decided against SQL Server 2005.

  14. PHP Pros • Current version well tested. • Many online examples. • No licensing issues. • Cross platform. • Fast code execution • Easy to learn

  15. PHP Cons • Not as well integrated as ASP .NET. • No graphical debugger/IDE. • No ability to drag and drop interfaces.

  16. Final Technology Selections • MySQL • PHP • Apache

  17. Application Homepage

  18. Application Search Page

  19. Application Search Results

  20. Attack Launch Page

  21. Database Administration

  22. Questions Any questions or comments?

More Related