Getting started

Overview

Deploy Cisco Cyber Vision in Microsoft Azure using a solution template available in the Azure Marketplace. When you deploy Cisco Cyber Vision using the Azure portal you can use an existing empty resource group and storage account (or create new ones). The solution template walks you through a set of configuration parameters that provide the initial setup of your Cisco Cyber Vision instance, allowing you to login to Cisco Cyber Vision web interface after first boot.

Prerequisites

  • An Azure account.

  • An SSH client (required to access the Cisco Cyber Vision Center console).

  • Communication path: Microsoft.Network/publicIPAddresses IPs for access to the Cisco Cyber Vision resources.

  • A Static IP (the default public IP may change after a reboot. This can cause an issue for sensors).

  • Minimum configuration to run and test the product are 4 vCPU and 16GB RAM.

  • SSD disks are mandatory.

Supported features

  • Center

  • Global Center

Limitations

Unsupported features or hardware include:

  • Dual interface Centers.

IP addresses

An IP address is a network identifier that

  • uniquely distinguishes each device in a network,

  • enables routing of data packets between devices, and

  • can be assigned dynamically or statically depending on network requirements.

IP address assignment in virtual machine environments

In virtual machine environments, dynamic IP addresses are often assigned by default and may change when a virtual machine (VM) reboots. Network administrators can configure static IP addresses during VM deployment. See Configure virtual machine settings. In the Azure portal, you can change the IP address assignment later by selecting the virtual machine IP address and choosing a different assignment method.

IPv6 support for Cyber Vision administration services

You can use both IPv4 and IPv6 protocols for administration services in Cyber Vision.

You can use IPv6 on center eth0 for all your administration-related access, such as:

  • Accessing the web UI.

  • Integrating with third-party solutions such as syslog, ISE configurations, and LDAP.

Consider these limitations:

  • License operations only work with direct transport; Transport Gateway and HTTP/HTTPS Proxy are not supported.

  • Sensor data collection uses only IPv4, whether performed on eth0 or eth1.