This quick reference page provides a summary of the specifications of this topology. For a complete reference including installation details, please refer to the CyberOps Associate Pod Planning and Installation Guide

Topology Supports Documentation

CyberOps Associate v1 Planning and Installation Guide

You may request virtual machine templates for the CyberOps Associate Pod from CSSIA.


Lab Topology


Virtual Machines

The OS and deployment names of the virtual machines in the CyberOps Associate Pod are provided in the table below.

VM Name VM OS Virtual Machine Deployment Name
Security Onion Linux Cisco_CyberOpsAssoc_Master.SecurityOnion
WinClient Windows Server 2016 Standard Cisco_CyberOpsAssoc_Master.WinClient
Workstation Linux Cisco_CyberOpsAssoc_Master.Workstation

Pod Resource Requirements

The CyberOps Associate Pod will consume consume 42.6 GB of storage per each master pod instance.

Details of the storage requirements for each of the lab virtual machines in the CyberOps Associate Pod are provided in the table below. Some fluctuation in the numbers may occur.

Virtual Machine OVF/OVA Initial Master Pod
(thin provisioning)
Security Onion 3.2 GB 8.1 GB
WinClient 12 GB 26.7 GB
Workstation 3.7 GB 7.8 GB
Total 18.9 42.6

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:
  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.