Tripwire Operations Center: Provisioning Guide
Tripwire Operations Center: Provisioning Guide
PROVISIONING GUIDE
FOUNDATIONAL CONTROLS FOR SECURITY, COMPLIANCE & IT OPS
© 2017-2018 Tripwire, Inc. All rights reserved.
Tripwire is a registered trademark of Tripwire, Inc. Other brand or product names may be trademarks or
registered trademarks of their respective companies or organizations.
Contents of this document are subject to change without notice. Both this document and the software described
in it are licensed subject to Tripwire’s End User License Agreement located at https://www.tripwire.com/terms,
unless a valid license agreement has been signed by your organization and an authorized representative of
Tripwire. This document contains Tripwire confidential information and may be used or copied only in
accordance with the terms of such license.
This product may be protected by one or more patents. For further information, please visit:
https://www.tripwire.com/company/patents.
Tripwire software may contain or be delivered with third-party software components. The license agreements
and notices for the third-party components are available at: https://www.tripwire.com/terms.
Tripwire, Inc.
One Main Place
101 SW Main St., Suite 1500
Portland, OR 97204
US Toll-free: 1.800.TRIPWIRE
main: 1.503.276.7500
fax: 1.503.223.0182
https://www.tripwire.com
[email protected]
Contents
Overview 4
Hardware and Software Requirements 4
Port Requirements 5
Installing Tripwire Operations Center 6
Step 1: Create a Virtual Machine for the Operations Center Appliance 6
Step 2: Configure the Operations Center Appliance 15
For information on using Tripwire Operations Center after it is installed, see the Tripwire
Operations Center Setup Guide.
Default
Port Description
443 Used to receive connections from the TE Supervisor installed on each monitored TE Console
system. A TE Supervisor establishes a secure connection between a TE Console and the
Operations Center, and manages communication using the TE REST API
Also used to connect with Tripwire servers to update the Operations Center software. For more
information about updates, see the Tripwire Operations Center Setup Guide.
22 Used by the Admin CLI to communicate with the Operation Center appliance over SSH.
Note Tripwire recommends that you periodically take snapshots of the virtual machine
where the Operations Center is installed for backup purposes.
2. In the Navigator panel on the left, select the location in which you want to create the new
VM (for example, a folder or datacenter).
4. In the 'Select source' dialog of the Deploy OVF Template wizard, complete one of the
following steps to select the Operations Center Open Virtualization Format (OVF)
package and click Next.
l Select URL and enter the URL from which the Operations Center OVA can be
downloaded and installed, OR
l Select Local file, click Browse, and select the OVF package.
The OVA file contains the OVF package and vSphere will automatically extract the OVF
file from the OVA.
9. In the 'Setup networks' dialog, select an appropriate VLAN for the lone network adapter,
then click Next.
10. In the 'Ready to complete' dialog:
a. Review and confirm your settings.
b. Click Finish to deploy the Operations Center appliance VM. The system will
display a progress bar indicating the progress of your deployment.
Note Tripwire recommends adjusting your virtual resources before the Operations
Center Appliance VM is powered on for the first time. If you decide to add
additional disk space to the VM once it has started collecting data, you will
first need to add another disk device.
2. In the Hyper-V Manager, select Action > New > Virtual Machine.
7. In the Configure Networking dialog, select a network adapter for your Operations Center
Appliance VM and click Next.
8. In the Connect Virtual Hard Disk dialog:
a. Select Use an existing virtual hard disk.
b. Extract the Operations Center Hyper-V zip file containing a VHDX file.
c. Click Browse to select the VHDX file and click Next.
9. Review your settings and click Finish to deploy the Operations Center appliance VM.
10. To configure the processors needed for the VM, right-click the virtual machine in the
Hyper-V Manager and select Settings.
Note Tripwire recommends at least four (4) processors for each Operations Center
appliance VM. For large-scale deployments, we recommend eight (8)
processors.
12. In the Hyper-V Manager, right-click the Operations Center appliance VM and select
Start.
Once you are connected to the Operations Center appliance's command line interface, proceed
to Step 2: Configure the Operations Center Appliance on the next page.
Notes These credentials are only for the Operations Center appliance CLI and are
different from the credentials used to log in to the Operations Center UI.
Note If your environment is using DHCP, use the steps in Configuring the Operations
Center Appliance for a DHCP Environment on the next page instead.
Note If the hostname is incorrectly set and the Operations Center has been started,
certificates will need to be regenerated after the hostname is updated with the
correct name. See the Tripwire Operations Center Setup Guide for detailed
instructions.
3. To configure the network-interface properties for the Operations Center appliance, enter:
network interface update <interface> <ip_address_and_netmask>
network interface_media update <interface> <speed> <duplex>
where:
<interface> is the network interface card (NIC),
<ip_address_and_netmask> is the IP address and netmask of the Operations Center appliance,
<speed> is the speed of the network (e.g., 100BaseTX, 1000BaseTX, etc.), and
<duplex> is either half-duplex or full-duplex.
For example:
network interface update enp0s17 10.1.2.3/255.255.255.0
network interface_media update enp0s17 1000BaseT full-duplex
For example:
network route_default create 10.0.0.1
For example:
system nameserver create 192.168.1.2
Where <network> is the IP address and netmask of the network hosting the Operations
Center Appliance.
For example:
network route create enp0s17 10.1.5.0/24 10.1.0.1