Security+ (SECPLUS v3) Pod - Quick Reference Page


This quick reference page provides a summary of the specifications of the Security+ v3 pod.

Topology Supports... Documentation
Security+ v3 Pod
SECPLUS v3 		Security+ v3 NETLAB+ Security+ v3 Pod Install and Configuration Guide

You may request virtual machine templates for the Security+ v3 pod from CSSIA.

 

Lab Topology

SECURITY+

Virtual Machines - Storage Requirements

Details of the storage requirements for each of the virtual machines in the Security+ v3 Pod are provided in the table below. The Virtual Machine Deployment Names are provided as a suggested naming convention. The Security+ v3 course will consume 74.1 GB of storage per each master pod instance. Some fluctuation in the numbers may occur.

Virtual Machine Virtual Machine Deployment Name OVF/OVA Initial Master Pod
(thin provisioning)
DVL NDG_SecPlus3_Master.DVL 2.6 GB 7.2 GB
Kali NDG_SecPlus3_Master.Kali 4.6 GB 11.7 GB
pfSense NDG_SecPlus3_Master.pfSense 285 MB 730 MB
SecOnion NDG_SecPlus3_Master.SecOnion 5.6 GB 16.1 GB
Ubuntu NDG_SecPlus3_Master.Ubuntu 1.7 GB 4.8 GB
Win12R2 NDG_SecPlus3_Master.Win12R2 8.2 GB 15.6 GB
Win16 NDG_SecPlus3_Master.Win16 10 GB 18 GB
Total   33 GB 74.1 GB
 

Virtual Machine Templates

The Center for Systems Security and Information Assurance (CSSIA) provides virtual machine templates to install on the pod.

To request access to the preconfigured virtual machine templates from CSSIA:

  1. Go to the CSSIA Resources page: https://www.cssia.org/cssiaresources/
  2. Select CSSIA VM Image Sharing Agreement.
  3. Complete and submit your access request by following the instructions on the request form.
  4. CSSIA will provide, via email, password-protected download links. Access to the download links is provided only to customers who are current with their NETLAB+ support contract and are participants in the appropriate partner programs (i.e., Cisco Networking Academy, VMware IT Academy, Red Hat Academy, and/or Palo Alto Networks Cybersecurity Academy).
  5. Once all virtual machines have been downloaded, they can be deployed following the steps in the appropriate pod installation guide. Each virtual machine is deployed individually.