1. Overview This document outlines the integration of CyberSnap with VMware vSphere vCenter and NetApp storage to deliver automated virtual machine (VM) integrity testing and cyber threat scanning using immutable NetApp snapshots. This integration enhances cyber resilience by enabling isolated,
In this document we will describe the process of collecting logs when you are submitting the case to Cybersnap support. CyberSnap logs are divided into three different categories: Collecting Policy log CyberSnap Windows service log CyberSnap creates Windows service log
To avoid receiving emails when a Datastore is connected or disconnected by CyberSnap, you should add an additional filter in the current alarm definition. Once you modify the rule, it will ignore Datastore names that start with ‘CSI’, and no
Reconfiguring Disk Usage Alarm in vSphere To prevent data stores created by CyberSnap from triggering the disk usage alarm, you should disable the default disk usage rule at the vCenter level and instead create a custom rule using the same
For regular functionality, CyberSnap requires access to the NetApp to oversee processes within the NetApp environment during scanning and recovery. The most efficient approach involves creating a dedicated user account with administrative privileges. In cases where customers need to restrict account privileges,
For regular functionality, CyberSnap requires VMware vCenter access to oversee processes within the VMware environment during scanning and recovery. The most efficient approach involves creating a dedicated user account with administrative privileges. In cases where customers need to restrict account
To ensure the correct operation of CyberSnap, certain pre-requisites must be set up before installation. Hardware and Software CyberSnap Server – Windows 2019/2022 – One server with 16 GB Ram, 4 CPUs, disk size of 250 GB. – The latest
Issue Description Cyber policy cannot scan virtual machines stored on a datastore that contains a VMware snapshot. Symptoms Environment Cause The virtual machine snapshot attachment process is not supported in the current environment. Resolution To resolve this issue: Additional Notes
Issue Description When attempting to sandbox virtual machines while a scan is in progress from the same datastore, SnapMap incorrectly marks the scan results as bad for the recovered virtual machine. Once the virtual machine is reverted from the sandbox,
