SNI – Server Name Indication

When a client (web browser) connects to vScope via HTTPS, a modern browser will attempt to use SNI during the handshake process. SNI tells the web server (vScope) which hostname the client is connecting to and allows the web server to present the correct certificate to the client. If the certificate contains the hostname or […]

Connecting to Nutanix Prism Central

Integrate vScope with Nutanix Prism Central to collect information about VMs, clusters, storage, and more. The information is automatically cross-referenced with other data sources such as SCCM, Windows/Linux OS, and Active Directory. Adding Nutanix Prism Central in Discovery Manager 7. Click Save8. Run a discovery. You can run a partial discovery by selecting the row […]

How vScope runs WMI scripts

vScope collects information from Windows operating systems using various WMI scripts, utilizing VBscript. The scripts can be run from the vScope server using plain WMI, or locally on the target machine using PowerShell via WinRM. Though we recommend using WinRM due to performance and security, you can configure vScope to use WMI in Discovery Manager […]

How to handle duplicate assets

vScope automatically identifies and merges assets across any datasource. Merging is based on numerous criterias eg. serial number, domain, and name. If you find multiple representations of an asset in vScope, you can handle this in different ways. 1. Confirm duplicates in the data source(s) Are you sure that it’s a duplicate? Sometimes, what’s considered […]

Clear disk space for vScope

Due to vScope keeping track of any historical changes in your IT environment, the disk usage of the vScope installation will increase the longer you run vScope. By default, vScope will prune historical data older than 60 months to handle this increasing disk size (See #2 below), meaning that the increase will subside after five […]

Creating a group or permission mapping from SSO

Using SSO, you can rely on external authentication methods in vScope. Once configured, you can use the external identity provider (IDP) to assign vScope users permissions and/or groups. If you have not yet configured SSO, please start by reading Setting up Azure Single Sign-On (SSO). Important notice Depending on what permissions you have configured in […]

Setting up Azure Single Sign-On (SSO)

Configuring Single Sign-On (SSO) to use Azure as an identity provider (IDP) to vScope allows you to use enhanced security features, eg. MFA (Multi-factor authentication). Azure can be used to handle authentication and/or permission settings for users in vScope. This helps you to centralize ACL and user management to Azure. This guide shows you how […]

vScope and Apache Log4j (CVE-2021-44228)

Summary vScope is not using Log4j2 vScope is not using JNDI or JMSAppender …and is not affected by neither CVE-2021-44228 nor CVE-2021-4104. Background A flaw was found in the Apache Log4j logging library in versions from 2.0.0 and before 2.15.0. It allows an attacker to execute arbitrary code by injecting attacker-controlled data into a logged […]

Customized Asset inventory

Notice: Customize inventory in vScope requires administrator priveliges By default, vScope inventories as many assets as possible from a data source. This way vScope will always reflect what’s in your data sources. However, sometimes you might want to customize what vScope inventories, eg. ignoring disabled computers or inactive user accounts. Discovery Manager in vScope includes […]

Windows Defender – Suspicious command launched from remote location

Background To inventory Windows operating systems, vScope uses WMI or WinRM (depending on your preferences). This is called a Discovery. Both WMI and WinRM run scripts from the vScope server to fetch information from a remote (target) server. This can cause antiviruses to trigger alerts related to remote scripting. Windows Defender has a default incident, […]