Security+ (SECPLUS v4) Pod - Quick Reference Page


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

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

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

 

Lab Topology

SECURITY+

Virtual Machines - Storage Requirements

Details of the storage requirements for each of the virtual machines in the Security+ v4 Pod are provided in the table below. The Virtual Machine Deployment Names are provided as a suggested naming convention. The Security+ v4 course will consume 109.5 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)
Kali NDG_SecPlusv4_Master.Kali 11 GB 28.9 GB
pfSense NDG_SecPlusv4_Master.pfSense 553.7 MB 872.5 MB
SecOnion NDG_SecPlusv4_Master.SecOnion 22.5 GB 38.9 GB
UbuntuSRV NDG_SecPlusv4_Master.UbuntuSRV 8.9 GB 19.6 GB
WinOS NDG_SecPlusv4_Master.WinOS 13.7 GB 21.2 GB
Total   56.7 GB 109.5 GB
 

Virtual Machine Templates

The virtual machines are made available as Open Virtualization Format (OVF) or Open Virtualization Archive (OVA) files. These files are available for download from EPNC (Education Pathway National Center).

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

  1. Go to the CSSIA Resources page: https://www.caeepnc.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. EPNC 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.