Skip to content

all the documentation that is specific to the lab network, infrastructure, etc.. (not documentation for lab rolls, but possibly for definitions)

Notifications You must be signed in to change notification settings

DrJZoidberg/lab-documentation

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

11 Commits
 
 
 
 
 
 
 
 

Repository files navigation

This repo will be for all the documentation we will need/have for the lab.

Lab

49th Logo

What is it?

The lab is a place of education that 49th utilizes to create a safe and educational environment for new people to the ethical hacking club the 49th Security Division at UNC Charlotte.

Why github?

We are going to be using github to store all the code we will be using for the infrastructure. This will allow people to contribute to the lab that want to in an opensource and educational fashion. The final say of if the information will get admitted or not will be up to a lab troll (definition link here). They are the keepers of the lab.

What will be on here?

We have great plans for the lab, and plan to use a lot of devops tools to manage and control everything in the lab. The reason why is because IaC is an auditable and reproducible way to control your infrastructure, so that way other people can understand what is happening in your infrastructure and easily (or at least easier) assume responsibility of it with full understanding of what is happening.

What devops tools will you use?

From the devops community we will we use a variety of tools:

  • terraform - used to control and manage the vCenter (vm) infrastructure
  • ansible - used to provision the vms infrastructure, this will be our configuration management tool.
  • vault - to manage password infrastructure for everything internal
  • packer - this will build the vms that we will control with the tools above
  • jenkins - will automate the packer builds so they stay up to date and other automation tasks
  • teamcity - this will ensure code sanity/checking to make sure nothing is badly configured in our IaC
  • kubernetes - to orchestrate vulnerable environments for students to learn in

What security/infrastructure tools will you use?

We will be using a whole host of security tools as well:

  • Palo Alto Firewall - used to maintain the over aching network of the lab
  • vCenter - used to host our vm infrastructure
  • Splunk - used to aggregate logs and monitor internal traffic
  • pfSense firewall - used to segment internal networks and simulate attack environments

Who can help/be involved?

This is github and everything is opensource so anyone can help out with this. The majority of this will be done by lab trolls and lab minions (link to definition), as they will be in charge of approval processes to all official lab repos.

About

all the documentation that is specific to the lab network, infrastructure, etc.. (not documentation for lab rolls, but possibly for definitions)

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published