Sunteți pe pagina 1din 12

Constructing Virtual Laboratory for

Research and Education


(Progress Report --- Week 8)

Team members: Melissa Nichols and Nathan Torrez


Mentor: Dr. Anyi Liu
Outline
Timeline
List of Tasks
Key Terms
Schedule and Achievement of Week 8
Finishing experiment documentation
Optimizing test environment and web client
Experimenting with Volatility
The Plan of Week 9
References
Demonstration Video
Timeline
Week Six Write the module that can change
network topologies using OpenStack
API (Part 2)
Start working on the module that
can change the routing rules (Part 2)

Week Seven Continue working on the module


that can change the routing rules
(Part 2)
Draft the research paper

Week Eight Improve the performance and


efficiency of the virtual laboratory
Refine the user interface


Work on the poster
Continue work on research paper
We are here

Week Nine Conduct tests in virtual laboratory


environment
Revise research paper
Continue work on poster
If possible, work with VMI library
(libVMI)
Week Ten Finalize research paper
Finalize poster
Finalize tests and scripts
List of Tasks
Task Status Finding better open-source SSH client Complete (Week Four)
Getting familiarized with CloudLab, Complete (Week One + Week Two) Examining Python code in depth Complete (Week Four)
Amazon EC2, and SSH clients Running attack scenario on local Complete (Week Four)
Adding function that lists virtual Complete (Week Two) computers
machine images to confirm Creating virtual machine images for Complete (Week Five)
connection to TesterScript use with Attack Scenario
Downloading VM images from Complete (Week Two) Running attack scenario in the cloud Complete (Week Five)
CloudLab and running them locally Creating documentation for instructors In Progress (Week Five)
Creating better documentation on Complete (Week Two) and students to run Attack scenario
how to run TesterScript and Experimenting with libvmi tools In Progress (Week Five)
MasterScript Familizarizing ourselves with Snort, Bro, Complete( Week Five)
Writing documentation In Progress (Week Two) and nmap (Tools for detecting attacks)
Adding functionality that allows Complete (Week Three) Improving the performance and In Progress (Week Five)
creation of multiple virtual machine efficiency of the virtual laboratory
images at once using TesterScript Automating router interface recreation Found Alternative (Week Six)
Using multithreading to speed up Complete (Week Three) from XML
creation of virtual machine images Writing the module that can change In Progress (Week Six + Seven)
Uploading VM images from local Complete (Week Two + Three) network topologies
machine and using SSH to connect
to them in CloudLab Using a proxy to distribute IP addresses Complete (Week Seven + Eight)
Uploading an experiment from XML Complete, but still need to automate for Attack scenario
document creation of router interfaces (Week Writing the module that can change To be completed
Three) routing rules
Fixing XML Importation issues Complete(Week Four) Writing research paper To be completed
regarding router interfaces Creating the poster To be completed
Key Terms

Volatility an open-source tool written in Python


that offers many digital forensics applications,
including analyzing memory dumps. [1]
The Achievement of Week 8
Day 1: Day 4:
Writing experiment documentation
Writing experiment documentation Optimizing test environment and web
Optimizing test environment and web client
client Experimenting with Volatility

Day 2:
Writing experiment documentation
Optimizing test environment and web
client
Day 3:
Writing experiment documentation
Optimizing test environment and web
client
Days 1-4: Optimizing test environment
and writing experiment documentation
A web client is used to assign
students IP addresses for an
experiment
The web client stores the IP
addresses in a database and
ensures that no duplicate IPs are
assigned
The web client allows the student Sign-in Page for Web Client
to open an in-browser SSH terminal
to the Attack machine
We have been working to perfect
the web client and ensure that it
works as intended with every
experiment

Attack and Victim IPs assigned to a student


Days 1-4: Optimizing test environment and
writing experiment documentation (cont.)

We continued to write our experiment documentation


with instructions on how to create the experiment and
how to run exploits using the created environment

We plan to add more features to the exploit portion of


our experiment, including memory forensics and
Windows virtual machines
Day 4: Experimenting with Volatility

In order to use Volatility, we first


need a memory dump of a virtual
machine
We took a snapshot of our
Metasploitable virtual machine
while running one of our exploits
and acquired a memory dump
using VirtualBox
We will then use Volatility to
examine the list of ports on our
Linux machine to find the port
being used by the malicious exploit
We plan to run exploits on a
Windows machine and acquire the A list of profiles in Volatility that can be used
memory dumps from that as well to examine memory information on a
specific virtual machine
Plan For Week 9

Testing

Adding Volatility memory forensics portion to


experiment
Finishing experiment documentation
Continuingto optimize experiment for best
performance
References

[1] The Volatility Foundation - Open Source


Memory Forensics. (n.d.). Retrieved from
http://www.volatilityfoundation.org/
Demonstration Video

https://www.youtube.com/watch?v=9xm6UbrdELY

S-ar putea să vă placă și