Abstract

1. Network Specification and Report System for ISEAGE (May05-25) Abstract Project Requirements • Design Objective • Must be easy to use • Must allow mapping of existing networks • Allow easy tracking of simulation output • Functional Requirements • A graphical user interface to configure a network • Mapping of existing networks • Viewing of ISEAGE simulation output • Design Constraints • Software must provide fast network configurations, regardless of scale • An individual network can be configured by only one user • The software must run on Microsoft Windows • Measurable Milestones • Project Plan • Design Report • Final Implementation and Report Recent terrorist activities have heightened the need for protecting critical infrastructures. Web-based systems like the highly-interconnected power grids used in transportation, water, and bureaucracy management systems are especially vulnerable since there exists no satisfactory means of evaluating their security risks. To meet this need, ISEAGE is creating a virtual internet to enable the research, design, and testing of cyber defense mechanisms. One component of the ISEAGE system, and the end product of this project, is the Network Specification and Report System. The specification system will allow the user to create a virtual computer network through a GUI tool, while the report system will enable the user to evaluate an attack in pseudo-real time or post-simulation. With the integration of this component into ISEAGE, users will be able to create and evaluate custom networks configured on actual hardware and faced with real attacks, thus allowing for an accurate assessment of network security. Introduction Project Schedule • General Problem Statement • ISEAGE lacks ability to allow a user to specify custom computer networks • No functionality exists to allow the user to specify networks that represent physically existing networks or potential networks • ISEAGE needs the ability to allow the user to track the simulation • General Solution Approach • A graphical user interface will be created for configuration of computer networks • End product will be capable of being GIS-based to map physically existing networks into simulation or reflecting only topology • A logically formatted document will enable the tracking of network simulation • Operating Environment • The end product will function on Microsoft Windows operating systems • The end product may be compatible with other operating systems if the appropriate technology can be located • Intended Users • Groups desiring large-scale computer network simulation (e.g., Department of Homeland Security) • Groups desiring small-scale computer network simulation (e.g., business owners, graduate students) • Intended Uses • Design of computer networks operating in ISEAGE • Map physically existing networks into simulation • Provide simulation tracking in a logical and understandable manner • Assumptions • Software will allow configuration of only one network at a time • To configure a different computer network on one computer, user must open another copy of software • Limitations • The software must run in the Windows operating environment • The software must be able to easily configure computer networks with or without physical relationships • The software must be able to specify IPv4 networks which is currently the most used on the Internet • Expected End Product • A program to enable a user to specify and map an IPv4 network the size of Iowa or smaller • A program allowing simulation tracking through a logically formatted file Figure 2 Proposed Approach and Considerations • Proposed Approach • Discuss requirements with client • Design classes and modules • Implementation of classes and modules • Testing of all components • Testing of unified whole • Feedback forms for outside testers • Client testing of graphical user interface • Technologies Considered • Platforms: Windows, BSD, Linux, Mac Graphics Library: FOX, FLTK, wxWindows • Languages: C++, C#, Java • Testing Considerations • Unit testing and system testing • Graphical interface testing by client • and outside users Estimated Resources and Schedule Figure 1 Conclusion The objective of this assignment is to create an interface which allows a large variety of people to create a large variety of networks using the same tool, and to do so quickly and easily. This requires a well-structured design. Additionally, the client will give frequent feedback to determine the usability of the software starting in the initial design stage and especially in the later testing stages. The final interface will be a product of this goal and approach. Client Faculty Advisor Team Members Project Web Site ISU Information Assurance Center Dr. Douglas W. Jacobson dougj@iastate.edu David Rodgers (ComS/CprE) Lijin Varghese (CprE) Derek Light (CprE) Justin Magnini (CprE) http://seniord.ece.iastate.edu/may0525/