Exacq Hardening Guide
Exacq Hardening Guide
Exacq Hardening Guide
exacqVision
Cybersecurity Overview
Whitepaper
Version 1.0
Date: 24-May-2018
security
Introduction
The Tyco security, Cyber Protection Product Security Program provides peace of mind
to our customers with a holistic cyber mindset beginning at initial design concept,
continues through product development, and is supported through deployment,
including a rapid incident response to meet the comprehensive and evolving
cybersecurity environments.
This guide provides hardening guidance for configuration and maintenance, password
strengthening and authentication recommendations, including the operating system’s
user accounts and services with their permissions and roles.
2
security
1 Introduction to Exacq
This section details manual remediation steps that provide greater security for
exacqVision Server, when installed on desktop platforms including Windows 7 or newer,
Ubuntu 10.04 or newer, S-Series, and M-Series.
To remediate a desktop Linux or M-Series system, execute the following script with
sudo and then reboot the system:
#!/bin/bash
/etc/init.d/edvrserver stop
adduser --system --group --shell /usr/bin/nologin edvrserver
usermod -G audio,dialout,cdrom edvrserver
chown -R edvrserver:edvrserver /mnt/edvr
sed -i 's/--start/--start -c edvrserver:edvrserver/' /etc/init.d/edvrserver
if grep -q poeinfo /proc/cpuinfo; then
echo 'SUBSYSTEM=="misc", KERNEL=="i2c", ACTION=="add",\
GROUP="edvrserver", MODE="0660"' >> /etc/udev/rules.d/91-permissions.rules
chown -R edvrserver:edvrserver /opt/exacq/server
else
chown -R edvrserver:edvrserver /usr/local/exacq/server/
fi
To remediate an S-Series system, the administrator must disable the edvrservice from
automatically starting. It should be manually started when performing a configuration,
then stopped when re-configuration operations have been applied. The following steps
explain how this can be accomplished:
Unless a user has deliberately changed them, older servers will have a default
username and password for the administrator and user accounts. We recommend
changing both of these default passwords to prevent unauthorized access to
exacqVision.
Starting with version 9.4 of exacqVision Server, the installer forces the user to change
the default full admin password. However, systems that are upgraded from an older
exacqVision version to version 9.4 will not force this password reset.
This feature, introduced in exacqVision Server version 9.0, enables a more secure
communication protocol between the client and server, by which the server can more
tightly enforce authentication controls. Once a user upgrades both the client and the
server to version 9.0 or newer, the client will feature a Security tab where this feature
can be enabled.
Once the user has done this, machines running older versions of exacqVision Client will
no longer be compatible with the server. This is the desired behavior because older
Client versions allow the setting of weak passwords, whereas newer Client versions (9.0
or higher) force users to set strong passwords.
Passwords themselves will be stored using a salt and hash. This helps prevent a server
from becoming compromised in the event someone gains access to the password file
because passwords that are salted and hashed cannot be converted into cleartext.
Passwords are then further strengthened with the Argon2 key extension algorithm,
thereby making dictionary or brute-force attacks much more time-consuming for
attackers.
If you use the e-mail notification feature, ensure that you only use an SMTPS server
that requires password authentication, and also requires SSL.
If you use the AD/LDAP integration feature, ensure that you only use an LDAP server
that requires password authentication, and also requires SSL.
If you connect an intrusion panel or an access control system, ensure that you only
connect to systems that require password authentication or some sort of secret key
mechanism.
If you use the archiving feature, ensure that you only connect to SMB targets that
require password authentication.
The following functionality has been verified as unavailable when the above server
hardening steps have been applied:
1. Windows Systems
1. Remote updates will fail with the error message "installer failed to
launch." The server must be manually updated.
2. Server failover: The user must employ a third-party solution.
3. The exacqVision DHCP service cannot be used. The user must
implement their own DHCP server on the camera network.
4. Time/Date Configuration: The user can change the time/date/time
zone configuration, but not the network transfer protocol. The user
must manually configure the NTP via Windows Control Panel.
5. Extended storage (iSCSI) support: The user must manually
configure the iSCSI initiator.
6. Motherboard sensor monitoring (voltage, fan, temperature): No
workaround is available.
7. Motherboard hardware watchdog support: The user will have to
configure a Windows task with administrator privileges.
3 Web Service
This section details manual remediation steps that provide greater security for
exacqVision Web Service, when installed on desktop platforms including Windows 7 or
newer, Ubuntu 10.04 or newer, S-Series, and M-Series. Remediation of the Web
Service is performed in the steps outlined below.
1. Log into the web service configuration by clicking the “Web Service
Configuration” link on the web service landing page.
• If this link is not displayed, the “Restrict to localhost” setting is enabled.
Either access the web service directly from the machine or disable this
setting.
2. Select Configuration -> HTTPS from the navigation menu.
3. Click the Configure button.
4. From the drop down, select the desired configuration type (Let’s Encrypt or
External).
5. Supply the required information for the selected type and click Apply.
6. Restart the web service when prompted. The web service is now reachable
via HTTPS.
Reconfigure the exacqVision Web Service service to instead run as "Local Service."
The Web Service always installs itself as Local System, which grants unlimited OS
administrative privileges to the software. This may be construed as a security risk if
the OS itself becomes compromised. The LocalService account is considered more
appropriately secure for a long-running Windows Service that accepts incoming
network connections. To do so:
1. Stop the exacqVision Web Service and exacqVision Web Server services.
2. Right-click on each service and select Properties.
3. On the Log On tab, select This Account and enter "Local Service".
4. Clear both password controls.
5. Click Apply.
6. Services control panel should indicate "Local Service" for service.
7. Start the services. Task Manager should show multiple evws processes and a
wfe process running as LOCAL SERVICE.
Due to the nature of some of the remediation steps, the following functions become
unavailable when these steps have been applied:
1. Updates (Windows Only): Attempting to update the web service through the
service configuration will result in an error message of “An error occurred
while installing the update.” The web service must be manually updated.
2. Restarting (Windows Only): Attempting to restart the web service through the
service configuration will result in an error message of “There was an error
exacqVision Overview Whitepaper
Copyright © 2018 Johnson Controls. All rights Reserved.
during restart.” The web service must be manually restarted using the
Windows Services utility or through the provided Start Menu shortcuts.