Amp Threat Grid Appliance Admin Guide 2 1 3

Cisco AMP Threat Grid Appliance
Administrator's Guide
Version 2.1.3
Last Updated: 8/11/2016
Cisco Systems, Inc. www.cisco.com
Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco
website at www.cisco.com/go/offices.
Cisco AMP Threat Grid Appliance Administrator's Guide
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE
SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND
RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED
WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY
FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET
FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED
HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED
WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the
University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system.
All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF
THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED
SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION,
THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR
ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL,
CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR
LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF
CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual
addresses and phone numbers. Any examples, command display output, network topology diagrams, and other
figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or
phone numbers in illustrative content is unintentional and coincidental.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and
other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party
trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a
partnership relationship between Cisco and any other company.
Cover photo: Claret Cup cactus in bloom on a ridge high above the Arches National Park visitor's center. It takes
good defenses and making the most of your resources to flourish in a harsh and hostile environment. Copyright
© 2015 Mary C. Ecsedy. All rights reserved. Used with permission.
Cisco AMP Threat Grid Appliance Administrator’s Guide

All contents are Copyright © 2015-2016 Cisco Systems, Inc. and/or its affiliates. All rights reserved.
CONTENTS
CONTENTS

LIST OF FIGURES .................................................................................................................... iii
INTRODUCTION ...................................................................................................................... 1
Who This Guide Is For ....................................................................................................................... 1
What’s New ..................................................................................................................................... 1
Version 2.0.3 ........................................................................................................................................ 1
Version 2.0 ........................................................................................................................................... 1
GETTING STARTED .................................................................................................................. 2
Updates ........................................................................................................................................... 2
Documentation ................................................................................................................................ 2
Threat Grid Appliance Setup and Configuration Guide ....................................................................... 2
Threat Grid Appliance Release Notes .................................................................................................. 2
Threat Grid Portal Release Notes ......................................................................................................... 2
Threat Grid Portal Online Help and API Documentation ..................................................................... 2
ESA/WSA Appliance Documentation ................................................................................................... 2
Licensing .......................................................................................................................................... 3
Rate Limits ........................................................................................................................................... 3
Assumptions .................................................................................................................................... 3
ADMINISTRATION .................................................................................................................. 4
Power On ......................................................................................................................................... 4
Login Names and Passwords -‐ Defaults ............................................................................................. 6
Threat Grid Portal UI Administrator ..................................................................................................... 6
TGA Administrator -‐ OpAdmin and threatgrid User ............................................................................ 6
CIMC (Cisco Integrated Management Controller) ............................................................................... 6
Lost Password Recovery ................................................................................................................... 6
Resetting a Lost Administrator's Password .......................................................................................... 6
Installing Updates ............................................................................................................................ 8
Appliance Build Number/Version Lookup Table .................................................................................. 9
Updates Port ...................................................................................................................................... 12
Updates Troubleshooting .................................................................................................................. 12
Support -‐ Contacting Threat Grid .................................................................................................... 12
Support Mode .................................................................................................................................... 12
Support Servers .................................................................................................................................. 13
Support Snapshots ............................................................................................................................. 13
Backups .......................................................................................................................................... 14
CONFIGURATION MANAGEMENT ......................................................................................... 15
Network Interface Configuration Management – TGSH Dialog ....................................................... 15
Reconnecting to the TGSH Dialog ...................................................................................................... 15
Password Updates ............................................................................................................................. 16
Setting Up Networking in Recovery Mode ......................................................................................... 16
Main Configuration Management – OpAdmin Portal ...................................................................... 16
i
CONTENTS
SSH Keys ............................................................................................................................................. 17

Syslog ................................................................................................................................................. 17
Reconfiguration ................................................................................................................................. 17
Using DHCP .................................................................................................................................... 19
Explicit DNS for DHCP ........................................................................................................................ 19
Network Configuration and DHCP ..................................................................................................... 20
Apply the DHCP Configuration ........................................................................................................... 20
SSL CERTIFICATES AND THREAT GRID APPLIANCES ................................................................ 21
Interfaces That Use SSL .................................................................................................................. 21
SSL/TLS Versions Supported ........................................................................................................... 21
Customer-‐Provided CA Certificates Are Supported ......................................................................... 21
SSL Certificates -‐ Self-‐Signed Default .............................................................................................. 21
Configuring SSL Certificates for Inbound Connections ..................................................................... 21
CN Validation ..................................................................................................................................... 22
Replacing an SSL Certificate ............................................................................................................... 22
Regenerating an SSL Certificate ......................................................................................................... 23
Downloading an SSL Certificate ......................................................................................................... 23
Uploading an SSL Certificate .............................................................................................................. 23
Generating Your Own SSL Certificate – an Example Using OpenSSL ................................................. 23
Configuring SSL Certificates for Outbound Connections .................................................................. 25
Configure DNS .................................................................................................................................... 25
CA Certificate Management ............................................................................................................... 25
Disposition Update Service Management ......................................................................................... 25
Connecting ESA/WSA Appliances to a Threat Grid Appliance .......................................................... 26
Links to ESA/WSA Documentation ..................................................................................................... 26
Activating a New Device User Account on the Threat Grid Appliance. .............................................. 27
Connecting a Threat Grid Appliance to a Cisco FireAMP Private Cloud ............................................ 27
MANAGING THREAT GRID ORGANIZATIONS AND USERS ...................................................... 33
Creating a New Organization .......................................................................................................... 33
Managing Users ............................................................................................................................. 34
PRIVACY AND SAMPLE VISIBILITY ......................................................................................... 35
Privacy and Visibility on Threat Grid Appliances ............................................................................. 35
WIPE APPLIANCE .................................................................................................................. 37
Wipe Options ..................................................................................................................................... 39
APPENDIX -‐ OPADMIN MENUS ............................................................................................. 40
Configuration Menu ....................................................................................................................... 40
Operations Menu ........................................................................................................................... 41
Status Menu ................................................................................................................................... 42
Support Menu ................................................................................................................................ 43
ii
LIST OF FIGURES
LIST OF FIGURES
Figure 1 - Cisco Screen During Boot Up................................................................................. 4

Figure 2 - TGSH Dialog .......................................................................................................... 5
Figure 3 - Boot Menu - Recovery Mode .................................................................................. 7
Figure 4 - The Threat Grid Shell in Recovery Mode ............................................................... 7
Figure 5 - Enter a New Password ........................................................................................... 8
Figure 6 - Appliance Version Number ..................................................................................... 9
Figure 7 - OpAdmin Start a Live Support Session ................................................................ 13
Figure 8 - Reconfigure Now .................................................................................................. 18
Figure 9 - TGSH Dialog (Connected to a Network Configured to Use DHCP) ..................... 19
Figure 10 - SSL Certificate Configuration Page .................................................................... 22
Figure 11 - User Details Page > Re-Activate User ............................................................... 27
Figure 12 - Privacy and Visibility on a Threat Grid Appliance ............................................... 36
Figure 13 - Wipe Appliance................................................................................................... 37
Figure 14 - Wipe Options ...................................................................................................... 38
Figure 15 - Wipe Finished ..................................................................................................... 39
Figure 16 - OpAdmin Configuration Menu ............................................................................ 40
Figure 17 - OpAdmin Operations Menu ................................................................................ 41
Figure 18 - OpAdmin Status Menu ....................................................................................... 42
Figure 19 - OpAdmin Support Menu ..................................................................................... 43
iii
INTRODUCTION
INTRODUCTION
A Cisco AMP Threat Grid Appliance ("TGA") provides the complete AMP Threat Grid malware analysis platform
installed on a single Cisco UCS server (UCS C220-M3). Threat Grid Appliances provide a safe and highly secure
on-premises environment for performing advanced malware analysis, with detailed threat analytics and content.
Many organizations that handle sensitive data, such as banks, insurance companies, healthcare services, etc.,
must follow various regulatory compliance rules, policy restrictions, and other guidelines that prohibit certain
types of files, such as malware artifacts, to be sent outside of the network for malware analysis. By maintaining a
Threat Grid Appliance on-premises, these organizations are able to send suspicious documents and files to the
appliance to be analyzed without ever leaving the network.
With an AMP Threat Grid Appliance, security teams can analyze all samples using proprietary and highly secure
static and dynamic analysis techniques. The appliance correlates the analysis results with hundreds of millions of
previously analyzed malware artifacts, to provide a global view of malware attacks and campaigns, and their
distributions.
A single sample of observed activity and characteristics can quickly be correlated against millions of other
samples to fully understand its behaviors within an historical and global context. This ability helps security teams
to effectively defend the organization against threats and attacks from advanced malware.
Who This Guide Is For

This document is the TGA administrator's guide. It describes how to get started with a new Threat Grid
Appliance, and how to manage the appliance for optimum malware analysis. This guide also provides
information for administrators who are integrating the Threat Grid Appliance with other Cisco products and
services, such as ESA and WSA appliances and FireAMP Private Cloud devices.
For information about Threat Grid Appliance setup and configuration, please see the Threat Grid Appliance
Setup and Configuration Guide, which is available on the Threat Grid Appliance product documentation page.
What’s New
Version 2.0.3
This point release introduces a number of features to support FireAMP Private Cloud device integrations. These
include the ability to split DNS between the Clean and Dirty interfaces, CA Management, and FireAMP
Integration Configuration.
Generated SSL certificates now have the CN duplicated as a subjectAltName. This addresses an incompatibility
with SSL clients which ignore the CN field when at least one subjectAltName is present. It may be necessary to
regenerate any previously appliance-generated certificates if using such tools.
Version 2.0
Version 2.0 is a major release, built upon an updated operating system. It includes enhancements that will
support future hardware releases, and also brings the Threat Grid Portal UI more in line with the Cloud version.
This includes significant numbers of new and updated Behavioral Indicators and other changes.
Please read the Threat Grid Portal Release Notes beginning with release 3.3.45 for details. (From the Portal UI
Navigation bar select Help, then click on the link to the release notes. The notes are cumulative: the most recent
version contains all previous notes.
1
GETTING STARTED
GETTING STARTED
A Cisco AMP Threat Grid Appliance is a Linux server that has been installed prior to shipping with all
components necessary to analyze samples. After a new appliance is received, it must first be set up and
configured for the on-premises network environment.
Once the server is up and running, the Threat Grid Appliance administrator is responsible for managing
organizations and users for the Threat Grid malware analysis tool, as well as appliance updates, backups, and
for performing other server administration tasks.
Updates
We recommend updating the appliance prior to use, in order to ensure that all the latest features and security
updates are installed.
Check for new release updates and install them, as described in the Installing Updates section.
Documentation
Threat Grid Appliance documentation (including this document, the Threat Grid Appliance Setup and
Configuration Guide, a formatted version of the Release Notes, integration guides, etc.) is available on the
internal resources page on the Cisco.com website: Install and Upgrade Guides. This page contains links to
documentation for the current and older appliance releases.
Threat Grid Appliance Setup and Configuration Guide

The Threat Grid Appliance Setup and Configuration Guide is the companion to the current document. It contains
detailed setup information, including network interfaces, suggested firewall rules, network diagram, configuration
instructions, and other tasks.
Threat Grid Appliance Release Notes

OpAdmin Portal > Operations > Update Appliance > Release Notes
Note: A formatted, PDF version of the Threat Grid Appliance Release Notes is also available on the
Install and Upgrade Guides page – see link above.
Threat Grid Portal Release Notes

Portal UI Navigation bar > Help > Release Notes
Threat Grid Portal Online Help and API Documentation

The Threat Grid Portal’s Using Threat Grid Online Help, API documentation, and other information is available
from the main Threat Grid Portal Help page:
Threat Grid Portal user interface >Navigation bar > Help
The Help home page opens, with links to the documentation.
ESA/WSA Appliance Documentation

For information on connecting an ESA or WSA appliance with a Threat Grid Appliance, see Connecting
ESA/WSA Appliances to a Threat Grid Appliance.
2
GETTING STARTED
See the instructions for "Enabling and Configuring File Reputation and Analysis Services" in the online help
or user guide for your ESA/WSA.
• The ESA user guides are located here:

http://www.cisco.com/c/en/us/support/security/email-security-appliance/products-user-guide-
list.html
• The WSA user guides are located here:

http://www.cisco.com/c/en/us/support/security/web-security-appliance/products-user-guide-list.html
Licensing
The Threat Grid license is managed in the OpAdmin Configuration License page:
Configuration > License
For questions about licenses, please contact [email protected].
Rate Limits
The API rate limit is global for the appliance under the terms of the license agreement. This affects API
submissions ONLY, not manual sample submissions.
Rate limits are based on a 24-hour window of rolling time, not to a calendar day. When the submission limit is
exhausted, the next API submission will return a 429 error, plus a message about how long to wait before
retrying.
Assumptions
This guide assumes that the initial setup and configuration steps have been completed as described in the
Threat Grid Appliance Setup and Configuration Guide, and that an initial test malware sample has been
successfully submitted and analyzed.
3
ADMINISTRATION
ADMINISTRATION
Power On
Turn on the Appliance and wait for it to boot up. The Cisco screen is displayed briefly:
Figure 1 - Cisco Screen During Boot Up
Note: If you want to configure the CIMC interface, press F8 after the memory check is completed.
For more information, see the section, Configuring CIMC, located in the Threat Grid Appliance Setup and
Configuration Guide.
The TGSH Dialog is displayed on the console when the server has successfully booted up and connected.
4
ADMINISTRATION
Figure 2 - TGSH Dialog
Note: After the TG appliance has been setup and configured, the TGSH Dialog will no longer display the
Password, which you need in order to access and configure the OpAdmin interface.
Lost Password: If you lose this password in the future, see Lost Password Recovery for instructions.
5
ADMINISTRATION
Login Names and Passwords - Defaults

Threat Grid Portal UI Administrator
• Login: "admin"
• Password: "changeme"
TGA Administrator - OpAdmin and threatgrid User

The OpAdmin administrator's password is the same as the "threatgrid" user password. It is maintained in the
OpAdmin interface. The default administrator's password was changed during the initial TGA setup, and is not
displayed in visible text once that step is completed. If the password is lost and you are unable to login to
OpAdmin, follow the Lost Password Recovery instructions below.
CIMC (Cisco Integrated Management Controller)

• Login: "admin"
• Password: "password"
Lost Password Recovery

The default administrator's password is only visible in the TGSH Dialog during the initial appliance setup and
configuration. Once the initial configuration is completed the password is no longer displayed in visible text.
If you lose the administrator's password and are unable to login to OpAdmin, complete the following steps:
Resetting a Lost Administrator's Password

1. Reboot your Appliance.
During the boot, there will be a brief window of time in which you can select Recovery Mode, as shown
below:
6
ADMINISTRATION
Figure 3 - Boot Menu - Recovery Mode
The Threat Grid Shell opens:
Figure 4 - The Threat Grid Shell in Recovery Mode
2. Run passwd to change the password:
7
ADMINISTRATION
Figure 5 - Enter a New Password
Note: The command prompt is not always visible in this mode and logging output may be displayed at any point
on top of your input. This does not affect input; you can keep typing "blindly".
3. Ignore the 2 lines of logging output. Blindly enter the password, press enter, and then retype the password
and enter again. The password will not be displayed.
4. You MUST type exit from the command line in order for the new password to be saved.
Rebooting will not save the new password. If you do not exit - even though everything appears to be OK -
the password change will be quietly discarded.
5. Next, type the command reboot and press Enter to start the appliance in normal mode.
Installing Updates
Before you can update the Threat Grid Appliance with newer versions, you must have completed the initial setup
and configuration steps as described in the Threat Grid Appliance Setup and Configuration Guide .
New Appliances: If you have a new Appliance that shipped with an older version and wish to install updates,
you must complete the initial configuration first. Do Not apply the updates until all Appliance configuration is
done.
Appliance updates will not download unless the license is installed, and may not apply correctly if the Appliance
has not been fully configured, including the database.
Threat Grid Appliance updates are applied through the OpAdmin Portal.
Updates are one-directional: you cannot revert to a previous version after you upgrade to a more recent version.
To test the update, submit a sample for analysis.
1. From the Operations menu, select Update Appliance.
The updates page opens, displaying the current build of the Appliance:
8
ADMINISTRATION
Figure 6 - Appliance Version Number
2. Click Check/Download Updates. The software checks to see if there is a more recent update/version of the
Appliance software, and if so, it is downloaded.
Note: The download can take some time:
• Updating from 1.0 to 1.0+hotfix2 takes approximately15 minutes.
• Applying a full update from 1.0 to 1.3 (without data migration) takes about 30 minutes.
3. Once the updates have been downloaded, click Run Update to install them.
Appliance Build Number/Version Lookup Table

The build number of an Appliance can be viewed on the Updates page (OpAdmin Operations > Update
Appliance), as illustrated above.
Appliance build numbers correspond to the following release version numbers:
9
ADMINISTRATION
Build Number Release Version Release Date Notes
2016.05.20160811044721.6af0fa61.rel 2.1.3 8/11/2016 Offline

update
support key,
M4 wipe
support
2016.05.20160715165510.baed88a3.rel 2.1.2 7/15/2016
2016.05.20160706015125.b1fc50e5.rel-1 2.1.1 7/6/2016
2016.05.20160621044600.092b23fc 2.1 6/21/2016
2015.08.20160501161850.56631ccd 2.0.4 5/1/2016 Starting point

for the 2.1
update. You
must be at
2.0.4 before
you can
update to 2.1.
2015.08.20160315165529.599f2056 2.0.3 3/15/2016 Introduces

AMP
integration,
CA mgmt.,
and split DNS
2015.08.20160217173404.ec264f73 2.0.2 2/18/2016
2015.08.20160211192648.7e3d2e3a 2.0.1 2/12/2016
2015.08.20160131061029.8b6bc1d6 2.0 2/11/2016 Force update

to 2.0.1 from
here
2014.10.20160115122111.1f09cb5f 1.4.6 1/27/2016 Starting point

for the 2.0.4
NOTE: This is the
update
starting point for the 2.0
upgrade.
2014.10.20151123133427.898f70c2 v1.4.5 11/25/2015
2014.10.20151116154826.9af96403 v1.4.4
2014.10.20151020111307.3f124cd2 v1.4.3
2014.10.20150904134201.ef4843e7 v1.4.2
2014.10.20150824161909.4ba773cb v1.4.1
10
ADMINISTRATION
Build Number Release Version Release Date Notes
2014.10.20150822201138.8934fa1d v1.4
2014.10.20150805134744.4ce05d84 v1.3
2014.10.20150709144003.b4d4171c v1.2.1
2014.10.20150326161410.44cd33f3 v1.2
2014.10.20150203155143+hotfix1.b06f7b4f v1.1+hotfix1
2014.10.20150203155142.b06f7b4f v1.1
2014.10.20141125162160+hotfix2.8afc5e2f v1.0+hotfix2
NOTE: The 1.0+hotfix2
is a mandatory update
that fixes the update
system itself to be able
to handle large files
without breaking.
2014.10.20141125162158.8afc5e2f v1.0
11
ADMINISTRATION
Updates Port
The Threat Grid Appliance downloads release updates over SSH, port 22.
• Starting with the appliance version 1.1, release updates can also be applied from the textual (curses)
interface, not just from the web-based administrative interface (OpAdmin), which is described below.
• As of 1.3, systems using DHCP need to explicitly specify DNS. Previously, they did not. An upgrade of a
system without a DNS server explicitly specified to 1.3 will fail.
Updates Troubleshooting
A "database upgrade not successful" message means that a new appliance is running an older version of
PostgreSQL than it's supposed to.
This is a critical thing to fix prior to any upgrade to 2.0 as it means the automated database migration process
didn't succeed.
Please see the Release Notes for v2.0.1 for more information.
Support - Contacting Threat Grid

If you need any assistance, there are several ways to request support from a Threat Grid engineer:
• Email. Send email to [email protected] with your query.
• Open a Support Case. You will need your Cisco.com ID (or to generate one) to open a support case.
You will also need your service contract number which was included on the order invoice.
https://tools.cisco.com/ServiceRequestTool/scm/mgmt/case
• Call. See: http://www.cisco.com/c/en/us/support/index.html
When requesting support from Threat Grid, please send the following information with your request:
• Appliance version: OpAdmin > Operations > Update Appliance)
• Full service status (service status from the shell)
• Network diagram or description (if applicable)
• Support Mode (Shell or Web interface)
• Support Request Details
Support Mode
If you require support from a Threat Grid engineer, they may ask you to enable "support mode", which is a live
support session that gives Threat Grid support engineers remote access to the appliance. Normal operations of
the appliance will not be affected. This can be done via the OpAdmin Portal Support menu. (You can also
enable SUPPORT MODE from the TGSH Dialog.)
To start a live support session with Threat Grid tech support:
In OpAdmin, Select Support > Live Support Session and click Start Support Session.
12
ADMINISTRATION
Figure 7 - OpAdmin Start a Live Support Session
Support Servers
Establishing a support session requires that the TG appliance reach the following servers:
• support-snapshots.threatgrid.com
• rash.threatgrid.com
Both servers should be allowed by the firewall during an active support session.
Support Snapshots
A support snapshot is basically a snapshot of the running system, which contains logs, ps output, etc., to help
Support staff troubleshoot any issues.
1. From the Support menu, select Support Snapshots.
2. Take the snapshot.
3. Once you take the snapshot you can either download it yourself as .tar .gz, or you can press Submit, which
will automatically upload the snapshot to the Threat Grid snapshot server.
13
ADMINISTRATION
Backups
In OpAdmin, under Operations > Backups
Backups contain a set of config files currently active on the appliance, such as installed SSL certificates and
networking configuration. They do NOT contain any data about samples, users, or organizations.
Multiple backups can be created and downloaded from the appliance.
14
CONFIGURATION MANAGEMENT
The initial Threat Grid Appliance configuration was performed during the appliance setup, as documented in the
Threat Grid Appliance Setup and Configuration Guide.
Threat Grid Appliance configuration is managed in the TGSH Dialog and the OpAdmin Portal interfaces.
Threat Grid Organizations and User accounts are managed via the Threat Grid Portal UI (from the navigation bar
upper-right Welcome menu).
The TGSH Dialog and OpAdmin configuration tasks are described in detail in the following sections.
Network Interface Configuration Management – TGSH Dialog

The TGSH Dialog interface is used primarily to manage the following:
• Network Interface Configuration
• View the OpAdmin Administrator's Password
• Install Updates
• Enable Support Mode
• Create and Submit Support Snapshots
Note: If you are using DHCP to obtain your IPs, then skip to the Networking section below: Using DHCP.
1. In the TGSH Dialog interface, select CONFIG_NETWORK.
The Network Configuration console opens, displaying the current network settings.
2. Make your changes as needed.
Note: You need to BACKSPACE over the old character before you can enter the new one.
3. Leave the Dirty network DNS Name blank.
4. After you finish updating the network settings, tab down and select Validate to validate your entries.
If invalid values have been entered, you may see errors. If this is the case, then fix the errors and re-
Validate.
After validation, the Network Configuration Confirmation displays the values you've entered.
5. Select Apply to apply your configuration settings.
The console will become a blank grey box, and then it will list detailed information about the configuration
changes that have been made.
6. Select OK.
The Network Configuration Console refreshes again and displays the IP addresses you entered. Network
configuration is now complete.
Reconnecting to the TGSH Dialog

TGSH Dialog will remain open on the console and can be accessed either by attaching a monitor to the
appliance or, if CIMC is configured, via remote KVM.
15
One way to reconnect to the TGSH Dialog is to SSH into the Admin IP address as the user 'threatgrid'. The
required password will either be the initial, randomly generated password, which is visible initially in the TGSH
Dialog, or the new Admin password you create during the first step of the OpAdmin Configuration.
Password Updates
Lost password? See Lost Password Recovery in the Getting Started section, above.
Setting Up Networking in Recovery Mode

1. Initiate a reboot, and wait for the boot menu, which is only present for a short period of time- so be ready
(see Figure 3 - Boot Menu - Support Mode, above).
2. Select Recovery Mode. Wait a couple of minutes for the system to start up.
3. Once the system is up, press Enter several times to get a clean command prompt.
4. Enter netctl clean and answer the questions as follows:
• Configuration type: static
• IP Address: <Clean IP Address>/<Netmask>
• Gateway Address: <Clean network gateway>
• Routes: <leave blank>
• Answer y to the final question.
5. Enter Exit to apply the configuration.
At this point the appliance will attempt to open an outbound support connection on the Clean interface on port
19791/tcp.
Main Configuration Management – OpAdmin Portal

The initial setup and configuration wizard is described in the Threat Grid Appliance Setup and Configuration
Guide. New appliances may require the administrator to completed additional configuration, and OpAdmin
settings may require updates over time.
The OpAdmin Portal is the Threat Grid Appliance administrator’s main configuration interface. It is a Web portal
that can be used once an IP address has been configured on the TGA’s Admin interface.
OpAdmin is the recommended tool for configuring your appliance, and in fact, much of the appliance
configuration can only be done via OpAdmin. OpAdmin is used to configure and manage a number of important
Threat Grid Appliance configuration settings, including:
• The administrator's passwords (for OpAdmin and the "threatgrid" user)
• Threat Grid License
• Rate Limits
• SMTP
• SSH
• SSL Certificates
16
• DNS servers (including DNS configuration for FireAMP Private Cloud integrations)
• NTP servers
• Server Notifications
• Syslog messages and Threat Grid Notifications remote server setup
• CA Certificate Management (for FireAMP Private Cloud integrations)
Note: Configuration updates in OpAdmin should be completed in one session to reduce the chance of an
interruption to the IP address during configuration.
Note: OpAdmin will not validate the gateway entries. If you enter the wrong gateway and save it, the OpAdmin
interface will be inaccessible. You will have to use the console to fix the networking configuration if that was done
on the admin interface. If Admin is still valid, you can fix it in OpAdmin and reboot.
Reminder: OpAdmin uses HTTPS. Pointing a browser at the Admin IP is not sufficient; you must point to:
https://adminIP/ OR https://adminHostname/
SSH Keys
Setting up SSH keys provides the Threat Grid Appliance administrator with access to TGSH Dialog via SSH
(threatgrid@<host>).
It does NOT provide root access or a command shell. Multiple keys may be added.
Configuration > SSH
Syslog
In addition to the periodic notifications that can be set up (in OpAdmin under Configuration > Notifications) to
deliver system notifications via email, you can also configure a remote syslog server to receive syslog messages
and Threat Grid notifications.
1. In OpAdmin, under Configuration > Syslog
2. Enter the server DNS in the field provided, and then select a protocol from the dropdown list; TCP is the
default, the other is UDP.
3. Check the Verification box to perform a DNS lookup when you click Save. If the host cannot resolve the
name, it will print an error and will not save (until you enter a valid hostname).
If you do not check the Verification box, the appliance will accept any name, whether valid in DNS or not.
4. Click Save.
To Edit or Delete: If you need to update the Syslog DNS, simply edit or delete it and click Save.
Reconfiguration
When changes are made to configuration settings, a light blue alert appears below the Configuration menu.
When you are done updating any OpAdmin configuration settings, you must save the reconfiguration in a
separate step.
1. Click Configuration Changed. The Reconfiguration dialog opens:
17
Figure 8 - Reconfigure Now
2. Click Reconfigure to apply your changes to the appliance.
18
Using DHCP
Most Appliance users do not use a network configured with DHCP. However, if you are connected to a network
configured to use DHCP, then read this section.
Note: If the initial appliance network configuration used DHCP and you now need to switch to static IP
addresses, see Network Configuration and DHCP below.
TGSH Dialog displays the information you will need to in order to access and configure the OpAdmin Portal
interface.
The IP addresses for DHCP may not be displayed immediately after your Appliance boots. Please be patient!
Explicit DNS for DHCP

As of v1.3, systems using DHCP need to explicitly specify DNS. Previously, they did not. An upgrade of a system
without a DNS server explicitly specified to 1.3 will fail.
Figure 9 - TGSH Dialog (Connected to a Network Configured to Use DHCP)
• Admin URL: The Admin network. You will need this address in order to continue the remaining
configuration tasks with OpAdmin.
• Application URL: The Clean network.
Note: This is the address to use after completing the configuration with OpAdmin, in order to access the
Threat Grid application.
• The Dirty network is not shown.
• Password is the initial administrator's password, which is randomly generated during the Appliance
installation. You will need to change this password later as the first step the OpAdmin configuration
process.
If you plan on using DHCP on a permanent basis, then no additional network configuration is necessary, unless
you need to change the Admin IP address to static.
19
Network Configuration and DHCP

• If you used DHCP for initial configuration, and you now need to adjust the IP assignment from DHCP to
your permanent static IP addresses for all three networks, follow the steps below:
Note: OpAdmin will not validate the gateway entries. If you enter the wrong gateway and save it, the OpAdmin
interface will be inaccessible. You will have to use the console to fix the networking configuration if that was done
on the admin interface. If Admin is still valid, you can fix it in OpAdmin and reboot.
1. In the left column, click on Network. (Although Configuration > Network is checked in the License window,
the DHCP network configuration has NOT yet been done.)
The Network Configuration page opens.
Clean
2. IP Assignment. Choose Static from the dropdown.
3. IP Address. Enter a static IP Address for the Clean network interface.
4. Complete the Subnet mask and Gateway as appropriate.
5. Check the box next to Validate DNS Name, to verify that the DNS resolves to the IP Address you entered.
Dirty
6. IP Assignment. Choose Static from the dropdown.
7. IP Address. Enter a static IP Address for the Dirty network interface.
8. Complete the Subnet mask and Gateway as appropriate.
Administration
The Admin network settings were configured using the TGSH Dialog during the initial appliance setup and
configuration.
DNS
9. Complete the Primary and Secondary DNS server fields.
Save Your Settings

10. When done, click Next (Applies Configuration) to save your network configuration settings.
SMTP/Email
Email configuration is managed from the Email page.
Time
NTP servers are managed on the Date and Time page.
Apply the DHCP Configuration

To apply your DHCP configuration settings, click Configuration Changed, then Reconfigure Now.
20
SSL CERTIFICATES AND THREAT GRID APPLIANCES

All network traffic passing to and from the Threat Grid Appliance is encrypted using SSL. A full description of how
to administer SSL certificates is beyond the scope of this Guide. However, the following information is provided
to assist you through the steps for setting up SSL certificates to support Threat Grid Appliance connections with
ESA/WSA appliances, FireAMP Private Cloud, and other integrations.
Interfaces That Use SSL

There are two interfaces on the Threat Grid Appliance that use SSL:
• Clean interface for the Threat Grid Portal UI and API, as well as integrations (ESA/WSA appliances,
FireAMP Private Cloud Disposition Update Service, etc.)
• Admin interface for the OpAdmin Portal.
SSL/TLS Versions Supported

• TLSv1.0
• TLSv1.1
• TLSv1.2
Customer-Provided CA Certificates Are Supported

With the 2.0.3 release we now support customer-provided CA certificates, allowing customers to import their own
trusted certificates or CA certificates.
SSL Certificates - Self-Signed Default

The Threat Grid Appliance is shipped with a set of self-signed SSL certificates and keys already installed. One
set is for the Clean interface and the other is for the Admin interface. The appliance SSL certificates can be
replaced by an administrator.
The default Threat Grid Appliance SSL certificate hostname (Common Name) is "pandem", which is valid for 10
years. If a different hostname was assigned to the Threat Grid Appliance during configuration, then the hostname
and the CN in the certificate will no longer match. The hostname in the certificate must also match the hostname
expected by a connecting ESA or WSA appliance, or other integrating Cisco device or service, as many client
applications require SSL certificates where the CN used in the certificate matches the hostname of the
appliance.
Configuring SSL Certificates for Inbound Connections

Other Cisco products, such as such as ESA and WSA appliances and FireAMP Private Clouds, can integrate
with a Threat Grid Appliance and submit samples to it. These integrations are Inbound connections from the
perspective of the Threat Grid Appliance. The integrating appliance or other device must be able to trust the
Threat Grid Appliance’s SSL certificate, so you will need to export it from the TGA (first making sure that it uses
the correct hostname in the CN field and regenerating or replacing it if necessary), and then import it into the
integrating appliance or service.
21
The certificates on the Threat Grid Appliance that are used for inbound SSL connections are configured in the
SSL Certificate Configuration page. The SSL certificates for the Clean and Admin interfaces can be
configured independently.
Select OpAdmin > Configuration > SSL. The SSL Certificate configuration page opens:
Figure 10 - SSL Certificate Configuration Page
There are two SSL certificates in the illustration above: "ThreatGRID Application" is the Clean interface, and
"Administration Portal" is the Admin interface.
CN Validation
In the SSL Certificate Configuration page, a colored padlock icon indicates the status of the SSL certificates on
the TG Appliance. The hostname must match the CN (“Common Name”) used in the SSL certificate. If they do
not match, you will need to replace the certificate with one that uses the current hostname. See Replacing an
SSL Certificate below.
• The green padlock icon indicates that the Clean interface hostname matches the CN ("Common
Name") used in the SSL certificate.
• The yellow padlock icon is a warning that the Admin interface hostname does NOT match the CN in that
SSL certificate. You will need to replace the certificate with one that uses the current hostname.
Replacing an SSL Certificate

SSL certificates usually need to be replaced at some time, for a variety of reasons. For example, they expire, or
the hostname changes. An SSL certificate may also need to be added or replaced in order to support
integrations between the Threat Grid Appliance and other Cisco devices and services.
ESA/WSA appliances and other CSA Cisco integrating devices may require an SSL certificate in which the
Common Name matches the Threat Grid Appliance hostname. In this case, you will need to replace the default
SSL certificate and generate a new one using the same hostname from which you'll be accessing the Threat Grid
Appliance.
22
In the case where you are integrating a Threat Grid Appliance with a FireAMP Private Cloud to use its
Disposition Update Service, you will need to install the FireAMP Private Cloud SSL Certificate so the Threat Grid
Appliance can trust the connection.
There are several ways to replace an SSL certificate on a Threat Grid Appliance:
• Regenerating a new SSL Certificate, which will use the current hostname for the CN.
• Downloading an SSL Certificate
• Uploading a new SSL Certificate. This can be a commercial or enterprise SSL, or one you make
yourself using OpenSSL.
• Generating Your Own SSL Certificate – an Example Using OpenSSL
These are described in the following sections.
Regenerating an SSL Certificate

This replaces the need in pre-v1.3 Threat Grid Appliances to generate a new SSL certificate manually using
OpenSSL or other SSL tool. However, that method is still valid, as described in the section Generating Your Own
SSL Certificate – an Example Using OpenSSL, below.
NOTE: The Threat Grid Appliance should be upgraded to 1.4.2 or higher before performing this task.
In the OpAdmin SSL Certificate Configuration page, click Regenerate. A new, self-signed SSL certificate is
generated on the Threat Grid Appliance that uses the current hostname of the appliance in the CN field of the
certificate. The CN validation padlock icon is green. The regenerated certificate (.cert file) can be downloaded as
described in the next section, and installed on the integrating appliance.
Downloading an SSL Certificate

The Threat Grid SSL certificate, but not the key, can be downloaded, and installed on your integrating device so
it can trust connections from the TG Appliance. You will only need the .cert file for this step.
1. In the OpAdmin SSL Certificate Configuration page, click Download next to the certificate you wish to
obtain. The SSL Certificate is downloaded.
2. Next, install the downloaded SSL certificate on the ESA/WSA appliance, FireAMP Public Cloud, or other
integrating Cisco products just as you would install any other SSL certificate.
Uploading an SSL Certificate

If you already have a commercial or corporate SSL certificate in place within your organization, you can use that
to generate a new SSL certificate for the TGA, and use the CA cert on the ESA/WSA or other integrating device.
Generating Your Own SSL Certificate – an Example Using OpenSSL

Another alternative is to generate your own SSL certificate manually, such as when there is no SSL certificate
infrastructure already in place on your premises, and you are unable to obtain one by other means. This can then
be uploaded as described above.
This example illustrates the command for generating a new self-signed SSL certificate for the "Acme Company".
The example uses OpenSSL, which is a standard open source SSL tool for creating and managing OpenSSL
certificates, keys, and other files.
23
NOTE: OpenSSL is not a Cisco product, and Cisco provides no technical support for it. Search the Web for
additional information on using OpenSSL. Cisco offers an SSL library, Cisco SSL, for generating SSL
certificates.
openssl req -x509 -days 3650 -newkey rsa:4096 -keyout

tgapp.key -nodes -out tgapp.cert -subj "/C=US/ST=New
York/L=Brooklyn/O=Acme Co/CN=tgapp.acmeco.com"
• openssl: OpenSSL.
• req: Specifies that we want to use X.509 certificate signing request (CSR) management.
"X.509" is a public key infrastructure standard that SSL and TLS use for key and certificate
management. We want to create a new X.509 cert, so we are using this subcommand.
• -x509: This modifies the previous subcommand by telling the utility that we want to make a self-signed
certificate instead of generating a certificate signing request, as would normally happen.
• -days 3650: This option sets the length of time for which the certificate will be considered valid. Here we
set it for 10 years.
• -newkey rsa:4096: This specifies that we want to generate a new certificate and a new key at the same
time. We did not create the key that is required to sign the certificate in a previous step, so we need to
create it along with the certificate. The rsa:4096 portion tells it to make an RSA key that is 4096 bits
long.
• -keyout: This line tells OpenSSL where to place the generated private key file that we are creating.
• -nodes: This tells OpenSSL to skip the option to secure our certificate with a passphrase. The
appliance needs to be able to read the file without user intervention, when the server starts up. A
passphrase would prevent this from happening because we would have to enter it after every restart.
• -out: This tells OpenSSL where to place the certificate that we are creating.
• -subj: Example:
C=US: Country.
ST=New York: State.
L=Brooklyn: Location.
O=Acme Co: Owner's name.
CN=tgapp.acmeco.com: Please enter the Threat Grid Appliance FQDN ("Fully Qualified Domain
Name"). This includes the HOSTNAME of the Threat Grid Appliance ("tgapp" in our example), together
with the associated domain name ("acmeco.com") appended to the end.
IMPORTANT: You will need to change at the very least the Common Name to match the FQDN of the
Threat Grid Appliance Clean interface.
Once the new SSL certificate is generated, use the SSL page Upload button to upload it to the Threat Grid
Appliance, and also upload it to the ESA/WSA appliance (.cert only).
24
Configuring SSL Certificates for Outbound Connections

The Threat Grid Appliance release 2.0.3 includes features to support integrations with FireAMP Private Cloud for
the Disposition Update Service.
Configure DNS
By default, DNS uses the Dirty interface. If the hostname of an integrating appliance or service such as a
FireAMP Private Cloud cannot be resolved over the Dirty interface, because the Clean interface is used for the
integration, then a separate DNS server that uses the Clean interface can be configured in OpAdmin.
In OpAdmin, select Configuration > Network, and complete the DNS fields for the Dirty and Clean
networks, and click Save.
CA Certificate Management
One of the features added with release 2.0.3 is a new page for the CA Certificate Management truststore for the
Outbound SSL connections, so the TGA can trust the FireAMP Private Cloud to notify it about analyzed samples
that are considered to be malicious.
In OpAdmin, select Configuration > CA Certificates. Select:
1. Import from Host. Retrieve the certificate from the server. The Retrieve certificates from server dialog
opens.
2. Enter the Host and Port for the FireAMP Private Cloud and click Retrieve. The certificate is retrieved.
OR
Import from Clipboard. Paste the PEM from the clipboard, and click Add Certificate.
3. Click Import.
Disposition Update Service Management

This task is performed from within the Threat Grid Portal UI.
1. From the My Account dropdown, select Manage FireAMP Integration. The Disposition Update Service
page opens.
2. Enter the FireAMP Private Cloud URL, the admin user name and password provided by the FireAMP
configuration portal, and click Config.
For more information on FireAMP Private Cloud appliance integrations, see Connecting a Threat Grid Appliance
to a Cisco FireAMP Private Cloud:
25
Connecting ESA/WSA Appliances to a Threat Grid Appliance

Cisco products such as ESA/WSA and other appliances, devices, services, etc. may integrate with Threat Grid
Appliances via connections encrypted with SSL, in order to submit possible malware samples to it for analysis.
Integrations between the Threat Grid Appliance and ESA/WSA appliances are enabled by the Cisco Sandbox
API ("CSA API"), are often referred to as "CSA Integrations".
In order for ESA/WSA appliances to connect to a Threat Grid Appliance, the Threat Grid Appliance's SSL
certificate CNs must match its current hostname, which must also be the hostname expected by the integrating
ESA/WSA appliance.
An integrating appliance must be registered with the Threat Grid Appliance before it can submit samples for
analysis. Before an integrating ESA/WSA appliance can register with the Threat Grid Appliance, the ESA/WSA
administrator must first set up the SSL certificate connection as appropriate for their appliance and their network
environment.
This section describes the steps necessary for setting up a Threat Grid Appliance to communicate with
integrating ESA/WSA appliances and other Cisco products.
Links to ESA/WSA Documentation

See the instructions for "Enabling and Configuring File Reputation and Analysis Services" in the online help
or user guide for your ESA/WSA.
• The ESA user guides are located here:

http://www.cisco.com/c/en/us/support/security/email-security-appliance/products-user-guide-
list.html
• The WSA user guides are located here:

http://www.cisco.com/c/en/us/support/security/web-security-appliance/products-user-guide-list.html
1. Hostname Must Match the CN and ESA/WSA Expectations
The CN in the Threat Grid Appliance SSL certificate(s) must match its current hostname. For a successful
connection with an integrating ESA/WSA appliance, this must also be the same hostname by which the
integrating ESA/WSA appliance identifies the TGA.
Depending on your requirements, you may need to regenerate the self-signed SSL certificate on the Threat
Grid Appliance so it uses the current hostname in the CN field, then download it to your working
environment and upload and install it onto the integrating ESA/WSA appliance.
Or, you may need to replace the current TGA SSL certificate by uploading an enterprise or commercial SSL
certificate (or a certificate generated manually).
For detailed instructions, see: Configuring SSL Certificates for Inbound Connections.
Once the SSL certificate setup is complete, the next step is to verify that the Threat Grid Appliance and the
ESA/WSA appliances can communicate with each other.
2. Verify Connectivity
Cisco ESA/WSA appliances must be able to connect to the Clean interface of the Threat Grid Appliance
over your network.
Follow the instructions in the appropriate guide for your product to verify that the TGA and ESA/WSA
Appliances can communicate with each other. (See links above.)
3. Register the Cisco ESA/WSA/other device with theThreat Grid Appliance.
An ESA/WSA appliance that is configured according to the documentation for those products registers itself
automatically with the Threat Grid appliance.
26
4. Complete the ESA/WSA File Analysis Configuration.
Upon registration of the connecting device, a new Threat Grid user is created automatically with the Device ID as
the login ID, and a new organization is created with a name based on the same ID. The new Device user
account must be activated by an administrator, as described in the next section.
Activating a New Device User Account on the Threat Grid Appliance.

When the ESA/WSA appliance or other integration connects and registers itself with the Threat Grid Appliance, a
new Threat Grid user account is created automatically. The initial status of this user account is "de-activated".
Just like any other Threat Grid user, the device user account must be manually activated by a Threat Grid
Appliance administrator before it can be used for submitting malware samples for analysis.
1. Log into the Threat Grid Portal UI as Admin.
2. From the navigation bar Welcome menu, select Manage Users. The Threat Grid Users page opens.
3. Open the User Details page for the device user account (you may need to use Search to find it). The user
status is currently "de-activated":
Figure 11 - User Details Page > Re-Activate User
4. Click Re-Activate User. A dialog opens asking you to confirm.
5. Click Re-Activate in the dialog to confirm.
The ESA/WSA or other integrating appliance or device can now communicate with the Threat Grid Appliance.
Connecting a Threat Grid Appliance to a Cisco FireAMP Private

Cloud
The Threat Grid Appliance Disposition Update Service and FireAMP Private Cloud integration setup tasks must
be performed on the devices in the following order, particularly if you are setting up new appliances. If you are
integrating appliances that are already set up and configured, the order is not as critical.
This connection is outgoing from the perspective of the Threat Grid Appliance. This integration does not use the
CSA API.
27
Please refer to the FireAMP Private Cloud documentation for more detailed information on the tasks which must
be performed on that side.
STEPS Threat Grid Appliance (“TGA”) FireAMP Private Cloud
1 Set up and configure the Threat Grid

Appliance (“TGA”) as normal (i.e., no
integration yet).
2 Set up and configure the FireAMP Private

Cloud as normal (i.e., no integration yet).
3 Configure the FireAMP Private Cloud for

the TGA Integration:
Select Integrations > Threat Grid and go to

the Connection to Threat Grid section.
To complete the connection with the Threat

Grid Appliance, you have to trust it. You need
its DNS hostname, SSL certificate, and API
key.
Go to step 3.1 in the TGA column to find this

information.
28
3.1 SSL Certificate: –
In the Threat Grid Appliance OpAdmin

interface, select Configuration > SSL
Regenerate a new SSL Certificate (on the

“Threat Grid Application” – the Clean
interface), to replace the default if needed,
and download it to install in the FireAMP
Private Cloud device. (TGA SSL Certificates
are documented in SSL CERTIFICATES
AND THREAT GRID APPLIANCES.)
Hostname
Select Configuration > Hostname
API Key:
The API Key may be found in the Threat

Grid Face Portal UI, in the User Details
page for the account that is going to be used
for integrations:
1. Go to the Threat Grid Portal UI.
2. From the upper-right Welcome

menu (located in the upper-right
corner of the navigation bar), select
Manage Users.
3. Navigate (use Search if necessary)

to the User Details page for the
integration’s user account, and
copy the API Key. Note that this
does not need to be the “admin”
user, but can be another user that
was specifically created for this
purpose on the Threat Grid
Appliance.
29
3.2 Complete the Connection to Threat Grid

fields:
1. Enter the TGA Hostname
2. Enter the Threat Grid API Key for the

account that is to be used for
integrations.
3. Choose the TGA SSL Certificate file.
4. Click Save Configuration.
5. Click Test Connection.
6. Once the connection test passes, you

will need to run the Reconfiguration
on the FireAMP Private Cloud to
apply the changes.
Technically, this will allow AMP to talk to the

Threat Grid Appliance, and you can now
submit samples to TG at this point. However,
you must complete the remaining steps to set
up the Disposition Update Service, in order to
communicate disposition results to the TGA.
(For more information, please refer to the user

documentation for the FireAMP Private Cloud.)
4 Set up the Disposition Update Service
The following steps describe how to set up

the Disposition Update Service
30
4.1 Configure DNS (if needed):
The Clean interface is used for the FireAMP

integration. But by default, DNS uses the
Dirty interface. If the FireAMP Private Cloud
hostname cannot be resolved over the Dirty
interface, then a separate DNS server that
uses the Clean interface can be configured
in OpAdmin.
In OpAdmin, select Configuration >

Network, and complete the fields for DNS
on the Dirty and Clean networks, and click
Save.
4.2 CA Certificate Management:
The next step is to download or copy/paste

the FireAMP Private Cloud SSL certificate to
the Threat Grid Appliance so it can trust the
integrating device:
1. In OpAdmin, select Configuration

> CA Certificates. You can select
an SSL certificate to import from
the FireAMP Private Cloud Host, or
import from the clipboard.
2. Select the certificate to import and

click Import from Host. The
Retrieve certificates from server
dialog opens. Enter the Host and
Port for the FireAMP Appliance
Disposition Service, and click
Retrieve.
3. The certificate is retrieved.
4. Click Import.
(OR click Import from Clipboard. Paste the

PEM from the clipboard, and click Add
Certificate.)
31
4.3 FireAMP Integration Management:
In the Threat Grid Face Portal UI, from the

upper-right menu select Manage FireAMP
Integration. The Disposition Update Service
window opens.
Enter the AMP Disposition Update Service

URL (you can find this on the FireAMP
appliance: select Integrations > Threat
Grid > FireAMP Private Cloud Details).
Enter your admin user name and

password, and click Config.
32
MANAGING THREAT GRID ORGANIZATIONS AND USERS

Threat Grid is installed on the appliance with a default organization and Admin user. Once the appliance is set up
and the network configuration is completed, you may create additional organization and user accounts, so
people can login and begin submitting malware samples for analysis.
Adding organizations, users, and administrators may require planning and coordination among multiple users
and teams, depending on your organization.
Creating a New Organization

Users are always affiliated with an organization; before you can add users, you must first create the Organization
to add them to.
IMPORTANT: You cannot delete an organization from this interface once it has been created, so plan this task
carefully.
1. Log into the Threat Grid portal as Admin.
2. Click the Welcome dropdown link located in the upper-left corner, and select Manage Orgs. The
Organizations page opens, listing all of the Organizations on the appliance.
3. Click the Add Organization button, located in the upper-right corner of the screen. The Properties dialog
opens.
4. All fields are required.
Name. Add a name for the organization (there is currently no size limit to the name).
Industry. Select the type of business from the Industry dropdown. If none of the industries on the list are
applicable, then leave it set to Unknown, and contact Threat Grid support ([email protected]) to
request that an option be added.
Complete the other Options.
Rate Limit:
The API rate limit is global for the appliance under the terms of the license agreement. This affects API
submissions ONLY, not manual sample submissions. The rate limit in the license applies to the
Organization.
Set the default user submission rate limit. You can also set sample submission rates on individual users - as
documented in Using Threat Grid, the Threat Grid Portal online Help (From the navigation bar select Help >
Using Threat Grid Online Help).
Rate limits are based on a 24-hour window of rolling time, not to a calendar day. When the submission limit
is exhausted, the next API submission will return a 429 error, plus a message about how long to wait before
retrying.
The Priority field is going away; for now just enter “50”.
5. Click Create. The new organization is created and is now visible in the list of Organizations.
33
Managing Users
For instructions and documentation on managing user accounts - including accounts for integrating Cisco
ESA/WSA appliances and other devices - see the Threat Grid Portal UI online help. From the navigation bar
select Help > Using Threat Grid Online Help > Managing Users.
34
PRIVACY AND SAMPLE VISIBILITY

When submitting samples to Threat Grid for analysis, an important consideration is the privacy of their contents.
Privacy is a particularly important consideration if sensitive documents or archive types are submitted for
analysis, because locating sensitive material could be relatively easy for those with access to Threat Grid,
especially with the search API.
Privacy may be less of a concern when submitting samples to an on-premises Threat Grid Appliance than to the
Threat Grid Cloud, but understanding the basics of privacy and sample visibility is still necessary for TGA
administrators.
The privacy and sample visibility model for sample submissions to Threat Grid is relatively simple: Unless
samples are designated as Private, they will be visible to users who are outside the submitter's Organization. In
general, a sample designated as Private may only be seen by Threat Grid users within the same Organization as
the user who submitted the sample.
Privacy and Visibility on Threat Grid Appliances

The privacy and sample visibility model is modified on Threat Grid Appliances for samples that are submitted by
"CSA Integrations." CSA Integrations are Cisco products such as ESA/WSA appliances and other devices or
services, which are integrated (registered) with Threat Grid Appliances via the CSA API.
All sample submissions on Threat Grid Appliances are Public by default, and can be viewed by any other
appliance user, including CSA Integrations, regardless of which Organization they belong to.
All appliance users can see all details of samples submitted by all other users.
Non-CSA Threat Grid users may submit Private samples to the Threat Grid Appliance, in which case the
samples are only visible to other Threat Grid Appliance users, including CSA Integrations, within the submitter's
Organization.
Privacy and sample visibility model on Threat Grid Appliances illustrated in the table below, using the following
terms:
CSA Integrations CSA Integrations are ESA/WSA appliances and other Cisco devices or services that are
registered on a Threat Grid Appliance via the CSA API. Samples submitted to Threat Grid Appliances by CSA
Integrations are Public by default.
Threat Grid User - Public Public samples submitted to a Threat Grid Appliance by normal Threat Grid
users (i.e., non-CSA Integrations).
For example, appliance administrators or malware analysts who submit samples via the Threat Grid Portal UI, or
by using the Threat Grid Native API.
Threat Grid User - Private Private samples submitted to a Threat Grid Appliance by normal Threat Grid
users.
In this case, the Private samples are invisible to all other users on the appliance who are outside of the
submitter's Organization. (The samples will be visible to CSA Integrations within the same Organization as the
submitter.)
35
Figure 12 - Privacy and Visibility on a Threat Grid Appliance
The same basic privacy rules apply to Threat Grid Appliance integrations with FireAMP Private Cloud.
36
WIPE APPLIANCE
WIPE APPLIANCE
A new boot menu option is available with V1.4.4 that will allow you to wipe the disks on a Threat Grid Appliance.
Use the Wipe Appliance option to remove all data from the appliance prior to decommissioning or returning it to
the Cisco Demo Loan Program. Several variants of this process are available, some of which perform additional
passes to provide safety against attempts at data retrieval using advanced techniques. (Note these techniques
are believed to be ineffectual against modern hard drive encodings, so even the fastest single-pass Wipe option
is considered safe and sufficient.)
IMPORTANT: Note that after performing this operation, the appliance will no longer operate without being
returned to Cisco for reimaging.
1. Reboot your Appliance.
During the boot, there will be a 4-second window in which you can select Wipe Appliance:
Figure 13 - Wipe Appliance
2. This option requires the following username and password:
username: "wipe"
password: "I ACCEPT ALL RESPONSIBILITY FOR THIS ACTION"
37
WIPE APPLIANCE
3. Next, select a Wipe option. See Wipe Options for the approximate run times of each option.
Figure 14 - Wipe Options
4. The Wipe Finished screen is displayed when the wipe operation is complete:
38
WIPE APPLIANCE
Figure 15 - Wipe Finished
5. Press Enter to exit.
Wipe Options
Wipe Option Approximate Run

Time
Wipe (Fast: Zero Disks) 2.5 hours
Wipe (3-pass DOD method) 16 hours
Wipe (Random Overwrite) 12 hours
39
APPENDIX - OPADMIN MENUS

We offer the following screenshots to illustrate the various menu options that are available for performing
numerous tasks within OpAdmin:
Configuration Menu
Figure 16 - OpAdmin Configuration Menu
Note: If you need to make changes in the future to your OpAdmin configuration settings, you must access them
from the Configuration menu in order to be in edit mode.
40
Operations Menu
Figure 17 - OpAdmin Operations Menu
Note: Select Update Appliance to view the Release Notes.
41
Status Menu
Figure 18 - OpAdmin Status Menu
42
Support Menu
Figure 19 - OpAdmin Support Menu
You can access a live support session (Support Mode) from this menu; see the Support sections for details.
43

Amp Threat Grid Appliance Admin Guide 2 1 3

Uploaded by

Copyright:

Available Formats

Amp Threat Grid Appliance Admin Guide 2 1 3

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Amp Threat Grid Appliance Admin Guide 2 1 3

Uploaded by

Copyright:

Available Formats

Cisco AMP Threat Grid Appliance

Last Updated: 8/11/2016

Cisco Systems, Inc. www.cisco.com

Cisco AMP Threat Grid Appliance Administrator’s Guide

SSH Keys ............................................................................................................................................. 17

Figure 1 - Cisco Screen During Boot Up................................................................................. 4

Who This Guide Is For

Threat Grid Appliance Setup and Configuration Guide

Threat Grid Appliance Release Notes

Threat Grid Portal Release Notes

Threat Grid Portal Online Help and API Documentation

Threat Grid Portal user interface >Navigation bar > Help

The Help home page opens, with links to the documentation.

ESA/WSA Appliance Documentation

• The ESA user guides are located here:

• The WSA user guides are located here:

Configuration > License

For questions about licenses, please contact [email protected].

Figure 1 - Cisco Screen During Boot Up

Figure 2 - TGSH Dialog

Login Names and Passwords - Defaults

TGA Administrator - OpAdmin and threatgrid User

CIMC (Cisco Integrated Management Controller)

Lost Password Recovery

Resetting a Lost Administrator's Password

Figure 3 - Boot Menu - Recovery Mode

The Threat Grid Shell opens:

Figure 4 - The Threat Grid Shell in Recovery Mode

2. Run passwd to change the password:

Figure 5 - Enter a New Password

To test the update, submit a sample for analysis.

1. From the Operations menu, select Update Appliance.

Figure 6 - Appliance Version Number

Note: The download can take some time:

• Updating from 1.0 to 1.0+hotfix2 takes approximately15 minutes.

Appliance Build Number/Version Lookup Table

Appliance build numbers correspond to the following release version numbers:

Build Number Release Version Release Date Notes

2016.05.20160811044721.6af0fa61.rel 2.1.3 8/11/2016 Offline

2016.05.20160715165510.baed88a3.rel 2.1.2 7/15/2016

2016.05.20160706015125.b1fc50e5.rel-1 2.1.1 7/6/2016

2016.05.20160621044600.092b23fc 2.1 6/21/2016

2015.08.20160501161850.56631ccd 2.0.4 5/1/2016 Starting point

2015.08.20160315165529.599f2056 2.0.3 3/15/2016 Introduces

2015.08.20160217173404.ec264f73 2.0.2 2/18/2016

2015.08.20160211192648.7e3d2e3a 2.0.1 2/12/2016

2015.08.20160131061029.8b6bc1d6 2.0 2/11/2016 Force update

2014.10.20160115122111.1f09cb5f 1.4.6 1/27/2016 Starting point

2014.10.20151123133427.898f70c2 v1.4.5 11/25/2015

Build Number Release Version Release Date Notes

Support - Contacting Threat Grid

• Email. Send email to [email protected] with your query.

• Call. See: http://www.cisco.com/c/en/us/support/index.html

• Appliance version: OpAdmin > Operations > Update Appliance)

• Full service status (service status from the shell)

• Network diagram or description (if applicable)

• Support Mode (Shell or Web interface)

• Support Request Details

To start a live support session with Threat Grid tech support:

Figure 7 - OpAdmin Start a Live Support Session