Security: Video

Follow this article and find out how to store a snapshot of all cameras automatically from the Operator Client

The firewall configuration dialog is a fixed step in the setup process and will allow automatic configuration of all required firewall settings to run BVMS.

The purpose of this article is to provide step by step instructions on how to successfully import video and storage devices from a DIVAR IP Recording Appliance to a BVMS standalone installation while retaining all existing recorded video.

This article describes how to configure a generic Microsoft Windows Server (2012 R2, 2016 or 2019) based server to serve as an iSCSI target for a Bosch video surveillance environment. SCSI (Small Computer System Interface) is most commonly used for the communication between computers and peripheral devices, such as hard drives. iSCSI enables devices to use SCSI over a network interface, therefore it makes a lot of sense for cameras to use iSCSI to record video. The camera is a small computer that needs a (network) connection to a "hard drive" to store video footage. In other systems this job is performed by the network video recorder (NVR).

When working with previous versions of BVMS, remote connectivity was cumbersome due to the amount of port mapping that needed to be configured. BVMS 7.5 provides a new method of remote connectivity utilizing Secure Shell (SSH) Tunnelling. SSH Tunnelling constructs an encrypted tunnel established by an SSH protocol/socket connection. This encrypted tunnel can provide transport to both encrypted and un-encrypted traffic. The Bosch SSH implementation also utilizes Omni-Path protocol, which is a high performance low latency communications protocol developed by Intel. Key management The BVMS SSH service generates a private and public key when it is started for the first time. Both keys are saved in an encrypted file. When the BVMS SSH service restarts this file is detected and the private key is read.   Step-by-step guide   1.Configuration   A. Installation There is little to no configuration required for this feature to function. The SSH Service must be installed and running. If deploying a BVMS Pro system, insure the SSH Service is part of the installation process. Recording Appliances that ship with BVMS 7.5 should have the service pre-installed. Check your “Services”. If the service has not been installed, the install package can be run from the BVMS 7.5 downloadable install package. If working with a DIVAR IP Recording Appliance, the appliance “Installer Package” must be used.   B. Port mapping entry The primary configuration step is to configure one (1) port forwarding for the BVMS Central Server to utilize port 5322 for both internal and external connections. This is the only port mapping entry that needs to be made for the entire system. The image below shows a sample configuration.   2. Operation   A. Login with the Operator Client After the basic configuration is done, logging in via Operator Client is very intuitive: From the log menu, select the “Connection” drop down menu, then Select <New…> You will be prompted to enter an IP address or DNS host name. You will also notice a cheat guide below the entry menu that will assist with address entry. Addressing must be in the following format: ssh://IP or servername:5322. In the example we used: ssh://49.49.49.49:5322. After entering a properly formatted address, enter a valid user name and password. SSH users MUST have a password associated with their BVMS account. User accounts without a password cannot log in utilizing an SSH Connection.   B. Verification After connection is established via an SSH Tunnel, all communications between the BVMS Server (192.168.1.19) and a remote client (49.49.49.48) are encrypted. Below is a Wireshark Capture taken from the BVMS Server after a connection is established. C. Changing the SSH port Locate the SSH service configuration file in "C:\Program Files\Bosch\BVMS\bin" Open the configuration file and find the section below. Edit the value of the BvmsSshServicePort (the port should be unused) and restart the system.

 This article shows the keyboard shortcuts that can be used by operators when operating the BVMS system. 

This article will provide a basic explanation and simple examples of the interfacing (scripting, calling functions by external applications) functionality in Bosch Video Management System.

Check this article and have a look at the attached documents which describe the settings you must perform after having installed BIS and BVMS on the different computers.

This attached document describes how Bosch Building Technologies handles the life-cycle of the BVMS, BIS, AMS, and APE, and in which state a specific release can reside.

The pop-up dialog window message: "Setup has detected a pending restart.  Please reboot the system and rerun the installation"  appears when attempting to run the valid BVMS windows installer package.

The timeline is present, but the recordings appear to be black for all cameras.

This article provides you with information related to the Windows Firewall, how to access, configure and adjust it.

This article aims to provide concerned parties, such as customers, users, operators or consultants, with an overview of data privacy and protection related features of BVMS Person Identification. Moreover, this article describes how data, as processed during the Person Identification steps, can be classified. Finally, this article lists technical measures for data protection in the context of BVMS Person Identification.

As video surveillance use grows in commercial, government and private use cases, the need for low-cost storage at scale is growing rapidly. BVMS, Bosch cameras, HPE hardware and SUSE Enterprise Storage provide a platform that is an ideal target for recording these streams.

In this scenario, an alarm button is connected to the Adam unit and when this input is activated (close or open), a full screen camera image shows on the display. The display is always logged in the Operator Client for live camera view on the DIVAR IP 7000 AIO.

Use the Project Assistant to its full extent and once the cameras are connected to the target network, perform a network scan using the BVMS Configuration Client

Log4j 1.2.17 is not actively used or called by the SQL Server or by the BVMS. This means that the vulnerabilities are not exploitable unless you install some additional components that refer to the vulnerable component. Therefore, there is no risk of exploitation within the SQL Server or BVMS environment.

This document is specifically for DIP-71xx as it's the DIP which supports certain versions of BVMS (regular BVMS installer) and must be updated in a certain order. The document details how to upgrade from BVMS v8 to BVMS v12.0.1.

Regular BVMS 12.1 installer will not run on any DIVAR IP all-in-one platform. The upgrade shall be performed via DIVAR IP System Manager application.

This document is specifically for DIP-73xx as it's the only DIP with Software Center. The document details how to upgrade all the way from BVMS 10.1 with Software Center and to BVMS 12.1 with System Manager 2.3