Network Security Lab

My Dream Network Security Lab

1. What a Network Security Lab is:

A Network Security Laboratory is an environment in which a computer-specialist controls a large number of variables in an effort to test system networks. Meaning creating a mock network in an effort to find vulnerabilities or weaknesses in the system which would allow an attack, or perhaps an unsuspecting child to get in to your mainframe and be asked “Do you want to play a game? (reference to the movie “Wargames”).

2. Why a technician would need a network security lab:

A good lab would be used to test the network in a secluded type of environment to avoid the destruction of an operating network. Any vulnerability which causes a catastrophic event could potentially cost a billion-dollar system to shut down by some glitch that wasn’t found before the install. Imagine a computer glitch in a nuclear reactor system. In theory there would be a meltdown (China Syndrome- the movie). The technician that made this mistake will probably have a hard time procuring a job flipping burgers much less ever working on another network.

3. How the Network Security Lab should or would be used:

Let’s say that a software developer finds a glitch in their system. They send out a patch for this, which is techie lingo for a fix. The lab technician would set the patch in motion on the mock lab and ensure that the patch actually works. The technician is responsible for knowing his or her system as much as possible from the inside out. All equipment used has been worked with and if and when there is an event, the tech will know immediately if not sooner. When all parties concerned are totally sure the software won’t crash the “always-on function” of the network, it will be installed and watched carefully.

4. The build sheet for my ideal network security lab computer:

• Cooler Master Elite 342 – MATX, w/ 400W Power Supply

• Gigabyte GA-B85M-D3H-s1150, USB3.0 HDMI/DVI/VGA

• 2 - PC3-12800 4GB DDR3-1600 (Single Module) (Crucial Premium)

• 1 - Intel Core i5-4590 Processor – s1150, 3.3GHz, Quad Core, 6M Cache, HD 4600 Graphics

• 1 - LG 24X DVD±RW – SATA, Black, OEM (no Software)

• 1 - 12in Serial SATA Cable

• 1 - WD WD5003AZEX Black 500GB

• 1 - Samsung 850 EVO Series 250GB SSD – 2.5in, SATA

• 1 - SIIG 3.5” to Dual 2.5’ Drive Bay Adapter (for the SSD)

• 1 - 12in LP4 2x Latch SATA Splitter

• 2 - StarTech.co 9.25cm Ball Bearing Quiet (YA right) Computer Case Fan

These fans sound like jets taking off from O’Hara.

**I would have a few extra Serial SATA cables and power connectors for the connection of external drive if needed.

5. The ideal operating system that I would use:

My first choice would be Windows 7. I have this system on three machines and it is very reliable, and stable. I have very few fights with it. My second choice is Win XP. This system may be old and Microsoft unsupported, but it is on two of my machines and out shines the others hands down. If I have a problem with the system, I still have the original install disk, and a copy of the full updates which Microsoft put out just before they discontinued all support. So far the only problem I have encountered is when my friends at _ _ _ _ slip their grubby paws in and try to “help” me with the system. (this is not a typo – it is intentional). I have been able to “fix” the problem myself.

My third choice if I was rich, is Mac OS. The limited use I have had with the system, albeit somewhat frustrating at first was enjoyable, and given more practice with it, could be mastered.

6. List of dream equipment for my lab build:

• Computers

• The tools I already own

• Cat5 cables

• Maybe some Fiber-Optic if money allows

• Network-attached storage (NAS)

• Hubs? (thought these are not used anymore)

• Switches

• Routers

• Removable disk storage

• Internet connection

• Cisco equipment

• Firewalls

• Wireless access points (good ones)

• Keyboard, video, mouse (KVM) switches

• Industrial surge suppressors and power strips

• Uninterruptable power sources

7. My list of software to use:

• VMware Workstation

• VMware Player (perhaps)

• VMware Server

• VirtualBox

• Windows Server 2008 and 2012R

• Linux products such as

• Red Hat

• Debian

• Mandrake

• Ubuntu

• KNOPPIX

• Fedora Security Spin

• Kali

• For the Mac:

• VMware Fusion

• Parallels Desktop

• VM VirtualBox

• Damn Vulnerable Linux

• Wireshark

• Metasploit

• Password Cracker

• Nessus

• Aircrack

• John the Ripper

And the list goes on. A little research provides one with an abundance of tools which can be used.

Well, to close this blog out, it was fun doing it the first time. After bragging up my knowledge of Win 7, I tried to copy and paste my masterpiece into the blog page and ended deleting and losing the whole thing. Haven’t been this unset since I lost nine weeks of a book report for my ethics class. Had to rewrite the whole thing two weeks before it was due. So the moral to that story is save and save often. Computers are only as smart as the operator, which is another reason for having a really good network security laboratory, and a very good computer-specialist running it. Maybe someone like “Abbey Sciuto” on NCIS. Pauley Perrette actually studied criminology before discovering acting (just a little trivia). Anyway, thanks once again for stopping in. It was a pleasure and a real learning adventure for me…hope it was the same for you.