1 / 15

Vulnerability Test Suite Visualization

This project aims to visualize the results of a VoIP vulnerability test suite to provide reliable data for Industry Canada's approval of the technology. The current tool's data format is unacceptable, and a proposed solution involves using TreeMaps to differentiate test results and afford customization.

emunoz
Download Presentation

Vulnerability Test Suite Visualization

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. Vulnerability Test Suite Visualization Project UpdatebyMohammed AlamChristian Chita

  2. Project Overview • What: • visualize the results of a VoIP vulnerability test suite • Why: • VoIP is about to become a major player in North-American communications • Industry Canada needs reliable results before approving the technology for commercial use Shahed and Christian's

  3. Why current tool is unacceptable: • Data set looks like this: Root $Suite $SuiteId H248 $SuiteOverviewPart $Begin_SuiteStructure $SuiteId H248 $StandardsRef /* ITU-T Recommendation H.248.1 (05/2002): "Gateway control protocol: Version 2" */ $PICSref /* ETSI DTS/MTS-0096-1 */ $PIXITref /* ETSI DTS/MTS-0096-3 */ $TestMethods /* Remote test method */ $Comment /* */ $Structure&Objectives $Structure&Objective $TestGroupRef H248/MG/ $SelectExprId TCS_MG $TestGroupRef H248/MG/SU/BV/ $SelectExprId $Objective /* */ $End_Structure&Objective $Structure&Objective $TestGroupRef H248/MG/AC/BV/ $TestCaseId H248_MG_AC_BV_02 $SelectExprId $Description /* Audit of a single Termination in a Context */ $End_CaseIndex $CaseIndex $TestGroupRef H248/MG/AC/BV/ $TestCaseId H248_MG_AC_BV_03 $SelectExprId $Description /* Audit of all matching Child 3rd level Test Case Description Test Case ID Child 1st level Shahed and Christian's

  4. Root Test Case with Verdict What does “NONE” mean? Test Case Run Details Why current tool is unacceptable: • Current tool looks like this: Shahed and Christian's

  5. Add Test Case Run Details Here Root with 1st level children Root with 2nd level children Test Case ID’s Why current tool is unacceptable: • Jtree constructed with Test Suite data: Shahed and Christian's

  6. Proposed Solution: • Use TreeMaps • Why: • Take advantage of the nested structure of the groups • Use color to differentiate between Pass/Fail/Inconclusive test results • Employ Direct Manipulation to afford information content customizing Shahed and Christian's

  7. 1st level Child 1st level Child Root 3rd level Child Test Case Info & Verdict pops up on mouse-over 2nd level Child Test Case Proposed Solution: Shahed and Christian's

  8. Choice Classic/Squarified Cushion and Vary its Parameters Vary Border Size Proposed Solution: Shahed and Christian's

  9. pointerToParent pointerToChildren What is harder than expected: • Code for treemaps comes from sourceforge.net • Source provided, but need to build a tree structure out of one’s data • A node in the tree must look like this: Updater == a Status == b Size == c Name == d getStatus() getName() … Shahed and Christian's

  10. Tree Structure ttcn2 Input File ttcn3 Input File Input File ttcn Parser What is harder than expected: Shahed and Christian's

  11. 12 test cases 12 test cases Changes of Direction: • Promised: • Vary container size based on number of failed test cases • Why would this not work? Shahed and Christian's

  12. Today Where are we? • Promised milestones: Shahed and Christian's

  13. Today Where are we? • Delivered milestones: Shahed and Christian's

  14. Tree Structure ttcn2 Input File ttcn3 Input File Input File ttcn Parser What We Would Like To Add: • Skip the ttcn file writing step: Shahed and Christian's

  15. Tree Structure Input File Shell running the Test Suite What We Would Like To Add: • Skip the ttcn file writing step: Shahed and Christian's

More Related