Lab Management

Managing existing labs deployed within your Snap Labs account.

Lab and System States

Your deployed labs can be in any number of states. When you first launch a lab environment, your lab will appear in a Launching state. From here, Snap Labs allows you to easily Start, Stop, Snapshot, Revert, and Template a lab and it's individual systems.

Launching

  • The infrastructure for your lab is deploying
  • You cannot manage or otherwise interact with the lab in this state

Starting

  • At least one system in the lab, or the individual system, is powering on
  • You cannot manage individual systems while they are Starting

Running

  • At least one system in your lab environment is fully powered on
  • You can manage lab/system settings and snapshots in this state
  • You can Stop the lab/system from this state

Stopping

  • The lab or individual system is powering off
  • You cannot manage individual systems while they are Stopping

Stopped

  • The lab or system is deployed but powered off
  • You can manage lab/system settings and snapshots in this state
  • You can Start the lab/system from this state

Snapshotting

  • The system or lab is saving it's state with a Snapshot of the disk(s)
  • You cannot manage individual systems while they are Snapshotting

Reverting

  • The system or lab is restoring itself to a previously saved state
  • You cannot manage the individual systems while they are Reverting

Power Functions

There are three important functions which control the power state of your labs and individual systems: Start, Stop, and Reboot.

Start

  • Starting the lab will power on every individual system in the environment
  • Starting an individual system will only power on that system, but your lab will be in the Running state

Stop

  • Stopping the lab will power off every individual system in the environment
  • Stopping an individual system will only power off that system, and your lab will remain in a Running state

Reboot

  • Rebooting the lab will power cycle every individual system in the environment
  • Rebooting an individual system will only power cycle that system
  • Rebooting does not affect the state of either the lab or it's individual systems
  • Systems which are rebooting will display as Running in the lab dashboard

Accessing your Labs

Snap Labs provides convenient access to the systems running in your lab environments. Users can connect directly through the browser with Console Sessions, or they can connect their own systems with a VPN connection.

Console Sessions

You can access lab systems directly through your browser by clicking the "console" button on any system visible in the dashboard. This grants administrative/root access via RDP, VNC, or SSH depending on the operating system. You can also run multiple concurrent console sessions to work in multiple lab systems simultaneously.

πŸ“˜

Share Files via Console Sessions

Users can easily copy/paste and share files between lab systems and their host devices through Console Sessions.

To upload files - press the CTRL-Shift-ALT key combination and select the Share Drive, then Upload Files.

To download files from Windows systems, drag and drop your desired files to the Download folder in the Guacamole drive. To download on Linux, press the CTRL-Shift-ALT key combination, select the Share Drive, then double click on your desired file.

Lab Apps

Users can access web applications running within the lab environment directly through their browser via Lab Apps. These are configured, managed, and accessed via the Apps tab within deployed lab environments.

Apps currently only support web based applications. They can also support Basic Authentication for browsing sessions.

VPN Connections

Every Snap Labs user can manage up to 4 VPN configuration files for each lab environment they have access to. These configuration files can provide two separate types of access: Admin or Attacker. You also have the option to create configuration files designed for Windows or Linux/MacOS VPN clients.

🚧

Sharing VPN Configs

VPN Configurations created for your lab environment only support one concurrent connection. This means if you share your configuration with another user, only one of you will be able to connect at a time.

To invite others to your lab environment, see User Management.

Any VPN client that is compatible with OpenVPN configuration files works, but we suggest using the OpenVPN Client.

Admin VPN Configs

  • These configurations are intended to provide access to every system in your lab environment
  • They allow you to connect even segmented areas of the lab network in our featured templates

Attacker VPN Configs

  • These configurations are intended to provide a limited or external view of the lab network.
  • In our featured templates, connecting with this type of configuration will provide equivalent access to the Kali (Attacker) system

Managing VPN Configs

  • To create configurations, navigate to the VPN Configs tab for your lab and provide a Config Name, Access Type, and Operating System Type. Then Create your certificate
  • Once a configuration is created, you may Download or Revoke the configuration
  • Revoking a configuration file will remove access for that configuration, and disconnect any active sessions

What’s Next