P. 1
Sourcefire_3D_System_Administrator_Guide_v4.9.1

Sourcefire_3D_System_Administrator_Guide_v4.9.1

|Views: 8,852|Likes:

More info:

Published by: dominic_murphy19791242 on Feb 15, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

05/16/2013

pdf

text

original

Sections

  • Components of the Sourcefire 3D System
  • •Real-time Network Awareness (RNA) on page15
  • Real-time Network Awareness (RNA)
  • Intrusion Prevention System (IPS)
  • Real-time User Awareness (RUA)
  • PEP Traffic Management
  • Defense Centers
  • Master Defense Centers
  • Intrusion Agents
  • RNA for Red Hat Linux
  • RNA and IPS for Crossbeam Systems
  • eStreamer
  • Logging into the Appliance
  • Logging into the Appliance to Set Up an Account
  • Logging Out of the Appliance
  • Last Successful Login
  • Specifying Your User Preferences
  • Changing Your Password
  • Changing an Expired Password
  • Configuring Event View Settings
  • Setting Your Default Time Zone
  • Specifying Your Home Page
  • To specify your home page:
  • Specifying Your Default Dashboard
  • To specify your default dashboard:
  • Using the Context Menu
  • Documentation Resources
  • Documentation Conventions
  • Platform Requirements Conventions
  • Access Requirements Conventions
  • IP Address Conventions
  • Setting Up 3DSensors
  • Setting up Defense Centers
  • Communication Ports
  • What’s Next?
  • Administrator User Tasks
  • Maintenance User Tasks
  • Policy & Response Administrator User Tasks
  • RNA Event Analyst User Tasks
  • Intrusion Event Analyst User Tasks
  • •Understanding Dashboard Widgets on page60
  • Understanding Dashboard Widgets
  • •Understanding Widget Availability on page61
  • Understanding Widget Availability
  • Sourcefire Appliances and Dashboard Widget Availability
  • Understanding Widget Preferences
  • Understanding the Predefined Widgets
  • Understanding the Appliance Information Widget
  • Understanding the Appliance Status Widget
  • Understanding the Compliance Events Widget
  • Understanding the Current Interface Status Widget
  • Understanding the Current Sessions Widget
  • Understanding the Custom Analysis Widget
  • •Configuring the Custom Analysis Widget on page72
  • Configuring the Custom Analysis Widget
  • Viewing Associated Events from the Custom Analysis Widget
  • Understanding the Disk Usage Widget
  • Understanding the Interface Traffic Widget
  • Understanding the Intrusion Events Widget
  • Understanding the Network Compliance Widget
  • Understanding the Product Licensing Widget
  • Understanding the Product Updates Widget
  • Understanding the RSS Feed Widget
  • Understanding the System Load Widget
  • Understanding the System Time Widget
  • Understanding the White List Events Widget
  • Working with Dashboards
  • •Creating a Custom Dashboard on page89
  • Creating a Custom Dashboard
  • Viewing Dashboards
  • Modifying Dashboards
  • •Changing Dashboard Properties on page93
  • Deleting a Dashboard
  • Using the Defense Center
  • Management Concepts
  • •The Benefits of Managing Your Sensors on page100
  • The Benefits of Managing Your Sensors
  • What Can Be Managed by a Defense Center?
  • Understanding Software Sensors
  • Managing 3DSensor Software with RNA for Crossbeam
  • Managing 3DSensor Software with IPS for Crossbeam
  • Beyond Policies and Events
  • Using Redundant Defense Centers
  • Working in NAT Environments
  • Working with Sensors
  • Understanding the Sensors Page
  • Adding Sensors to the Defense Center
  • Deleting Sensors
  • Resetting Management of a Sensor
  • Managing a 3Dx800 Sensor
  • •Managing 3Dx800 Sensors with a Defense Center on page125
  • Managing 3Dx800 Sensors with a Defense Center
  • Deleting a 3Dx800 Sensor from the Defense Center
  • Resetting Communications on the 3Dx800
  • Adding Intrusion Agents
  • Sensor Attributes - Intrusion Agent Page
  • Managing Sensor Groups
  • Creating Sensor Groups
  • Editing Sensor Groups
  • Deleting Sensor Groups
  • Editing a Managed Sensor’s System Settings
  • Viewing a Sensor’s Information Page
  • Stopping and Restarting a Managed Sensor
  • Managing Communication on a Managed Sensor
  • Setting the Time on a Managed Sensor
  • Managing a Clustered Pair
  • •Establishing a Clustered Pair on page142
  • Establishing a Clustered Pair
  • Separating a Clustered Pair
  • Configuring High Availability
  • Using High Availability
  • Sensor Configurations and User Information
  • Understanding High Availability
  • Guidelines for Implementing High Availability
  • Setting Up High Availability
  • Monitoring the High Availability Status
  • Disabling High Availability and Unregistering Sensors
  • Pausing Communication between Paired Defense Centers
  • Restarting Communication between Paired Defense Centers
  • Understanding Event Aggregation
  • Aggregating Intrusion Events
  • Aggregating Compliance Events
  • Limitations on Event Aggregation
  • Master Defense Center and Defense Center Functional Comparison
  • Understanding Global Policy Management
  • Managing Global Intrusion Policies
  • Using RNA Detection Policies on a Master Defense Center
  • Using Health Policies on a Master Defense Center
  • Using System Policies on a Master Defense Center
  • Master Defense Center Policy Management Limitations
  • Adding and Deleting Defense Centers
  • Adding a Master Defense Center
  • Adding a Defense Center
  • Deleting a Defense Center
  • Resetting Management of a Defense Center
  • Using the Appliances Page
  • Editing Settings for a Managed Defense Center
  • •Viewing the Defense Center Information Page on page175
  • Viewing the Defense Center Information Page
  • Defense Center Information
  • Editing the Event Filter Configuration
  • Editing or Disabling Remote Management Communications
  • Managing the Health Blacklist
  • Managing High Availability Defense Centers
  • Managing Appliance Groups
  • Creating Appliance Groups
  • Editing Appliance Groups
  • Deleting Appliance Groups
  • Editing Master Defense Center System Settings
  • Listing Master Defense Center Information
  • Viewing a Master Defense Center License
  • Configuring Remote Management Networking
  • Setting System Time
  • Blacklisting Health Policies
  • Understanding Detection Engines
  • Understanding Detection Resources and 3DSensor Models
  • Understanding Default Detection Engines
  • Managing Detection Engines
  • •Creating a Detection Engine on page193
  • •Editing a Detection Engine on page194
  • Creating a Detection Engine
  • To create a detection engine:
  • Editing a Detection Engine
  • Deleting a Detection Engine
  • To delete a detection engine:
  • Using Detection Engine Groups
  • •Creating Detection Engine Groups on page197
  • •Editing Detection Engine Groups on page198
  • Creating Detection Engine Groups
  • Editing Detection Engine Groups
  • To edit a detection engine group:
  • Deleting Detection Engine Groups
  • To delete a detection engine group:
  • Using Variables within Detection Engines
  • Assigning Values to System Default Variables in Detection Engines
  • Creating New Variables for Detection Engines
  • Deleting and Resetting Variables
  • Configuring Custom Variables in Detection Engines
  • Using Portscan-Only Detection Engines
  • Using Interface Sets
  • •Understanding Interface Set Configuration Options on page207
  • Understanding Interface Set Configuration Options
  • Creating an Interface Set
  • Creating an Inline Interface Set
  • Editing an Interface Set
  • Deleting an Interface Set
  • Using Interface Set Groups
  • •Creating Interface Set Groups on page224
  • Creating Interface Set Groups
  • Editing Interface Set Groups
  • Deleting Interface Set Groups
  • Inline Fail Open Interface Set Commands
  • Removing Bypass Mode on Inline Fail Open Fiber Interfaces
  • Forcing an Inline Fail Open Interface Set into Bypass Mode
  • To force an inline fail open interface set into bypass mode:
  • Using Clustered 3DSensors
  • •Using Detection Engines on Clustered 3DSensors on page228
  • Using Detection Engines on Clustered 3DSensors
  • •Managing Clustered 3DSensor Detection Engines on page228
  • Managing Clustered 3DSensor Detection Engines
  • Using Clustered 3DSensor Detection Engines in Policies
  • Understanding Interface Sets on Clustered 3DSensors
  • Managing Information from a Clustered 3DSensor
  • •Working with Event Reports on page234
  • •Working with Report Profiles on page234
  • Working with Report Profiles
  • Generating Reports from Event Views
  • Managing Generated Reports
  • •Viewing Generated Reports on page238
  • •Downloading Generated Reports on page238
  • Viewing Generated Reports
  • Downloading Generated Reports
  • To download generated reports:
  • Deleting Generated Reports
  • Moving Reports to a Remote Storage Location
  • Running Remote Reports
  • Understanding Report Profiles
  • Understanding the Predefined Report Profiles
  • Modifying a Predefined Report Profile
  • Creating a Report Profile
  • Working with Report Information
  • Report Categories
  • •Using Report Types on page250
  • Using Report Types
  • IPS Category Report Types
  • RNA Category Report Types
  • Defining Report Information
  • Working with Report Sections
  • •Using Summary Reports on page255
  • Using Summary Reports
  • Comparison of Quick Summary and Detail Summary Reports
  • Including an Image File
  • Defining the Report Sections
  • To define the Report Sections:
  • Working with Report Options
  • Using a Report Profile
  • •Generating a Report using a Report Profile on page261
  • Generating a Report using a Report Profile
  • Editing Report Profiles
  • Deleting Report Profiles
  • •Understanding Sourcefire User Authentication on page264
  • Understanding Sourcefire User Authentication
  • •Understanding Internal Authentication on page266
  • •Understanding External Authentication on page266
  • Understanding Internal Authentication
  • Understanding External Authentication
  • Understanding User Privileges
  • Managing Authentication Objects
  • •Understanding LDAP Authentication on page269
  • •Creating LDAP Authentication Objects on page269
  • •Editing LDAP Authentication Objects on page286
  • Understanding LDAP Authentication
  • Creating LDAP Authentication Objects
  • Configuring LDAP Authentication Settings
  • Configuring Attribute Mapping
  • Configuring Access Settings by Group
  • Testing User Authentication
  • To test user authentication:
  • LDAP Authentication Object Examples
  • •OpenLDAP Example on page281
  • Microsoft Active Directory Server Example
  • Editing LDAP Authentication Objects
  • Understanding RADIUS Authentication
  • Creating RADIUS Authentication Objects
  • Configuring RADIUS Connection Settings
  • Configuring RADIUS User Roles
  • Configuring Administrative Shell Access
  • RADIUS Authentication Object Examples
  • •Authenticating a User using RADIUS on page295
  • Editing RADIUS Authentication Objects
  • •Creating RADIUS Authentication Objects on page287
  • Deleting Authentication Objects
  • Managing User Accounts
  • Viewing User Accounts
  • •Adding New User Accounts on page300
  • Adding New User Accounts
  • Managing Externally Authenticated User Accounts
  • Managing User Password Settings
  • Configuring User Roles
  • Modifying User Privileges and Options
  • Modifying Restricted Event Analyst Access Properties
  • Modifying User Passwords
  • Deleting User Accounts
  • User Account Privileges
  • •Creating a System Policy on page321
  • •Editing a System Policy on page323
  • Creating a System Policy
  • Editing a System Policy
  • Applying a System Policy
  • To apply a system policy:
  • Deleting System Policies
  • Configuring the Parts of Your System Policy
  • •Configuring the Access List for Your Appliance on page325
  • Configuring the Access List for Your Appliance
  • Configuring Audit Log Settings
  • Configuring Authentication Profiles
  • Configuring Dashboard Settings
  • Configuring Database Event Limits
  • Configuring Detection Policy Preferences
  • To configure detection policy preferences:
  • Configuring DNS Cache Properties
  • Configuring a Mail Relay Host and Notification Address
  • Configuring Intrusion Policy Preferences
  • Specifying a Different Language
  • Adding a Custom Login Banner
  • Configuring RNA Settings
  • •Understanding RNA Data Storage Settings on page342
  • Understanding Vulnerability Impact Assessment Settings
  • Configuring RNA Subnet Detection Settings
  • Configuring RUA Settings
  • Synchronizing Time
  • Serving Time from the Defense Center
  • Mapping Vulnerabilities for Services
  • System Settings Options
  • Viewing and Modifying the Appliance Information
  • Understanding Licenses
  • Understanding Feature Licenses
  • Verifying Your Product License
  • Managing Your Feature Licenses
  • •Adding Feature Licenses on page370
  • •Viewing Feature Licenses on page372
  • NetFlow License Columns
  • RNA Host License Columns
  • Intrusion Agent License Columns
  • Virtual 3DSensor License Columns
  • Configuring Network Settings
  • Editing Network Interface Configurations
  • Shutting Down and Restarting the System
  • Configuring the Communication Channel
  • •Setting Up the Management Virtual Network on page384
  • Setting Up the Management Virtual Network
  • Editing the Management Virtual Network
  • Configuring Remote Access to the Defense Center
  • Setting the Time Manually
  • Blacklisting Health Modules
  • Specifying NetFlow-Enabled Devices
  • Managing Remote Storage
  • Using Local Storage
  • Using NFS for Remote Storage
  • Using SSH for Remote Storage
  • Using SMB for Remote Storage
  • Updating System Software
  • Installing Software Updates
  • Updating a Defense Center or Master Defense Center
  • Updating Managed Sensors
  • Updating Unmanaged 3DSensors
  • Uninstalling Software Updates
  • Updating the Vulnerability Database
  • Using Backup and Restore
  • Creating Backup Files
  • Creating Backup Profiles
  • Performing Sensor Backup with the Defense Center
  • Uploading Backups from a Local Host
  • Restoring the Appliance from a Backup File
  • Configuring a Recurring Task
  • •Automating Backup Jobs on page428
  • Automating Backup Jobs
  • Automating Software Updates
  • •Automating Software Downloads on page431
  • Automating Software Downloads
  • Automating Software Pushes
  • Automating Software Installs
  • Automating Vulnerability Database Updates
  • •Automating VDB Update Downloads on page438
  • Automating VDB Update Downloads
  • Automating VDB Update Pushes
  • Automating VDB Update Installs
  • Automating SEU Imports
  • Automating Intrusion Policy Applications
  • Automating Reports
  • Automating Nessus Scans
  • •Preparing Your System to Run a Nessus Scan on page450
  • Preparing Your System to Run a Nessus Scan
  • Scheduling a Nessus Scan
  • Synchronizing Nessus Plugins
  • Automating Nmap Scans
  • •Preparing Your System for an Nmap Scan
  • Preparing Your System for an Nmap Scan
  • Scheduling an Nmap Scan
  • Automating Recommended Rule State Generation
  • Viewing Tasks
  • •Using the Calendar on page459
  • Using the Calendar
  • Using the Task List
  • Editing Scheduled Tasks
  • Deleting Scheduled Tasks
  • Deleting a Recurring Task
  • Deleting a One-Time Task
  • Viewing Host Statistics
  • Data Correlator Process Statistics
  • Intrusion Event Information
  • Monitoring System Status and Disk Space Usage
  • Viewing System Process Status
  • Understanding Running Processes
  • •Understanding System Daemons on page471
  • Understanding System Daemons
  • Understanding Executables and System Utilities
  • System Executables and Utilities
  • Viewing IPS Performance Statistics
  • •Generating IPS Performance Statistics Graphs on page476
  • Generating IPS Performance Statistics Graphs
  • IPS Performance Statistics Graph Types
  • Saving IPS Performance Statistics Graphs
  • Viewing RNA Performance Statistics
  • •Generating RNA Performance Statistics Graphs on page479
  • Generating RNA Performance Statistics Graphs
  • RNA Performance Statistics Graph Types
  • Saving RNA Performance Statistics Graphs
  • Understanding Health Monitoring
  • •Understanding Health Policies on page484
  • Understanding Health Policies
  • Understanding Health Modules
  • Understanding Health Monitoring Configuration
  • Configuring Health Policies
  • •Predefined Health Policies on page490
  • Predefined Health Policies
  • Default Health Policy
  • Enabled Defense Center Health Modules - Default Health Policy
  • Enabled MDC Health Modules - Default Health Policy
  • Default Intrusion Sensor Health Policy
  • Default IPS (3Dx800 only) Health Policy
  • Enabled Health Modules: Default Intrusion Sensor Health Policy
  • Creating Health Policies
  • Enabled Health Modules: Default RNA Sensor Health Policy
  • Configuring Appliance Heartbeat Monitoring
  • Configuring Automatic Application Bypass Monitoring
  • Configuring Data Correlator Process Monitoring
  • Configuring Health Status Monitoring
  • Configuring Link State Propagation Monitoring
  • Configuring Time Synchronization Monitoring
  • Applying Health Policies
  • Editing Health Policies
  • Deleting Health Policies
  • Using the Health Monitor Blacklist
  • Blacklisting Health Policies or Appliances
  • Blacklisting a Health Policy Module
  • Configuring Health Monitor Alerts
  • •Preparing to Create a Health Alert on page540
  • •Creating Health Monitor Alerts on page540
  • •Editing Health Monitor Alerts on page543
  • Preparing to Create a Health Alert
  • Continue with Creating Health Monitor Alerts on page540
  • Creating Health Monitor Alerts
  • Interpreting Health Monitor Alerts
  • Editing Health Monitor Alerts
  • To edit health monitor alerts:
  • Deleting Health Monitor Alerts
  • To delete health monitor alerts:
  • •Using the Health Monitor on page545
  • Using the Health Monitor
  • Interpreting Health Monitor Status
  • Using Appliance Health Monitors
  • Health Status Indicator
  • Interpreting Appliance Health Monitor Status
  • Viewing Alerts by Status
  • Running All Modules for an Appliance
  • Running a Specific Health Module
  • Generating Health Module Alert Graphs
  • To generate a health module alert graph:
  • Generating Appliance Troubleshooting Files
  • To generate appliance troubleshooting files:
  • Working with Health Events
  • Understanding Health Event Views
  • •Viewing Health Events on page556
  • Viewing Health Events
  • •Viewing All Health Events on page556
  • Viewing Health Events by Module and Appliance
  • Interpreting Hardware Alert Details for 3D9900 Sensors
  • Understanding the Health Events Table
  • Health Event Fields
  • Searching for Health Events
  • Health Event Search Criteria
  • Managing Audit Records
  • •Viewing Audit Records on page567
  • Viewing Audit Records
  • Suppressing Audit Records
  • Understanding the Audit Log Table
  • Searching Audit Records
  • Audit Record Search Criteria
  • Viewing the System Log
  • Filtering System Log Messages
  • System Log Filter Syntax
  • Using Four-Digit Year Formats on the 3D3800
  • System Log Filter Examples
  • •Exporting Objects on page584
  • Exporting Objects
  • •Exporting a Custom Table on page584
  • Exporting a Custom Table
  • Exporting a Custom Workflow
  • To export a custom workflow:
  • Exporting a Dashboard
  • Exporting a Health Policy
  • To export a health policy:
  • Exporting an Intrusion Policy
  • Exporting a PEP Policy
  • Exporting an RNA Detection Policy
  • To export an RNA detection policy:
  • Exporting a System Policy
  • Exporting a User-Defined RNA Detector
  • To export a user-defined RNA detector:
  • Exporting Multiple Objects
  • Importing Objects
  • Viewing the Status of Long-Running Tasks
  • •Viewing the Task Queue on page600
  • Viewing the Task Queue
  • Managing the Task Queue
  • Glossary
  • Policy & Response Administrator
  • RADIUS authentication
  • Restricted Event Analyst
  • RNA recommended rules
  • Index

Sourcefire 3D System Administrator Guide

Version 4.9.1

Intellectual Property Notices, Disclaimers, and Terms of Use Applicable to the User Documentation. The legal notices, disclaimers, terms of use, and other information contained herein (the “terms”) apply only to Sourcefire, Inc. appliance discussed in the Documentation (“Documentation”) and your use of it. The terms do not apply to or govern the use of Sourcefire's web site or Sourcefire's appliance discussed in the Documentation. Sourcefire appliances are available for purchase and subject to a separate license containing very different terms of use. Terms Of Use and Copyright and Trademark Notices The copyright in the Documentation is owned by Sourcefire, Inc., and is protected by copyright pursuant to US copyright law, international conventions, and other laws. You may use, print out, save on a retrieval system, and otherwise copy and distribute the documentation solely for non-commercial use, provided that (i) you do not modify the documentation in any way and (ii) you always include Sourcefire's copyright, trademark, and other notices, as well as a link to, or print out of, the full contents of this page and its terms. No part of the documentation may be used in a compilation or otherwise incorporated into another work, or be used to create derivative works, without the express prior written permission of Sourcefire, Inc. Sourcefire, Inc. reserves the right to change the Terms at any time, and your continued use of the Documentation shall be deemed an acceptance of those terms. Sourcefire, the Sourcefire logo, Snort, the Snort logo, 3D Sensor, Intrusion Sensor, Intrusion Agent, Realtime Network Awareness, RNA Sensor, Defense Center, Master Defense Center, Success Pack, and 3D System, are trademarks or registered trademarks of Sourcefire, Inc. All other trademarks are property of their respective owners. © 2004 - 2010 Sourcefire, Inc. All rights reserved. Liability Disclaimers THE DOCUMENTATION AND ANY INFORMATION AVAILABLE FROM IT MAY INCLUDE INACCURACIES OR TYPOGRAPHICAL ERRORS. SOURCEFIRE, INC. MAY CHANGE THE DOCUMENTATION FROM THE TIME TO TIME. SOURCEFIRE, INC. MAKES NO REPRESENTATIONS OR WARRANTIES ABOUT THE ACCURACY OR SUITABILITY OF THE SOURCEFIRE, INC. WEB SITE, THE DOCUMENTATION, AND/OR ANY APPLIANCE OR INFORMATION. SOURCEFIRE, INC. PROVIDES THE SOURCEFIRE, INC. WEB SITE, THE DOCUMENTATION, AND ANY APPLIANCE OR INFORMATION “AS IS” AND SOURCEFIRE, INC. DISCLAIMS ANY AND ALL EXPRESS OR IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO WARRANTIES OF TITLE OR THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SOURCEFIRE, INC. BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES (INCLUDING BUT NOT LIMITED TO PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, LOSS OF DATA, LOSS OF PROFITS, AND/OR BUSINESS INTERRUPTIONS), ARISING OUT OF OR IN ANY WAY RELATED TO THE SOURCEFIRE, INC. WEB SITE, THE DOCUMENTATION, AND/OR ANY SOFTWARE OR INFORMATION, NO MATTER HOW CAUSED AND/OR WHETHER BASED ON CONTRACT, STRICT LIABILITY, NEGLIGENCE OR OTHER TORTUOUS ACTIVITY, OR ANY OTHER THEORY OF LIABILITY, EVEN IF SOURCEFIRE, INC. IS ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BECAUSE SOME STATES/JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU. The Documentation may contain “links” to sites on the Internet that are not created by, or under the control of Sourcefire, Inc. Sourcefire, Inc. provides such links solely for your convenience, and assumes no responsibility for the availability or content of such other sites. 2010-Jul-12 13:56

Table of Contents

Chapter 1:

Introduction to the Sourcefire 3D System............................. 14
Components of the Sourcefire 3D System......................................................... Real-time Network Awareness (RNA).................................................... Intrusion Prevention System (IPS) ......................................................... Real-time User Awareness (RUA) .......................................................... PEP Traffic Management ....................................................................... Defense Centers.................................................................................... Master Defense Centers ....................................................................... Intrusion Agents..................................................................................... RNA for Red Hat Linux........................................................................... RNA and IPS for Crossbeam Systems................................................... eStreamer .............................................................................................. 15 15 16 17 17 17 19 19 20 20 20

Logging into the Appliance ................................................................................. 21 Logging into the Appliance to Set Up an Account .............................................. 23 Logging Out of the Appliance ............................................................................. 24 Last Successful Login......................................................................................... 25 Specifying Your User Preferences ...................................................................... Changing Your Password ....................................................................... Configuring Event View Settings ........................................................... Setting Your Default Time Zone ............................................................. Specifying Your Home Page................................................................... Specifying Your Default Dashboard........................................................ 25 25 27 34 35 35

Using the Context Menu .................................................................................... 36 Documentation Resources ................................................................................. 37

Version 4.9.1

Sourcefire 3D System Administrator Guide

3

Table of Contents

Documentation Conventions .............................................................................. 38 Platform Requirements Conventions ..................................................... 38 Access Requirements Conventions ....................................................... 39 IP Address Conventions...................................................................................... 41

Chapter 2:

Performing the Initial Setup .................................................... 43
Setting Up 3D Sensors ....................................................................................... 44 Setting up Defense Centers ............................................................................... 47 Communication Ports ......................................................................................... 50 What’s Next? ...................................................................................................... Administrator User Tasks....................................................................... Maintenance User Tasks........................................................................ Policy & Response Administrator User Tasks ........................................ RNA Event Analyst User Tasks .............................................................. Intrusion Event Analyst User Tasks........................................................ 52 53 54 55 56 57

Chapter 3:

Using Dashboards..................................................................... 59
Understanding Dashboard Widgets.................................................................... 60 Understanding Widget Availability ......................................................... 61 Understanding Widget Preferences ...................................................... 64 Understanding the Predefined Widgets ............................................................. Understanding the Appliance Information Widget................................. Understanding the Appliance Status Widget......................................... Understanding the Compliance Events Widget..................................... Understanding the Current Interface Status Widget ............................. Understanding the Current Sessions Widget ........................................ Understanding the Custom Analysis Widget......................................... Understanding the Disk Usage Widget ................................................. Understanding the Interface Traffic Widget ........................................... Understanding the Intrusion Events Widget.......................................... Understanding the Network Compliance Widget .................................. Understanding the Product Licensing Widget ....................................... Understanding the Product Updates Widget......................................... Understanding the RSS Feed Widget .................................................... Understanding the System Load Widget............................................... Understanding the System Time Widget .............................................. Understanding the White List Events Widget ....................................... Working with Dashboards .................................................................................. Creating a Custom Dashboard............................................................... Viewing Dashboards .............................................................................. Modifying Dashboards........................................................................... Deleting a Dashboard ............................................................................ 65 66 67 67 68 69 69 80 81 81 82 84 85 86 87 87 88 89 89 91 93 97

Version 4.9.1

Sourcefire 3D System Administrator Guide

4

Table of Contents

Chapter 4:

Using the Defense Center........................................................ 99
Management Concepts .................................................................................... 100 The Benefits of Managing Your Sensors.............................................. 100 What Can Be Managed by a Defense Center? .................................... 101 Understanding Software Sensors ........................................................ 105 Beyond Policies and Events .................................................................. 111 Using Redundant Defense Centers ..................................................... 112 Working in NAT Environments.......................................................................... 112 Working with Sensors ...................................................................................... 113 Understanding the Sensors Page ........................................................ 115 Adding Sensors to the Defense Center ................................................ 117 Deleting Sensors ................................................................................. 121 Resetting Management of a Sensor .................................................... 122 Managing a 3Dx800 Sensor................................................................. 125 Adding Intrusion Agents ...................................................................... 130 Sensor Attributes - Intrusion Agent Page............................................. 130 Managing Sensor Groups ................................................................................. Creating Sensor Groups....................................................................... Editing Sensor Groups ......................................................................... Deleting Sensor Groups....................................................................... Editing a Managed Sensor’s System Settings .................................................. Viewing a Sensor’s Information Page .................................................. Stopping and Restarting a Managed Sensor ....................................... Managing Communication on a Managed Sensor............................... Setting the Time on a Managed Sensor .............................................. 131 131 132 133 133 135 137 138 139

Managing a Clustered Pair ................................................................................ 140 Establishing a Clustered Pair ............................................................... 142 Separating a Clustered Pair.................................................................. 144 Configuring High Availability ............................................................................. Using High Availability.......................................................................... Guidelines for Implementing High Availability ..................................... Setting Up High Availability .................................................................. Monitoring the High Availability Status ................................................ Disabling High Availability and Unregistering Sensors......................... Pausing Communication between Paired Defense Centers ................ Restarting Communication between Paired Defense Centers ............ 145 145 149 150 152 153 154 154

Chapter 5:

Using the Master Defense Center........................................ 156
Understanding Event Aggregation.................................................................... Aggregating Intrusion Events............................................................... Aggregating Compliance Events.......................................................... Limitations on Event Aggregation........................................................ 157 158 158 159

Version 4.9.1

Sourcefire 3D System Administrator Guide

5

Table of Contents

Understanding Global Policy Management....................................................... Managing Global Intrusion Policies ...................................................... Using RNA Detection Policies on a Master Defense Center ............... Using Health Policies on a Master Defense Center............................. Using System Policies on a Master Defense Center ........................... Master Defense Center Policy Management Limitations .................... Adding and Deleting Defense Centers ............................................................. Adding a Master Defense Center ........................................................ Adding a Defense Center..................................................................... Deleting a Defense Center .................................................................. Resetting Management of a Defense Center ...................................... Editing Settings for a Managed Defense Center .............................................. Viewing the Defense Center Information Page ................................... Editing the Event Filter Configuration .................................................. Editing or Disabling Remote Management Communications .............. Managing the Health Blacklist ............................................................. Managing High Availability Defense Centers ....................................... Managing Appliance Groups............................................................................. Creating Appliance Groups .................................................................. Editing Appliance Groups..................................................................... Deleting Appliance Groups .................................................................. Editing Master Defense Center System Settings ............................................. Listing Master Defense Center Information ........................................ Viewing a Master Defense Center License ......................................... Configuring Network Settings.............................................................. Shutting Down and Restarting the System.......................................... Configuring Remote Management Networking................................... Setting System Time............................................................................ Blacklisting Health Policies...................................................................

161 161 162 162 162 163 164 165 168 171 171 175 175 176 178 178 178 179 180 180 181 181 182 182 182 182 183 183 184

Using the Appliances Page ............................................................................... 173

Chapter 6:

Using Detection Engines and Interface Sets...................... 185
Understanding Detection Engines .................................................................... 186 Understanding Detection Resources and 3D Sensor Models ............. 189 Understanding Default Detection Engines .......................................... 191 Managing Detection Engines............................................................................ Creating a Detection Engine ................................................................ Editing a Detection Engine .................................................................. Deleting a Detection Engine ................................................................ Using Detection Engine Groups ....................................................................... Creating Detection Engine Groups ...................................................... Editing Detection Engine Groups......................................................... Deleting Detection Engine Groups ...................................................... 193 193 194 197 197 197 198 199

Version 4.9.1

Sourcefire 3D System Administrator Guide

6

Table of Contents

Using Variables within Detection Engines ........................................................ Assigning Values to System Default Variables in Detection Engines... Creating New Variables for Detection Engines .................................... Deleting and Resetting Variables ......................................................... Configuring Custom Variables in Detection Engines ........................... Using Portscan-Only Detection Engines .............................................. Using Interface Sets ......................................................................................... Understanding Interface Set Configuration Options............................ Creating an Interface Set ..................................................................... Creating an Inline Interface Set ........................................................... Editing an Interface Set ....................................................................... Deleting an Interface Set ..................................................................... Using Interface Set Groups .............................................................................. Creating Interface Set Groups ............................................................. Editing Interface Set Groups................................................................ Deleting Interface Set Groups .............................................................

199 200 202 203 204 205 207 207 213 216 221 223 223 224 224 225

Inline Fail Open Interface Set Commands ........................................................ 225 Removing Bypass Mode on Inline Fail Open Fiber Interfaces ............. 225 Forcing an Inline Fail Open Interface Set into Bypass Mode ............... 226 Using Clustered 3D Sensors............................................................................. Using Detection Engines on Clustered 3D Sensors ............................ Understanding Interface Sets on Clustered 3D Sensors ..................... Managing Information from a Clustered 3D Sensor ............................ 227 228 229 230

Chapter 7:

Working with Event Reports.................................................. 232
Working with Event Reports............................................................................. 234 Working with Report Profiles............................................................................ 234 Generating Reports from Event Views ............................................................. 235 Managing Generated Reports........................................................................... Viewing Generated Reports................................................................. Downloading Generated Reports......................................................... Deleting Generated Reports ................................................................ Moving Reports to a Remote Storage Location................................... Running Remote Reports .................................................................... Understanding Report Profiles.......................................................................... Understanding the Predefined Report Profiles .................................... Modifying a Predefined Report Profile................................................. Creating a Report Profile...................................................................... 237 238 238 239 239 240 241 242 246 246

Working with Report Information ..................................................................... 248 Using Report Types.............................................................................. 250 Defining Report Information ................................................................ 254

Version 4.9.1

Sourcefire 3D System Administrator Guide

7

Table of Contents

Working with Report Sections .......................................................................... Using Summary Reports...................................................................... Including an Image File ........................................................................ Defining the Report Sections............................................................... Using a Report Profile ....................................................................................... Generating a Report using a Report Profile ......................................... Editing Report Profiles ......................................................................... Deleting Report Profiles.......................................................................

255 255 257 258 260 261 263 263

Working with Report Options ........................................................................... 258

Chapter 8:

Managing Users ...................................................................... 264
Understanding Sourcefire User Authentication ................................................ Understanding Internal Authentication ................................................ Understanding External Authentication ............................................... Understanding User Privileges ............................................................ Managing Authentication Objects .................................................................... Understanding LDAP Authentication ................................................... Creating LDAP Authentication Objects ................................................ LDAP Authentication Object Examples ............................................... Editing LDAP Authentication Objects .................................................. Understanding RADIUS Authentication ............................................... Creating RADIUS Authentication Objects............................................ RADIUS Authentication Object Examples ........................................... Editing RADIUS Authentication Objects .............................................. Deleting Authentication Objects .......................................................... Managing User Accounts ................................................................................. Viewing User Accounts........................................................................ Adding New User Accounts................................................................. Managing Externally Authenticated User Accounts............................. Managing User Password Settings...................................................... Configuring User Roles........................................................................ Modifying User Privileges and Options ............................................... Modifying Restricted Event Analyst Access Properties....................... Modifying User Passwords.................................................................. Deleting User Accounts ....................................................................... User Account Privileges....................................................................... 264 266 266 267 269 269 269 281 286 287 287 295 298 298 299 299 300 302 303 304 306 307 311 312 312

Chapter 9:

Managing System Policies .................................................... 320
Creating a System Policy .................................................................................. 321 Editing a System Policy..................................................................................... 323 Applying a System Policy .................................................................................. 324 Deleting System Policies .................................................................................. 325

Version 4.9.1

Sourcefire 3D System Administrator Guide

8

Table of Contents

Configuring the Parts of Your System Policy..................................................... Configuring the Access List for Your Appliance ................................... Configuring Audit Log Settings ............................................................ Configuring Authentication Profiles ..................................................... Configuring Dashboard Settings .......................................................... Configuring Database Event Limits ..................................................... Configuring Detection Policy Preferences ........................................... Configuring DNS Cache Properties...................................................... Configuring a Mail Relay Host and Notification Address ..................... Configuring Intrusion Policy Preferences ............................................. Specifying a Different Language .......................................................... Adding a Custom Login Banner ........................................................... Configuring RNA Settings .................................................................... Configuring RNA Subnet Detection Settings ....................................... Configuring RUA Settings .................................................................... Synchronizing Time .............................................................................. Mapping Vulnerabilities for Services....................................................

325 325 327 329 331 332 336 337 338 339 340 341 342 349 352 354 358

Chapter 10:

Configuring System Settings ................................................. 360
Viewing and Modifying the Appliance Information ........................................... 362 Understanding Licenses ................................................................................... Understanding Feature Licenses ......................................................... Verifying Your Product License ............................................................ Managing Your Feature Licenses ......................................................... 364 366 368 370

Configuring Network Settings........................................................................... 377 Editing Network Interface Configurations......................................................... 380 Shutting Down and Restarting the System....................................................... 382 Configuring the Communication Channel ......................................................... 383 Setting Up the Management Virtual Network...................................... 384 Editing the Management Virtual Network............................................ 385 Configuring Remote Access to the Defense Center ........................................ 386 Setting the Time Manually ................................................................................ 389 Blacklisting Health Modules.............................................................................. 391 Specifying NetFlow-Enabled Devices ............................................................... 392 Managing Remote Storage............................................................................... Using Local Storage ............................................................................. Using NFS for Remote Storage ........................................................... Using SSH for Remote Storage ........................................................... Using SMB for Remote Storage .......................................................... 393 393 394 395 396

Version 4.9.1

Sourcefire 3D System Administrator Guide

9

Table of Contents

Chapter 11:

Updating System Software.................................................... 398
Installing Software Updates.............................................................................. Updating a Defense Center or Master Defense Center ...................... Updating Managed Sensors ................................................................ Updating Unmanaged 3D Sensors ...................................................... 400 402 404 406

Uninstalling Software Updates ......................................................................... 409 Updating the Vulnerability Database................................................................. 410

Chapter 12:

Using Backup and Restore .................................................... 413
Creating Backup Files ....................................................................................... 414 Creating Backup Profiles ................................................................................... 418 Performing Sensor Backup with the Defense Center ....................................... 419 Uploading Backups from a Local Host .............................................................. 420 Restoring the Appliance from a Backup File ..................................................... 421

Chapter 13:

Scheduling Tasks .................................................................... 425
Configuring a Recurring Task ............................................................................ 426 Automating Backup Jobs .................................................................................. 428 Automating Software Updates ......................................................................... Automating Software Downloads ........................................................ Automating Software Pushes .............................................................. Automating Software Installs............................................................... Automating Vulnerability Database Updates .................................................... Automating VDB Update Downloads................................................... Automating VDB Update Pushes......................................................... Automating VDB Update Installs ......................................................... 430 431 433 435 437 438 440 442

Automating SEU Imports.................................................................................. 444 Automating Intrusion Policy Applications.......................................................... 446 Automating Reports.......................................................................................... 448 Automating Nessus Scans................................................................................ 450 Preparing Your System to Run a Nessus Scan..................................... 450 Scheduling a Nessus Scan................................................................... 451 Synchronizing Nessus Plugins .......................................................................... 452 Automating Nmap Scans .................................................................................. 454 Preparing Your System for an Nmap Scan ........................................... 454 Scheduling an Nmap Scan ................................................................... 455 Automating Recommended Rule State Generation.......................................... 456

Version 4.9.1

Sourcefire 3D System Administrator Guide

10

Table of Contents

Viewing Tasks ................................................................................................... 458 Using the Calendar .............................................................................. 459 Using the Task List............................................................................... 460 Editing Scheduled Tasks ................................................................................... 461 Deleting Scheduled Tasks ................................................................................. 461 Deleting a Recurring Task .................................................................... 462 Deleting a One-Time Task.................................................................... 462

Chapter 14:

Monitoring the System ........................................................... 463
Viewing Host Statistics..................................................................................... 464 Monitoring System Status and Disk Space Usage ........................................... 468 Viewing System Process Status ....................................................................... 468 Understanding Running Processes................................................................... 471 Understanding System Daemons ........................................................ 471 Understanding Executables and System Utilities ................................ 473 Viewing IPS Performance Statistics.................................................................. 476 Generating IPS Performance Statistics Graphs ................................... 476 Saving IPS Performance Statistics Graphs .......................................... 478 Viewing RNA Performance Statistics................................................................ 478 Generating RNA Performance Statistics Graphs ................................. 479 Saving RNA Performance Statistics Graphs ........................................ 481

Chapter 15:

Using Health Monitoring ........................................................ 482
Understanding Health Monitoring .................................................................... Understanding Health Policies ............................................................. Understanding Health Modules ........................................................... Understanding Health Monitoring Configuration ................................. Configuring Health Policies ............................................................................... Predefined Health Policies ................................................................... Creating Health Policies ....................................................................... Applying Health Policies....................................................................... Editing Health Policies ......................................................................... Deleting Health Policies ....................................................................... 483 484 485 489 489 490 497 528 530 533

Using the Health Monitor Blacklist ................................................................... 534 Blacklisting Health Policies or Appliances ............................................ 535 Blacklisting a Health Policy Module ..................................................... 537

Version 4.9.1

Sourcefire 3D System Administrator Guide

11

Table of Contents

Configuring Health Monitor Alerts .................................................................... Preparing to Create a Health Alert ....................................................... Creating Health Monitor Alerts ............................................................ Interpreting Health Monitor Alerts....................................................... Editing Health Monitor Alerts .............................................................. Deleting Health Monitor Alerts ............................................................

539 540 540 542 543 544

Chapter 16:

Reviewing Health Status........................................................ 545
Using the Health Monitor ................................................................................. 545 Interpreting Health Monitor Status ...................................................... 547 Using Appliance Health Monitors ..................................................................... Interpreting Appliance Health Monitor Status ..................................... Viewing Alerts by Status...................................................................... Running All Modules for an Appliance ................................................. Running a Specific Health Module....................................................... Generating Health Module Alert Graphs.............................................. Generating Appliance Troubleshooting Files........................................ Working with Health Events ............................................................................. Understanding Health Event Views ..................................................... Viewing Health Events......................................................................... Understanding the Health Events Table............................................... Searching for Health Events................................................................. 547 549 549 550 551 553 554 555 556 556 561 563

Chapter 17:

Auditing the System................................................................ 566
Managing Audit Records .................................................................................. Viewing Audit Records......................................................................... Suppressing Audit Records.................................................................. Understanding the Audit Log Table...................................................... Searching Audit Records...................................................................... 566 567 570 574 575

Viewing the System Log ................................................................................... 578 Filtering System Log Messages .......................................................... 579 Using Four-Digit Year Formats on the 3D3800 ..................................... 581

Version 4.9.1

Sourcefire 3D System Administrator Guide

12

.......9.......... 603 Index ........... Exporting a User-Defined RNA Detector.............................................. Exporting an RNA Detection Policy...Table of Contents Appendix A: Importing and Exporting Objects ............................................ 593 Appendix B: Appendix C: Purging the RNA and RUA Databases...................................................................................................................................................... 629 Version 4..................................... 600 Managing the Task Queue .... 598 Viewing the Status of Long-Running Tasks ............................................ Exporting a PEP Policy ......................................... Exporting a System Policy........... Exporting Multiple Objects ....................................................................... 602 Glossary ............................ Exporting an Intrusion Policy........ 584 584 585 585 586 586 588 588 588 589 590 Importing Objects ..................................................................................................................................................................................................................................................................... 583 Exporting Objects ... Exporting a Health Policy ..................................................................................................................................................... 600 Viewing the Task Queue ......................................................1 Sourcefire 3D System Administrator Guide 13 .... Exporting a Custom Table ...................................................................................................... Exporting a Custom Workflow.......................................................................................................................................................................................................................... Exporting a Dashboard.........................

and event viewing preferences. account password. • • • Version 4.9. Logging into the Appliance on page 21 explains how to access the web interface on your appliance and log in using one of the user accounts. • • • Components of the Sourcefire 3D System on page 15 provides descriptions of each of the components that may be in your Sourcefire 3D System. time zone. Logging into the Appliance to Set Up an Account on page 23 explains how to set up an association between a external user account and a set of credentials on the appliance. Sourcefire 3D System has the tools you need to: • • • discover the changing assets and vulnerabilities on your network determine the types of attacks against your network and the impact they have to your business processes defend your network in real time The topics that follow introduce you to the Sourcefire 3D System and describe some of the key components that contribute to its value as a part of any security strategy for your network. Using the Context Menu on page 36 explains how to display a context-specific menu of shortcuts on certain pages in the web interface.1 Sourcefire 3D System Administrator Guide 14 . dashboard. Logging Out of the Appliance on page 24 explains how to log out of the web interface. such as the home page. Specifying Your User Preferences on page 25 explains how to configure the preferences that are tied to a single user account.Introduction to the Sourcefire 3D System Chapter 1 Administrator Guide tn The Sourcefire 3D System™ provides you with real-time network intelligence for real-time network defense.

Introduction to the Sourcefire 3D System Components of the Sourcefire 3D System Chapter 1 • • • Documentation Resources on page 37 explains where to locate specific information about using the Defense Center.9. compliance white lists. Components of the Sourcefire 3D System The topics that follow introduce you to the Sourcefire 3D System and describe some of the key components that contribute to its value as a part of any security strategy for your network. listening to the network segments you specify. RNA monitors traffic on your network. using information from detected packets to build a comprehensive map of the devices on the network. and traffic profiles to protect your company’s infrastructure by monitoring network traffic for unusual patterns or behavior and automatically responding as needed. Documentation Conventions on page 38 explains typeface conventions used throughout the guide to convey specific types of information visually. IP Address Conventions on page 41 explains how the Sourcefire 3D System treats IP address ranges specified using Classless Inter-Domain Routing (CIDR) notation. As RNA passively observes traffic. You must use a Defense Center to manage a 3D Sensor if it is running RNA.1 Sourcefire 3D System Administrator Guide 15 . You can set up compliance policies. • • • • • • • • • Real-time Network Awareness (RNA) on page 15 Intrusion Prevention System (IPS) on page 16 Real-time User Awareness (RUA) on page 17 Defense Centers on page 17 Master Defense Centers on page 19 Intrusion Agents on page 19 RNA for Red Hat Linux on page 20 RNA and IPS for Crossbeam Systems on page 20 eStreamer on page 20 Real-time Network Awareness (RNA) Sourcefire Real-time Network Awareness (also called RNA) is one of the components of the Sourcefire 3D System that you can use on your 3D Sensor. it compiles the following information: • • • the number and types of network devices running on your network the operating systems running on monitored network devices the active services and open ports on monitored network devices Version 4.

When a 3D Sensor identifies a possible intrusion. and RNA detection policies to your sensors. 3D Sensors that are licensed to use IPS include a set of intrusion rules developed by the Sourcefire Vulnerability Research Team (VRT).9. the sensors transmit events and sensor statistics to the Defense Center where you can view the aggregated data and gain a greater understanding of the attacks against your network assets. system. Each 3D Sensor uses rules. IPS allows you to monitor your network for attacks that might affect the availability. see What Can Be Managed by a Defense Center? on page 101. and intrusion policies to your sensors. the type of exploit. it generates an intrusion event. you can examine the packets that traverse your network for malicious activity. The Defense Center can also push health. You can choose to enable rules that would detect the attacks you think most likely to occur on your network. In addition. event and flow data. or confidentiality of hosts on the network.Introduction to the Sourcefire 3D System Components of the Sourcefire 3D System Chapter 1 • • the vulnerabilities and exploits to which monitored network devices may be susceptible flow data. services.The Defense Center can also push health. By placing 3D Sensors on key network segments. and assigned host attributes. 3D Sensors with IPS run preprocessors against detected network traffic to normalize traffic and detect malicious packets. which are records of active sessions involving monitored network devices including the frequency and size of the session. the client application and URL involved in the session You can access event views and graphs to analyze this collected data. You can also create custom intrusion rules tuned to your environment. For more information. You can access host profiles by browsing the network map or through one of the workflows Sourcefire provides to aid your analysis. and contextual information about the source of the attack and its target. and preprocessors to look for the broad range of exploits that attackers have developed. as well as the service and protocol used and. integrity. if applicable. 3D Sensors running RNA transmit the network map. containing host details such as detected operating system. which is a record of the date. system. You can push software Version 4. time. a copy of the packet or packets that triggered the event is also recorded. and sensor statistics to the Defense Center so you can see a consolidated view of events. You can push vulnerability database (VDB) and software updates from the Defense Center as well. and protocols. RNA builds a host profile for each host it detects.1 Sourcefire 3D System Administrator Guide 16 . In a Sourcefire 3D System deployment that includes 3D Sensors with IPS and a Defense Center. decoders. Intrusion Prevention System (IPS) The Sourcefire Intrusion Prevention System (also called IPS) is one of the components of the Sourcefire 3D System that you can run on the 3D Sensor. RNA assigns vulnerabilities to the host based on the operating system vendor and version detected for the host. For packet-based events.

PEP Traffic Management PEP is a technology based on the hardware capabilities of the 3D9900 Sensors. Sourcefire recommends that you use only the Defense Center’s web interface to interact with the sensor and its data. As a result. If you deploy your 3D Sensor inline on your network and create what is called an inline detection engine. You can apply these policies and rules across the Sourcefire 3D System. IMPORTANT! The Sourcefire 3D Sensor 3800. You can analyze and respond to events from all your sensors consistently by doing the analysis through an interface where you can see all the data collected by the managed sensors. analyze.9. Real-time User Awareness (RUA) The Real-time User-Awareness component (also called RUA) allows you to create policies and response rules that are user-based. The network protocol used by your organization to provide user authentication largely determines the amount of data and efficiency of RUA. 3D Sensor 6800. see What Can Be Managed by a Defense Center? on page 101.Introduction to the Sourcefire 3D System Components of the Sourcefire 3D System Chapter 1 updates from the Defense Center to sensors as well. You must manage these models with a Defense Center. you can configure your 3D Sensor to drop or replace packets that you know to be harmful. You can also push policies created on the Defense Center and software updates to managed sensors.1 Sourcefire 3D System Administrator Guide 17 . Defense Centers The Defense Center provides a centralized management interface and database repository for the Sourcefire 3D System. See Using Sourcefire RUA in the Analyst Guide for more information about RUA. RUA enables you to implement and enforce policies specific to individuals. PEP allows you to create rules to block. departments. If you have software sensors or Intrusion Agents on your network. or other user characteristics. or send traffic directly through the 3D9900 with no further inspection. and 3D Sensor 9800 models (usually referred to a the 3Dc800 sensors) do not have a web interface. If your 3D Sensor is running IPS. PEP traffic management enhances the sensor’s efficiency by allowing you to pre-select traffic to cut through or to drop instead of analyzing. For more information. you must use the Defense Center to manage them. you can also use a local web interface to create intrusion policies and review the resulting intrusion events. Note that if you do manage your 3D Sensors with a Defense Center. Note that a 3D Sensor running Version 4.

or network vulnerabilities. The DC500 receives data at an aggregate rate of up to 100 intrusion events or 900 flow events per second. You can configure a DC3000 as a Master Defense Center during the initial setup. and network intelligence with user identity information so that you can identify the source of policy breaches. IMPORTANT! You cannot use DC500s in high availability configurations. Impact correlation lets you focus in on attacks most likely to damage high priority hosts. the Defense Center correlates intrusion events from IPS with host vulnerabilities from RNA and assigns impact flags to the intrusion events. Version 4. Key DC500 database limits are: • • • Intrusion Events .1 million default and 10 million maximum RNA Flow Summaries . but if you want to use RNA on the sensor. You can use either DC1000s or DC3000s in high availability configurations. A DC3000 allows you to use higher database quantities.2 million default and 10 million maximum DC1000 You can use DC1000 Defense Centers in most environments. DC500s also have an RNA host limit of 1000.1 million default and 10 million maximum RNA Flow Summaries . If you use your Defense Center to manage 3D Sensors that run RNA and IPS (either on the same sensor or different sensors that monitor the same network segments). Key DC1000 database quantities are: • • • Intrusion Events . DC500 You can use the DC500 model of the Defense Center in managed services environments to collect data from up to three 3D Sensors.Introduction to the Sourcefire 3D System Components of the Sourcefire 3D System Chapter 1 the IPS component includes its own local web interface.9.5 million maximum RNA Flows .2 million default and 10 million maximum DC3000 You can use DC3000 Defense Centers in high-demand environments. you must manage the sensor with a Defense Center.1 Sourcefire 3D System Administrator Guide 18 . endpoint. the Defense Center correlates threat.1 million default and 10 million maximum RNA Flows . If you deploy Real-time User-Awareness (RUA). You can rack mount a DC1000 and collect data from a large number of 3D Sensors. attacks.500 thousand default and 2.

The Master Defense Center can also aggregate events related to the health of the Defense Centers it is managing.1 Sourcefire 3D System Administrator Guide 19 . You can manage up to 25 physical and Virtual 3D Sensors with a Virtual Defense Center.Introduction to the Sourcefire 3D System Components of the Sourcefire 3D System Chapter 1 Key DC3000 database quantities are: • • • Intrusion Events .2 million default and 10 million maximum Master Defense Centers The Sourcefire Master Defense Center is a key component in the Sourcefire 3D System. compliance events. see the Sourcefire 3D System Virtual Defense Center and 3D Sensor Installation Guide.2 million default and 100 million maximum Virtual Defense Center Virtual Defense Centers are hosted on VMware’s ESX/ESXi or Xen virtual machines.1 million default and 100 million maximum RNA Flow Summaries .1 million default and 100 million maximum RNA Flows . and white list events from up to ten Defense Centers within your Sourcefire 3D System deployment. See Using the Master Defense Center on page 156 for more information about managing your Defense Centers with a Master Defense Center. If the network map on the Defense Center has entries for the target host in a given event. For more information.1 million default and 10 million maximum RNA Flows .9. You can use the Master Defense Center to aggregate and analyze intrusion events. you can view the current status of the Defense Centers across your enterprise from a single web interface. In this way. You cannot use a Virtual Defense Center in high availability configurations or as a Master Defense Center.1 million default and 10 million maximum RNA Flow Summaries . you can do analysis and reporting on those events. the Defense Center Version 4. Key Virtual Defense Center database quantities are: • • • Intrusion Events . you can install an Intrusion Agent to forward intrusion events to a Defense Center. You can then analyze the events detected by Snort alongside your other data. Intrusion Agents If you have an existing installation of Snort®. Although you cannot manage policies or rules for an Intrusion Agent from the Defense Center.

you could write a program to retrieve host criticality or vulnerability data from the Defense Center and add that information to your display. See the Sourcefire RNA Software on Red Hat Linux Configuration Guide for more information. IMPORTANT! You must have a Defense Center in your Sourcefire 3D System deployment to use RNA for Red Hat Linux. If. RNA and IPS data received by a Defense Center from a Crossbeam-based software sensors is treated in a similar way to data received from a 3D Sensor. Separate installation and configuration guides are available for the 3D Sensor Software for X-Series.Introduction to the Sourcefire 3D System Components of the Sourcefire 3D System Chapter 1 assigns impact flags to the events. register all Intrusion Agents to the primary Defense Center. IMPORTANT! When using Intrusion Agents registered to Defense Centers configured for high availability and managed by a Master Defense Center. but allows you to request specific data from a Defense Center. RNA data received by a Defense Center from the server is treated in a similar way to RNA data received from a 3D Sensor that is running RNA. See the eStreamer Integration Guide for more information. you display network host data within one of your network management applications. IMPORTANT! Because the 3D Sensor Software for X-Series does not have a web interface. you must use a Defense Center to manage it. eStreamer integration requires custom programming. RNA and IPS for Crossbeam Systems The Sourcefire 3D System currently supports software-only versions of RNA and IPS for Crossbeam Systems X-Series security switches. for example. You can continue to manually tune Snort rules and preprocessors with the Intrusion Agent in place.9. eStreamer You can access event data within your own applications through the eStreamer Application Programming Interface (API).1 Sourcefire 3D System Administrator Guide 20 . Version 4. RNA for Red Hat Linux The Sourcefire 3D System currently supports a software-only version of the RNA component on your server hardware running Red Hat Enterprise Linux 5 (RHEL5) or CentOS 5.

RNA for Red Hat Linux. and Virtual 3D Sensors) do not have a web interface.5. Note that 3Dx800 and software sensors (Crossbeam-based software sensors.Introduction to the Sourcefire 3D System Logging into the Appliance Chapter 1 Logging into the Appliance Requires: Any The Defense Center and many 3D Sensor models have a web-based interface that you can use to perform administrative. Browser Requirements Browser Firefox 3.0 Microsoft Internet Explorer 8. If your 3D Sensor is not licensed for IPS.0 TIP! Some processes that take a significant amount of time may cause your web browser to display a message that a script has become unresponsive. You must use the Defense Center’s web interface to manage these sensors. If you are the first user to log into the appliance after it is installed.x Required Enabled Options and Settings JavaScript cookies Secure Sockets Layer (SSL) v3 JavaScript cookies Secure Sockets Layer (SSL) v3 128-bit encryption Active scripting security setting JavaScript cookies Secure Sockets Layer (SSL) v3 128-bit encryption Active scripting security setting Compatibility View Microsoft Internet Explorer 7 . make sure you allow the script to continue until it finishes. Version 4. and analysis tasks.1 Sourcefire 3D System Administrator Guide 21 . management. there is a limited web interface that you can use to perform the initial appliance setup and to register the sensor with a Defense Center. you must log in using the admin user account. you are presented with a more complete web interface that you can use to perform additional configuration and event analysis.9. Intrusion Agents. If this occurs. You can access the web interface by logging into the appliance using a web browser. The current version of the web interface supports the browsers listed in the following table. If your 3D Sensor is licensed for IPS. The initial setup process is described in Setting Up 3D Sensors on page 44.

For example. The first time you log into the appliance. you should use this account. Version 4.Introduction to the Sourcefire 3D System Logging into the Appliance Chapter 1 After you log into the appliance. unless you are viewing a page (such as an unpaused dashboard) that periodically communicates with the web server on the appliance.1 Sourcefire 3D System Administrator Guide 22 . append the SecurID token to the end of your SecurID pin and use that as your password when you log in. if your pin is 1111 and the SecurID token is 222222. To log into the appliance: Access: Any 1. the user who performed the installation created a single administrative user account and password.5 hours of inactivity. However. type your user name and password. append the token to your SecurID pin and use that as your password to log in. IMPORTANT! If your company uses SecurID. The Login page appears. the procedures for logging into and out of the appliance remain the same. In the Username and Password fields. type 1111222222. you should make sure that users log into the system with the correct account. you and other users should use those accounts to log into the appliance.9. where hostname corresponds to the host name of the appliance. You must have already generated your SecurID pin before you can log into the Sourcefire 3D System. IMPORTANT! Because the Defense Center and the 3D Sensor audit user activity based on user accounts. the features that you can access are controlled by the privileges granted to your user account. 2. Direct your browser to https://hostname/. After you create other user accounts as described in Adding New User Accounts on page 300. If your organization uses SecurID® tokens when logging in. When the appliance was installed. Your session automatically logs you out after 3.

you can log in but cannot access any functionality. externally authenticated users can log into the appliance using their external account credentials without any additional configuration by the system administrator. If the default role for external user accounts is set to a specific access role. it does not create a local user account. the following warning message is displayed: You are attempting to view an unauthorized page. The permissions for that local user record can then be modified. If you selected a new home page for your user account.). Click Login. Shell access is controlled entirely through the shell access filter or PAM login attribute set for an LDAP server or the shell access list on a RADIUS server. Note that when a shell access user logs into the appliance. The menus and menu options that are available to you at the top of the page are based on the privileges for your user account. Shell users should log in using usernames with all lowercase letters. If this is the case. the links on the default home page include options that span the range of user account privileges. You can either select a different option from the available menus or click Back in your browser window. if your pin is 1111 and the SecurID token is 222222.9. append the token to your SecurID pin and use that as your password to log in. The default start page appears. If your organization uses SecurID tokens when logging in. then that page is displayed instead. However. and hyphens (-) but otherwise only alphanumeric characters are supported. See Specifying Your Home Page on page 35 for more information. LDAP usernames can include underscores (_). If you click a link that requires different privileges from those granted to your account. If an account is externally authenticated and by default receives no access privileges. use the Defense Center’s web interface to manage policies and view events. the appliance associates those credentials with a set of permissions by creating a local user record. This activity has been logged. type 1111222222. For example. IMPORTANT! The 3Dx800 sensor models do not have a web interface.Introduction to the Sourcefire 3D System Logging into the Appliance to Set Up an Account Chapter 1 3. Version 4. the first time you log into the Defense Center or 3D Sensor using your external user credentials. periods (. Instead. You (or your system administrator) can then change the permissions to grant the appropriate access to user functionality. Logging into the Appliance to Set Up an Account Requires: Any Some user accounts may be authenticated through an external authentication server. unless they are granted through group or list membership.1 Sourcefire 3D System Administrator Guide 23 .

then that page is displayed instead. IMPORTANT! If your company uses SecurID. The page that appears depends on the default access role for external authentication: • If a default access role is selected in the authentication object or the system policy. the default start page appears. 2. The menus and menu options that are available to you at the top of the page are based on the privileges for your user account. If you click a link that requires different privileges from those granted to your account. where hostname corresponds to the host name of the appliance. This activity has been logged. 4.Introduction to the Sourcefire 3D System Logging Out of the Appliance Chapter 1 To create an externally authenticated account on the appliance: Access: Any 1. see Modifying User Privileges and Options on page 306. The Login page appears. type your user name and password. • If no default access role is selected. See Specifying Your Home Page on page 35 for more information.1 Sourcefire 3D System Administrator Guide 24 . If you do not have access. Version 4.9. even if you are only stepping away from your web browser for a short period of time. In the Username and Password fields. the links on the default home page include options that span the range of user account privileges. For more information. Logging Out of the Appliance Requires: Any Make sure you log out of the appliance. However. 3. Click Login. the following warning message is displayed: You are attempting to view an unauthorized page. If you continue to have difficulty accessing this device. with the following error message: Unable to authorize access. Logging out ends your web session and ensures that no one can use the appliance with your credentials. contact your system administrator and ask them to modify your account privileges or login as a user with Administrator access and modify the privileges for the account. append the SecurID token to your SecurID pin and use that as your password when you log in. please contact the system administrator. You can either select a different option from the available menus or click Back in your browser window. Direct your browser to https://hostname. If you selected a new home page for your user account. the Login page re-appears.

you can view information about the last login session for the appliance. Setting Your Default Time Zone on page 34 explains how to set the time zone for your user account and describes how that affects the time stamp on the events that you view. event viewing preferences. Specifying Your User Preferences Requires: Any Users can specify certain preferences for their user account. See the following sections for more information: • • • Changing Your Password on page 25 explains how to change the password for your user account. unless you are viewing a page (such as an unpaused dashboard) that periodically communicates with the web server on the appliance.Introduction to the Sourcefire 3D System Last Successful Login Chapter 1 Note that your session automatically logs you out after 3.1 Sourcefire 3D System Administrator Guide 25 . you may have to change your password periodically. month. Last Successful Login Requires: Any The first time you visit the appliance home page during a web session. You can change your password at any time. see Changing an Expired Password on page 26. Configuring Event View Settings on page 27 describes how the event preferences affect what you see as you view events. and depending on the settings for your user account. To log out of the appliance: Access: Any Click Logout on the toolbar. date and year of your last login the appliance-local time of your last login in 24-hour notation host and domain name last used to access the appliance. this is the first page you see upon logging into the appliance. After setting this value.9.5 hours of inactivity. and home page preferences. Specifying Your Home Page on page 35 explains how to use one of the existing pages as your default home page. Specifying Your Default Dashboard on page 35 explains how to choose which of the dashboards you want to use as your default dashboard. You can see the following information about that user account last login: • • • day of the week. • • Changing Your Password Requires: Any All user accounts are protected with a password. including passwords. Version 4. time zone settings.

click Preferences. A success message appears on the page when your new password is accepted by the system. you cannot change your password through the web interface. To respond to the password expiration warning: Access: Any You have two choices: • Click Change Password to change your password now. If you have zero warning days left. the Password Expiration Warning page appears. In the Current Password field. IMPORTANT! If you are an LDAP or a RADIUS user. Passwords cannot be a word that appears in a dictionary or include consecutive repeating characters • Click Skip to change your password later. passwords must be at least eight alphanumeric characters of mixed case and must include at least one numeric character. In the toolbar. 3. Click Change Password. 5. Changing an Expired Password Requires: DC/MDC or 3D Sensor Depending on the settings for your user account.9. If your password has exired. type your new password. type your current password and click Change. passwords must be at least eight alphanumeric characters of mixed case and must include at least one numeric character. Click Change. 4. Also. In the New Password and Confirm fields. Passwords cannot be a word that appears in a dictionary or include consecutive repeating characters. The User Preferences page appears. if password strength-checking is enabled. Version 4. you must change your password. 2. Note that the password expiration time period is set when your account is created and cannot be changed. your password can expire.1 Sourcefire 3D System Administrator Guide 26 .Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 Note that if password strength-checking is enabled. To change your password: Access: Any 1. The Change Password page appears.

The User Preferences page appears. For more information. In the toolbar. For more information. The Event View Settings page appears. click Preferences. Configure the default time window or windows. 3. 6. Your changes are implemented.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 Configuring Event View Settings Requires: Any Use the Event View Settings page to configure characteristics of event views in the Sourcefire 3D System. Click Save. Configure the basic characteristics of event views. Version 4. see Event Preferences on page 27. 4. see Default Workflows on page 32. To configure event preferences: Access: Any 1.9. Configure default workflows. For more information. Click Event View Settings. 5. see Default Time Windows on page 29.1 Sourcefire 3D System Administrator Guide 27 . Event Preferences Use the Event Preferences section of the Event View Settings page to configure basic characteristics of event views in the Sourcefire 3D System. 2.

Note that an event view can be slow to display if it contains a large number of IP addresses and you have enabled this option.collapse all subsections of the Packet Information section of the packet view • Packet Text .Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 The Event Preferences table describes the settings you can configure. Resolve IP Addresses Whenever possible. By default. Rows Per Page Controls how many rows of events per page you want to appear in drill-down pages and table views. you can always manually expand the sections in the packet view to view detailed information about a captured packet. allows the appliance to display host names instead of IP addresses in event views. Note also that for this setting to take effect.9. if this setting is enabled and you click Delete All on an event view. you must have a DNS server configured in the system settings. Any IPS or DC/MDC + IPS IPS or DC/MDC Requires Any Version 4. Event Preferences Setting Confirm ‘All’ Actions Description Controls whether the appliance forces you to confirm actions that affect all events in an event view. see Using the Packet View in the Analyst Guide. see Configuring Network Settings on page 377.expand all sections Regardless of the default setting.expand only the Packet Text subsection • Packet Bytes . you must confirm that you want to delete all the events that meet the current constraints (including events not displayed on the current page) before the appliance will delete them from the database.expand only the Packet Bytes subsection • All . the appliance displays a collapsed version of the packet view. For more information on the packet view. • None . For example. Expand Packet View Allows you to configure how the packet view for intrusion events appears.1 Sourcefire 3D System Administrator Guide 28 .

Use the Default Time Windows section of the Event View Settings page to control the default behavior of the time window. • Ask . The following graphic shows the Defense Center version of the page. imposes a time constraint on the events in any event view. sometimes called the time range. your user account must have either Administrator access or both Intrusion Event Analyst and Policy & Response Administrator access.1 Sourcefire 3D System Administrator Guide 29 .9. Entering zero disables the refresh option. Note that this interval does not apply to dashboards. Note that you cannot deactivate rules in the default policies. Also keep in mind that time window settings are valid for only the current session. Note that regardless of the default time window setting. you can always manually change the time window for individual event views during your event analysis.links for each of these options To see these links on the packet view. Requires Any Statistics Refresh Interval IPS or DC/MDC Deactivate Rules IPS or DC/MDC + IPS Default Time Windows Requires: Any The time window. When you log out and then log back in. Controls which links appear on the packet view for intrusion events generated by standard text rules.a single link that deactivates the standard text rule in all the locally defined custom intrusion policies • Current Policy .Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 Event Preferences (Continued) Setting Refresh Interval Description Sets the refresh interval for event views. in minutes. Note that this interval does not apply to dashboards.a single link that deactivates the standard text rule in only the currently applied intrusion policy. time windows are reset to the Version 4. Sets the refresh interval for event summary pages such as the Intrusion Event Statistics and RNA Statistics pages. Entering zero disables the refresh option. • All Policies .

maintenance users. see Setting Event Time Constraints in the Analyst Guide. as time moves forward. which displays all the events generated from a specific start time to the present. RNA event analysts. Requires: Any The Audit Log Time Window sets the default time window for the audit log. compliance events. • • You can only set time windows for event types your user account can access. There are three types of time window: • • static. Administrators. white list events.1 Sourcefire 3D System Administrator Guide 30 . RNA events. RUA events. flow data. There are three types of events for which you can set the default time window. All user types can set event time windows. or white list violations. Note that because not all event views can be constrained by time. the time window “slides” so that you see only the events for the range you configured (in this example. host attributes. services. Administrators and maintenance users can set audit log time windows. and event views for custom tables that can be constrained by time. You can either use Multiple time windows. the SEU import log.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 defaults you configured on this page. If you use a single time window. which displays all the events generated from a specific start time (for example. one for each of these types of events. the settings for the three types of time window disappear and a new Global Time Window setting appears.9. or you can use a Single time window that applies to all events. • Requires: IPS or DC/MDC The Events Time Window sets a single default time window for (depending on the appliance) intrusion events. time window settings have no effect on event views that display RNA hosts. client applications. the time window expands and new events are added to the event view sliding. for the last day) • Version 4. one day ago) to the present. which displays all the events generated from a specific start time to a specific end time expanding. RUA users. vulnerabilities. For more information. remediation status events. Requires: DC/MDC The Health Monitoring Time Window sets the default time window for health events. as time moves forward. and IPS event analysts can set health monitoring time windows.

the appliance displays all the events generated from a specific start time (for example.9. For static time windows (enable the Use End Time check box). IMPORTANT! The maximum time range for all time windows is from midnight on January 1. to the present. 1 hour ago). 1 hour ago). the time window “slides” so that you always see events from the last hour. The appliance displays all the events generated from a specific start time (for example. to the time when you first viewed the events. Show the Last Static/Expanding This setting allows you to configure either a static or expanding default time window of the length you specify. As you change event views. Version 4. the time window expands to the present time.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 The Time Window Settings table explains the kinds of default time windows you can configure. Time Window Settings Setting Show the Last Sliding Description This setting allows you to configure a sliding default time window of the length you specify. As you change event views. the time window stays fixed so that you see only the events that occured during the static time window. 2038 (UTC).1 Sourcefire 3D System Administrator Guide 31 . the appliance displays all the events generated from a specific start time (for example. As you change event views. For expanding time windows (disable the Use End Time check box). 1 hour ago) to the present. 1970 (UTC) to 3:14:07 AM on January 19.

For each event type.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 Time Window Settings (Continued) Setting Current Day Static/Expanding Description This setting allows you to configure either a static or expanding default time window for the current day. the time window expands to the present time. The current day begins at midnight. based on the time zone setting for your current session. the appliance displays all the events generated from midnight to the time when you first viewed the events. For static time windows (enable the Use End Time check box). As you change event views. Default Workflows Requires: Any A workflow is a series of pages displaying data that analysts use to evaluate events. each of which presents intrusion event data in a different way. the time window expands to the present time. the appliance displays all the events generated from midnight Sunday to the present. For example. the appliance displays all the events generated from midnight to the time when you first viewed the events. Current Week Static/Expanding This setting allows you to configure either a static or expanding default time window for the current week. The current week begins at midnight on the previous Sunday. For expanding time windows (disable the Use End Time check box). For static time windows (enable the Use End Time check box). based on the time zone setting for your current session. this time window can be more than 24 hours. depending on the type of analysis you are performing. As you change event views. The appliance is configured with a default workflow for each event type. Note that if your analysis continues for over 1 week before you log out. this time window can be more than 1 week. you can choose between ten different intrusion event workflows. the appliance displays the Events by Priority and Classification workflow. the appliance displays all the events generated from midnight to the present. Note that if your analysis continues for over 24 hours before you log out. the Events by Priority and Classification workflow is the default for intrusion events.1 Sourcefire 3D System Administrator Guide 32 . the time window stays fixed so that you see only the events that occured during the static time window. the time window stays fixed so that you see only the events that occured during the static time window. For example. As you change event views. This means whenever you view intrusion events (including reviewed intrusion events). the appliance ships with at least one predefined workflow. As you change event views.9. For expanding time windows (disable the Use End Time check box). Version 4.

For example.9. As another example. The following graphic shows the Defense Center version of the Default Workflows section.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 You can. change the default workflow for each event type using the Default Workflows sections of the Event View Settings page. For general information on workflows. on the Defense Center. intrusion event analysts cannot set default RNA workflows. but also on your user role. on a 3D Sensor without an IPS license. Version 4. Keep in mind that the default workflows you are able to configure depend not only on the appliance you are using. you can only configure the default workflow for the audit log.1 Sourcefire 3D System Administrator Guide 33 . however. see Understanding and Using Workflows in the Analyst Guide.

4.1 Sourcefire 3D System Administrator Guide 34 . 2.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 Setting Your Default Time Zone Requires: Any You can change the time zone used to display events from the standard UTC time that the appliance uses. The time zone is set. Click Save. For example. From the box on the left. select the continent or area that contains the time zone you want to use. South America. WARNING! The Time Zone function assumes that the default system clock is set to UTC time. 5. click Preferences. If you have changed the system clock on the appliance to use a local time zone. select America. The Time Zone Preference page appears. When you configure a time zone. you must change it back to UTC time in order to view accurate local time on the appliance. The User Preferences page appears. select the zone (city name) that corresponds with the time zone you want to use. To change your time zone: Access: Any 1. From the box on the right. if you want to use a time zone standard to North America. see Synchronizing Time on page 354. it applies only to your user account and is in effect until you make further changes to the time zone. Click Time Zone Settings. you would select New York after selecting America in the first time zone box. For example. For more information about time synchronization between the Defense Center and the sensors. Version 4. In the toolbar. or Canada. if you want to use Eastern Standard Time.9. 3.

IMPORTANT! User accounts with Restricted Event Analyst access cannot use the dashboard and therefore cannot specify a default dashboard. Restricted Event Analyst full or read-only access. click Preferences. Specifying Your Default Dashboard Requires: Any You can specify one of the dashboards on the appliance as the default dashboard. see Using Dashboards on page 59. Your home page preference is saved. For general information on dashboards. To specify your home page: Access: Any 1. That is. The User Preferences page appears. The User Preferences page appears. the Dashboard List page appears. To specify your default dashboard: Access: Any 1. 4.9. who use the Welcome page. Click Save. Maintenance access. If you do not have a default dashboard defined. The Home Page page appears. In the toolbar.1 Sourcefire 3D System Administrator Guide 35 . 3. user accounts with Policy & Response Administrator access have different options from accounts with Intrusion or RNA Event Analyst full or read-only access. Click Home Page.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 Specifying Your Home Page Requires: Any You can specify a page within the web interface as your home page for the appliance. The default dashboard appears when you select Analysis & Reporting > Event Summary > Dashboards. 2. click Preferences. or Administrator access. The default home page is the dashboard (Analysis & Reporting > Event Summary > Dashboards). In the toolbar. Select the page you want to use as your home page from the Opening Screen drop-down list. except for user accounts with Restricted Event Analyst access. The options in the drop-down list are based on the access privileges for your user account. Version 4.

To access the context menu: Access: Any 1. For example. You can access the context menu on the following pages. • • Event pages (drill-down pages and table views) contain hotspots over each event. As the name implies. suppressing. Note that if you try to access the context menu for a web page or location that doesn’t support the Sourcefire-specific menu. when you select Analysis & Reporting > Event Summary > Dashboards. The Rule Editor page for intrusion rules contains a hotspot over each intrusion rule. Click Dashboard Settings.1 Sourcefire 3D System Administrator Guide 36 . On one of the hotspot-enabled pages in the web interface. the contents of the menu depend on the context where you access it.9. if you access the context menu while viewing an intrusion event that was triggered by an intrusion rule. the Dashboard List page appears. the context menu provides you with the option to view the event in a separate browser window. You can then select a dashboard to view. If you select None. Version 4. You can also view the rule documentation and edit the rule. However. the normal context menu for your browser appears.Introduction to the Sourcefire 3D System Using the Context Menu Chapter 1 2. A “Right-click for menu” message appears. you have a range of options that includes enabling. 3. Using the Context Menu Requires: Any For your convenience. if you access the menu while viewing an RNA event. 4. Click Save. certain pages in the web interface support a pop-up context menu that you can use as a shortcut for accessing other features in the Sourcefire 3D System. The Dashboard Settings page appears. Your default dashboard preference is saved. Select the dashboard you want to use as your default from the Default Dashboard drop-down list. disabling. and thresholding the rule. hover your pointer over one of the hotspots.

and Policy & Response Administrators. The Documentation CD contains a PDF version of the Sourcefire 3D System Administrator Guide and the Sourcefire 3D System Analyst Guide. A pop-up context menu appears with options that are appropriate for the hotspot.9. which includes information about installing the appliance as well as hardware specifications and safety information. system management. including procedural and conceptual information about user management. Documentation Resources The Sourcefire 3D System documentation set includes online help and PDF files. and 3D Sensors. and intrusion data. In this guide you will find information about managing RNA and IPS policies. Right-click your pointing device. which together include the same content as the online help. The CD also contains copies of various API guides and supplementary material. managing user accounts. For example.sourcefire. scheduling tasks. configuring system settings and system policies. analyzing RNA. and using event reports. The Documentation CD also contains copies of the Defense Center Installation Guide and the 3D Sensor Installation Guide. and monitoring the health of your appliances. RNA Event Analysts. A new browser window opens based on the option you selected.com/). Select one of the options by left-clicking the name of the option. RUA. The online help includes information about the tasks you can complete on the web interface. The Administrator Guide contains information specifically for administrators and maintenance users. 3. Version 4.1 Sourcefire 3D System Administrator Guide 37 . and IPS and RNA analysis. The Analyst Guide contains information for Intrusion Event Analysts. the following menu appears if you right-click over an intrusion event.Introduction to the Sourcefire 3D System Documentation Resources Chapter 1 2. You can access the most up-to-date versions of the documentation on the Sourcefire Support web site (https://support. You can reach the online help in two ways: • • by clicking the context-sensitive help links on each page by selecting Operations > Help > Online. but in an easy-to-print format. In this guide you will find information about managing Master Defense Centers. Defense Centers.

Virtual Defense Center. Refer to Platform Requirements Conventions on page 38 for the meaning of the Requires statement at the beginning of each section. Refer to Access Requirements Conventions on page 39 for the meaning of the Access statement at the beginning of each procedure. or DC3000 appliance used as a Defense Center Version 4.Introduction to the Sourcefire 3D System Documentation Conventions Chapter 1 Documentation Conventions This documentation includes information about which Sourcefire 3D System components are required for each feature and which user roles have permission to complete each procedure. Platform requirement information for specific aspects of a feature is provided where needed. The following table defines the abbreviations used to indicate each different platform requirement: Platform and Licensing Requirement Abbreviations Requires Acronym 3D Sensor Indicates One of the following Series 1 or Series 2 sensors: • 3D500 • 3D1000 • 3D2000 • 3D2100 • 3D2500 • 3D3500 • 3D4500 • 3D6500 • 3D9900 This acronym on its own indicates that the task in question can be performed on any of these sensors even if an IPS license is not applied on the sensor and the sensor is not managed.1 Sourcefire 3D System Administrator Guide 38 . All platform information is formatted with an orange typeface. Any DC Any appliance with any combination of licenses A DC500. Platform Requirements Conventions The Requires statement at the beginning of each section in this documentation indicates the combination of appliance platform and licenses you need to use the feature described in the section.9. DC1000.

to manage a Defense Center with a Master Defense Center. so the Changing an Expired Password topic has a Requires statement of DC/MDC or 3D Sensor.1 Sourcefire 3D System Administrator Guide 39 . Access Requirements Conventions The Access statement at the beginning of each procedure in this documentation indicates the access role required to use the feature described in the section. you need both a Defense Center and a Master Defense Center. All access information is formatted with a green typeface. you can change an expired password on a Defense Center or Master Defense Center or on a 3D Sensor. The following table defines the abbreviations used to indicate each different platform requirement: Access Requirement Abbreviations Requires Acronym Admin Any Any Analyst Any except Restricted Indicates User must have the Administrator role User can have any role User can have any analyst role User can have any role except Restricted Analyst or Restricted Analyst (Read Only) Version 4.Introduction to the Sourcefire 3D System Documentation Conventions Chapter 1 Platform and Licensing Requirement Abbreviations (Continued) Requires Acronym DC/MDC IPS RNA RUA Indicates A DC3000 appliance used as a Defense Center or a Master Defense Center A 3D Sensor licensed with the IPS technology An RNA license An RUA license An or conjunction indicates that the task or feature is available on either of the indicated platforms. For example.9. A “+” conjunction indicates that the platforms are required in combination. so the Adding a Master Defense Center topic has a Requires statement of MDC + DC. In contrast.

9.Introduction to the Sourcefire 3D System Documentation Conventions Chapter 1 Access Requirement Abbreviations (Continued) Requires Acronym Any Analyst except Restricted Any IPS Indicates User can have any analyst role except Restricted Analyst or Restricted Analyst (Read Only) User must have the Intrusion Event Analyst role or Intrusion Event Analyst (Read Only) role or the Restricted Event Analyst role or Restricted Event Analyst (Read Only) role with rights to that function User must have the Intrusion Event Analyst role or Restricted Event Analyst role with rights to that function User must have the Intrusion Event Analyst (Read Only) role or Restricted Event Analyst (Read Only) role with rights to that function User must have the Maintenance role User must have the Policy & Response Administrator role User must have the RNA Event Analyst or RNA Event Analyst (Read Only) or Restricted Event Analyst or Restricted Event Analyst (Read Only) with rights to that function User must have the RNA Event Analyst role or Restricted Event Analyst role with rights to that function User must have the RNA Event Analyst (Read Only) role or Restricted Event Analyst (Read Only) role with rights to that function IPS IPS-RO Maint P&R Admin Any RNA RNA RNA-RO A “/” conjunction indicates that the task or feature is available to users with one or more of the indicated platforms. a user must have the RNA Event Analyst or RNA Event Analyst (Read Only) role or the Restricted Event Analyst or Restricted Event Analyst (Read Only) role with RNA Hosts Data set to Show All Data or to show a specific search. For example. to view the Hosts network map. Rule thresholding in the packet view provides an example of required combined access roles. The Access setting for the procedure in the Working with the Hosts Network Map topic is Any RNA/Admin. You must have the Administrator role or have the Policy & Response Administrator role in combination with the Intrusion Event Analyst role or the Restricted Event Analyst role with Intrusion Events Data set to Show All Data or to show a specific search to access the packet view and set thresholding for a rule Version 4. A “+” conjunction indicates that the platforms are required in combination.1 Sourcefire 3D System Administrator Guide 40 .

0.576 65.255.0.0 255. Version 4.168.0 255.0.3/8.255. the Sourcefire 3D System uses only the masked portion of the network IP address you specified. the Sourcefire 3D System uses 10.0.0.0 172.0/8.1.0 10.9.255.0. without changing your user input. IP Address Conventions Requires: Any You can use Classless Inter-Domain Routing (CIDR) notation to define IP address ranges in many places in the Sourcefire 3D System.0/12 192.0.1.16. the following table lists the private IPv4 address spaces in CIDR notation.536 When you use CIDR notation to specify a range of IP addresses.0.255.0/16 IP Addresses in CIDR Block 10.0 Number of IP Addresses 16.2. if you type 10. the Access setting for the procedure in the Setting Threshold Options within the Packet View topic is IPS + P&R Admin/Admin.255 192.255. For example.0 192.255 172.0.0.0.0. CIDR Notation Syntax Examples CIDR Block 10. variables. but the web interface continues to display 10. including but not limited to the following: • • • • • • • • RNA detection policies custom topologies auto-assigned networks for user-defined host attributes traffic profiles compliance rules and white lists active scan targets intrusion policies.1 Sourcefire 3D System Administrator Guide 41 .777 .3/8.0.16.255 Subnet Mask 255.216 1.2.168. and standard text rules PEP CIDR notation uses a network IP address combined with a bit mask to define the IP addresses in the specified range.31.0/8 172.Introduction to the Sourcefire 3D System IP Address Conventions Chapter 1 from the packet view.048.168. For example.240.0. As a result.

1 Sourcefire 3D System Administrator Guide 42 .Introduction to the Sourcefire 3D System IP Address Conventions Chapter 1 In other words. the Sourcefire 3D System does not require it. Version 4. although Sourcefire recommends the standard method of using a network IP address on the bit boundary when using CIDR notation.9.

Consult your original documentation or contact Sourcefire Support for information about performing the initial setup on those sensor models.9. see the Sourcefire 3D System Virtual Defense Center and 3D Sensor Installation Guide. Version 4. See the following sections for more information: • • • Setting Up 3D Sensors on page 44 explains how to complete the setup process for Series 2 3D Sensors. Newer models of the 3D Sensor. To perform the initial setup of a Virtual 3D Sensor. you are presented with a series of start-up pages. you may have a Series 1 3D Sensor. Note that if you purchased your sensor prior to 2008. What’s Next? on page 52 provides detailed lists of the next tasks to be performed by each type of user.1 Sourcefire 3D System Administrator Guide 43 .Performing the Initial Setup Chapter 2 Administrator Guide After installing your Defense Center or 3D Sensor as described in the Installation Guide and logging into the web interface for the first time. called Series 2 sensors. Setting up Defense Centers on page 47 explains how to complete the setup process for Defense Centers. provide a rapid set up feature and a status page.

the results can be unpredictable. WARNING! Prepare for the initial setup and complete it promptly after you begin. Series 2 sensors) provide a simple web form to collect information about your network environment and how you intend to deploy the sensor. setting up the IP address for the management interface. Use the command line interface on the appliance for subsequent changes to the root password.9. the Install page appears so that you can continue the setup process.Performing the Initial Setup Setting Up 3D Sensors Chapter 2 Setting Up 3D Sensors Requires: 3D Sensor Newer models of the 3D Sensor (that is. Sourcefire strongly recommends that your password is at least eight alphanumeric characters of mixed case and includes at least one numeric character. enter a new password for the admin user account and for the root password for the shell account. and logging into the 3D Sensor’s web interface (as described in the 3D Sensor Installation Guide). These sensors include the following models: • • • • • • • • • 3D500 3D1000 3D2000 3D2100 3D2500 3D3500 3D4500 3D6500 3D9900 You can view illustrations of each model in the 3D Sensor Installation Guide to determine your sensor model. After physically installing the 3D Sensor. Under Change Password. To complete the initial setup: Access: Admin 1. If the initial setup is interrupted or if a second user logs in while it is underway. The same password is used for both accounts. in the New Password and Confirm fields. Avoid using words that appear in a dictionary.1 Sourcefire 3D System Administrator Guide 44 . Defense Centers use the setup process in Setting up Defense Centers on page 47. Version 4. TIP! The initial change to the admin user password changes the root password for the shell account.

under Time Settings. you must also specify the primary and secondary DNS servers.1 Sourcefire 3D System Administrator Guide 45 . 5. select Inline with Failopen Mode. specify how you want to deploy the 3D Sensor. user-created string that you will also use from within the Defense Center’s web interface when you complete the sensor registration process. Under Remote Management. its hostname. this step is unnecessary as the current software will synchronize automatically. netmask. you can specify the Defense Center as the sensor’s NTP server. You have two options: • • If you deployed the sensor as an inline IPS using paired sensing interfaces. Note that if you are managing the sensor with a Defense Center and the Defense Center itself is set up as an NTP server. resulting in unexpected network behavior. If you deployed the sensor as a passive IDS on your network. Note that if you used the configure-network script before logging into the web interface. indicate whether you want to manage the 3D Sensor with a Defense Center.9. indicate how you want to set the time for the 3D Sensor. The registration key is a single-use. Optionally. defer Defense Center management until after you complete the initial setup. and gateway fields are pre-populated with your settings. 3. the IP address. select Passive Mode. WARNING! If you select Inline with Failopen Mode when the sensor is deployed passively. if your Defense Center is running current software and your sensors are running earlier software. If your sensor and Defense Center are separated by a network address translation (NAT) device. You can set the time manually or via network time protocol (NTP) from an NTP server. Refer to Working in NAT Environments on page 112 and Adding Sensors to the Defense Center on page 117 for more information.Performing the Initial Setup Setting Up 3D Sensors Chapter 2 2. You can use the IP address of the Defense Center or. you may cause your network to be bridged. Under Network Settings. enter the settings that you want to use for the management IP address. Version 4. if you specify a DNS server. Under Detection Mode. IMPORTANT! If both your Defense Center and your sensors are running current software. Note that if you use an NTP server to set the time. 4.

indicate whether you want to add a product license to the 3D Sensor. Note that you will be prompted for the license key and an activation key.com/. You can also instruct the system to reapply intrusion policies after the SEU import completes. The activation key was previously emailed to the contact person identified on your support contract. select Update Now. Under Recurring SEU Imports. You will automatically create an RNA detection engine without a policy. refer to Using Recurring SEU Imports in the Analyst Guide. you must add a product license to the 3D Sensor. Select the state for adding new rules to intrusion policies as disabled or in the predefined default state. you do not need to add a product license. switch to a host that can and navigate to the keyserver web page. Skip to step 8. enter the license key in the license key field.sourcefire. For detailed information on adding new rules to custom policies in the default state or in the disabled rule state. check the Enable Recurring SEU Imports check box to configure automatic SEU imports and specify the update frequency. • To use IPS functionality (either by itself or with RNA or RUA functionality). To obtain a product license. You control licensing for RNA or RUA through the Defense Center managing the sensor.Performing the Initial Setup Setting Up 3D Sensors Chapter 2 6. and click Add/Verify. Under License Settings. To add a product license. You have two options: • To use only the RNA or RUA functionality without IPS. If your current host cannot access the Internet. Follow the on-screen instructions to generate an email containing the license file and paste it into the License field. Version 4. click the link to navigate to https:// keyserver.9. 7. To queue an immediate update from the Sourcefire support site.1 Sourcefire 3D System Administrator Guide 46 .

The 3D Sensor is configured according to your selections. Setting up Defense Centers Requires: DC/MDC The first time you log in to the web interface. Defense Centers and Master Defense Centers provide a simple web form to collect information about your network environment and how you intend to deploy the appliance. You will see no intrusion events until it completes. the results can be unpredictable. TIP! Applying a default policy to detection engines can take several minutes. setting up the IP address for the management interface. and logging into the Defense Center’s web interface (as described in the Defense Center Installation Guide). TIP! If you used the option to connect through the management port to perform the initial setup. If you agree to abide by its provisions. which indicates the appliance is now operational. See Using Dashboards on page 59 for more information. You can check the task progress at Operations > Monitoring > Task Status.9. A dashboard page appears after you log back in. the Install page appears so that you can continue the setup process. select the check box and click Apply. The appliance logs you out. remember to connect the cable to the protected management network. If the initial setup is interrupted or if a second user logs in while it is underway. After physically installing the Defense Center.1 Sourcefire 3D System Administrator Guide 47 . Version 4. read the agreement carefully. WARNING! Prepare for the initial setup and complete it promptly after you begin.Performing the Initial Setup Setting up Defense Centers Chapter 2 8. See What’s Next? on page 52 for some suggestions about how to proceed after you complete these initial startup pages. Under End User License Agreement.

The same password is used for both accounts. under Operational Mode.Performing the Initial Setup Setting up Defense Centers Chapter 2 To complete the initial setup: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 48 . IMPORTANT! If your Defense Center and Master Defense Center are separated by a network address translation (NAT) device. its hostname.9. Version 4. enter a new password for the admin user account and the root password shell account. the Remote Management section becomes unnecessary and is hidden from the form. 3. enter the settings that you want to use for the management IP address. 4. you can set the appliance to operate as a Defense Center or a Master Defense Center. Sourcefire strongly recommends that your password is at least eight alphanumeric characters of mixed case and includes at least one numeric character. if you specify a DNS server. see Master Defense Center and Defense Center Functional Comparison on page 159. If you are installing a DC3000. The registration key is a single-use. Under Network Settings. See Working in NAT Environments on page 112 and Adding a Master Defense Center on page 165 for more information. defer remote management until after you complete the initial setup. netmask. indicate whether you want to manage the Defense Center with a Master Defense Center. 2. and not 3D Sensors. Under Remote Management. TIP! The initial change to the admin user password changes the root password for the shell account. For more information on the differences between the features provided by a Master Defense Center and a Defense Center. Note that if you used the configure-network script before logging into the web interface. Defense Center capabilities are not a subset of a Master Defense Center. You can use the IP address of the Master Defense Center or. the IP address. Avoid using words that appear in a dictionary. and gateway fields are pre-populated with your settings. IMPORTANT! A Master Defense Center can manage only Defense Centers. Under Change Password. user-created string that you will also need to use when you register the Defense Center through the Master Defense Center’s web interface. Skip to step 5. Use the command line interface on the appliance for subsequent changes to the root password. in the New Password and Confirm fields. If you select the Master Defense Center mode.

You can set the time manually or via network time protocol (NTP) from an NTP server. defer remote management until after you complete the initial setup. You can use the IP address of the Defense Center or. you must also specify the primary and secondary DNS servers. 6. IMPORTANT! Use this function only if you have previously installed 3D Sensors that are pending registration with this Defense Center. On Defense Centers. user-created string you used in the Defense Center’s web interface when you configured remote management.Performing the Initial Setup Setting up Defense Centers Chapter 2 5. if you specify a DNS server. Click Add to register each newly listed 3D Sensors with this Defense Center. this step is unnecessary as the current software will synchronize automatically. The registration key is the single-use. IMPORTANT! If your Defense Center and Master Defense Center are separated by a network address translation (NAT) device. You can use the IP address of the 3D Sensor or. Version 4.9. you should defer remote management until after you complete the initial setup. If you are installing a DC3000 and your operational mode is Master Defense Center. if you specify a DNS server. IMPORTANT! If your Defense Center. Master Defense Center and all sensors are running current software. indicate how you want to set the time for the Defense Center. If your 3D Sensor and Defense Center are separated by a network address translation (NAT) device. Under Time Settings. user-created string used in the 3D Sensor’s web interface when you configured remote management for the sensor. See Working in NAT Environments on page 112 and Adding a Defense Center on page 168 for more information. its hostname. under Sensor Registration. indicate whether you want to apply default policies. 7.1 Sourcefire 3D System Administrator Guide 49 . Note that if you use an NTP server to set the time. Note that if you are managing the Defense Center with a Master Defense Center and the Master Defense Center itself is set up as an NTP server. Refer to Working in NAT Environments on page 112 and Adding Sensors to the Defense Center on page 117 for more information. Use these fields only to register Defense Centers where you have already configured remote management by this Master Defense Center. The registration key is the single-use. the Defense Center Registration portion of the form is visible. you can specify the Master Defense Center as the Defense Center’s NTP server. its hostname.

The Defense Center or Master Defense Center is configured according to your selections. You can also instruct the system to reapply intrusion policies after the SEU import completes. select the check box and click Apply. Note that you will be prompted for the license key and an activation key. To queue an immediate update from the Sourcefire support site.com/. Under Recurring SEU Imports. Select the state for adding new rules to intrusion policies as disabled or in the predefined default state. To obtain a product license. See Using Dashboards on page 59 for more information. The activation key was previously emailed to the contact person identified on your support contract. Follow the on-screen instructions to generate an email containing the license file and paste it into the License field. which indicates the appliance is operational. add a product license and any required feature licenses to the Defense Center. If your current host cannot access the Internet. 9. 10.1 Sourcefire 3D System Administrator Guide 50 . click the link to navigate to https:// keyserver. Communication Ports The Sourcefire 3D System requires the use of specific ports to communicate internally and externally. See What’s Next? on page 52 for some suggestions about how to proceed after you complete these initial startup pages.9.sourcefire. and to enable Version 4.The appliance logs you out. Under License Settings. select Update Now. A dashboard page appears after you log back in. Under End User License Agreement. switch to a host that can and navigate to the keyserver web page.If you agree to abide by its provisions. remember to connect the cable to the protected management network. read the agreement carefully. TIP! If you used the option to connect through the management port to perform the initial setup. between Defense Centers and sensors.Performing the Initial Setup Communication Ports Chapter 2 8. For detailed information on adding new rules to custom policies in the default state or in the disabled rule state see Using Recurring SEU Imports in the Analyst Guide. check the Enable Recurring SEU Import check box to configure automatic SEU imports and specify the update frequency.

Open this port for communicatiosn between the Defense Center and RUA Agents. Required Open Ports Ports 20. Refer to the Required Open Ports table for more information on functions and their associated ports.1 Sourcefire 3D System Administrator Guide 51 .Performing the Initial Setup Communication Ports Chapter 2 certain functionality within the network deployment. Open this port for communications between the Defense Center and Intrusion Agents. 21 22 23 25 53 67 68 . 80 162 389. Open this port when you connect to a remote web server through the RSS widget. Notes Version 4.9. 636 443 514 1241 1660 1812 and 1813 3306 8301 Description ftp ssh/ssl telnet smtp dns dhcp http snmp ldap https syslog Nessus Nmap FreeRADIUS RUA Agent Intrustion Agent Note that you must open both ports to ensure that FreeRADIUS functions correctly. Open this port only if you are using a remote syslog server.

if your Defense Center or 3D Sensor must be licensed for IPS. For deployments that include a Defense Center. your next steps depend on the role assigned to your user account (Administrator user. Policy & Response Administrator user. which are based on the user account privileges required for the task. Maintenance user. Requires: RNA. or RNA Event Analyst user) and what appliance you are using. Maintenance User Tasks on page 54 explain some of the steps in the process that Maintenance users can perform after Administrator users finish their required tasks. • • Version 4. IMPORTANT! Tasks that must be completed on specific hardware or software platforms are indicated by special text: For example. or RUA. Review the tasks in the following sections. Similarly. Notes What’s Next? Requires: Any After you complete the initial setup for the Sourcefire 3D System.1 Sourcefire 3D System Administrator Guide 52 . a user with Administrator access must perform the first steps. For standalone 3D Sensor deployments (that is. deployments that do not include a Defense Center and do not use RNA). tasks that require a Defense Center are preceded with Requires: DC.x 3D Sensors. the task is preceded with Requires: IPS. or Requires: RUA. See Managing Users on page 264 for more information about user roles. Intrusion Event Analyst user. you can perform much of the process on the Defense Center itself.Performing the Initial Setup What’s Next? Chapter 2 Required Open Ports (Continued) Ports 8302 8305 18183 Description eStreamer Management Virtual Network OPSEC SAM Open this port for communications between the Defense Center and v. 4.9. • Administrator User Tasks on page 53 describe the steps that you must complete before Policy & Response Administrator users and analyst users can begin their tasks. RNA.8. Policy & Response Administrator User Tasks on page 55 describe some of the policies and custom rules that Policy & Response Administrator users can create and apply so that analyst users receive useful data for their analyses.

you should set it up now. Intrusion Event Analyst User Tasks on page 57 describe the features that Intrusion Event Analyst users can use to learn about the kinds of attacks that are launched against assets on your network. 3. In most network environments. Administrator User Tasks Requires: Any Administrator users have a superset of tasks. but you cannot use high availability mode directly on the Master Defense Center itself.9. If you want to manage your 3D Sensors with a Defense Center but did not enable remote management as part of the initial setup on the sensor.Performing the Initial Setup What’s Next? Chapter 2 • • RNA Event Analyst User Tasks on page 56 describe the features that RNA Event Analyst users can use to learn about the assets on your network. The first steps for the Administrator user are as follows: Access: Admin 1. 2. Sourcefire recommends that you use the Defense Center’s web interface rather than the sensor’s web interface to manage the sensor and view the events that it generates. set up high availability as explained in Configuring High Availability on page 145. TIP! After you set up management. Requires: DC If you want to authenticate users using an external authentication server. TIP! You can use high availabilty mode on Defense Centers which are managed by a Master Defense Center. Version 4.1 Sourcefire 3D System Administrator Guide 53 . See Configuring Remote Access to the Defense Center on page 386 for information about setting up management links between your sensors and the Defense Center. Requires: DC If you are deploying two Defense Centers in high availability mode. the sensors you add to the primary Defense Center are automatically added to the secondary Defense Center. You must complete the steps outlined in Working with Sensors on page 113 on the Defense Center and on the sensors to complete the process. Tasks essential to initial setup are listed below. you must create an authentication object for that server as described in Creating LDAP Authentication Objects on page 269.

Maintenance User Tasks Requires: Any After a user with Administrator privileges performs the initial configuration as described in Setting Up 3D Sensors on page 44. a Maintenance user or an Administrator user can perform the following tasks: Version 4. Maintenance User Tasks. You can also create different policies on your Defense Center and apply them to the managed sensors where it is appropriate. you should configure one that meets the needs of your network and security environment. and Security Enhancement Updates (SEUs) and apply them to your Defense Center where required. 8. By default. See Importing SEUs and Rule Files in the Analyst Guide and Updating System Software on page 398 for more information. Note that a Maintenance user can also set up health policies. See Using Detection Engines and Interface Sets on page 185 for more information about examining traffic on multiple network segments with a single sensor. Check for any available software patches. The next section. The auditing feature records events based on the user account name. See Managing Users on page 264 for more information. The health monitoring feature includes a range of modules that you can enable or disable based on the needs of your network environment. Create new user accounts that match the roles you want to assign to your users.9. vulnerability database updates. you need to enable it in a system policy on the Defense Center and apply that policy to any appliances where users will authenticate to the external server. Note that. Patches and updates are available on the Sourcefire Support site.1 Sourcefire 3D System Administrator Guide 54 .Performing the Initial Setup What’s Next? Chapter 2 4. if you want to use external authentication. Apply any available software patches or vulnerability database updates to managed sensors where required. If you did not already set up a system policy as part of the initial setup. so it is much better to have an account for each user rather than allowing multiple users to access the appliance from one or two accounts. describes the steps that a user with Maintenance access can perform. you must modify the default detection engine. 6. Requires: DC Set up health monitoring policies and apply them to your managed sensors and to the Defense Center itself. See Using Health Monitoring on page 482 for more information. See Managing System Policies on page 320 for more information. To take advantage of the multiple detection engine feature. 7. 5. each 3D Sensor has a single detection engine that encompasses all of the available sensing interfaces (or all of the available fast-packetenabled interfaces) on the sensor.

including anomalous network traffic patterns. sending a notification by email or SNMP or simply generating a syslog alert. Requires: IPS Part of the process for creating an intrusion policy includes enabling the appropriate intrusion rules and fine-tuning the preprocessors and packet decoders to match your network traffic. you can set up and apply health policies on your managed sensors and the Defense Center. Requires: RNA If a compliance policy violation occurs. Requires: DC If a user with Administrator privileges has not configured health monitoring. 3. Policy & Response Administrator User Tasks. Set up scheduled tasks for any jobs that you want to perform on a regular basis. Policy & Response Administrator users can: Access: P&R Admin/ Admin 1. See Using Backup and Restore on page 413 for details about backing up configurations as well as event data. 4. 2. Policy & Response Administrator User Tasks Requires: Any After a user with Administrator privileges performs the initial configuration as described in Setting Up 3D Sensors on page 44. responses.Performing the Initial Setup What’s Next? Chapter 2 To continue the initial setup. The next section. See Managing Intrusion Rules in the Analyst Guide and Using Advanced Settings in an Intrusion Policy in the Analyst Guide for more in-depth information about configuring intrusion policies. See Using Basic Settings in an Intrusion Policy in the Analyst Guide for more information. 3. Maintenance users can: Access: Maint/Admin 1. Develop a backup and restore plan.1 Sourcefire 3D System Administrator Guide 55 . Note that you can also schedule regular backups of your appliance. you can specify that the Defense Center automatically respond to it in one of several ways. Requires: IPS Create and apply intrusion policies to the IPS-related detection engines on your 3D Sensor. Version 4. See Using Health Monitoring on page 482 for more information. For more information on . describes the steps that a user with Policy & Response Administrator access can perform. See Scheduling Tasks on page 425 for more information. 2. See Configuring Compliance Policies and Rules in the Analyst Guide. Compliance policies can contain rules based on nearly any kind of network activity that your 3D Sensor can detect. see Configuring Responses for Compliance Policies in the Analyst Guide. including blocking a suspect host at the firewall or router.9. a Policy & Response Administrator user or an Administrator user can perform the following tasks: To continue the initial setup. Requires: RNA Set up compliance policies to determine when prohibited activity occurs on your network.

describe the steps that a user with Intrusion Event Analyst. 6. RNA Event Analyst User Tasks and Intrusion Event Analyst User Tasks. use the host profile feature to learn more about them. See Using Host Profiles in the nAnalyst Guide for more information.Performing the Initial Setup What’s Next? Chapter 2 5. If your network environment includes an OPSEC-compliant firewall. RNA Event Analyst. The network map provides you with an overview of your network and is a good tool for locating rogue access points. RNA Event Analyst (Read-Only). 2. but their event views are limited to specific IP address ranges. 3. unknown hosts. Restricted Event Analyst users can perform most of these tasks. you can also send SAM-based responses to the firewall. Similarly. Requires: RNA Review the information in the network map. RNA Event Analyst (Read Only) users can perform any of these tasks. Begin by reviewing the summary statistics. Intrusion Event Analyst (Read-Only). which is an expandable tree view of all the hosts and services reported by RNA. or Restricted Event Analyst access can perform. or via SNMP) if a specific intrusion rule is triggered. See Using the Network Map in the Analyst Guide for more information. via email. an RNA Event Analyst user or an Administrator user can perform the tasks listed below. which can provide you with a high-level view of the activity and events taking place on your network. See Understanding and Writing Intrusion Rules in the Analyst Guide and Rule-Writing Examples and Tips in the Analyst Guide to learn more about using the rule editor to write your own intrusion rules. and services that are prohibited by your security policies. you may want to write your own rules to meet the unique needs of your network. consider setting up automated notifications (that can be sent to the syslog. Version 4. To continue the initial setup. Requires: IPS As you gain more experience with the intrusion rules provided by Sourcefire. Requires: RNA If you locate unknown hosts on the network map. RNA Event Analyst users can: Access: Any RNA/ Admin 1. See Configuring External Responses to Intrusion Events in the Analyst Guide for more information. You can also use the host profile to set host criticality and to learn about the vulnerabilities reported for the operating system and services running on each host. The policies and rules that you create as a Policy & Response Administrator user determine the kinds of events that are seen by the RNA Event Analyst and Intrusion Event Analyst users on your appliance. The next sections.1 Sourcefire 3D System Administrator Guide 56 . Requires: IPS To ensure that your intrusion event analysts are informed as soon as possible regarding attacks against your most valuable network assets. See Viewing RNA Event Statistics in the Analyst Guide for more information.9. RNA Event Analyst User Tasks Requires: Any After a user with Administrator privileges performs the initial configuration as described in Setting Up 3D Sensors on page 44.

Requires: RNA Use flow data and traffic profiles to gain a different kind of insight into the activity on your network.9. You can use the scheduler to automate reporting. Most of these can be performed by Restricted Event Analyst users also. or PDF-based event and incident reports. Use any of the predefined workflows to view. As you grow more experienced with the Sourcefire 3D System. 5. See Understanding and Using Workflows in the Analyst Guide for more information. an Intrusion Event Analyst user or an Administrator user can perform the tasks listed below.1 Sourcefire 3D System Administrator Guide 57 . See Working with RNA Events in the Analyst Guide for more information. See Working with Event Reports on page 232 for more information. Version 4. You can automatically email a report when it is complete. 6. services. investigate. Intrusion Event Analyst User Tasks Requires: Any After a user with Administrator privileges performs the initial configuration as described in Setting Up 3D Sensors on page 44. You can review information for network hosts. Note that flow data is collected by your sensors only if the flow data option is enabled in the RNA detection policy. HTML. you can review the information collected by RNA’s traffic monitoring features and identify hightraffic hosts.Performing the Initial Setup What’s Next? Chapter 2 4. See Working with Flow Data and Traffic Profiles in the Analyst Guide for more information. Use the report designer to create CSV. then determine which might be behaving abnormally. and you can create and save report profiles to use later. 7. but their event views are limited to specific IP address ranges. You can also use the extensive search capability to define and save your own search criteria that you can use as part of your regular analysis. See Scheduling Tasks on page 425. For example. Requires: RNA Use the RNA event workflows to review the activity that has occurred on your network over time. and act on the events generated by your sensors. Note that the kinds of RNA events that are logged to the database are determined by the system policy on the managing Defense Center. and host attributes. client applications. vulnerabilities. you may want to create your own workflows.

1 Sourcefire 3D System Administrator Guide 58 . You can use an incident to record details about your investigation. 2. and the appliance automatically records the amount of time you have the incident open. See Working with Event Reports on page 232 for more information. and act on the events generated by your sensors. See Using Impact Flags to Evaluate Events in the Analyst Guide for more information. 3. As you grow more experienced with the Sourcefire 3D System.Performing the Initial Setup What’s Next? Chapter 2 To continue the initial setup. You can automatically email a report when it is complete. You can use the scheduler to automate reporting. HTML. See Scheduling Tasks on page 425. Events with high impact are more likely to indicate that an attack is targeted against a vulnerable host on your network. Version 4.9. investigate. Intrusion Event Analyst users can: Access: Any IPS/ Admin 1. which can provide you with a high-level view of the activity and events taking place on your network. 5. Requires: IPS Use the intrusion event views to determine which hosts on your network are the targets of attacks and the types of attacks that are attempted against them. Use any of the predefined workflows to view. See Working with Intrusion Events in the Analyst Guide for more information. See Understanding and Using Workflows in the Analyst Guide for more information. intrusion events are correlated with any available RNA data to generate an impact flag. See Handling Incidents in the Analyst Guide for more information. or PDF-based event and incident reports. Requires: RNA Note that on the Defense Center. Note that the events that you see are limited by the options that are enabled in the intrusion policy that is applied to your sensors. 4. Requires: IPS Use the incident handling feature to collect information about your investigation of possible intrusions on your network. You can also add intrusion event data that you believe might be important to your investigation of the incident. and you can create and save report profiles to use later. you may want to create your own workflows. See Viewing Intrusion Event Statistics in the Analyst Guide for more information. Begin by reviewing the summary statistics. Use the report designer to create CSV.

Note that because not all widgets are useful for all types of appliances. Defense Center. each of which can display one or more widgets in a three-column layout. as well as information about the status and overall health of the appliances in your deployment. the default dashboard differs depending on whether you are using a Master Defense Center. current version of the Sourcefire 3D System software running on the appliance. named Default Dashboard. Each dashboard has a time range that constrains its widgets.9.Administrator Guide Sourcefire 3D System dashboards provide you with at-a-glance views of current system status. This dashboard provides the casual user with basic event and system status information for your Sourcefire 3D System deployment. Each type of appliance is delivered with a default dashboard. including data about the events collected and generated by the Sourcefire 3D System. and its remote manager.Using Dashboards Chapter 3 . self-contained components that provide insight into different aspects of the Sourcefire 3D System. the Appliance Information widget tells you the appliance name. Widgets are small. Each dashboard has one or more tabs. The Sourcefire 3D System is delivered with several predefined widgets. model.1 Sourcefire 3D System Administrator Guide 59 . For example. You can change the time range to reflect a period as short as the last hour or as long as the last year. or 3D Sensor. Version 4.

each of which can display one or more widgets in a three-column layout. The Sourcefire 3D System is delivered with several predefined dashboard widgets. or you can create a custom dashboard solely for your own use. and includes multiple widgets that summarize collected IPS.1 Sourcefire 3D System Administrator Guide 60 . see Viewing Dashboards on page 91. You can also set a custom dashboard as your default dashboard. RNA. You can share custom dashboards among all users of an appliance. • The Detailed Dashboard provides advanced users with detailed information about your Sourcefire 3D System deployment. modify the predefined dashboards.9. although you can configure your appliance to display a different default home page. You can use the predefined dashboards. see Understanding Flow Data in the Analyst Guide. the home page for your appliance displays the default dashboard. TIP! If you change the home page. In addition to the default dashboard. Note that Restricted Event Analysts use the Flow Summary page instead of the Flow Summary Dashboard. see Viewing the Flow Summary Page in the Analyst Guide for more information. including pages that are not dashboard pages. and system status data. compliance. you can access dashboards by selecting Analysis & Reporting > Event Summary > Dashboards. the Defense Center is delivered with two other predefined dashboards: • The Flow Summary dashboard uses flow data to create tables and charts of the activity on your monitored network. see the following sections: • • • Understanding Dashboard Widgets on page 60 Understanding the Predefined Widgets on page 65 Working with Dashboards on page 89 Understanding Dashboard Widgets Requires: Any Each dashboard has one or more tabs. each of which provides insight into a Version 4. for more information on flow summary data.Using Dashboards Understanding Dashboard Widgets Chapter 3 By default. For more information. or create a custom dashboard to suit your needs. For more information.

9. RNA events. An unauthorized widget is one that you cannot view because you do not have the necessary account privileges. or RNA Event Analyst account privileges.1 Sourcefire 3D System Administrator Guide 61 . the Master Defense Center cannot access flow data. These widgets are disabled and display error messages that indicate the reason why you cannot view them.Using Dashboards Understanding Dashboard Widgets Chapter 3 different aspect of the Sourcefire 3D System. The dashboard widgets that you can view depend on the type of appliance you are using and on your user role: • • An invalid widget is one that you cannot view because you are using the wrong type of appliance. while the Compliance Events widget is available only on the Defense Center for users with Administrator. see: • • • • Understanding Widget Availability on page 61 Understanding Widget Preferences on page 64 Understanding the Predefined Widgets on page 65 Working with Dashboards on page 89 Understanding Widget Availability Requires: Any The Sourcefire 3D System is delivered with several predefined dashboard widgets. if you import a dashboard created either on a different kind of appliance or by a user with different access privileges. RUA events. You can minimize and maximize widgets. Currently the only widget in this category displays an RSS feed. as well as rearrange the widgets on a tab. Also note that widgets cannot display data to which an appliance has no access. In addition. Miscellaneous widgets display neither event data nor operations data. Operations widgets display information about the status and overall health of the Sourcefire 3D System. each dashboard has a set of preferences that determines its behavior. For more information. The dashboard widgets that you can view depend on the type of appliance you are using and on your user role. the Appliance Information widget is available on all appliances for all user roles. If you import a dashboard onto a Master Defense Center that contains a Custom Analysis widget configured to display one of those data types. Version 4. add and remove widgets from tabs. Intrusion Event Analyst. Although you cannot add an unauthorized or invalid widget to a dashboard. For example. that dashboard may contain unauthorized or invalid widgets. For example. the widget displays an error message. Widgets are grouped into three categories: • • • Analysis & Reporting widgets display data about the events collected and generated by the Sourcefire 3D System. and so on.

Using Dashboards Understanding Dashboard Widgets Chapter 3 Similarly. see Minimizing and Maximizing Widgets on page 97 and Deleting Widgets on page 97. Sourcefire Appliances and Dashboard Widget Availability Widget Appliance Information Appliance Status Compliance Events Current Interface Status Current Sessions Custom Analysis Disk Usage Interface Traffic Intrusion Events Network Compliance Product Licensing Product Updates RSS Feed X X Master Defense Center X X X X X X X X X Defense Center X X X X X X X X X X X X X X X X X X X X X X X X X X X X X 3D Sensor with IPS (and RNA) X 3D Sensor with RNA (only) X Version 4. An X indicates that the appliance can display the widget. the Current Interface Status widget on a 3D Sensor displays the status of its sensing interfaces. as well as widgets that display no data. the content of a widget can differ depending on the type of appliance you are using. keeping in mind that modifying a widget on a shared dashboard modifies it for all users of the appliance. Note than any content generated in table format can be sorted by clicking on the table column header. but on Defense Centers and Master Defense Centers the widget displays only the status of the management interface. The Sourcefire Appliances and Dashboard Widget Availability table lists the valid widgets for each appliance.1 Sourcefire 3D System Administrator Guide 62 . You can delete or minimize unauthorized and invalid widgets.9. For example. For more information.

Using Dashboards Understanding Dashboard Widgets Chapter 3 Sourcefire Appliances and Dashboard Widget Availability (Continued) Widget System Load System Time White List Events Master Defense Center X X X Defense Center X X X 3D Sensor with IPS (and RNA) X X 3D Sensor with RNA (only) X X The User Roles and Dashboard Widget Availability table lists the user account privileges required to view each widget.1 Sourcefire 3D System Administrator Guide 63 . IMPORTANT! dashboards. User accounts with Restricted Event Analyst access cannot use User Roles and Dashboard Widget Availability Widget Appliance Information Appliance Status Compliance Events Current Interface Status Current Sessions Custom Analysis Disk Usage Interface Traffic Intrusion Events Network Compliance Product Licensing Administrator X X X X X X X X X X X X X X X X X X X X X X X X X Maintenance X X P&R Admin X IPS Analyst X X X X RNA Analyst X X X X Version 4.9. An X indicates the user can view the widget.

the following graphic shows the preferences for the Current Interface Status widget. the following graphic shows the preferences for the Custom Analysis widget. which is a highly customizable widget that allows you to display detailed information on the events collected and generated by the Sourcefire 3D System.9. On the title bar of the widget whose preferences you want to change. The preferences section for that widget appears. click the show preferences icon ( ). To modify a widget’s preferences: Access: Any except Restricted 1.Using Dashboards Understanding Dashboard Widgets Chapter 3 User Roles and Dashboard Widget Availability (Continued) Widget Product Updates RSS Feed System Load System Time White List Events Administrator X X X X X Maintenance X X X X P&R Admin X X X X X X X X X X X X IPS Analyst RNA Analyst Understanding Widget Preferences Requires: Any Each widget has a set of preferences that determines its behavior. which displays the current status of the network interfaces for the appliance.1 Sourcefire 3D System Administrator Guide 64 . For example. Version 4. For example. You can only configure the update frequency for this widget. Widget preferences can also be more complex. Widget preferences can be simple.

For information on the preferences you can specify for individual widgets. see the following sections: • • • • • • • • • • • • • • • • Understanding the Appliance Information Widget on page 66 Understanding the Appliance Status Widget on page 67 Understanding the Compliance Events Widget on page 67 Understanding the Current Interface Status Widget on page 68 Understanding the Current Sessions Widget on page 69 Understanding the Custom Analysis Widget on page 69 Understanding the Disk Usage Widget on page 80 Understanding the Interface Traffic Widget on page 81 Understanding the Intrusion Events Widget on page 81 Understanding the Network Compliance Widget on page 82 Understanding the Product Licensing Widget on page 84 Understanding the Product Updates Widget on page 85 Understanding the RSS Feed Widget on page 86 Understanding the System Load Widget on page 87 Understanding the System Time Widget on page 87 Understanding the White List Events Widget on page 88 IMPORTANT! The dashboard widgets you can view depend on the type of appliance you are using and on your user role. see Understanding Widget Availability on page 61.1 Sourcefire 3D System Administrator Guide 65 . when used on dashboards. see Understanding the Predefined Widgets on page 65. Your changes take effect immediately. Make changes as needed. For more information. Version 4. 3. ) to hide the Understanding the Predefined Widgets Requires: Any The Sourcefire 3D System is delivered with several predefined widgets that. On the widget title bar. as well as information about the status and overall health of the appliances in your deployment. click the hide preferences icon ( preferences section. including data about the events collected and generated by the Sourcefire 3D System. can provide you with at-a-glance views of current system status. For detailed information on the widgets delivered with the Sourcefire 3D System.Using Dashboards Understanding the Predefined Widgets Chapter 3 2.9.

operating system. Version 4. rule pack.1 Sourcefire 3D System Administrator Guide 66 . and Sourcefire 3D System software and operating system versions of the peer Defense Center. the name and status of the communications link with the managing appliance for Defense Centers in a high availability pair. and vulnerability database (VDB) installed on the appliance for managed appliances. see Understanding Widget Preferences on page 64. management interface IP address. model. For more information. module pack. Snort. the preferences also control how often the widget updates. the name.9. as well as how recently the Defense Centers made contact • • You can configure the widget to display more or less information by modifying the widget preferences to display a simple or an advanced view. and model of the appliance the versions of the Sourcefire 3D System software. The widget provides: • • the name.Using Dashboards Understanding the Predefined Widgets Chapter 3 Understanding the Appliance Information Widget Requires: Any The Appliance Information widget provides a snapshot of the appliance. SEU.

9. see Understanding Widget Preferences on page 64. The preferences also control how often the widget updates. For more information. over the dashboard time range. For more information. Version 4. You can configure the widget to display appliance status as a pie chart or in a table by modifying the widget preferences. Note that because the Defense Center does not automatically apply a health policy to managed sensors.1 Sourcefire 3D System Administrator Guide 67 . you must manually apply a health policy or their status appears as Disabled. see Using the Health Monitor on page 545. Understanding the Compliance Events Widget Requires: DC/MDC The Compliance Events widget shows the average events per second by priority.Using Dashboards Understanding the Predefined Widgets Chapter 3 Understanding the Appliance Status Widget Requires: DC/MDC The Appliance Status widget indicates the health of the appliance and of any appliances it is managing. You can click a section on the pie chart or one of the numbers on the appliance status table to go to the Health Monitor page and view the compiled health status of the appliance and of any appliances it is managing.

accessing compliance events via the dashboard changes the events (or global) time window for the appliance. the events are constrained by the dashboard time range.Using Dashboards Understanding the Predefined Widgets Chapter 3 You can configure the widget to display compliance events of different priorities by modifying the widget preferences. Select Show All to display an additional graph for all compliance events. Understanding the Current Interface Status Widget Requires: Any The Current Interface Status widget shows the status of the network interfaces for the appliance. regardless of priority. see Understanding Widget Preferences on page 64. passive. the widget provides: • • • the name of the interface the link state of the interface. You can click a graph to view compliance events of a specific priority. including events that do not have a priority. For each interface. grouped by type: management. and unused. or click the All graph to view all compliance events.9. In either case.1 Sourcefire 3D System Administrator Guide 68 . as well as to select a linear (incremental) or logarithmic (factor of ten) scale. 100Mb full duplex. see Viewing Compliance Events in the Analyst Guide. For more information. inline. Note that only 3D Sensors have interface types other than the management interface. Select one or more Priorities check boxes to display separate graphs for events of specific priorities. The preferences also control how often the widget updates. For more information on compliance events. or 10Mb half duplex) of the interface Version 4. represented by a green ball (up) or a gray ball (down) the link mode (for example.

For more information. The presets serve as examples and can provide quick access to information about your deployment. you can: • • click any user name to manage user accounts on the User Management page. you must select which table and individual field you want to display. and the last time each user accessed a page on the appliance (based on the local time for the appliance). copper or fiber the amount of data received (Rx) and transmitted (Tx) by the interface The widget preferences control how often the widget updates.Using Dashboards Understanding the Predefined Widgets Chapter 3 • • the type of interface. that is. as well as the aggregation method that configures how the widget groups the data it displays. the IP address of the machine where the session originated. Understanding the Current Sessions Widget Requires: Any The Current Sessions widget shows which users are logged into the appliance. For more information. The Custom Analysis widget is delivered with several presets. You can use these presets or you can create a custom configuration. which are groups of configurations that are predefined by Sourcefire. On the Current Sessions widget. see Viewing Audit Records on page 567 • The widget preferences control how often the widget updates. see Using Host Profiles in the nAnalyst Guide (Defense Center with RNA only) click any IP address or access time to view the audit log constrained by that IP address and by the time that the user associated with that IP address logged on to the web interface. Understanding the Custom Analysis Widget Requires: Any The Custom Analysis widget is a highly customizable widget that allows you to display detailed information on the events collected and generated by the Sourcefire 3D System.9. When you configure the widget preferences. see Managing User Accounts on page 299 click the host icon ( ) next to any IP address to view the host profile for that computer. that is.1 Sourcefire 3D System Administrator Guide 69 . see Understanding Widget Preferences on page 64. Version 4. see Understanding Widget Preferences on page 64. The user that represents you. is marked with a user icon and is rendered in bold type. the user currently viewing the widget.

constraining the first example (operating systems Version 4.Using Dashboards Understanding the Predefined Widgets Chapter 3 For example. Aggregating this data by Count tells you how many hosts are running each operating system. On the other hand. Mac OS X.9. how many unique versions of Linux. Optionally. For example. Microsoft Windows. you can further constrain the widget using a saved search. aggregating by Unique OS tells you how many unique versions of each operating system are running on the same hosts (for example. either one of the predefined searches delivered with your appliance or a custom search that you created. you can configure the Custom Analysis widget to display which operating systems are running on the hosts in your organization by configuring the widget to display OS data from the RNA Hosts table.1 Sourcefire 3D System Administrator Guide 70 . if you are using Sourcefire RNA as part of your deployment. and so on).

You can also configure the widget to display the most frequently occurring events or the least frequently occurring events. To change the sort order. if you set the dashboard time range to a year.1 Sourcefire 3D System Administrator Guide 71 . The up-arrow icon ( ) indicates that the event has moved up in the standings since the last time the widget updated. For example. hover your pointer over the Last updated notice in the bottom left corner of the widget. you should read the bars from right to left. The widget updates with a frequency that depends on the dashboard time range. the widget updates every five minutes. the widget updates once a week. you can configure the Custom Analysis widget to display a line graph. A downward-pointing icon indicates descending order. The colored bars in the widget background show the relative number of occurrences of each event. A number indicating how many places the event has moved down appears next to the icon. To determine when the dashboard will update next. The direction icon ( ) indicates and controls the sort order of the display. such as one that displays the total number of intrusion events generated in your deployment over Version 4. If you want information on events or other collected data over time.9. • The widget displays the last time it updated.Using Dashboards Understanding the Predefined Widgets Chapter 3 aggregated by Count) using the Local Systems search tells you how many hosts within one hop of your 3D Sensors are running each operating system. if you set the dashboard time range to an hour. A number indicating how many places the event has moved up appears next to the icon. On the other hand. click the icon. You can change the color of the bars as well as the number of rows that the widget displays. the widget can display one of three icons to indicate any additions or movement from the most recent results: • • The new event icon ( ) signifies that the event is new to the results. an upwards-pointing icon indicates ascending order. based on the local time of the appliance. The down-arrow icon ( ) indicates that the event has moved down in the standings since the last time the widget updated. Next to each event.

To configure a Custom Analysis widget.1 Sourcefire 3D System Administrator Guide 72 . For graphs over time. you should remove the widget. From Custom Analysis widgets.Using Dashboards Understanding the Predefined Widgets Chapter 3 time. Version 4. a red-shaded Custom Analysis widget indicates that its use is harming system performance. a line graph). IMPORTANT! Depending on how they are configured. the Custom Analysis widget has preferences that determines its behavior. If the widget continues to stay red over time. Custom Analysis widgets can place a drain on an appliance’s resources. Finally. a bar graph). show the preferences as described in Understanding Widget Preferences on page 64. A different set of preferences appears depending on whether you configure the widget to show relative occurrences of events (that is. For more information. you can choose a custom title for the widget. workflows) that provide detailed information about the events displayed in the widget. you can choose the time zone that the widget uses as well as the color of the line. you can invoke event views (that is. or you configure the widget to show a graph over time (that is. see the following sections: • • • Configuring the Custom Analysis Widget on page 72 Viewing Associated Events from the Custom Analysis Widget on page 78 Custom Analysis Widget Limitations on page 79 Configuring the Custom Analysis Widget Requires: Any As with all widgets.9.

1 Sourcefire 3D System Administrator Guide 73 . Preset the preset for the widget. For a detailed list of presets.Using Dashboards Understanding the Predefined Widgets Chapter 3 To configure the widget to show a bar graph. the title of the widget. The Custom Analysis widget is delivered with several presets. select Time from the Field drop-down list. the appliance uses the configured event type as the widget title. The following table describes the various preferences you can set in the Custom Analysis widget. Custom Analysis Widget Preferences Use this preference.9.. Title To control. You can use these presets or you can create a custom configuration. Version 4. The presets serve as examples and can provide quick access to information about your deployment. as shown in the following graphic. select any value except Time from the Field drop-down list.. as shown in the following graphic. see the Custom Analysis Widget Presets table on page 75. To configure the widget to show a line graph. If you do not specify a title.. which are groups of configurations that are predefined by Sourcefire..

. Search the saved search you want to use to further constrain the data that the widget displays.9. the specific field of the event type you want to display. although some presets use predefined searches.. Aggregate the aggregation method for the widget. You do not have to specify a search. The following table describes the available presets for the Custom Analysis widget. The aggregation method configures how the widget groups the data it displays. which time zone you want to use to display results. in increments of five. TIP! To display a graph over time.. the number of results rows you want to display. select Time. Defense Center predefined dashboard uses Version 4. You can display from 10 to 25 result rows. Show Movers Time Zone whether you want to display the icons that indicate additions or movement from the most recent results. It also indicates which.Using Dashboards Understanding the Predefined Widgets Chapter 3 Custom Analysis Widget Preferences (Continued) Use this preference. Color the color of the bars in the widget background that show the relative number of occurrences of each result. Table Field To control. The time zone appears whenever you select a time-based field.. For most event types.1 Sourcefire 3D System Administrator Guide 74 . the default aggregation criterion is Count. Show Results whether you want to display the most frequently occurring events (Top) or the least frequently occurring events (Bottom). the table of events which contains the event data the widget displays. if any.

based on the number of detected flows. Custom Analysis Widget Presets Preset All Intrusion Events Description Displays a graph of the total number of intrusion events on your monitored network over the dashboard time range. by classification. Displays the most active client applications on your monitored network. by classification. Displays the most active hosts on your monitored network.Using Dashboards Understanding the Predefined Widgets Chapter 3 each preset. based on the number of flows where the host initiated the session. Displays counts for the most frequently occurring intrusion events. (The predefined dashboards on the Master Defense Center and 3D Sensor do not include Custom Analysis widgets.) . Displays the most frequently occurring types of intrusion events. Displays the most active ports on your monitored network. by application type. where the packet was dropped. based on the number of flows where the host was the responder in the session. Displays the most active hosts on your monitored network. Displays the most active services on your monitored network. based on the number of detected flows. Predefined Dashboards Default Dashboard Detailed Dashboard Detailed Dashboard Requires IPS or DC/MDC + IPS All Intrusion Events (Not Dropped) IPS or DC/MDC + IPS Client Applications Detailed Dashboard DC + RNA Dropped Intrusion Events Default Dashboard IPS or DC/MDC + IPS Flows by Initiator IP Flow Summary DC + RNA Flows by Port Flow Summary DC + RNA Flows by Responder IP Flow Summary DC + RNA Flows by Service Flow Summary DC + RNA Version 4.9.1 Sourcefire 3D System Administrator Guide 75 . where the packet was not dropped as part of the event.

based on event classification. Displays the most common operating system.9.1 Sourcefire 3D System Administrator Guide 76 . Displays a count of intrusion event requiring analysis. based on the number of intrusion events where the host was the attacking host in the flow that caused the event. Displays the most active hosts on your monitored network. based on the number of intrusion events where the host was the targeted host in the flow that caused the event. Displays the most common RNA service vendors. Predefined Dashboards Flow Summary Requires DC + RNA Intrusion Events Requiring Analysis Intrusion Events by Hour Intrusion Events to High Criticality Hosts Detailed Dashboard DC/MDC + IPS + RNA IPS or DC/MDC + IPS DC/MDC + IPS + RNA none Detailed Dashboard Operating Systems Detailed Dashboard DC + RNA Services Detailed Dashboard DC + RNA Top Attackers Default Dashboard IPS or DC/MDC + IPS Top Targets Default Dashboard IPS or DC/MDC + IPS Version 4. based on the number of intrusion events occurring on high criticality hosts.Using Dashboards Understanding the Predefined Widgets Chapter 3 Custom Analysis Widget Presets (Continued) Preset Flows over Time Description Displays a graph of the total number of flows on your monitored network. based on the number of hosts running each operating system within your network. based on the number of hosts on the network running services made by that vendor. Displays the most active hours of the day. Displays the most active hosts on your monitored network. Displays the most frequently occurring types of intrusion events. over the dashboard time range. based on frequency of intrusion events.

based on the number of kilobytes per second of data transmitted by the hosts. based on the number of kilobytes per second of data received by the hosts. based on the total number of kilobytes of data received by the hosts where those users are logged in.9.Using Dashboards Understanding the Predefined Widgets Chapter 3 Custom Analysis Widget Presets (Continued) Preset Traffic by Initiator IP Description Displays the most active hosts on your monitored network. based on the number of kilobytes per second of data transmitted via the port. Displays the most active responder ports on your monitored network. Displays the most active services on your monitored network. Predefined Dashboards Detailed Dashboard Flow Summary Requires DC + RNA Traffic by Initiator User Detailed Dashboard DC + RNA + RUA Traffic by Port Flow Summary DC + RNA Traffic by Responder IP Detailed Dashboard Flow Summary DC + RNA Traffic by Service Detailed Dashboard Flow Summary DC + RNA Traffic over Time Detailed Dashboard Flow Summary DC + RNA Version 4. Displays the most active hosts on your monitored network. Displays the most active RUA users on your monitored network.1 Sourcefire 3D System Administrator Guide 77 . based on the number of kilobytes per second of data transmitted by the service. Displays a graph of the total kilobytes of data transmitted on your monitored network over the dashboard time range.

the events appear in the default workflow for that event type. This also changes the appropriate time window for the appliance. if you configure a single time window and then access any type of event from the Custom Analysis widget. depending on how many time windows you have configured and on what type of event you are trying to view.9. and the global time window changes to the dashboard time range. by violation count? Predefined Dashboards none Requires IPS or DC/MDC + IPS none DC/MDC + IPS + RNA DC + RNA Detailed Dashboard Viewing Associated Events from the Custom Analysis Widget Requires: Any Depending on the kind of data that a Custom Analysis widget is configured to display. Displays the hosts with the most white list violations. the events appear in the default workflow for that event type. see Default Time Windows on page 29 and Specifying Time Constraints in Searches in the Analyst Guide. For more information on time windows. Version 4. As another example. When you invoke an event view from the dashbaord. if you configure multiple time windows on your Defense Center and then access health events from a Custom Analysis widget. a workflow) that provides detailed information about the events displayed in the widget. Displays the number of unique intrusion event types associated with each impact flag level. constrained by the dashboard time range. based on the number of unique intrusion events per targeted host. you can invoke an event view (that is. and the health monitoring time window changes to the dashboard time range.Using Dashboards Understanding the Predefined Widgets Chapter 3 Custom Analysis Widget Presets (Continued) Preset Unique Intrusion Events by Destination IP Unique Intrusion Events by Impact White List Violations Description Displays the most active targeted hosts. For example.1 Sourcefire 3D System Administrator Guide 78 . the events appear in the default health events workflow.

Intrusion Event Analysts cannot view RNA events. click the View All icon in the lower right corner of the widget to view all associated events. depending on how you configured the widget: • On widgets configured to show relative occurrences of events (that is. • For information on working with specific event types.9. constrained by the widget preferences. remember that not all appliances have access to data of all event types. if you are using a dashboard imported from another appliance. If you are configuring the widget on a shared dashboard.Using Dashboards Understanding the Predefined Widgets Chapter 3 To view associated events from the Custom Analysis Widget: Access: Any except Restricted You have two options. bar graphs). Similarly. For example. You can also click the View All icon in the lower right corner of the widget to view all associated events. depending on the user’s account privileges. On widgets configured to show flow data over time. click any event to view associated events constrained by the widget preferences. remember that not all users can view data of all event types.1 Sourcefire 3D System Administrator Guide 79 . For Version 4. see the following sections: • • • • • • • • • • • • • • • • • Viewing Audit Records on page 567 Viewing Intrusion Events in the Analyst Guide Viewing RNA Network Discovery and Host Input Events in the Analyst Guide Viewing Hosts in the Analyst Guide Viewing Host Attributes in the Analyst Guide Viewing Services in the Analyst Guide Viewing Client Applications in the Analyst Guide Viewing Vulnerabilities in the Analyst Guide Viewing Flow Data in the Analyst Guide Viewing RUA Users in the Analyst Guide Viewing RUA Events in the Analyst Guide Viewing Compliance Events in the Analyst Guide Viewing White List Events in the Analyst Guide Viewing White List Violations in the Analyst Guide Viewing the SEU Import Log in the Analyst Guide Working with Active Scan Results in the Analyst Guide Understanding Custom Tables in the Analyst Guide Custom Analysis Widget Limitations Requires: Any There are some important points to keep in mind when using the Custom Analysis widget. constrained by the widget preferences. as well as by that event.

You enable or disable the Custom Analysis widget from the Dashboard settings in your system policy. For more information. that you (and any other users who share the dashboard) can modify the preferences of the widget to display data that you can see.9. Understanding the Disk Usage Widget Requires: Any The Disk Usage widget indicates the percentage of space used on each partition of the appliance’s hard drive. however.Using Dashboards Understanding the Predefined Widgets Chapter 3 example. If your dashboard includes a Custom Analysis widget that displays data that you cannot see. see Understanding Widget Preferences on page 64. save the dashboard as private. The widget preferences also control how often the widget updates. If you want to make sure that this does not happen. Version 4. the widget resets to not using the search when another user logs in. If you want to make sure that this does not happen. Remember that only you can access searches that you have saved as private. save the dashboard as private.1 Sourcefire 3D System Administrator Guide 80 . as well as whether it displays the current disk usage or collected disk usage statistics over the dashboard time range. see Configuring Dashboard Settings on page 331. the widget indicates that you are unauthorized to view the data. For more information. or even delete the widget. This affects your view of the widget as well. the Master Defense Center does not store flow data. If you configure the widget on a shared dashboard and constrain its events using a private search. You can configure the widget to display just the root (/) and /volume partition usage. It also shows the capacity of each partition. Note. or you can show these plus the /boot partition usage by modifying the widget preferences.

The widget preferences control how often the widget updates. this includes statistics on intrusion events of different impacts. On the 3D Sensor. On the 3D Sensor. On 3D Sensors. On the Defense Center and Master Defense Center. the widget can display statistics for dropped intrusion events.9.Using Dashboards Understanding the Predefined Widgets Chapter 3 Understanding the Interface Traffic Widget Requires: Any The Interface Traffic widget shows the rate of traffic received (Rx) and transmitted (Tx) on the appliance’s interfaces over the dashboard time range. On the Defense Center and Master Defense Center. Understanding the Intrusion Events Widget Requires: IPS or DC/ MDC + IPS The Intrusion Events widget shows the rate of intrusion events that occurred over the dashboard time range. all intrusion events. see Understanding Widget Preferences on page 64. the widget only displays the traffic rate for interfaces that belong to an interface set). or both.1 Sourcefire 3D System Administrator Guide 81 . Note that for managed 3D Sensors. you cannot configure the widget to display Version 4. you can configure the widget to display intrusion events of different impacts by modifying the widget preferences. For more information. Note that only 3D Sensors have interfaces other than the management interface. you must enable local event storage or the widget will not have any data to display. the preferences also control whether the widget displays the traffic rate for unused interfaces (by default.

9. see Viewing Intrusion Events in the Analyst Guide. see Understanding Widget Preferences on page 64. On the Intrusion Events widget. For more information on intrusion events. you can: • Requires: DC/MDC select one or more Event Flags check boxes to display separate graphs for events of specific impacts. the widget displays a pie chart that shows the Version 4. For more information. you can: • • • Requires: DC/MDC click a graph corresponding to a specific impact to view intrusion events of that impact click the graph corresponding to dropped events to view dropped events click the All graph to view all intrusion events Note that the resulting event view is constrained by the dashboard time range.Using Dashboards Understanding the Predefined Widgets Chapter 3 intrusion events by impact. Understanding the Network Compliance Widget Requires: DC The Network Compliance widget summarizes your hosts’ compliance with the compliance white lists you configured (see Using RNA as a Compliance Tool in the Analyst Guide). see Using Impact Flags to Evaluate Events in the Analyst Guide select Show to choose Events per second or Total events select Vertical Scale to choose Linear (incremental) or Logarithmic (factor of ten) scale • • The preferences also control how often the widget updates. regardless of impact or rule state. select All to display an additional graph for all intrusion events. accessing intrusion events via the dashboard changes the events (or global) time window for the appliance.1 Sourcefire 3D System Administrator Guide 82 . By default. you can display dropped events. In the widget preferences. The following graphic shows the Defense Center version of the widget preferences. On either appliance.

and that have not been evaluated. the widget considers a host to be non-compliant if it is not compliant with any of the white lists on the Defense Center. and that have not been evaluated. You can click the pie chart to view the host violation count. by modifying the widget preferences.9. including white lists that are no longer in active compliance policies. You can configure the widget to display network compliance either for all white lists. delete the unused white lists. non-compliant.1 Sourcefire 3D System Administrator Guide 83 .Using Dashboards Understanding the Predefined Widgets Chapter 3 number of hosts that are compliant. Note that if you choose to display network compliance for all white lists. The Network Compliance style (the default) displays a pie chart that shows the number of hosts that are compliant. which lists the hosts that violate at least one white list. or for a specific white list. non-compliant. see Viewing White List Violations in the Analyst Guide. Version 4. You can also use the widget preferences to specify which of three different styles you want to use to display network compliance. for all compliance white lists that you have created. To bring these hosts into compliance. For more information.

and that have not yet been evaluated. including temporary licenses. while the Temporary Licenses section displays only temporary and expired licenses. non-compliant. Understanding the Product Licensing Widget Requires: DC The Product Licensing widget shows the feature licenses currently installed on the Defense Center.1 Sourcefire 3D System Administrator Guide 84 . non-compliant. You can check the Show Not Evaluated box to hide events which have not been evaluated. For example. The Network Compliance over Time style displays a line graph that shows the number of hosts that are compliant. For more information. one of which is a permanent license and Version 4. see Understanding Widget Preferences on page 64. It also indicates the number of items (such as hosts or users) licensed and the number of remaining licensed items allowed. over the dashboard time range. if you have two feature licenses for RNA Hosts. over the dashboard time range. The preferences control how often the widget updates.9. The top section of the widget displays all of the feature licenses installed on the Defense Center.Using Dashboards Understanding the Predefined Widgets Chapter 3 The Network Compliance over Time (%) style displays a stacked area graph showing the relative proportion of hosts that are compliant. and that have not yet been evaluated.

but not yet installed. push. Note that you cannot update the VDB on a sensor or a Master Defense Center.9. Note that the widget displays Unknown as the latest version of the software unless you have configured a scheduled task to download. the widget uses scheduled tasks to determine the latest version. while the Temporary Licenses section displays an RNA Hosts feature license with 750 hosts. For more information. You can configure the widget to hide the latest versions by modifying the widget preferences. the Defense Center version of the widget provides you with similar links so you can update the software on your managed sensors. Version 4. For more information. see Managing Your Feature Licenses on page 370. see Scheduling Tasks on page 425. Understanding the Product Updates Widget Requires: Any The Product Updates widget provides you with a summary of the software (Sourcefire 3D System software. for that software.Using Dashboards Understanding the Predefined Widgets Chapter 3 allows 750 hosts. or all the features that you can license. and VDB) currently installed on the appliance as well as information on available updates that you have downloaded.1 Sourcefire 3D System Administrator Guide 85 . You can configure the widget to display either the features that are currently licensed. The bars in the widget background show the percentage of each type of license that is being used. you should read the bars from right to left. or install software updates. the top section of the widget displays an RNA Hosts feature license with 1500 licensed hosts. For more information. and another that is temporary and allows an additional 750 hosts. SEU. The widget also provides you with links to pages where you can update the software. see Understanding Widget Preferences on page 64. The preferences also control how often the widget updates. Expired licenses are marked with a strikethrough. You can click any of the license types to go to the License page of the System Settings and add or delete feature licenses. For more information. see Understanding Widget Preferences on page 64. by modifying the widget preferences. The preferences also control how often the widget updates.

You can also configure the widget to display a preconfigured feed of Sourcefire security news. SEU. as well as whether you want to show descriptions of the stories along with the headlines. or VDB. When you configure the widget. Keep in mind that the appliance must have access to the Sourcefire web site (for the two preconfigured feeds) or to any custom feed you configure. Version 4. or VDB by clicking either the latest version or the Unknown link in the Latest column. keep in mind that not all RSS feeds use descriptions. you can also choose how many stories from the feed you want to show in the widget.9.1 Sourcefire 3D System Administrator Guide 86 . By default. or you can create a custom connection to any other RSS feed by specifying its URL in the widget preferences.Using Dashboards Understanding the Predefined Widgets Chapter 3 On the Product Updates widget. Feeds update every 24 hours (although you can manually update the feed) and the widget displays the last time the feed was updated based on the local time of the appliance. the widget shows a feed of Sourcefire company news. see Updating System Software on page 398 and Importing SEUs and Rule Files in the Analyst Guide create a scheduled task to download the latest version of the Sourcefire 3D System software. you can: • manually update an appliance by clicking the current version of the Sourcefire 3D System software. SEU. see Scheduling Tasks on page 425 • Understanding the RSS Feed Widget Requires: Any The RSS Feed widget adds an RSS feed to a dashboard.

and system load (also called the load average. The preferences also control how often the widget synchronizes with the appliance’s clock. memory (RAM) usage.Using Dashboards Understanding the Predefined Widgets Chapter 3 On the RSS Feed widget. measured by the number of processes waiting to execute) on the appliance. The preferences also control how often the widget updates. Understanding the System Time Widget Requires: Any The System Time widget shows the local system time.9. uptime. For more information. see Understanding Widget Preferences on page 64. see Understanding Widget Preferences on page 64.1 Sourcefire 3D System Administrator Guide 87 . and boot time for the appliance. You can configure the widget to show or hide the load average by modifying the widget preferences. you can: • • • click one of the stories in the feed to view the story click the more link to go to the feed’s web site click the update icon ( ) to manually update the feed Understanding the System Load Widget Requires: Any The System Load widget shows the CPU usage (for each CPU). You can configure the widget to hide the boot time by modifying the widget preferences. both currently and over the dashboard time range. For more information. Version 4.

1 Sourcefire 3D System Administrator Guide 88 . you can: • • • select one or more Priorities check boxes to display separate graphs for events of specific priorities. In either case. For more information.9. For more information on white list events. over the dashboard time range. or click the All graph to view all white list events. including events that do not have a priority select Show All to display an additional graph for all white list events. You can configure the widget to display white list events of different priorities by modifying the widget preferences.Using Dashboards Understanding the Predefined Widgets Chapter 3 Understanding the White List Events Widget Requires: DC/MDC The White List Events widget shows the average events per second by priority. accessing white list events via the dashboard changes the events (or global) time window for the Defense Center. see Understanding Widget Preferences on page 64. regardless of priority select Vertical Scale to choose Linear (incremental) or Logarithmic (factor of ten) scale The preferences also control how often the widget updates. You can click a graph to view white list events of a specific priority. Version 4. In the widget preferences. see Viewing White List Events in the Analyst Guide. the events are constrained by the dashboard time range.

These settings determine how often the dashboard cycles through its tabs and how often the entire dashboard page refreshes. in a network operations center (NOC) where a dashboard is displayed at all times. the user who created it) and whether a dashboard is private. Note that you do not need to refresh the entire dashboard to see data updates. you can only see your own private dashboards.1 Sourcefire 3D System Administrator Guide 89 . you can choose to base it on any pre-existing dashboard. the page indicates the owner (that is. Note that. Finally. you can modify this copy to suit your needs. the page indicates which dashboard is the default. You specify the default dashboard in your user preferences. Optionally. you can create a blank new dashboard by choosing not to base your dashboard on any pre-existing dashboards. see Specifying Your Default Dashboard on page 35. For more information on working with dashboards. and delete dashboards. unless you have Admin access. for more information. This can be useful. For each dashboard. you can make the changes at a local computer. the dashboard in the NOC automatically refreshes at the interval you specify and displays your changes without you having to manually refresh the dashboard in the NOC. you cannot view or modify private dashboards created by other users. If you want to make changes to the dashboard. Then. view.9. including the Sourcefire default dashboard. individual widgets update according to their preferences. or on any user-defined dashboard. You must also specify (or disable) the tab change and page refresh intervals. export. since the last time the dashboard refreshed.Using Dashboards Working with Dashboards Chapter 3 Working with Dashboards Requires: Any You manage dashboards on the Dashboard List page (see Viewing Dashboards on page 91). or that you made to a private dashboard on another computer. You can create. modify. for example. This makes a copy of the pre-existing dashboard. see: • • • • • Creating a Custom Dashboard on page 89 Viewing Dashboards on page 91 Modifying Dashboards on page 93 Deleting a Dashboard on page 97 Exporting a Dashboard on page 585 Creating a Custom Dashboard Requires: Any When you create a new dashboard. Refreshing the entire dashboard allows you to see any preference or layout changes that were made to a shared dashboard by another user. Version 4.

Type a name and optional description for the dashboard. the Dashboard List page appears.Using Dashboards Working with Dashboards Chapter 3 Finally. it appears. users with fewer permissions viewing a dashboard created by a user with more permissions may not be able to use all of the widgets on the dashboard. Keep in mind that because not all user roles have access to all dashboard widgets. select None (the default) to create a blank dashboard. for example. You can then edit the imported dashboard to suit your needs. a dashboard created on the Defense Center and imported onto a 3D Sensor or Master Defense Center may display some invalid. If you want to make sure that only you can modify a particular dashboard. click New Dashboard.1 Sourcefire 3D System Administrator Guide 90 .9. Although the unauthorized widgets still appear on the dashboard. If you do not have a default dashboard defined. You should also keep in mind that any user. If you choose not to save the dashboard as private. they are disabled. Use the Copy Dashboard drop-down list to select the dashboard on which you want to base the new dashboard. To create a new dashboard: Access: Any except Restricted 1. see Importing and Exporting Objects on page 583. you can choose to associate the new dashboard with your user account by saving it as a private dashboard. TIP! Instead of creating a new dashboard. The New Dashboard page appears. can modify shared dashboards. all other users of the appliance can view it. If you have a default dashboard defined. In either case. Note that the dashboard widgets you can view depend on the type of appliance you are using and on your user role. disabled widgets. Optionally. you can export a dashboard from another appliance and then import it onto your appliance. Version 4. You can select any predefined or user-defined dashboard. Select Analysis & Reporting > Event Summary > Dashboards. 4. 2. save it as private. regardless of role. For more information. 3.

the home page for your appliance displays the default dashboard. For example. TIP! You can configure your appliance to display a different default home page. If you do not have a default dashboard defined. Click Save. In the Change Tabs Every field. enter 0 in the Change Tabs Every field.9. For more information. 8. Viewing Dashboards Requires: Any By default. click Dashboards from the Dashboard toolbar. the dashboard time range has no effect on the Appliance Information widget. specify (in minutes) how often the current dashboard tab should refresh with new data. Unless you pause the dashboard. including pages that are not dashboard pages. specify (in minutes) how often the dashboard should change tabs.1 Sourcefire 3D System Administrator Guide 91 . see Modifying Dashboards on page 93. Each dashboard has a time range that constrains its widgets. Note that this setting is separate from the update interval available on many individual widgets. this setting advances your view to the next tab at the interval you specify. To disable the periodic page refresh. select the Save As Private check box to associate the dashboard with your user account and to prevent other users from viewing and modifying the dashboard. this setting will refresh the entire dashboard at the interval you specify. Note that not all widgets can be constrained by time. To disable tab cycling. which provides Version 4. 6. 7. the home page shows the Dashboard List page. where you can choose a dashboard to view. You can change the time range to reflect a period as short as the last hour (the default) or as long as the last year. You can now tailor it to suit your needs by adding tabs and widgets (and. When you change the time range. although refreshing the dashboard page resets the update interval on individual widgets. To view the details of all available dashboards. widgets will update according to their individual preferences even if you disable the Refresh Page Every setting. enter 0 in the Refresh Page Every field. Unless you pause the dashboard or your dashboard has only one tab. by rearranging and deleting widgets). Your dashboard is created and appears in the web interface. Optionally. For more information. the widgets that can be constrained by time automatically update to reflect the new time range. This value must be greater than the Change Tabs Every setting. see Specifying Your Home Page on page 35 and Specifying Your Default Dashboard on page 35. You can also change the default dashboard. if you based it on a pre-existing dashboard. In the Refresh Page Every field.Using Dashboards Working with Dashboards Chapter 3 5.

Dashboard tabs stop cycling. Keep in mind that for enterprise deployments of the Sourcefire 3D System.9. To view a different dashboard.5 hours of inactivity. The dashboard you selected appears. Unpausing the dashboard causes all the appropriate widgets on the page to update to reflect the current time range.1 Sourcefire 3D System Administrator Guide 92 . depending on whether you have a default dashboard defined: • • If you have a default dashboard defined. and current version of the Sourcefire 3D System software. To change the dashboard time range: Access: Any except Restricted From the Show the Last drop-down list. To view a dashboard: Access: Any except Restricted Select Analysis & Reporting > Event Summary > Dashboards. the Dashboard List page appears. this will not happen while you are viewing a dashboard. IMPORTANT! Although your session normally logs you out after 3. When you are finished with your analysis. Click View next to the dashboard you want to view. You have two options. Version 4. it appears. use the Dashboards menu on the toolbar. regardless of the Cycle Tabs Every setting in the dashboard properties. all appropriate widgets on the page update to reflect the new time range. choose a dashboard time range. Changing the time range has no effect. You can also pause a dashboard. regardless of the Refresh Page Every setting in the dashboard properties. regardless of any Update Every widget preference. depending on how often newer events replace older events. you can unpause the dashboard. unless the dashboard is paused. which allows you to examine the data provided by the widgets without the display changing and interrupting your analysis. Dashboard pages stop refreshing. dashboard tabs resume cycling and the dashboard page resumes refreshing according to the settings you specified in the dashboard properties. changing the time range to a long period may not be useful for widgets like the Custom Analysis widget.Using Dashboards Working with Dashboards Chapter 3 information the includes the appliance name. If you do not have a default dashboard defined. In addition. Unless the dashboard is paused. model. Pausing a dashboard has the following effects: • • • • Individual widgets stop updating.

see the following sections • • • • • • • • Changing Dashboard Properties on page 93 Adding Tabs on page 94 Deleting Tabs on page 95 Renaming Tabs on page 95 Adding Widgets on page 95 Rearranging Widgets on page 97 Minimizing and Maximizing Widgets on page 97 Deleting Widgets on page 97 Changing Dashboard Properties Requires: Any Use the following procedure to change the basic dashboard properties. the tab cycle and page refresh intervals.1 Sourcefire 3D System Administrator Guide 93 . ). Each tab can display one or more widgets in a three-column layout. add and remove widgets from tabs. click the play icon ( The dashboard is unpaused. which include its name and description. and rename tabs. make sure to set it as a private dashboard in the dashboard properties. Modifying Dashboards Requires: Any Each dashboard has one or more tabs. ). IMPORTANT! Any user.Using Dashboards Working with Dashboards Chapter 3 To pause the dashboard: Access: Any except Restricted On the time range control. regardless of role. click the pause icon ( The dashboard is paused until you unpause it. Note that you cannot change the order of dashboard tabs. which include its name and description. To unpause the dashboard: Access: Any except Restricted On the time range control of a paused dashboard. delete.9. as well as rearrange the widgets on a tab. can modify shared dashboards. For more information. You can minimize and maximize widgets. You can add. Version 4. and whether you want to share the dashboard with other users. You can also change the basic dashboard properties. and whether you want to share the dashboard with other users. If you want to make sure that only you can modify a particular dashboard. the tab cycle and page refresh intervals.

You can now add widgets to the new tab. see Renaming Tabs on page 95. it appears. continue with the next step. skip to step 3.1 Sourcefire 3D System Administrator Guide 94 . The dashboard is changed. Note that you can rename the tab at any time.Using Dashboards Working with Dashboards Chapter 3 To change a dashboard’s properties: Access: Any except Restricted 1. The Edit Dashboard page appears. If you have a default dashboard defined. 3. Make changes as needed and click Save.9. 2. See Creating a Custom Dashboard on page 89 for information on the various configurations you can change. To the right of the existing tabs. To add a tab to a dashboard: Access: Any except Restricted 1. Type a name for the tab and click OK. 4. Select Analysis & Reporting > Event Summary > Dashboards. A pop-up window appears. For more information. View the dashboard where you want to add a tab. Adding Tabs Requires: Any Use the following procedure to add a tab to a dashboard. click Dashboards. 2. see Adding Widgets on page 95. The Dashboard List page appears. the Dashboard List page appears. click the add tab icon ( ). 3. or simply click OK to accept the default name. For more information. The new tab is added. Click Edit next to the dashboard whose properties you want to change. see Viewing Dashboards on page 91. On the toolbar. If you do not have a default dashboard defined. Version 4. prompting you to name the tab.

The tab is deleted. Type a name for the tab and click OK. For more information. prompting you to rename the tab. Click the tab you want to rename. move widgets from tab to tab. see Viewing Dashboards on page 91. 2. When you add a widget to a tab. the appliance automatically adds it to the column with the fewest widgets. View the dashboard where you want to add a widget. A pop-up window appears. you can move them to any location on the tab. you must first decide to which tab you want to add the widget. Version 4. To add a widget to a dashboard: Access: Any except Restricted 1. To rename a tab: Access: Any except Restricted 1. Adding Widgets Requires: Any To add a widget to a dashboard. see Viewing Dashboards on page 91. see Rearranging Widgets on page 97. To delete a tab from a dashboard: Access: Any except Restricted 1. 4. click the delete icon ( 3. ). Confirm that you want to delete the tab. each dashboard must have at least one tab. If all columns have an equal number of widgets. Click the tab title. View the dashboard where you want to rename a tab. 2. View the dashboard where you want to delete a tab. see Viewing Dashboards on page 91. You cannot. TIP! After you add widgets.1 Sourcefire 3D System Administrator Guide 95 . You can add a maximum of 15 widgets to a dashboard tab. the new widget is added to the left-most column. however. The tab is renamed. On the tab you want to delete. For more information.Using Dashboards Working with Dashboards Chapter 3 Deleting Tabs Requires: Any Use the following procedure to delete a dashboard tab and all its widgets. Renaming Tabs Requires: Any Use the following procedure to rename a dashboard tab. You cannot delete the last tab from a dashboard. For more information.9. For more information. 3.

TIP! To add multiple widgets of the same type (for example. click Add again.Using Dashboards Working with Dashboards Chapter 3 2. reflecting the changes you made. including the widget you just added. The tab where you added the widgets appears again. Select the tab where you want to add the widget. Version 4. You can view the widgets in each category by clicking on the category name. 3.9. or multiple Custom Analysis widgets). Operations. or you can view all widgets by clicking All Categories. 4. click Done to return to the dashboard. Click Add Widgets. 5. The widget is immediately added to the dashboard.1 Sourcefire 3D System Administrator Guide 96 . and Miscellaneous. Click Add next to the widgets you want to add. They are organized according to function: Analysis & Reporting. The Add Widgets page appears. when you are finished adding widgets. you may want to add multiple RSS Feed widgets. The widgets that you can add depend on the type of appliance you are using and on your user role. The Add Widgets page indicates how many widgets of each type are on the tab. Optionally.

If you want a widget to appear on a different tab. Select Analysis & Reporting > Event Summary > Dashboards. 2. Confirm that you want to delete the widget. that you cannot move widgets from tab to tab. Deleting a Dashboard Requires: Any Delete a dashboard if you no longer need to use it. Click the close icon ( ) in the title bar of the widget. the Dashboard List page appears. Version 4. you must delete it from the existing tab and add it to the new tab. If you delete your default dashboard. you must define a new default or the appliance will force you to select a dashboard to view every time you attempt to view a dashboard. If you do not have a default dashboard defined. Deleting Widgets Delete a widget if you no longer want to view it on a tab. then maximize them when you want to see them again.9. For more information. then drag it to its new location. Minimizing and Maximizing Widgets Requires: Any You can minimize widgets to simplify your view. ) in a widget’s title bar. skip to step 3. To move a widget: Access: Any except Restricted Click the title bar of the widget you want to move. continue with the next step. see Specifying Your Default Dashboard on page 35. Note. To delete a widget: Access: Any except Restricted 1. The widget is deleted from the tab. To minimize a widget: Access: Any except Restricted Access: Any except Restricted Requires: Any Click the minimize icon ( To maximize a widget: Click the maximize icon ( ) in a minimized widget’s title bar. To delete a dashboard: Access: Any except Restricted 1. it appears. however.1 Sourcefire 3D System Administrator Guide 97 . If you have a default dashboard defined.Using Dashboards Working with Dashboards Chapter 3 Rearranging Widgets Requires: Any You can change the location of any widget on a tab.

4. click Dashboards.1 Sourcefire 3D System Administrator Guide 98 . Version 4. Click Delete next to the dashboard you want to delete. Confirm that you want to delete the dashboard. The Dashboard List page appears. 3. The dashboard is deleted. On the toolbar.Using Dashboards Working with Dashboards Chapter 3 2.9.

you can push various types of software updates to sensors. In addition. 3Dx800 sensors. making it easier to change configurations.9. network discovery information. and respond to the threats they detect on your network. The Defense Center aggregates and correlates intrusion events. and Crossbeam-based software sensors) do not provide a web interface that you can use to view events or manage policies. you can configure policies for all your sensors from a single location. You can also push health policies to your managed sensors and monitor their health status from the Defense Center.Using the Defense Center Chapter 4 Administrator Guide The Sourcefire Defense Center is a key component in the Sourcefire 3D System. You must use a Defense Center if your deployment includes any of these products. Version 4.1 Sourcefire 3D System Administrator Guide 99 . You can use the Defense Center to manage the full range of sensors that are a part of the Sourcefire 3D System. Intrusion Agents. RNA Software for Red Hat Linux. and to aggregate. By using the Defense Center to manage sensors. analyze. IMPORTANT! Some of the components in the Sourcefire 3D System (such as the Virtual 3D Sensors. and sensor performance data. allowing you to monitor the information that your sensors are reporting in relation to one another and to assess the overall activity occurring on your network.

Configuring High Availability on page 145 describes how to set up two Defense Centers as a high availability pair to help ensure continuity of operations. Managing Sensor Groups on page 131 describes how to create sensor groups as well as how to add and remove sensors from groups. Instead of managing each sensor using its own local web interface.9. Managing a Clustered Pair on page 140 describes how to create a clustered pair of 3D9900s and how to remove 3D9900s from clusters. Editing a Managed Sensor’s System Settings on page 133 describes the sensor attributes you can edit and explains how to edit them. Working in NAT Environments on page 112 describes the principles of setting up the management of your sensors in Network Address Translation environments. you can use the Defense Center as a central point of management. For example. Working with Sensors on page 113 describes how to establish and disable connections between sensors and your Defense Center.1 Sourcefire 3D System Administrator Guide 100 . you can use the Defense Center’s web interface to accomplish nearly any task on any sensor it manages. It also explains how to add. and change the state of managed sensors and how to reset management of a sensor. • • • • • Management Concepts Requires: DC You can use a Defense Center to manage nearly every aspect of a sensor’s behavior. • • • • • The Benefits of Managing Your Sensors on page 100 What Can Be Managed by a Defense Center? on page 101 Understanding Software Sensors on page 105 Beyond Policies and Events on page 111 Using Redundant Defense Centers on page 112 The Benefits of Managing Your Sensors Requires: DC There are several benefits to using a Defense Center to manage your sensors. First. delete. This saves you from having Version 4.Using the Defense Center Management Concepts Chapter 4 See the following sections for more information about using the Defense Center to manage your sensors: • • Management Concepts on page 100 describes some of the features and limitations involved with managing your sensors with a Defense Center. you can create an intrusion policy on the Defense Center and apply it to all your managed 3D Sensors with IPS. You can only use a single Defense Center to manage your sensor unless you are using a second Defense Center as a part of a high availability pair. The sections that follow explain some of the concepts you need to know as you plan your Sourcefire 3D System deployment.

and those sensors view the same network traffic. The Defense Center can then assign impact flags to each intrusion event. What Can Be Managed by a Defense Center? Requires: DC You can use your Defense Center as a central management point in a Sourcefire 3D System deployment to manage the following devices: • • Sourcefire 3D Sensors RNA Software for Red Hat Linux Version 4. There is a similar savings when you create and apply RNA appliance and detection policies to managed 3D Sensors with RNA. External authentication cannot be managed on the sensor. you can use your Defense Center to configure external authentication through an Lightweight Directory Access Protocol (LDAP) or Remote Authentication Dial In User Service (RADIUS) server. Fourth. You can also create and apply system policies to your managed sensors. so you must use the Defense Center to manage it. You can also apply a health policy to the Defense Center to monitor its health. The impact flag indicates how likely it is that an intrusion attempt will affect its target. if your Defense Center manages sensors with IPS and RNA. You can use user information from an external server to authenticate users on your Sourcefire 3D System appliances. You can take advantage of health monitoring by applying health policies to each of your managed sensors and then reviewing the health data that they send back to the Defense Center. all the intrusion events and RNA events are automatically sent to the Defense Center. Third.1 Sourcefire 3D System Administrator Guide 101 . You can view the events from a single web interface instead of having to log into each sensor’s interface to view the events there. Second. you can create the policy on the Defense Center and push it to the appropriate sensors instead of replicating it locally. By pushing a system policy with configured authentication objects to your sensor. you push the external authentication object to the sensor. Because most of the sensors in your deployment are likely to have similar settings in the system policy.9. Finally.Using the Defense Center Management Concepts Chapter 4 to replicate the intrusion policy on each sensor. which can be a laborious task depending on how many of the thousands of intrusion rules you want to enable or disable. then the Defense Center can correlate the intrusion events it receives with the information about hosts that RNA provides. the Defense Center includes a feature called health monitoring that you can use to check the status of critical functionality across your Sourcefire 3D System deployment. You can also generate reports based on events from multiple sensors. when you manage a sensor with a Defense Center. A system policy controls several appliance-level settings such as the login banner and the access control list.

Note that the types of events and policies that are sent between the appliances are based on the sensor type. Version 4. For details on DC500 database limitations see Database Event Limits on page 333.1 Sourcefire 3D System Administrator Guide 102 . The following illustration lists what is transmitted between a Sourcefire Defense Center and its managed sensors.Using the Defense Center Management Concepts Chapter 4 • • 3D Sensor Software for Crossbeam Systems X-Series Intrusion Agents on various platforms IMPORTANT! Sourcefire recommends that you manage no more than three 3D Sensors with the DC500 model Defense Center. When you manage a sensor (or a software sensor). information is transmitted between the Defense Center and the sensor over a secure. you can see a read-only version of the policy on the Defense Center’s web interface. If you apply a policy on a sensor before you begin managing it with a Defense Center. as well as intrusion agents and RNA software on approved platforms.9. You can also use a DC500 to manage Sourcefire 3D Sensor software on approved platforms. SSL-encrypted TCP tunnel.

before you set up sensor management.Using the Defense Center Management Concepts Chapter 4 Similarly. you can see a read-only version of the running policies on the sensor’s web interface.9. each appliance has its own policies: Version 4. after you set up communications with a Defense Center and apply policies from the Defense Center to your sensor. First. The following graphics illustrate this process.1 Sourcefire 3D System Administrator Guide 103 .

9. The Sample Intrusion Policy that is currently applied to the sensor’s two detection engines was created on the Defense Center (pine.com). the following graphic shows the Detection Engine page on a 3D Sensor with IPS. TIP! After you set up management with a Defense Center.example. If you want to edit a policy. Version 4. after communications are set up.1 Sourcefire 3D System Administrator Guide 104 . you must do it on the appliance where the policy was created. read-only versions of running policies (represented by the dotted lines) are available: The appliance where you originally create a policy is the policy’s “owner” and is identified that way if you view the policy on a different appliance. Sourcefire recommends that you use only the Defense Center’s web interface to view events and manage policies for your managed sensors.Using the Defense Center Management Concepts Chapter 4 Then. For example.

the event remains on the sensor that discovered it. The following Sourcefire 3D System sensors are software-based: • • • • Intrusion Agents for various platforms . Understanding Software Sensors Requires: DC Several of the sensors you can manage with a Defense Center are softwarebased sensors. RNA Software for Red Hat Linux . A software-based sensor is a software-only installation of Sourcefire 3D System sensor software. deleting an intrusion event from a sensor does not delete it from the Defense Center.1 Sourcefire 3D System Administrator Guide 105 . see Managing RNA Software for Red Hat Linux on page 109 3D Sensor Software with RNA for Crossbeam X-Series . they are automatically shared with managed 3D Sensors with RNA.Using the Defense Center Management Concepts Chapter 4 The following user-created data and configurations are retained locally on the sensor and are not shared with the Defense Center: • • • • • • • • • • • user accounts user preferences bookmarks saved searches custom workflows report profiles audit events syslog messages reviewed status for intrusion events (IPS only) contents of the clipboard (IPS only) incidents (IPS only) If you create custom fingerprints on the Defense Center. Similarly. 3D3800. see Managing 3Dx800 Sensors on page 107. if you delete an intrusion event from the Defense Center. see Managing 3D Sensor Software with RNA for Crossbeam on page 110 3D Sensor Software with IPS for Crossbeam X-Series . For example. see Managing Intrusion Agents on page 106 3D5800.for more information.for more information. see Managing 3D Sensor Software with IPS for Crossbeam on page 110 • Version 4. and 3D9800 sensors . Also note that operations you perform on data on one appliance are not transmitted to other appliances.9.for more information.for more information.for more information.

they can only be managed from a Defense Center. high availability is not supported on Intrusion Agents. These events can then be viewed along with data from 3D Sensors with IPS so you can easily analyze all the intrusion information gathered on your network. IMPORTANT! When using Intrusion Agents registered to Defense Centers configured for high availability and managed by a Master Defense Center. In addition.Using the Defense Center Management Concepts Chapter 4 Software-based sensors do not have a user interface on the sensor. For some software-based sensors. You must tune your Snort rules and options manually on the computer where the Intrusion Agent resides. some of the functionality in the Defense Center interface cannot be used with software-based sensors. Version 4. register all Intrusion Agents to the primary Defense Center. Managing Intrusion Agents Requires: DC The Sourcefire Intrusion Agent transmits events generated by open source Snort sensor installations to the Sourcefire Defense Center.1 Sourcefire 3D System Administrator Guide 106 . Also. The Defense Center cannot apply intrusion policies to the Intrusion Agent.9. certain aspects of functionality are managed through the operating system or other features on the appliance.

Supported Features for Intrusion Agents Supported through Defense Center • Intrusion event collection and management • Licensing • Reports generated on the Defense Center Supported through CLI and .conf files • Process management • Registration of remote manager • Rules tuning Not Supported • Detection engine management • Event storage on sensor • Health policy apply • High availability synchronization • Host Statistics • Interface set management • Intrusion policy apply • Network interface management • Network settings • Performance Statistics • Remote backup and restore • Remote reports • Sensor information management (System Settings) • SEU updates • Software updates • System policy apply • Time settings Managing 3Dx800 Sensors Requires: DC + 3D Sensor Sourcefire 3D Sensor 3800. However. because these models do not have a web interface and because configuration and event data cannot be stored on the sensors. and 3D Sensor 9800 models (usually referred to as the 3Dx800 sensors) provide many of the features found on other 3D Sensors. 3D Sensor 5800.1 Sourcefire 3D System Administrator Guide 107 . Version 4.Using the Defense Center Management Concepts Chapter 4 See the Supported Features for Intrusion Agents table for more information.9.

Using the Defense Center Management Concepts Chapter 4 certain features cannot be used with these sensors.9. See the Supported Features for 3Dx800 Sensors table for more information.1 Sourcefire 3D System Administrator Guide 108 . Supported Features for 3Dx800 Sensors Supported through Defense Center All 3Dx800 models: • Detection engine management • Health policy apply • High availability synchronization • Host Statistics • Interface set management • Intrusion policy apply (no OPSEC support) • Intrusion event collection and management • Licensing • Performance Statistics (may be underreported because of multiple detection resources) • Process management • Reports generated on the Defense Center • Sensor information management (System Settings) • SEU updates • Software updates • System policy apply • Time settings 3D3800 and 3D5800 only: • Compliance policy apply • RNA and compliance event collection and management • RNA detection policy apply • VDB updates Supported through CLI • Network interface management • Network settings • Registration of remote manager Not Supported • Custom fingerprinting • Event storage on sensor • Remote backup and restore • Remote reports Version 4.

1 Sourcefire 3D System Administrator Guide 109 . Supported Features for RNA Software for Red Hat Linux Supported through Defense Center • Compliance policy apply • Detection engine management • High availability synchronization • Host Statistics • Interface set management • Licensing • Performance Statistics • Reports generated on the Defense Center • RNA and compliance event collection and management • RNA detection policy apply • Sensor information management (System Settings) • Software updates • VDB updates Supported through CLI • Network interface management • Network settings • Process management • Registration of remote manager • Time settings Not Supported • Custom fingerprinting • Event storage on sensor • Health policy apply • Remote backup and restore • Remote reports • System policy apply Version 4. However.9. not all of the features function in the same manner.Using the Defense Center Management Concepts Chapter 4 Managing RNA Software for Red Hat Linux Requires: DC RNA Software for Red Hat Linux provides many of the features found on 3D Sensors with RNA. See the Supported Features for RNA Software for Red Hat Linux table for more information.

because the Crossbeam sensors do not have a user interface and because configuration and event data cannot be stored on Version 4. Supported Features for RNA on Crossbeam Supported through Defense Center Supported through Crossbeam X-Series CLI • Backup and restore • Network interface management • Network settings • Process management • Registration of remote manager • Time settings Not Supported • Compliance policy apply • Detection engine management • High availability synchronization • Host Statistics • Interface set management • Licensing • Performance Statistics • Reports generated on the Defense Center • RNA detection policy apply • RNA and compliance event collection and management • Sensor information management (in System Settings) • Software updates • VDB updates • Custom fingerprinting • Event storage on sensor • Health policy apply • Remote backup and restore • Remote reports • System policy apply Managing 3D Sensor Software with IPS for Crossbeam Requires: DC 3D Sensor Software with IPS for Crossbeam provides many of the features found on 3D Sensors with IPS. not all of the features function in the same manner.1 Sourcefire 3D System Administrator Guide 110 . See the Supported Features for RNA on Crossbeam table for more information.9. However. However.Using the Defense Center Management Concepts Chapter 4 Managing 3D Sensor Software with RNA for Crossbeam Requires: DC 3D Sensor Software with RNA for Crossbeam provides many of the features found on 3D Sensors with RNA.

Audit events are stored locally Version 4.1 Sourcefire 3D System Administrator Guide 111 . See the Supported Features for IPS on Crossbeam table for more information. See Performing Sensor Backup with the Defense Center on page 419 for more information. Running Remote Reports You can create a report profile on the Defense Center and run it remotely using the data on a managed sensor. This is particularly useful if you want to generate a report for the audit events on a managed sensor. you can also perform other sensor-related tasks on the Defense Center. you can use the Defense Center’s web interface to back up those events from the sensor.Using the Defense Center Management Concepts Chapter 4 the sensors.9. Supported Features for IPS on Crossbeam Supported through Defense Center Supported through Crossbeam X-Series CLI • Backup and restore • Network interface management • Network settings • Process management • Registration of remote manager • Time settings Not Supported • Detection engine management • High availability synchronization • Host Statistics • Interface set management • Intrusion policy apply • Intrusion event collection and management • Licensing • Performance Statistics • Reports generated on the Defense Center • SEU updates • Sensor information management (in System Settings) • Software updates • Custom fingerprinting • Event storage on sensor • Health policy apply • Remote backup and restore • Remote reports • System policy apply Beyond Policies and Events Requires: DC In addition to applying policies to sensors and receiving events from them. Backing Up a Sensor If you are storing event data on your sensor in addition to sending it to the Defense Center. certain features cannot be used with this software.

you establish connections between appliances and register the appliances with one another. Using Redundant Defense Centers Requires: DC You can set up two Defense Centers as a high availability pair.company.9. Events are automatically sent to both Defense Centers. See Working with Event Reports on page 232 for more information. the two required pieces of common information during registration are the registration key and the unique IP address or the fully qualified domain name of the host. This ensures redundant functionality in case one of the Defense Centers fails. you do not even need a user account on the sensor to read the resulting report. user accounts. Updating Sensors From time to time. use the Defense Center’s fully qualified domain name maple.com as its host name. as well as new and updated preprocessors and protocol decoders vulnerability database updates software patches and updates • • You can use the Defense Center to push an update to the sensors it manages and then automatically install the update. See Configuring High Availability on page 145 or more information. Policies. you can use snort when adding either sensor. If you establish that communication in an environment without NAT. and run the report. the two required pieces of common information during registration are the registration key and the unique NAT ID.1 Sourcefire 3D System Administrator Guide 112 . when you set up the remote office 3D Sensors connections to the home office. select a managed sensor. If you set up the report so that it is automatically emailed to you. Sourcefire releases updates to the Sourcefire 3D System. For the registration key. Working in NAT Environments Requires: Any Network address translation (NAT) is a method of transmitting and receiving network traffic through a router that involves reassigning the source or destination IP address as the traffic passes through the router. When you add an appliance. and more are shared between the two Defense Centers. including: • Security Enhancement Updates (SEUs). because the registration key does not have to Version 4.Using the Defense Center Working in NAT Environments Chapter 4 and are not sent to the Defense Center. but you can design a report on the Defense Center. If you establish that communication in an environment with NAT. In the example diagram. Typical applications using NAT enable multiple hosts on a private network to use a single public IP address to access the public network. which can contain new and updated intrusion rules.

You can create the following policies on your Defense Center and apply them to managed sensors: • • • health policies system policies RUA policies Version 4. it generates events and sends them to the Defense Center using the same channel. However. Each NAT ID has to be unique among all NAT IDs used to register sensors on the Defense Center. As the sensor evaluates the traffic. you set up a two-way. and then use a different unique NAT ID when adding the Miami 3D Sensor. Working with Sensors Requires: DC + 3D Sensor When you manage a sensor.9. The Defense Center uses this channel to send information (in the form of policies) to the sensor about how you want to analyze your network traffic.1 Sourcefire 3D System Administrator Guide 113 .Using the Defense Center Working with Sensors Chapter 4 be unique. you must use a unique NAT ID when adding the New York 3D Sensor to the Defense Center. SSL-encrypted communication channel between the Defense Center and the sensor.

) 2.Using the Defense Center Working with Sensors Chapter 4 • • RNA detection policies intrusion policies There are several steps to managing a sensor with a Defense Center: The procedure for managing a 3Dx800 sensor differs from the procedure for managing other sensors. which controls the networks that 3D Sensors with RNA monitor.9. which control certain appliance-level features on your sensors. Version 4. You can create and apply health policies that allow you to monitor the processes and status of your sensors. with procedures that you need to perform on each side of the communications channel. You can also create and apply system policies. See Configuring Health Policies on page 489 for more information. (Deleting Sensors on page 121 explains how to remove a sensor from the Defense Center. RNA detection engines require an RNA detection policy. Note that the system policy applied to the Defense Center controls the types of RNA events that are logged to the database. Begin by setting up a communications channel between the two appliances.1 Sourcefire 3D System Administrator Guide 114 . and the Intrusion Agents are slightly different. • IPS detection engines require an intrusion policy that determines which types of attacks 3D Sensor with IPS detect. Confirm that you are receiving the events generated by your sensors. See Managing a 3Dx800 Sensor on page 125 for more information. RNA Software for Red Hat Linux. See Using Intrusion Policies in the Analyst Guide for more information. 1. See What is an RNA Detection Policy? in the Analyst Guide for more information. Create the appropriate policies on the Defense Center and apply them to the sensor or to the appropriate detection engines on the sensor. Refer to the configuration guides for those products for more information. See Managing System Policies on page 320 for more information. • • • 3. See Adding Sensors to the Defense Center on page 117 for more information. This is a two-step process. Many sensor management tasks are performed on the Sensors page and are described in Understanding the Sensors Page on page 115. See Viewing Intrusion Event Statistics in the Analyst Guide and Viewing RNA Event Statistics in the Analyst Guide for more information. TIP! The process for setting up communications between the Defense Center and other products such as the Crossbeam-based software sensors.

9. see Managing Sensor Groups on page 131) Model (that is. The following sections describe some of the features on the Sensors page. the sensor model) Sensor List The first column lists the hostname. sensor group. and sensor groups. Virtual Sensor Count When you manage Virtual 3D Sensors from the Defense Center. Health Policy The next column lists the health policy for the sensor.1 Sourcefire 3D System Administrator Guide 115 . If you use clustered 3D9900 sensors. You can click the name of the health policy to view a read-only version of the policy. For details about Virtual 3D Sensors. you can see which sensors are paired and if you configured the sensor as a master or a slave. You can click the folder icon next to the name of the category to expand and contract the list of sensors.Using the Defense Center Working with Sensors Chapter 4 Understanding the Sensors Page Requires: DC + 3D Sensor The Sensors page (Operations > Sensors) provides you with a range of information and options that you can use to manage your sensors (including software-based sensors). see the Virtual Defense Center and 3D Sensor Installation Guide. Version 4. sensor type. Sort-by Drop-Down List Use this drop-down list to sort the Sensors page according to your needs. intrusion agents. and software version for each sensor. sensor model. they are designated in the sensor list by a peer icon. the field for a Virtual Sensor count appears above the sensor list on the Sensors page. See Editing Health Policies on page 530 for information about modifying an existing health policy. if one has been applied. You can sort by: • • Group (that is. When you hover over the peer icon.

The policy name and the icon for the system policy in the top row highlight a special feature of the Sensors page. If your network is constrained in bandwidth. As with the health policy.Using the Defense Center Working with Sensors Chapter 4 System Policy The next column lists the currently applied system policy. you can click the Edit icon next to the name of a sensor group to modify the list of sensors that belong to the group. Edit and Delete Icons Click the Edit icon next to a sensor if you want to change the sensor’s current system settings. See Editing Sensor Groups on page 132 for more information. Note that this is the case for any policy that you create and apply from the Defense Center. the remote management configuration. The system settings include the storage settings for the sensor. The red exclamation point icon indicates that the Defense Center has not received communications from the sensor in the last three minutes.9. If you sort your Sensors page by sensor group. See Editing a Managed Sensor’s System Settings on page 133 for more information. a pop-up window indicates the amount of time (in hours. Status Icons The status icons indicate the state of a sensor. and access to the processes for stopping and restarting the sensor or its software. Version 4.1 Sourcefire 3D System Administrator Guide 116 . and seconds) since the last contact. If the Defense Center has not received a communication from a sensor within the last two minutes. the time. The green check mark icon indicates that the sensor and the Defense Center are communicating properly. minutes. you can click the name of the system policy to view a read-only version. See Managing System Policies on page 320 for more information. it sends a two-byte heartbeat packet to establish contact and ensure that the communications channel is still running. you can contact technical support to change the default time interval. If you hover your cursor over the icon. If a policy has a different icon and its name is in italics. The icon and the name of the policy in the bottom row indicate that the version applied to the sensor is up to date. that indicates the policy was modified after it was applied to the sensor.

IMPORTANT! If you registered a Defense Center and 3D Sensor using IPv4 and want to convert them to IPv6.1 Sourcefire 3D System Administrator Guide 117 .Using the Defense Center Working with Sensors Chapter 4 Click the Delete icon next to a sensor if you no longer want to manage the sensor with the Defense Center. SSL-encrypted communication channel between the Defense Center and the sensor. which monitor the health of your managed sensors Note that before you add sensors to a Defense Center. As the sensor evaluates the traffic. and custom login banners RNA detection policies. you must make sure that the network settings are configured correctly on the sensor. This is usually completed as part of the installation process. you set up a two-way. For more information.9. see Adding Intrusion Agents on page 130 and the Sourcefire Intrusion Agent Configuration Guide. which control RNA data-gathering behavior and determine which networks are monitored which detection engines intrusion policies. but you can refer to Configuring Network Settings on page 377 for details. You can create the following policies on your Defense Center and apply them to managed sensors: • • • • system policies. The Defense Center uses this channel to send information about how you want to analyze your network traffic (in the form of policies) to the sensor. Adding Sensors to the Defense Center Requires: DC + 3D Sensor When you manage a sensor. which control appliance-level configurations such as database limits. See Deleting Sensors on page 121 for more information. it generates events and sends them to the Defense Center using the same channel. See Deleting Sensor Groups on page 133 for more information. DNS cache settings. which control how protocol decoders and preprocessors are configured and which intrusion rules are enabled health policies. you must delete and re-register the sensor. You can also add Intrusion Agents to the Defense Center. If you sort your Sensors page by sensor group. Version 4. you can click the Delete icon next to the name of a sensor group to remove the sensor group from the Defense Center.

Unique NAT ID . or on both the Defense Center and the sensor • • TIP! Set up the managed appliance first. Management Host and Registration Key used on both appliances Registration Key and Unique NAT ID used on the 3D Sensor with Host. You must begin the procedure for setting up the management relationship between a Defense Center and a sensor on the sensor.9. 2.1 Sourcefire 3D System Administrator Guide 118 . Registration Key. Log into the web interface of the sensor you want to add.for the hostname or IP address. Registration Key . The Information page appears. and Unique NAT ID used on the 3D Sensor with Registration Key and Unique NAT ID used on the Defense Center. Management Host. Refer to Working in NAT Environments on page 112 for more information. Version 4. Three fields are provided for setting up communications between appliances: • • • Management Host . Registration Key. To add a sensor to a Defense Center: Access: Admin 1.for registration key.for a unique alphanumeric ID. you need: • the sensor’s IP address or hostname (in the connection context “hostname” is the fully qualified domain name or the name that resolves through the local DNS to a valid IP address) the Defense Center’s IP address or hostname to decide if you want to store the events generated by the sensor only on the Defense Center. Valid combinations include: • • • IMPORTANT! The Management Host or Host field (hostname or IP address) must be used on at least one of the appliances. Select Operations > System Settings.Using the Defense Center Working with Sensors Chapter 4 To add a sensor. and Unique NAT ID used on the Defense Center.

Click Remote Management. type the one-time use registration key that you want to use to set up a communications channel between the sensor and the Defense Center. 5.1 Sourcefire 3D System Administrator Guide 119 . Click Add Manager. in the Unique NAT ID field. Version 4. use both the Registration Key and the Unique NAT ID fields. The Add Remote Management page appears. Click Save. 7. In the Management Host field. TIP! You can leave the Management Host field empty if the management host does not have a routable address. In that case. 6. type the IP address or the host name of the Defense Center that you want to use to manage the sensor.9. Optionally. The Remote Management page appears. 4.Using the Defense Center Working with Sensors Chapter 4 3. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. the Pending Registration status appears. In the Registration Key field. After the sensor confirms communication with the Defense Center. type a unique alphanumeric ID that you want to use to identify the sensor. 8.

IMPORTANT! Software-based sensors such as the 3D Sensor Software for Crossbeam cannot store data locally. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. 15. Type the IP address or the hostname of the sensor you want to add in the Host field. packet data is not retained. enter the same ID in the Unique NAT ID (optional) field. For more information on supported functionality for software-based sensors. and select Operations > Sensors.1 Sourcefire 3D System Administrator Guide 120 . Click New Sensor. IMPORTANT! If you elect to prohibit sending packets and you do not store events on the 3D Sensor. You can prevent packet data from leaving a sensor by enabling the Prohibit Packet Transfer to the Defense Center check box. 13. Version 4.9.Using the Defense Center Working with Sensors Chapter 4 9. In the Registration Key field. data is stored only on the Defense Center and not on the sensor. You can store data on both the Defense Center and the sensor by clearing the Store Events and Packets Only on the Defense Center check box. By default. see Understanding Software Sensors on page 105. The Add New Sensor page appears. Packet data is often important for forensic analysis. enter the same registration key that you used in step 6. 11. The Sensors page appears. If you used a NAT ID in step 7. Log into the Defense Center’s web interface using a user account with Admin access. You must store events on the Defense Center. 14. 10. 12.

It can take up to two minutes for the Defense Center to verify the sensor’s heartbeat and establish communication. To add the sensor to a group. Deleting a sensor severs all communication between the Defense Center and the sensor. you should also delete the manager on the sensor. To keep the sensor from trying to reconnect to the Defense Center. Communication between the sensor and the Defense Center is discontinued and the sensor is deleted from the Sensors page. You can view the sensor’s status on the Sensors page (Operations > Sensors). 2. For more information about groups. you must re-add it to the Defense Center. IMPORTANT! If you delete a sensor from a Defense Center configured in a high availability pair and intend to re-add it. Click Delete next to the sensor you want to delete.Using the Defense Center Working with Sensors Chapter 4 16. it may take more than one synchronization cycle to add the sensor to both Defense Centers. you should delete the managed sensor from the Defense Center and then re-add it rather than try to delete the non-communicative detection engine. IMPORTANT! In some high availability deployments where network address translation is used. you may need to use the Add Manager feature a second time to add the secondary Defense Center. To manage the sensor again at a later date. If you do not wait five minutes. To delete a sensor from the Defense Center: Access: Admin 1. Sourcefire recommends that you wait at least five minutes before re-adding it. Log into the Defense Center web interface and select Operations > Sensors. Version 4. you can delete it from the Defense Center. Click Add. This interval ensures that the high availability pair re-synchronizes so that both Defense Centers recognize the deletion. if the sensor is down or the network interface card is damaged). see Managing Sensor Groups on page 131. 17. Deleting Sensors Requires: DC + 3D Sensor If you no longer want to manage a sensor.9.1 Sourcefire 3D System Administrator Guide 121 . The Sensors page appears. select the group from the Add to Group list. The sensor is added to the Defense Center. Contact technical support for more information. TIP! If you can no longer communicate with a detection engine on a managed sensor (for example.

2. see Managing Communication on a Managed Sensor on page 138. If you want to manage a sensor with a different Defense Center. you can disable the manager on the sensor. If the sensor has a system policy that causes it to receive time from the Defense Center via NTP the sensor reverts to local . For more information on resetting management on a 3Dx800 sensor. You can then re-add the manager on the sensor and then add the sensor to a Defense Center. you must also reset management before adding the sensor to another Defense Center. 5. time management. you can reset management of the sensor. To reset management: Access: Admin 1. Version 4. Resetting Management of a Sensor Requires: DC + 3D Sensor If communications fail between the Defense Center and one of your sensors. The manager is removed. The Sensors page appears. The Remote Management page appears. The Information page appears. You must first delete the manager on the sensor and delete the sensor on the Defense Center. For more information. see the Sourcefire 3D Sensor Software for X-Series Installation Guide. TIP! To temporarily disable communications between appliances without having to reset management. The procedures for resetting management on the 3Dx800 sensors and on Crossbeam-based software sensors differ from the procedure for other sensors.9. Select Operations > System Settings. Using a user account with Admin access. 4.1 Sourcefire 3D System Administrator Guide 122 .Using the Defense Center Working with Sensors Chapter 4 3. Log into the web interface of the Defense Center where you want to reset communications. For more information on resetting management on a Crossbeam-based software sensor. Click Delete next to the Defense Center where you want to reset management. Select Operations > Sensors. log into the web interface of the sensor you want to delete. 6. Click Remote Management. see Resetting Communications on the 3Dx800 on page 128.

To re-add the sensor to the Defense Center: Access: Admin 1. type the one-time use registration key that you want to use to set up a communications channel between the sensor and the Defense Center. Click Remote Management. maple. use both the Registration Key and the Unique NAT ID fields. you can delete the management on the sensor. Log into the web interface of the sensor where you want to reset communications and click Add Manager. 3. To delete management on the sensor: Access: Admin 1. In the Registration Key field. 3.com. You must delete the appliance from its manager. The Add Remote Management page appears. In that case. Communication between the sensor and the Defense Center is discontinued and the sensor is deleted from the Sensors page. 2. Log into the web interface of the sensor where you want to reset communications.9. In the Management Host field. Version 4. 2. The Remote Management page appears. If your sensor is no longer communicating with the Defense Center. Click Delete next to the sensor you want to delete. Click Delete next to the Defense Center where you want to reset management.Using the Defense Center Working with Sensors Chapter 4 3. type the IP address or the host name of the Defense Center that you want to use to manage the sensor. You can leave the Management Host field empty if the management host does not have a routable address. If you attempt to delete management on the sensor while it is communicating with the Defense Center you will receive an error similar to: Delete failed.1 Sourcefire 3D System Administrator Guide 123 . WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. The manager is removed. The Information page appears.example. Select Operations > System Settings. 4.

WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. type the same value in the Unique NAT ID field. packet data is not retained. Click New Sensor. in the Unique NAT ID field. If you used a unique NAT ID in step 4. Version 4. 9. By default. If you elect to prohibit sending packets and you do not store events on the 3D Sensor. data is stored only on the Defense Center and not on the sensor. 12. 7. Log into the Defense Center’s web interface using a user account with Admin access. the Pending Registration status appears. 11. type the same one-time use registration key that you used in step 3. 8. The Sensors page appears. Packet data is often important for forensic analysis. After the sensor confirms communication with the Defense Center.1 Sourcefire 3D System Administrator Guide 124 .Using the Defense Center Working with Sensors Chapter 4 4. 10. The Add New Sensor page appears. Click Save. 6. In the Registration Key field. You can store data on both the Defense Center and the sensor by clearing the Store Events and Packets Only on the Defense Center check box. Type the IP address or the hostname of the sensor you want to add in the Host field. Optionally. and select Operations > Sensors. You can prevent packet data from leaving a sensor by checking the Prohibit Packet Transfer to the Defense Center check box. 5.9. type a unique ID that you want to use to identify the sensor.

see Managing Sensor Groups on page 131. you must add them to a Defense Center as managed sensors so that you can perform procedures such as: • • • • creating and applying intrusion and RNA detection policies viewing events generating reports uploading and installing software updates The following sections explain how to manage 3Dx800 sensors with a Defense Center: • • • Managing 3Dx800 Sensors with a Defense Center on page 125 Deleting a 3Dx800 Sensor from the Defense Center on page 127 Resetting Communications on the 3Dx800 on page 128 Managing 3Dx800 Sensors with a Defense Center Requires: DC + 3D Sensor Setting up communications between a 3Dx800 sensor and a Defense Center is a two-step process that involves setting up the sensor and then adding the sensor to the Defense Center. It can take up to two minutes for the Defense Center to verify the sensor’s heartbeat and establish communication. To add the sensor to a group. For more information about groups. The sensor is added to the Defense Center. select the group from the Add to Group list. Click Add. This procedure assumes that you have completed the setup steps described in the sensor’s Installation Guide.Using the Defense Center Working with Sensors Chapter 4 13.domain [admin] Version 4. The CLI prompt appears. To manage a 3Dx800 sensor with a Defense Center: Access: Admin 1. 3D Sensor 5800. Managing a 3Dx800 Sensor Requires: DC + 3D Sensor Because the Sourcefire 3D Sensor 3800.9. you may need to use the Add Manager feature a second time to add the secondary Defense Center. 14. Log into the 3D Sensor using the admin account. sensor.1 Sourcefire 3D System Administrator Guide 125 . and 3D Sensor 9800 (usually called the 3Dx800 sensors) do not have their own web interfaces. In some high availability deployments where network address translation is used. Contact technical support for more information. You can view the sensor’s status on the Sensors page (Operations > Sensors).

The NAT ID together with the registration key must uniquely identify the communications channel between the sensor and the Defense Center.Using the Defense Center Working with Sensors Chapter 4 2. Using a user account with Admin access. 5. Enter the following at the CLI prompt: [admin] configure sensor 3. 4.1 Sourcefire 3D System Administrator Guide 126 . the sensor may be managed by another Defense Center. log into the web interface of the Defense Center where you want to add the sensor. Use the following command to determine whether remote management is already enabled: [admin:sensor] show management If management is already enabled. Use one of the following commands to enable management on the 3D Sensor: • If you are deploying your sensor in a network that does not use network address translation.9. Version 4. enter the following command: [admin:sensor] set management enable ip_address reg_key where ip_address is the IP address of the Defense Center and reg_key is a unique single-use alphanumeric registration key. The IP address and registration key pair must uniquely identify the communications channel between the sensor and the Defense Center. 8. In either case. a message appears indicating that remote management is enabled. If you changed the management port on the Defense Center. you must change it on the 3Dx800 also: [admin:sensor] set management port port_number where port_number is the same port number you used on the Defense Center. The Sensors page appears. reg_key is a unique single-use alphanumeric registration key. 6. Select Operations > Sensors. See Resetting Communications on the 3Dx800 on page 128 for information about deleting the sensor from the other Defense Center and preparing it for new management. and nat_id is a unique alphanumeric string. Use the following command to exit the CLI and return to the login prompt: [admin:sensor] exit 7. • If you are deploying your sensor in a network that does use network address translation. enter the following command: [admin:sensor] set management enable NONE reg_key nat_id where NONE is a placeholder for the unresolvable IP address of the Defense Center.

you must complete a two-step process to disable remote management and then delete it from the Defense Center. In the Host field. packet data. The 3Dx800 is added to the Defense Center. 12. 11. type the same one-time use registration key that you used on the sensor. 14. type the same value in the Unique NAT ID field. In the Registration Key field. make sure the Store Events and Packets Only on the Defense Center check box is selected. Deleting a 3Dx800 Sensor from the Defense Center Requires: DC + 3D Sensor If you want to delete a 3Dx800 sensor from a Defense Center (for example.9. It can take up to two minutes for the Defense Center to verify the sensor’s heartbeat and establish communication. which is often important for forensic analysis. type the IP address or the hostname of the sensor you want to add. Version 4. 10. Click Add. is not retained anywhere. Click New Sensor. to manage it with a different Defense Center).Using the Defense Center Working with Sensors Chapter 4 9. If you used a NAT ID in step 4. 13. If you prohibit sending packets to the Defense Center. IMPORTANT! Because 3Dx800 sensors do not have any local storage for events. The Add New Sensor page appears. For more information about groups. see Managing Sensor Groups on page 131. 15. You can prevent packet data from leaving a sensor by checking the Prohibit Packet Transfer to the Defense Center check box. select the name of the group from the Add to Group list. To add the sensor to a group.1 Sourcefire 3D System Administrator Guide 127 .

The CLI prompt appears. To reset communications between the sensor and the Defense Center: Access: Admin 1. Log into the web interface of the Defense Center that manages the sensor. 6.domain [admin] 2. access the command prompt and use the admin account to log in.1 Sourcefire 3D System Administrator Guide 128 . 4.Using the Defense Center Working with Sensors Chapter 4 To delete a 3Dx800 sensor from a Defense Center: Access: Admin 1. For more information. access the command prompt and use the admin account to log in. see the next section. Enter the following command to disable remote management: [admin:sensor] set management disable A message appears indicating that remote management is disabled. Log into the web interface of the Defense Center where you want to delete the sensor. The sensor is deleted. The sensor is deleted. On the sensor. On the sensor. Enter the following command to exit the CLI and return to the login prompt: [admin:sensor] exit To add the sensor to either the same or a different Defense Center. Select Operations > Sensors. sensor. The CLI prompt appears.9. Version 4. 3. 7. The Sensors page appears. you can manually reset communications on the sensor. The Sensors page appears. sensor. Click Delete next to the sensor that is no longer communicating with the Defense Center.domain [admin] 5. 4. Click Delete next to the sensor you want to delete. Select Operations > Sensors. Resetting Communications on the 3Dx800 Requires: DC + 3D Sensor If communication fails between a 3Dx800 sensor and the Defense Center that manages it. Resetting Communications on the 3Dx800. 3. you must re-enable remote management and then add the sensor to the Defense Center. Enter the following at the CLI prompt: [admin] configure sensor 2.

Communications are restarted and the sensor is re-added to the Defense Center.1 Sourcefire 3D System Administrator Guide 129 . The Sensors page appears. re-add the sensor by clicking New Sensor. reg_key is a unique single-use alphanumeric registration key. In either case.Using the Defense Center Working with Sensors Chapter 4 5. On the Defense Center’s Sensors page. • If your sensor is in a network that does use network address translation. Click Add. enter the following command: [admin:sensor] set management enable ip_address reg_key where ip_address is the IP address of the Defense Center and reg_key is a unique single-use alphanumeric registration key. The IP address and registration key pair must uniquely identify the communications channel between the sensor and the Defense Center. enter the following command: [admin:sensor] set management enable NONE reg_key nat_id where NONE is a placeholder for the unresolvable IP address of the Defense Center. Version 4. Enter the following command to exit the CLI and return to the login prompt: [admin:sensor] exit 9. Use one of the following commands to enable remote management. 10. 11. 8. In the Host field. type the IP address or hostname of the sensor and make sure the Store Events and Packets Only on the Defense Center check box is selected. Enter the following at the CLI prompt: [admin] configure sensor 6. • If your sensor is in a network that does not use network address translation. and nat_id is a unique alphanumeric string. The NAT ID together with the registration key must uniquely identify the communications channel between the sensor and the Defense Center. 7.9. remote management is enabled again. Enter the following command to disable remote management: [admin:sensor] set management disable Remote management is disabled.

In the Name Of Agent field. Version 4. The Intrusion Agent is added and the page reloads.Intrusion Agent Page on page 130. enter the IP address granted by the NAT device.Using the Defense Center Working with Sensors Chapter 4 Adding Intrusion Agents Requires: DC + Intrusion Agent The Add Agent page allows you to add an Intrusion Agent. event view pages. 4. you should the IP address that the Defense Center will “see” when the Intrusion Agent attempts to communicate with it. Access the Defense Center web interface and select Operations > Sensors. It will appear on the event summary. To download authentication credentials. 6. This is the name that the Defense Center uses to identify the Intrusion Agent. see Sensor Attributes . register all Intrusion Agents to the primary Defense Center.9.Intrusion Agent Page Requires: DC + Intrusion Agent The Sensor Attributes page for Intrusion Agents allows you to view basic information about the Intrusion Agent and allows you to download authentication credentials. Click Download Auth Credentials and save them for later use on the Intrusion Agent. WARNING! If your Intrusion Agent sensor resides behind a NAT device. The Managed Sensors page appears. and reports. see the Sourcefire Intrusion Agent Configuration Guide. In the Hostname or IP Address field. Click Add Agent. The Agent Administration page appears. type an identifying name for the agent. To add an Intrusion Agent: Access: Admin 1. that is.1 Sourcefire 3D System Administrator Guide 130 . displaying a link that allows you to download authentication credentials. Sensor Attributes . 2. During configuration. Click New Agent. 5. type the Intrusion Agent’s host name (if DNS resolution is enabled on the Defense Center) or IP address. you copy this file to the Intrusion Agent appliance to allow the Intrusion Agent to authenticate with the Defense Center. 3. For information on the requirements for the intrusion agent side of the connection. IMPORTANT! When using Intrusion Agents registered to Defense Centers configured for high availability and managed by a Master Defense Center.

3. To create a sensor group and add sensors to it: Access: Admin 1. Deleting Sensor Groups on page 133 explains how to delete a sensor group. select Operations > Sensors. For more information about copying the credentials. and update multiple sensors with new software updates at the same time. See the following sections for more information: • • • Creating Sensor Groups on page 131 explains how to create a sensor group on the Defense Center.1 Sourcefire 3D System Administrator Guide 131 . 2. see Managing Appliance Groups on page 179. The Managed Sensors page appears. see the Sourcefire Intrusion Agent Configuration Guide. To download authentication credentials from the Sensor Attributes page: Access: Admin 1. Editing Sensor Groups on page 132 explains how to modify the list of sensors in a sensor group. Click Download Credential File. You are prompted to download the credentials to your local computer. The Sensors page appears.Using the Defense Center Managing Sensor Groups Chapter 4 Authentication credentials are unique to each Intrusion Agent appliance and Defense Center and cannot be copied from one appliance to another. Version 4. Click Edit next to the Intrusion Agent. The System Settings page for the Intrusion Agent appears. Access the Defense Center web interface and select Operations > Sensors. On the Defense Center.9. Managing Sensor Groups Requires: DC + 3D Sensor The Defense Center allows you to group sensors so that you can easily apply policies and install updates on multiple sensors. For information about Defense Center groups. Creating Sensor Groups Requires: DC + 3D Sensor Grouping managed sensors allows you to configure multiple sensors with a single system or health policy.

Click Save. In the Group Name field. The Sensor Group Edit page appears. The sensors are added to the group. The Sensors page appears. The Create Sensor Group page appears. select Operations > Sensors. TIP! You must remove a sensor from its current group before you can add it to a new group. 3. 7. Click Save. Click Create New Sensor Group.9. Moving a sensor to a new group does not change its policy to the policy previously applied to the group. See Applying an Intrusion Policy in the Analyst Guide for details. 5. Editing Sensor Groups Requires: DC + 3D Sensor You can change the set of sensors that reside in any sensor group. The group is added. To change the sensor’s policy. Version 4.1 Sourcefire 3D System Administrator Guide 132 . 6. return to the Sensors page (Operations > Sensors) and click Edit next to the name of the sensor group. 4. To add sensors to the group. Select the IP addresses or hostnames of the sensors you want to add from the Available Sensors list and click the arrow to move them into sensor group. you must apply a new policy to the sensor or sensor group.Using the Defense Center Managing Sensor Groups Chapter 4 2. To edit a sensor group: Access: Admin 1. On the Defense Center. type the name of the group you want to create.

To remove a sensor from a group. Deleting Sensor Groups Requires: DC + 3D Sensor If you delete a group that contains sensors. select it from the Available Sensors list and click the arrow pointing toward the group you are editing.9. The Sensor Group Edit page appears. The Sensors page appears. Select Operations > Sensors. Editing a Managed Sensor’s System Settings Requires: DC or 3D Sensor Each sensor has a number of system settings.Using the Defense Center Editing a Managed Sensor’s System Settings Chapter 4 2.1 Sourcefire 3D System Administrator Guide 133 . Select the sensor you want to move and click the arrow to add or remove it from the group. On an unmanaged sensor you can use the sensor’s web interface to modify the settings as needed. • • To add a sensor to the group. Click Edit next to the sensor group you want to edit. Click Delete next to the group you want to delete. 3. To delete a sensor group: Access: Admin 1. 2. the sensors are moved to Ungrouped on the Sensors page. select it from the list in the group you are editing and click the arrow pointing to the Available Sensors list. 4. When you Version 4. They are not deleted from the Defense Center. Click Done.

The Sensors page appears. see Stopping and Restarting a Managed Sensor on page 137. For more information. For more information.Using the Defense Center Editing a Managed Sensor’s System Settings Chapter 4 manage one or more sensors with a Defense Center. 3. It is possible to select a setting that makes it difficult to access the web interface. see Editing Network Interface Configurations on page 380. You must perform those tasks on the sensor’s web interface (generally before you begin to manage the sensor with the Defense Center). See Configuring System Settings on page 360 for more information about system settings.1 Sourcefire 3D System Administrator Guide 134 . modify the default settings for each network interface on the managed sensor. WARNING! Do not modify the settings for the management interface unless you have physical access to the appliance. The Appliance page appears and includes a list of links on the left side of the page that you can use to navigate between pages. On the Defense Center. see Viewing a Sensor’s Information Page on page 135. Click Edit next to the name of the sensor where you want to edit the system settings. you can: • • view detailed information about the sensor. For more information. To edit the system settings for a managed sensor: Access: Admin 1. • reboot or restart the processes on the managed sensor. select Operations > Sensors.9. Version 4. 2. you can modify their system settings through the Defense Center’s web interface. From the System Settings page. IMPORTANT! You cannot edit the network settings or add a license file to a sensor through the Defense Center’s web interface.

The operating system currently running on the managed sensor. Product Model Software Version Store Events Only on Defense Center Prohibit Packet Transfer to the Defense Center Operating System Operating System Version VDB Version IPv4 Address Version 4. • • Viewing a Sensor’s Information Page Requires: DC or 3D Sensor The Information page for a managed sensor includes the fields described in the Sensor Information table. Enable this check box to store event data on the Defense Center.1 Sourcefire 3D System Administrator Guide 135 . Clear this check box to store event data on both appliances. The version of the software currently installed on the managed sensor.Using the Defense Center Editing a Managed Sensor’s System Settings Chapter 4 • manage communications between the sensor and the Defense Center.9. Note that is the name of the sensor in the Defense Center web interface. See Editing Settings for a Managed Defense Center on page 175. For more information. Sensor Information Field Name Description The assigned name for the managed sensor. Enable this check box to prevent the managed sensor from sending packet data with the events. Clear this check box to allow packet data to be stored on the DC with events. the fields are slightly different. blacklist individual health policy modules on the managed sensor. The model name for the managed sensor. see Managing Communication on a Managed Sensor on page 138. but not the managed sensor. For more information. The version of the operating system currently running on the managed sensor. When you view the Information page for a managed Defense Center from the Master Defense Center’s web interface. see Blacklisting a Health Policy Module on page 537. not the hostname. manage time settings on the managed sensor. The IPv4 address of the managed sensor. see Setting the Time on a Managed Sensor on page 139. For more information. The version level of the vulnerability database currently loaded on the managed sensor.

If you hover your cursor over the icon. The sensor group that the sensor belongs to. To edit a managed sensor’s settings: Access: Admin 1. • The name of the current health policy is listed under Health. the name of the policy appears in italics. if any. This number can be important for troubleshooting. Model Number Current Group The model number for the sensor. Select Operations > Sensors.1 Sourcefire 3D System Administrator Guide 136 . Status An icon showing the current status of the managed sensor. You can click Refresh to update the Status icon and its accompanying pop-up message. Version 4. See Creating Sensor Groups on page 131 for more information. a pop-up message indicates how long it has been (in hours.9. If a policy has been updated since it was last applied. • The name of the current system policy is listed under System. minutes. if you applied one from the Defense Center that manages the sensor. The appliance-level policies currently applied to the managed sensor. The Sensors page appears. and seconds) since the sensor communicated with the Defense Center.Using the Defense Center Editing a Managed Sensor’s System Settings Chapter 4 Sensor Information (Continued) Field IPv6 Address Current Policies Description The IPv6 address of the managed sensor.

3. Click Save. See the Sensor Information table on page 135 for a description of each field. RNA Software for Red Hat Linux. You can edit the following: • • • the sensor’s hostname where events generated by the sensor are stored the group in which the sensor resides WARNING! Sensor host names must be made up of a combination of alphanumeric characters and should not be made up of numeric characters only. 4.Using the Defense Center Editing a Managed Sensor’s System Settings Chapter 4 2. Version 4. Change the sensor’s attributes as needed. and Intrusion Agents. The Information page for that sensor appears. You must use the command line interface (CLI) to manage processes on Crossbeam-based software sensors. The updated sensor attributes are saved. you can reboot or restart the processes on a managed sensor using the Defense Center’s web interface.1 Sourcefire 3D System Administrator Guide 137 . Click Edit next to the name of the sensor whose system settings you want to edit.9. Stopping and Restarting a Managed Sensor Requires: DC For 3D Sensors.

click Run Command next to Restart Appliance Console. 2.1 Sourcefire 3D System Administrator Guide 138 . Select Operations > Sensors. If you want to restart the software processes on the sensor. 4. but does not physically shut off power. 3. you can manage communications between a managed sensor and the Defense Center managing it using the Defense Center’s web interface. To shut off power. If you want to restart the Snort and RNA processes. RNA Software for Red Hat Linux. you must press the power button on the appliance. WARNING! If you shut down the appliance.9. Click Edit next to the name of the sensor that you want to restart.Using the Defense Center Editing a Managed Sensor’s System Settings Chapter 4 To shut down or restart a managed sensor: Access: Admin 1. click Run Command next to Reboot Appliance. The Sensors page appears. Crossbeam-based software sensors. click Run Command next to Shutdown Appliance. The Sensors page appears. You must use the command line interface (CLI) to manage communication on 3Dx800 sensors. Version 4. If you want to reboot the sensor. and Intrusion Agents. Select Operations > Sensors. To disable communications between the Defense Center and the sensor: Access: Admin 1. Click Process in the list to the left of the page. click Run Command next to Restart Detection Engines. The Information page for that sensor appears. the process shuts down the operating system on the appliance. Specify what command you want to perform: • • • • If you want to shut down the sensor. The Process page appears for your managed sensor. Managing Communication on a Managed Sensor Requires: DC + 3D Sensor For most 3D Sensors.

then you cannot change the time manually. Click Edit next to the name of the sensor where you want to set the time. if the system policy applied to the managed sensor allows you to set the time manually. The Information page for that sensor appears. Version 4. Click Edit next to the name of the sensor that you want to manage.9.1 Sourcefire 3D System Administrator Guide 139 . TIP! To enable communications between the two appliances again. Click Disable next to the name of the sensor.Using the Defense Center Editing a Managed Sensor’s System Settings Chapter 4 2. To set the time for a managed sensor: Access: Admin 1. However. Communications between the two appliances are interrupted. click Enable. For information about editing the remote management communications from a sensor see Configuring Remote Access to the Defense Center on page 386. For 3D Sensors. which is the recommended setting for a managed sensor and its Defense Center. The Remote Management page appears. Setting the Time on a Managed Sensor Requires: DC or 3D Sensor If your managed sensor is receiving its time from an NTP server. 2. The Sensors page appears. You cannot manage time settings on Intrusion Agents. you can manage time settings on a managed sensor using the Defense Center’s web interface. Select Operations > Sensors. The Information page for that sensor appears. Click Remote Management in the list to the left of the page. You must use the command line interface (CLI) to manage time settings on Crossbeam-based software sensors and RNA Software for Red Hat Linux. 3. then you can change it as part of the system settings. See the NTP Status table on page 390 for a description of the values you are likely to see for a sensor that is synchronized with an NTP server. 4.

6. When you connect the two 3D9900 sensors you determine which is the master. 4. In other words. 7. A pop-up window appears. From the Set Time drop-down lists. after the time zone setting is saved. use a Defense Center to establish the clustered pair relationship between the two sensors and manage their joint resources. click the time zone link located next to the date and time.9. This setting does not affect the time zone setting on the managed sensor. Click Apply. Managing a Clustered Pair Requires: DC + 3D9900 You can increase the amount of traffic inspected on a network segment by connecting two fiber-based 3D9900 sensors in a clustered pair.1 Sourcefire 3D System Administrator Guide 140 . If you want to change the time zone. Click Time in the list to the left of the page. Changing the time zone with this option is equivalent to changing the time zone using the Time Zone Settings option in the user preferences.Using the Defense Center Managing a Clustered Pair Chapter 4 3. this time zone option changes the time setting your user account uses on the Defense Center web interface. Select your time zone and click Save and. shared configuration. After you do the cabling. click Close to close the pop-up window. You connect the master to the network segment you wish to analyze. you combine the 3D9900 sensors resources into a single. select the following: • • • • • year month day hour minute 5. The Time page appears showing the current time. The time is updated. When you establish a clustered pair configuration. Version 4.

1 Sourcefire 3D System Administrator Guide 141 . see the Cluster Interconnect table. they act like two separate sensors with a single. shared detection configuration. Cluster Interconnect Master Interface ethb2 RX ethb2 TX Slave Interface ethb0 TX ethb0 RX Version 4.Using the Defense Center Managing a Clustered Pair Chapter 4 After you establish the relationship between the two sensors. The following diagram shows interfaces on the master and slave sensors. and local management is blocked on the shared portion of the clustered pair. interface set.9. and data from a clustered pair. For information on the detection engines. see: • • • Using Detection Engines on Clustered 3D Sensors on page 228 Understanding Interface Sets on Clustered 3D Sensors on page 229 Managing Information from a Clustered 3D Sensor on page 230 The Defense Center manages the clustered pair. For information about the connections between the master and slave 3D9900 sensors.

see: • • Establishing a Clustered Pair on page 142 Separating a Clustered Pair on page 144 Establishing a Clustered Pair Requires: DC + 3D9900 You can group two fiber-based 3D9900 sensors in a clustered pair to increase throughput. Before you begin. see the Sourcefire 3D Sensor Installation Guide. After you establish the relationship. IMPORTANT! If you apply an RNA detection policy to the RNA detection engines on two different 3D9900 sensors and then establish clustering with those two sensors. you must edit and reapply your detection policy after you establish clustering. Connect the master’s ethb2 and ethb3 pair to the slave’s ethb0 and ethb1 pair as shown in the Cluster Interconnect table.Using the Defense Center Managing a Clustered Pair Chapter 4 Cluster Interconnect Master Interface ethb3 RX ethb3 TX Slave Interface ethb1 TX ethb1 RX You connect the master to the network and the slave to the master. You determine the master/slave designation by the way you cable the pair.8. you must: • • • decide which unit will be the master have SEU 2.9. you cannot change which sensor is the master or slave unless you break and reestablish the relationship using the Defense Center. For more information. IMPORTANT! You cannot connect the slave’s ethb2 and ethb3 pair when you establish the clustered pairing. the detection engines and interface set are combined on the two sensors.6 or later loaded on your 3D9900 and Defense Center cable the units properly prior to designating the master/slave relationship Connect the master’s ethb0 and ethb1 pair to the network.1 Sourcefire 3D System Administrator Guide 142 . For more information about cabling. Version 4. After you establish the master/slave relationship.

instead of the 3D9900 sensors. 3. TIP! If you edit a 3D9900 that is not cabled as the master. The Sensor page appears. To establish 3D9900 clustered pairing: Access: Admin 1. the following message is displayed. 2. Version 4. Select Operations > Sensors on your Defense Center. In the Clustering field. select the sensor you want to form a cluster with.com. The Click Edit next to the 3D9900 sensor that you cabled for master operation.com. For example.1 Sourcefire 3D System Administrator Guide 143 .example. If you attempt to manage the combined detection engines and interface set on the paired 3D9900 sensors. They are managed from the Defense Center. if the other member of your pair is birch. Clustering is established and a confirmation message appears.9. select Clustered with birch.Using the Defense Center Managing a Clustered Pair Chapter 4 There is one detection engine and interface set shared over the paired 3D9900 sensors. you cannot perform the next series of steps. The System Settings page appears and there is a Clustering field at the bottom. under status.example.

5. it removes detection configurations (interface sets. the sensing traffic is interrupted. 3. 5. Select Break Cluster in the Clustering field.Using the Defense Center Managing a Clustered Pair Chapter 4 4. Use the managing Defense Center to establish the cluster’s detection configurations for the interface set and detection engines. the field reads: Status Clustered and Role Slave • 3D9900 clustering is established.1 Sourcefire 3D System Administrator Guide 144 . • On the master. the field reads: Status Clustered sensor_name. For example: 4. The 3D9900 sensors separate and the confirmation message disappears. Click OK to confirm the Master/Slave pairing. If the system determines that the cabling is correct. Review the confirmation message and confirm the correct the Master/Slave pairing. Review the confirmation message. After clustering is established. IMPORTANT! While system verifies the cabling configuration. On the slave. Click Save. Version 4. The Sensor page appears. The System Settings page appears with the Clustering field at the bottom. Separating a Clustered Pair Requires: DC + 3D9900 If you no longer need to use the two 3D9900 sensors as a clustered pair.9. To separate a 3D9900 clustered pair: Access: Admin 1. Click Edit next to the 3D9900 sensor that you designated as the maser sensor when you connected the pair’s cables. Select Operations > Sensors on your Defense Center. verify that the Clustering field changes to indicate the correct state. 6. you can use the Defense Center to break the cluster. Note the Master/Slave pairing and click OK to confirm the Master/Slave that you want to separate the clustered pair. detection engines) from the slave. 2. where sensor_name is the name of the sensor you designated as the slave in step 3 and Role Master.

Sourcefire strongly recommends that both Defense Centers in an HA pair be the same model.Using the Defense Center Configuring High Availability Chapter 4 Configuring High Availability Requires: DC To ensure the continuity of operations. Monitoring the High Availability Status on page 152 explains how to check the status of your linked Defense Centers. Guidelines for Implementing High Availability on page 149 outlines some guidelines you must follow if you want to implement high availability. you can monitor your network for intrusion events. Using High Availability Requires: DC The DC1000 and DC3000 models of the Defense Center support high availability configurations. Pausing Communication between Paired Defense Centers on page 154 explains how to pause communications between linked Defense Centers. Restarting Communication between Paired Defense Centers on page 154 explains how to restart communications between linked Defense Centers.1 Sourcefire 3D System Administrator Guide 145 . do not attempt to set up high availability between a Defense Center 1000 and a Defense Center 3000. RNA events.9. and compliance events without interruption using the second Defense Center. Setting Up High Availability on page 150 explains how to specify primary and secondary Defense Centers. WARNING! Sourcefire recommends that you change configurations only on the primary Defense Center and that you keep your secondary Defense Center as a backup. If one Defense Center fails. That is. Disabling High Availability and Unregistering Sensors on page 153 explains how to permanently remove the link between linked Defense Centers. Version 4. RUA events. See the following sections for more information about setting up high availability. the high availability feature allows you to designate redundant Defense Centers to manage 3D Sensors. The DC500 model of the Defense Center and the Virtual Defense Center do not support high availability. • • • • • • • Using High Availability on page 145 list the items that are and are not duplicated when you implement high availability. Event data streams from managed sensors to both Defense Centers and certain configuration elements are maintained on both Defense Centers.

such as the sensor’s host name. • • RNA detection policies RNA custom service detectors Version 4. because both Defense Centers must have an admin account.9.1 Sourcefire 3D System Administrator Guide 146 . make sure you remove duplicate user accounts from one of the Defense Centers. RNA.Using the Defense Center Configuring High Availability Chapter 4 For more information on: • • • • sensor attributes and user information shared in a high availability pair. and the group in which the sensor resides intrusion. Also. you must make sure that the admin account uses the same password on both Defense Centers. • • • • • • • • • • custom dashboards authentication objects for Sourcefire 3D System user accounts custom workflows custom tables sensor attributes. where events generated by the sensor are stored. see Health and System Policies on page 147 feature license operation in a high availability pair. see Understanding High Availability on page 148 Sensor Configurations and User Information Requires: DC Defense Centers in a high availability pair (also called an HA pair) share the following sensor attributes and user information: • user account attributes and authentication configurations WARNING! Before you establish a high availability. and RUA detection engines intrusion policies and their associated rule states local rules custom intrusion rule classifications variable values and user-defined variables IMPORTANT! If your deployment includes intrusion agents and you are also using a Master Defense Center to manage your linked Defense Centers. see Feature Licenses on page 148 details of high availability pair operation. see Sensor Configurations and User Information on page 146 health and system policies shared in a high availability pair. make sure you register all intrusion agents to the primary Defense Center. if you have any user accounts with the same name on both Defense Centers.

However. is synchronized on a newly activated Defense Center. Health and System Policies Requires: DC Health and system policies for Defense Centers and 3D Sensors are shared in high availability pairs. modules. make sure you remove the associations so responses and remediations will only be generated by the primary Defense Center. For more information. you should quickly associate your compliance policies with the appropriate responses and remediations on the secondary Defense Center to maintain continuity of operations. you can synchronize time with multiple alternative NTP servers. and the deactivation or modification of vulnerabilities compliance policies and their associated rules compliance white lists • • To avoid launching duplicate responses and remediations when compliance policies are violated. For more information. the NTP function does not automatically switch. Although system policies are shared by Defense Centers in a high availability pair. For 3D Sensors.9. they are not automatically applied. including notes and host criticality. blacklists. If you want identical system policies on both Defense Centers.1 Sourcefire 3D System Administrator Guide 147 . apply the policy after it synchronizes. If the primary Defense Center fails. you can point to one Defense Center as your first NTP server and the other Defense Center as your second NTP server.You must upload and install any custom remediation modules and configure remediation instances on your secondary Defense Center before remediations are available to associate with compliance policies. Allow enough time to ensure that 3D Sensor information about health policies. and networks from the network map. Defense Centers do not share the associations between the policies and their responses and remediations. When you restore your primary Defense Center after a failure. Version 4. the deletion of hosts. see Creating Compliance Policies in the Analyst Guide and Configuring Remediations in the Analyst Guide.Using the Defense Center Configuring High Availability Chapter 4 • • • • activated custom fingerprints host attributes traffic profiles RNA user feedback. if you created associations between rules or white lists and their responses and remediations on the secondary Defense Center. see Synchronizing Time on page 354. services. TIP! If you employ an HA paired Defense Center as a NTP server.

1 Sourcefire 3D System Administrator Guide 148 . and NetFlow licenses: • • Both Defense Centers must have RNA host licenses if you want to manage 3D Sensors with RNA with the high availability pair. If one Defense Center does not have a NetFlow license.9. if the primary Defense Center fails. IMPORTANT! An RUA Agent can only connect to one Defense Center at a time. • While RUA LDAP authentication objects are shared. if you want to use NetFlow data to supplement the data gathered by your 3D Sensors with RNA. While NetFlow data and devices are shared. the two Defense Centers must have enough NetFlow licenses to merge the list of devices on each. both Defense Centers must have RUA licenses if you want to manage 3D Sensors with RUA with the high availability pair. so changes appear within two five-minute Version 4. RUA. it will not receive data from your NetFlow-enabled devices. you can make policy or other changes to either Defense Center. but the cycles themselves could be out of sync by as much as five minutes. For more information. you must make sure that your RUA Agents can communicate with the secondary Defense Center. and any change you make to one Defense Center should be applied on the other Defense Center within ten minutes. Understanding High Availability Requires: DC Although Defense Centers in high availability mode are named “primary” and “secondary. ” Defense Centers periodically update each other on changes to their configurations. (Each Defense Center has a five-minute synchronization cycle. In an high-availability environment. TIP! Both Defense Centers in a high-availability pair must have NetFlow licenses for at least the number of NetFlow-enabled devices you are using.Using the Defense Center Configuring High Availability Chapter 4 Defense Centers in an HA pair share the following system and health policy information: • • • • • • system policies system policy configurations (what policy is applied where) health policies health monitoring configurations (what policy is applied where) which appliances are blacklisted from health monitoring which appliances have individual health monitoring policies blacklisted Feature Licenses Requires: DC Defense Centers in an HA pair do not share RNA. see Configuring an RUA Agent on an Active Directory Server in the Analyst Guide.

the Defense Centers use port 8305/tcp for communications. Because the sensor has a policy applied to it that the secondary Defense Center does not recognize. the last change you make takes precedence. nor created any new rules. see Guidelines for Implementing High Availability on page 149. TIP! To avoid confusion. both Defense Centers can be configured with policies. if you make conflicting policy or other changes to both Defense Centers within the same window between Defense Centers syncs. • You must designate one Defense Center as the primary Defense Center and one as the secondary. start with the secondary Defense Center in its original state. You can change the port as described in Configuring the Communication Channel on page 383. Regardless of their designations as primary and secondary. You cannot configure a recurring task schedule on the inactive Defense Center. For more information. You must recreate the recurring task schedule on a newly activated Defense Center when it changes from inactive to active. For example. Both Defense Centers must be running the same software version. Both Defense Centers must be running the same SEU version. Also. use the Restore CD to remove changed settings. Note that this also deletes event and configuration data from the Defense Center. Defense Centers configured as a high availability pair do not need to be on the same trusted management network. and so on before you set up high availability. That is. the secondary Defense Center displays a new policy with the name “unknown” until the Defense Centers synchronize. nor have you previously managed any sensors with it. managed sensors. Guidelines for Implementing High Availability Requires: DC To take advantage of high availability.1 Sourcefire 3D System Administrator Guide 149 . nor do they have to be in the same geographic location. during this ten-minute window. you must follow these guidelines. regardless of the designations of the Defense Center as primary and secondary. policies may appear incorrectly on the other Defense Center. • • • Version 4. you have not created or modified any policies.Using the Defense Center Configuring High Availability Chapter 4 cycles. the sensor could contact the secondary Defense Center before the Defense Centers contact each other. rules. The Defense Center software version must be the same or newer than the software version of managed 3D Sensors. • By default. To make sure the secondary Defense Center is in its original state. if you create a policy on your primary Defense Center and apply it to a sensor that is also managed by your secondary Defense Center.) However.9.

• Setting Up High Availability Requires: DC To use high availability. The two Defense Centers do not need to be on the same network segment.9. If you use a Master Defense Center to manage a high-availability pair of Defense Centers. add the primary Defense Center and the secondary Defense Center is automatically added. and vice versa. Version 4. Select Operations > Configuration > High Availability. use this sequence to establish communications between the three of them: First. For details on setting time. TIP! To add an existing high availability pair of Defense Centers to a Master Defense Center. see Adding a Master Defense Center on page 165. see Editing the Management Virtual Network on page 385. To set up high availability for two Defense Centers: Access: Admin 1. but each of the Defense Centers must be able to communicate with the other and with the sensors they share. then set up high availability as detailed in Setting Up High Availability on page 150. Before you configure high availability. make sure you synchronize time settings between the Defense Centers you want to link. set up remote management between each Defense Center and the Master Defense Center as detailed in Adding and Deleting Defense Centers on page 164. In addition.1 Sourcefire 3D System Administrator Guide 150 . 2. That is. For information about editing the remote management communications between the two appliances. you must designate one Defense Center as the primary and another Defense Center of the same model as the secondary. the primary Defense Center must be able to contact the secondary Defense Center at the IP address on the secondary Defense Center’s own management interface. see Synchronizing Time on page 354. WARNING! Sourcefire recommends that you change configurations only on the primary Defense Center and that you use your secondary Defense Center as a backup. The High Availability page appears.Using the Defense Center Configuring High Availability Chapter 4 • • All RNA software sensors managed by Defense Centers in high availability mode must be the same software version. For information about adding a Defense Center to a Master Defense Center. Log into the Defense Center that you want to designate as the secondary Defense Center. either each Defense Center must be able to contact the sensors it manages or the sensors must be able to contact the Defense Center.

Type a one-time-use registration key in the Registration Key text box 6. In that case. 11. Select Operations > Configuration > High Availability. 7. Using an account with Admin access.9. You can leave the Primary DC Host field empty if the management host does not have a routable address. Version 4. The Primary Defense Center Setup page appears. type a unique alphanumeric registration ID that you want to use to identify the primary Defense Center. Type the hostname or IP address of the primary Defense Center in the Primary DC Host text box. A success message appears. Click the primary Defense Center option. The Secondary Defense Center Setup page appears. showing the current state of the secondary Defense Center. 5. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. Optionally. Type the hostname or IP address of the secondary Defense Center in the Secondary DC Host text box. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. and the Peer Manager page appears. Click the secondary Defense Center option. 4. 10.Using the Defense Center Configuring High Availability Chapter 4 3. 8. The High Availability page appears. See Working in NAT Environments on page 112 for more information. in the Unique NAT ID field. log into the Defense Center that you want to designate as the primary.1 Sourcefire 3D System Administrator Guide 151 . Click Register. use both the Registration Key and the Unique NAT ID fields. 9.

Log into one of the Defense Centers that you linked using high availability. You can also monitor the Task Status to see when the process completes. 14. See Monitoring the High Availability Status on page 152. including: • • • • • IP address product model operating system operation system version time the Defense Centers last synchronized To check high availability status: Access: Admin 1. it may take up to 10 minutes before all the rules and policies appear on both Defense Centers. If you used a unique NAT ID on the secondary Defense Center. A success message appears. type the same registration ID that you used in step 6 in the Unique NAT ID text box. Depending upon the number of policies and custom standard text rules they have. 2. Type the same one-time-use registration key in the Registration Key text box you used in step 5. 13.Using the Defense Center Configuring High Availability Chapter 4 12. Monitoring the High Availability Status Requires: DC Once you have identified your primary and secondary Defense Centers.9. Click Register. Version 4. showing the current state of the primary Defense Center. You can view the High Availability page to check the status of the link between the two Defense Centers.1 Sourcefire 3D System Administrator Guide 152 . and the Peer Manager page appears. The High Availability page appears. you can use one of them to view status information about the other. Select Operations > Configuration > High Availability.

For example. Sourcefire recommends that you wait at least five minutes before adding the sensor back. of the communications link the state. it may take more than one synchronization cycle to add the sensor to both Defense Centers. it is automatically shared with the other Defense Center within 5 minutes. The Peer Manager page appears. if you create a new policy on one Defense Center. 5. Disabling High Availability and Unregistering Sensors Requires: DC If you want to remove one of the Defense Centers from a high availability pair. The two Defense Centers automatically synchronize within ten minutes (five minutes for each Defense Center) after any action that affects a shared feature. of the HA pair For information about editing the remote management communications between the two appliances. see Editing the Management Virtual Network on page 385. Version 4. IMPORTANT! If you delete a sensor from a Defense Center configured in a high availability pair and intend to re-add it.1 Sourcefire 3D System Administrator Guide 153 .Using the Defense Center Configuring High Availability Chapter 4 3. If you do not wait five minutes. click Synchronize. Under High Availability Status. you can view the following information about the other Defense Center in the high availability pair: • • • • • the IP address the model name the software version the operating system the length of time since the last contact between the two Defense Centers 4. enabled or disabled. You can view the following information: • • • the IP address of the other Defense Center in the HA pair the status. This interval ensures that the high availability pair re-synchronizes first.9. if you want to synchronize the policy immediately. you must first disable the high availability link between them. registered or unregistered. However. Click Peer Manager in the toolbar.

Pausing Communication between Paired Defense Centers Requires: DC If you want to temporarily disable high availability. Select Operations > Configuration > High Availability.9. 3. see Editing the Management Virtual Network on page 385. The Peer Manager page appears. For information about editing the remote management communications between the two appliances. To stop managing the sensors altogether. you can disable the communications channel between the Defense Centers. To disable the communications channel for a high availability pair: Access: Admin 1. You can enable high availability with a different Defense Center as described in Setting Up High Availability on page 150. To control all the managed sensors with the other Defense Center. select Unregister sensors on the other peer. Click Disable to disable the communications channel between the two Defense Centers. select Unregister sensors on this peer. 2. 4. Log into one of the Defense Centers in the HA pair. Version 4. Click Disable HA. Select one of the following options from the Handle Registered Sensors dropdown list: • • • To control all the managed sensors with the Defense Center where you are accessing this page.1 Sourcefire 3D System Administrator Guide 154 . After you answer the prompt Do you really want to Disable High Availability? by selecting OK. 2. Click Peer Manager. The High Availability page appears.Using the Defense Center Configuring High Availability Chapter 4 To disable a high availability pair: Access: Admin 1. Restarting Communication between Paired Defense Centers Requires: DC If you temporarily disabled high availability. you can enable the communications channel between the Defense Centers to restart high availability. select Unregister sensors on both peers. high availability is disabled and any managed sensors are deleted from the Defense Centers according to your selection.

For information about editing the remote management communications between the two appliances.9. Click Peer Manager.Using the Defense Center Configuring High Availability Chapter 4 To enable the communications channel for a high availability pair: Access: Admin 1. Click Enable to disable the communications channel between the two Defense Centers. see Editing the Management Virtual Network on page 385. 2. Version 4.1 Sourcefire 3D System Administrator Guide 155 . The Peer Manager page appears.

and white list events from up to ten Defense Centers within your Sourcefire 3D System deployment. You can use the Master Defense Center to aggregate and analyze intrusion events. Version 4.9. compliance events.1 Sourcefire 3D System Administrator Guide 156 .Using the Master Defense Center Chapter 5 Administrator Guide The Sourcefire Master Defense Center is a key component in the Sourcefire 3D System.

The Master Defense Center can also aggregate events related to the health of managed Defense Centers. Managing Appliance Groups on page 179 explains how to use appliance groups to aid in managing 3D Sensors and Defense Centers. you can view the current status of the Defense Centers across your enterprise from a web interface. If it finds an older SEU. it updates the managing Defense Center’s SEU. the Sourcefire 3D System checks the SEU on the managing Defense Center. See the following sections for more information: • • • Aggregating Intrusion Events on page 158 Aggregating Compliance Events on page 158 Limitations on Event Aggregation on page 159 Version 4.Using the Master Defense Center Understanding Event Aggregation Chapter 5 You can use the Master Defense Center to build and dispatch global detection and intrusion policies.1 Sourcefire 3D System Administrator Guide 157 . The following sections explain more about using a Master Defense Center in your Sourcefire 3D System deployment. Understanding Global Policy Management on page 161 explains which policies you can send from your Master Defense Center to 3D Sensors and Defense Centers.9. Editing Settings for a Managed Defense Center on page 175 explains how to change some of the settings for a Defense Center from the Master Defense Center’s web interface. In this way. The settings on the Filter Configuration page determine which events are forwarded from the Defense Center to the Master Defense Center. • Understanding Event Aggregation on page 157 explains which types of events you can send from your Master Defense Centers to your Master Defense Center. IMPORTANT! The Product Compatibility section of the release notes for each version describes which versions of the Defense Center you can manage with a Master Defense Center. You can also choose whether to include the packet data collected with the intrusion events. You can set up a different configuration for each Defense Center. When you apply intrusion policies from a Master Defense Center. You can configure a Defense Center to send intrusion events based on their flag. • • • • Understanding Event Aggregation Requires: MDC A Master Defense Center can aggregate intrusion events and compliance events (including white list events) from up to ten Defense Centers. although most deployments will use the same configuration across the enterprise. Adding and Deleting Defense Centers on page 164 explains how to configure a Defense Center to communicate with a Master Defense Center.

9. preprocessors. along with any related packets. the red impact flag. RNA events. The conditions that can trigger a compliance rule include intrusion events.Intrusion events are not forwarded to the Master Defense Center. flow data.The intrusion events specified in the Flags section. Aggregating Compliance Events Requires: MDC A compliance event is generated by a Defense Center when the conditions for a compliance rule in an active compliance policy are met. When you use the Filter Configuration page to specify which events are forwarded to the Master Defense Center. Packet decoders. For example. and anomalous network traffic. you may also want to send intrusion events with the black inline result flag.The intrusion events specified in the Flags section are forwarded to the Master Defense Center. • You can use the Flags section of the Filter Configuration page to forward only the intrusion events that are important to your analysis. If you do not deploy 3D Sensors with RNA on your network.Using the Master Defense Center Understanding Event Aggregation Chapter 5 Aggregating Intrusion Events Requires: MDC An intrusion event is generated by IPS when it analyzes network traffic and finds one or more packets that violate the currently applied intrusion policy. IMPORTANT! You must deploy both RNA and IPS on your network to generate intrusion events with meaningful impact flags. however. You can also use flag settings to reduce the number of intrusion events that are sent to the Master Defense Center in deployments where large numbers of intrusion events are being generated from your 3D Sensors. Events and Packet Data . then intrusion events are limited to gray impact flags to indicate unknown impact. any packets captured for the event are not sent.1 Sourcefire 3D System Administrator Guide 158 . Events Only . For example. you can choose one of the following options: • • Do Not Send . If your 3D Sensors are deployed inline and you are using intrusion rules set to Drop and Generate Events. you can greatly reduce the number of events sent from a Defense Center by excluding events with the blue or gray impact flags. and intrusion rules are all able to generate intrusion events. are forwarded to the Master Defense Center. that is. you may want to limit the intrusion events on the Master Defense Center to only those with the greatest impact. Version 4.

and NetFlow. flow data. hosts. compliance events. network interfaces. services. The Master Defense Center and Defense Center Functional Comparison table compares and contrasts Defense Center and Master Defense Center functional areas. health events. white list events. audit log. remediation status. interface sets. health events. allows you search for intrusion events. scan results. white list violations. RNA events. Analysis and reporting search Version 4. 3D Sensor configuration allows you to configure detection engines allows you to search for intrusion events.Using the Master Defense Center Understanding Event Aggregation Chapter 5 When you use the Filter Configuration page to specify which events are forwarded to the Master Defense Center. See the following sections for more information: • • Adding a Defense Center on page 168 Editing the Event Filter Configuration on page 176 Limitations on Event Aggregation Requires: MDC The Master Defense Center is a powerful tool for analyzing the potential malicious activity across your enterprise’s network. you can choose to send or not send compliance events. white list events. host attributes. and RUA events. users. RNA and RUA feature licenses allows you to configure detection engines. Master Defense Center and Defense Center Functional Comparison Function License provisions Master Defense Center provides product license Defense Center provides product license. audit log. there are certain limitations that you should take into consideration when you design your Master Defense Center deployment. compliance events. However.1 Sourcefire 3D System Administrator Guide 159 . client applications. vulnerabilities.9. SEU import log. SEU import log.

Using the Master Defense Center Understanding Event Aggregation Chapter 5 Master Defense Center and Defense Center Functional Comparison (Continued) Function Network scans Global policies Master Defense Center does not provide for Nessus and Nmap scans.9. you might want to adjust the filter to send only intrusion events with red impact flags. Event Rate The event rate limit for the Master Defense Center is the same rate limit on Defense Centers. For example. However. Intrusion Agents Intrusion events generated by intrusion agents are not forwarded to the Master Defense Center. You can also limit the amount of data transferred between a Defense Center and its Master Defense Center by sending only intrusion event data. This means that if your Defense Centers are accepting events from their 3D Sensors up to the rate limit. the Master Defense Center does not build a network map or host data for the hosts on your network. To take advantage of this. Version 4. on your Defense Centers you need to build compliance rules and policies that are triggered by the RNA events that interest you and forward the resulting compliance events to the Master Defense Center. policies are normally downloaded only to their managed 3D Sensors Event consolidation events are collected only from managed 3D Sensors Data Generated by RNA The Master Defense Center cannot aggregate RNA events or flow data generated by RNA and forwarded to a Defense Center. and not sending the packet data. you must adjust the event filter on the Master Defense Center so that only the most important events are forwarded from the Defense Centers.1 Sourcefire 3D System Administrator Guide 160 . because you can forward compliance events and white list events from your managed Defense Centers to your Master Defense Center. In addition. allows you to build intrusion policies and to distribute them through connected Defense Centers to their managed 3D Sensors throughout the enterprise allows for collection of events from up to ten Defense Centers Defense Center provides Nessus and Nmap scans and results. you can gain insight into RNA-detected activity across your enterprise. in cases where the intrusion event rate is high.

1 Sourcefire 3D System Administrator Guide 161 . Defining IP Addresses and Ports for Your Network in the Analyst Guide provides the syntax used to specify IP addresses and port numbers within the variables and rules in your policy. delete and export RNA on a Master Defense Center. see What is an RNA Detection Policy? in the Analyst Guide. however if a newer SEU resides on the Master Defense Center than on a Defense Center in the path. The Master Defense Center sends the policy through a Defense Center to a 3D Sensor’s detection engine. if client application are being detected. Existing RNA policies are available for viewing so that you can determine: • • • • RNA policy name and description Detection policy settings such as update interval. • Version 4. Master Defense Center generated policies are not accessible on an intermediate Defense Center.Using the Master Defense Center Understanding Global Policy Management Chapter 5 Understanding Global Policy Management Requires: MDC You can use the Master Defense Center to generate global intrusion policies and coordinate them with potential vulnerabilities detected by RNA policies. Managing Global Intrusion Policies Requires: MDC Refer to the following sections for information about managing intrusion policies: • • • • Creating an Intrusion Policy in the Analyst Guide explains how to create an intrusion policy. see Importing and Exporting Objects on page 583. and so on. and health policies.9. For information on import and export functions. Which networks and ports are monitored by the RNA policy If NetFlow is used to generate host information. apply edit. as well as intrusion. You can also import and export compliance policies and rules. Managing Variables in the Analyst Guide explains how to create and manage variables that you can use within intrusion policies. custom service decoders. system. if banners and HTTP URLs are captured. You can build. RNA compares the data it collects and analyzes with its vulnerability database to determine the potential vulnerabilities on the detected host. Editing an Intrusion Policy in the Analyst Guide explains how to modify existing intrusion policies. Applying an Intrusion Policy in the Analyst Guide explains how to apply a new or updated intrusion policy to the appropriate IPS detection engines. then the downstream SEU is updated. which networks and NetFlow-enabled devices are monitored by NetFlow. This ensures that a global intrusion policies utilize the latest SEU. Global intrusion policies are beneficial in rapid response scenarios and during enterprise-wide intrusion policy updates. For information on creating and applying as well as deleting RNA policies.

edit.1 Sourcefire 3D System Administrator Guide 162 . delete. export.9. Refer to the following.Using the Master Defense Center Understanding Global Policy Management Chapter 5 • Managing Intrusion Rules in the Analyst Guide explains how to enable and disable intrusion rules within an intrusion policy. Using System Policies on a Master Defense Center Requires: MDC System policies allow you to manage the following functions on your Defense Centers or Master Defense Center: • • access configuration authentication profiles (Defense Center only) Version 4. and apply default health policies to the Master Defense Center and to connected Defense Centers. and for brief descriptions of those modules that are used. delete. and apply RNA detection policies from a Master Defense Center. for information on the following RNA detection policy functions: • • • • Creating RNA Detection Policies in the Analyst Guide Applying an RNA Detection Policy in the Analyst Guide Editing an RNA Detection Policy in the Analyst Guide Deleting an RNA Detection Policy in the Analyst Guide Using Health Policies on a Master Defense Center Requires: MDC You can edit. For information about health policies see the following: • • • • • • • Understanding Health Monitoring on page 483 Configuring Health Policies on page 489 Using the Health Monitor Blacklist on page 534 Configuring Health Monitor Alerts on page 539 Using the Health Monitor on page 545 Using Appliance Health Monitors on page 547 Working with Health Events on page 555 See Health Policies on page 164 to distinguish the health policy modules that are useful on a Master Defense Center or Defense Center from those that are not. This section also explains how to configure rules in inline intrusion policies so that they drop malicious packets. Importing SEUs and Rule Files in the Analyst Guide explains how to download and import Security Enhancement Updates (SEUs) that contain new intrusion rules. • Using RNA Detection Policies on a Master Defense Center Requires: MDC You can create. Note that SEUs can also contain new and updated decoders and preprocessors.

the Apply button activates. The Sourcefire 3D System bases intrusion policies on SEUs residing on the appliance where the policy is built. a warning message with a check box appears. edit.Using the Master Defense Center Understanding Global Policy Management Chapter 5 • • • • • • • database limits DNS cache settings the mail relay host and a notification address for database prune messages language selection (English or Japanese) login banner the kinds and amount of RNA data stored in the database (Defense Center only) time synchronization settings See Managing System Policies on page 320 for information about system policy usage. You can apply one or more custom intrusion policies filtered to monitor VLAN or subnetwork traffic on the network monitored by the detection engine where you apply the policy. the Sourcefire 3D System checks for any older SEUs on Defense Center(s) managing those detection engines. and health policies. RUA detection. Detection and Prevention Policies You can create. Master Defense Center Policy Management Limitations Requires: MDC There are several types of policies including detection and prevention. export. if your Version 4. Therefore. You cannot apply a non-filtered policy from a Defense Center then add filters to it from a managing Master Defense Center. listing RNA hosts and events. However. delete. The Defense Center and Master Defense Center do not handle these policies in the same manner. and apply intrusion detection and prevention policies from a Master Defense Center.9. TIP! Before applying a filtered policy.1 Sourcefire 3D System Administrator Guide 163 . and listing client applications and vulnerabilities are performed on Defense Centers and not on Master Defense Centers. After you acknowledge the message by clicking its check box. they are updated. If it finds SEUs older than those on the Master Defense Center. you must apply a non-filtered policy to the detection engine from the same Defense Center or Master Defense Center. RNA detection. RNA Detection Policies RNA analysis and reporting functions such as using the network map. When you apply an intrusion policy to a 3D Sensor’s detection engines from a Master Defense Center.

RUA functions are available only on properly licensed Defense Centers. System Policies System policies are applied only to Master Defense Centers and Defense Centers from a Master Defense Center. Default IPS. and Default RNA Health Policies are not used on the Master Defense Center.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 deployment includes RNA. Master Defense Centers apply health policies only to Master Defense Centers and Defense Centers. Default IPS (3Dx800 only). see the Enabled MDC Health Modules . For a listing of the health policy modules that apply to Defense Centers. SSL -encrypted communication channel between the appliances. Adding and Deleting Defense Centers Requires: MDC + DC When you manage a Defense Center with your Master Defense Center. Policies that are not applicable are implicitly disabled when there is an attempt to apply them to a Defense Center or an Master Defense Center. see Editing Health Policies on page 530. it evaluates which events. Default 3D Sensor. The Defense Center uses this channel to send events to the Master Defense Center. only the generic Default Health Policy is available for editing and application to appliances. As the Defense Center receives events from its sensors. • • • Adding a Defense Center on page 168 Deleting a Defense Center on page 171 Resetting Management of a Defense Center on page 171 Version 4.9. Currently. RUA Detection Policies There are currently no Real-Time User Awareness functions on a Master Defense Center. For a listing of the health policy modules that apply to Master Defense Centers. you set up a two-way. you can view host profiles from event views by clicking the host profile icon ( ) next to an IP address. based on filter configuration. it should send to the Master Defense Center using the same channel.1 Sourcefire 3D System Administrator Guide 164 . Health Policies The Master Defense Center monitors its health and the health of connected Defense Centers.Default Health Policy table on page 493.Default Health Policy table on page 494. For details about editing appropriate health policies. see the Enabled Defense Center Health Modules .

The Information page appears. add the remote management then at the managing Master Defense Center.9. and Unique NAT ID used on the Master Defense Center Management Host.1 Sourcefire 3D System Administrator Guide 165 .registration key Unique NAT ID (optional) . TIP! Set up the managed appliance first. At a Defense Center. Three fields are provided for setting up communications between appliances: • • • Management Host or Host.for a unique alphanumeric ID. Select Operations > System Settings. however before you do. you must make sure that the network settings are configured correctly on both appliances. 2. add the primary Defense Center and the secondary Defense Center is automatically added. Log into the web interface of the Defense Center you want to add. Registration Key. Valid combinations include: • • • Management Host or Host and Registration Key used on both appliances Registration Key and Unique NAT ID used on the Defense Center with Host. add the Defense Center. Registration Key. TIP! To add an existing high availability pair of Defense Centers to a Master Defense Center. and Unique NAT ID used on the Defense Center with Registration Key and Unique NAT ID used on the Master Defense Center IMPORTANT! The Management Host or Host field (hostname or IP address) must be used on at least one of the appliance. Version 4.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 Adding a Master Defense Center Requires: MDC + DC You can add a Master Defense Center connection to your Defense Center. See Working in NAT Environments on page 112 for more information. but you can see Configuring Network Settings on page 377 for details. To add a Master Defense Center to a Defense Center: Access: Admin 1. Registration Key . This is usually completed as part of the installation process.for the hostname or IP address. you need to determine which events on the Defense Center you want to forward to the Master Defense Center. To add a Master Defense Center.

The Remote Management page appears. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 3. The Defense Centers page appears. type the IP address or the host name of the Master Defense Center that you want to use to manage the Defense Center. in the Unique NAT ID field. Click Remote Management. and select Operations > Appliances. Log into the Master Defense Center’s web interface using a user account with Admin access. In the Registration Key field.1 Sourcefire 3D System Administrator Guide 166 . You can leave the Management Host field empty if the management host does not have a routable address. 5. In the Management Host field. 7. use both the Registration Key and the Unique NAT ID fields 6. 4. Click Save. type a unique alphanumeric NAT ID that you want to use to identify the Defense Center.9. After the Defense Center confirms communication with the Master Defense Center. type the one-time use registration key that you want to use to set up a communications channel between the Master Defense Center and the Defense Center. The Add Remote Management page appears. 8. Click Add Manager. the Pending Registration status appears. 9. In that case. Optionally. Version 4.

Click New Defense Center. In the Registration Key field. 11. Note that if you select intrusion events.1 Sourcefire 3D System Administrator Guide 167 . WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. 13. Under Filter Configuration. white list events are also sent. If you used an unique NAT ID in step 6. 14. If you chose to send compliance events to the Master Defense Center. you can send events or events and packet data. Type the IP address or the hostname of the Defense Center you want to add in the Host field. IMPORTANT! You must select at least one type of flag if you want to send intrusion events. You can leave the Host field empty if the host does not have a routable address. Version 4. type the same value in the Unique NAT ID (optional) field. use both the Registration Key and the Unique NAT ID fields 12. identify the types of events you want to forward from the Defense Center to the Master Defense Center.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 10. You can also filter which intrusion events are forwarded based on their impact flag. The New Defense Center page appears. See Editing the Event Filter Configuration on page 176 for more information. type the same one-time use registration key that you used in step 6. In that case.9.

16.1 Sourcefire 3D System Administrator Guide 168 . add the remote management. At a Defense Center. Registration Key. then at the managing Master Defense Center add the Defense Center. The Defense Center is added to the Master Defense Center. This is usually completed as part of the installation process. You can view the status on the Defense Centers page (Operations > Appliances). TIP! Set up the managed appliance first. continue with the procedure in Adding a Defense Center. Three fields are provided for setting up communications between appliances: • • • Management Host or Host. and Unique NAT ID used on the Master Defense Center Management Host.for the hostname or IP address. you must delete and re-register the Defense Center.for a unique alphanumeric ID.9. IMPORTANT! If you registered a Master Defense Center and Defense Center using IPv4 and want to convert them to IPv6. Click Add. Version 4. Registration Key. Valid combinations include: • • • Management Host or Host and Registration Key used on both appliances Registration Key and Unique NAT ID used on the Defense Center with Host. After communications between the two appliances are established.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 15. you must make sure that the network settings are configured correctly on both appliances.one-time use registration key Unique NAT ID (optional) . It can take up to two minutes for the Defense Center to establish communication with the Master Defense Center. For more information see Configuring Network Settings on page 377. and Unique NAT ID used on the Defense Center with Registration Key and Unique NAT ID used on the Master Defense Center IMPORTANT! The Management Host or Host field (hostname or IP address) must be used on at least one of the appliance. Adding a Defense Center Requires: MDC + DC Before you add a Defense Center to a Master Defense Center. See Working in NAT Environments on page 112 for more information. Registration Key .

WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 To add a Defense Center. type the one-time use registration key that you want to use to set up a communications channel between the Master Defense Center and the Defense Center. Click Remote Management. Using a user account with Admin access. After the Defense Center confirms communication with the Master Defense Center. In the Registration Key field. type the IP address or the host name of the Master Defense Center that you want to use to manage the Defense Center. In that case. Select Operations > System Settings. use both the Registration Key and the Unique NAT ID fields. TIP! You can leave the Management Host field empty if the management host does not have a routable address. The Add Remote Management page appears. Click Add Manager. Version 4. 5. The Information page appears. The Remote Management page appears. In the Management Host field. the Pending Registration status appears. in the Unique NAT ID field. Click Save. 8. Optionally. 4. 7. log into the web interface of the Defense Center you want to add. 6.9. type a unique alphanumeric NAT ID that you want to use to identify the Defense Center. To add a Defense Center to a Master Defense Center: Access: Admin 1. 3.1 Sourcefire 3D System Administrator Guide 169 . you need to predetermine which events on the Defense Center you want to forward to the Master Defense Center. 2.

13. 10. Note that if you select intrusion events. type the same one-time use registration key that you used in step 6.1 Sourcefire 3D System Administrator Guide 170 . Type the IP address or the hostname of the Defense Center you want to add in the Host field. identify the types of events you want to forward from the Defense Center to the Master Defense Center.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 9. The New Defense Center page appears. In the Registration Key field. Under Filter Configuration. you can send events or events and packet data. and select Operations > Appliances. If you used a NAT ID in step 7. Click New Defense Center. IMPORTANT! You must select at least one type of flag if you want to send intrusion events. 12. If you chose to send compliance events to the Master Defense Center. Log into the Master Defense Center’s web interface using a user account with Admin access. 14. See Editing the Event Filter Configuration on page 176 for more information. type the same value in the Unique NAT ID (optional) field. white list events are also sent. Version 4. You can also filter which intrusion events are forwarded based on their impact flag. The Defense Centers page appears. 11.9. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses.

4. Select Operations > System Settings. 5. you must also reset management before adding the Defense Center to the another Master Defense Center. you must first delete the manager on the Defense Center and delete the Defense Center on the Master Defense Center. To keep the Defense Center from trying to reconnect to the Master Defense Center. Resetting Management of a Defense Center Requires: MDC + DC If communications fail between the Master Defense Center and one of your Defense Centers. you should also delete the manager on the Defense Center. you must re-add it to the Master Defense Center. you can delete it from the Master Defense Center. Log into the Master Defense Center web interface. The Information page appears. 6. Log into the web interface of the Defense Center you want to delete. Version 4. Communication between the Master Defense Center and the Defense Center is discontinued and the Defense Center is deleted from the Defense Centers page. Click Delete next to the Master Defense Center that was managing the Defense Center.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 15.9. The manager is removed. Click Delete next to the Defense Center you want to delete. To manage the Defense Center again at a later date. You can view the status on the Defense Centers page (Operations > Appliances). It can take up to two minutes for the Defense Center to establish communication with the Master Defense Center. The Defense Center is added to the Master Defense Center. Click Remote Management. Deleting a Defense Center Requires: MDC + DC If you no longer want to manage a Defense Center. you can reset management of the Defense Center. and select Operations > Appliances. Deleting a Defense Center severs all communication between the Defense Center and the Master Defense Center. 3. You can then re-add the Master Defense Center on the Defense Center and then add the Defense Center to a Master Defense Center. To do this. Click Add.1 Sourcefire 3D System Administrator Guide 171 . To delete a Defense Center from the Master Defense Center: Access: Admin 1. If you want to manage a Defense Center with a different Master Defense Center. 2. The Defense Centers page appears. The Remote Management page appears.

use both the Registration Key and the Unique NAT ID fields Version 4. 2. The Remote Management page appears. Log into the web interface of the Defense Center where you want to reset communications and click Add Manager. In that case. The Defense Centers page appears.9. Log into the web interface of the Master Defense Center where you want to reset communications. Click Delete next to the Defense Center you want to delete.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 To reset management from a Master Defense Center: Access: Admin 1. 2. 2. The manager is removed. 3. To re-add the Defense Center to the Master Defense Center: Access: Admin 1. Click Remote Management. Select Operations > Appliances. In the Management Host field. Communication between the Defense Center and the Master Defense Center is discontinued and the Defense Center is deleted from the Defense Centers page. Click Delete next to the Master Defense Center where you want to reset management. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses.1 Sourcefire 3D System Administrator Guide 172 . 3. type the IP address or the host name of the Master Defense Center that you want to use to manage the Defense Center. Select Operations > System Settings. The Information page appears. 4. To delete management on the Defense Center: Access: Admin 1. Log into the web interface of the Defense Center where you want to reset communications. TIP! You can leave the Management Host field empty if the management host does not have a routable address. The Remote Management page appears.

To add the Defense Center to a group. 6. 12. type the same one-time use registration key that you used in step 3. 8. The following sections describe the features on the Appliances page. If you used an alphanumeric NAT ID in step 4. 4. Using the Appliances Page Requires: MDC + DC The Appliances page (Operations > Appliances) provides you with a range of information and options that you can use to manage your Defense Centers. In the Registration Key field. in the Unique NAT ID field. See Working in NAT Environments on page 112 for more information. After the Defense Center confirms communication with the Master Defense Center. type a unique alphanumeric NAT ID that you want to use to identify the Defense Center. Click New Defense Center.1 Sourcefire 3D System Administrator Guide 173 . The Defense Centers page appears. Click Save. For more information about Defense Center groups. 9.Using the Master Defense Center Using the Appliances Page Chapter 5 3. Version 4. In the Registration Key field. 5. the Pending Registration status appears. The Add New Defense Center page appears. 11. 7. The Defense Center is added to the Master Defense Center. You can view the Defense Center’s status on the Defense Centers page (Operations > Appliances).9. type the same value in the Unique NAT ID (optional) field. It can take up to two minutes for the Master Defense Center to verify communication with the Defense Center. Click Add. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. Type the IP address or the hostname of the Defense Center you want to add in the Host field. type the one-time use registration key that you want to use to set up a communications channel between the Defense Center and the Master Defense Center. Log into the Master Defense Center’s web interface and select Operations > Appliances. select the group from the Add to Group list. 10. see Managing Appliance Groups on page 179. Optionally.

See Editing Settings for a Managed Defense Center on page 175 for more information. the remote management configuration. Status Icons The status icons indicate the state of a Defense Center. and the high availability settings. • • Manager. the Defense Center 1000 and the Defense Center 3000. If your network is constrained in bandwidth. The system settings include the filter configuration for the Defense Center. 3D Sensor 2100. Model. and so on. An HA pair is listed as a group named with the name of the active Defense Center. that is. which sorts by Appliance group (see Managing Appliance Groups on page 179) TIP! High availability Defense Center pairs are automatically listed as an appliance group. minutes. Click the Delete icon next to a Defense Center if you no longer want to manage the Defense Center with the Master Defense Center. The red exclamation point icon indicates that the Master Defense Center has not received communications from the Defense Center in the last three minutes. You can sort by: • Group. and seconds) since the last contact. The green check mark icon indicates that the Master Defense Center and the Defense Center are communicating properly. the health blacklist settings. which sorts by the Defense Center then the 3D Sensor connected to it.9. Edit and Delete Icons Click the Edit icon next to a sensor if you want to change the Defense Center’s current system settings. it sends a two-byte heartbeat packet to establish contact and ensure that the communications channel is still running.1 Sourcefire 3D System Administrator Guide 174 .Using the Master Defense Center Using the Appliances Page Chapter 5 Sort-by Drop-Down List Use this drop-down list to sort the Appliances page according to your needs. If you hover your cursor over the icon. Version 4. If the Master Defense Center has not received a communication from a Defense Center within the last two minutes. you can contact technical support to change the default time interval. which sorts by appliance model number. See Deleting a Defense Center on page 171 for more information. a pop-up window indicates the amount of time (in hours.

See the following sections for more information. not the hostname. The Information page for a managed Defense Center includes the fields described in the Defense Center Information table.9. The IP address of the managed Defense Center. Note that this is the name of the Defense Center in the Master Defense Center web interface. The Vulnerability Database version on the managed Defense Center. The version of the operating system currently running on the managed Defense Center. you can use the Master Defense Center web interface to view and edit the configuration of the Defense Center. The version of the software currently installed on the managed Defense Center.Using the Master Defense Center Editing Settings for a Managed Defense Center Chapter 5 Editing Settings for a Managed Defense Center Requires: MDC + DC After you configure management of a Defense Center by a Master Defense Center. • • • • • Viewing the Defense Center Information Page on page 175 Editing the Event Filter Configuration on page 176 Editing or Disabling Remote Management Communications on page 178 Managing the Health Blacklist on page 178 Managing High Availability Defense Centers on page 178 Viewing the Defense Center Information Page Requires: MDC + DC To access the system settings information page for a managed Defense Center. then click Edit next to the Defense Center. Product Model Software Version Operating System Operating System Version VDB Version IP Address Version 4. Defense Center Information Field Name Description The assigned name for the Defense Center. The model name for the managed Defense Center.1 Sourcefire 3D System Administrator Guide 175 . The operating system currently running on the managed Defense Center. select Appliances from the Operations menu.

If you want to send intrusion events (with or without packet data). 2. This number can be important for troubleshooting. Change the Defense Center’s attributes as needed. To edit a managed Defense Center’s settings: Access: Admin 1.9.1 Sourcefire 3D System Administrator Guide 176 . and seconds) since the Defense Center communicated with the Master Defense Center. Click Save. and compliance events. Model Number Current Group The model number for the Defense Center. you can also specify which intrusion events are sent based on their impact flag. minutes. if any. You can edit the following: • • the name of the Defense Center the group in which the Defense Center resides WARNING! The name must be made up of a combination of alphanumeric characters and should not be made up of numeric characters only. a pop-up message indicates how long it has been (in hours. If you hover your cursor over the icon. Your options are to send intrusion events. Editing the Event Filter Configuration Requires: MDC The settings on the Filter Configuration page control which events are sent from the Defense Center to the Master Defense Center that manages it. The updated Defense Center attributes are saved. You can click Refresh to update the Status icon and its accompanying pop-up message.Using the Master Defense Center Editing Settings for a Managed Defense Center Chapter 5 Defense Center Information (Continued) Field Status Description An icon showing the current status of the managed Defense Center. See the Impact Flags table in the Analyst Guide for an explanation of what each impact Version 4. The group that the Defense Center belongs to. intrusion events and related packet data.

In the Intrusion Events area. The Flags options are: • • • • • • • All Black (or Drop) Red (or Vulnerable) Orange (or Potentially Vulnerable) Yellow (or Currently Not Vulnerable) Blue (or Unknown Target) Gray (or Unknown) TIP! If you select All. TIP! If you set up the 3D Sensor so it does not send packet data to the intermediate Defense Center. 4. The options are Do Not Send. then you must specify which events you want to send based on their impact flag. 2. then all the options are immediately selected.Using the Master Defense Center Editing Settings for a Managed Defense Center Chapter 5 flag means. If you indicated that you want to send intrusion events. use the drop-down list to indicate whether you want to forward intrusion events to the Master Defense Center. To modify the event filter configuration: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 177 . and Events and Packet Data.9. The Appliances page appears. select Operations > Appliances. 3. If you want to send intrusion events to the Master Defense Center. Next to the Defense Center whose filter configuration you want to change. The Filter Configuration page appears. then packet data is not forwarded to the Master Defense Center. Note that you must deploy both RNA and IPS as part of your Sourcefire 3D System deployment to generate meaningful impact flags. then you must select at least one impact flag option. Version 4. On the Master Defense Center’s web interface. click Edit. Events Only.

Editing or Disabling Remote Management Communications Requires: MDC + DC You can manage communications between a managed Defense Center and its Master Defense Center using the Master Defense Center’s web interface. In the Compliance Events area.9. For example.1 Sourcefire 3D System Administrator Guide 178 .0. 6. see Editing the Management Virtual Network on page 385. See the following sections for more information: • • Using Redundant Defense Centers on page 112 Setting Up High Availability on page 150 Version 4.0. To enable communications between the two appliances again.0/24 to indicate that the Management Virtual Network is disabled on a Master Defense Center. if a Defense Center is no longer responding. use the drop-down list to indicate whether you want to forward compliance events to the Master Defense Center. Click Save. monitor. Your settings are saved and the Defense Center begins forwarding the events you specified to the Master Defense Center that manages it. You may want to do this to prevent events from the module from changing the status for the appliance to warning or critical. you can temporarily disable communications between the Defense Center and its Master Defense Center. click Enable. The field is filled with 0. Managing the Health Blacklist Requires: MDC + DC You can blacklist individual health policy modules on Defense Centers. Communications between the two appliances are interrupted. The options are Do Not Send and Send. For information on using the blacklisting function. You cannot edit the Management Virtual Network field of a Master Defense Center. Managing High Availability Defense Centers Requires: MDC + DC You can configure. To disable communications between the Defense Center and the Master Defense Center: Access: Admin Click Disable next to the name of the Defense Center. pause and restart Defense Center High Availability from a Defense Center.Using the Master Defense Center Editing Settings for a Managed Defense Center Chapter 5 5. IMPORTANT! Master Defense Centers do not currently use a Management Virtual Network. see Using the Health Monitor Blacklist on page 534. disable. For more information about editing the Management Virtual Network.

Using the Master Defense Center Managing Appliance Groups Chapter 5 • • • • Monitoring the High Availability Status on page 152 Disabling High Availability and Unregistering Sensors on page 153 Pausing Communication between Paired Defense Centers on page 154 Restarting Communication between Paired Defense Centers on page 154 If High Availability is configured. 2. Click Activate to activate the redundant Defense Center. you can activate Defense Center High Availability from a Master Defense Center. 3. Managing Appliance Groups Requires: MDC The Master Defense Center allows you to group appliances so that you can easily search for events based on whether they were forwarded by one of a specific group of appliances. The redundant Defense Center is activated. TIP! When using Intrusion Agents registered to Defense Centers configured for high availability and managed by a Master Defense Center.9.1 Sourcefire 3D System Administrator Guide 179 . The high availability page appears with the paired Defense Centers. Select Operations > Appliances. The Appliances page appears. The System Settings page for that Defense Center appears. TIP! High availability Defense Center pairs are automatically listed as an appliance group. To activate a redundant Defense Center: Access: Admin 1. 4. Version 4. Click High Availability. An HA pair is listed as a group with the name of the active Defense Center. Click Edit next to the appropriate Defense Center. TIP! A light bulb icon shows which of the high availability paired Defense Centers is currently active. register all Intrusion Agents to the primary Defense Center.

7. 6. In the Group Name field. On the Master Defense Center. The group is added. The Appliances page appears.1 Sourcefire 3D System Administrator Guide 180 . 5. TIP! You must remove an appliance from its current group before you can add it to a new group. 3. return to the Appliances page (Operations > Appliances) and click Edit next to the name of the group. The appliances are added to the group and the Appliances page appears again. 4.9. Editing Appliance Groups Requires: MDC You can change the set of appliances that reside in any appliance group. The Appliance Group Edit page appears. Version 4. Deleting Appliance Groups on page 181 explains how to delete a Defense Center group. Click Save. select Operations > Appliances. To add appliances to the group.Using the Master Defense Center Managing Appliance Groups Chapter 5 See the following sections for more information: • • • Creating Appliance Groups on page 180 explains how to create a Defense Center group on the Master Defense Center. Click Create New Appliance Group. Editing Appliance Groups on page 180 explains how to modify the list of Defense Centers in a Defense Center group. Click Save. Creating Appliance Groups Requires: MDC Grouping managed appliances allows you to use the group name as a search criterion when you search for specific compliance or intrusion events. type the name of the group you want to create. 2. Moving an appliance to a new group does not change any of its policies or configurations. Select the IP addresses or hostnames of the appliances you want to add from the Available Appliances list and click the arrow to move them into the group. The Create Appliance Group page appears. To create an appliance group and add appliances to it: Access: Admin 1.

Click Edit next to the Appliance group you want to edit. • • • • Listing Master Defense Center Information on page 182 Viewing a Master Defense Center License on page 182 Configuring Network Settings on page 377 Shutting Down and Restarting the System on page 182 Version 4. 2. Click Delete next to the group you want to delete. • • To add an appliance to the group. Click Save.9.1 Sourcefire 3D System Administrator Guide 181 . Deleting Appliance Groups Requires: MDC If you delete a group that contains appliances. the Master Defense Center system settings are the same as those of a Defense Center. select it from the Available Appliances list and click the arrow pointing toward the group you are editing. select it from the list in the group you are editing and click the arrow pointing to the Available Appliances list. 3. The Appliances page appears. Editing Master Defense Center System Settings Requires: MDC With a few exceptions. select Operations > Appliances. To remove an appliance from a group. They are not deleted from the Master Defense Center. the appliances are moved to Ungrouped on the Appliances page. On the Master Defense Center. See the following sections for information on each of the listed system settings: IMPORTANT! NetFlow-enabled devices cannot currently be added to a Master Defense Center. 4. 2. The Appliance Group Edit page appears. The Appliances page appears. To delete an appliance group: Access: Admin 1. Select Operations > Appliances. Select the appliance you want to move and click the arrow to add or remove it from the group. The appliances group is removed from the Master Defense Center.Using the Master Defense Center Editing Master Defense Center System Settings Chapter 5 To edit an appliance group: Access: Admin 1.

1 Sourcefire 3D System Administrator Guide 182 . To view information about the Master Defense Center license: Access: Admin 1. Change the name of the Master Defense Center attributes as needed.Using the Master Defense Center Editing Master Defense Center System Settings Chapter 5 • • Setting System Time on page 183 Blacklisting Health Policies on page 184 Listing Master Defense Center Information Requires: MDC For details on information listed under the Master Defense Center system settings. To edit a Master Defense Center’s settings: Access: Admin 1. see Configuring Network Settings on page 377.9. 2. Click License. Click Save. a Master Defense Center cannot manage the licenses of Defense Centers or 3D Sensors. You can: • • • shut down the appliance reboot the appliance restart the appliance Version 4. Configuring Network Settings Requires: MDC The network settings are identical to those of the Defense Center. The updated Master Defense Center attributes are saved. WARNING! The name must be made up of a combination of alphanumeric characters and should not be made up of numeric characters only. For information on configuring the Master Defense Center network settings. Select Operations > System Settings. see Defense Center Information on page 175. The Information page appears. Viewing a Master Defense Center License Requires: MDC Unlike a Defense Center. The License page appears. 2. Shutting Down and Restarting the System Requires: MDC You have several options for controlling the processes on your Master Defense Center.

0/24 to disable the Management Virtual Network. their real IP network is used to serve time. You cannot edit the Management Virtual Network field if the Defense Center is in the Master Defense Center operational mode. If you want to reboot the system. Setting System Time Requires: MDC The system time is set and synchronized in accordance with the system policy. On the Time Synchronization page you can choose to serve time from the Master Defense Center by selecting Enabled in the Serve Time via NTP field.Using the Master Defense Center Editing Master Defense Center System Settings Chapter 5 To shut down or restart your appliance: Access: Admin 1. IMPORTANT! Master Defense Centers do not currently use a Management Virtual Network.0.1 Sourcefire 3D System Administrator Guide 183 . The field is filled with the address range 0. Specify the command you want to perform: • • • If you want to shut down the Master Defense Center. The Information page appears.0. click Run Command next to Shutdown Master Defense Center. 2. If you want to restart the Defense Center. click Run Command next to Restart Master Defense Center Console. Select Operations > System Settings.9. Configuring Remote Management Networking Requires: MDC A Master Defense Center’s Management Virtual Network is disabled. click Run Command next to Reboot Master Defense Center. TIP! Because Master Defense Centers do not currently use Management Virtual Networks. Note that restarting the Defense Center may cause deleted hosts to reappear. Version 4. Click Process. 3. The Appliance Process page appears.

select Via NTP Server from and. if DNS is enabled. Version 4. see Synchronizing Time on page 354. For more information about setting system time. To receive time through NTP from a different server.9. see Blacklisting a Health Policy Module on page 537.1 Sourcefire 3D System Administrator Guide 184 .Using the Master Defense Center Editing Master Defense Center System Settings Chapter 5 To specify how the Master Defense Center clock is set: Access: Admin You have two options: • • To set the time manually. type the IP address of the NTP server or. Blacklisting Health Policies Requires: MDC You can blacklist health policy modules when required. you should configure your DHCP server to set the same NTP server. the DHCP-provided NTP server will be used instead. To avoid this situation. select Manually in the System Settings. type the fully qualified host and domain name. WARNING! If the appliance is rebooted and your DHCP server sets an NTP server record different than the one you specify here. in the text box. The Master Defense Center supports the following health policy modules: • • • • • • • • Appliance Heartbeat CPU Usage Data Correlator Process Defense Center Status Disk Usage eStreamer Process Event Stream Status Memory Usage For more information on blacklisting a health policy.

The number of detection engines per sensor is limited by the number of detection resources that are available. See the Detection Resources by Model table on page 190 for more information. you cannot use RUA or RNA on 3D9800 sensors.Using Detection Engines and Interface Sets Chapter 6 Administrator Guide To give you increased flexibility in your deployment choices. However. you can combine the data from those sensors with RUA or RNA on a Defense Center. You can think of a detection engine as a collection of one or more sensing interfaces (called an interface set) on a 3D Sensor plus a portion of the sensor’s computing resources (called a detection resource). one for RNA. Most 3D Sensor models have at least three detection resources available and can support at least three detection engines: one for IPS. In addition.1 Sourcefire 3D System Administrator Guide 185 . and the third for RUA. 3D Sensors support three types of detection engines: • • • IPS RNA RUA TIP! You cannot use the RUA feature on Crossbeam-based software sensors.9. the Sourcefire 3D System provides a feature called the detection engine. Version 4.

Using Detection Engine Groups on page 197 explains how to create and use detection engine groups.9. This section also describes how default detection engines are configured. Using Interface Set Groups on page 223 describes how to create and use interface sets groups. including some of the limitations based on the sensor model. Version 4.Using Detection Engines and Interface Sets Understanding Detection Engines Chapter 6 The following sections describe the detection engines and interface set features and how you can use them in your Sourcefire 3D System deployment: • Understanding Detection Engines on page 186 explains detection engines in more detail. sensor. Using Clustered 3D Sensors on page 227 explains how to use detection engines and interface sets in a clustered 3D9900 sensor pairing. The figure below shows the Defense Center version of the page. or interface set type.1 Sourcefire 3D System Administrator Guide 186 . The Available Detection Engines page appears. edit. To list the available detection engines: Access: Admin Select Operations > Configuration > Detection Engines > Detection Engines. Managing Detection Engines on page 193 explains how to create. Using Interface Sets on page 207 describes how to create interface sets and how to use them with detection engines. and delete detection engines. • • • • • • • Understanding Detection Engines Requires: DC or 3D Sensor A detection engine is the mechanism on a 3D Sensor that is responsible for analyzing the traffic on the network segment where the sensor is connected. detection engine type. Using Variables within Detection Engines on page 199 explains how to use detection engine-specific variable values to tailor your detection capabilities to more closely match your infrastructure. policy. Inline Fail Open Interface Set Commands on page 225 explains how to force an interface set in and out of bypass mode when using an inline fiber fail open interface set. You can sort the available detection engines by group.

9. (The exception is on 3D9900s. Use an inline with fail open interface set if you deployed the sensor inline on your network and the sensing interfaces do support automatic fail-open capabilities. and Interface Set Depending on which components are licensed on the sensor. A detection engine has two main components: • • an interface set. RNA. see Using PEP to Manage Traffic in the Analyst Guide. Note that you must use paired fail-open interfaces on the sensor’s network interface cards for an inline with fail open interface set. Set Type An interface set refers to a grouping of one or more sensing interfaces on a sensor. For more information on the PEP feature. and RUA. 3D Sensors can support three types of detection engines: IPS. Interface Set Types Type Passive Inline Description Use a passive interface set if you deployed the sensor out of band from the flow of network traffic. where pairs are pre-determined). but the interface options available to you depend on the type of sensor and the capabilities of its sensing interfaces. The three interface types are described in the Interface Set Types table. Note that you can use any two of the non-fail-open interfaces on the sensor’s network interface cards as part of an inline interface set. Inline with Fail Open Version 4.Using Detection Engines and Interface Sets Understanding Detection Engines Chapter 6 Detection Engine Type. which is a portion of the sensor’s computing resources For information about detection engines and detection resources.1 Sourcefire 3D System Administrator Guide 187 . The Sourcefire 3D System supports three types of interface sets. although a sensing interface can belong to only one interface set at a time. see Understanding Detection Resources and 3D Sensor Models on page 189 PEP Policy Only 3D9900 sensors provide the PEP feature. Use an inline interface set if you deployed the sensor inline on your network and the sensing interfaces do not support automatic fail-open capabilities. which can include one or more sensing interfaces a detection resource. Resources.

• You can click the name of an IPS policy to see details about the running policy.9 you have the advantage of the following listed features. you must either configure an IPS detection engine that uses that interface set.1 Sourcefire 3D System Administrator Guide 188 . For more information see Viewing an Intrusion Policy Report in the Analyst Guide. the RNA or RUA detection engine monitoring that interface set will not see any traffic until the IPS detection engine restarts. or configure the interface set in tap mode. as well as apply an intrusion policy to that detection engine. See Using Interface Sets on page 207 for more information about creating and editing interface sets. Policy 3D Sensors have different capabilities and limitations depending on whether you licensed IPS. if you plan to use RNA to monitor either an inline or inline with fail open interface set. Otherwise. Version 4. RUA. the RNA detection engine monitoring that interface set will not see any traffic. You can determine what the name and state of IPS and RNA policies from the following information in the policy column: • If you change an IPS and RNA policy and have not applied it to the detection engine since the change. or RNA. then the icon has an exclamation point and the name is italicized. IMPORTANT! On a 3D3800 or 3D5800 sensor. If you are monitoring the same inline interface set with both IPS and RNA or RUA.Using Detection Engines and Interface Sets Understanding Detection Engines Chapter 6 You can use RNA or RUA to monitor the traffic that passes through any of the three types of interface sets.9. TIP! After you upgrade your sensor to version 4. Neither RNA nor RUA are supported on the 3D9800 sensor. and the IPS detection engine fails for any reason.

if you plan to use the 3D3500 sensor in inline mode. click the delete icon ( ) next to the intrusion policy name. the Available Detection Engines page does not indicate that the filtered or base intrusion policy is deleted. If you want to remove the currently applied filter from the IPS policy. or delete variables associated with a detection engine’s IPS or RNA policy.Using Detection Engines and Interface Sets Understanding Detection Engines Chapter 6 • If there is a network or VLAN filter applied to the IPS policy. which allows you to use more computing resources when network traffic is high. then OK to confirm. click Edit or Delete next to its sensor name.1 Sourcefire 3D System Administrator Guide 189 . use one detection resource per application per core on your appliance. click Reapply All. reset. you can click More or the down icon ( ) and view the type (Net for network or VLAN for virtual LAN) filter. which takes approximately 30 seconds. For example. add. • • For more information see Understanding Detection Resources and 3D Sensor Models on page 189 When you configure a new sensor. See Understanding Default Detection Engines for more information. • Sensor The sensor column provides the name of the sensor where the policy is applied. If you want to list. edit. Select Monitor > Task Status to track the progress of the deletion process. Different sensor models have different Version 4. it has a predefined detection engine that you can choose to modify to meet your needs. It also provides the following capabilities: • If you want to edit or delete a detection engine. click the delete icon ( ) next to the filter name. If you want to reapply all policies for the detection engine. See Editing a Detection Engine on page 194 and Deleting a Detection Engine on page 197 for more information. you could assign two detection resources to your detection engine to allow processing of more events per second. See Using Variables within Detection Engines on page 199 for more information. If you want to remove the currently applied IPS policy from the detection engine. IMPORTANT! Initially. click Variables.9. As a best practice. Understanding Detection Resources and 3D Sensor Models Requires: DC or 3D Sensor 3D Sensors with IPS can use multiple detection resources per detection engine. The delete icon only appears next to the base policy when there are no network or VLAN filters applied. If you hover above the name you can view the network or VLAN range of the filter.

It also indicates the maximum number of detection resources you can assign a single detection engine. • The Optimal column indicates the per-sensor total number of detection resources you should use if you want to maximize the performance of the sensor. can be any type No restrictions No restrictions No restrictions No restrictions No restrictions No restrictions No restrictions No restrictions No restrictions No restrictions Version 4.Using Detection Engines and Interface Sets Understanding Detection Engines Chapter 6 numbers of detection resources available as shown in the Detection Resources by Model table. The Maximum column indicates the total number of detection resources available on the sensor. RNA and RUA.1 Sourcefire 3D System Administrator Guide 190 . The Combination Restrictions column indicates the permitted combinations of detection resources that you can allocate to detection engines on the same sensor. 3D Sensors can run combinations of IPS. can be any type Maximum of two. • • Detection Resources by Model Model 3D500 3D1000 3D2000 3D2100 3D2500 3D3000 3D3500 3D3800 3D4500 3D5800 3D6500 3D9800 3D9900 Optimal per Sensor 1 1 1 2 2 2 2 2 4 6 8 12 7 Maximum per Sensor 2 2 2 3 4 4 6 2 8 6 12 12 12 Combination Restrictions Maximum of one IPS and either one RNA or one RUA Maximum of two.9.

Understanding Default Detection Engines Requires: DC or 3D Sensor When you install a new 3D Sensor. and detection resources available on Crossbeam System hardware.9. you can use initial interface sets and default detection engines to quickly begin evaluating network traffic. you can reduce latency by distributing your network traffic across all available interfaces on the sensor. After initial installation can modify interface sets and detection engines.Using Detection Engines and Interface Sets Understanding Detection Engines Chapter 6 Detection Resources by Model (Continued) Model Virtual 3D Sensor Crossbeambased software sensors Optimal per Sensor 3 Maximum per Sensor 3 Combination Restrictions No restrictions Refer to Crossbeam-based Software Sensor Considerations on page 191 General Recommendations with Two or More Detection Resources For improved 3D Sensor performance on sensors with optimal detection resources of two or greater. Consider how your network is configured and how you want to deploy the Sourcefire 3D System within it. you have several deployment options for 3D Sensor Software. then distribute the detection engines and detection resources across all operative interfaces on the sensor. the maximum number of detection engines that you can create is equal to the number of available detection resources.1 Sourcefire 3D System Administrator Guide 191 . Crossbeam-based Software Sensor Considerations Depending upon the capabilities of your X-Series and the products you are licensed to use. The number of detection resource depends on the Crossbeam System hardware. Version 4. As with other 3D Sensors. Refer to the Sourcefire 3D Sensor Software for X-Series Installation Guide for information on deployment scenarios. current Crossbeam System hardware and software support.

the default that builds paired fail-open interface sets on all 3D Sensor interfaces. Passive that builds a single passive interface set for all 3D Sensor interfaces. see Editing a Detection Engine on page 194.9.1 Sourcefire 3D System Administrator Guide 192 . Choose from these initial interface sets based on how you deployed the sensor. If you want to change either the number of detection resources or the interfaces assigned to the default detection engine. With this configuration. IMPORTANT! For the 3D3000 on the IBM xSeries 346 appliance. Second On-Board Interface Some Sourcefire sensors have a second on-board interface. the detection engine may not provide optimum performance. If your appliance has one of these extra interfaces. the second on-board interface cannot support the same high-performance standards as the interfaces on the network interface cards. for example. However. Depending on the 3D Sensor. that is automatically included in the default detection engine. Sourcefire recommends that you remove the second on-board interface from the detection engine for improved performance. a 3D2000 Sensor uses eth1 and eth2 as one inline fail-open interface set and it uses eth3 and eth4 as another inline fail-open interface set. on some of the older models. Select Passive Mode if the sensing interfaces are not cabled inline. less the management interface. typically you pair adjacent interfaces. and you have deployed it in a high-bandwidth environment where the traffic load is likely to reach the design limits of the appliance. usually near the management interface. note that the default detection engine does not include the second on-board interface. Version 4. Select Inline with Fail-Open Mode if you cabled the sensing interfaces inline on your network as an IPS.Using Detection Engines and Interface Sets Understanding Detection Engines Chapter 6 Initial Interface Sets The initial interface sets for 3D Sensors are: • • Inline with Fail-Open. less the management interface. you can connect any of the non-management interfaces to your network and apply the appropriate policy to the detection engine and begin analyzing your network. If you modify the default detection engine to include it. Default Detection Engines Default detection engines are configured with the optimal (rather than maximum) number of detection resources as described in the Detection Resources by Model table on page 190.

3. • • • Creating a Detection Engine on page 193 Editing a Detection Engine on page 194 Deleting a Detection Engine on page 197 Creating a Detection Engine Requires: DC or 3D Sensor You can create a detection engine if you have an available interface set and at least one available detection resource. edit. enter a name and description for the new detection engine. 2. punctuation. and delete detection engines.9. The following sections explain how to create. In the Name and Description fields. You can use alphanumeric characters. To create a detection engine: Access: Admin 1. Click Create Detection Engine. The Detection Engines page appears. Select Operations > Configuration > Detection Engines > Detection Engines. You can use interface sets that include multiple inline interface pairs.Using Detection Engines and Interface Sets Managing Detection Engines Chapter 6 Managing Detection Engines Requires: DC/MDC or 3D Sensor See Understanding Detection Engines on page 186 and Using Interface Sets on page 207 for more information about the capabilities of detection engines and the interface sets they depend on. The figure below shows the Defense Center version of the page. Version 4.1 Sourcefire 3D System Administrator Guide 193 . and spaces. The Create Detection Engine page appears. when they are available on your 3D Sensor.

See the Detection Resources by Model table on page 190 for more information. IMPORTANT! For most 3D Sensors with inline interface sets. The following sections describe some of the cases where a detection engines is affected by changes to the detection engines and interface sets: Version 4. Select the interface set that you want to assign to this detection engine. The detection engine is created. Click Save. or RUA. 8. Optionally. 7. Although some packets are transmitted without inspection during this time. 9. Select the type of detection engine that you want to create from the Type drop-down list. Optionally. The second detection resource is available only if you want to create a second detection engine for RNA or RUA. Editing a Detection Engine Requires: DC or 3D Sensor In some circumstances. you can select Inspect Traffic During Policy Apply. a software bridge is automatically set up to transport packets when the sensor restarts. See Using Interface Sets on page 207 for information about creating and modifying interface sets. TIP! This option may degrade performance when you apply a policy and may result in longer policy-apply periods.Using Detection Engines and Interface Sets Managing Detection Engines Chapter 6 4. See Using Detection Engine Groups on page 197 for information on creating and modifying detection engine groups. 6. if this option is employed. if you are creating an IPS detection engine and if you are using a 3D Sensor other than a 3D500.9. you can only use one of the two detection resources for IPS. no packets are lost. Select the number of detection resources for this detection engine. which can cause a short pause in processing. the detection engine does not restart and interrupt traffic inspection when the policy is applied. 3D1000. However. or 3D3800. RNA. editing an interface set or detection engine can cause the detection engines on the sensor to restart. 5. IPS. add the detection engine to an existing detection engine group. IMPORTANT! On the 3D500.1 Sourcefire 3D System Administrator Guide 194 .

all the detection engines on the sensor are restarted. If you change the number of detection resources allocated to a detection engine. • • • Version 4. all the detection engines on the sensor are restarted because the total number of allocated resources has changed. only that detection engine is started (although other CPUs may be restarted to rebalance the processing load). If you change an interface set’s transparent mode setting.9. • • • • If you create a detection engine. all detection engines assigned to that interface set are restarted. or the detection engine type. all the detection engines on the sensor are restarted. that detection engine is restarted. If you change the detection engine type for a detection engine. If you change a detection engine’s interface set. nothing is restarted. all detection engines on the sensor are restarted. If you change the number of detection resources. or the setting for tap mode or transparent mode for an interface set. When you create a detection engine.1 Sourcefire 3D System Administrator Guide 195 . If you create an interface set. • Other Sensors • • • • • • If you change which network interfaces are used by an interface set. IMPORTANT! If you have an 3Dx800 health policy applied to a 3D9800 sensor when you change the number of detection resources. If you change the name or description of an interface set or detection engine. If you create an interface set. the interface set type. nothing is restarted. it will generate hardware alarms.Using Detection Engines and Interface Sets Managing Detection Engines Chapter 6 3Dx800 Sensors • If you change the number of network interfaces. only that detection engine is restarted (although other CPUs may be restarted to rebalance the processing load). nothing is restarted. or interface set type. all detection engines on the sensor are restarted. all the detection engines using that interface set are restarted. A restart occurs only when you assign a detection engine to the interface set. all detection engines on the sensor are restarted. which interface set is used. Contact Sourcefire Support for information about how to clear those hardware alarms. nothing is restarted. If you change the name or description of an interface set or detection engine. If you delete a detection engine or interface set. If you delete a detection engine or interface set.

you must delete the detection engine and create a new one.Using Detection Engines and Interface Sets Managing Detection Engines Chapter 6 Make sure you plan these actions for times when they will have the least impact on your deployment. you may want to remove any affected VAPs from the load-balanced list until the associated detection engines restart.1 Sourcefire 3D System Administrator Guide 196 . description. If you need to change the detection engine type. To edit an existing detection engine: Access: Admin 1.9. 3. The Edit Detection Engine page appears. You cannot modify the detection engine type. then reinstate the VAPs. TIP! On your 3D Sensor Software for Crossbeam Systems X-Series. Version 4. You can modify the name. In the case of an IPS detection engine you can also select if traffic is inspected while a policy is being applied. or 3D3800 sensors. The Detection Engines page appears. see the Sourcefire 3D Sensor Software for X-Series Installation Guide. 2. 3D1000. Your changes are saved. TIP! The Inspect Traffic During Policy Apply option is not available on 3D500. Select Operations > Configuration > Detection Engines > Detection Engines. Click Edit next to the detection engine you want to modify. and number of detection resources for the detection engine. group. For more information. Click Save.

Click Delete next to the detection engine you want to delete.1 Sourcefire 3D System Administrator Guide 197 . Using Detection Engine Groups Requires: DC/MDC or 3D Sensor You can use detection engine groups to combine similar detection engines. The Detection Engines page appears. The detection engine is deleted.9. however. 3. see Modifying a Rule in the Analyst Guide. Select Operations > Configuration > Detection Engines > Detection Engines. Select Operations > Configuration > Detection Engines > Detection Engines. See the following sections for more information: • • • Creating Detection Engine Groups on page 197 Editing Detection Engine Groups on page 198 Deleting Detection Engine Groups on page 199 Creating Detection Engine Groups Requires: DC/MDC or 3D Sensor Access: Admin The following procedure explains how to create a detection engine group. To delete a detection engine: Access: Admin 1. For information on modifying compliance rules. At the prompt. The Detection Engines page appears.Using Detection Engines and Interface Sets Using Detection Engine Groups Chapter 6 Deleting a Detection Engine Requires: DC or 3D Sensor Use the following procedure to delete a detection engine. you should not delete a detection engine that is used as a constraint in one or more compliance rules. These groups make it easier to apply policies to detection engines that have similar purposes. you should first delete (or modify) the constraint in all rules in which it is used. a record of the detection engine is retained so that events generated by that detection engine are viewable. To create a detection engine group: 1. 2. Version 4. WARNING! Do not delete a detection engine that is in use. Also. confirm that you want to delete the detection engine.

on the Edit Detection Engine page. 4. 3. The Detection Engines page appears. Editing Detection Engine Groups Requires: DC/MDC or 3D Sensor The following procedure explains how to edit a detection engine group.9. The Detection Engine Group Edit page appears. Click Save to add the selected detection engines to the detection engine group. 3. Click Edit for the detection engine group. Type a name for the detection engine group in the Group Name field. The Available Detection Engines page appears. The Detection Engine page appears again. You must create a detection engine group before you can edit it. 2. The Create Detection Engine Group page appears. To edit a detection engine group: Access: Admin 1. Select Operations > Configuration > Detection Engines > Detection Engines.1 Sourcefire 3D System Administrator Guide 198 .Using Detection Engines and Interface Sets Using Detection Engine Groups Chapter 6 2. Version 4. You can also move detection engines out of the detection engine group. adding the detection engine to the group and clicking Update. 4. See Creating Detection Engine Groups on page 197. You can add detection engines to this group by clicking Edit next to a detection engine name and. Click Create Detection Engine Group. Select available detections engines and to move them to the detection engine group with the arrow buttons. Click Save.

The Detection Engines page appears. When you apply an intrusion policy to that detection engine. if you have created your detection engines so that one detection engine monitors one class of hosts (in this example. For example. which includes a mixed address space. hosts in your network’s DMZ in the range 10. any detection engines in the group are automatically ungrouped.10.0/16).0/24 In the detection engine named DE_ACCT: HOME_NET = 10. Using Variables within Detection Engines Requires: IPS or DC/MDC + IPS A system default variable sets a variable value on your Sourcefire 3D Sensor or Defense Center that IPS uses by default unless it is overridden by a policy-specific or detection engine-specific value for the same variable.0/24 If you later create another detection engine that monitors the rest of your network.10. which are specific to the policy in which they are created.0. Click Delete next to the name of the detection engine group.9.30. Select Operations > Configuration > Detection Engines > Detection Engines. see Creating New Policy-Specific Variables in the Analyst Guide.0/24) and another monitors a different class (for example.10. However. hosts in your accounting department in the address range 10. you can use the system default Version 4. 10.30. You can associate a system default variable with a specific detection engine and give the resulting detection engine-specific variable an explicit value for that detection engine. In the system default variable used in the intrusion policy: HOME_NET = 10. You can define HOME_NET in your system default variable to encompass your internal address range (for example. the intrusion rules in an intrusion policy take advantage of certain system default variables such as HOME_NET and EXTERNAL_NET to look for exploits that originate outside your network and are targeted against hosts within your network. For information on policy-specific variables.10. 2.90. IPS can use the value of the detection engine-specific variable in rules you enable in your policy to monitor network traffic and generate events. The detection engine group is deleted.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 Deleting Detection Engine Groups Requires: DC/MDC or 3D Sensor When you delete a detection engine group.0/16 In the detection engine named DE_DMZ: HOME_NET = 10. you can use detection engine-specific variable values to tailor your detection capabilities to more closely match your infrastructure.0. To delete a detection engine group: Access: Admin 1.0/24).10.90. they are not deleted.1 Sourcefire 3D System Administrator Guide 199 .10.

For an explanation see Using Variables within Detection Engines on page 199. Version 4. see Creating New Variables in the Analyst Guide. You can create detection engine-specific variables and set detection engine-specific values for system default variables within an intrusion policy or from the detection engine Variable List page. IMPORTANT! You cannot use variables with RNA detection engines. see the following sections: • • • • • Assigning Values to System Default Variables in Detection Engines on page 200 Creating New Variables for Detection Engines on page 202 Deleting and Resetting Variables on page 203 Configuring Custom Variables in Detection Engines on page 204 Using Portscan-Only Detection Engines on page 205 Assigning Values to System Default Variables in Detection Engines Requires: IPS or DC/MDC + IPS You can assign detection engine-specific values to system default variables. Optionally. You can view the corresponding new system default variable in the list of system default variables within each policy. which means that the value specified in the policy will be used when you apply the policy.1 Sourcefire 3D System Administrator Guide 200 . See Creating New Variables in the Analyst Guide and Modifying Variables in the Analyst Guide for more information.9.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 variable value rather than creating another detection engine-specific value for HOME_NET. Variables use the same syntax and must follow the same guidelines regardless of whether you create or define them from within intrusion policies or from the detection engine Variable List page. Creating a detection engine-specific variable from the detection engine Variable List page also creates a corresponding system default variable with the value set to any. You can view the explicit detection engine-specific value you configured in the list of variables for the detection engine within each policy. or on the detection engine Variable List page for the detection engine. If you disable a variable defined on the Variable List page by resetting the variable. Configuration details in this section relate to the detection engine Variable List page. and on the Variable list page for all other detection engines where it is listed with the value set to Policy Defined. you can modify the variable in the intrusion policies and detection engines where it is added automatically to give it a specific definition. a detection engine-specific variable value takes precedence over a policy-specific or system default value for the same variable. the definition reverts to the definition in the intrusion policy the next time you apply the policy. For configuration details related to setting detection engine-specific variables within an intrusion policy. For more information. When they exist. You can also create new variables for use only within the context of the detection engine.

See Creating New Variables in the Analyst Guide for information about variable syntax. Enter a value for the variable and click Save. as described in Applying an Intrusion Policy in the Analyst Guide. Click Variables next to the detection engine where you want to define a variable value. The variable takes effect the next time you apply an intrusion policy to the detection engine. 2. Select Operations > Configuration > Detection Engines > Detection Engines.1 Sourcefire 3D System Administrator Guide 201 . The Variable Binding page appears. The Detection Engines page appears. The Variable List page appears. The Variable List page appears again and shows the new value for the variable. 4.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 To assign a detection engine-specific value to a system default variable: Access: Admin 1. The value for each of the variables defaults to the value within the intrusion policy that is applied to the detection engine. 3. Version 4.9. Click Edit next to the variable you want to define.

Click Add Variable. Click Variables next to the detection engine where you want to define a variable value.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 Creating New Variables for Detection Engines Requires: IPS or DC/MDC + IPS When you create an intrusion policy. The Detection Engines page appears. 4. See Understanding Custom Variables in the Analyst Guide if you are defining a special-purpose custom variable with one of the reserved variable names described in the Custom Variables table in the Analyst Guide. The Variable page appears. From the Variable Type drop-down list. To create a new variable for a detection engine: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 202 . select IP Port. enter a name for the variable. 3. 2. The Variable List page appears. . 5. • • • See Defining IP Addresses in Variables and Rules in the Analyst Guide for more information if you are defining a IP address-based variable.9. For an explanation see Using Variables within Detection Engines on page 199. See Defining Ports in Variables and Rules in the Analyst Guide for more information if you are defining a port-based variable. Select Operations > Configuration > Detection Engines > Detection Engines. or Custom. you can associate detection engine-specific variable definitions with the policy. Version 4. In the Variable Name field.

Version 4. The Variable List page appears again and shows the new variable and its value. In any intrusion policy that you apply to a different detection engine and do not explicitly set a policy-defined or detection engine-specific variable to override the value of the system variable.1 Sourcefire 3D System Administrator Guide 203 . IMPORTANT! Each new detection engine variable adds a system variable with a value of any that is accessible in all your intrusion policies. but only if they are not used in any active or inactive rule within the system. the value any will be used. In the Value field. You can also delete variables that you created within the context of the detection engine. The variable is created and is accessible to all policies as a system default variable. The Detection Engines page appears. and listed for all other detection engines on the Variable List page with a value of Policy Defined. The variable takes effect the next time you apply an intrusion policy to the detection engine. meaning that the value specified in the policy will be used when you apply the policy. You cannot delete predefined system variables within an intrusion policy. enter a value for the variable and click Save.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 6. It is listed in the variable list for the detection engine in all intrusion policies with the explicitly set value.9. Creating the new detection engine variable also lists the description Policy Defined for all other IPS detection engines on the Variable List page. To delete or reset variables on a detection engine: Access: Admin 1. Select Operations > Configuration > Detection Engines > Detection Engines. You can delete predefined system variables on the detection engine Variable List page. Deleting and Resetting Variables Requires: IPS or DC/MDC + IPS You can reset the value of a variable on the Variable List page and the variable reverts to the value defined in the intrusion policy the next time you apply the intrusion policy to the detection engine. See Creating New Variables in the Analyst Guide for information about the syntax for variables. as described in Applying an Intrusion Policy in the Analyst Guide.

The variable is deleted from the detection engine the next time you apply an intrusion policy to the detection engine. The variable is reset and Policy Defined appears in the Value column. 3. You then define the variable value with a set of instructions appropriate to the function the variable provides. Configuring Custom Variables in Detection Engines Requires: IPS or DC/MDC + IPS Custom variables allow you to configure special IPS features that you cannot otherwise configure via the web interface.1 Sourcefire 3D System Administrator Guide 204 . see Understanding Custom Variables in the Analyst Guide. You create a detection engine-specific custom variable by setting an explicit value for a reserved predefined system variable. click Reset next to the name of the variable. • To delete a locally created variable. The Variable List page appears.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 2. Version 4. click Delete next to the name of the variable. For more information. You can add a new USER_CONF detection engine variable using the reserved name USER_CONF .9. You can set an explicit detection engine value for the predefined SNORT_BPF custom system variable. Click Variables next to the detection engine where you want to delete or reset a variable value. You have two options: • To disable the variable value defined in the IPS detection engine and revert to the variable value defined in the policy. or by creating a variable using a specific reserved name.

see Assigning Values to System Default Variables in Detection Engines on page 200. The interface set can be passive. or inline with fail open depending on how your sensor is deployed. However. you may need to adjust the number of resources in the multi-resource detection engine. the sensor can process more packets with greater efficiency. Create another IPS detection engine that uses up to the remaining number of detection resources and the interface set that you created in step 1. Using Portscan-Only Detection Engines Requires: IPS or DC/MDC + IPS If you configure a sensor to use multiple detection resources within a single IPS detection engine. Engines on page 202.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 To configure the SNORT_BPF custom variable for a detection engine: Access: P&R Admin/Admin To set an explicit detection engine-specific value for SNORT_BPF using the existing system default variable. you can create a portscan-only intrusion policy and apply it to a portscan-only detection engine on the sensor. 3. The following steps outline the process you can use to configure your sensor to detect portscans in addition to other exploits against your network assets. Version 4. To overcome this issue. Make sure you use the interface set that you created in step 1. To configure the USER_CONF custom variable for a detection engine: Access: P&R Admin/Admin To create USER_CONF as a new detection engine-specific variable using the reserved name USER_CONF see Creating New Variables for Detection . Using the Defense Center’s web interface. Multiple detection engines will use this interface set. 1. inline. which is a requirement for the portscan preprocessor.1 Sourcefire 3D System Administrator Guide 205 . One downside to using multiple detection resources is that no single resource sees all the traffic on a network segment. 2. IMPORTANT! A portscan-only intrusion policy is able to process up to three times more traffic than a more complex intrusion policy because it uses fewer CPU resources. Remember that the portscan-only detection engine can use only one detection resource.9. In this way. Create an IPS portscan-only detection engine and assign one detection resource to it. a portion of the traffic that the 3D Sensor sees is directed to each detection resource for processing. Depending on the traffic mix on your network. Sourcefire recommends that you monitor the performance of your sensor to make sure that the portscan-only detection engine is able to keep up with the multi-resource detection engine. create an interface set that includes the network interfaces you want to use on the sensor. Internal logic on the sensor ensures that packets belonging to the same session are directed to the same resource for analysis.

Ensure that OPSEC Configuration (under External Responses) is disabled. Enable Portscan Detection and configure it for your network environment. or Rule Processing Configuration. The policy should inherit or be set to the following settings in the layer in your intrusion policy where you enable portscan detection (See Creating an Intrusion Policy in the Analyst Guide. See the Portscan Detection SIDs (GID:122) table in the Analyst Guide for more information. 6. the HTTP Configuration preprocessor. Working with Layers. Review the resulting intrusion events to ensure that you are receiving the events you expect.1 Sourcefire 3D System Administrator Guide 206 . Create and apply an intrusion policy for the multi-resource detection engine. make sure you disable portscan detection in this policy. items listed under Performance Statistics.9. Ensure that the DCE/RPC Configuration preprocessor. See Detecting Portscans in the Analyst Guide for more information. Make sure portscan rules are enabled for the types of portscans you configure. you must enable rules on the Rules page with generator ID (GID) 122 for enabled portscan types for the portscan detector to generate portscan events. You should not change the default settings for Checksum Verification or Packet Decoding (under Transport/Network Layer Preprocessors). and Applying an Intrusion Policy in the Analyst Guide for more information): • Select the No Rules Active Base Policy and make sure the Protection Mode is Passive. and Back Orifice Detection (under Specific Threat Detection) are disabled. You do not need to set up variables for this policy. 5. See Enabling and Disabling Advanced IPS Features in the Analyst Guide for more information. Enable IP Defragmentation (under Transport/Network Layer Preprocessors) and make sure it is configured for your environment (using the Hosts option) See Enabling and Disabling Advanced IPS Features in the Analyst Guide for more information. See Selecting the Base Policy in the Analyst Guide for more information. Also. Version 4. Note that all rules are disabled on the Rules page. • • • • • • IMPORTANT! Note that when portscan detection is enabled. Make sure you match the type of intrusion policy to the type of interface set that you created in step 1.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 4. the SMTP Configuration preprocessor (under Application Layer Preprocessors). Create and apply an intrusion policy to the portscan-only detection engine.

• With the exception of the Virtual 3D Sensor. The Virtual 3D Sensor supports only passive mode operation. See the following sections for more information about interface sets: • • • • • • • Understanding Interface Set Configuration Options on page 207 Creating an Interface Set on page 213 Creating an Inline Interface Set on page 216 Editing an Interface Set on page 221 Deleting an Interface Set on page 223 Inline Fail Open Interface Set Commands on page 225 Using Clustered 3D Sensors on page 227 Understanding Interface Set Configuration Options Requires: DC or 3D Sensor There are a number of configuration variables to consider when you configure interface sets. Some installations require that the link state be propagated and most sensor interfaces provide that option. inline. Sensors with Gigabit Ethernet interfaces can employ jumbo frames. To list the available interface sets: Access: Admin Select Operations > Configuration > Detection Engines > Interface Sets.9. see Using PEP to Manage Traffic in the Analyst Guide. 3D Sensors deployed in networks that are highly sensitive to latency can use the automatic application bypass option. On selected sensors you can set interfaces to tap mode. Only 3D9900 sensors provide a fail-safe option that works with inline interface sets. You can sort the available interface sets by group. or PEP policy. you can set up any of your 3D Sensor interfaces in passive. or inline with fail-open mode. For more information on the PEP feature. set type. • • • • • • • Version 4. sensor.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 Using Interface Sets Requires: DC or 3D Sensor An interface set is a collection of one or more sensing interfaces on your appliance. You can also set interfaces on most sensors in transparent inline mode.1 Sourcefire 3D System Administrator Guide 207 . Only 3D9900 sensors provide the PEP feature.

9.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 See the following table for a list of 3D Sensors and each of their applicable interfaces features. Supported Features by 3D Sensor Model 3D Sensor Model Virtual 3D Sensor 3D500 3D1000 3D2000 3D2100 3D2500 3D3000 3D3500 3D3800 3D4500 3D5800 3D6500 3D9800 3D9900 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Transparent Inline Mode Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Link State Propagation Mode Tap Mode Jumbo Frames Automatic Application Bypass Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Enable Fail-safe PEP See the following sections for more information: • • • • • • • Types of Interface Sets on page 209 Transparent Inline Mode on page 209 Tap Mode on page 210 Link State Propagation Mode on page 211 Jumbo Frames on page 212 Automatic Application Bypass on page 212 Enabling Fail-Safe on page 213 Version 4.1 Sourcefire 3D System Administrator Guide 208 .

The interfaces do not have to be on the same network cards. an inline interface set on a 3D3800 or 3D5800 sensor can include up to four interface pairs. or in addition to. You can set up multiple detection engines to use a single interface set. Transparent Inline Mode Transparent inline mode is a feature for inline interface sets and is not available for Passive interface sets.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 Types of Interface Sets When you create an interface set. It is not available on the 3D500 and available but not a default configuration on the Virtual 3D Sensor. except on the 3D9800 sensor. and an inline with fail open interface set on a 3D9800 sensor can include up to the total number of interface pairs on the sensor. If you choose the Inline or Inline with Fail Open option.1 Sourcefire 3D System Administrator Guide 209 . That is. then apply different policies to the detection engines. interfaces on the network cards).9. Version 4. you could create a single passive interface set and create two detection engines. This allows the sensor to act as a “bump in the wire” and means that the sensor forwards all the network traffic it sees regardless of its source and destination. However. the Transparent Inline Mode option is enabled by default. Note that interface pairs on the same fiber-based NIM will act as fail open interfaces even if you assign them to an inline interface set. the appliance’s performance could be degraded. you can choose one of three types: • Passive A passive interface set can encompass any number of the available sensing interfaces on a sensor. an inline interface set can include any two interfaces. IMPORTANT! If you include an on-board sensing interface (instead of. an inline with fail open interface set on a 3D3800 or 3D5800 sensor can include up to four interface pairs. network traffic continues to flow through the sensor as it would for an inline with fail open interface set. • Inline with Fail Open For most sensors. and an inline interface set on a 3D9800 sensor can include up to the total number of interface pairs on the sensor. • Inline For most sensors. an inline with fail open interface set must include exactly one interface pair. one for an IPS and the other for RNA. For example. if the power fails or the Snort process halts. but you should avoid using an on-board interface. except for the 3D500 and the Virtual 3D Sensor. However. which only supports a single IPS detection engine.

it does not allow the traffic to pass through the interface to the side of the network with Host C. rules of these types do generate intrusion events when they are triggered. rules that you set to Drop and rules that use the replace keyword do not affect the packet stream. Keep in mind that if you create an inline interface set but do not use transparent inline mode. and forwards packets accordingly. If the sensor is inline and you are not using transparent inline mode. TIP! 3D9800 sensors with earlier versions of firmware do not support tap mode. For example. then if the sensor sees network traffic from Host A to Host B.9. Version 4. consider the following diagram. if your sensor includes a detection engine with an inline interface set) and the Transparent Inline Mode option is selected. you must be especially careful not to create loops in your network infrastructure. when the sensor sees traffic from Host A to Host B. Tap Mode Tap mode is available for the 3D3800. 3D9900. Because you are working with copies of packets rather than the packets themselves. and you cannot disable it. However. and on later versions of 3D9800 3D Sensor when you create an inline or inline with fail open interface set. a sensor acts as a bridge. the sensor is deployed inline. Only traffic between Host A and Host C or between Host B to Host C is allowed to pass. it allows the traffic to pass through the interface even though Host A and Host B are on the same side of the sensor. With tap mode. 3Dx800 sensors run in transparent inline mode. a copy of each packet is sent to the sensor and the network traffic flow is undisturbed. If your sensor is deployed inline (or more precisely.1 Sourcefire 3D System Administrator Guide 210 .Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 If you disable this option. Over time. the sensor learns which hosts are on which side of the inline interface. but instead of the packet flow passing through the sensor. The Sourcefire 3D System checks the 3D9800 firmware version and displays the optional tap mode check box in the Create Interface Set page when appropriate. 3D5800.

Otherwise. the second interface automatically comes back up. Link state propagation mode automatically brings down the second interface in the interface pair when one of the interfaces in an inline interface set goes down. you must either configure an IPS detection engine that uses that interface set. Version 4. the RNA detection engine monitoring that interface set will not see any traffic. too. Link State Propagation Mode Link state propagation mode is a feature for interface sets in the inline fail-open mode so both pairs of an inline pair track state. the link state of the other interface is changed automatically to match it. you can set up the cabling between the sensor and the network as if the sensor were inline and analyze the kinds of intrusion events the sensor generates. It is also available on 3D9900s in both the inline and inline fail-open mode. Based on the results. see Removing Bypass Mode on Inline Fail Open Fiber Interfaces on page 225. you can disable tap mode and begin dropping suspicious traffic without having to reconfigure the cabling between the sensor and the network.9. the RNA or RUA detection engine monitoring that interface set will not see any traffic until the IPS detection engine restarts. When the downed interface comes back up. When you are ready to deploy the sensor inline. if the link state of one interface changes. you can modify your intrusion policy and add the drop rules that best protect your network without impacting its efficiency. Neither RNA nor RUA are supported on the 3D9800 sensor. It is not available for passive interface sets. In other words. other than those on 3D9900s must be in hardware bypass mode for link state propagation to function correctly. as well as apply an intrusion policy to that detection engine. or configure the interface set in tap mode. IMPORTANT! Fiber interface sets configured as inline fail-open. If you are monitoring the same inline interface set with both IPS and RNA or RUA.1 Sourcefire 3D System Administrator Guide 211 . For example. For more information about fiber interface sets and hardware bypass. IMPORTANT! Crossbeam-based software sensors and 3D9800 sensors do not support link state propagation. Link state propagation is available for both copper and fiber fail-open NIMs. IMPORTANT! On a 3D3800 or 3D5800 sensor. if you plan to use RNA to monitor either an inline or inline with fail open interface set.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 There are benefits to using tap mode with sensors that are deployed inline. and the IPS detection engine fails for any reason.

Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 Link state propagation is especially useful in resilient network environments where routers are configured to reroute traffic automatically around network devices that are in a failure state. If a detection engine is bypassed. You can apply automatic application bypass on an interface set basis. If your 3D Sensor and interface supports jumbo frames.000 ms. 3D Sensors generate a health monitoring alert. For more information on the health monitoring alert. a core file is automatically generated for potential troubleshooting by Sourcefire Support. see Configuring Automatic Application Bypass Monitoring on page 502. Typical maximum sized jumbo frames are 9018 bytes. or RUA detection engine and allows packets to bypass the detection engine if the time is exceeded. The automatic application bypass option is off by default. Note also that frames larger than the configured maximum frame size are silently dropped by the sensor.9. however. you do not need to set it in the Create Interface Set page. Automatic application bypass limits the time allowed to process packets through an IPS. set the maximum frame size for the interface using the Create Interface Set page. The valid range is from 250 ms to 60. The feature functions with both passive and inline interface sets. WARNING! If a detection engine is bypassed. Most gigabit Ethernet network interface cards support jumbo frames to increase efficiency. To see a list of which 3D Sensors you can use Automatic Application Bypass Monitoring on. Jumbo Frames Jumbo frames are Ethernet frames with a frame size greater than the standard 1518 bytes. 3D Sensor that support jumbo frames include: • • • 3D6500 3D9800 (9018-byte jumbo frames are always accepted) 3D9900 Note that since the 3D9800 is set to always accept the maximum size frame. The default setting is 750 milliseconds (ms). excessive numbers of core files can result in disk usage health alerts. RNA. Version 4. You can change the bypass threshold if the option is selected. see the Supported Features by 3D Sensor Model table on page 208.1 Sourcefire 3D System Administrator Guide 212 . If the application bypass triggers repeatedly. it is most valuable in inline deployments. Automatic Application Bypass The automatic application bypass feature allows you to balance packet processing delays with your network’s tolerance for packet latency.

traffic is allowed to bypass detection and continue through the sensor. The Interface Sets page appears. Version 4. The Create Interface Set page appears.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 Enabling Fail-Safe The Create Interface Set page includes an additional option for 3D9900 sensors: the Enable Fail-Safe option. When you enable the Enable Fail-Safe option. 2. Passive. Select Operations > Configuration > Detection Engines > Interface Sets. Click Create Interface Set. 3D9900 sensors monitor internal traffic buffers and bypass detection engines if those buffers are full. To create an interface set: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 213 .9. see the next section. or Inline with Fail Open. Type a name and description for the new interface set in the Name and Description fields. Creating an Inline Interface Set. You can use alphanumeric characters and spaces. TIP! Some sensors do not support every interface set type. 4. The Enable Fail-Safe option is only available on inline interface configurations. Creating an Interface Set Requires: DC or 3D Sensor An interface set is a collection of one or more sensing interfaces on your appliance. For more information. Inline. Select the type of interface you want to create. IMPORTANT! The procedure for creating an inline interface set for 3Dx800 sensors is slightly different. 3. For information about their use. from the Interface Set Type drop-down list. see Using Interface Sets on page 207.

When the option selected. you can select a Bypass Threshold in milliseconds (ms). then optionally. 9. The default setting is 750 ms and the valid range is from 250 ms to 60. you can select the Enable Fail-safe check box to enable traffic pass-though during application bypass. You can. Optionally. 7.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 5. Automatic Application Bypass is most useful in inline applications. select Automatic Application Bypass if your network is sensitive to latency. clear the Transparent Inline Mode check box to disable transparent mode. IMPORTANT! Link state propagation and automatic application bypass are not supported on Sourcefire 3D Sensor Software for X-Series platforms.1 Sourcefire 3D System Administrator Guide 214 . however. select Link State Propagation Mode. This option is especially useful if the routers on your network are able to re-route traffic around a network device that is down. Version 4. Optionally. If you selected either the Inline or Inline with Fail Open option and you are not configuring a Crossbeam-based software sensor. See Using Interface Set Groups on page 223 for more information. and if you are configuring an inline interface set on a 3D9900.9. Optionally. select an existing interface set group or select Create New Group to create a new interface set group.000 ms. Optionally. set jumbo frame options on the Crossbeam CLI. 8. if you selected the Inline or Inline with Fail Open option. 6.

Version 4. including a list of ungrouped sensors. A list of network interfaces on the sensor appears. and if you are configuring an interface set on a 3D6500 or 3D9900 type a maximum frame size for your IP traffic in the Maximum Frame Size field. 12. a list of sensor groups appears. You can set any jumbo frame size between 1518 and 9018 bytes. A list of sensors appears.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 10.9. Defense Center Only Select the sensor group containing the sensors where you want to create the interface set. On the Defense Center only. The following shows a 3D9900 interface set.1 Sourcefire 3D System Administrator Guide 215 . You can also select the ungrouped sensors. 11. Optionally. Defense Center Only Select one of the sensors from the list. inclusive.

1 Sourcefire 3D System Administrator Guide 216 . For 3D Sensor Software for Crossbeam Systems X-Series. the names that appear in the Available Interfaces list correspond to the device names you assigned to the circuits you created on the X-Series. Select the interfaces that you want to add from the Available Interfaces list and click the arrow button to add the interface to the Selected Interfaces list. TIP! After you create an interface set. Different types of interface sets have different requirements. A message appears on the console indicating the name of the interface (eth1.9. For example. IMPORTANT! If you select an on-board interface rather than an interface on a network card. see the Installation Guide for your sensor or sensor software. Using one interface set that includes all available inline interface pairs. Click Save. the names that appear in the Available Interfaces list correspond to the slot number and interface location. For 3Dx800 sensors. 14.e0 corresponds to the leftmost interface on the network interface module (NIM) in I/O Slot 0 on the back of your appliance. Remember to reconnect the network cable when you are finished. and so on). The interface set is created.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 13. make sure you reapply intrusion policies to the IPS detection engines on the affected sensor. you can include all of the available interfaces in a passive interface set. log into the console and disconnect the network cable from the interface. your sensor may not provide optimum performance. Determining which interface name corresponds with a physical interface on your sensor depends on the model: • For most 3D Sensors. eth2. but inline interface sets must contain exactly two interfaces (except on 3Dx800 sensors). s0. You can use the Shift and Ctrl keys to select multiple interfaces at once. • • For more information. This is the default behavior during 3D Sensor installations. Creating an Inline Interface Set Requires: DC or 3D Sensor You can add multiple interface pairs to an inline interface set on 3D Sensors and Crossbeam-based software sensors. For example. Inline with fail open interface sets must contain one pair of interfaces from the same fail-open network card. you can apply a single policy and rapidly complete your initial Version 4.

Your network may be set up to route traffic between a host on your network and external hosts through different interface pairs depending on whether the traffic is inbound or outbound.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 3D Sensor deployment. You can also use multiple interface pairs when your network employs asynchronous routing.9.1 Sourcefire 3D System Administrator Guide 217 . Later. TIP! Although the default interface set on 3D Sensors includes all the available inline interface pairs. If you include only one interface pair in an interface set. in many cases you can improve performance by modifying the interface set to include only the inline interface pairs your network requires. as shown in the following graphic. Version 4. the sensor might not correctly analyze your network traffic because a detection engine might see only half of the traffic. you can refine policies for specific connected network segments and their requirements.

The Interface Sets page appears. 4. Otherwise. For Crossbeam-based software sensors. and the IPS detection engine fails for any reason. you must either configure an IPS detection engine that uses that interface set. no packets are lost. Select the type of inline interface you want to create. from the Interface Set Type drop-down list. if you plan to use RNA to monitor either an inline or inline with fail open interface set. 3. the RNA detection engine monitoring that interface set will not see any traffic. or configure the interface set in tap mode. including a list of ungrouped sensors. Version 4. a software bridge is automatically set up to transport packets when the sensor restarts. choose Inline from the Interface Set Type drop-down list. choose either Inline or Inline with Fail Open. the RNA or RUA detection engine monitoring that interface set will not see any traffic until the IPS detection engine restarts. To create an inline interface set: Access: Admin 1. If you are monitoring the same inline interface set with both IPS and RNA or RUA. Optionally. 5. select an existing interface set group or select Create New Group to create a new interface set group. • • For an 3Dx800 sensor. See Using Interface Set Groups on page 223 for more information.1 Sourcefire 3D System Administrator Guide 218 . Select Operations > Configuration > Detection Engines > Interface Sets. as well as apply an intrusion policy to that detection engine. A list of sensor groups appears. 2. You can use alphanumeric characters and spaces. Type a name and description for the new interface set in the Name and Description fields. The Create Interface Set page appears.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 For most 3D Sensors with inline interface sets.9. Neither RNA nor RUA are supported on the 3D9800 sensor. Click Create Interface Set. IMPORTANT! On a 3D3800 or 3D5800 sensor. Although some packets are transmitted without inspection during this time.

however. 9. If you are creating an inline interface set. a list of sensor groups appears. If you are creating an inline with fail open interface set. 7. you can select the Enable Fail-safe check box to enable traffic pass-though during application bypass. you can select a Bypass Threshold in milliseconds (ms). select Automatic Application Bypass if your network is sensitive to latency. inclusive. When the option selected. You can set any jumbo frame size between 1518 and 9018 bytes.000 ms.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 6.1 Sourcefire 3D System Administrator Guide 219 . Optionally. and if you are configuring an interface set on a 3D6500 or 3D9900 type a maximum frame size for your IP traffic in the Maximum Frame Size field. Version 4. including a list of ungrouped sensors. Select one of the sensors from the list. On the Defense Center only. 8. You can. The following shows a 3D9900 interface set. and if you are configuring an interface set on a 3D9900. IMPORTANT! Link state propagation and automatic application bypass are not supported on Sourcefire 3D Sensor Software for X-Series platforms. set jumbo frame options on the Crossbeam CLI. Optionally. a list of paired network interfaces on the sensor’s fail-open cards appears. The default setting is 750 ms and the valid range is from 250 ms to 60. a list of network interfaces on the sensor appears. Optionally.9.

1 Sourcefire 3D System Administrator Guide 220 . for a 3DX800 or 3DX900 sensor. Repeat to add additional interface pairs. • If you are creating an inline interface set. • For more information. Add the interfaces to your interface set. For example. select two interfaces that you want to designate as an inline pair from the Available Interfaces list and click the arrow button to add the interface to the Selected Interfaces list. TIP! 3D9800 sensors with earlier versions of firmware do not support tap mode. select the Enable Tap Mode check box to use tap mode. Note that 3D Sensor Software for Crossbeam Systems X-Series does not support inline with fail open interface sets. You can configure inline interface sets on 3D3800 and 3D5800 sensors to contain up to four pairs of interfaces. the paired interface names that appear in the Available Interfaces list correspond to the device names you assigned to the transparent bridge-mode bridge circuits you created on the X-Series. Inline with fail open interface sets on 3D3800 and 3D5800 sensors can also contain up to four pairs of interfaces. select at least one interface pair from the Available Interfaces list and click the arrow button to add the interface to the Selected Interfaces list.e0 corresponds to the leftmost interface on the network interface module (NIM) in I/O Slot 0 on the back of your appliance.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 10. If you are creating an inline with fail open interface set. inline and inline with fail open interface sets can include up to the total number of interface pairs on the sensor. Optionally. see the Installation Guide for your sensor or sensor software. On the 3D9800 sensor. s0. the names that appear in the Available Interfaces list correspond to the slot number and interface location. but each pair must reside on a single fail-open network card.9. The Sourcefire 3D System checks the 3D9800 firmware version and displays the optional tap mode check box in the Create Interface Set page when appropriate. For 3D Sensor Software for Crossbeam Systems X-Series. 11. • Use the Shift and Ctrl keys to select multiple interfaces or interface pairs at once. Determining which interface name corresponds with a physical interface on your sensor depends on the model: • For 3Dx800 sensors. Version 4.

Editing an Interface Set Requires: DC or 3D Sensor In some circumstances. no packets are lost. TIP! The link lights on fiber fail-open NIMs remain lighted even when the link state is down on 3D3800 or 3D5800 sensors with link state propagation enabled.1 Sourcefire 3D System Administrator Guide 221 . Click Save. The following sections describe some of the cases where a detection engine is affected by changes to the detection engines and interface sets: Version 4.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 12. Optionally. This option is especially useful if the routers on your network are able to re-route traffic around a network device that is down. which can cause a short pause in processing. The interface set is created. TIP! After you create an interface set. select Link State Propagation Mode. editing an interface set or detection engine can cause the detection engines on the sensor to restart.9. a software bridge is automatically set up to transport packets when the sensor restarts. IMPORTANT! For most 3D Sensors with inline interface sets. make sure you reapply intrusion policies to the IPS detection engines on the affected sensor. Although some packets are transmitted without inspection during this time. 13. IMPORTANT! Note that link state propagation is not available for Crossbeambased software sensors or 3D9800 sensors. for a 3D3800 or 3D5800 sensor.

• If you change the number of detection resources.9.1 Sourcefire 3D System Administrator Guide 222 . that detection engine is restarted. all detection engines assigned to that interface set are restarted. nothing is restarted. If you change an interface set’s tap mode setting. which interface set is used. If you change an interface set’s transparent mode setting or interface set type. all the detection engines using that interface set are restarted. If you create an interface set. all the detection engines on the sensor are restarted. nothing is restarted. If you create a detection engine. When you create a detection engine. If you change which network interfaces are used by the interface set. or the detection engine type. or transparent mode for an interface set. all the detection engines on the sensor are restarted because the total number of allocated resources has changed. If you change a detection engine’s interface set. all the detection engines on the sensor are restarted. only that detection engine is restarted (although other CPUs may be restarted to rebalance the processing load).Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 3Dx800 Sensors • If you change the number of network interfaces. If you delete a detection engine or interface set. If you delete a detection engine or interface set. only that detection engine is started (although other CPUs may be restarted to rebalance the processing load). If you change the name or description of an interface set or detection engine. all detection engines on the sensor are restarted. If you change the detection engine type for a detection engine. • • • • • Other Sensors • • • • • • • Version 4. all detection engines on the sensor are restarted. If you change the number of detection resources allocated to a detection engine. the interface set type. all detection engines on the sensor are restarted. TIP! 3D9800 sensors with earlier versions of firmware do not support tap mode. The Sourcefire 3D System checks the 3D9800 firmware version and displays the optional tap mode check box in the Create Interface Set page when appropriate. all detection engines assigned to that interface set are restarted.

at the prompt. For more information on PEP policies. If you change the name or description of an interface set or detection engine. nothing is restarted. Click Delete next to the interface set that you want to delete. The Interface Sets page appears.9. nothing is restarted. To delete an interface set: Access: Admin 1. 3. TIP! After you edit an interface set used by an IPS detection engine. The Interface Sets page appears. Make sure you plan these actions for times when they will have the least impact on your deployment. Select Operations > Configuration > Detection Engines > Interface Sets.1 Sourcefire 3D System Administrator Guide 223 . make sure you reapply your intrusion policy on the affected sensor. The Create Interface Set page appears. 2. and. Click Edit next to the interface set that you want to modify. 2. Select Operations > Configuration > Detection Engines > Interface Sets. Deleting an Interface Set Requires: DC You cannot delete an interface set that is being used by a detection engine. You must delete the detection engine before you can delete the interface set. The interface set is deleted. Your changes are saved. Make any changes to the interface set and click Update. See the following sections for more information: • • Creating Interface Set Groups on page 224 Deleting Interface Set Groups on page 225 Version 4. To edit an interface set: Access: Admin 1. These groups make it easier to apply PEP policies to interface sets that have similar purposes. confirm that you want to delete the interface set. Using Interface Set Groups Requires: DC You can use interface set groups to combine similar interface sets.Using Detection Engines and Interface Sets Using Interface Set Groups Chapter 6 • • If you create an interface set. A restart occurs only when you assign a detection engine to the interface set. see Understanding PEP Traffic Management in the Analyst Guide.

adding available interfaces to the group and clicking Save. Select Operations > Configuration > Detection Engines > Interface Sets. 2.Using Detection Engines and Interface Sets Using Interface Set Groups Chapter 6 Creating Interface Set Groups Requires: DC The following procedure explains how to create an interface set group. 2. The Available Interface Sets page appears.9. Version 4. on the Interface Group Edit page. Click Save. The Interface Group Edit page appears. See Creating Interface Set Groups on page 224. Editing Interface Set Groups Requires: DC/MDC or 3D Sensor The following procedure explains how to edit an interface set group. The Create Interface Set Group page appears. To edit an interface set group: Access: Admin 1. You can add interface sets to an interface set group by clicking Edit next to a interface set group name and. To create a interface set group: Access: Admin 1. Click Create Interface Set Group or click Create Interface Set then click Create New Group in the Group field. 3. Type a name for the interface set group in the Group Name field.1 Sourcefire 3D System Administrator Guide 224 . You must create an interface set group before you can edit it. The Interface Set page appears again. Select Operations > Configuration > Detection Engines > Interface Sets. Click Edit for the interface set group.

The interface set group is deleted. IMPORTANT! Make sure you contact Technical Support if you are having issues with the fail open interfaces on your sensor.1 Sourcefire 3D System Administrator Guide 225 . You can also move interface sets out of the interface set group. Inline Fail Open Interface Set Commands Requires: 3D Sensor When you use fiber inline fail open interfaces sets and the interface set goes into bypass. Version 4. any interface sets in the group are automatically ungrouped. Click Delete next to the name of the interface set group. 2. You can force a copper or fiber inline fail open interface in or out of bypass. See Forcing an Inline Fail Open Interface Set into Bypass Mode on page 226. 4. Deleting Interface Set Groups Requires: DC When you delete an interface set group. most fiber inline fail open interface sets do not return from bypass automatically. TIP! This tool works on most 3D Sensors with inline with fail open fiber interface pairs. all network traffic passes through the interface pair without being analyzed. See Removing Bypass Mode on Inline Fail Open Fiber Interfaces.Using Detection Engines and Interface Sets Inline Fail Open Interface Set Commands Chapter 6 3. To delete a interface set group: Access: Admin 1. The Available Interface Sets page appears. You can use a command line tool to force the interface set out of bypass mode. The Interface Sets page appears. When the links restore. It is not necessary to use this tool on inline with fail open copper interface pairs or to use this tool with 3D9900 sensors. Select Operations > Configuration > Detection Engines > Interface Sets. Select available interface sets and to move them to the interface set group with the arrow buttons.9. they are not deleted. you can force the interface out of bypass mode. Removing Bypass Mode on Inline Fail Open Fiber Interfaces Requires: 3D Sensor When link state propagation is enabled on a sensor with an inline fail open interface set and the sensor goes into bypass mode. Click Save to add the selected interfaces to the interface set group.

a message in syslog indicates the 3D Sensor is analyzing traffic. You cannot use it with non-fail open inline interface sets. it goes into bypass mode. at the prompt. or if the interface card does not fail open on its own. click Edit next to the inline with fail open interface set you are investigating. On the appliance’s web interface. Enter the following at the command line: 3. Log in as root onto the sensor and. Open a terminal window on your 3D Sensor and enter the command su and the root password to switch to the root user.1 Sourcefire 3D System Administrator Guide 226 . The Create Interface Set page appears. You can determine this information on the Interface Sets page.Using Detection Engines and Interface Sets Inline Fail Open Interface Set Commands Chapter 6 To force a fiber inline fail open interface set out of bypass mode: Access: Admin 1.sh 2. 3. The Interface Sets page appears.9. If you are troubleshooting an interface set. To force an inline fail open interface set into bypass mode. /var/sf/bin/unbypass_cards. IMPORTANT! Make sure you contact Technical Support if you are having issues with the fail open interfaces on your sensor. For example: Fiber pair has been reset by un_bypass Forcing an Inline Fail Open Interface Set into Bypass Mode Requires: 3D Sensor When the sensor with an inline fail open interface set fails. Version 4. you can use a command line tool to force the interface set into bypass mode. a state where all network traffic passes through the interface pair without being analyzed. select Operations > Configuration > Detection Engines > Interface Sets. When the interfaces switch out of bypass mode. The Selected Interfaces column displays the names of the interfaces in the interface set. 2. TIP! Note that this tool works only with inline with fail open interface pairs. Under Available Interface Sets. enter the correct password. To force an inline fail open interface set into bypass mode: Access: Admin 1. you must know which two interfaces are included in the interface set.

Version 4.pl close eth2:eth3 The following message appears: Mode changed for interfaces eth2:eth3 The interfaces return to normal mode and the traffic flowing through the detection engines on the interface set is analyzed as you would expect. you can identify them on the Sensor list page.9. at the prompt. Enter the following at the command line: failopen_pair. enter the following: failopen_pair. see Managing a Clustered Pair on page 140. Using Clustered 3D Sensors Requires: DC + 3D9900 You can increase the amount of traffic inspected on a network segment by connecting two fiber-based 3D9900 sensors in a clustered pair. Select Operation > Sensors and note that clustered sensors have a peer icon. if the interfaces in the interface set are eth2 and eth3.pl open eth#:eth# For example.Using Detection Engines and Interface Sets Using Clustered 3D Sensors Chapter 6 4. If you did not specify the correct interfaces. you combine the 3D9900 sensors resources into a single. the following message appears: Mode changed for interfaces eth2:eth3 The interfaces switch to bypass mode and the traffic is no longer analyzed. Log in as root onto the sensor and. For information on establishing and separating clustered pairs. When you establish a clustered pair configuration. if you specified the correct interfaces.pl close eth#:eth# For example. shared configuration.1 Sourcefire 3D System Administrator Guide 227 . To return an inline fail open interface set to normal mode: Access: Admin 1.pl open eth2:eth3 The following message appears: NOTE: You must already have a failopen interface set and detection engine configured on the pair you are forcing open or closed for this utility to work. After the cluster is established. 2. enter the following: failopen_pair. enter the correct password.. if the interfaces in the interface set are eth2 and eth3. Enter the following at the command line: failopen_pair. the following message appears: No failopen interface set configured for interfaces eth2:eth3. Then..

the Defense Center displays the single interface set of the master sensor. and which sensor it is paired with.9. a clustered 3D Sensors detection engine could be: Z inline DE (birch.1 Sourcefire 3D System Administrator Guide 228 . see: • • • Managing Clustered 3D Sensor Detection Engines on page 228 Using Clustered 3D Sensor Detection Engines in Policies on page 229 Managing Information from a Clustered 3D Sensor on page 230 Creating a Detection Engine on page 193 Editing a Detection Engine on page 194 Deleting a Detection Engine on page 197 For information about how to manage detection engines. you can only manage them from a Defense Center and not from one of the clustered sensors. edit. For example.com is the name of the slave in the pair of 3D9900 sensors. You cannot manage detection engines on the local GUI of a paired 3D Sensor. and fir.Using Detection Engines and Interface Sets Using Clustered 3D Sensors Chapter 6 You can see if the sensor is a master or slave. SlaveSensorName).example. By combining two 3D9900 sensors as a clustered pair. you can combine their detection engines. see: • • • Managing Clustered 3D Sensor Detection Engines Requires: DC + 3D9900 Use the managing Defense Center to create. where Z inline DE is the name of the detection engine.com. Version 4. when you hover over the peer icon.example. the Edit page is replaced with an informational page.com is the name of the master in the pair. and list the detection engines of paired 3D Sensors. the slave’s ethb0 and ethb1 connect to the master and the its ethb2 and ethb3 are not connected. In a clustered pair. You use the combined detection engines as a single entity except when viewing information from the clustered pair. both sensors are listed in the interface set.example. Because the detection engines and interface sets are combined. see: • • • Using Detection Engines on Clustered 3D Sensors on page 228 Understanding Interface Sets on Clustered 3D Sensors on page 229 Managing Information from a Clustered 3D Sensor on page 230 Using Detection Engines on Clustered 3D Sensors Requires: DC + 3D9900 For information about using detection engines with clustered 3D9900s. When you create a detection for a clustered pair. When you combine two 3D9900 sensors as a clustered pair. fir.example. Both 3D9900 sensors are listed as a part of the detection engine formed by the clustered 3D Sensors. The format is DetectionEngineName (MasterSensorName.com). For more information. birch.

Understanding Interface Sets on Clustered 3D Sensors Requires: DC + 3D9900 After you set up the clustered pair. those pages are replaced with an informational page. a master/slave relationship is established between the two 3D9900 sensors.1 Sourcefire 3D System Administrator Guide 229 . Clustered 3D Sensors detection engines present their names in the form DetectionEngineName (MasterSensorName.com. The slave’s ethb2 and ethb3 pair are not functional and must not be connected when you establish the clustered pairing. and fir. The master’s ethb2 and ethb3 pair connect to the slave’s ethb0 and ethb1 pair. fir. Version 4.example. IMPORTANT! You cannot use the Policy & Response menu on the local GUI of a paired 3D Sensor.Using Detection Engines and Interface Sets Using Clustered 3D Sensors Chapter 6 When you create or edit a detection engine formed by the clustered 3D Sensors.com is the name of the slave in the pair of 3D9900 sensors. a clustered 3D Sensors detection engine could be: Z inline DE (birch. Using Clustered 3D Sensor Detection Engines in Policies Requires: DC + 3D9900 Use the managing Defense Center to manage policies and responses of paired 3D Sensors. where Z inline DE is the name of the detection engine.example. birch. The master’s ethb0 and ethb1 pair are used for sensing connections.com).com is the name of the master in the pair.example.example. the detection resources are listed as from both sensors. SlaveSensorName) when you use them in: • • • • IPS policies PEP policies RNA detection policies compliance rules For example.9.

com. When you examine information from the clustered pair.example. A clustered pair interface set displays both the master and the slave in the Sensor column.example. For information about using interface sets in the detection engines of clustered 3D9900s.example.com and from Z inline DE / fir.9. see Using Detection Engines on Clustered 3D Sensors on page 228. in the form DetectionEngineName/MasterSensorName and DetectionEngineName/SlaveSensorName. and fir. Do not attempt to change the interface settings while a clustered sensor is paired. Analysis & Reporting tools display the information from each half of the detection engine independently. add data from both sensor of the detection engine to measure the total. For example. IMPORTANT! If you collect statistics from clustered 3D9900s. where Z inline DE is the detection engine. it is listed as from both Z inline DE / birch. birch.Using Detection Engines and Interface Sets Using Clustered 3D Sensors Chapter 6 To view the clustered pair interface sets: Access: Admin Select Operations > Configuration > Detection Engines > Interface Sets. Managing Information from a Clustered 3D Sensor Requires: DC + 3D9900 Clustered sensors report information from each of the sensors. These reports include: • • • intrusion event statistics intrusion events event graphs Version 4.example. The Interface Sets page appears. A Select Detection Engines list from the Intrusion Event Statistics page is show below.com is the master sensor. fir.com is the slave sensors.com. the clustered 3D Sensors detection engine could be: Z inline DE (birch.example.example.com).1 Sourcefire 3D System Administrator Guide 230 .

Version 4. The eStreamer settings are not automatically synchronized over the pair.Using Detection Engines and Interface Sets Using Clustered 3D Sensors Chapter 6 • • • • dashboards RNA statistics network map searches IMPORTANT! If you use eStreamer to stream event data from a clustered pair of 3D9900s to an external client application. collect the data from both 3D9900s and ensure that you configure each 3D9900 identically.9.1 Sourcefire 3D System Administrator Guide 231 .

You can run the report on the 3D Sensor or on the Defense Center that manages the sensor. Report Types Report Intrusion Events with Destination Criticality Intrusion Events with Source Criticality Intrusion Events SEU Import Log Host Attributes Report Category IPS or RNA IPS or RNA IPS IPS RNA Requires DC + RNA + IPS DC + RNA + IPS DC + IPS DC + IPS DC + RNA Version 4.9. The Report Types table describes the reports you can create and the components required for producing them. Similarly. the Intrusion Events report appears under the IPS report category and requires the IPS component on a 3D Sensor.1 Sourcefire 3D System Administrator Guide 232 . For example.Working with Event Reports Chapter 7 Sourcefire 3D System Administrator Guide The Sourcefire 3D System provides a flexible reporting system that you can use to generate a variety of event reports. the RNA Events report appears under the RNA report category on the Report Designer page. Event reports include the data that you see on the event view pages for each type of event presented in a report format. and you must configure the RNA component for that sensor to collect RNA events. You must have an RNA host license on the Defense Center managing your 3D Sensor.

Version 4.Working with Event Reports Chapter 7 Report Types (Continued) Report RNA Hosts Scan Results RNA Client Applications RNA Events RNA Services Vulnerabilities Hosts with Services Flow Data RUA Events Users White List Violations Compliance Events White List Events Remediation Status Health Events Audit Log Events Report Category RNA RNA RNA RNA RNA RNA RNA RNA RUA RUA Compliance Compliance Compliance Compliance Health Monitoring Audit Log Requires DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RUA DC + RUA DC + RNA DC + RNA DC + RNA DC + RNA DC Any You can use a predefined report profile to generate your report.9. For more information on how to create and save report profiles. see Understanding Report Profiles on page 241. You can create a new report profile through the use of the Report Designer. see Editing Report Profiles on page 263. For information on modifying a predefined or existing report profile. or use it as a template for an event report profile which can be customized by modifying field settings as appropriate and saving the report with the new values.1 Sourcefire 3D System Administrator Guide 233 .

9. For more information on how to manage your reports. Working with Report Profiles Requires: IPS or DC/ MDC You can use a predefined report profile to generate your report.1 Sourcefire 3D System Administrator Guide 234 . or SMB. see Running Remote Reports on page 240. For information on how to generate a report from a report profile view. download. or delete previously generated reports. For more information on how to how to generate reports on managed sensors and view the results on the Defense Center. see Editing Report Profiles on page 263. For information on how to generate a report for the data that appears in an event view. see Using a Report Profile on page 260. as well as move reports to a remote storage location. For more information on how to configure a Defense Center to store reports in a remote location using SSH. see Creating a Report Profile on page 246. see Managing Remote Storage on page 393.Working with Event Reports Working with Event Reports Chapter 7 See the following sections for more information: • • • • • • • • Working with Event Reports on page 234 Working with Report Profiles on page 234 Managing Generated Reports on page 237 Understanding Report Profiles on page 241 Working with Report Information on page 248 Working with Report Sections on page 255 Working with Report Options on page 258 Using a Report Profile on page 260 Working with Event Reports Requires: IPS or DC/ MDC You can generate reports manually or automatically on any subset of events in an event view. For more information on how to create and save report profiles. You can use a predefined report profile as a template for an event report which can be customized by modifying field settings as appropriate and saving the report with the new values. You can create a new report profile through the use of the Report Designer. see Generating Reports from Event Views on page 235. Version 4. NFS. You can store reports locally or remotely. see Managing Generated Reports on page 237. You can run reports remotely from the Defense Center using the data on the sensors for the report. You can view. if you use a Defense Center to manage your sensors. You can also specify which detection engine to use when generating the report. For information on how to modify a report profile.

You can also specify how you want the report formatted: PDF HTML. Populate an event view with the events you want to include in the report. you can also create a report profile and then either use it to generate a report or save it to use later. Generating Reports from Event Views Requires: IPS or DC/ MDC You can generate reports on any subset of events in an event view. For more information. see Working with Report Options on page 258. • TIP! In addition to generating reports in an event view. You can do this several ways: • Use an event search to define the type of events you want to view. . see Understanding Report Profiles on page 241. as described in this section. see Searching for Events in the Analyst Guide. and a short description of the report. To generate a report for a specific set of events: Access: Any Analyst/ Admin 1. or as comma-separated .Working with Event Reports Generating Reports from Event Views Chapter 7 You can include a summary report for intrusion events and RNA events by selecting the appropriate radio button in your report profile. For more information on each of the summary reports. values (CSV). For information on how to incorporate these options into your reports. see Understanding and Using Workflows in the Analyst Guide. Version 4. Drill down through a workflow until you have the proper events in your event view. You can generate reports in PDF HTML or comma-separated value (CSV) formats. and include custom options such as a corporate logo or footers. For details on using the event search. see Using Summary Reports on page 255.1 Sourcefire 3D System Administrator Guide 235 . For details on using workflows and constraining events within a workflow.9.

Click Generate Report. The Report Designer page appears. Note that you may select more than one format. or CSV. 5. The following graphic shows the Defense Center version of the page. 3. TIP! If you need to go back to the drill-down page where you opened the Report Designer. HTML. Change any of the parameters as necessary to meet your needs. Version 4. Click Report Designer in the toolbar. see Creating a Report Profile on page 246.1 Sourcefire 3D System Administrator Guide 236 .Working with Event Reports Generating Reports from Event Views Chapter 7 2. click Return to Calling Page at the bottom of the Report Designer page.9. 4. For details on the parameters for a report. The settings on the page reflect the parameters that you selected for the search or through the drill-down pages. Select the check boxes next to the output options you want in the report: PDF .

Click OK to confirm that you want to save the current parameters as a report profile. You can view.1 Sourcefire 3D System Administrator Guide 237 . then click the report name on the Reporting page that appears. NFS. who generated it.pdf for PDF reports . the Defense Center hides any previously generated remotely stored reports. Version 4. click Reports in the toolbar.zip for HTML reports (HTML reports are zipped along with the necessary graphics) Finally.Working with Event Reports Managing Generated Reports Chapter 7 6. Note that only Series 2 Defense Centers support remote storage of reports.csv for comma-separated value reports . To configure remote storage. 7. Each report is listed with the report name as defined in the report profile plus the date and time the report was generated. click Remote Storage on the toolbar. see Managing Remote Storage on page 393. If you are using a Series 2 Defense Center. if you change the remote storage location. or delete reports. which indicates whether it has yet to be generated (for example. you can move reports to a remote storage location. You can enable or disable remote storage using the Enable Remote Storage for Reports check box. or whether the generation failed (for example. due to lack of disk space). and SMB storage. the appliance lists the status of each of the reports. The report profile is saved and the report generates in the output formats you selected. If you disable remote storage. For more information. for scheduled tasks). In addition. the appliance provides the disk usage of the storage device. The report appears. for local. the Defense Center hides reports not stored in the new location. The default location for report storage is listed at the top of the page. Managing Generated Reports Requires: IPS or DC/ MDC Manage previously generated reports on the Reporting page. Each report has one of the following file extensions appended to the report name: • • • . and whether it is stored locally or remotely. it has already been generated. download.9. To view the report.

The Report Profiles page appears. In either case. On the toolbar. The Report Profiles page appears. You can view one report at a time. click Reports. see the following topics: • • • • • Viewing Generated Reports on page 238 Downloading Generated Reports on page 238 Deleting Generated Reports on page 239 Moving Reports to a Remote Storage Location on page 239 Running Remote Reports on page 240 Viewing Generated Reports Requires: IPS or DC/ MDC Use the following procedure to view generated reports. the report opens. The Reporting page appears.Working with Event Reports Managing Generated Reports Chapter 7 For information on managing reports. Note that users with Admin access can view all reports generated on the appliance. Version 4. Click the name of the report. For more information. You have two options: • • Enable the check box next to the report you want to view. TIP! You can also save reports locally.9. Select Analysis & Reporting > Report Profiles. 2. 2. On the toolbar. other users can only view reports that they generated themselves. Downloading Generated Reports Requires: IPS or DC/ MDC Access: Any Analyst/ Admin Use the following procedure to download generated reports. 3. see the next section. To download generated reports: 1. Select Analysis & Reporting > Report Profiles. Downloading Generated Reports.1 Sourcefire 3D System Administrator Guide 238 . then click View. To view a generated report: Access: Any Analyst/ Admin 1. The Reporting page appears. click Reports.

1 Sourcefire 3D System Administrator Guide 239 . The Report Profiles page appears.Working with Event Reports Managing Generated Reports Chapter 7 3. 4. TIP! Enable the check box at the top left of the page to delete all reports on the page. see Managing Remote Storage on page 393. The Reporting page appears. Deleting Generated Reports Requires: IPS or DC/ MDC Access: Any Analyst/ Admin Use the following procedure to delete generated reports. click Reports. If you have multiple pages of reports. a second check box appears that you can enable to download all reports on all pages. For information on configuring a remote storage location and enabling remote storage of reports.zip file. click Reports. Select Analysis & Reporting > Report Profiles. then click Download. The Reporting page appears. On the toolbar. a second check box appears that you can enable to delete all reports on all pages. Select Analysis & Reporting > Report Profiles. On the toolbar. Enable the check boxes next to the reports you want to delete. TIP! Enable the check box at the top left of the page to download all reports on the page. Version 4. To move generated reports: Access: Any Analyst/ Admin 1. The reports are downloaded in a single . you cannot move it back. To delete generated reports: 1. 3. Enable the check boxes next to the reports you want to download. you can move locally stored reports to a remote storage location. The reports are deleted. The Report Profiles page appears. If you have multiple pages of reports. Moving Reports to a Remote Storage Location Requires: DC/MDC On Series 2 Defense Centers.9. Follow your browser’s prompts to download the reports. Note that after you move a report to a remote location. Confirm that you want to delete the reports. 2. 2. then click Delete. 4.

TIP! Enable the check box at the top left of the page to move all reports on the page. Click OK. Select Analysis & Reporting > Report Profiles. the logo or image file must exist on both the Defense Center and the managed sensor where you run the report.Working with Event Reports Managing Generated Reports Chapter 7 3. 3. Confirm that you want to move the reports. and you store IPS data on the sensor in addition to sending it automatically to the Defense Center.9. You cannot run remote reports on 3Dx800 or Crossbeam-based software sensors. The Report Designer page appears. 2. Enable the check boxes next to the reports you want to move. You cannot run incident reports remotely on managed 3D Sensors with IPS. Create the report that you want to run on the managed sensor. If you have multiple pages of reports. A prompt appears asking you to confirm that you want to run the report remotely. For example. a second check box appears that you can enable to move all reports on all pages. 4. Version 4. select the sensor where you want to run the report and click Run Remote Report. There are several limitations that you need to keep in mind: • • If you do not store data on the sensor. then the remote report will be empty. From the drop-down list at the bottom of the page. The Report Profiles page appears. if you use your Defense Center to manage a 3D Sensor with IPS. The reports are moved. See Generating Reports from Event Views on page 235 for details. Click Create Report Profile. Running Remote Reports Requires: DC + 3D Sensor If you use a Defense Center to manage your sensors. you can run the report on the data that is resident on the sensor. then click Move. • • To run a remote report: Access: Any Analyst/ Admin 1. The report is run on the sensor that you selected. you have the option of running reports remotely from the Defense Center using the data on the sensors. 5. If your report uses a logo or image file. 4.1 Sourcefire 3D System Administrator Guide 240 .

Reports Sections. Report Information defines the basic nature of the report profile by first giving the report profile a name. inserts a logo. search query. You can view or download the remote report as you would with any other locally generated report. click Reports. such as detection engine. In the toolbar. You can then manually run these reports or schedule them to run automatically (for information about scheduling tasks. For more information. 7. Understanding Report Profiles Requires: IPS or DC/ MDC Report profiles provide the structure for the generated report. When you run the report. listing the report you just generated on the managed sensor. For more information.Working with Event Reports Understanding Report Profiles Chapter 7 6. a new report profile can be created through the use of the Report Designer. and Report Options. see Scheduling Tasks on page 425). and then selecting the report category and type. Note that remote. such as a drill down of events. and provides an option to email the report. The Reporting page appears.1 Sourcefire 3D System Administrator Guide 241 . make sure you select the name of the sensor and click Run Report Remotely. Whether you use a predefined report profile or create your own. see Working with Report Information on page 248. TIP! You can also use report profiles as the basis for remote reports by creating a profile as described in Creating a Report Profile on page 246. Report Sections identifies which sections to include in the report. see Working with Report Options on page 258.is prepended to the name of the report. comma-separated (CSV format). Depending upon your choices. or use as a template for a new report profile by modifying field settings as appropriate and saving the report with the new values. adds a custom footer. all report profiles contain the same three configurable areas: Report Information. See the following sections for more information: • • • • Understanding the Predefined Report Profiles on page 242 Modifying a Predefined Report Profile on page 246 Creating a Report Profile on page 246 Working with Report Information on page 248 Version 4. Note that not all options are available for all categories or types. For more information. Report Options specifies the outputs of the report format (PDF HTML. table view of events. and workflow. Additionally. or the inclusion of an image file. you will have other options to define. or . see Working with Report Sections on page 255.9. You can use a predefined report profile to either generate your report.

As with custom report profiles that you create (see Creating a Report Profile on page 246). save the report with the new values.1 Sourcefire 3D System Administrator Guide 242 .9. You can modify field settings as appropriate.Working with Event Reports Understanding Report Profiles Chapter 7 • • • • • Working with Report Sections on page 255 Working with Report Options on page 258 Using a Report Profile on page 260 Generating a Report using a Report Profile on page 261 Deleting Report Profiles on page 263 Understanding the Predefined Report Profiles Requires: IPS or DC/ MDC A predefined report profile provides you with predefined setting for event reports. and run the report manually or automatically. Version 4. you can use a predefined report profile as a template for an event report.

9. High Priority Events. The following graphic shows the Blocked Events report profile on the Defense Center version of the page. and Host Audit. you must save the report profile with a new name to preserve your new settings. Note that if you modify the default settings.Working with Event Reports Understanding Report Profiles Chapter 7 Predefined reports are provided by the Sourcefire system: Blocked Events. The following tables provide the default settings for each of the predefined report profiles. The Report Options area is not included in these charts. you have created a new report profile.1 Sourcefire 3D System Administrator Guide 243 . Version 4.

Working with Event Reports Understanding Report Profiles Chapter 7 The Blocked Events report profile provides information on blocked intrusion events for all detection engines for the past twenty-four hours.1 Sourcefire 3D System Administrator Guide 244 .9. Default Settings for the Blocked Events Report Profile Field Report Category Report Type Detection Engine Search Query Workflow Setting IPS Intrusion Events All Blocked Events Impact and Priority (on the Defense Center) Destination Port (on the 3D Sensor) Time Add Summary Report Impact Based Event Summary (on the Defense Center) Drill Down of Source and Destination IPS (on the Defense Center) Drill Down of Destination Port (on the 3D Sensor) Drill Down of Events (on the 3D Sensor) Table View of Events Packets (limit 50 pages) Last day. sliding time window Quick Enabled Enabled Enabled Enabled Disabled Disabled The High Priority Events report profile provides information on intrusion events as well as the host criticality of hosts involved in the intrusion events for the past Version 4. This report profile is available on the Defense Center or on a 3D Sensor with IPS.

Working with Event Reports Understanding Report Profiles Chapter 7 twenty-four hours. This report profile is available only on the Defense Center that manages 3D Sensors with RNA. Default Settings for the High Priority Events Report Profile Field Report Category Report Type Detection Engine Search Query Workflow Time Add Summary Report Impact to Criticality Summary Source Destination Drill Down Intrusion Events with Destination Criticality Packets (limit 50 pages) Setting IPS Intrusion Events with Destination Criticality All High Priority Events Events by Impact. Priority. sliding time window Quick Enabled Enabled Enabled Disabled The Host Audit report profile provides operating system details for the past week on systems less than two network hops away from 3D Sensors with RNA. Default Settings for the Host Audit Report Profile Field Report Category Report Type Detection Engine Search Query Setting RNA RNA Hosts All Local Systems Version 4.9. This report profile is available only on a Defense Center that manages 3D Sensors with RNA and IPS.1 Sourcefire 3D System Administrator Guide 245 . and Host Criticality Last day.

and which workflows to examine. save the report profile. Creating a Report Profile Requires: IPS or DC/ MDC You can create the report profile by defining category and type. . Version 4. the criteria for the search. selecting the Intrusion Events with Source Criticality report type does not provide that option. table view of events. and. and saving the report with the new values. queries. Note that all reports contain the option for a summary report and an image file. For more information on how to modify a predefined report profile. and workflows to apply. configure the options in each of three report areas (Report Information. finally. For example. and then specifying which detection engines to search. Working with Report Information on page 248 explains how to set the type of report and how to specify which detection engines. and Report Options). You perform three steps to create the a report profile: first. in the IPS report category. Working with Report Sections on page 255 explains how to specify which the sections to be included in the report. or an image file. second. Not all options are available for all reports. Criticality Table View of Events Packets (limit 50 pages) Setting Operating System Summary Last week.Working with Event Reports Understanding Report Profiles Chapter 7 Default Settings for the Host Audit Report Profile (Continued) Field Workflow Time Add Summary Report Summary of OS Names Summary of OS Versions OS Details with IP NetBIOS. see Editing Report Profiles on page 263. create the report profile in the system. sliding time window summary Enabled Enabled Enabled Disabled Disabled Modifying a Predefined Report Profile Requires: IPS or DC/ MDC You can use a predefined report profile as a template to create a new report profile by modifying the field settings as appropriate. such as a drill down of events. selecting the Intrusion Events report type gives you the option to select which detection engines to search. but not all options are available for all reports.1 Sourcefire 3D System Administrator Guide 246 .9. Report Sections.

1 Sourcefire 3D System Administrator Guide 247 . TIP! You can also reach the Report Designer page from any event view by clicking Report Designer on the toolbar. The following graphic shows the Defense Center version of the page. Click Create Report Profile. 2. and how to use the option which emails the report.9. The Report Profiles page appears. adds a custom . To create a report profile: Access: Any Analyst/ Admin 1.Working with Event Reports Understanding Report Profiles Chapter 7 Working with Report Options on page 258 section explains how to set the output of the report (PDF HTML or comma-separated value (CSV) format). footer or logo. Version 4. 3. Continue with Defining Report Information on page 254. Select Analysis & Reporting > Report Profiles. The Report Designer page appears.

Depending upon your choices. The following graphic is an example of the Report Information section. periods. such as detection engine. search query. and then selecting the report category and type. Note that not all options are available for all categories or types.9. parentheses. and spaces. The Report Name can be any name using 1-80 alphanumeric characters. dashes.Working with Event Reports Working with Report Information Chapter 7 Working with Report Information Requires: IPS or DC/ MDC You define the basic nature of the report profile by first giving the report profile a name. Version 4.1 Sourcefire 3D System Administrator Guide 248 . and workflow. you will have other options to define.

For example. you can create a report which searches selected detection engines for RNA client applications. RUA are using a Defense Center with an RUA host license and you want to search one or more detection engines to examine the RUA Events and users. For information on IPS Report Type options. high impact or high priority events. RNA services. Use this option to select a workflow on one or more detection engines to search for blocked events. RNA are using a Defense Center with an RNA host license and you want to report on host attributes. The Report Type is a subset of the Report Category and provides a greater level of detail to the report. you can create a report which searches for IP-specific high impact intrusion events on a specified detection engine. Report Categories Select. IPS If you.. Use this option to search hosts for blocked or high priority events. For more information on RNA Report Type options. are using a Defense Center and you want to report on the health of your sensors. report types are limited and self-explanatory.. have an IPS license and you want to report on intrusion events with or without source or destination criticality. For example. RNA events. For example. Select from the Report Categories table . or scan results. see RNA Category Report Types on page 252. RNA client applications. see IPS Category Report Types on page 251. you can create a report which searches a selected detection engine for RNA compliance events. In many cases. See Using Report Types on page 250 for more information. intrusion events with source criticality. or exploits that target client/server issues.. RNA hosts. Options vary depending upon Report Type. Compliance Health Monitoring Audit Log Version 4.9. vulnerabilities. remediation status. compliance events. public or private addresses only. hosts with services. want to report on audit log events.Working with Event Reports Working with Report Information Chapter 7 The Report Category defines which system feature is examined in the report. common concerns. or the SEU import log. you can create a report which searches selected detection engines for RUA events.. However IPS and RNA report types options are extensive and provide detailed options for defining your report profile. such as the Compliance or Audit Log report categories. are using a Defense Center with an RNA host license and you want to report on white list violations. or white list events.For example. and generate a report which can include sections with a Table View of Events and Users.1 Sourcefire 3D System Administrator Guide 249 . or various services.

and health monitoring. The Workflow allows you to select which workflow to examine. white list. See the following sections for more information: • • Using Report Types on page 250 Defining Report Information on page 254 Using Report Types Requires: IPS or DC/ MDC The Report Type is a subset of the Report Category and provides a greater level of detail to the report. client applications.1 Sourcefire 3D System Administrator Guide 250 . and can include such options as Network Services by Count or Host Violations. and can include a list of exploits (such as Sasser Worm Search or non-standard service attempts) or areas of concern such as IRC Events or Kerberos Client/Server issues. have limited report types and are self-explanatory. and Search Query. and IP-Specific or Impact and Priority. The Time option allows you to define the period of time for which the report is generated. The Search Query identifies the search criteria for the report.9. Click in the current time field to open a pop-up window from which you can select a static. or compliance events. Options vary depending upon which options you selected for Report Type. However. Options for the report type vary depending upon which Report Category is selected. Some report categories. expanding. See the following sections for more information: • • IPS Category Report Types on page 251 RNA Category Report Types on page 252 Version 4.Working with Event Reports Working with Report Information Chapter 7 The Detection Engine allows you to select which detection engines are to be searched for the report. or when searching the network for RNA hosts. such a intrusion. Detection Engine. host attributes. the report types available to the IPS and RNA report categories are extensive and provide detailed options for defining your report profile. see Setting Event Time Constraints in the Analyst Guide. Options vary depending upon Report Type. RNA. This option is available when searching for events. or sliding time frame. For more information. such as the Compliance or Audit Log report categories.

Working with Event Reports Working with Report Information

Chapter 7

IPS Category Report Types
You can choose from the following IPS Category Report Types
:

IPS Category Report Types Select... Intrusion Events To... search one or more detection engines using user-specified search queries and workflows to generate a report which can include sections with a drill down of the destination port and events, a table view of events, and the packets. Search queries include: Blocked Events, Bootstrap Client/Server, Common Concerns, DNS Service, DirectX Service, FTP Service, Finger Service, High Impact Events, High Priority Events, IRC Events, Impact1/Not Dropped Events, Kerberos Client/Server, LDAP Services, Mail Services, Oracle Service, Private Addresses Only, Public Addresses Only, RPC Services, and Reserved Port TCP Scan. Workflows include: Destination Port, Event-Specific, Events by Priority and Classification, Events to Destinations, IP-Specific, Impact and Priority, Impact and Source, Impact to Destination, Source Port, and Source and Destination. Intrusion Events with Source Criticality search using the Blocked Events or High Priority events search queries to generate a report on the Intrusion Events with Source Criticality default workflow which can include sections on Intrusion Events with Source Criticality, and the packets. search using the Blocked Events or High Priority Events search queries on your choice of three workflows: Events by Impact, Priority, and Host Criticality, which can include sections on Impact to Criticality Summary, Source Destination Drill Down, Intrusion Events with Destination Criticality, and the packets. Events with Destination, Impact, and Host Criticality, which can include sections on Current Events Monitor, Intrusion Events with Destination Criticality, and the packets. Intrusion Events with Destination Criticality default workflow, which can include sections on Intrusion Events with Destination Criticality, and the packets. SEU Import Log generate a report on the SEU Detail View workflow.

Intrusion Events with Destination Criticality

Version 4.9.1

Sourcefire 3D System Administrator Guide

251

Working with Event Reports Working with Report Information

Chapter 7

RNA Category Report Types
You can choose from the following RNA Category Report Types: RNA Category Report Types Select... Host Attributes To... search one or more detection engines to examine the Attributes workflow, and generate a report which can include sections with a table view of host attributes and the packets. search one or more detection engines to examine the Client Application Summaries or RNA Client Applications workflows, and generate a report which can include sections with a table view of client applications and the packets. examine the Vulnerabilities workflow and generate a report which can include sections with a table view of vulnerabilities, vulnerabilities on the network, and the packets. search using the Blocked Events or High Priority events search queries on the Intrusion Events with Source Criticality default workflow, and generate a report which can include sections on Intrusion Events with Source Criticality, and the packets. examine the Hosts with Services Default Workflow or the Service and Host Details, and generate a report which can include sections on Hosts with Services and the hosts. search one or more detection engines to examine the operating system summary or RNA hosts for local, remote, unidentified, or unknown systems, and generate a report which can include sections with a Summary of Operating System Names, Summary of Operating System Versions, Operating System Details with IP NetBIOS Criticality, Table View of Hosts, and Hosts. , generate a report on the Scan Results workflow. search one or more detection engines using the NetSky.S Worm Search, New Events, Sasser Worm Search, Subseven Trojan Search, Timeout Events, and Update Events, and generate a report which can include sections with a Table View of Events, and Hosts.

RNA Client Applications

Vulnerabilities

Intrusion Events with Source Criticality

Host with Services

RNA Hosts

Scan Results RNA Events

Version 4.9.1

Sourcefire 3D System Administrator Guide

252

Working with Event Reports Working with Report Information

Chapter 7

RNA Category Report Types (Continued) Select... RNA Services To... search one or more detection engines for non-standard service events (such as non-standard HTML, non-standard mail, non-standard SSH) in Network Services by Count, Network Services by Hit, and RNA Services workflows, and to generate a report which can include sections with Active Services, Service Application Activity, Service Version Audit, Service by Host, and Hosts. search using the Blocked Events, Events to High Criticality Hosts, or High Priority Events search queries, and generate a report on your choice of three workflows: Events by Impact, Priority, and Host Criticality, which can include sections on Impact to Criticality Summary, Source Destination Drill Down, Intrusion Events with Destination Criticality, and the packets. Events with Destination, Impact, and Host Criticality, which can include sections on Current Events Monitor, Intrusion Events with Destination Criticality, and the packets. Intrusion Events with Destination Criticality default workflow, which can include sections on Intrusion Events with Destination Criticality, and the packets. Flow Data search one or more detection engines using user-specified search queries and workflows, and generate a report which can include sections with the Top Ten workflows, Table View of Flow Summary Data, Table View of Flow Data drill down of the destination port and events, a table view of events, and the packets. Search queries include: Possible Database Access, Standard HTTP Standard , Mail, Standard SSL, and Unauthorized SMTP . Workflows include: Flow Summaries, Flows by Detection Engine, Flows by Initiator, Flows by Port, Flows by Responder, Flows by Service, Flows Over Time, RNA Flows, Traffic by Detection Engine, Traffic by Initiator, Traffic by Port, Traffic by Responder, Traffic by Service, Traffic Over Time, Unique Initiators by Responder, and Unique Responders by Initiator.

Intrusion Events with Destination Criticality

Version 4.9.1

Sourcefire 3D System Administrator Guide

253

Working with Event Reports Working with Report Information

Chapter 7

Defining Report Information
Requires: IPS or DC/ MDC Access: Any Analyst/ Admin After you have determined which options you need for your report, use the following procedure to define the report information options. To define the Report Information: 1. From the Report Category drop-down list, select the report category for which you want to create a report.

You can choose from: • • • • • • IPS (with an IPS license) RNA (on a Defense Center with an RNA host license) RUA (on a Defense Center with an RUA host license) Compliance (on a Defense Center with an RNA host license) Health Monitoring (on a Defense Center) Audit Log

2. From the Report Type drop-down list, select the type of report you want to create. 3. Optionally, if the report type you selected includes the Detection Engine option, select a specific Detection Engine on which to report. 4. Requires: DC Optionally, if you are reporting on health events, select a specific sensor or sensor group from the Sensor drop-down list. 5. From the Search Query drop-down list, either use the Use Current Query option (which retains any query parameters you specified on the search page or event page) or select one of the existing search queries. Note that if you did not previously specify a search query, the Use Current Query option places no constraints on the events. 6. From the Workflows list, select the workflow you want to use to build the report. For information on workflows, see Understanding and Using Workflows in the Analyst Guide.

Version 4.9.1

Sourcefire 3D System Administrator Guide

254

Working with Event Reports Working with Report Sections

Chapter 7

7.

Specify the time range for the report. Depending on your default time window, the time range matches either the time window for the event view you are using to building the report profile, or the global time window. You can change time range by clicking it and using the Date/Time pop-up window to select a new time range. For more information, see Setting Event Time Constraints in the Analyst Guide.

8. Continue with Defining the Report Sections on page 258. IMPORTANT! For report profiles that you plan to use multiple times, such as in scheduled tasks, Sourcefire strongly recommends that you use a sliding time range. If you create a report profile with a static time range, the appliance will generate a report using the same time range (and therefore the same events) every time you use the report profile.

Working with Report Sections
Requires: IPS or DC/ MDC The Report Sections area is populated based on the workflow you selected. Select the check box for each report section you want to include in the report. Reports can include up to 10,000 records for each report section you select. See the following sections for more information: • • • Using Summary Reports on page 255 Including an Image File on page 257 Defining the Report Sections on page 258

Using Summary Reports
Requires: IPS or DC/ MDC Depending on the components you are licensed to use in your Sourcefire 3D System deployment, you can include summary reports for intrusion events and RNA events. You can append these summary reports to the beginning of any report by selecting the appropriate radio button in the report profile. Intrusion event reports require the IPS component. If your deployment includes IPS, you can include either a Quick Summary or a Detail Summary report in your report profile definition.

Version 4.9.1

Sourcefire 3D System Administrator Guide

255

Working with Event Reports Working with Report Sections

Chapter 7

The Comparison of Quick Summary and Detail Summary Reports table shows which information is included in the reports
.

Comparison of Quick Summary and Detail Summary Reports Report Information Pie chart showing the percentage of events in each event type (which maps to the rule category for the rule that generated the event) List of the 10 most active and 10 least active events Graph showing the number of events over time Pie charts showing the percentage of events by protocol (for example, TCP , UDP or ICMP) and event classification (which maps to the value for the , classtype keyword in the rule that generated the event) Tables listing the 50 most active and least active events Tables listing the 50 most active source and destination ports Tables listing the 25 most active source and destination hosts and host combinations. Tables listing the 25 most active source and destination hosts as well as the 25 most active source and host combinations Tables listing the most active events for each of the 25 most active destination hosts Tables listing the most active events for the 25 most active source and destination host combinations Quick Summary X X X X Detail Summary X X X X

X X X

X X X X X X

IMPORTANT! On the Defense Center, the report includes summary information for all the managed 3D Sensors with IPS that you include in the report. RNA-related event reports require the RNA component. If your deployment includes 3D Sensors with RNA and a Defense Center that manages the sensors,

Version 4.9.1

Sourcefire 3D System Administrator Guide

256

Working with Event Reports Working with Report Sections

Chapter 7

you can add the RNA Summary to RNA event, host, client application, service, and flow data reports. The RNA Summary includes: • RNA event statistics including total number of events, events in the last day and hour, total services, total hosts, total routers, total bridges, and host limit usage a list of events divided by event type with counts for the last hour and total number within the report range pie charts showing the percentage of events by protocol (for example, TCP , UDP or ICMP), service, and operating system ,

• •

Including an Image File
Requires: IPS or DC/ MDC You can add an image to your report which will be displayed after the summary report and before the drill down or table views. This can be useful for providing information best displayed in a visual, non-graphical format, or simply as a break between sections. You can use JPEG, PNG, and TIFF files as image files, but only JPEG and PNG graphics are supported in most browsers.

Version 4.9.1

Sourcefire 3D System Administrator Guide

257

Working with Event Reports Working with Report Options

Chapter 7

Defining the Report Sections
Requires: IPS or DC/ MDC Access: Any Analyst/ Admin After you have determined which options you need for your report, use the following procedure to define the report section options. To define the Report Sections: 1. If a summary is available for the report type you selected, specify whether you want to include it as part of your report.

To include a summary with intrusion event-based reports, select quick or detailed. For a full description of the information provided in Quick and Detailed summaries, see Using Summary Reports on page 255. On a Defense Center with an RNA host license, to include a summary with an RNA-based report, select summary. For a full description of the information provided in the RNA summary, see Using Summary Reports on page 255. To exclude the summary, select none, which is the default.

2. If you want to include an image in the report, type the path to the image in the Include Image File text box, or navigate to a JPEG, PNG, or TIFF file. 3. Select the check boxes next to the sections of the workflow you want to include in the report. The options in this section depend on the workflow you selected in step 6. 4. Continue with Working with Report Options on page 258. TIP! Note that if you select a table view of events, the report is limited to 10,000 records as noted in step 6, regardless of the number of events.

Working with Report Options
Requires: IPS or DC/ MDC Report Options define the look of the report, and provide the option to email the report You can generate a report in PDF HTML or comma-separated value (CSV) format. , You can also generate the same report in multiple formats. Note that graphics are not available in the CSV format.

Version 4.9.1

Sourcefire 3D System Administrator Guide

258

Working with Event Reports Working with Report Options

Chapter 7

You can include a logo on your report. In PDF formats, the logo is included on every page. In HTML formats, the logo is included at the top of the report. You can add a description which will be included on the front page summary of the report. Access: Any Analyst/ Admin To define the report options: 1. Select the check boxes next to one or more output options for your report: PDF HTML, or CSV. ,

2. Optionally, for PDF and HTML reports, select a logo from the list of image files that were previously added to the system. See Including an Image File on page 257 for information about how to make more logos available to the report designer. 3. Optionally, for PDF and HTML reports, type a description in the Description field. You can use alphanumeric characters and spaces. The description appears in the report header. 4. Optionally, for PDF reports, type the text you want to include as the footer in the Custom Footer field. You can use 1 - 80 alphanumeric characters and spaces. 5. Optionally, you can specify that reports are automatically emailed after they are generated. To email a report, type one or more email addresses in a comma-separated list in the Email to field. IMPORTANT! You must make sure that the mail host is identified: Click Not available. You must set up your mail relay host. The System Policy page appears. Click Edit in the row for the system policy you want to modify. Click Email Notification. Type the name of your mail server in the Mail Relay Host field and click Save. Click Apply in the row for the system policy you changed and apply it to the appliance. The report is emailed from host_name@domain_name, where host_name is the host name of the appliance and domain_name is the name of the domain where you deployed the appliance.

Version 4.9.1

Sourcefire 3D System Administrator Guide

259

Working with Event Reports Using a Report Profile

Chapter 7

6. You have the following options: • To save the report profile, click Save Report Profile. When prompted, follow the instructions for your browser to save the report profile. The report profile is saved with the name you specified in the Report Name field. • To generate the report and save the report profile, click Generate Report. When prompted, follow the instructions for your browser to generate the report and save the report profile. • To see a PDF preview of your report, click Preview Report. When prompted, follow the instructions for your browser to display a PDF version of the report in the browser window. • On a Defense Center, to generate the report remotely, select the sensor where you want to run the report and click Run Remote Report. When prompted, follow the instructions for your browser to generate the report and save the report profile. IMPORTANT! The PDF HTML, and CSV selections for Output Options apply to , generated reports, not to report previews. When you click Preview Report, you see a PDF version of the report.

Using a Report Profile
Requires: IPS or DC/ MDC You can use report profiles to generate reports that contain the information that is important to you and your evaluation of the events generated for your network. You can use an predefined or existing report profile as a template for a new report profile. For information on editing a report profile, see Editing Report Profiles on page 263. If you want to generate a report for a specific set of events or a specific time period, populate the event view with the events you want to see in your report before opening the report designer. For details on using the event view, see the following sections: • • • • • • Viewing RNA Network Discovery and Host Input Events in the Analyst Guide Viewing Hosts in the Analyst Guide Viewing Services in the Analyst Guide Viewing Client Applications in the Analyst Guide Working with Flow Data and Traffic Profiles in the Analyst Guide Working with Intrusion Events in the Analyst Guide

Version 4.9.1

Sourcefire 3D System Administrator Guide

260

Working with Event Reports Using a Report Profile

Chapter 7

See the following sections for more information: • • • Generating a Report using a Report Profile on page 261 Editing Report Profiles on page 263 Deleting Report Profiles on page 263

Generating a Report using a Report Profile
Requires: IPS or DC/ MDC Access: Any Analyst/ Admin You can use report profiles to generate reports that contain the information that is important to you and your evaluation of the events generated for your network. To generate a report using a report profile: 1. Select Analysis & Reporting > Report Profiles. The Report Profiles page appears.

Version 4.9.1

Sourcefire 3D System Administrator Guide

261

Working with Event Reports Using a Report Profile

Chapter 7

2. Click the name of the report profile you want to use. The Report Designer page loads the parameters defined for that selected report.

3. If necessary, click the time range to change it to include the events you want in your report. For more information, see Setting Event Time Constraints in the Analyst Guide. 4. Click Generate Report. The system generates the report. 5. Click Reports in the toolbar to display the Reporting page. The Reporting page appears, listing the report that you generated as well as any other previously generated reports. For information on managing generated reports, see Managing Generated Reports on page 237.

Version 4.9.1

Sourcefire 3D System Administrator Guide

262

remember to change the name of the report profile in the Report Name field. modifying the field settings as appropriate. Click Save Report Profile. and saving the report with the new values. Make changes to the report areas as needed. Select Analysis & Reporting > Report Profiles. Access: Any Analyst/ Admin To edit a report profile: 1. Click Delete next to the profile that you want to delete. Use the following procedure to edit a report profile. The Report Profiles page appears. 3. When prompted. Version 4. You can also edit a report profile to make changes to the resulting report.Working with Event Reports Using a Report Profile Chapter 7 Editing Report Profiles Requires: IPS or DC/ MDC You can create a new report profile by using a predefined or existing report profile as a template for a new report profile. The Report Designer page appears and contains the current settings for the report profile.1 Sourcefire 3D System Administrator Guide 263 .9. The report profile is saved with the name you specified in the Report Name field. To delete a report profile: 1. See the following sections for information: • • • Working with Report Information on page 248 Working with Report Sections on page 255 Working with Report Options on page 258 IMPORTANT! If you are creating a new report profile from a predefined or existing report profile. The Report Profiles page appears. Click Edit next to the profile that you want to delete. The report profile is deleted. follow the instructions for your browser to save the report profile. 2. Select Analysis & Reporting > Report Profiles. Deleting Report Profiles Requires: IPS or DC/ MDC Access: Any Analyst/ Admin Use the following procedure to delete a report profile. 2. 4.

such as a Lightweight Directory Version 4. rather than through the internal database. For more information. There are two kinds of authentication: internal and external. if the user is not found locally.Managing Users Chapter 8 Administrator Guide If your user account has Administrator access. you can also set up user authentication via an external authentication server. If the account uses external authentication. the authentication process checks the local database for this list. you can manage the user accounts that can access the web interface on your Defense Center or 3D Sensor. the appliance looks for a match for the user name and password in the local list of users. it queries an external server.9. the process checks the local database to see if the user exists there and. This process is called authentication. see the following sections: • • • Understanding Sourcefire User Authentication on page 264 Managing Authentication Objects on page 269 Managing User Accounts on page 299 Understanding Sourcefire User Authentication Requires: DC/MDC or 3D Sensor When a user logs into the web interface. On the Defense Center.1 Sourcefire 3D System Administrator Guide 264 . If the user’s account uses internal authentication.

for a list of users. Version 4.9. For users with either internal or external authentication.Managing Users Understanding Sourcefire User Authentication Chapter 8 Access Protocol (LDAP) directory server or a Remote Authentication Dial In User Service (RADIUS) authentication server. you can control user permissions. unless you change the user permissions manually.1 Sourcefire 3D System Administrator Guide 265 . Users with external authentication receive the permissions either for the group or access list they belong to. or based on the default user access role you set in the server authentication object or in a system policy on the managing Defense Center.

If you want to use external authentication. You can then enable that object in a system policy on the managing Defense Center and apply the policy to an appliance to enable authentication. The authentication object contains your settings for connecting to and retrieving user data from that server. Internal authentication occurs when the username and password are verified against records in the internal Sourcefire 3D System database. Understanding External Authentication Requires: DC External authentication occurs when the Defense Center or managed sensor retrieves user credentials from an external repository.1 Sourcefire 3D System Administrator Guide 266 . such as an LDAP directory server or RADIUS authentication server. LDAP authentication and RADIUS authentication are types of external authentication. the web interface checks each authentication server to see if that user is listed. IMPORTANT! Note that an internally authenticated user is converted to external authentication if you enable external authentication. the Sourcefire 3D System uses internal authentication to check user credentials when a user logs in. in the order the servers are listed in the system policy. If you do not enable external authentication when you create a user.Managing Users Understanding Sourcefire User Authentication Chapter 8 For more information. you cannot revert to internal authentication for that user. see the following sections: • • • Understanding Internal Authentication on page 266 Understanding External Authentication on page 266 Understanding User Privileges on page 267 Understanding Internal Authentication Requires: DC/MDC or 3D Sensor By default.Note that you can only use one form of external authentication for an appliance. When any externally authenticated user logs in. you must configure an authentication object for each external authentication server where you want to request user information. Version 4. and the user logs in using the password stored for that user on the external server. the user credentials are managed in the internal database.9. you set the access settings when you create the user and you do not need to set default settings. Because you manually create each internally authenticated user. the same username exists for the user on the external server. Once an internally authenticated user converts to an externally authenticated user.

You can grant Intrusion Event Analyst and RNA Event Analyst access privileges for analysts and reserve the Administrator role for the network administrator managing the Sourcefire 3D System. You can then import the policy and object on another Defense Center. For more information on specific types of external authentication. If you configured management of access rights through LDAP groups. Intrusion Agents. but you cannot control the authentication object from the sensor’s web interface. TIP! You can use the Import/Export feature to export system policies. the user has only the rights granted by default. the authentication objects are exported with the policy. They receive the Version 4. After an externally authenticated user logs in for the first time. you set the access rights when you create them. If you do not modify the user’s rights. the access rights for users are based on their membership in LDAP groups. external authentication is also disabled. you can add or remove access rights for that user on the User Management page.9.Managing Users Understanding Sourcefire User Authentication Chapter 8 When you create a user. You can push a system policy to a managed 3D Sensor to enable external authentication on that sensor. Do not import policies with authentication objects onto 3D Sensors.1 Sourcefire 3D System Administrator Guide 267 . For example. disable it in the system policy on the managing Defense Center and re-apply the policy to the sensor. 3Dx800 sensors. or Crossbeambased software sensors. see the following sections: • • Understanding LDAP Authentication on page 269 Understanding RADIUS Authentication on page 287 Understanding User Privileges The Sourcefire 3D System lets you allocate user privileges based on the user’s role. an analyst typically needs access to event data to analyze the security of monitored networks. Because you create internally authenticated users manually. The only configuration of external authentication on the sensor occurs when you select the type of authentication for a new user. you set a default access role for all users who are externally authenticated. you can specify whether that user is internally or externally authenticated. If you apply a local system policy (created on the sensor) to the sensor itself. When you export a policy with external authentication enabled. In the system policy on the Defense Center. but might never require access to administrative functions for the Sourcefire 3D System itself. IMPORTANT! Sourcefire does not support external authentication for RNA Software for Red Hat Linux. If you want to disable external authentication on a managed 3D Sensor.

1 Sourcefire 3D System Administrator Guide 268 . listed in order of precedence. The Sourcefire 3D System supports the following user roles. If you configure group access. they receive the default user access rights configured in the authentication object for the LDAP server. and delete intrusion events and compliance and RUA events. the user receives the role that has the highest level of access. Note that on the Defense Center you cannot select Restricted Event Analyst as the default user role in the system policy. Intrusion Event Analysts (Read Only) have all the same rights as Intrusion Event Analysts.Managing Users Understanding Sourcefire User Authentication Chapter 8 default access rights for the group that they belong to that has the highest level of access. unless one or more of those roles are mutually incompatible. RNA analysts can also generate reports and view (but not delete or modify) health events. Restricted analysts can also be assigned the Policy & Response Administrator or Maintenance User roles. the user receives that role. but cannot be assigned the Intrusion Event Analyst or RNA Event Analyst roles. hosts. Restricted Event Analysts have the combined privileges of Intrusion Event Analysts and RNA Event Analysts. services. analyze. those settings override the default access setting in the system policy. If a user is on the lists for two mutually incompatible roles. RNA Event Analysts (Read Only) have all the same rights as RNA Event Analysts. except that they cannot delete events. Users with the Administrator role also have Intrusion Event Analyst. • • • • • Version 4. and delete network change events. If the user does not belong to any lists and you have configured a default access role in the authentication object. Policy & Response (P&R) Administrator. manage user accounts.9. if you assign a user to specific user role lists in a RADIUS authentication object. those settings override the default access setting in the system policy. Intrusion Event Analysts can view. but you can modify a user’s settings via the User Management page to grant this level of access. They can also create incidents. vulnerabilities. client applications. review. the user receives all assigned roles. compliance events. generate reports. and view (but not delete or modify) health events. and Maintenance access rights. depending on the features you have licensed: • Administrators can set up the appliance’s network configuration. If they do not belong to any groups and you have configured group access. host attributes. but users are limited to subsets of that data. RNA Event Analysts can view. If you configure default access in the authentication object. configure system policies and system settings. analyze. RNA Event Analyst. and RUA events. Similarly. except that they cannot delete events.

policies. Creating LDAP Authentication Objects Requires: DC You can create LDAP authentication objects to provide user authentication services for an appliance. rather than having to change them on the local appliances as well as on any other application that uses them. you can configure shell access authentication. and responses. you define settings that let you connect to an authentication server. containing connection settings and authentication filter settings for those servers. Multiple applications can then access those credentials and the information used to describe them.9.Managing Users Managing Authentication Objects Chapter 8 • • Policy & Response Administrators can manage intrusion rules. You can create. Managing Authentication Objects Requires: DC Authentication objects are server profiles for external authentication servers.1 Sourcefire 3D System Administrator Guide 269 . in a centralized location. Note that maintenance administrators do not have access to the functions in the Policy & Response menu and can only access the dashboard from the Analysis & Reporting menu. host statistics. and responses. directory on your network that organizes objects. and system logs) and maintenance functions (including task scheduling and backing up the system). allows you to set up a . you can change them in one place. If you ever need to change a user's credentials. When you create an authentication object. manage. You also select the directory context and search criteria you want to use to retrieve user data from the server. such as user credentials. Optionally. See the following sections for details on these tasks: • • • • • • • • Understanding LDAP Authentication on page 269 Creating LDAP Authentication Objects on page 269 LDAP Authentication Object Examples on page 281 Editing LDAP Authentication Objects on page 286 Creating RADIUS Authentication Objects on page 287 RADIUS Authentication Object Examples on page 295 Editing RADIUS Authentication Objects on page 298 Deleting Authentication Objects on page 298 Understanding LDAP Authentication LDAP or the Lightweight Directory Access Protocol. performance data. Version 4. Maintenance Administrators can access monitoring functions (including health monitoring. policies. as well as compliance rules. and delete authentication objects on the Defense Center.

see Configuring LDAP Authentication Settings on page 271.Managing Users Managing Authentication Objects Chapter 8 Note that to create an authentication object.9. 2. you first specify the primary and backup server and server port where you want the local appliance (3D Sensor or Defense Center) to connect for authentication. For more information. Configure authentication settings to build a search request that retrieves the users you want to authenticate. configure authentication settings for shell access. Specify a user name template to format the usernames that users enter on login. the port resets to the default value. Click Create Authentication Object. For more information.1 Sourcefire 3D System Administrator Guide 270 . For more information. Test your configuration by entering the name and password for a user who can successfully authenticate. Identifying the LDAP Authentication Server Requires: DC When you create an authentication object. 5. 8. see Configuring Attribute Mapping on page 274. see Testing User Authentication on page 280. the port uses the default of 636. The Login Authentication page appears. Your changes are saved. you need TCP/IP access from your local appliance to the authentication server where you want to connect. configure LDAP groups to use as the basis for default access role assignments. The Create Authentication Object page appears. Optionally. For more information. see Identifying the LDAP Authentication Server on page 270. For more information. Identify the authentication server where you want to retrieve user data for external authentication. see Configuring Access Settings by Group on page 275. see Configuring Authentication Profiles on page 329 and Applying a System Policy on page 324. 4. If you select SSL encryption. 7. Optionally. Note that if you change the encryption method after specifying the port. Remember that you have to apply a system policy with the object enabled to an appliance before the authentication changes take place on that appliance. 3. To create an authentication object: Access: Admin 1. For none or TLS. For more information. Select Operations > Configuration > Login Authentication. Version 4. 6. see Configuring Administrative Shell Access on page 278. specify the appropriate attributes for your server. For more information. the port uses the default value of 389. If you are using a Microsoft Active Directory server or if your LDAP server uses a UI access attribute or a shell access attribute other than uid.

Type the IP address or host name for the primary server where you want to obtain authentication data in the Primary Server Host Name/IP Address field. modify the port used by the primary authentication server in the Backup Server Port field. If. If LDAP is running on the port of the primary LDAP server and for some reason refuses to service the request (due to misconfiguration or other issues). Optionally. type the IP address or host name for the backup server where you want to obtain authentication data in the Backup Server Host Name/IP Address field. Optionally. 6. In addition. the primary server has LDAP disabled. 4. the failover to the backup server does not occur. the appliance then queries the backup server. however. 3. IMPORTANT! If you are using a certificate to connect via TLS or SSL. 7. 2.Managing Users Managing Authentication Objects Chapter 8 To identify an LDAP authentication server: Access: Admin 1. modify the port used by the primary authentication server in the Primary Server Port field. If the number of seconds indicated in the Timeout field (or the timeout on the directory server) elapses without a response from the primary authentication server. you can set a timeout for the connection attempt to the primary server.9. Continue with Configuring LDAP Authentication Settings.1 Sourcefire 3D System Administrator Guide 271 . IPv6 addresses are not supported. for example. Type a name and description for the authentication server in the Name and Description fields. Optionally. Configuring LDAP Authentication Settings Requires: DC If you specify a backup authentication server. Version 4. the appliance would query the backup server. 5. the host name in the certificate must match the host name used in this field. Select LDAP from the Authentication Method drop-down list.

you can use the address specification syntax documented in the Internet RFC 822 (Standard for the Format of ARPA Internet Text Messages) specification when referencing a user name that contains a domain. For example. For example. Note that when you set up an authentication object to connect to a Microsoft Active Directory Server.dc=com.Managing Users Managing Authentication Objects Chapter 8 To allow an appliance to connect to the LDAP server. that the local appliance should search by providing a base distinguished name. If one of the objects has a matching username and password. and hyphens (-) but otherwise only alphanumeric characters are supported. Note that if you are using a certificate to authenticate when connecting via TLS or SSL. if you enter 10. to filter for only users with a common name starting with F use the .example.1 Sourcefire 3D System Administrator Guide 272 .250 as the server and computer1. To test your base filter more specifically by entering a test username and password. For example. the name of the LDAP server in the certificate must match the name that you use to connect. the connection fails.com rather than the equivalent user distinguished name of cn=JoeSmith. Version 4.com causes the connection to succeed. or base DN. the Security organization of the Example company might have a base DN of ou=security. it needs a starting point for that search. you need to select the encryption method for the connection. You can choose no encryption.ou=security.dc=com when using Microsoft Active Directory Server. If your LDAP Server uses a Pluggable Authentication Module (PAM) login attribute of uid. Remember that the distinguished name for the user you specify must be unique to the directory information tree for the directory server. When the local appliance searches the LDAP directory server to retrieve user information on the authentication server. the user login request is authenticated. When you save the authentication object. you must supply user credentials for a user with appropriate rights to the authentication objects you want to retrieve.9.dc=example. LDAP usernames can include underscores (_). or Secure Sockets Layer (SSL) encryption. filter (cn=F*). For example. the local appliance checks the uid attribute value for each object in the directory tree indicated by the base DN you set. you might type JoeSmith@security. periods (. You can also add a base filter that sets a specific value for a specific attribute. Examples of syntax are provided throughout this procedure. For the authentication method specific parameters. the base DN will have a basic structure indicating the company domain and operational unit. The base filter focuses your search by only retrieving objects in the base DN that have the attribute value set in the filter.example. To allow the local appliance to access the user objects. Typically.10. RFC 3377 . You can specify the namespace. Changing the name of the server in the authentication profile to computer1. Enclose the base filter in parentheses. see Testing User Authentication on page 280. or directory tree.example. to refer to a user object.10. dc=example. you can use the LDAP naming standards and filter and attribute syntax defined in the RFCs listed in the Lightweight Directory Access Protocol (v3): Technical Specification.com in the certificate.). the local appliance queries using the base filter to test it and indicates whether or not the filter appears to be correct. Transport Layer Security (TLS).

For none or TLS. Type the number of seconds that should elapse before rolling over to the backup connection in the Timeout field. you would enter %s@security.9. you reset the port to the default value for that method. To configure the authentication method for a server: Access: Admin 1. To connect using Transport Layer Security (TLS). IMPORTANT! Note that if you change the encryption method after specifying a port. Optionally. the port uses the default value of 389. Type the base distinguished name for the LDAP directory you want to access in the Base DN field. A message appears. to authenticate names in the Security organization at the Example company. select TLS.1 Sourcefire 3D System Administrator Guide 273 .com. When a user enters a user name into the login page. type ou=security. If you select SSL encryption. select None.dc=example.dc=com. 2.example. the port uses the default of 636. by mapping the string conversion character (%s) to the value of the shell access attribute for the user. 3. indicating a successful certificate upload.Managing Users Managing Authentication Objects Chapter 8 Selecting a user name template lets you indicate how user names entered on login should be formatted. select SSL. the name is substituted for the string conversion character and the resulting distinguished name is used to search for the user credentials. click Browse to browse to the location of a valid TLS or SSL certificate or type the path to the certificate in the SSL Certificate Upload Path field. 4. to set a user name template for the Security organization of the Example company. To connect without encryption. The user name template is the format for the distinguished name used for authentication. if you selected TLS or SSL encryption and you want to use a certificate to authenticate. Select one of the following encryption modes: • • • To connect using Secure Sockets Layer (SSL). Version 4. For example. For example.

to retrieve only users in the New York office. a comparison operator.ou=security. 8. in the Base Filter field. You can use any attribute. you can map a different attribute for the local appliance to search. you do not need to specify a UI access attribute. 6. have no spaces and no periods in them.1 Sourcefire 3D System Administrator Guide 274 . you would type uid=NetworkAdmin. and do not begin with a numeral. Re-type the password in the Confirm Password field. If your LDAP server uses uid. you would type uid=%s. if the value of the attribute is a valid user name for either the Sourcefire 3D System web interface or for shell access. 9. and the attribute value you want to use as a filter. when a user logs in. Type the user distinguished name.example.dc=com in the User Name Template field.dc=example. to authenticate all users who work in the Security organization of our example company by connecting to an OpenLDAP server where the shell access attribute is uid. if the user objects in a directory tree have a physicalDeliveryOfficeName attribute and users in the New York office have an attribute value of NewYork for that attribute. If the shell access attribute for a server is something other than uid. type the attribute type. enclosed in parentheses. 7.Managing Users Managing Authentication Objects Chapter 8 5. with the string conversion character (%s) in place of the shell access attribute value. Valid user names are unique. Version 4. the local appliance (3D Sensor or Defense Center) checks the value of the uid attribute for each user record on the LDAP Server to see if it matches the user name. For example. Configuring Attribute Mapping Requires: DC If your LDAP Server uses a default UI access attribute of uid.9. The Pluggable Authentication Module (PAM) login attribute of your LDAP Server acts as a shell access attribute. Type the distinguished name and password for the user whose credentials should be used to validate access to the LDAP directory in the User Name and Password fields.ou=security. Setting a UI access attribute tells the local appliance to match the value of that attribute rather than the value of the uid attribute. the local appliance checks the user name entered on login against the attribute value of uid.com. If you want to filter on uid. For example.dc=com.dc=example. However. you must explicitly set the Shell Access Attribute to match the attribute value. you could type %s@security. type (physicalDeliveryOfficeName=NewYork). if you are connecting to an OpenLDAP Server where user objects have a uid attribute and the object for the administrator in the Security division at our example company has a uid value of NetworkAdmin. For example. Continue with Configuring Attribute Mapping. To set a filter that retrieves only specific objects within the namespace you specified as the Base DN. into the User Name Template field. For a Microsoft Active Directory server.

1 Sourcefire 3D System Administrator Guide 275 . use the 3. Configuring Access Settings by Group Requires: DC If you prefer to base default access settings on a user’s membership in an LDAP group. you can configure a default access setting for those users detected by LDAP that do not belong to any specified groups. on a Microsoft Active Directory Server. When a user logs in. Version 4. on a Microsoft Active Directory Server. the Sourcefire 3D System dynamically checks the LDAP directory and assigns default access rights according to the user’s current group membership. you may want to use the UI Access Attribute to retrieve users. If you are not using LDAP groups for authentication. because there may not be a uid attribute on Active Directory Server user objects. You can reference static LDAP groups or dynamic LDAP groups. To retrieve users based on an attribute instead of the Base DN and Base Filter. Instead.Managing Users Managing Authentication Objects Chapter 8 To configure attribute mapping for a server: Access: Admin 1. sAMAccountName shell access attribute to retrieve shell access users by typing sAMAccountName in the Shell Access Attribute field. you have two choices: • • If you want to configure user default roles based on LDAP group membership. For example. continue with Configuring Administrative Shell Access on page 278. To retrieve users for shell access. For the next step. When you do so. continue with Configuring Access Settings by Group. For example. and dynamic LDAP groups are groups where membership is determined by creating an LDAP search that retrieves group users based on user object attributes. you can search the userPrincipalName attribute by typing userPrincipalName in the UI Access Attribute field. type the attribute type in the UI Access Attribute field. you can specify distinguished names for existing groups on your LDAP server for each of the access roles used by your Sourcefire 3D System. 2. type the attribute type you want to filter on in the Shell Access Attribute field.9. Any group you reference must exist on the LDAP server. Group access settings for a role only affect users who are members of the group. Static LDAP groups are groups where membership is determined by group object attributes that point to specific users.

the Sourcefire 3D System limits the number of recursions of a search to four to prevent search syntax errors from causing infinite loops.Managing Users Managing Authentication Objects Chapter 8 The access rights granted when a user logs into the Sourcefire 3D System depends on the LDAP configuration: • If no group access settings are configured for your LDAP server. the Authentication Method column on the User Management page provides a status of External . When you modify the access rights for an externally authenticated user. the user is assigned the default minimum access role specified in the Group Controlled Access Roles section of the authentication object.9. when a new user logs in. For this reason. however. You can.1 Sourcefire 3D System Administrator Guide 276 . the default access role defined in the Group Controlled Access Roles section is granted to the user. If a user belongs to more than one configured group. • • • You cannot remove the minimum access rights for users assigned an access role because of LDAP group membership through the Sourcefire 3D System user management page. the LDAP query is used exactly as it is configured on the LDAP server. If a user’s group membership is not established in those recursions. If you configure any group settings. new users belonging to specified groups inherit the minimum access setting for the groups where they are members. If a new user does not belong to any specified groups. the user receives the access role for the group with the highest access as a minimum access role. assign additional rights. the Sourcefire 3D System authenticates the user against the LDAP server and then grants user rights based on the default minimum access role set in the system policy.Locally Modified. IMPORTANT! If you use a dynamic group. Version 4.

dc=com. dc=com. system management.ou=groups. to authenticate names in the information technology organization at the Example company. Type the distinguished name for the LDAP group containing users who should at minimum have access to analysis and reporting features. type cn=securitygroup. For example.Managing Users Managing Authentication Objects Chapter 8 To base access defaults on LDAP group membership: Access: Admin 1. to authenticate names in the Security organization at the Example company. Version 4. For example.dc=example. 4.ou=groups. dc=example. 2. Type the distinguished name for the LDAP group containing users who should at minimum have access to monitoring and maintenance features in the Maintenance Group DN field.dc=example. dc=example. Type the distinguished name for the LDAP group containing users who should at minimum have access to rules and policy configuration in the Policy & Response Administrator Group DN field. type cn=ipsanalystgroup. For example. Type the distinguished name for the LDAP group containing users who should at minimum have access to IPS analysis features in the Intrusion Event Analyst Group DN field.1 Sourcefire 3D System Administrator Guide 277 . to authenticate names in the information technology organization at the Example company. 3. to authenticate names in the Intrusion Event Analyst group at the Example company. dc=com.9. type cn=itgroup.ou=groups. For example. type cn=itgroup.ou=groups. and all maintenance features in the Administrator Group DN field.dc=com. rule and policy configuration.

3Dx800 sensors. For example. Type the distinguished name for the LDAP group containing users who should at minimum have access to IPS analysis features in the Intrusion Event Analyst Group DN (Read Only) field.9. type the LDAP attribute that contains the LDAP search string used to determine membership in a dynamic group in the Group Member URL Attribute field. see Adding New User Accounts on page 300. 9. For more information on managing authentication object order.Managing Users Managing Authentication Objects Chapter 8 5. 11. if the member attribute is used to indicate membership in the static group you reference for default Policy & Response Administrator access. TIP! Press the Ctrl key while clicking role names to select multiple roles in the list. Configuring Administrative Shell Access Requires: DC You can also use the LDAP directory server to authenticate accounts for shell access on your local appliance (3D Sensor or Defense Center). Specify a search filter that will retrieve entries for users you want to grant shell access. Note that you can only configure shell access for the first authentication object in your system policy. 10. Type the LDAP attribute that designates membership in a static group in the Group Member Attribute field. Optionally. Version 4. Continue with Configuring Administrative Shell Access on page 278. IMPORTANT! Sourcefire does not support external authentication for RNA Software for Red Hat Linux. if the memberURL attribute contains the LDAP search that retrieves members for the dynamic group you specified for default Admin access. For more information on user access roles. 7.1 Sourcefire 3D System Administrator Guide 278 . see Configuring Authentication Profiles on page 329. type member. Type the distinguished name for the LDAP group containing users who should at minimum have access to RNA analysis features in the RNA Event Analyst Group DN (Read Only) field. type memberURL. 8. Type the distinguished name for the LDAP group containing users who should at minimum have access to RNA analysis features in the RNA Event Analyst Group DN field. For example. 6. Intrusion Agents. Select the default minimum access role for users that do not belong to any of the specified groups from the Default User Role list. or Crossbeam-based software sensors.

type the attribute type.Managing Users Managing Authentication Objects Chapter 8 With the exception of the root account. Make sure that you restrict the list of users with shell access appropriately. If the user then is re-enabled. You can use the Same as Base Filter option to run the query only once for both purposes. 2. and the attribute value you want to use as a filter. a warning displays when you save the authentication object to confirm that you meant to leave the filter blank. the directory remains. Addition and deletion of shell access users occurs only on the LDAP server.9. Continue with Testing User Authentication. Shell users should log in using usernames with all lowercase letters. a comparison operator. which is unnecessarily time-consuming. but the user shell is set to /bin/false in /etc/password to disable the shell. if all network administrators have a manager attribute which has an attribute value of shell. Note that a home directory for each shell user is created on login. or select Same as Base Filter to use the same filter you specified when configuring authentication settings. the shell is reset. and when an LDAP shell access user account is disabled (by disabling the LDAP connection). you can set a base filter of (manager=shell).1 Sourcefire 3D System Administrator Guide 279 . using the same home directory. IMPORTANT! If you choose not to specify a shell access filter. Shell users are not configured as local users on the appliance. enclosed in parentheses. WARNING! All shell users have sudoers privileges. the same query would be run twice. If the shell access filter was the same as the base filter. in the Shell Access Filter field. shell access is controlled entirely though the shell access attribute you set. For example. To configure shell account authentication: Access: Admin 1. Version 4. even after they log in. the LDAP query to retrieve users combines the base filter with the shell access filter. Normally. and the filter you set here determines which set of users on the LDAP server can log into the shell. The Same as Base Filter check box allows you to search more efficiently if all users qualified in the base DN are also qualified for shell access privileges. To set a filter to retrieve administrative user entries based on attribute value.

Click Test. If you are connecting to a Microsoft Active Directory Server and supplied a shell access attribute in place of uid in Configuring Attribute Mapping on page 274. the test fails even if the server configuration is correct. A message appears. you must apply a system policy with that object enabled to the appliance. TIP! If you mistype the name or password of the test user. select Show Details. To test user authentication: Access: Admin 1. see Configuring Authentication Profiles on page 329 and Applying a System Policy on page 324. type JSmith. To enable LDAP authentication using the object on an appliance. Note that testing the connection to servers with more than 1000 users only returns 1000 users because of UI page size limitations. If that succeeds supply a user name and password to test with the specific user. to test to see you can retrieve the JSmith user credentials at our example company.9. 3. For the user name. For example.1 Sourcefire 3D System Administrator Guide 280 . with the new object listed. 2.Managing Users Managing Authentication Objects Chapter 8 Testing User Authentication Requires: DC After you configure LDAP server and authentication settings. type the uid value or shell access attribute value and password for the user whose credentials should be used to validate access to the LDAP directory. you can enter the value for the uid attribute for the user you want to test with. The Login Authentication page appears. click Save. You can also specify a fully-qualified distinguished name for the user. use the value for that attribute as the user name. In the User Name and Password fields. you can specify user credentials for a user who should be able to authenticate to test those settings. For more information. 4. Test the server configuration without the additional test parameters first. If the test succeeds. To view details of test output. Version 4. either indicating success of the test or detailing what settings are missing or need to be corrected.

5.Managing Users Managing Authentication Objects Chapter 8 LDAP Authentication Object Examples Requires: DC For sample configurations showing how different configuration options might be used for connections to specific directory server types. • OU=security.10.1 Sourcefire 3D System Administrator Guide 281 .10.3.3.DC=it.DC=com for the security organization in This example shows a connection using a base distinguished name of the information technology domain of the Example company. see the following sections: • • • OpenLDAP Example on page 281 Microsoft Active Directory Server Example on page 282 Sun Directory Server Example on page 284 OpenLDAP Example Requires: DC The following figures illustrate parts of a sample LDAP login authentication object for an OpenLDAP directory server with an IP address of 10.DC=example. Note that the connection uses port 389 for access and that connections to the server time out after 30 seconds of disuse. This example illustrates important aspects of LDAP configuration.9.4. with a backup server that has an IP address of 10. Version 4.

11. the connection uses port 389 for access and connections to the server time out after 30 seconds of disuse (or the timeout period set on the LDAP server). Microsoft Active Directory Server Example Requires: DC The following figure illustrates a sample LDAP login authentication object for a Microsoft Active Directory Server with an IP address of 10.11. the CN attribute is set as the shell access attribute. Because the user names to be retrieved are contained in the default uid attribute.Managing Users Managing Authentication Objects Chapter 8 • Because this is an OpenLDAP server that uses CN as a part of each user’s name. no UI access attribute is specified. the user name template for the connection uses CN=%s.9. The Sourcefire 3D System checks the uid attribute of each object in the directory indicated by the distinguished name against the username for each user who logs into the system.1 Sourcefire 3D System Administrator Guide 282 . Version 4.4. to indicate the template used to format user names retrieved from the server. Aspects of this example illustrate important differences in this LDAP configuration from the configuration discussed in the OpenLDAP Example on page 281.5. A shell access filter has been applied to this configuration. allowing only those users who have a common name attribute value of jsmith to log into the appliance using a shell account.3. Like the OpenLDAP server.3. with a backup server that has an IP address of 10. • • • To support shell access. Note that all objects in the directory are checked because no base filter is set. followed by the base distinguished name for the server directory.

1 Sourcefire 3D System Administrator Guide 283 .DC=it.DC=example. it uses the userPrincipalName attribute to store user names rather than the uid attribute. a Shell Access Attribute of sAMAccountName causes each sAMAccountName attribute to be checked for all objects in the directory for matches when a user logs into a shell account on the appliance. because this server is a Microsoft Active Directory server. However. the Sourcefire 3D System checks attributes for all objects in the directory indicated by the base distinguished name.9. the user name template for the connection uses address specification syntax documented in RFC 822 rather than the typical LDAP naming syntax. Version 4. Note that the configuration includes a UI Access Attribute of userPrincipalName. because no base filter is applied to this server. this example shows a connection using a base distinguished name of OU=security. • • In addition.DC=com for the security organization in the information technology domain of the Example company.Managing Users Managing Authentication Objects Chapter 8 • Like the OpenLDAP server. • Because this is a Microsoft Active Directory Server. As a result. Again. the Sourcefire 3D System checks the userPrincipalName attribute for each object for matching user names when a user attempts to log into the Sourcefire 3D System.

a shell access filter has been specified for this server. allowing only those users who have a common name attribute value of jsmith to log into the appliance using a shell account.4. The maintenance role is automatically assigned to all members of the group with a member group attribute and the base domain name of CN=maintenance.3.3.12. as noted above. However.5.DC=it. Version 4. • As in the OpenLDAP server.Managing Users Managing Authentication Objects Chapter 8 • This example also has group settings in place. a shell access attribute value of sAMAccountName must be set for shell access to work on a Microsoft Active Directory server.1 Sourcefire 3D System Administrator Guide 284 .DC=com.12.9. Sun Directory Server Example Requires: DC The following figure illustrates a sample LDAP login authentication object for a Sun Directory Server with an IP address of 10. with a backup server that has an IP address of 10.DC=example.

the Server Port is set to 636.DC=example. Version 4. Using Same as Base Filter allows a more efficient search query if and only if all users qualified in the base DN are also qualified for shell access privileges.DC=it.DC=com for the security organization in the information technology domain of the Example company. • To allow shell access on the server. However. A certificate has been uploaded to allow the SSL connection. the uid attribute is named as the Shell Access Attribute and the Same as Base Filter option for the shell access filter is set.9. allowing all users with a common name ending in smith to log in using a shell account as well. • This example shows a connection using a base distinguished name of OU=security. note that this server does have a base filter of (cn=*smith). • • The user name template shown uses the uid attribute value as the user name.1 Sourcefire 3D System Administrator Guide 285 . Note that all objects in the directory are checked because no base filter is set. The Sourcefire 3D System checks the uid attribute of each object in the directory indicated by the distinguished name against the user name for each user who logs into the system.Managing Users Managing Authentication Objects Chapter 8 Settings in the example illustrate important differences in this LDAP configuration from the configuration discussed in Microsoft Active Directory Server Example on page 282: • Because the Encryption for the connection is set to SSL. no UI access attribute is specified. Because user names can be retrieved from the uid attribute on this server. The filter restricts the users retrieved from the server to those with a common name ending in smith.

The Create Authentication Object page appears.1 Sourcefire 3D System Administrator Guide 286 . The Login Authentication page appears. If the object is in use in a system policy. To edit an authentication object: Access: Admin 1. Select Operations > Configuration > Login Authentication. 2.Managing Users Managing Authentication Objects Chapter 8 Editing LDAP Authentication Objects Requires: DC You can edit an existing authentication object. Version 4. upload the new certificate and re-apply the system policy to your appliances to copy over the new certificate. the settings in place at the time the policy was applied stay in effect until you re-apply the policy.9. see the following topics: • • • • • Creating LDAP Authentication Objects on page 269 Configuring LDAP Authentication Settings on page 271 Configuring Attribute Mapping on page 274 Configuring Administrative Shell Access on page 278 Testing User Authentication on page 280 IMPORTANT! If you previously uploaded a certificate and want to replace it. Click Edit next to the object you want to edit. 3. Modify the object settings as needed. For more information.

you can also configure shell access authentication. Select Operations > Configuration > Login Authentication. you need TCP/IP access from your local appliance to the authentication server where you want to connect. The Sourcefire 3D System implementation of RADIUS supports the use of SecurID® tokens. or if the user is not listed for any of the user roles. those users can log into a Sourcefire 3D System appliance using their pin plus the SecurID token without any additional configuration on the appliance. users authenticated against that server append the SecurID token to the end of their SecurID pin and use that as their password when they log into a Sourcefire appliance. For more information. or failing that. If your RADIUS server returns custom attributes for any users you plan to authenticate. and account for user access to network resources. if needed. Click Save. When a user authenticated on a RADIUS server logs in for the first time. You can create an authentication object for any RADIUS server that conforms to RFC 2865. Optionally. Note that to create an authentication object. You also grant user roles to specific and default users. Understanding RADIUS Authentication Requires: DC The Remote Authentication Dial In User Service (RADIUS) is an authentication protocol used to authenticate. Version 4. the default access role you selected in the authentication object.9. unless the settings are granted through the user lists in the authentication object. you define settings that let you connect to an authentication server. Your changes are saved and the Login Authentication page re-appears. Creating RADIUS Authentication Objects Requires: DC When you create a RADIUS authentication object. The Login Authentication page appears. authorize. Click Create Authentication Object. 2. the user receives the roles specified for that user in the authentication object. To create an authentication object: Access: Admin 1. Remember that you have to apply a system policy with the object enabled to an appliance before the authentication changes take place on that appliance. When you configure authentication by a server using SecurID.Managing Users Managing Authentication Objects Chapter 8 4. The Create Authentication Object page appears. You can modify a user’s roles. As long as SecurID is configured correctly to authenticate users outside the Sourcefire 3D System.1 Sourcefire 3D System Administrator Guide 287 . you need to define those custom attributes. see Configuring Authentication Profiles on page 329 and Applying a System Policy on page 324. the system policy.

specify the users or user attribute values for users that you want to receive specific Sourcefire 3D System access roles. Test your configuration by entering the name and password for a user who should successfully authenticate. Set the default user role. see Testing User Authentication on page 294. see Defining Custom RADIUS Attributes on page 293. 6. Your changes are saved. For more information. 5. After the appliance re-queries the primary authentication server the number of times indicated by the Retries field and the number of seconds indicated in the Timeout field again elapses without a response from the primary authentication server. the appliance then rolls over to the backup server. define those attributes. see Configuring RADIUS Connection Settings on page 288. you first specify the primary and backup server and server port where you want the local appliance (3D Sensor or Defense Center) to connect for authentication. For more information.1 Sourcefire 3D System Administrator Guide 288 . configure administrative shell access. IMPORTANT! For FreeRADIUS to function correctly. Remember that you have to apply a system policy with the object enabled to an appliance before the authentication changes take place on that appliance. for example. see Configuring Administrative Shell Access on page 292. see Configuring Authentication Profiles on page 329 and Applying a System Policy on page 324. For more information. you can set a timeout for the connection attempt to the primary server. 4. If. the primary server has RADIUS disabled. If you specify a backup authentication server. For more information. For more information. the appliance would query the backup server.Managing Users Managing Authentication Objects Chapter 8 3. For more information. Configuring RADIUS Connection Settings Requires: DC When you create a RADIUS authentication object. If the profiles for any of the users to authenticate return custom RADIUS attributes. Optionally. you need to open both ports 1812 and 1813 on your firewall and on the FreeRADIUS server. If the number of seconds indicated in the Timeout field (or the timeout on the directory server) elapses without a response from the primary authentication server. 7. Identify the primary and backup authentication servers where you want to retrieve user data for external authentication and set timeout and retry values. Optionally. the appliance then re-queries the primary server.9. see Configuring RADIUS User Roles on page 290. If RADIUS is running on the port of the primary RADIUS server and for some reason refuses to service the request (due to Version 4.

4. Type the number of seconds that should elapse before retrying the connection in the Timeout field.Managing Users Managing Authentication Objects Chapter 8 misconfiguration or other issues). Type the secret key for the primary RADIUS authentication server in the RADIUS Secret Key field. Type the IP address or host name for the primary RADIUS server where you want to obtain authentication data in the Primary Server Host Name/IP Address field. the failover to the backup server does not occur. Select RADIUS from the Authentication Method drop-down list. To identify a RADIUS authentication server: Access: Admin 1. 8. 7. IMPORTANT! IPv6 addresses are not supported. modify the port used by the backup RADIUS authentication server in the Backup Server Port field. Type the secret key for the backup RADIUS authentication server in the RADIUS Secret Key field. however. 6. Type the IP address or host name for the backup RADIUS authentication server where you want to obtain authentication data in the Backup Server Host Name/IP Address field. modify the port used by the primary RADIUS authentication server in the Primary Server Port field.9. 2. Optionally. Optionally. Type a name and description for the authentication server in the Name and Description fields. 9. Version 4.1 Sourcefire 3D System Administrator Guide 289 . 3. 5.

• • You can also use attribute-value pairs. If a new user is not specified on any lists and default access roles are selected in the Default User Role list of the authentication object. You can select multiple roles on the Default User Role list. Configuring RADIUS User Roles Requires: DC You can specify the access roles for existing users on your RADIUS server by listing the user names for each of the access roles used by your Sourcefire 3D System. if you know all users who should be RNA Analysts have the value Analyst for their User-Category attribute. You can.1 Sourcefire 3D System Administrator Guide 290 . when a new user logs in.9. the user is assigned those access roles. and you must remove the assigned user right on the user management page. see Configuring User Roles on page 304. When you do so. you must not only move the user from one list to another in the RADIUS Specific Parameters section or change the user’s attribute on the RADIUS server. For more information on the user roles supported by the Sourcefire 3D System.Managing Users Managing Authentication Objects Chapter 8 10. Note that you need to define any custom attributes before you use them to set user role membership. to identify users who should receive a particular user role. you can also configure a default access setting for those users detected by RADIUS that are not specified for a particular role. the Sourcefire 3D System checks the RADIUS server and grants access rights depending on the RADIUS configuration: • If specific access settings are not configured for a user and a default access role is not selected. that user receives all assigned access roles. however. For example. You cannot remove the minimum access rights for users assigned an access role because of RADIUS user list membership through the Sourcefire 3D System user management page. WARNING! If you want to change the minimum access setting for a user. rather than usernames. Version 4. you must reapply the system policy. you can type User-Category=Analyst in the RNA Analyst List field to grant that role to those users. assign additional rights. Type the number of times the primary server connection should be tried before rolling over to the backup connection in the Retries field. Continue with Configuring RADIUS User Roles. When a user logs in. For more information. If you add a user to the list for one or more specific role. see Defining Custom RADIUS Attributes on page 293. 11. You can assign a default user role (or roles) to be assigned to any users that are authenticated externally but not listed for a specific role. the Sourcefire 3D System authenticates the user against the RADIUS server and then grants user rights based on the default access role (or roles) set in the system policy.

rule and policy configuration.who should at minimum receive access to rules and policy configuration in the Policy & Response Administrator List field. Type the name of each user or each identifying attribute-value pair. Type the name of each user or each identifying attribute-value pair. separated by commas. who should at minimum receive access to monitoring and maintenance features in the Maintenance List field. to grant the Maintenance role to all users with a in the Maintenance List field. For example. 4. 3. 5. Type the name of each user or each identifying attribute-value pair. who should at minimum receive access to IPS analysis features in the Intrusion Event Analyst (Read Only) List field. Type the name of each user or each identifying attribute-value pair. 2. User-Category value of Maintenance. Type the name of each user or each identifying attribute-value pair. to grant the Administrator role to the users jsmith and jdoe. who should at minimum receive access to IPS analysis features in the Intrusion Event Analyst List field. and all maintenance features in the Administrator List field. jdoe in the Administrator List field. type User-Category=Maintenance For example.Managing Users Managing Authentication Objects Chapter 8 To base access on user lists: Access: Admin 1.9. Version 4. separated by commas. type jsmith. system management. separated by commas. separated by commas. separated by commas. who should at minimum receive access to analysis and reporting features.1 Sourcefire 3D System Administrator Guide 291 .

WARNING! All shell users have sudoers privileges. Make sure that you restrict the list of users with shell access appropriately. separated by commas. Shell users should log in using usernames with all lowercase letters. Specify user names for users you want to grant shell access. Type the name of each user or each identifying attribute-value pair. Type the name of each user or each identifying attribute-value pair. and when an RADIUS shell access user account is disabled (by disabling the RADIUS connection). who should at minimum receive access to RNA analysis features in the RNA Event Analyst List field. see Configuring Authentication Profiles on page 329. Shell users are configured as local users on the appliance when the system policy is applied. If the user then is re-enabled. 8. Configuring Administrative Shell Access Requires: DC You can also use the RADIUS server to authenticate accounts for shell access on your local appliance (3D Sensor or Defense Center). the directory remains. separated by commas. 7. the shell is reset. who should at minimum receive access to RNA analysis features in the RNA Event Analyst (Read Only) List field.Managing Users Managing Authentication Objects Chapter 8 6. Version 4. the shell access list you set on the RADIUS authentication object entirely controls shell access on the appliance. For more information on user access roles. Continue with Configuring Administrative Shell Access. 9. Note that a home directory for each shell user is created on login. Note that you can only configure shell access for the first authentication object in your system policy.1 Sourcefire 3D System Administrator Guide 292 . Select the default minimum access role for users that do not belong to any of the specified groups from the Default User Role list. see Configuring User Roles on page 304. With the exception of the root account.9. using the same home directory. For more information on managing authentication object order. TIP! Press the Ctrl key while clicking role names to select multiple roles in the list. but the user shell is set to /bin/false in / etc/password to disable the shell.

Managing Users Managing Authentication Objects

Chapter 8

To configure shell account authentication: Access: Admin 1. Type the usernames, separated by commas, in the Administrator Shell Access User List field. IMPORTANT! If you choose not to specify a shell access filter, a warning displays when you save the authentication object to confirm that you meant to leave the filter blank. 2. Continue with Defining Custom RADIUS Attributes on page 293.

Defining Custom RADIUS Attributes
Requires: DC
dictionary file in /etc/radiusclient/ and you plan to use those attributes to

If your RADIUS server returns values for attributes not included in the

set user roles for users with those attributes, you need to define those attributes in the login authentication object. You can locate the attributes returned for a user by looking at the user’s profile on your RADIUS server. When you define an attribute, you provide the name of the attribute, which consists of alphanumeric characters. Note that words in an attribute name should be separated by dashes rather than spaces. You also provide the attribute ID, which should be an integer and should not conflict with any existing attribute IDs in the etc/radiusclient/dictionary file. You also specify the type of attribute: string, IP address, integer, or date. As an example, if a RADIUS server is used on a network with a Cisco router, you might want to use the Ascend-Assign-IP-Pool attribute to grant a specific role to all users logging in from a specific IP address pool. Ascend-Assign-IP-Pool is an integer attribute that defines the address pool where the user is allowed to log in, with the integer indicating the number of the assigned IP address pool. To declare that custom attribute, you create a custom attribute with an attribute name of Ascend-IP-Pool-Definition, an attribute ID of 218, and an attribute type of integer. You could then type Ascend-Assign-IP-Pool=2 in the Intrusion Event Analyst (Read Only) field to grant read-only intrusion event analyst rights to all users with an Ascend-IP-Pool-Definition attribute value of 2. When you create a RADIUS authentication object, a new dictionary file for that object is created on the Sourcefire 3D System appliance in the /var/sf/ userauth directory. Any custom attributes you add to the authentication object are added to the dictionary file.

Version 4.9.1

Sourcefire 3D System Administrator Guide

293

Managing Users Managing Authentication Objects

Chapter 8

To define a custom attribute: Access: Admin 1. Click the arrow to expand the Define Custom RADIUS Attributes section. The attribute fields appear.

2. Type an attribute name consisting of alphanumeric characters and dashes, with no spaces, in the Attribute Name field. 3. Type the attribute ID, in integer form, in the Attribute ID field. 4. Select the type of attribute from the Attribute Type drop-down list. 5. Click Add to add the custom attribute to the authentication object. TIP! You can remove a custom attribute from an authentication object by clicking Delete next to the attribute. 6. Continue with Testing User Authentication on page 294.

Testing User Authentication
Requires: DC After you configure RADIUS connection, user role, and custom attribute settings, you can specify user credentials for a user who should be able to authenticate to test those settings. For the user name, you can enter the user name for the user you want to test with. Note that testing the connection to servers with more than 1000 users only returns 1000 users because of UI page size limitations. TIP! If you mistype the name or password of the test user, the test fails even if the server configuration is correct. To verify that the server configuration is correct, click Test without entering user information in the Additional Test Parameters first. If that succeeds supply a user name and password to test with the specific user.

Version 4.9.1

Sourcefire 3D System Administrator Guide

294

Managing Users Managing Authentication Objects

Chapter 8

To test user authentication: Access: Admin 1. In the User Name and Password fields, type the user name and password for the user whose credentials should be used to validate access to the RADIUS server. For example, to test to see you can retrieve the jsmith user credentials at our example company, type jsmith.

2. Select Show Details and click Test. A message appears, either indicating success of the test or detailing what settings are missing or need to be corrected. 3. If the test succeeds, click Save. The Login Authentication page appears, with the new object listed. To enable RADIUS authentication using the object on an appliance, you must apply a system policy with that object enabled to the appliance. For more information, see Configuring Authentication Profiles on page 329 and Applying a System Policy on page 324.

RADIUS Authentication Object Examples
Requires: DC This section provides examples of RADIUS server authentication objects to show how Sourcefire 3D System RADIUS authentication features can be used. See the following sections for more information: • • Authenticating a User using RADIUS on page 295 Authenticating a User with Custom Attributes on page 296

Authenticating a User using RADIUS
Requires: DC The following figure illustrates a sample RADIUS login authentication object for a server running freeRadius with an IP address of 10.10.10.98. Note that the connection uses port 1812 for access and that connections to the server time out after 30 seconds of disuse and will retry three times before attempting to connect to a backup authentication server.

Version 4.9.1

Sourcefire 3D System Administrator Guide

295

Managing Users Managing Authentication Objects

Chapter 8

This example illustrates important aspects of RADIUS user role configuration: • Users ewharton and gsands are granted administrative access to Sourcefire 3D System appliances where this authentication object is enabled. The user jaustin is granted Intrusion Event Analyst access to Sourcefire 3D System appliances where this authentication object is enabled. The user cbronte is granted RNA Event Analyst access to Sourcefire 3D System appliances where this authentication object is enabled. The user ewharton can log into the appliance using a shell account.

• • •

The following graphic depicts the role configuration for the example:

Authenticating a User with Custom Attributes
Requires: DC You can use an attribute-value pair to identify users who should receive a particular user role. If the attribute you use is a custom attribute, you must define the custom attribute.

Version 4.9.1

Sourcefire 3D System Administrator Guide

296

Managing Users Managing Authentication Objects

Chapter 8

The following figure illustrates the role configuration and custom attribute definition in a sample RADIUS login authentication object for the same freeRadius server as in the previous example. In this example, however, the MS-RAS-Version custom attribute is returned for one or more of the users because a Microsoft remote access server is in use. Note the MS-RAS-Version custom attribute is a string. In this example, all users logging in to RADIUS through a Microsoft v. 5.00 remote access server should receive the Intrusion Event Analyst (Read Only role), so you type the attribute-value pair of MS-RAS-Version=MSRASV5.00 in the Intrusion Event Analyst (Read Only) field.

Version 4.9.1

Sourcefire 3D System Administrator Guide

297

Managing Users Managing Authentication Objects

Chapter 8

Editing RADIUS Authentication Objects
Requires: DC You can edit an existing authentication object. If the object is in use in a system policy, the settings in place at the time the policy was applied stay in effect until you re-apply the policy. To edit an authentication object: Access: Admin 1. Select Operations > Configuration > Login Authentication. The Login Authentication page appears. 2. Click Edit next to the object you want to edit. The Create Authentication Object page appears. 3. Modify the object settings as needed. For more information, see the following topics: • • • • • Creating RADIUS Authentication Objects on page 287 Configuring RADIUS Connection Settings on page 288 Configuring RADIUS User Roles on page 290 Configuring Administrative Shell Access on page 292 Testing User Authentication on page 294

4. Click Save. Your changes are saved and the Login Authentication page re-appears. Remember that you have to apply a system policy with the object enabled to an appliance before the authentication changes take place on that appliance. For more information, see Configuring Authentication Profiles on page 329 and Applying a System Policy on page 324.

Deleting Authentication Objects
Requires: DC You can delete an authentication object if it is not currently enabled in a system policy. To delete an authentication object: Access: Admin 1. Select Operations > Configuration > Login Authentication. The Login Authentication page appears. 2. Click Delete next to the object you want to delete. The object is deleted and the Login Authentication page appears.

Version 4.9.1

Sourcefire 3D System Administrator Guide

298

Managing Users Managing User Accounts

Chapter 8

Managing User Accounts
If you have Admin access, you can use the web interface to view and manage user accounts on a Defense Center or a 3D Sensor, including adding, modifying, and deleting accounts. User accounts without Admin access are restricted from accessing management features. The navigation menu differs in appearance for each type of user. See the following sections for more information about managing user accounts: • Viewing User Accounts on page 299 explains how to access the User Management page, where you can add, activate, deactivate, edit, and delete user accounts. Adding New User Accounts on page 300 describes the different options you can use when you add a new user account. Managing Externally Authenticated User Accounts on page 302 explains how externally authenticated users are added and what aspects of the user configuration you can manage within the Sourcefire 3D System. Modifying User Privileges and Options on page 306 explains how to access and modify an existing user account. Modifying Restricted Event Analyst Access Properties on page 307 explains how to restrict the data available to a user account with restricted data access. Deleting User Accounts on page 312 explains how to delete user accounts. User Account Privileges on page 312 contains tables that list the menus and options each type of user account can access.

• •

• •

• •

Viewing User Accounts
Requires: DC/MDC or 3D Sensor From the User Management page, you can view, edit, and delete existing accounts. You can determine the type of authentication for a user from the Authentication Method column. The Password Lifetime column indicates the days remaining on each user’s password. The Action column allows you to set users active or inactive. Note that for externally authenticated users, if the authentication object for the server is disabled, the Authentication Method column displays External (Disabled). To access the User Management page: Access: Admin Select Operations > User Management. The User Management page appears, showing each user, with options to activate, deactivate, edit, or delete the user account.

Version 4.9.1

Sourcefire 3D System Administrator Guide

299

Managing Users Managing User Accounts

Chapter 8

See the following sections for information about the actions you can perform on the User Management page: • • • • • Adding New User Accounts on page 300 Modifying User Privileges and Options on page 306 Modifying Restricted Event Analyst Access Properties on page 307 Modifying User Passwords on page 311 Deleting User Accounts on page 312

Adding New User Accounts
Requires: DC/MDC or 3D Sensor When you set up a new user account, you can control which parts of the system the account can access. To add a new user: Access: Admin 1. Select Operations > User Management. The User Management page appears.

Version 4.9.1

Sourcefire 3D System Administrator Guide

300

Managing Users Managing User Accounts

Chapter 8

2. Click Create User. The Create User page appears.

3. In the User Name field, type a name for the new user. New user names must contain alphanumeric or hyphen characters with no spaces, and must be no more than 32 characters. 4. Requires: DC/MDC If you want this user to authenticate to an external directory server on login, select Use External Authentication Method. IMPORTANT! If you select this option, the password management options below disappear. Configure access settings and click Add User to complete configuration of the externally authenticated user. You must also create an authentication object for the external authentication server you want to use for authentication on your Defense Center, and apply a system policy with authentication enabled to your appliance before users can log in using credentials from an external server. For more information, see Managing Authentication Objects on page 269 and Configuring Authentication Profiles on page 329.

Version 4.9.1

Sourcefire 3D System Administrator Guide

301

Managing Users Managing User Accounts

Chapter 8

5. In the Password field, type a password (up to 32 alphanumeric characters). If you enable password strength checking, the password must be at least eight alphanumeric characters of mixed case and must include at least one numeric character. It cannot be a word that appears in a dictionary or include consecutive repeating characters. 6. In the Confirm Password field, type the password again. 7. Configure the remaining password user account options. For more information, see the User Account Password Options table on page 304. 8. Select user roles to grant to the user. For more information, see the User Roles table on page 305. 9. Optionally, for users with event analyst roles, click Restrict Deletion Rights - User Cannot Delete Bookmarks, Searches, Reports, Report Profiles, Custom Workflows or Custom Tables Created by Other Users to restrict the user to deletion of reports, report profiles, searches, bookmarks, custom tables, and custom workflows created by the user. 10. Click Add User. A message appears, indicating that the user was added. The username appears on the User Management page. IMPORTANT! Click Deactivate next to the name of an internally authenticated user on the User Management page to disable that user login without deleting it. To reactivate a user, click Activate next to the username.

Managing Externally Authenticated User Accounts
Requires: DC/MDC or 3D Sensor When an externally authenticated user logs into an appliance that has external authentication enabled, the appliance grants the user the default access role you set by specifying group membership in the authentication object. If you did not configure access group settings, the appliance grants the default user role you set in the system policy. However, if you add users locally before they log into the appliance, the user privileges you configure on the User Management page override the default settings. An internally authenticated user is converted to external authentication when all of the following conditions exist: • • • You enable LDAP or RADIUS authentication. The same username exists for the user on the LDAP or RADIUS server. The user logs in using the password stored for that user on the LDAP or RADIUS server.

Version 4.9.1

Sourcefire 3D System Administrator Guide

302

Managing Users Managing User Accounts

Chapter 8

Once an internally authenticated user converts to an externally authenticated user, you cannot revert to internal authentication for that user. For more information on selecting a default user role, see Configuring Authentication Profiles on page 329 and Understanding User Privileges on page 267. Note that you can only enable external authentication in a system policy on a Defense Center. You must use the Defense Center to apply the policy to managed sensors if you want to use external authentication on them. For more information on associating an external user with a set of permissions on your appliance, see Logging into the Appliance to Set Up an Account on page 23. For more information on modifying user access, see Modifying User Privileges and Options on page 306. Note that you cannot manage passwords for externally authenticated users or deactivate externally authenticated users through the Sourcefire 3D System interface. For externally authenticated users, you cannot remove the minimum access rights through the Sourcefire 3D System user management page for users assigned an access role because of LDAP group or RADIUS list membership or attribute values. On the Edit User page for an externally authenticated user, rights granted because of settings on an external authentication server are marked with a status of Externally Modified. You can, however, assign additional rights. When you modify the access rights for an externally authenticated user, the Authentication Method column on the User Management page provides a status of External - Locally Modified.

Managing User Password Settings
You can also control how and when the password for each user account is changed, as well as when user accounts are disabled. The User Account

Version 4.9.1

Sourcefire 3D System Administrator Guide

303

Managing Users Managing User Accounts

Chapter 8

Password Options table describes some of the options you can use to regulate passwords and account access. IMPORTANT! After you enable Use External Authentication Method, password options no longer appear. Use the external authentication server to manage password settings. User Account Password Options Option Use External Authentication Method Description Select this option if you want this user's credentials to be externally authenticated. IMPORTANT! If you select this option for the user and the external authentication server is unavailable, that user can log into the web interface but cannot access any functionality. Enter an integer, without spaces, that determines the maximum number of times each user can try to log in after a failed login attempt before the account is locked. The default setting is five tries; use 0 to allow an unlimited number of failed logins. Enter the number of days after which the user’s password will expire. The default setting is 0, which indicates that the password never expires. Enter the number of warning days users have to change their password before their password actually expires. The default setting is 0 days. WARNING! The number of warning days must be less than the number of days before the password expires Force Password Reset on Login Check Password Strength Select this option to force the user to change his password the first time the user logs in. Select this option to require strong passwords. A strong password must be at least eight alphanumeric characters of mixed case and must include at least one numeric character. It cannot be a word that appears in a dictionary or include consecutive repeating characters.

Maximum Number of Failed Logins

Days Until Password Expiration Days Until Expiration Warning

Configuring User Roles
The User Roles table contains a synopsis of each access type. For a full list of the menus available to each access type, see User Account Privileges on page 312.

Version 4.9.1

Sourcefire 3D System Administrator Guide

304

system management. Maintenance users see the main toolbar and maintenancerelated options on the Operations top-level menu. client applications. In addition. You cannot remove minimum access rights through the Sourcefire 3D System user management page for users assigned an access role because of LDAP group or RADIUS list membership or attribute values . RNA Event Analyst (Read Only) Access Version 4. RNA Event Analysts see the main toolbar and analysisrelated options on the Analysis & Reporting and Operations menus. client applications. Select Restrict Deletion Rights . Note that you should limit use of the Administrator role for security reasons. custom tables. and reports. User Roles User Role Administrator Access Privileges Provides access to analysis and reporting features. rule and policy configuration. externally authenticated users cannot authenticate unless the external authentication server is available. assign additional rights. network maps. and you must remove the assigned user right on the user management page. Note that you can restrict an event analyst user’s deletion rights to only allow deletion of report profiles. and reports. host profiles. WARNING! If you want to change the minimum access setting for a user. network maps.9. Maintenance User Access RNA Event Analyst Access Provides access to monitoring and maintenance features. services. bookmarks. vulnerabilities. incidents.1 Sourcefire 3D System Administrator Guide 305 .User Cannot Delete Items Created by Other Users to restrict the user’s deletion rights. and custom workflows created by that user. including event views. vulnerabilities. you must reapply the system policy. however. Provides read-only access to analysis features. host profiles.Managing Users Managing User Accounts Chapter 8 Note that you cannot change the authentication type for a user after you create the user account. Provides access to RNA analysis features. including event views. you must not only move the user from one list to another in the authentication object or change the user's attribute value or group membership on the external authentication server. services. RNA Event Analysts see the main toolbar and RNA analysis-related options on the Analysis & Reporting and Operations menus. You can. and all maintenance features. Administrator users see the main toolbar as well as all the menu options. searches.

You can restrict access by allowing access to only for those events that match specified search criteria or you can turn off access for an entire category of events. Intrusion Event Analysts see the main toolbar and IPS analysis-related options on the Analysis & Reporting and Operations menus.1 Sourcefire 3D System Administrator Guide 306 . You can. including those that are externally authenticated. You manage those settings on the external server. or passwords at any time. Policy & Response Administrators have access to the main toolbar and rule and policy-related options on the Policy & Response and Operations menus. Version 4. the Authentication Method column on the User Management page provides a status of External . you must configure access rights for all accounts. Note that password management options do not apply to users who authenticate to an external directory server. and reports. Restricted event analyst users see only the main toolbar and analysis-related options on the Analysis & Reporting and Operations menus. Policy & Response Administrator Access Modifying User Privileges and Options Requires: DC/MDC or 3D Sensor After adding user accounts to the system. account options. Intrusion Event Analysts see the main toolbar and IPS analysis-related options on the Analysis & Reporting and Operations menus. however.Locally Modified.9. See Modifying Restricted Event Analyst Access Properties on page 307 for more information. incidents. However. assign additional rights. you must supply a new password for the user. For externally authenticated users. incidents. When you modify the access rights for an externally authenticated user. Provides read-only access to IPS analysis features. Note that if you change the authentication for a user from externally authenticated to internally authenticated. Provides access to rules and policy configuration. you cannot remove the minimum access rights through the Sourcefire 3D System user management page for users assigned an access role because of LDAP group or RADIUS list membership or attribute values. you can modify access privileges.Managing Users Managing User Accounts Chapter 8 User Roles (Continued) User Role Intrusion Event Analyst Access Intrusion Event Analyst (Read Only) Access Restricted Event Analyst Access Privileges Provides access to IPS analysis features. Provides access to the same features as Intrusion Event Analyst or RNA Event Analyst access. including intrusion event views. and reports. including intrusion event views.

Optionally. select or clear the Only delete items created by user option to manage the user’s ability to delete of items not created by that user.Managing Users Managing User Accounts Chapter 8 To modify user account privileges: Access: Admin 1. Select Operations > User Management. You can specify this information only after the user is added. 3.1 Sourcefire 3D System Administrator Guide 307 . See Managing User Password Settings on page 303 for information on changing password settings for internally authenticated users. See Adding New User Accounts on page 300 for information about adding new user accounts. 2. • • • Modifying Restricted Event Analyst Access Properties Requires: DC/MDC or 3D Sensor User accounts with Restricted Event Analyst access use saved searches to specify which events a user can view. The Edit User page appears. The User Management page appears. Modify the account or accounts as needed: • See Managing Externally Authenticated User Accounts on page 302 for a description of how users can be authenticated through external servers. See Configuring User Roles on page 304 for more information on configuring roles to grant access for Sourcefire 3D System functions. Click Edit next to the user you want to modify. for users with event analyst roles. Version 4.9.

The Restricted Event Analyst Settings table shows the correlation between platform and access requirements for the restricted event analyst. DC + RNA Set this data set or data sets to Show All or to a specific search One or more of the following: • Host Attributes Data • RNA Client Applications Data • RNA Hosts Data • RNA Services Data • Vulnerabilities Data view network discovery events view hosts view host attributes view services view vulnerabilities view client applications view flow data view compliance events view white list events view white list violations view users or user events view intrusion events use the clipboard DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RUA IPS IPS RNA Events Data RNA Hosts Data Host Attributes Data RNA Services Data Vulnerabilities Data RNA Client Applications Data Flow Data Compliance Events Data White List Events Data White List Violations Data Users Data Intrusion Events Data N/A .1 Sourcefire 3D System Administrator Guide 308 .Managing Users Managing User Accounts Chapter 8 Restricted event analyst users have access to only a few sections of the web interface.9.... view the network map When these platforms are present. Restricted Event Analyst Settings To allow the restricted event analyst to..included in the base set of rights for the restricted analyst role Version 4.

Managing Users Managing User Accounts Chapter 8 Restricted Event Analyst Settings (Continued) To allow the restricted event analyst to. To restrict event analyst access to events: Access: Admin 1. Searches must be private. IMPORTANT! You must have saved private searches available before you can add restricted event analyst values to a user account. IPS IPS DC/MDC or 3D Sensor Set this data set or data sets to Show All or to a specific search All data sets for which the user will generate reports All data sets for which the user will create incident reports N/A . Version 4. create multiple private saved searches. If they are saved as public. custom tables create and manage bookmarks view events from a custom table When these platforms are present. one for each of the event types.included in the base set of rights for the restricted analyst role DC/MDC or 3D Sensor All data sets for which the user will create custom workflows DC/MDC or 3D Sensor Platforms required to view custom table All data sets for which the user will need to create or access bookmarks All data sets for the applicable custom tables If you want to ensure that a user only sees data for a specific subnet. See Searching for Events in the Analyst Guide for more information. on the Defense Center. and event view settings create custom workflows and. The User Management page appears.9. generate (but not view) reports create (but not modify) incident reports change user-specific preferences such as the account password. and then apply each saved search to the account as described in the following procedure.. restricted event analyst users could delete the searches and enhance their access privileges..1 Sourcefire 3D System Administrator Guide 309 . time zone. Select Operations > User Management.. Click Edit next to the user to whom you want to grant restricted event analyst rights. 2..

Intrusion Event Analyst. Intrusion Event Analyst (Read Only). 4. IMPORTANT! You cannot select Restricted Event Analyst if Administrator. select Hide Data. you have three choices: • • • To grant access to all events for a category. If the user you want to modify does not already have the Restricted Event Analyst option enabled.1 Sourcefire 3D System Administrator Guide 310 .9. To deny access to all events in a category. they appear on this page. Click Save to save your changes and return to the User Management page. select Show All Data. select the search that you want to use to restrict the user account. IMPORTANT! If you created any custom tables on the Defense Center. Version 4. The Restrictions section of the page appears. 5.Managing Users Managing User Accounts Chapter 8 3. or RNA Event Analyst (Read Only) access is enabled. select Restricted Event Analyst. RNA Event Analyst. To grant access to events that match a specific saved search. The Defense Center version of the page is shown below. For each row.

Note that you must manage externally authenticated user passwords on the LDAP or RADIUS server. 3. In the Password field. To change a user’s password: Access: Admin 1. click Reset Password next to the user account on the User Management page.9. type the new password (up to 32 alphanumeric characters). Version 4. The User Management page appears. Next to the user name.Managing Users Managing User Accounts Chapter 8 Modifying User Passwords Requires: DC/MDC or 3D Sensor You can modify user passwords from the User Management page for internally authenticated users. 2. click Edit. Select Operations > User Management. TIP! If you want to force a user to change the password on the next log-in. The Edit User page appears.1 Sourcefire 3D System Administrator Guide 311 .

see Configuring User Roles on page 304. For more information on user roles. In the Confirm Password field. which cannot be deleted. It cannot be a word that appears in a dictionary or contain consecutive repeating characters. re-type the new password. 6.Managing Users Managing User Accounts Chapter 8 4. Make any other changes you want to make to the user configuration: • • For more information on password options. Click Save. Next to the user whose account you want delete. The account is deleted. the password must have at least eight alphanumeric characters of mixed case. 2. 5. with at least one number. User Account Privileges Requires: DC/MDC or 3D Sensor The following sections provide a list of the menus and toolbar options in Sourcefire 3D System and the user account privileges required to access them. • • • • Analysis & Reporting Menu on page 313 Policy & Response Menu on page 316 Operations Menu on page 317 Toolbar Options on page 319 Version 4.9. see Access Requirements Conventions on page 39. To delete a user account: Access: Admin 1. For more information on the access notations used in the tables that follow and throughout this documentation. The password is changed and any other changes saved. see Managing User Password Settings on page 303.1 Sourcefire 3D System Administrator Guide 312 . The User Management page appears. with the exception of the admin account. Deleting User Accounts Requires: DC/MDC or 3D Sensor You can delete user accounts from the system at any time. Select Operations > User Management. click Delete. IMPORTANT! If password strength checking is enabled for the user account.

Users with only Rules or Maintenance access cannot see the Analysis & Reporting menu at all.9.1 Sourcefire 3D System Administrator Guide 313 . Analysis & Reporting Menu Menu Admin Maint RNA/ RNA-RO Event Analyst X IPS/ IPS-RO Event Analyst X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Restricted Event Analyst P&R Admin Event Summary Intrusion Event Statistics Event Graphs Dashboards RNA Statistics Flow Summary IPS Events Reviewed Events Clipboard Incidents RNA Network Map | Hosts Network Map | Network Devices Network Map | Services Network Map | Vulnerabilities Network Map | Host Attributes X X X X X X X X X X X X X X X X X X Version 4. An X indicates that the user can access the option.Managing Users Managing User Accounts Chapter 8 Analysis & Reporting Menu Requires: IPS or DC/ MDC The Analysis & Reporting Menu table lists the user account privileges required to access each option on the Analysis & Reporting menu.

1 Sourcefire 3D System Administrator Guide 314 .Managing Users Managing User Accounts Chapter 8 Analysis & Reporting Menu (Continued) Menu Admin Maint RNA/ RNA-RO Event Analyst X X X X X X X X X X X X X X X X X X X X X X X X IPS/ IPS-RO Event Analyst Restricted Event Analyst P&R Admin RNA Events Hosts Host Attributes Services Client Applications Flow Data Vulnerabilities RUA Users RUA Events Compliance Compliance Events White List Events White List Violations Custom Tables Searches Audit Log Client Applications Compliance Events Flow Data Health Events X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Version 4.9.

1 Sourcefire 3D System Administrator Guide 315 .9.Managing Users Managing User Accounts Chapter 8 Analysis & Reporting Menu (Continued) Menu Admin Maint RNA/ RNA-RO Event Analyst X X X X IPS/ IPS-RO Event Analyst Restricted Event Analyst P&R Admin Host Attributes Hosts Intrusion Events Remediation Status RNA Events RUA Events Scan Results Services SEU Import Log Users Vulnerabilities White List Events White List Violations Custom Workflows Bookmarks Report Profiles X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Version 4.

or Maintenance access can not see the Policy & Response menu at all. RNA Event Analyst. Policy & Response Menu Menu Admin Maint RNA/ RNA-RO Event Analyst IPS/ IPS-RO Event Analyst Res. An X indicates that the user can access the option.Managing Users Managing User Accounts Chapter 8 Policy & Response Menu Requires: IPS or DC/ MDC The Policy & Response Menu table lists the user account privileges required to access each option on the Policy & Response menu.1 Sourcefire 3D System Administrator Guide 316 . Users with Intrusion Event Analyst. Event Analyst P&R Admin IPS Intrusion Policy SEU Rule Editor Email OPSEC RNA Detection Policy Host Attributes RNA Detectors Custom Fingerprinting Custom Product Mappings User 3rd Party Mappings Network Map | Custom Topology Compliance Policy Management Rule Management X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Version 4.9.

An X indicates that the user can access the option. Operations Menu Menu Admin Maint RNA/ RNA-RO Event Analyst IPS/ IPS-RO Event Analyst Res. Event Analyst P&R Admin Configuration RNA/RUA Event Purge Detection Engines High Availability eStreamer Login Authentication X X X X X X X Version 4. All users can access at least some options on the Operations menu.1 Sourcefire 3D System Administrator Guide 317 .9.Managing Users Managing User Accounts Chapter 8 Policy & Response Menu (Continued) Menu Admin Maint RNA/ RNA-RO Event Analyst IPS/ IPS-RO Event Analyst Res. Event Analyst P&R Admin White List Traffic Profiles Responses Alerts Impact Flag Alerts RNA Event Alerts Remediations Groups X X X X X X X X X X X X X X X X Operations Menu Requires: DC/MDC or 3D Sensor The Operations Menu table lists the user account privileges required to access each option on the Operations menu.

Managing Users Managing User Accounts Chapter 8 Operations Menu (Continued) Menu Admin Maint RNA/ RNA-RO Event Analyst IPS/ IPS-RO Event Analyst Res. Event Analyst P&R Admin RUA Sensors User Management System Settings System Policy Update Monitoring Statistics Performance | IPS Performance | RNA Audit Task Status Syslog Health Tools Scheduling Backup/Restore Import/Export Whois Scan Results Scanners X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Version 4.9.1 Sourcefire 3D System Administrator Guide 318 .

Managing Users Managing User Accounts Chapter 8 Operations Menu (Continued) Menu Admin Maint RNA/ RNA-RO Event Analyst X X X X X IPS/ IPS-RO Event Analyst X X X X X Res.9. Toolbar Options Menu Admin Maint RNA/ RNA-RO Event Analyst X X X X X X X X X X X X IPS/ IPS-RO Event Analyst X X X X X X X X X X X X X X X X X X X X X Res. Event Analyst P&R Admin Health Preferences Preferences | Home Page Preferences | Event View Settings Preferences | Change Password Preferences | Time Zone Settings Help Logout X X X X X X X X X X X Version 4. An X indicates that the user can access the option. Event Analyst X X X X X P&R Admin Help About Online Email Support Support Site X X X X X X X X X X X X X X X Toolbar Options Requires: DC/MDC or 3D Sensor The Toolbar Options table lists the user account privileges required to access each option on the toolbar and its sub-menus.1 Sourcefire 3D System Administrator Guide 319 . All users can access at least some of the options on the toolbar.

9. your organization’s security policies may require that Version 4. For example.1 Sourcefire 3D System Administrator Guide 320 . including multiple fingerprint and subnet detection settings RUA settings synchronizing time serving time from the Defense Center mapping vulnerabilities for services You can use a system policy to control the aspects of your Defense Center that are likely to be similar for other Sourcefire 3D System appliances in your deployment.Managing System Policies Chapter 9 Administrator Guide A system policy allows you to manage the following on your Defense Center or 3D Sensor: • • • • • • • • • • • • • • • • access control lists audit log settings authentication profiles dashboard settings database event limits detection policy preferences DNS cache properties the mail relay host and notification address tracking intrusion policy changes specifying a different language custom login banners RNA settings.

you can set the login banner once in a system policy on a Defense Center and then apply the policy to all the sensors that it manages. you can export a system policy from another appliance and then import it onto your appliance. Next. which controls aspects of an appliance that are likely to be similar across a deployment. See the following sections for more information: • • • • Creating a System Policy on page 321 Editing a System Policy on page 323 Applying a System Policy on page 324 Deleting System Policies on page 325 Creating a System Policy Requires: Any When you create a system policy. You can then edit the imported policy to suit your needs before you apply it. With system policies. IMPORTANT! You cannot apply system policies to Crossbeam-based software sensors or Intrusion Agents. or if you want to test different database limits. Contrast a system policy. you assign it a name and a description. For more information.9.Managing System Policies Creating a System Policy Chapter 9 your appliances have a “No Unauthorized Use” message when a user logs in. You can also benefit from having multiple policies on a 3D Sensor. you configure the various aspects of the policy. Version 4. each of which is described in its own section. which are likely to be specific to a single appliance. if you have different mail relay hosts that you use under different circumstances. See Configuring System Settings on page 360 for more information. Instead of creating a new policy. you can create several system policies and switch between them rather than editing a single policy.1 Sourcefire 3D System Administrator Guide 321 . For example. with system settings. see Importing and Exporting Objects on page 583.

5.9.1 Sourcefire 3D System Administrator Guide 322 . Click Create Policy. From the drop-down list. 3. see one of the following sections: • • • • • • • • • • • • Configuring the Access List for Your Appliance on page 325 Configuring Audit Log Settings on page 327 Configuring Authentication Profiles on page 329 Configuring Dashboard Settings on page 331 Configuring Database Event Limits on page 332 Configuring Detection Policy Preferences on page 336 Configuring DNS Cache Properties on page 337 Configuring a Mail Relay Host and Notification Address on page 338 Configuring Intrusion Policy Preferences on page 339 Specifying a Different Language on page 340 Adding a Custom Login Banner on page 341 Configuring RNA Settings on page 342 Version 4. 4. The Policy Name column includes its description. The System Policy page appears. The Create page appears. select an existing policy to use as a template for your new system policy. The Applied To column indicates the number of appliances where the policy is applied and a count of out-of-date appliances where the previously applied policy has changed and should be reapplied.Managing System Policies Creating a System Policy Chapter 9 To create a system policy: Access: Admin 1. 2. Your system policy is saved and the Access List page appears. For information about configuring each aspect of the system policy. Type a name and description (up to 40 alphanumeric characters and spaces each) for your new policy. Select Operations > System Policy. Click Save.

9. For information about configuring each aspect of the system policy. Click Edit next to the system policy that you want to edit. appears. but remember to re-apply the policy as explained in Applying a System Policy on page 324. see one of the following sections: • • • • • • • • • • • • • • • Configuring the Access List for Your Appliance on page 325 Configuring Audit Log Settings on page 327 Configuring Authentication Profiles on page 329 Configuring Dashboard Settings on page 331 Configuring Database Event Limits on page 332 Configuring Detection Policy Preferences on page 336 Configuring DNS Cache Properties on page 337 Configuring a Mail Relay Host and Notification Address on page 338 Configuring Intrusion Policy Preferences on page 339 Specifying a Different Language on page 340 Adding a Custom Login Banner on page 341 Configuring RNA Settings on page 342 Configuring RNA Subnet Detection Settings on page 349 Configuring RUA Settings on page 352 Synchronizing Time on page 354 Version 4. With the Policy Name and Policy Description fields at the top. To edit an existing system policy: Access: Admin 1. Select Operations > System Policy.Managing System Policies Editing a System Policy Chapter 9 • • • • • Configuring RNA Subnet Detection Settings on page 349 Configuring RUA Settings on page 352 Synchronizing Time on page 354 Serving Time from the Defense Center on page 357 Mapping Vulnerabilities for Services on page 358 Editing a System Policy Requires: Any You can edit a system policy that is currently in use. the first section of the system policy. Access List. You can change the policy name and description. The System Policy page appears. including a list of the existing system policies. 2.1 Sourcefire 3D System Administrator Guide 323 .

model. the Apply page appears. The System Policy page appears. the Defense Center itself.9. 3. your settings do not take effect until you apply it. A message appears indicating that the task is added to the task queue. IMPORTANT! You cannot apply system policies to Crossbeam-based software sensors or Intrusion Agents. make sure you apply the updated policy when you are finished. If a policy has been updated since it was applied. Click Apply next to the system policy that you want to apply. You can also select an entire group. On the 3D Sensor. select the sensors. TIP! You can sort the sensors by sensor group. type of sensor. To apply a system policy: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 324 . Select Operations > System Policy. Applying a System Policy Requires: Any After you create or edit a system policy. Version 4. including a list of the existing system policies. On the Defense Center. See Applying a System Policy on page 324.Managing System Policies Applying a System Policy Chapter 9 • • Serving Time from the Defense Center on page 357 Mapping Vulnerabilities for Services on page 358 IMPORTANT! If you are editing the current system policy. Click Apply. 4. where you want to apply the system policy. and. if required. the name of the policy appears in italics. 2. or previously applied policy. On the Defense Center. the system policy is applied.

port 443 (Hypertext Transfer Protocol Version 4. Default system policies cannot be deleted. To delete a system policy: Access: Admin 1.9. For information about configuring each aspect of the system policy. 2. it is used until a new policy is applied. If the policy is still in use. including a list of the existing system policies. Configuring the Parts of Your System Policy Requires: Any You can change various parts of your system policy. Select Operations > System Policy. The System Policy page appears.1 Sourcefire 3D System Administrator Guide 325 . The policy is deleted. Click Delete next to the system policy that you want to delete. see one of the following sections: • • • • • • • • • • • • • • • • • Configuring the Access List for Your Appliance on page 325 Configuring Audit Log Settings on page 327 Configuring Authentication Profiles on page 329 Configuring Dashboard Settings on page 331 Configuring Database Event Limits on page 332 Configuring Detection Policy Preferences on page 336 Configuring DNS Cache Properties on page 337 Configuring a Mail Relay Host and Notification Address on page 338 Configuring Intrusion Policy Preferences on page 339 Specifying a Different Language on page 340 Adding a Custom Login Banner on page 341 Configuring RNA Settings on page 342 Configuring RNA Subnet Detection Settings on page 349 Configuring RUA Settings on page 352 Synchronizing Time on page 354 Serving Time from the Defense Center on page 357 Mapping Vulnerabilities for Services on page 358 Configuring the Access List for Your Appliance Requires: Any The Access List page allows you to control which computers can access your appliance on specific ports. By default.Managing System Policies Deleting System Policies Chapter 9 Deleting System Policies Requires: Any You can delete a system policy even if it is in use.

3. or SSH). consider adding access to the appliance for specific IP addresses and then deleting the default any option. click Edit next to the system policy. which is used to access the web interface and port 22 (Secure Shell. or HTTPS). the Access List page appears. WARNING! If you delete access for the IP address that you are currently using to connect to the appliance interface (and if there is no entry for “IP=any port=443”). Provide a name and description for the system policy as described in Creating a System Policy on page 321. access to the appliance is not restricted. The setting is removed. To delete one of the current settings. 2. In either case.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 Secure. are enabled for any IP address. Select Operations > System Policy. you will lose access to the system when you apply the policy.1 Sourcefire 3D System Administrator Guide 326 . click Create Policy. To configure the access list: Access: Admin 1. click Delete. The access list is part of the system policy. You can specify the access list either by creating a new system policy or by editing an existing policy. WARNING! By default. The System Policy page appears. In either case. To configure the access list as part of a new system policy. and click Save. the access list does not take effect until you apply the system policy. which is used to access the command line.9. You have two options: • • To modify the access list in an existing system policy. Version 4. To operate the appliance in a more secure environment.

In the IP Address field. 192.1 Sourcefire 3D System Administrator Guide 327 . click Add. use the following syntax depending on the IP addresses you want to add: • • an exact IP address (for example.9. to designate any IP address 6.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 4. The Add IP Address page appears. a severity. The appliance does not send the audit log until you apply the system policy.1/24) For information on using CIDR in the Sourcefire 3D System. Configuring Audit Log Settings Requires: Any You can configure the system policy so that the appliance streams an audit log to an external host.1.101) an IP address range using CIDR notation (for example.1. IMPORTANT! You must ensure that the external host is functional and accessible from the appliance sending the audit log. 7. The system policy is updated. reflecting the changes you made. To add access for one or more IP addresses. then click Add. See Applying a System Policy on page 324 for more information. The Access List page appears again. TIP! You can click Add to add access for additional IP addresses or click Delete to remove access from other IP addresses. see IP Address Conventions on page 41. Version 4. • any. Select SSH. HTTPS.168. 5.168. The name of the sending host is part of the sent information and you can further identify the audit log stream with a facility. or both to specify which ports you want to enable for these IP addresses. and an optional tag. Your changes do not take effect until you apply the system policy. 192. Click Save Policy and Exit.

1. Optionally. you can select any of the standard syslog facility and severity settings.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 To configure the audit log settings: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 328 .1. For example: Mar 01 14:45:24 localhost [TAG] Dev-DC3000: admin@10. Label the audit data that you are sending with a facility and severity. [Action] where the local date. Provide a name and description for the system policy as described in Creating a System Policy on page 321. Click Audit Log Settings. Your changes do not take effect until you apply the system policy to the Defense Center and its managed sensors. The default port (514) is used. 2. In either case. and the sending device name precedes the audit log message. However. 4. The system policy is updated. You have two options: • • To modify the audit log settings in an existing system policy. The default for Facility is USER. The following is an example of the output structure: Date Time Host [Tag] Sender: [User_Name]@[User_IP]. Select Operations > System Policy. Version 4. time. Select Enabled next to Send Audit Log to Syslog. and click Save. Designate the destination host for the audit information by using the IP address or the fully qualified name of the host in the Host field. [Subsystem]. 6. The System Policy Page appears. the appliance may the send audit log to the host. but it will not be accepted. Otherwise. the Access List page appears. Operations > Monitoring. See Applying a System Policy on page 324 for more information. 7. 5. 3. the syslog messages are sent. Click Save Policy and Exit. WARNING! The computer you configure to receive an audit log must be set up to accept remote messages. After you apply a policy with this feature enabled and your destination host is configured to accept the audit log. click Create Policy. insert a reference tag in the TAG field.2. click Edit next to the system policy.9. To configure the audit log settings as part of a new system policy. The default setting is Disabled. Page View 8. The default for Severity is INFO. and hostname precede the bracketed optional tag.

See Configuring Attribute Mapping on page 274 for more information. the appliance then checks the external server for a set of matching credentials. For a complete procedure for logging in initially as an externally authenticated user. Once you apply the policy to a Version 4. their account is listed on the User Management page. After a user attempts to log in. the appliance does not revert to checking the local database. you can apply the system policy to let users logging into the Defense Center or managed sensor authenticate to that server rather than using the local database. if you set up an authentication profile that retrieves only users in the Network Security group in your company. you would probably want to leave the default role unselected. if a user has internal authentication enabled and the user credentials are not found in the internal database. In addition. then later modify the policy to use different default user roles and re-apply. as long as those roles can be combined.1 Sourcefire 3D System Administrator Guide 329 . where you can edit the account settings to grant additional permissions. any user accounts created before the modification retain the first user role until you modify or delete and recreate them. Note that when you create an LDAP authentication object on your Defense Center. the appliance verifies the user credentials by comparing them to a user account stored in the Defense Center or managed sensor’s local database. you can set the default user role for any user whose account is externally authenticated. However.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 Configuring Authentication Profiles Requires: DC/MDC Normally. if your authentication profile retrieves records for other personnel in addition to the security group. For more information on modifying a user account. However. For example. The Authentication Profiles page only displays in the system policy on a Defense Center. if you create an authentication object referencing an external authentication server. see Understanding User Privileges on page 267. Note.9. you may set the default user role to include both the Intrusion Event Analyst role and the RNA Event Analyst so users can access collected event data without any additional user configuration on your part. If no access role is selected. you can set a filter search attribute to specify the set of users who can successfully authenticate against the LDAP server. when a user logs into a Sourcefire 3D System Defense Center or managed sensor. You can enable authentication in a system policy on your Defense Center and then push that policy to managed sensors. the appliance verifies the user credentials against users on an LDAP or RADIUS server. If you configure the system policy to use one user role and apply the policy. For more information on available user roles. see Logging into the Appliance to Set Up an Account on page 23. If a user has the same username on multiple systems. all passwords across all servers work. however. When you apply a policy with authentication enabled to an appliance. When you enable authentication. that if authentication fails on the available external authentication servers. users can log in but cannot access any functionality. see Modifying User Privileges and Options on page 306. You can select multiple roles.

the user logs in successfully. If the username and password match results from an external server. If an external user attempts to log in. To enable authentication of users on external servers: Access: Admin 1. select Operations > System Policy. click Create Policy. Version 4. The System Policy page appears. click Edit next to the system policy. In either case. If a match is found. the system policy on the sensor does not display authentication profile settings. you can either disable it in a system policy on the Defense Center and push that to the sensor or apply a local system policy (which cannot contain authentication profile settings) on the sensor. the appliance then checks the username and password against the local database. 2.1 Sourcefire 3D System Administrator Guide 330 . and external authentication is enabled. the user login attempt is rejected. To configure the authentication profile settings as part of a new system policy. you have to modify the policy on the Defense Center and then push it to the sensor again. and click Save.9. the Access List page appears. Note that you can only enable external authentication on Defense Centers and 3D Sensors. If the login fails. the appliance first checks if that user is in the local user database. Provide a name and description for the system policy as described in Creating a System Policy on page 321. so you cannot manage them on the sensor itself. the appliance checks the user against each external authentication server in the authentication order shown in the system policy.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 sensor. the user logs in successfully. If the user exists. the appliance checks the username and password against the external database. If the user is a new external user. eligible externally authenticated users can log into the sensor. If a match is found. However. Enabling external authentication by applying a system policy is not supported on the following sensor types: • • • • 3Dx800 sensors Crossbeam-based software sensors Intrusion Agents RNA Software for Red Hat Linux If a user with internal authentication attempts to log in. an external user account is created in the local database with the default privileges for the external authentication object. On the Defense Center. To make changes to the authentication profile settings. the appliance changes the user to an external user with the default privileges for that authentication object. External users cannot authenticate against the user list in the local database. To disable authentication on a managed sensor. If the login fails. You have two options: • • To modify the authentication profile settings in an existing system policy. however.

Note that although you can select both an event analyst role and the corresponding read-only event analyst role. 5. Click Save Policy and Exit.1 Sourcefire 3D System Administrator Guide 331 . 4. only the analyst role is applied.9. 9. use the up and down arrows to change the order in which authentication servers are accessed when an authentication request occurs. To enable use of an authentication object. The Authentication Profiles page appears. Optionally. Your changes do not take effect until you apply the system policy to the Defense Center and its managed sensors. Click Authentication Profiles.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 3. select a user role to define the default permissions you want to grant to users authenticated externally. The system policy is updated. select Enabled from the Shell Authentication drop-down list. 8. select Enabled. If you want to use the external server to authenticate shell access accounts as well. IMPORTANT! You must enable at least one authentication object to enable external authentication. Configuring Dashboard Settings Requires: Any You can configure the system policy so that Custom Analysis widgets are enabled on the dashboard. click Enable next to the object. 6. From the Status drop-down list. Dashboards provide you with at-a-glance views of current Version 4. From the Default User Role drop-down list. See Applying a System Policy on page 324 for more information. 7. TIP! Press Ctrl before selecting roles to select multiple default user roles. Remember that shell access users can only authenticate against the server whose authentication object is highest in the profile order.

for some databases.1 Sourcefire 3D System Administrator Guide 332 . See Deleting System Policies on page 325for more information. The Custom Analysis widget allows you to create a visual representation of events based on a flexible. You have two options: • • To modify the dashboard settings in an existing system policy. By default. In either case. Select Operations > System Policy. Click Save Policy and Exit. To improve performance. click Create Policy. click Edit next to the system policy. one day’s history). Custom Analysis widget use is enabled 5. The System Policy page appears. The Dashboard Settings page appears. Your changes do not take effect until you apply the system policy. Provide a name and description for the system policy as described in Creating a System Policy on page 321. in the case of the compliance violation history database. and click Save. Select the Enable Custom Analysis Widgets check box to allow users to add Custom Analysis widgets to dashboards. you should try to tailor the database event limit to the number of events you regularly work with.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 system status through the use of widgets: small. To configure the dashboard settings as part of a new system policy. 4. the minimum number of records you can store in any database is one record (or. the Access List page appears. clear the check box to prohibit users from using those widgets. However. The system policy is updated. self-contained components that provide insight into different aspects of the Sourcefire 3D System. Click Dashboard. See Understanding the Custom Analysis Widget on page 69 for more information on how to use custom widgets.9. Configuring Database Event Limits Requires: Any You can use the Database page to specify the maximum number of events you want to store on an appliance. you can choose not to store any events. To enable Custom Analysis widgets: Access: Admin 1. 3. In most cases. Version 4. 2. user-configurable query of the events in your appliance's database.

intrusion events on a Defense Center or on a Master Defense Center (which is always a DC3000) intrusion events on a 3D Sensor And can store up to. the maximum limit for the appliance is silently enforced.9. if you use the Defense Center to apply the same system policy to itself and the 3D Sensors it manages. or DC1000 100 million events on the DC3000 1 million events RNA Flow Summary Database Compliance & White List Event Database Health Event Database RNA flow summaries (aggregated RNA flows) on a Defense Center compliance events and white list events on a Defense Center or Master Defense Center health events on a Defense Center or Master Defense Center 1 million events Version 4. Virtual Defense Center. Intrusion Event Database (Defense Center or Master Defense Center) Intrusion Event Database (3D Sensor) RNA Event Database RNA Flow Database Is the database that stores.. or DC1000 100 million events on the DC3000 10 million events on the DC500..Managing System Policies Configuring the Parts of Your System Policy Chapter 9 These databases include those that store RNA and RUA events. Database Event Limits The.... The Database Event Limits on page 333 below describes the maximum number of records you can store in the databases on your appliance. 2. Virtual Defense Center. any health alert limits you set in the policy have no effect on the sensors. if you specify 100 million intrusion events and apply that policy to a 3D Sensor). For example. as well as flow events. flow summaries.. database limits that do not apply to a particular appliance are silently ignored. Note that if you apply a system policy to an appliance that does not support the maximum limit you specify (for example. In addition.5 million events on the DC500 10 million events on the Virtual Defense Center or the DC1000 100 million events on the DC3000 2 million events RNA network discovery events on a Defense Center RNA flows on a Defense Center 10 million events 10 million events on the DC500. IMPORTANT! You cannot apply system policies to Crossbeam-based software sensors or Intrusion Agents. and health events.1 Sourcefire 3D System Administrator Guide 333 .

In either case. The System Policy page appears.1 Sourcefire 3D System Administrator Guide 334 .9. click Create Policy. Select Operations > System Policy.. click Edit next to the system policy. on a Defense Center RUA events on a Defense Center RUA storage of user logins on a Defense Center SEU import log records And can store up to. and click Save. the Access List page appears.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 Database Event Limits (Continued) The. For information on manually pruning the RNA and RUA databases. You have two options: • • To modify the database settings in an existing system policy. see Purging the RNA and RUA Databases on page 598. audit records remediation status events on a Defense Center the white list violation history of the hosts on your network. Version 4. In addition.. unified files are deleted from the system...000 records 10 million events a 30-day history of violations 10 million events 10 million user login records 1 million records Note that if the number of events in the intrusion event database exceeds the maximum. 2. the oldest events and packet files are pruned until the database is back within limits.. Provide a name and description for the system policy as described in Creating a System Policy on page 321. To configure the database settings as part of a new system policy.. beginning with the oldest files. Audit Event Database Remediation Status Event Database White List Violation History Database RUA Event Database RUA History Database SEU Import Log Database Is the database that stores. To configure the maximum number of records in the database: Access: Admin 1. See Configuring a Mail Relay Host and Notification Address on page 338 for information about generating automated email notifications when events are automatically pruned. 100. if the /volume disk partition reaches 85% of its capacity.

see Database Event Limits on page 333. Click Database. The following graphic shows the Database page on a DC1000 Defense Center. 4.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 3. For information on how many records each database can maintain.1 Sourcefire 3D System Administrator Guide 335 . Version 4. The Database page appears. For each of the databases.9. enter the number of records you want to store.

Version 4.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 5. If you enable this setting. Configuring Detection Policy Preferences Requires: Any The Detection Policy Preferences page allows you to configure whether you must confirm your action when you apply RNA detection policies and intrusion policies. The system policy is updated. In either case. 4.9.1 Sourcefire 3D System Administrator Guide 336 . The appliance also warns you if the detection engine has a different policy applied to it than the one you are attempting to apply. The Detection Policy Preferences page appears. See Applying a System Policy on page 324 for more information. Click Save Policy and Exit. The System Policy page appears. click Create Policy. See Applying a System Policy on page 324 for more information. 2. To configure the detection policy preferences as part of a new system policy. To configure detection policy preferences: Access: Admin 1. The system policy is updated. If no. Provide a name and description for the system policy as described in Creating a System Policy on page 321. the appliance prompts you to confirm that you want to apply the policy. Select Operations > System Policy. Your changes do not take effect until you apply the system policy. 5. Click Detection Policy Preferences. select Yes from the drop-down list. 3. and click Save. whenever you apply an RNA detection policy or an intrusion policy to one or more detection engines. Click Save Policy and Exit. click Edit next to the system policy. Do you want to confirm your action when you apply RNA detection policies and intrusion policies? • • If yes. the Access List page appears. select No from the drop-down list. You have two options: • • To modify the detection policy preferences in an existing system policy. Your changes do not take effect until you apply the system policy.

IMPORTANT! DNS resolution caching is a system-wide setting that allows the caching of previously resolved DNS lookups. and click Save. click Create Policy.9. see Configuring Network Settings on page 377. For information about configuring event preferences. enter the number of minutes a DNS entry remains cached in memory before it is removed for inactivity. you can configure the appliance to resolve IP addresses automatically on the event view pages. To configure IP address resolution on a per-user-account basis. 3. 5. The System Policy page appears. To configure the DNS cache properties: Access: Admin 1. In the DNS Cache Timeout field. The default setting is 300 minutes (five hours).Managing System Policies Configuring the Parts of Your System Policy Chapter 9 Configuring DNS Cache Properties Requires: Any If you have a DNS server configured on the Network page. enable Resolve IP Addresses. In either case. the Access List page appears. Select Operations > System Policy. Click DNS Cache. Provide a name and description for the system policy as described in Creating a System Policy on page 321. Version 4.1 Sourcefire 3D System Administrator Guide 337 . users must also select Event View Settings from the User Preferences menu. and then click Save. click Edit next to the system policy. To configure the DNS cache settings as part of a new system policy. Next to DNS Resolution Caching. see Configuring Event View Settings on page 27. As an administrator. Configuring DNS caching allows you to identify IP addresses you previously resolved without performing additional lookups. 4. 2. The DNS Cache page appears. You have two options: • • To modify the DNS cache settings in an existing system policy. you can also configure basic properties for DNS caching performed by the appliance. select Enabled to enable caching or Disabled to disable it. This can reduce the amount of traffic on your network and speed the display of event pages when IP address resolution is enabled. For information about configuring DNS servers.

requires IPS) use email for health event alerting (Defense Center only) you must configure a mail host. See Applying a System Policy on page 324 for more information. In addition.1 Sourcefire 3D System Administrator Guide 338 . Your changes do not take effect until you apply the system policy. click Edit next to the system policy. Configuring a Mail Relay Host and Notification Address Requires: Any If you plan to: • • • • • email event-based reports email status reports for scheduled tasks use email for RNA event. the Access List page appears. WARNING! Although DNS caching is enabled for the appliance. Provide a name and description for the system policy as described in Creating a System Policy on page 321. you can configure an email address that will receive notifications when intrusion events and audit logs are pruned from the database. Version 4.requires RNA) use email for intrusion event alerting (Defense Center only . and compliance event alerting (Defense Center only . In either case. Select Operations > System Policy. The System Policy page appears. IP address resolution is not enabled on a per-user basis unless it is configured on the Events page accessed from the User Preferences menu. Click Save Policy and Exit. The system policy is updated. To configure a mail relay host: Access: Admin 1. 2. To configure the email settings as part of a new system policy. impact flag. and click Save. You have two options: • • To modify the email settings in an existing system policy.9.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 6. click Create Policy.

See Applying a System Policy on page 324 for more information. You have two options: • • To modify the intrusion policy preferences in an existing system policy. Click Save Policy and Exit. The System Policy page appears. In either case. the Access List page appears. 3. Configuring Intrusion Policy Preferences Requires: Any You can allow or require comments to be added to the audit log when an intrusion policy changes. Version 4. Provide a name and description for the system policy as described in Creating a System Policy on page 321. The Configure Email Notification page appears. To configure the intrusion policy preferences as part of a new system policy. click Edit next to the system policy.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 3. and click Save. Optionally. The system policy is updated. Select Operations > System Policy. Your changes do not take effect until you apply the system policy. In the Mail Relay Host field.9. click Create Policy. 4. Click Email Notification. Click Intrusion Policy Preferences.1 Sourcefire 3D System Administrator Guide 339 . The Intrusion Policy Preferences page appears. enter the email address you want to receive notifications when intrusion events and audit logs are pruned from the appliance’s database. 6. 2. IMPORTANT! The mail host you enter must allow access from the appliance. To configure intrusion policy change tracking: Access: Admin 1. 5. You can also track all changes to intrusion policies in the audit log. type the hostname or IP address of the mail server you want to use. in the Data Pruning Notification Address field.

The System Policy page appears. 6. See Applying a System Policy on page 324 for more information. The system policy is updated. Select Disabled.1 Sourcefire 3D System Administrator Guide 340 . The Language page appears. WARNING! The language you select here is used for the web interface for every user who logs into the appliance. and click Save. 2. To select a different language for the user interface: Access: Admin 1. Version 4. 3.9. Provide a name and description for the system policy as described in Creating a System Policy on page 321. Click Save Policy and Exit. 4.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 4. the Access List page appears. click Create Policy. In either case. If you select Optional or Required. Your changes do not take effect until you apply the system policy. select Write changes in Intrusion Policy to audit log. Specifying a Different Language Requires: Any You can use the Language page to specify a different language for the web interface. a Description of Changes text box appears when you commit your intrusion policy changes. Select the language you want to use. You have two options: • • To modify the language settings in an existing system policy. Optionally. if you want to track changes to intrusion policies. To configure the language settings as part of a new system policy. click Edit next to the system policy. Click Language. or Required from the Comments on policy change drop-down list. Select Operations > System Policy. 5. Optional.

Select Operations > System Policy. Click Save Policy and Exit. Your changes do not take effect until you apply the system policy. The System Policy page appears. 3. click Edit next to the system policy. See Applying a System Policy on page 324 for more information. To add a custom banner: Access: Admin 1. Custom login banners are part of the system policy. The Login Banner page appears. Click Login Banner. In the Custom Login Banner field. Version 4. Provide a name and description for the system policy as described in Creating a System Policy on page 321. Adding a Custom Login Banner Requires: Any You can create a custom login banner that appears when users log into the appliance using SSH and on the login page of the web interface. and click Save. click Create Policy. Banners can contain any printable characters except the less-than symbol (<) and the greaterthan symbol (>). The system policy is updated. the Access List page appears. enter the login banner that you want to use with this system policy. 4.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 5. the login banner is not used until you apply the system policy. In either case. 2. In either case. You have two options: • • To modify the login banner in an existing system policy. You can specify the login banner either by creating a new system policy or by editing an existing policy.9.1 Sourcefire 3D System Administrator Guide 341 . To configure the login banner as part of a new system policy.

9. in minutes. including how RNA stores data. The default setting is 10080 minutes (7 days). whether operating system and service identity conflicts are automatically resolved. See Applying a System Policy on page 324 for more information. make sure that the host timeout value is longer than the update interval in the RNA detection policy. The default setting is 10080 minutes (7 days). whether identity conflict events are logged. Version 4. Configuring RNA Settings Requires: DC/ MDC + RNA You can configure several aspects of RNA behavior through the system policy. before RNA drops a host from the network map due to inactivity. IMPORTANT! To avoid premature timeout of services. which vulnerability types to use for impact assessment. in minutes. IMPORTANT! To avoid premature timeout of hosts. before RNA drops a service from the network map due to inactivity. see Creating RNA Detection Policies in the Analyst Guide. see Creating RNA Detection Policies in the Analyst Guide. Your changes do not take effect until you apply the system policy. The system policy is updated. For more information. RNA Data Storage Settings Field Host Timeout Description The amount of time that passes. and therefore determine the data that other parts of the Sourcefire 3D System can use. as described in the following table.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 5.1 Sourcefire 3D System Administrator Guide 342 . For more information. control the kinds of RNA data stored in the database. what RNA and host input events are logged. make sure that the service timeout value is longer than the update interval in the RNA detection policy. These settings also control how long data is retained in the network map. and the priority of active sources of identity data. Service Timeout The amount of time that passes. For more information. see the following sections: • • • • Understanding RNA Data Storage Settings on page 342 Understanding Vulnerability Impact Assessment Settings on page 345 Understanding Multiple Fingerprint Settings on page 345 Configuring Settings for RNA on page 347 Understanding RNA Data Storage Settings Requires: DC/ MDC + RNA RNA data storage settings. Click Save Policy and Exit.

before RNA drops a client application from the network map due to inactivity.9. graphs.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 RNA Data Storage Settings (Continued) Field Client Application Timeout Description The amount of time that passes. which can reduce the number of events sent to the Defense Center. Select this check box if you want you want to combine flow summaries involving external hosts. and if they were detected by the same detection engine (for flows detected by 3D Sensor) or were exported by the same NetFlow-enabled device and were processed by the same detection engine. instead of an individual IP address. Event views. However. in minutes. keep in mind that setting this option in the RNA detection policy requires that you set your flow data mode to Summary. IMPORTANT! Make sure that the client application timeout value is longer than the update interval in the RNA detection policy. Drop New Hosts When Host Limit Reached Combine Flows for Out-Of-Network Responders Select this check box if you want new hosts rather than old hosts dropped when the Defense Center reaches its host limit and the network map is full. protocol.1 Sourcefire 3D System Administrator Guide 343 . For more information. However. For more information. see Creating RNA Detection Policies in the Analyst Guide. service. which prevents your 3D Sensors from transmitting individual flows to the Defense Center and therefore prevents you from taking advantage of any feature that requires data from individual flows. This option is especially valuable if you want to prevent spoofed hosts from taking the place of valid hosts in the network map. Enabling this option treats flow summary data from IP addresses that are not in your list of monitored networks (as defined by your RNA detection policy) as coming from a single host. This can reduce the space required to store flow data and can also speed up the rendering of flow data graphs. the table view contains no information. and reports use external to indicate the hosts outside your monitored network. access data on individual flows) for a flow summary that involves an external responder. The Defense Center will combine flow summaries involving a host on your monitored network and one or more external hosts if the flows use the same port. see Combining Flow Summaries from External Responders in the Analyst Guide as well as Configuring RNA Detection Policy Settings in the Analyst Guide. Note that you can also use the RNA detection policy to force your 3D Sensors to combine flow summaries involving external hosts before they transmit the data to the Defense Center. if you enable this option and you attempt to drill down to the table view of flow data (that is. Version 4. The default setting is 10080 minutes(7 days).

each of which is monitoring a separate network segment using separate detection engines. see Drop Duplicate RNA Flow Events. not following best practices can degrade performance as the Defense Center attempts to resolve the conflicts. Duplicate flow events can be created if you use two RNA detection policies. if two NetFlow-enabled devices export information about the same session. Version 4. best practices are to avoid creating duplicate NetFlow events. Just as with RNA flow events.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 RNA Data Storage Settings (Continued) Field Drop Duplicate RNA Flow Events Description Select this check box if you want the Defense Center to drop duplicate flow events generated by 3D Sensors with RNA. each detection engine generates a flow event when RNA detects that a connection is terminated between a monitored host on one of the networks and a monitored host on the other network. Note that best practices are to use only one detection policy and to not overlap network segment coverage. and can also use excessive bandwidth. only the reporting detection engine for the flow initiator generates a flow event. In that scenario.9. for example. Duplicate flow events can also be created if you overlap network segment coverage with your RNA detection engines in your RNA detection policy. On the other hand. Drop Duplicate NetFlow Events Select this check box if you want the Defense Center to drop duplicate flow events that are based on NetFlow data. Duplicate NetFlow events can be created.1 Sourcefire 3D System Administrator Guide 344 . For more information. if you use one policy to monitor both networks.

For example. See Understanding RNA Network Discovery Event Types in the Analyst Guide for information about each event type Expand this section and use the check boxes to specify the types of RNA host input events that you want to log in the database. as described in the following table. the intrusion event will be marked with the red (Vulnerable) impact flag. Note that if you clear all the check boxes. if you scan using Nessus. • Select the Use RNA Vulnerability Mappings check box if you want to use RNA vulnerability information to perform impact flag correlation. see Understanding Nessus Scans in the Analyst Guide or the Sourcefire 3D System Host Input API Guide.1 Sourcefire 3D System Administrator Guide 345 . For more information. • Select the Use Third Party Scanner Vulnerability Mappings check box if you are using an integrated scan capability or the AddScanResult host input API function and you want to use vulnerability lookups from the scanner to perform impact flag correlation. Vulnerability Impact Assessment Settings Field Vulnerabilities to use for Impact Assessment Requires: IPS Description Select the check boxes in this section to configure how the Sourcefire 3D System performs impact flag correlation with intrusion events. • Select the Third Party Vulnerability Mappings check box if you want to use third-party vulnerability references to perform impact flag correlation.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 Understanding Vulnerability Impact Assessment Settings Requires: DC/ MDC + RNA The RNA vulnerability impact assessment settings. Host Input Event Logging Understanding Multiple Fingerprint Settings Requires: DC + RNA RNA matches fingerprints for operating systems and services against patterns in traffic to determine what operating system and which services are running on a particular host. select this option to use the Nessus vulnerability mappings. see Mapping Third-Party Vulnerabilities in the Analyst Guide. You can select any or all of the check boxes in this section. intrusion events will never be marked with the red impact flag.9. To provide the most reliable operating system and service identity information. For more information. RNA collates fingerprint information from several sources. RNA Event Logging Expand this section and use the check boxes to specify the types of RNA network discovery events that you want to log in the database. Version 4. see Using Impact Flags to Evaluate Events in the Analyst Guide. For more information. See Understanding RNA Host Input Event Types in the Analyst Guide for information about each event type. if IPS generates an intrusion event and the Sourcefire 3D System is able to use any of the methods you specified to determine that the host involved in the event is vulnerable to the attack or exploit. control which vulnerability types to use for impact assessment.

or change the priority or timeout settings for existing sources. that user input data overrides scanner and application data regardless of priority. RNA retains one identity for each source. By default. You can add new active sources through this page.9. By default. An identity conflict occurs when RNA detects an identity that conflicts with an existing identity that came from the active scanner or application sources listed on the Multiple Fingerprinting page or from a user. For more information on current identities and how RNA selects the current identity. Note. but only data from the highest priority application or scanner source is used as the current identity. you can set your system to always automatically resolve the conflict by keeping the passive identity or to always resolve it by keeping the active identity. see Enhancing Your Network Map in the Analyst Guide.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 RNA uses all passive data to derive operating system identities and assign a confidence value. Note that adding a scanner to this page does not add the full integration capabilities that exist for the Nmap and Nessus scanners. identity data added by a scanner or application overrides identity data detected by RNA. however. remember to make sure that you map vulnerabilities from the source to the RNA vulnerabilities in the network Version 4. but does allow integration of imported application or scan results. However.1 Sourcefire 3D System Administrator Guide 346 . You can use the Multiple Fingerprinting page to rank scanner and application fingerprint sources by priority. unless there is an identity conflict. identity conflicts are not automatically resolved and you must resolve them through the host profile or by rescanning the host or re-adding new identity data to override the RNA identity. If you import data from a third-party application or scanner. as indicated in the Multiple Fingerprint Settings table.

Type a name for the source. • To change the type of source. click the down arrow next to the source name. click the up arrow next to the source name. select Hours. To specify RNA settings: Access: Admin 1. or Weeks from the Timeout drop-down list and type the appropriate duration. Scanner/ Application List You have several options: • To add a new source. Days. Version 4. select Passive from the Automatically Resolve Conflicts drop-down list.1 Sourcefire 3D System Administrator Guide 347 . click Add in the Multiple Fingerprints page of the system policy. select Active from the Automatically Resolve Conflicts drop-down list. • To use the RNA fingerprint when an identity conflict occurs. • To use the current identity from the highest priority active source when an identity conflict occurs. • To indicate the duration of time that should elapse between the addition of an identity to the network map by this source and the deletion of that identity.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 map. select Disabled from the Automatically Resolve Conflicts drop-down list. • To promote a source and cause the operating system and service identities to be used in favor of sources below it in the list. select Scanner or Application. from the Type drop-down list. The System Policy page appears.9. • To demote a source and cause the operating system and service identities to be used only if there are no identities provided by sources above it in the list. For more information. Multiple Fingerprint Settings Option Generate Identity Conflict Event Automatically Resolve Conflicts Description Enable this option to generate an event when an identity conflict occurs on a host in the network map. Configuring Settings for RNA Requires: DC + RNA Use the following procedure to configure RNA settings in the system policy. Select Operations > System Policy. You have the following options: • To force manual conflict resolution of identity conflicts. see Mapping Third-Party Vulnerabilities in the Analyst Guide.

the Access List page appears.1 Sourcefire 3D System Administrator Guide 348 .9. The RNA Settings page appears. click Edit next to the system policy. You have two options: • • To modify the RNA settings in an existing system policy. 4. click Create Policy. and click Save.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 2. In either case. See the RNA Data Storage Settings table on page 342 for more information. 3. To configure the RNA settings as part of a new system policy. Provide a name and description for the system policy as described in Creating a System Policy on page 321. Click RNA Settings. Specify the RNA data storage settings that you want for your Defense Center. Version 4.

specify the RNA network discovery events that you want to log by clicking the arrow next to RNA Event Logging. you can use the system policy to configure RNA to automatically generate subnet recommendations for your currently applied RNA detection policies on a daily basis. you can configure the Defense Center to automatically update those policies and apply the updated policies to your RNA detection engines. Your changes do not take effect until you apply the system policy.1 Sourcefire 3D System Administrator Guide 349 . Subnet detection allows RNA to make recommendations about which are the best detection engines to analyze the traffic on the various network segments in your organization. which can make it challenging to stay on top of proper RNA policy configurations. you must revisit the detection policy after you apply it for the first time so that you can manually evaluate and apply any subnet recommendations. configure multiple fingerprint settings to manage operating system and service source priorities and identity conflict resolution settings. This is because RNA only gathers secondary information Version 4. 6. Click Save Policy and Exit. Choosing which subnets to monitor with which detection engines is an iterative process that you should revisit from time to time. Unfortunately.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 5. you may not always be kept abreast of network configuration changes. The system policy is updated. If you do not configure the Defense Center to automatically apply subnet recommendations. Optionally. All the event types are enabled by default. 8. your RNA detection policy specifies that each RNA detection engine is configured as the reporting detection engine for the hosts that are closest to it from a network hop standpoint. See the Multiple Fingerprint Settings table on page 347 for more information. See the RNA Network Discovery Event Types table in the Analyst Guide for more information. All the event types are enabled by default. A network administrator may modify a network configuration through routing or host changes without informing you. Optionally. As RNA continuously monitors your network traffic.9. it may be able to refine any subnet recommendations it has made for your RNA detection policies. Alternately. See Applying a System Policy on page 324 for more information. Optionally. Configuring RNA Subnet Detection Settings Requires: DC + RNA Optimally. 7. See the RNA Host Input Event Types table in the Analyst Guide for more information. specify the RNA host input events that you want to log by clicking the arrow next to Host Input Event Logging. as a time-saving and performance-maximizing measure. especially if your network configuration has been altered through routing or host changes. Optionally.

to notify you of any changes made. or. you must explicitly assign an RNA detection engine to monitor that subnet. Version 4. including operating system and service identity data. Note that you can configure the Defense Center to notify you of subnet recommendations via email so that you can make the changes manually.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 (hops and MAC address data) about hosts in subnets that are set to autodetect. To get detailed information about the hosts in a subnet. if you configured the Defense Center to automatically apply recommendations. The following diagram illustrates the automated subnet detection process. and so on. flow data.9.1 Sourcefire 3D System Administrator Guide 350 .

The RNA Subnet Detection Settings page appears. 2. Click RNA Subnet Detection Settings.1 Sourcefire 3D System Administrator Guide 351 . and click Save. select Disabled. To configure RNA subnet detection settings: Access: Admin 1. click Edit next to the system policy. TIP! To receive email notifications. RNA only automatically generates recommendations for RNA deployments running on Version 4. If your RNA deployment includes even one legacy (pre-Version 4. you must configure a valid mail relay host.9. 3. in the Mail Notifications To field. see Introduction to Sourcefire RNA in the Analyst Guide. Provide a name and description for the system policy as described in Creating a System Policy on page 321. 4. see Configuring a Mail Relay Host and Notification Address on page 338.9 and later 3D Sensors. From the Generate Recommendations Daily At drop-down list. The System Policy page appears. select the time when you want RNA to automatically generate daily subnet recommendations for all applied RNA detection policies. click Create Policy.9) 3D Sensor. see Manually Generating Subnet Recommendations in the Analyst Guide. Optionally. 5. you must manually generate and apply recommendations for your RNA detection policies.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 For more information on subnet detection. Version 4. enter the email address where you want to receive notifications of new subnet recommendations. To configure the RNA subnet detection settings as part of a new system policy. For more information. the Access List page appears. In either case. You have two options: • • To modify the RNA subnet detection settings in an existing system policy. IMPORTANT! For performance reasons. Select Operations > System Policy. To disable daily generation of subnet recommendations.

POP3.1 Sourcefire 3D System Administrator Guide 352 . RUA can add users to the database using the following types of detected protocols: • • • • • • LDAP AIM POP3 IMAP Oracle SIP (VoIP) Note that although RUA detects SMTP logins. Click Save Policy and Exit. 7. When RUA detects a user login for a user who is not already in the database. After you reach your licensed limit. and SIP logins always create duplicate user records. and IMAP can introduce usernames not relevant to your organization due to network access from contractors. the Defense Center does not record them unless there is already a user with a matching email address in the database. Configuring RUA Settings Requires: DC + RUA You can use the RUA settings in the system policy to filter which types of network activity cause RUA to add users to the database. RUA users are not added to the database based on SMTP logins. This is because these logins are not associated with any of the user metadata that RUA obtains from an LDAP server. Your changes do not take effect until you apply the system policy. The system policy is updated. AIM. Restricting RUA helps minimize username clutter and preserve RUA licenses. For example. Enable the Automatically Apply Daily Recommendations check box to automatically update and apply your RNA detection policies after RNA generates subnet recommendations. See Applying a System Policy on page 324 for more information.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 6. Sourcefire RUA (see Using Sourcefire RUA in the Analyst Guide) is an optional component of the Sourcefire 3D System that allows you to correlate network activity with user identity information. In addition. obtaining usernames through protocols such as AIM. an RUA user is added to the Defense Center user database. Version 4.9. The RUA feature license on the Defense Center (see Licensing RUA in the Analyst Guide) specifies the number of users you can monitor with RUA. RUA stops adding new users to the Defense Center database. Oracle. Note that this option has no effect unless you enable daily recommendations. visitors. and other guests.

IMPORTANT! Sourcefire RUA Agents installed on Microsoft Active Directory LDAP servers collect only LDAP user login information. Your changes do not take effect until you apply the system policy. Therefore.1 Sourcefire 3D System Administrator Guide 353 . filtering non-LDAP logins has no effect. The RUA Detection Settings page appears.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 nor are they associated with any of the information contained in the other types of login that your 3D Sensors detect. Select the check boxes that correspond to the types of logins that will create RUA users. 4. To filter RUA users based on network activity type: Access: Admin 1. Click RUA Settings. all login types cause RUA to add users to the database. For more information on RUA Agents and 3D Sensors with RUA. By default. unless your RUA implementation includes 3D Sensors with RUA. 5. Version 4. Select Operations > System Policy.9. Click Save Policy and Exit. See Applying a System Policy on page 324 for more information. In either case. To configure the RUA settings as part of a new system policy. The System Policy page appears. The system policy is updated. click Edit next to the system policy. click Create Policy. see How Do I Choose an RUA Implementation? in the Analyst Guide. Provide a name and description for the system policy as described in Creating a System Policy on page 321. the Access List page appears. 3. You have two options: • • To modify the RUA settings in an existing system policy. and click Save. 2.

In either case. Do not synchronize your 3D Sensors (virtual or physical) to a Virtual Defense Center. such as command line interfaces or the operating system interface. Note that time settings are displayed on most pages on the appliance in local time using the time zone you set on the Time Zone page (America/New York by default). see the Sourcefire 3D Sensor Software for X-Series Installation Guide. You must use native applications. For more information on configuring settings for RNA Software for Red Hat Linux. Sourcefire recommends that you synchronize your virtual appliances to a physical NTP server. but are stored on the appliance itself using UTC time. see the Sourcefire RNA Software for Red Hat Linux Configuration Guide. You manage time settings on an Intrusion Agent through the operating system. You can choose to synchronize the time: • • manually using one or more NTP servers (one of which can be a Defense Center) Time settings are part of the system policy. Select Operations > System Policy. the time setting is not used until you apply the system policy. the current time appears in UTC at the top of the Time Synchronization page (local time is displayed in the Manual clock setting option. To synchronize time on the Defense Center: Access: Admin 1. Each procedure is explained separately below. You can specify the time settings either by creating a new system policy or by editing an existing policy.9. Version 4. If you specify a remote NTP server. The procedure for synchronizing time differs slightly depending on whether you are using the web interface on a Defense Center or a 3D Sensor. see Serving Time from the Defense Center on page 357. The System Policy page appears. your appliance must have network access to it.1 Sourcefire 3D System Administrator Guide 354 . if enabled). to manage time settings for software sensors: • For more information on configuring settings for Crossbeam Systems Switches.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 Synchronizing Time Requires: Any You can manage time synchronization on the appliance using the Time Synchronization page. • • You can synchronize the appliance’s time with an external time server. Connections to NTP servers do not use configured proxy settings. To use the Defense Center as an NTP server. In addition.

the DHCP-provided NTP server will be used instead.9. To avoid this situation. you should configure your DHCP server to set the same NTP server. in the Serve time via NTP drop-down list. See Setting the Time Manually on page 389 for information about setting the time after you apply the system policy. type the fully qualified host and domain names. You have two options for specifying how the time is synchronized on the appliance: • To set the time manually. type a comma-separated list of IP addresses for the NTP servers you want to use or. select Via NTP Server from and. You have two options: • • To modify the time settings in an existing system policy. Click Time Synchronization. The Time Synchronization page appears. To receive time through NTP from a different server. Note that if you set this option to Enabled and then apply the system policy to a sensor rather than a Defense Center. click Edit next to the system policy. Provide a name and description for the system policy as described in Creating a System Policy on page 321. Version 4. in the text box. click Create Policy. To configure the time settings as part of a new system policy. if DNS is enabled. 3.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 2.1 Sourcefire 3D System Administrator Guide 355 . • WARNING! If the appliance is rebooted and your DHCP server sets an NTP server record different than the one you specify here. In either case. this value is ignored. the Access List page appears. 5. 4. select Enabled. If you want to serve time from the Defense Center to your managed sensors. select Manually in the System Settings. Only Defense Centers can act as NTP servers. and click Save.

Click Time Synchronization. Select Operations > System Policy.1 Sourcefire 3D System Administrator Guide 356 . Provide a name and description for the system policy as described in Creating a System Policy on page 321. IMPORTANT! It may take a few minutes for the appliance to synchronize with the configured NTP servers.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 6. See Applying a System Policy on page 324 for more information. click Edit next to the system policy.9. 4. To configure the time settings as part of a new system policy. and click Save. You have two options: • • To modify the time settings in an existing system policy. You have two options for specifying how time is synchronized on the 3D Sensor: Version 4. The system policy is updated. The System Policy page appears. the Access List page appears. In either case. 3. 2. To synchronize time on a 3D Sensor: Access: Admin 1. Your changes do not take effect until you apply the system policy. The Time Synchronization page appears. Click Save Policy and Exit. click Create Policy.

Serving Time from the Defense Center Requires: DC/MDC You can configure the Defense Center as a time server using NTP and then use it to synchronize time between the Defense Center and managed 3D Sensors. if you are synchronizing the 3D Sensor to a Defense Center that is configured as an NTP server. On the Defense Center. and then enable Via NTP and click Save. This is because the Defense Center must first synchronize with its configured NTP server before it can serve time to the 3D Sensor. in the text box.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 • To set the time manually. if DNS is enabled. change the time manually after configuring the Defense Center as an NTP server.1 Sourcefire 3D System Administrator Guide 357 . Version 4. type a comma-separated list of IP addresses of the NTP servers or. IMPORTANT! It may take a few minutes for the 3D Sensor to synchronize with the configured NTP servers. The System Policy page appears. select Manually in the System Settings. and the Defense Center itself is configured to use an NTP server. change the time manually and click Save. select Via NTP Server from and. Click Save Policy and Exit. In addition. See Setting the Time Manually on page 389 for information about setting the time after you apply the system policy. You must disable NTP from the managed sensors’ web interfaces to stop the synchronization attempts. To configure the Defense Center as an NTP server: Access: Admin 1. disable the Via NTP option and click Save. before configuring the Defense Center to serve time using NTP If you need to . TIP! You cannot set the time manually after configuring the Defense Center to serve time using NTP If you need to manually change the time.9. See Applying a System Policy on page 324 for more information. it may take some time for the time to synchronize. select Operations > System Policy. then later disable it. the NTP service on managed sensors will still attempt to synchronize time with the Defense Center. you should do so . The system policy is updated. IMPORTANT! If you configure the Defense Center to serve time using NTP and . To receive time through NTP from different servers. type the fully qualified host and domain names. Your changes do not take effect until you apply the system policy. • 5.

Click Save Policy and Exit. The Time Synchronization page appears. You have two options: • • To modify the NTP server settings in an existing system policy. Your changes do not take effect until you apply the system policy to the Defense Center and its managed sensors. a host receives SMTP traffic that does not have a vendor or version in the header. Provide a name and description for the system policy as described in Creating a System Policy on page 321. For the services listed in the system policy. click Create Policy. 6.1 Sourcefire 3D System Administrator Guide 358 . IMPORTANT! It may take a few minutes for the Defense Center to synchronize with its managed sensors. when the service has a service ID in the RNA database and the packet header for the traffic includes a vendor and version. select Enabled. and click Save. you can configure whether RNA associates vulnerabilities with service traffic for vendor and versionless services. 5. all vulnerabilities associated with SMTP applications are added to the host profile for the host. However. 3. select Via NTP from Defense Center. In either case. Version 4.9. To configure the NTP server settings as part of a new system policy. then apply that policy to the Defense Center managing the sensor that detects the traffic. Click Time Synchronization. See Applying a System Policy on page 324 for more information. the Access List page appears. Note that although RNA detectors collect service information and add it to host profiles. For example. In the Set My Clock option for the sensors. 4.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 2. If you enable the SMTP service on the Vulnerability Mapping page of a system policy. many services do not include vendor and version information. Mapping Vulnerabilities for Services Requires: DC/MDC RNA automatically maps vulnerabilities to a host for any service traffic received or sent by the host. the service information will not be used for vulnerability mapping because you cannot specify a vendor or version for a custom service and cannot select the service for vulnerability mapping in the system policy. From the Serve Time via NTP drop-down list. click Edit next to the system policy. The system policy is updated.

click Create Policy. • TIP! You can select or clear all check boxes at once using the check box next to Enable. the Access List page appears. Your changes do not take effect until you apply the system policy to the Defense Center and its managed sensors. The system policy is updated. The System Policy page appears. 3. You have two options: • To prevent vulnerabilities for a service from being mapped to hosts that receive service traffic without vendor or version information. In either case. Version 4.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 To configure vulnerability mapping for services: Access: Admin 1. To configure active fingerprint source settings as part of a new system policy. 2.1 Sourcefire 3D System Administrator Guide 359 . Click Save Policy and Exit. clear the check box for that service. The Vulnerability Mapping page appears. Provide a name and description for the system policy as described in Creating a System Policy on page 321. Click Vulnerability Mapping. You have two options: • • To modify active fingerprint source settings in an existing system policy. See Applying a System Policy on page 324 for more information.9. To cause vulnerabilities for a service to be mapped to hosts that receive service traffic without vendor or version information. click Edit next to the system policy. 4. select the check box for that service. Select Operations > System Policy. 5. and click Save.

which controls aspects of an appliance that are likely to be similar across a deployment. See Managing System Policies on page 320 for more information.Configuring System Settings Chapter 10 Administrator Guide The system settings include a series of linked pages that you can use to view and modify settings on your appliance. with a system policy. Contrast the system settings.1 Sourcefire 3D System Administrator Guide 360 . Version 4.9. which are likely to be specific to a single appliance.

Time Displays the current time. See Configuring Remote Access to the Defense Center on page 386 for more information. License Network Network Interface Process Version 4. See Editing Network Interface Configurations on page 380 for more information. On the Defense Center.1 Sourcefire 3D System Administrator Guide 361 . If the time synchronization settings in the current system policy for the appliance is set to Manual. System Settings Options Option Information Description Allows you to view current information about the appliance. Provides options that you can use to: • shut down the appliance • reboot the appliance • restart the Sourcefire 3D System-related processes See Shutting Down and Restarting the System on page 382 for more information. See Understanding Licenses on page 364 for more information.9. See Configuring Network Settings on page 377 for more information. See Configuring the Communication Channel on page 383 for more information. Enables you to change options such as the IP address. You can also change the appliance name. enables you to specify values for the internal network and management port that the Defense Center uses to communicate with its managed sensors and high availability peer. See Setting the Time Manually on page 389 for more information. and proxy settings of the appliance that were initially set up as part of the installation. enables you to establish communications with a Defense Center from the sensor. See Viewing and Modifying the Appliance Information on page 362 for more information. hostname.Configuring System Settings Chapter 10 The System Settings Options table describes the options you can configure in the system settings. then you can use this page to change the time. Allows you to view and modify the settings for the network interfaces on your appliance. Provides you with options for managing your current licenses and for adding additional feature licenses on the platforms that support them. Remote Management On the 3D Sensor.

On the Defense Center. Version 4. Viewing and Modifying the Appliance Information Requires: Any The Information page provides you with information about the Defense Center or 3D Sensor. See Blacklisting Health Modules on page 391 for more information. See Managing Remote Storage on page 393 for more information. The page also provides you with an option to change the name of the appliance. and the current appliance-level policies.9.Configuring System Settings Viewing and Modifying the Appliance Information Chapter 10 System Settings Options (Continued) Option Health Blacklist Description On the Defense Center. The Series 2 DC1000 or DC3000 Defense Center version of this the page is shown below.1 Sourcefire 3D System Administrator Guide 362 . On Series 2 DC1000 and DC3000 Defense Centers. IMPORTANT! You cannot view sensor information for Intrusion Agents. allows you to specify the NetFlow-enabled devices you want to use to collect flow data. allows you to configure remote storage for backups and reports. The information includes view-only information such as the product name and model number. NetFlow Devices Remote Storage To configure the system settings: Access: Admin Select Operations > System Settings. with a list on the left side of the page that you can use to access other system settings. The Information page appears. the operating system and version. See Specifying NetFlow-Enabled Devices on page 392 for more information. allows you to temporarily disable health monitoring for a 3D Sensor to prevent the Defense Center from generating unnecessary health events.

Product Model Software Version Store Events Only on Defense Center Prohibit Packet Transfer to the Defense Center Operating System Operating System Version IP Address Current Policies Model Number Version 4.9. The IP address of the appliance. This number can be important for troubleshooting. entering a different name in this field does not change the hostname. If a policy has been updated since it was last applied.Configuring System Settings Viewing and Modifying the Appliance Information Chapter 10 The Appliance Information table describes each field. The model name for the appliance. but not the managed sensor. Clear this check box to allow packet data to be stored on the DC with events. Appliance Information Field Name Description A name you assign to the appliance. The operating system currently running on the appliance. Clear this check box to store event data on both appliances. Enable this check box to prevent the managed sensor from sending packet data with the events. The appliance-level policies currently applied to the appliance. Note that this name is only used within the context of the Sourcefire 3D System. The version of the operating system currently running on the appliance. the name of the policy appears in italics. Enable this check box to store event data on the Defense Center. The model number for the appliance.1 Sourcefire 3D System Administrator Guide 363 . Although you can use the hostname as the name of the appliance. The version of the software currently installed.

2. The Defense Center version of the page is shown below. type a new name in the Name field. WARNING! The name must be alphanumeric characters and should not be composed of numeric characters only. the 3D Sensor version of the page is shown below. Select Operations > System Settings. 3. To change the appliance name.Configuring System Settings Understanding Licenses Chapter 10 To modify the appliance information: Access: Admin 1. To save your changes. The Information page appears. Understanding Licenses Requires: Any You can license a variety of products and features to create your optimal deployment. Version 4. The page refreshes and your changes are saved. the Sourcefire 3D System requires that you enable IPS by applying a product license file to each appliance as part of the installation process.9. For comparison. You can also add feature licenses such as RNA host licenses and Intrusion Agent licenses. click Save.1 Sourcefire 3D System Administrator Guide 364 . For Defense Centers.

.. For information on adding a product license. see Understanding Feature Licenses on page 366. For information on how to add a feature license. see Adding Feature Licenses on page 370.Configuring System Settings Understanding Licenses Chapter 10 See the following for more information: • • • Understanding Feature Licenses on page 366 Verifying Your Product License on page 368 Managing Your Feature Licenses on page 370 You can use a variety of appliances and optional features in your deployment. see Sourcefire 3D Sensor Installation Guide. Product License to.. For information on how to use virtual appliances. see Sourcefire Virtual Defense Center and 3D Sensor Installation Guide. use IPS on that appliance. To understand why and when to use these licenses. Virtual License a Defense Center at any time use virtual machines. Version 4.9. TIP! You can view your licenses by using the Product Licensing widget in the dashboard. see the Sourcefire Licenses table on page 365. and Sourcefire Defense Center Installation Guide.1 Sourcefire 3D System Administrator Guide 365 . a 3D Sensor or a Defense Center during installation so that you can. For information on IPS... RUA. See Understanding the Product Licensing Widget on page 84 for more information. see Introduction to Sourcefire IPS in Sourcefire 3D System Analyst Guide Feature License a Defense Center at any time use additional features such as RNA. Sourcefire Licenses You apply a. and so on. For information on how the various features function.

RUA Users. You must use a Defense Center to configure NetFlow data collection and to view the collected data. IPS Software Sensors. NetFlow-enabled devices are widely used to capture and export data about the traffic that passes through those devices. FreeBSD. Although you can use NetFlow-enabled devices exclusively to monitor your network. and your deployment must include at least one 3D Sensor with RNA that can communicate with your NetFlow-enabled devices. The NetFlow cache stores a record of every flow (a sequence of packets that represents a connection between a source and destination host) that passes through the devices. NetFlows. but can also be embedded in Juniper. RUA Users and either RNA Hosts or the product license (or both). Intrusion Agents. endpoint. attacks. RNA Hosts. You can deploy NetFlow-enabled devices on networks that your sensors cannot monitor.9. NetFlow is available not only on Cisco networking devices. see Introduction to NetFlow in the Sourcefire 3D System Analyst Guide. up-to-the-minute profile of your network correlate threat. and OpenBSD devices.1 Sourcefire 3D System Administrator Guide 366 . Version 4. capture and export data about the traffic that passes through NetFlow-enabled devices monitor hosts on your network (including hosts discovered by NetFlow-enabled devices) to observe your network traffic to analyze a complete. the Sourcefire 3D System uses RNA detection engines on 3D Sensors to analyze NetFlow data. and network intelligence with user identity information identify the source of policy breaches. or network vulnerabilities transmit events generated by open source Snort installations to the Defense Center IPS for use with Crossbeam Systems X-Series you need a license for.. Feature Licenses If you want to. NetFlow NetFlow is an embedded instrumentation within Cisco IOS Software that characterizes network operation.. Standardized through the RFC process... and use NetFlow data to monitor those networks. For more information.Configuring System Settings Understanding Licenses Chapter 10 Understanding Feature Licenses The Feature Licenses table describes how to determine which features to license for your deployment.

(The 3D9800 does not support RNA. However. and events directly to individual users. and network intelligence with user identity information. or network vulnerabilities. that Defense Center must have an RNA host license installed and the 3D Sensor must have a product license installed. You can continue to manually tune Snort rules and preprocessors with the Intrusion Agent in place. For more information. RNA is installed on most 3D Sensors. LDAP server to augment the Defense Center’s database of user identity information with available metadata. By linking network behavior. 3D Sensors with RNA passively observe your organization’s network traffic and analyze it to provide you with a complete. see Introduction to Sourcefire RNA in the Sourcefire 3D System Analyst Guide.) Sourcefire also makes key components of RNA available in installation packages for Red Hat Linux servers and Crossbeam Systems security switches. as well as mitigate risk. All RUA deployments require a Defense Center that has an RUA feature license installed.9. For more information. For more information. see Sourcefire 3D System Intrusion Agent Configuration Guide. Intrusion Agent If you have an existing installation of Snort®. In addition. If your organization uses LDAP you can use the user information on your . Although you cannot manage policies or rules for an Intrusion Agent from the Defense Center. you must manage 3D Sensors with RNA with a Defense Center. and take action to protect others from disruption. allows your organization to correlate threat. You can then analyze the events detected by Snort alongside your other data. block users or user activity.Configuring System Settings Understanding Licenses Chapter 10 RNA Host Sourcefire RNA allows your organization to confidently monitor and protect your network using a combination of forensic analysis. traffic. These capabilities also significantly improve audit controls and enhance regulatory compliance. attacks. see Using Sourcefire RUA in the Sourcefire 3D System Analyst Guide. If the network map on the Defense Center has entries for the target host in a given event. RUA can help you to identify the source of policy breaches.1 Sourcefire 3D System Administrator Guide 367 . you can do analysis and reporting on those events. you can install an Intrusion Agent to forward intrusion events to a Defense Center. By default. RUA Host Sourcefire Real-time User Awareness. the Defense Center assigns impact flags to the events. endpoint. and built-in alerting and remediation. behavioral profiling. also called RUA. up-tothe-minute profile of your network. Version 4. to control how network intelligence is gathered and to view the resulting information. to enable RNA functionality.

1 Sourcefire 3D System Administrator Guide 368 . viewing. The Information page appears. see Managing Your Feature Licenses on page 370. Click License. In most cases.Configuring System Settings Understanding Licenses Chapter 10 IPS Software Sensor An IPS Software Sensor allows you to use 3D Sensor Software for X-Series on a Crossbeam® Next Generation Security Platform to gather network intelligence and intrusion information. and deleting feature licenses. Select Operations > System Settings. To verify the product license file: Access: Admin 1. The License page appears.9. Version 4. see Sourcefire Crossbeam Installation Guide XOS. you do not need to re-install the license. For more information. the user who sets up the appliance adds the software license as part of the process. 2. For information on adding. Verifying Your Product License Requires: Any During installation.

Follow the on-screen instructions for an appliance license to obtain your license file. The Licensing Center web site appears.9. 5. 4. 7. you must switch to a host that can access it. click Add New License and add it using the Add Feature License page. Click Get License. see Managing Your Feature Licenses on page 370. which will be sent to you in an email.sourcefire. IMPORTANT! If your web browser cannot access the Internet. Copy the license file from the email. click Edit. and click Submit License.Configuring System Settings Understanding Licenses Chapter 10 3.1 Sourcefire 3D System Administrator Guide 369 . For more information about feature licenses. Version 4. a message appears under the License field. paste it into the License field (as shown in Step 3). If the license file is correct. 6. and the features for the appliance are available in the web interface. The Manage License page appears.com/. Do not proceed to step 5. you will receive an error message. Continue with step 5 to obtain a license and install it. the license is added to the appliance. Click Verify License. • • If the license file is valid. If the license file is invalid. Copy the license key at the bottom of the page and browse to https://keyserver. Under Product Licenses. IMPORTANT! If you purchased a feature license.

which allow you to use intrusion agents 3D Virtual Sensors.9. you should have the 12-digit feature license serial number provided by Sourcefire when you purchased the licensable feature. Feature licenses include: • • • • • • NetFlow licenses. then clicking Products & Contracts. If you do not have the serial number. which allow you to use the RUA feature Intrusion Agent licenses. clicking Account. Version 4. which specify the number of hosts that you can monitor with RNA RUA licenses. you can find it by logging into the Sourcefire Support Site (https://support. which allow you use virtual sensors in your deployment IPS licenses for Crossbeam. IMPORTANT! Both Defense Centers in a high-availability pair must have NetFlow licenses for at least the number of NetFlow-enabled devices you are using.Configuring System Settings Understanding Licenses Chapter 10 Managing Your Feature Licenses Requires: DC The Defense Center uses feature licenses to allow for additional features.com/). which specify the number of NetFlow-enabled devices you can use to gather flow data RNA host licenses. See the following sections for more information: • • • Adding Feature Licenses on page 370 Viewing Feature Licenses on page 372 Configuring Network Settings on page 377 Adding Feature Licenses Requires: DC If you need to obtain a feature license for a feature you purchased.1 Sourcefire 3D System Administrator Guide 370 . which allow you to use 3D Sensor Software with IPS on Crossbeam Systems security switches When you purchase license packs for any licensable feature. you can request it from the web interface. The serial number appears in the Sourcefire Software & Licenses section.sourcefire. it will not receive data from your NetFlow-enabled devices. Before beginning. you must add them to the Defense Center from the web interface. If one Defense Center does not have a NetFlow license.

1 Sourcefire 3D System Administrator Guide 371 .9. 3. Click License. Select Operations > System Settings. Version 4.Configuring System Settings Understanding Licenses Chapter 10 To add a license: Access: Admin 1. The Information page appears. The License page appears. The Add Feature License page appears. Click Add New License. 2.

The first license that appears shows the Defense Center’s product license which shows the license status. connections. model code. Viewing Feature Licenses Requires: DC The licenses page displays the product and feature licenses that you have added to the Defense Center. node (MAC address).1 Sourcefire 3D System Administrator Guide 372 . If the license file is correct. and the licensed feature is available. For more information about viewing and modifying product licenses. you must switch to a host that can access it. TIP! You can also view licenses by using the Product Licensing widget on the dashboard. and so on). paste it into the License field. If you have feature or host licenses installed. After you receive an email with the feature license file. 6. which will be sent to you in an email. one or more licenses for RNA Hosts in addition to one or more licenses for Intrusion Agents. RUA. Note that there is only one product license. and provides a link that allows you to view or edit the license. the license is added to the appliance. Copy the license key at the bottom of the page and browse to https://keyserver. and click Submit License. they appear itemized below the product license. Click Get License.9. The Licensing Center web site appears. and expiration date. exporters. Follow the on-screen instructions for a feature license to obtain your license file. A summary of your licenses appears below the itemized list. TIP! Your Defense Center can have multiple feature licenses (for example. or users allowed by the sum of your feature or host licenses.sourcefire. IMPORTANT! If your web browser cannot access the Internet. and shows the total number of hosts. 5.com/. See Understanding the Product Licensing Widget on page 84 for more information. Version 4. You can repeat this process for each feature license you need to add. see Verifying Your Product License on page 368.Configuring System Settings Understanding Licenses Chapter 10 4. virtual appliances. copy the license file from the email.

Lists the number of NetFlow-enabled devices that the license allows you to use. Displays the appliance model number. NetFlow License Columns Column Feature ID Serial Number Status Model Allowed NetFlow Exporters Node Expires Action Description Displays the ID number that corresponds with the feature being licensed. Allows you to delete the feature license by clicking Delete.Configuring System Settings Understanding Licenses Chapter 10 The NetFlow License Columns table describes each column that appears in a NetFlow license.1 Sourcefire 3D System Administrator Guide 373 . or if a temporary license has expired. invalid. Displays the appliance model number. Version 4. Indicates if the license is valid. Lists the number of monitored hosts added by the license. Displays the feature serial number. or if a temporary license has expired. Displays the appliance’s MAC address. Displays the appliance’s MAC address. invalid.9. Indicates if the license is valid. Displays the date and time that the feature license expires. Displays the feature serial number. The RNA Host License Columns table describes each column that appears in an RNA host license. RNA Host License Columns Column Feature ID Serial Number Status Number of Hosts Model Node Description Displays the ID number that corresponds with the feature being licensed.

Intrusion Agent License Columns Column Feature ID Serial Number Description Displays the ID number that corresponds with the feature being licensed. Allows you to delete the host license by clicking Delete. RUA License Columns Column Feature ID Serial Number Status Model Number of Users Node Expires Action Description Displays the ID number that corresponds with the feature being licensed. Lists the number of monitored users added by the license. Displays the feature serial number. or if a temporary license has expired.Configuring System Settings Understanding Licenses Chapter 10 RNA Host License Columns (Continued) Column Expires Action Description Displays the date and time that the feature license expires. Allows you to delete the feature license by clicking Delete. The RUA License Columns table describes each column that appears in an RUA host license. Version 4.1 Sourcefire 3D System Administrator Guide 374 . The Intrusion Agent License Columns table describes each column that appears in an intrusion agent license. Indicates if the license is valid. Displays the appliance model number. Displays the appliance’s MAC address. invalid.9. Displays the feature serial number. Displays the date and time that the feature license expires.

and other physical hardware constraints. 45. or 250MB). invalid.1 Sourcefire 3D System Administrator Guide 375 . invalid. Allows you to delete the feature license by clicking Delete. Indicates if the license is valid. Virtual 3D Sensor License Columns Column Feature ID Serial Number Status Model Allowed Virtual Sensors Node Throughput Limit Description Displays the ID number that corresponds with the feature being licensed. or if a temporary license has expired. or if a temporary license has expired. Displays the appliance model number. Displays the appliance’s MAC address. The Virtual 3D Sensor License Columns table describes each column that appears in an intrusion agent license.9.Configuring System Settings Understanding Licenses Chapter 10 Intrusion Agent License Columns (Continued) Column Status Model Swagent Max Connections Node Expires Action Description Indicates if the license is valid. Lists the maximum number of software agent connections allowed by the license. Displays the date and time that the feature license expires. Lists the maximum number of Virtual 3D Sensors allowed by the license. Displays the appliance’s MAC address. 100. IMPORTANT! These speeds are not a guaranteed throughput for the Virtual 3D Sensor you license. its connections. Displays the maximum capacity licensed for processing by the Virtual 3D Sensor (20. Maximum throughput is limited by other factors such as number of Virtual Machines on your VMware server. Version 4. Displays the feature serial number. Displays the appliance model number.

Displays the appliance’s MAC address. Select Operations > System Settings. Version 4. Displays the date and time that the feature license expires. Allows you to delete the feature license by clicking Delete. Displays the feature serial number. Allows you to delete the feature license by clicking Delete. invalid. To view or delete your feature licenses: Access: Admin 1. IPS Software License Columns Column Feature ID Serial Number Status Model Node Expires Action Description Displays the ID number that corresponds with the feature being licensed. Indicates if the license is valid. The IPS Software License Columns table describes each column that appears in an IPS Software license.Configuring System Settings Understanding Licenses Chapter 10 Virtual 3D Sensor License Columns (Continued) Column Expires Action Description Displays the date and time that the feature license expires. The Information page appears. or if a temporary license has expired. Displays the appliance model number.9.1 Sourcefire 3D System Administrator Guide 376 .

see the Virtual Defense Center and 3D Sensor Installation Guide. click Delete in the Action column. For more information on configuring settings for RNA Software for Red Hat Linux. showing the product license and any feature licenses you have added. see the Sourcefire RNA Software for Red Hat Linux Configuration Guide. or the operating system interface. or both IPv4 and IPv6 network settings in System Settings. For more information on configuring settings for Intrusion Agents. see the Sourcefire 3D Sensor Software for X-Series Installation Guide. The License page appears. Click License. If you specify DHCP the appliance automatically retrieves its network settings from a . such as command line interfaces. see the Intrusion Agent Configuration Guide. see the 3D Sensor Installation Guide. You must use native applications. For the feature that you want to delete. to manage network settings for software sensors or 3Dx800 sensors: • For more information on configuring settings for Crossbeam-based software sensors. Version 4. Disabled (IPv4 or IPv6) Manual (IPv4 and IPv6) DHCP (IPv4 and IPv6) Router assigned (IPv6 only) • • • • You have the following configuration options: • • • • If you specify manual. you must manually configure all network properties.Configuring System Settings Configuring Network Settings Chapter 10 2.1 Sourcefire 3D System Administrator Guide 377 .9. 3. The exceptions include software sensors or 3Dx800 sensors. For more information on configuring settings for 3Dx800 appliances. For more information on configuring settings for Virtual 3D Sensors. Configuring Network Settings Requires: Any With some exceptions. your Sourcefire 3D System provides a dual stack implementation so that you can choose IPv4. IPv6. third-party user interfaces.

you can configure a proxy server to be used when downloading updates and SEUs.255. This is the network through which Defense Centers and sensors communicate. • For IPv6. in the case of IPv6. the appliance is configured to directly connect to the Internet.Configuring System Settings Configuring Network Settings Chapter 10 local DHCP server. Version 4. Manual Network Configuration Settings Setting Management Interface Address and either IPv4 Netmask or IPv6 Prefix Length Description The IP address for the management interface. you specify Router assigned. the management interface is connected to an internal. By default. The Information page appears. If. the appliance retrieves its network settings from a local router. In most installations.1 Sourcefire 3D System Administrator Guide 378 .9.0). Select Operations > System Settings. you must set the address in colon-separated hexadecimal form and the number of bits in the prefix (for example: a prefix length of 112). Default Network Gateway Hostname The IP address of the gateway device for your network The DNS-resolvable name for the appliance IMPORTANT! If you change the hostname. To configure network settings: Access: Admin 1. • For IPv4. the new name is not reflected in the syslog until after you reboot the appliance. you must set the address and netmask in dotted decimal form (for example: a netmask of 255. protected network.0. Domain Primary DNS Server Secondary DNS Server Tertiary DNS Server The fully-qualified domain name where the appliance resides The IP address of the DNS server for the network where the appliance resides A secondary DNS server’s IP address A tertiary DNS server’s IP address If the appliance is not directly connected to the Internet.

If you selected Manual.1 Sourcefire 3D System Administrator Guide 379 . Select DHCP to allow DHCP server network setting resolution. in the IPv4 section select Disabled).9. and domain servers) if you use manual or router assigned configurations. 4. domain. 3. Specify which IP version (v4. Select Router assigned (an IPv6-only configuration) to allow router assigned network setting resolution. Select Manual to manually specify network settings. v6. Version 4. if your network uses only IPv6. or both) you want to use by selecting the Configuration from the IPv4 and IPv6 settings: • • • • Select Disabled to use only the alternative IP version (for example. specify the network settings. See the Manual Network Configuration Settings table on page 378 for a full description of each field you can configure. You can change the Shared Settings (hostname.Configuring System Settings Configuring Network Settings Chapter 10 2. Click Network. The Network page appears.

To configure network interfaces from a Defense Center. select Operations > System Settings. You must configure 3Dx800 interfaces on the 3Dx800 CLI. To configure a proxy server. select Operations > Sensor. Editing Network Interface Configurations Requires: DC or 3D Sensor You can use the Network Interface page to modify the default settings for each network interface on your appliance. select Manual proxy configuration and enter the IP address or fully qualified domain name of your proxy server in the HTTP Proxy field and the port in the Port field. the sensor drops traffic while the network interface card renegotiates its network connection. By default. WARNING! Do not modify the settings for the management interface unless you have physical access to the appliance. If your appliance is not directly connected to the Internet.Configuring System Settings Editing Network Interface Configurations Chapter 10 5. Any changes you make to the Auto Negotiate value are ignored for Gigabit interfaces. The System Settings page appears.9. you have two options: • • If you have a direct connection from the appliance to the Internet. If you change the link mode for a sensing interface. then click Edit next to the 3D Sensor. you can identify a proxy server to be used when downloading updates and rules. To edit a network interface: Access: Admin 1. 6. The network settings are changed. You have two choices: • • To configure network interfaces from a 3D Sensor. Click Save. If your network uses a proxy. select Direct connection. appliances are configured to connect directly to the Internet. Version 4.1 Sourcefire 3D System Administrator Guide 380 . It is possible to select a setting that makes it difficult to access the web interface.

Click Network Interface. 3.Configuring System Settings Editing Network Interface Configurations Chapter 10 2. listing the current settings for each interface on your appliance.1 Sourcefire 3D System Administrator Guide 381 . The Network Interface page appears. Click Edit next to the interface that you want to modify. The current settings for the interface appear: These setting include: • • • • • interface name sensor name interface type.9. either Sensing or Management interface description whether the interface is configured to auto-negotiate speed and duplex settings Version 4.

but does not physically shut off power. MDIX (medium dependent interface crossover). database. N/A indicates that there is no link for the interface • You can modify the interface name and description. automatic MDI/MDIX handling is disabled.1 Sourcefire 3D System Administrator Guide 382 . 4. you must press the power button on the appliance. including the bandwidth and duplex setting (Full or Half). N/A in this column indicates that the interface does not support MDI/MDIX the current link mode. However.9. or. unplug it. or Auto mode (Series 2 3D Sensors only). Version 4.Configuring System Settings Shutting Down and Restarting the System Chapter 10 • whether the interface is configured for MDI (medium dependent interface). which automatically handles switching between MDI and MDIX to attain link. You can: • • • • shut down the appliance reboot the appliance restart communications. select Off only if you require a specific link mode setting. However. Any changes you make to the Auto Negotiate value are ignored for Gigabit interfaces. for an appliance without a power button. keep the following in mind: • In the Auto Negotiate field. MDI/MDIX settings. you must also set the MDI/MDIX field to the required MDI or MDIX mode. MDI/MDIX is set to Auto. The Network Interface page appears again. select it in the Link Mode field. when you set a specific link mode. • Series 2 3D Sensors only If you disable auto negotiation and specify a link mode. If you need to specify a link mode. making it impossible for the endpoints to attain link unless you manually set the required MDI/MDIX mode. and http server processes on the appliance (this is typically used during troubleshooting) restart the RNA and Snort processes (Snort runs on the 3D Sensor only if you are licensed to use IPS) IMPORTANT! If you shut down the appliance. You cannot change the Auto Negotiate setting for 10Gb interfaces. and the link mode as needed. Shutting Down and Restarting the System Requires: Any You have several options for controlling the processes on your appliance. To shut off power to the appliance. Click Save. Normally. You must configure 3Dx800 interfaces on the 3Dx800 CLI. the process shuts down the operating system on the appliance.

Note that this logs you out of the 3D Sensor. in high availability deployments. To restart the Snort and RNA processes. The Appliance Process page appears.8 and earlier Defense Centers and sensors use a range of internal network IP addresses called the management virtual network to transmit thirdparty communications such as NTP to managed sensors and.0/ 16. click Run Command next to Reboot Appliance. its high availability peer is 8305/tcp.Configuring System Settings Configuring the Communication Channel Chapter 10 To shut down or restart your appliance: Access: Admin 1. The communication on port 8305 is bi-directional. and if high availability is enabled. To reboot the system. Note that this logs you out of the Defense Center. click Run Command next to Restart Appliance Console. click Run Command next to Shutdown Defense Center. The default address range is 172.0. click Run Command next to Shutdown Appliance. 3. The default port for communications between the Defense Center. Select Operations > System Settings. Enhancements in the current software eliminate the need for the management virtual network provided both the Defense Center and the sensors it manages are Version 4. click Run Command next to Restart Defense Center Console. Note that restarting the Defense Center may cause deleted hosts to reappear in the network map. 2. To reboot the system. click Run Command next to Reboot Defense Center. its managed sensors. to its Defense Center peer. For 3D Sensor • • • • Configuring the Communication Channel Requires: DC + 3D Sensor Version 4. Click Process. click Run Command next to Restart Detection Engines.9. To restart the Defense Center. Specify the command you want to perform: For DC/MDC • • • To shut down the Defense Center.16. To shut down the 3D Sensor. To restart the 3D Sensor.1 Sourcefire 3D System Administrator Guide 383 . The Defense Center version of the page is shown below. The Information page appears.

Version 4. For more information on configuring settings for RNA Software for Red Hat Linux.0. For more information. The field is filled with 0. IMPORTANT! Master Defense Centers do not currently use a Management Virtual Network. or the operating system interface. refer to: • • Setting Up the Management Virtual Network on page 384 Editing the Management Virtual Network on page 385 Setting Up the Management Virtual Network Requires: DC + 3D Sensor If the IP address range or the port conflicts with other communications on your network. third-party user interfaces. However. For more information on configuring settings for Crossbeam-based software sensor. If both the Defense Center and all sensors have been upgraded to the current version. For more information on configuring settings for 3Dx800 sensors. You must use native applications.0/24 to indicate that the Management Virtual Network is disabled on a Master Defense Center. see the Sourcefire 3D Sensor Installation Guide. see the Sourcefire RNA Software for Red Hat Linux Configuration Guide. see the Sourcefire 3D Sensor Software for X-Series Installation Guide.1 Sourcefire 3D System Administrator Guide 384 . but you can change it later. 3Dx800 sensors.9. you can specify different values. WARNING! The IP address range you specify for the Management Virtual Network must not conflict with any other local network. see the Intrusion Agent Configuration Guide. to manage the communication channel sensor settings for Crossbeam-based software sensors. including your management network.Configuring System Settings Configuring the Communication Channel Chapter 10 both using the current software. such as command line interfaces. IMPORTANT! The management virtual network is required only when the Defense Center must communicate with sensors running an older version.0. and Intrusion Agents. you will need to use a management virtual network and ensure that it does not conflict with other communications on your network. the management virtual network is unnecessary. but make sure you do not to enter a range that overlaps other local networks. You can not edit the Management Virtual Network field of a Master Defense Center. Doing so may break communications between hosts on the local network. The user interface prevents you from entering the address range for the management network. For more information on configuring settings for Intrusion Agents. if your Defense Center is running the current version of the software and the sensors it manages are running an older version of the software. This is usually configured as part of the installation process.

The field is filled with 0. this function is used only under the direction of Sourcefire Support. In the Management Port field. 5. 3. The new values are saved. WARNING! If the Management Virtual Network is functioning properly. 2. You can also regenerate the Virtual IP address. which provided enough addresses for 127 appliances. Past versions of Sourcefire 3D Systems used a default /24 (twenty-four bit) CIDR address space. TIP! The subnet mask is fixed at /16 (sixteen bits). Editing the Management Virtual Network Requires: DC + 3D Sensor You can change the host IP or host name of the connected appliance. Typically.0/24 to indicate that the Management Virtual Network is disabled on a Master Defense Center. You can not edit the Management Virtual Network field of a Master Defense Center. The current Version 4. a feature that is especially useful after network reconfigurations or appliance updates.Configuring System Settings Configuring the Communication Channel Chapter 10 To configure the communications channel: Access: Admin 1. it should not be edited. WARNING! Changing the management port on the Defense Center requires that you also manually change the management port on every managed sensor. In the Management Virtual Network field. 4. The Information page appears. The Remote Management page appears. Click Remote Management. enter the IP address range that you want to use. Select Operations > System Settings. enter the port number that you want to use. Master Defense Centers do not currently use a Management Virtual Network.0.9.0.1 Sourcefire 3D System Administrator Guide 385 . Click Save to save your changes for both the IP address range and the port number.

click Regenerate VIP to regenerate the IP address used by the virtual network.the hostname of IP address. Select Operations > System Settings. 5.1 Sourcefire 3D System Administrator Guide 386 . The Edit Remote Management page appears. Three fields are provided for setting up communications between appliances: • • • Management Host . 2. The Remote Management page appears.9.registration key Unique NAT ID .Configuring System Settings Configuring Remote Access to the Defense Center Chapter 10 version uses a default /16 (sixteen bit) CIDR address space. 4. Configuring Remote Access to the Defense Center Requires: DC + 3D Sensor You must begin the procedure for setting up the management relationship between a Defense Center and a sensor on the sensor. To edit the remote management virtual network: Access: Admin 1. The Information page appears. which provides for a much greater number of appliances. 3. Registration Key . After appropriate management virtual network edits are made. Optionally.a unique alphanumeric ID for use when registering sensors in NAT environments. Click Edit next to the host whose Management Virtual Network you want to change. Click Remote Management. TIP! The regenerate VIP option is useful after you reconfigure your network or change the Sourcefire 3D System to take advantage of a larger address space. See Working in NAT Environments on page 112 for more information. Edit the name or host ID in the Name or Host fields as required. Version 4. click Save. 6.

Click Add Manager. The Management Host or Host field (hostname or IP address) must be used on at least one of the appliances. In the Management Host field. Click Remote Management. Registration Key. see Setting Up the Management Virtual Network on page 384.Configuring System Settings Configuring Remote Access to the Defense Center Chapter 10 Valid combinations include: • • • Management Host and Registration Key used on both appliances Registration Key and Unique NAT ID used on the 3D Sensor with Host. the Remote Management page displays the Unique NAT ID in the Host field. WARNING! Leave the Management Port field at the top of the Remote Management page in the default setting in nearly all cases. If you must change the Management Port. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. The Add Remote Management page appears. 2. and Unique NAT ID used on the 3D Sensor with Registration Key and Unique NAT ID used on the Defense Center. On the sensor’s web interface.9. 4. Version 4. To set up sensor management from the sensor: Access: Admin 1. Registration Key. TIP! If you register a sensor to a Defense Center using a Registration Key and Unique NAT ID. 3. Management Host. The Information page appears. Sourcefire strongly recommends that you read Using the Defense Center on page 99 before you add sensors to the Defense Center. but without a hostname or IP address. type the IP address or the hostname of the Defense Center that you want to use to manage the sensor. and Unique NAT ID used on the Defense Center.1 Sourcefire 3D System Administrator Guide 387 . select Operations > System Settings. The Remote Management page appears.

If you used a unique ID in step 6. Type the IP address or the hostname of the sensor you want to add in the Host field. 9. 8. In the Registration Key field. After the sensor confirms communication with the Defense Center.9. 10. type the same value in the Unique NAT ID field. Click New Sensor. in the Unique NAT ID field. Version 4. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. 11. type the same one-time use registration key that you used in step 5. 5. use both the Registration Key and the Unique NAT ID fields. the Pending Registration status appears. 7. type a unique alphanumeric NAT ID that you want to use to identify the sensor. The Add New Sensor page appears. In that case. 12.Configuring System Settings Configuring Remote Access to the Defense Center Chapter 10 Note that you can leave the Management Host field empty if the management host does not have a routable address. type the one-time use registration key that you want to use to set up a communications channel between the sensor and the Defense Center. Click Save. 6. Optionally.1 Sourcefire 3D System Administrator Guide 388 . Access the Defense Center web interface and select Operations > Sensors. In the Registration Key field. The Sensors page appears.

then you can manually set the time for the appliance using the Time page in the system settings. To add the sensor to a group. Setting the Time Manually Requires: Any If the Time Synchronization setting in the currently applied system policy is set to Manual. see Managing Sensor Groups on page 131. 14. The sensor is added to the Defense Center. Version 4.1 Sourcefire 3D System Administrator Guide 389 . Note that RNA data is never stored on the sensor. IMPORTANT! In some high availability deployments where network address translation is used. You can store IPS data on both the Defense Center and the sensor by clearing the Store Events and Packets Only on the Defense Center check box. By default. Packet data is often important for forensic analysis. You can prevent packet data from leaving a sensor by checking the Prohibit Packet Transfer to the Defense Center check box.Configuring System Settings Setting the Time Manually Chapter 10 13. select the group from the Add to Group list. IMPORTANT! 3Dx800 sensors and Crossbeam-based software sensors cannot store IPS data locally. It can take up to two minutes for the Defense Center to verify the sensor’s heartbeat and establish communication. you may need to use the Add Manager feature to add the secondary Defense Center. You must store events on the Defense Center.9. Click Add. IMPORTANT! If you elect to prohibit sending packets and you do not store events on the 3D Sensor. packet data is not retained. 16. 15. Contact Sourcefire Support for more information. IPS data is stored only on the Defense Center and not on the sensor. For more information about groups.

9. its value should change to Being Used. the NTP Status section on the Time page provides the following information: NTP Status Column NTP Server Status Description The IP address and name of the configured NTP server. For example. Last Update See Synchronizing Time on page 354 for more information about the time settings in the system policy. Select Operations > System Settings. To manually configure the time: Access: Admin 1. The status of the NTP server time synchronization. Version 4. • Unknown indicates that the status of the NTP server is unknown. Offset The number of milliseconds of difference between the time on the appliance and the configured NTP server. Available. Instead. • Pending indicates that the NTP server is new or the NTP daemon was recently restarted. and positive values indicate that it is ahead. that indicates that the time is relatively stable and the NTP daemon has determined that it does not need to use a lower update increment. The following states may appear: • Being Used indicates that the appliance is synchronized with the NTP server. The Information page appears. Over time. time manually. if you see larger update times such as 300 seconds. • Available indicates that the NTP server is available for use but time is not yet synchronized.1 Sourcefire 3D System Administrator Guide 390 .Configuring System Settings Setting the Time Manually Chapter 10 If the appliance is synchronizing its time based on NTP you cannot change the . • Not Available indicates that the NTP server is in your configuration but the NTP daemon is unable to use it. The NTP daemon automatically adjusts the synchronization times based on a number of conditions. Negative values indicate that the appliance is behind the NTP server. The number of seconds that have elapsed since the time was last synchronized with the NTP server. or Not Available.

You may want to do this to prevent events from the module from changing the status for the appliance to warning or critical. The time is updated. From list boxes that appear. click Close to close the pop-up window. if an appliance is temporarily disconnected from the management network. after the time zone setting is saved. select the following: • • • • • year month day hour minute 4. Blacklisting Health Modules Requires: DC/MDC If you want to disable health events for all appliances with a particular health policy. For information on blacklisting individual or groups of appliances see Blacklisting Health Policies or Appliances on page 535. For information on blacklisting an individual policy modules. you can blacklist the policy.9. If you want to change the time zone. A pop-up window appears. you can blacklist the group of appliances. the appliances report a disabled status in the Health Monitor Summary. For example. you can blacklist the Appliance Heartbeat module during that maintenance window. see Setting Your Default Time Zone on page 34.Configuring System Settings Blacklisting Health Modules Chapter 10 2. You can also blacklist individual health policy modules on appliances. 3. click the time zone link located next to the date and time. The Time page appears. Click Apply. 6. For more information about using the time zone page. Click Time. If you need to disable the results of a group of appliances’ health monitoring. see Blacklisting a Health Policy Module on page 537 Version 4. 5. Once the blacklist settings take effect. Select your time zone and click Save and.1 Sourcefire 3D System Administrator Guide 391 .

Keep in mind that if you remove a NetFlow-enabled device from the system policy. One of the prerequisites for using NetFlow data is to use the system settings to specify the NetFlow-enabled devices you are going to use to collect the data. For more information on using NetFlow data with the Sourcefire 3D System. Click NetFlow Devices. You must configure these NetFlow-enabled devices to export NetFlow version 5 data. 2. 6. The NetFlow Devices page appears. repeat steps 3 and 4.9. including information on additional prerequisites. The Information page appears. In the IP Address field. To add additional NetFlow-enabled devices. you can use the flow data that these devices collect to supplement the flow data collected by 3D Sensors with RNA by specifying the devices and the networks they monitor in your RNA detection policy.Configuring System Settings Specifying NetFlow-Enabled Devices Chapter 10 Specifying NetFlow-Enabled Devices Requires: DC + RNA If you have enabled the NetFlow feature on your NetFlow-enabled devices).1 Sourcefire 3D System Administrator Guide 392 . click Delete next to the device you want to remove. see Introduction to NetFlow in the Analyst Guide. Click Add Device to add a NetFlow-enabled device. For more information. To add NetFlow-enabled devices for flow data collection: Access: Admin 1. enter the IP address of the NetFlow-enabled device you want to use to collect flow data. see Editing an RNA Detection Policy in the Analyst Guide. 5. TIP! To remove a NetFlow-enabled device. you should also remove it from your RNA detection policy. Click Save. Select Operations > System Settings. The list of NetFlow-enabled devices is saved. 3. Version 4. 4.

Version 4. You must ensure that your external remote storage system is functional and accessible from the Defense Center. Select Operations > System Settings. or Server Message Block (SMB)/Common Internet File System (CIFS) for backup and report remote storage. 3Dx800 sensors. Secure Shell (SSH). Select one of the backup and report storage options: • • • • To disable external remote storage and use the local Defense Center for backup and report storage. For information on backup and restore. IMPORTANT! You cannot use remote backup and restore to manage data on Crossbeam-based software sensors.9. You can use Network File System (NFS). or Intrusion Agents. To use SSH for backup and report storage. RNA Software for Red Hat Linux. The Information page appears. see Using Local Storage on page 393.1 Sourcefire 3D System Administrator Guide 393 . see Using Backup and Restore on page 413.Configuring System Settings Managing Remote Storage Chapter 10 Managing Remote Storage Requires: Series 2 DC On Series 2 Defense Centers you can use local or remote storage for backups and reports. Keep in mind that only Series 2 Defense Centers and not Master Defense Centers provide backup and report remote storage. Using Local Storage Requires: Series 2 DC You can store backups and reports on the local Defense Center. you can switch back to local storage only if you have not increased the RNA flow database limit. To use SMB for backup and report storage. but you can choose to send either to a remote system and store the other on the local Defense Center. You cannot send backups to one remote system and reports to a another. see Using NFS for Remote Storage on page 394. To use NFS for backup and report storage. To store backups and reports locally: Access: Admin 1. TIP! After configuring and selecting remote storage. see Using SSH for Remote Storage on page 395. see Using SMB for Remote Storage on page 396.

Configuring System Settings Managing Remote Storage Chapter 10 2. At Storage Type. 3. Click Remote Storage Device. 3. The Remote Storage Device page appears. Click Remote Storage Device. At Storage Type. The Remote Storage Device page appears. Using NFS for Remote Storage Requires: Series 2 DC You can select Network File System (NFS) protocol to store your reports and backups. Enter the path to your storage area in the Directory field. Add the connection information: • • Enter the IP or hostname of the storage system in the Host field. Your storage location choice is saved. TIP! You do not use the Test button with local storage. The page refreshes to display the NFS storage configuration options. 4.1 Sourcefire 3D System Administrator Guide 394 . To store backups and reports using NFS: Access: Admin 1. select NFS. 4. Version 4. 2.9. Click Save. select Local (No Remote Storage). The Information page appears. Select Operations > System Settings.

The Information page appears. Under System Usage. To store backups and reports using SSH: Access: Admin 1. The page refreshes to display the SSH storage configuration options. Version 4. select either or both of the following: • • 7. select SSH. The Remote Storage Device page appears. Select Enable Remote Storage for Backups to store backups on the designated host. The test ensures that the Defense Center can access the designated host and directory. At Storage Type. Using SSH for Remote Storage Requires: Series 2 DC You can select Secure Shell (SSH) protocol to store your reports and backups.Configuring System Settings Managing Remote Storage Chapter 10 5. 3. 2. Your remote storage configuration is saved. 8. Select Operations > System Settings. select Use Advanced Options. click Test. Click Remote Storage Device. Click Save. Optionally.9. A Command Line Options field appears where you can enter the commands.1 Sourcefire 3D System Administrator Guide 395 . If there are any required command line options. Select Enable Remote Storage for Reports to store reports on the designated host. 6.

1 Sourcefire 3D System Administrator Guide 396 . Select Enable Remote Storage for Backups to store backups on the designated host. click Test. The test ensures that the Defense Center can access the designated host and directory. Optionally. To store backups and reports using SMB: Access: Admin 1. Enter the storage system’s user name in the Username field and the password for that user in the Password field. Your remote storage configuration is saved. copy the content of the SSH Public Key field and place it in your authorized_keys file. Under System Usage. Enter the path to your storage area in the Directory field. Select Operations > System Settings. Using SMB for Remote Storage Requires: Series 2 DC You can select Server Message Block (SMB) protocol to store your reports and backups. A Command Line Options field appears where you can enter the commands. If there are any required command line options. Click Save. select Use Advanced Options. 2. Select Enable Remote Storage for Reports to store reports on the designated host. Click Remote Storage Device.Configuring System Settings Managing Remote Storage Chapter 10 4. Add the connection information: • • • • Enter the IP or hostname of the storage system in the Host field. select either or both of the following: • • 7. Version 4. 8. 6. The Remote Storage Device page appears. The Information page appears.9. 5. To use SSH keys.

A Command Line Options field appears where you can enter the commands. 8. Enter the share of your storage area in the Share field.1 Sourcefire 3D System Administrator Guide 397 . Under System Usage.9. If there are any required command line options. Select Enable Remote Storage for Reports to store reports on the designated host. Optionally. Your remote storage configuration is saved. Optionally. Version 4. 4. click Test. 5. select either or both of the following: • • 7. At Storage Type. 6. enter the domain name for the remote storage system in the Domain field. select SMB. Enter the user name for the storage system in the Username field and the password for that user in the Password field. Select Enable Remote Storage for Backups to store backups on the designated host. The page refreshes to display the SMB storage configuration options. select Use Advanced Options.Configuring System Settings Managing Remote Storage Chapter 10 3. Click Save. The test ensures that the Defense Center can access the designated host and directory. Add the connection information: • • • • Enter the IP or hostname of the storage system in the Host field.

Updating System Software Chapter 11 Administrator Guide Use the Update feature to update the Sourcefire 3D System. 4. for example. client applications. For information on Intrusion Agents.0).1 Sourcefire 3D System Administrator Guide 398 .1). see Importing SEUs and Rule Files in the Analyst Guide. Sourcefire electronically distributes several different types of updates: • • Patches include a limited range of fixes (and usually change the fourth digit in the version number. and services that RNA detects. Version 4. Major and minor version releases include new features and functionality and may entail large-scale changes to the product (and usually change the first or second digit in version number. Vulnerability database (VDB) updates affect the vulnerabilities reported by RNA as well as the operating systems. see the Intrusion Agent Configuration Guide.9.9. • • IMPORTANT! You cannot use the Update feature to update the SEU or Intrusion Agents.0. Feature updates are more comprehensive than patches and generally include new features (and usually change the third digit in the version number.9. For information on updating your SEU. for example. 4. for example.1). 4.9 or 5.

They also contain information on any prerequisites. See the following sections for more information: • • • Installing Software Updates on page 400 Uninstalling Software Updates on page 409 Updating the Vulnerability Database on page 410 Version 4. Uploaded VDB updates also appear on the page. When you upload updates to your appliance. TIP! For patches. for major updates to software sensors. You can uninstall patches to the Sourcefire software using an appliance’s local web interface. feature updates. If your deployment includes a Defense Center. It also indicates whether a reboot is required as part of the update. However. the version number.1 Sourcefire 3D System Administrator Guide 399 . they appear on the page. you can use it to install updates on its managed 3D Sensors. you must read the release notes that accompany the update.9. Uninstalling from the web interface is not supported for major version upgrades. nor is it supported for appliances that do not have local web interfaces. you may need to uninstall the previous version and install the new version. known and resolved issues. which are created when you install a patch to a Sourcefire appliance.The following graphic shows the Defense Center version of the page. see Scheduling Tasks on page 425. including software sensors. and specific installation and uninstallation instructions. you can take advantage of the automated update feature. new features and functionality. and the date and time it was generated. warnings. and product compatibility. Before you update Sourcefire software.Updating System Software Chapter 11 You can obtain updates from the Sourcefire Support and then manually install them using the Patch Update Management page. The list of updates shows the type of each update. The release notes describe supported platforms. as do uninstaller updates. and VDB updates. WARNING! This chapter contains general information on updating the Sourcefire 3D System.

see Automating Software Updates on page 430. as described in the release notes. Make sure the computers or appliances where you installed software sensors are running the correct versions of their operating systems. TIP! This section explains how to plan for and perform manual software updates on your Sourcefire appliances.Updating System Software Installing Software Updates Chapter 11 Installing Software Updates Requires: Any Sourcefire periodically issues updates to the Sourcefire 3D System software. You can obtain the SEU from the Sourcefire Support Site. the policies and network settings on the appliance remain intact. Version 4. You must install the latest SEU (see Importing SEUs and Rule Files in the Analyst Guide) on your appliances before you begin the update. you can obtain updates from the Sourcefire Support Site. Note that for major updates to software sensors (Crossbeam-based software sensors and RNA for Red Hat Linux). Available on the Sourcefire Support Site. 3. Install the latest SEU on your appliances. you may need to uninstall the previous version and install the new version. new features and functionality. For patches and feature updates. they also contain information on any prerequisites. Make sure your appliances (including software sensors) are running the correct version of the Sourcefire 3D System. see the release notes for more information. Make sure that any Crossbeam Systems or Red Hat Linux platforms you are using to host Sourcefire software sensors are running the correct version of the operating system. the release notes describe supported platforms. Read the release notes for the update. and product compatibility. To update your Sourcefire 3D System appliances: Access: Admin 1. you can take advantage of the automated update feature.9. The release notes for the update indicate the required version. If you are running an earlier version.1 Sourcefire 3D System Administrator Guide 400 . Updating an appliance does not modify its configuration. known and resolved issues. 4. 2. warnings. and specific installation and uninstallation instructions.

including the types of backups that are supported for your appliance. Update your unmanaged 3D Sensors. Version 4. see Using Backup and Restore on page 413. When you update a managed sensor. the other Defense Center in the pair becomes the primary. To ensure continuity of operations. you may need to uninstall the previous version and install the new version. paired Defense Centers do not receive software updates as part of the regular synchronization process. After you update any Master Defense Centers in your deployment. Event data is not backed up as part of the update process. see Updating a Defense Center or Master Defense Center on page 402.Updating System Software Installing Software Updates Chapter 11 5. 7. Note that when you begin to update one Defense Center in a high availability pair.1 Sourcefire 3D System Administrator Guide 401 . Delete any backups that reside on the appliance. Update your Defense Centers. Update your managed 3D Sensors. 10. the update requires additional disk space on the Defense Center. the paired Defense Centers stop sharing configuration information. Update your Master Defense Centers. Make sure you have enough free disk space and allow enough time for the update. then back up current event and configuration data to an external location. do not update paired Defense Center at the same time. However. Always update Master Defense Centers first. The release notes for the update indicate space and time requirements. First. then update the second Defense Center. complete the update procedure for one of the Defense Centers. see the release notes for more information. 9. In addition.9. if it is not already. Sourcefire strongly recommends that you use your Defense Centers to update the sensors they manage. for major updates to software sensors. Sourcefire strongly recommends that you delete or move any backup files that reside on your appliance. See Updating Unmanaged 3D Sensors on page 406. Note that you must use the Defense Center to update sensors that do not have a web interface. including Crossbeam-based software sensors. then back up current event and configuration data to an external location. After you update the Master Defense Centers and Defense Centers in your deployment. see Updating Managed Sensors on page 404. For more information on the backup and restore feature. 8. and 3Dx800 sensors. you can update your managed sensors (including software sensors). see Updating a Defense Center or Master Defense Center on page 402. 6. you can update the Defense Centers they manage. RNA for Red Hat Linux.

This option is not supported for major updates. as well as their uninstall scripts. the other Defense Center in the pair becomes the primary.9. Version 4. IMPORTANT! For major updates. the paired Defense Centers stop sharing configuration information. Pre-update tasks can include making sure that the Defense Center is running the correct version of the Sourcefire software. depending on the type of update and whether your Defense Center has access to the internet: • You can use the Defense Center to obtain the update directly from the Support Site. complete the update procedure for one of the Defense Centers. To ensure continuity of operations. updating the Defense Center removes any existing updates and patches. do not update paired Defense Center at the same time. If your deployment includes Master Defense Centers.Updating System Software Installing Software Updates Chapter 11 Updating a Defense Center or Master Defense Center Requires: DC/MDC Use the procedure in this section to update your Defense Centers and Master Defense Centers. backing up event and configuration data. Choose this option if your Defense Center does not have access to the internet or if you are performing a major update. To update the Defense Center or Master Defense Center: Access: Admin 1. • Note that when you begin to update one Defense Center in a high availability pair. if it is not already. making sure you have enough free disk space to perform the update. you must update them before you update the Defense Centers that they manage. First. paired Defense Centers do not receive software updates as part of the regular synchronization process. then update the second Defense Center. In addition. You update the Defense Center in one of two ways. from the appliance. making sure you have set aside adequate time to perform the update. Read the release notes for the update and complete any required pre-update tasks. You can manually download the update from the Sourcefire Support Site and then upload it to the Defense Center. Choose this option if your Defense Center has access to the internet and you are not performing a major update. and so on.1 Sourcefire 3D System Administrator Guide 402 .

Tasks that are running when the update begins are stopped and cannot be resumed. and if your Defense Center has access to the Internet. Select Operations > Update to display the Patch Update Management page. Select Operations > Monitoring > Task Status to view the task queue and make sure that there are no jobs in process. If you transfer an update file by email. 6. The update is uploaded to the Defense Center. The page also indicates whether a reboot is required as part of the update. Make sure that the appliances in your deployment are successfully communicating and that there are no issues being reported by the health monitor. You have two options. Click Install next to the update you uploaded. For major releases. and the date and time it was generated. You must wait until any long-running tasks are complete before you begin the update.Updating System Software Installing Software Updates Chapter 11 2. then click Download Updates to check for the latest updates on the Support Site. then click Upload Update. or if your Defense Center does not have access to the Internet. depending on the type of update and whether your Defense Center has access to the internet. 3. The Patch Update Management page appears. select Operations > Update to display the Patch Update Management page. Select Operations > Update. either manually or by clicking Update on the Patch Update Management page. The Install Update page appears. 4. it may become corrupted. • For all except major releases. first manually download the update from the Sourcefire Support Site.1 Sourcefire 3D System Administrator Guide 403 . you must manually delete them from the task queue after the update completes. The task queue automatically refreshes every 10 seconds. Version 4. • IMPORTANT! Download the update directly from the Support Site.9. The Patch Update Management page shows the type of update you just uploaded. its version number. Browse to the update and click Upload. 5. Upload the update to the Defense Center.

select the Defense Center and click Install. If prompted. 11. This is expected behavior. If you encounter issues with the update (for example. WARNING! Do not use the web interface to perform any other tasks until the update has completed and (if necessary) the Defense Center reboots. If this occurs. 10. Updating managed sensors is a multi-step process. to update the Sourcefire software on the sensors that the Defense Center manages.Updating System Software Installing Software Updates Chapter 11 7. the web interface may become unavailable. 12. for most detection engines with inline interface sets. confirm that you want to install the update and reboot the Defense Center. continue to refrain from using the web interface until the update has completed. 9. Update the VDB on your Defense Centers and the 3D Sensors with RNA that they manage. Select Operations > Help > About and confirm that the software version is listed correctly. The update process begins. Re-apply intrusion policies to the IPS detection engines on your managed 3D Sensors. Continue with the next section. may cause a few packets to pass through the sensor uninspected. see Creating a Detection Engine on page 193). 8. if necessary. Clear your browser cache and force a reload of the browser. Updating Managed Sensors Requires: DC + 3D Sensor After you update your Defense Centers. After the update finishes. log in again to view the task queue. contact Support. see Updating the Vulnerability Database on page 410. Updating Managed Sensors. install the software. Under Selected Update. Unless you enabled the Inspect Traffic During Policy Apply option when you created your IPS detection engines (this option is supported on many sensor models. Instead. First.1 Sourcefire 3D System Administrator Guide 404 . Otherwise. If the update is still running. do not restart the update. if the task queue indicates that the update has failed or if a manual refresh of the task queue shows no progress). download the update from the Support Site and upload it to the managing Defense Center. the user interface may exhibit unexpected behavior. Note that you can update Version 4. 13. push the update to the sensors from the Defense Center. This can cause a short pause in processing and. Finally. Next. Sourcefire strongly recommends that you use them to update the sensors they manage. 14. Before the update completes. or the Defense Center may log you out.9. log into the Defense Center. You can monitor the update's progress in the task queue (Operations > Monitoring > Task Status). applying an intrusion policy causes IPS detection engines to restart. Verify that all managed sensors are successfully communicating with the Defense Center.

6. Read the release notes for the update and complete any required pre-update tasks. Download the update from the Sourcefire Support Site. select Operations > Update. If you transfer an update file by email. you have set aside adequate time to perform the update. Different 3D Sensor models use different updates. RNA for Red Hat Linux. making sure software sensors are running the correct version of their operating systems. Click Push next to the update. However. The Patch Update Management page shows the type of update you just uploaded. 5. 3. you may need to uninstall the previous version and install the new version. and date and time it was generated. including Crossbeam-based software sensors. Update the Sourcefire software on the sensors’ managing Defense Center. On the managing Defense Center. see Updating a Defense Center or Master Defense Center on page 402. 2. see the release notes for more information. then click Upload. The Patch Update Management page appears.1 Sourcefire 3D System Administrator Guide 405 . and 3Dx800 sensors. 4. 7. making sure you have enough free disk space to perform the update. Make sure that the appliances in your deployment are successfully communicating and that there are no issues being reported by the health monitor. Click Upload Update to browse to the update you downloaded. see the release notes. For information on updating the 3D Sensors in your deployment.Updating System Software Installing Software Updates Chapter 11 multiple 3D Sensors at once. IMPORTANT! Download the update directly from the Support Site. The page also indicates whether a reboot is required as part of the update. and so on. Version 4. The Push Update page appears. for major updates to software sensors.9. making sure that the 3D Sensors are running the correct version of the Sourcefire software. see the release notes. IMPORTANT! You must use the Defense Center to update sensors that do not have a web interface. Pre-update tasks can include updating your managing Defense Center. it may become corrupted. its version number. To update managed 3D Sensors: Access: Admin 1. The update is uploaded to the Defense Center. but only if they use the same update. For information on the updates you can download. backing up event and configuration data.

see Updating Managed Sensors on page 404. Select the sensors where you pushed the update and click Install. may cause a few packets to pass through the sensor uninspected. If the update requires a reboot. 11. applying an intrusion policy causes IPS detection engines to restart. Sourcefire strongly recommends that you update managed 3D Sensors using their managing Defense Centers. continue with the next step. for most detection engines with inline interface sets. Click Install next to the update you are installing. select the sensors you want to update. 13. see Creating a Detection Engine on page 193). Updating Unmanaged 3D Sensors Requires: 3D Sensor Use the procedure in this section to update unmanaged 3D Sensors only.Updating System Software Installing Software Updates Chapter 11 8. 9. some traffic may pass through the sensors uninspected while they reboot. Instead. You can monitor the progress of the push in the task queue (Operations > Monitoring > Task Status). 10. your 3D Sensors use IPS detection engines with inline interface sets. Select Operations > Sensors and confirm that the sensors you updated have the correct version listed. You can monitor the update's progress in the Defense Center’s task queue (Operations > Monitoring > Task Status).1 Sourcefire 3D System Administrator Guide 406 . This can cause a short pause in processing and. If your sensors have fail-open network cards. Re-apply intrusion policies to the IPS detection engines on your managed 3D Sensors. The Install Update page appears. confirm that you want to install the update and reboot the 3D Sensors. If prompted. Unless you enabled the Inspect Traffic During Policy Apply option when you created your IPS detection engines (this option is supported on many sensor models. traffic is interrupted while the sensors reboot. 12.9. Verify that the sensors you updated are successfully communicating with the Defense Center. contact Support. it may take some time to push the update to all sensors. Depending on the size of the file. then click Push. Version 4. do not restart the update. if the task queue indicates that the update has failed or if a manual refresh of the task queue shows no progress). The update process begins. WARNING! If you encounter issues with the update (for example. Under Selected Update. For more information. and the sensors do not have fail-open network cards. When the push is complete.

and so on. • For all except major releases. either manually or by clicking Update on the Patch Update Management page. Read the release notes for the update and complete any required pre-update tasks. its version number. backing up event and configuration data. depending on the type of update and whether your 3D Sensor has access to the internet: • You can use the 3D Sensor to obtain the update directly from the Support Site. or if your 3D Sensor does not have access to the Internet. The page also indicates whether a reboot is required as part of the update. making sure you have enough free disk space to perform the update. Pre-update tasks can include making sure that the 3D Sensor is running the correct version of the Sourcefire software. it may become corrupted. and if your 3D Sensor has access to the Internet. If you transfer an update file by email. 2. The update is uploaded to the 3D Sensor. first manually download the update from the Sourcefire Support Site. To update an unmanaged 3D Sensor: Access: Admin 1.9.Updating System Software Installing Software Updates Chapter 11 You update the 3D Sensor in one of two ways. depending on the type of update and whether your 3D Sensor has access to the internet. You have two options. Choose this option if your 3D Sensor has access to the internet and you are not performing a major update. The Patch Update Management page shows the type of update you just uploaded.1 Sourcefire 3D System Administrator Guide 407 . Browse to the update and click Upload. select Operations > Update to display the Patch Update Management page. Version 4. making sure you have set aside adequate time to perform the update. Choose this option if your 3D Sensor does not have access to the internet or if you are performing a major update. from the sensor. and the date and time it was generated. For major releases. updating the 3D Sensor removes any existing updates and patches. then click Upload Update. then click Download Updates to check for the latest updates on the Support Site. This option is not supported for major updates. • IMPORTANT! For major updates. as well as their uninstall scripts. • IMPORTANT! Download the update directly from the Support Site. You can manually download the update from the Sourcefire Support Site and then upload it to the 3D Sensor. Select Operations > Update to display the Patch Update Management page. Upload the update to the 3D Sensor.

Click Install next to the update you just uploaded. 9. Select Operations > Help > About and confirm that the software version is listed correctly. do not restart the update. log in again to view the task queue. If prompted. You can monitor the update's progress in the task queue (Operations > Monitoring > Task Status). traffic is interrupted while the sensor reboots. WARNING! Do not use the web interface to perform any other tasks until the update has completed and (if necessary) the 3D Sensor reboots. The task queue automatically refreshes every 10 seconds. After the update finishes. your 3D Sensor uses IPS detection engines with inline interface sets. for most detection engines with inline interface sets. You must wait until any long-running tasks are complete before you begin the update. This is expected behavior. or the 3D Sensor may log you out.1 Sourcefire 3D System Administrator Guide 408 . log into the 3D Sensor. applying an intrusion policy causes IPS detection engines to restart. This can cause a short pause in processing and. 4. Clear your browser cache and force a reload of the browser. Instead. If you encounter issues with the update (for example. some traffic may pass through the sensor uninspected while it reboots.Updating System Software Installing Software Updates Chapter 11 3. the web interface may become unavailable. you must manually delete them from the task queue after the update completes. If the update requires a reboot. Unless you enabled the Inspect Traffic During Policy Apply option when you created your IPS detection engines (this option is supported on many sensor models. see Creating a Detection Engine on page 193). Select Operations > Monitoring > Task Status to view the task queue and make sure that there are no jobs in process. If this occurs. 6. The update process begins. Otherwise. Version 4. if the task queue indicates that the update has failed or if a manual refresh of the task queue shows no progress). contact Support. may cause a few packets to pass through the sensor uninspected. Before the update completes. If the update is still running.9. 7. confirm that you want to install the update and reboot the 3D Sensor. The Patch Update Management page appears. the user interface may exhibit unexpected behavior. and the sensor does not have a fail-open network card. Re-apply intrusion policies to your IPS detection engines. Select Operations > Update. Tasks that are running when the update begins are stopped and cannot be resumed. 8. continue to refrain from using the web interface until the update has completed. 5. if necessary. If the sensor has a fail-open network card.

then your Defense Centers.0 to Version 4. For information on the resulting Sourcefire software version when you uninstall an update. If you upgraded to a new version of the appliance and need to revert to an older version.0. Uninstalling the Version 4. you must uninstall a patch from the appliances in your deployment in the reverse order of how you installed it.0. In addition.0.2 patch might result in an appliance running Version 4.Updating System Software Uninstalling Software Updates Chapter 11 Uninstalling Software Updates Requires: Any When you install a patch to a Sourcefire appliance.2.1. see the release notes.9. and finally your Master Defense Centers. see the release notes. IMPORTANT! Uninstalling from the web interface is not supported for major version upgrades. the resulting Sourcefire software version depends on the update path for your appliance.0. RNA for Red Hat Linux.9. as described by the procedure in this section.9. Select Operations > Update. For information on uninstalling patches from appliances that do not have local web interfaces (Crossbeam-based software sensors.9. Version 4. That is. For example.9. you cannot use the Defense Center to uninstall patches from managed sensors.1 Sourcefire 3D System Administrator Guide 409 . first uninstall the patch from your managed 3D Sensors. consider a scenario where you updated an appliance directly from Version 4. You must use the local web interface to uninstall patches.1 update. contact Support. the update process creates an uninstaller update that allows you to uninstall the patch from that appliances’s web interface.9. and 3Dx800 sensors). To uninstall a patch using the local web interface: Access: Admin 1. When you uninstall a patch. even though you never installed the Version 4. The Patch Update Management page appears.

Clear your browser cache and force a reload of the browser. Before the uninstall completes. If the uninstall is still running. RNA correlates the operating system and services detected on each host with the vulnerability database to help you determine whether a particular host increases your risk of network compromise. You can monitor its progress in the task queue (Operations > Monitoring > Task Status). If the uninstall for a 3D Sensor requires a reboot. 3. If this occurs. 5. This is expected behavior. the sensor uses IPS detection engines with inline interface sets. 4. and services. Updating the Vulnerability Database Requires: DC + RNA The Sourcefire Vulnerability Database (VDB) is a database of known vulnerabilities to which hosts may be susceptible. Verify that the appliance where you uninstalled the patch is successfully communicating with its managed sensors (for the Defense Center) or its managing Defense Center (for 3D Sensors). as well as fingerprints for RNA-detection operating systems. select the Defense Center and click Install. and the sensor does not have a fail-open network card. for example. Under Selected Update. there is no intervening page. 6. confirm that you want to uninstall the update and reboot the appliance. client applications. The Sourcefire Vulnerability Research Team (VRT) issues periodic updates to the VDB. If the sensor has a fail-open network card. if necessary. log in again and view the task queue. if prompted.9. After the uninstall finishes. if the task queue indicates that the uninstall has failed or if a manual refresh of the task queue shows no progress. • • On the Defense Center. log into the appliance. contact Support. or the appliance may log you out. Click Install next to the uninstaller for the update you want to remove.1 Sourcefire 3D System Administrator Guide 410 . some traffic may pass through the sensor uninspected while it reboots. the user interface may exhibit unexpected behavior.Updating System Software Updating the Vulnerability Database Chapter 11 2. the web interface may become unavailable. traffic is interrupted while the sensor reboots. WARNING! Do not use the web interface to perform any other tasks until the uninstall has completed and (if necessary) the appliance reboots. On the 3D Sensor. In either case. If you encounter issues with the uninstall. the Install Update page appears. Version 4. The uninstall process begins. do not restart the uninstall. Select Operations > Help > About and confirm that the software version is listed correctly. continue to refrain from using the web interface until the uninstall has completed. Instead. Otherwise.

Browse to the update and click Upload. You can take advantage of the automated update feature to schedule VDB updates. Because you cannot view RNA data on Master Defense Centers or on unmanaged 3D Sensors. The Push Update page appears.1 Sourcefire 3D System Administrator Guide 411 . To update the vulnerability database: Access: Admin 1. IMPORTANT! Download the update directly from the Support Site. divide the number of hosts on your network by 1000 to determine the approximate number of minutes to perform the update. you do not need to update the VDB on these appliances. see Automating Vulnerability Database Updates on page 437. • • If your Defense Center has access to the Internet. The VDB Update Advisory Text includes information about the changes to the VDB made in the update. 2. including software sensors. As a rule of thumb. use your Defense Centers to push and install the VDB on all managed 3D Sensors with RNA. If you transfer an update file by email. then click Upload Update. Select Operations > Update. The Patch Update Management page appears. 3.9. Upload the update to the Defense Center. click Download Updates to check for the latest updates on the Support site. To ensure you install the same VDB version. Read the VDB Update Advisory Text for the update. it may become corrupted. Click Push next to the VDB update. The time it takes to update vulnerability mappings depends on the number of hosts in your network map. The VDB update is saved on the Defense Center and appears in the Updates section. either manually or by clicking Update. You may want to schedule the update during low system usage times to minimize the impact of any system downtime. 4. If your Defense Center does not have access to the Internet. Version 4.Updating System Software Updating the Vulnerability Database Chapter 11 You should install the same version of the VDB on all the appliances in your deployment. manually download the update from the Sourcefire Support Site. as well as product compatibility information. TIP! This section explains how to plan for and perform manual VDB updates on your Sourcefire 3D System appliances.

then click Push. After the update finishes. • • To check the VDB build number on the Defense Center. if the task queue indicates that the update has failed or if a manual refresh of the task queue shows no progress. contact Support. The update process begins. then click Install. 7.9. Instead. it may take some time to push the VDB update to all sensors. 6. the update may take some time. Version 4. select Operations > Sensors on the Defense Center. select Operations > Help > About.Updating System Software Updating the Vulnerability Database Chapter 11 5. Depending on the size of the file. for example. confirm that the VDB build number matches the update you installed. The Install Update page appears. Click Install next to the VDB update. To check the VDB build number on your managed sensors. Select the Defense Center. 8. Depending on the number of hosts in your network map. You can monitor the progress of the push in the Defense Center’s task queue (Operations > Monitoring > Task Status). Under Selected Update. do not restart the update. If you encounter issues with the update. select the managed 3D Sensors you want to update. When the push is complete.1 Sourcefire 3D System Administrator Guide 412 . as well as the sensors where you pushed the VDB update. WARNING! Do not use the web interface to perform tasks related to mapped vulnerabilities until the update has completed. You can monitor the update's progress in the task queue (Operations > Monitoring > Task Status). then click Edit next to each sensor you updated. continue with the next step.

system configuration files are saved in the backup file. You can restore a backup onto a replacement appliance if the two appliances are the same model and are running the same version of the Sourcefire 3D System software. WARNING! Do not use the backup and restore process to copy the configuration files between sensors.Using Backup and Restore Chapter 12 Administrator Guide Backup and restoration is an essential part of any system maintenance plan. You can also choose to back up the following. those updates are not backed up. The configuration files include information that uniquely identifies a sensor and cannot be shared. Version 4. if applicable for the range of appliances in your deployment: • • • the entire intrusion event database the entire RNA event database additional files that reside on the appliance WARNING! If you applied any SEU updates. Sourcefire 3D System provides a mechanism for archiving data so that the Defense Center or 3D Sensor can be restored in case of disaster. While each organization’s backup plan is highly individualized. You need to apply the latest SEU update after you restore.1 Sourcefire 3D System Administrator Guide 413 .9. By default.

Uploading a backup from your local computer does not work on backup files larger than 4GB since web browsers do not support uploading files that large. On Series 2 Defense Centers. if you are using a Series 2 Defense Center. see Managing Remote Storage on page 393. You may also want to back up the system when testing configuration changes so that you can revert to the saved configuration. You can choose to save the backup file on the appliance or on your local computer. the backup file can be saved to a remote location. As an alternative or if your backup file is larger than 4GB. Creating Backup Files Requires: IPS or DC/ MDC To view and use existing system backups go to the System Backup Management page.1 Sourcefire 3D System Administrator Guide 414 . See Creating Backup Profiles on page 418 for information about creating backup profiles that you can use later as templates for creating backups.Using Backup and Restore Creating Backup Files Chapter 12 You can save backup files to the appliance or to your local computer. See the following sections for more information.9. copy it via SCP to a remote host. You should periodically save a backup file that contains all of the configuration files required to restore the appliance. See Restoring the Appliance from a Backup File on page 421 for information about how to restore a backup file to the appliance. if needed. in addition to event and packet data. • • • • • See Creating Backup Files on page 414 for information about backing up files from the appliance. See Performing Sensor Backup with the Defense Center on page 419 for information about backing up managed sensors with the Defense Center. Version 4. you can use remote storage as detailed in Managing Remote Storage on page 393. See Uploading Backups from a Local Host on page 420 for information about uploading backup files from a local host. Additionally. data correlation is temporarily suspended. When your backup task is collecting RNA events.

Using Backup and Restore Creating Backup Files Chapter 12 The Defense Center and Master Defense Center version of the page is shown below.1 Sourcefire 3D System Administrator Guide 415 .9. Version 4.

Requires: IPS To archive individual intrusion event data files. The Backup page appears. 5. Requires: IPS or DC/MDC To archive the entire event database. type a name for the backup file. Click Sensor Backup on a 3D Sensor toolbar or Defense Center Backup on a Defense Center toolbar. select Backup Configuration. the 3D Sensor version of the page is shown below. and spaces. 3. select Backup Events. select the files that you want to include from the Unified File List.Using Backup and Restore Creating Backup Files Chapter 12 For comparison.9. punctuation. The System Backup Management page appears. Requires: IPS or DC/MDC To archive the configuration. In the Name field. 4. Version 4. To create a backup file: Access: Maint/Admin 1. 2. Select Operations > Tools > Backup/Restore. You can use alphanumeric characters. 6.1 Sourcefire 3D System Administrator Guide 416 .

Optionally. to use secure copy (scp) to copy the backup archive to a different machine. to be notified when the backup is complete.Using Backup and Restore Creating Backup Files Chapter 12 7. select the Copy when complete check box and then type the following information in the accompanying text boxes: • • • • the hostname or IP address of the machine where you want to copy the backup the path to the directory where you want to copy the backup the user name that you want to use to log into the remote machine the password for that user name TIP! Sourcefire recommends that you periodically save backups to a remote location so that the appliance can be restored in case of system failure. You must make sure that your mail relay host is configured as described in Configuring a Mail Relay Host and Notification Address on page 338. select the Email when complete check box and type your email address in the accompanying text box. Requires: IPS Ensure that the value of the compressed backup file in the Selected Sum field is less than the value in the Available Space field. TIP! The compressed value that appears in the Selected Sum field is a conservative estimate of the size of the compressed file. 9. 10. type the full path and file name in the Additional Files field and click the plus sign (+). the file will be smaller. TIP! You can repeat this step to add additional files. Optionally. If you want to include an additional file in the backup. Version 4. 8.1 Sourcefire 3D System Administrator Guide 417 . Often.9.

On Series 2 Defense Centers. Click Backup Profiles on the toolbar. For information about restoring a backup file.9. Select Operations > Tools > Backup/Restore. To create a backup profile: Access: Maint/Admin 1. see Managing Remote Storage on page 393. you can direct the backup file to a remote location. 3. The System Backup page appears. You can modify or delete the backup profile by selecting Operations > Tools > Backup & Restore and then clicking Backup Profiles. see Restoring the Appliance from a Backup File on page 421. Creating Backup Profiles Requires: IPS or DC/ MDC You can use the Backup Profiles page to create backup profiles that contain the settings that you want to use for different types of backups. TIP! When you create a backup file as described in Creating Backup Files on page 414. You have the following options: • To save the backup file to the appliance. • To save this configuration as a backup profile that you can use later. The System Backup Management page appears. The Backup Profiles page appears with a list of existing backup profiles. Version 4. click Save As New. The backup file is saved in the /var/sf/backup directory. you can view the file on the Restoration Database page. See Creating Backup Profiles on page 418 for more information. click Start Backup. a backup profile is automatically created.Using Backup and Restore Creating Backup Profiles Chapter 12 11. TIP! You can click Edit to modify an existing profile or click Delete to delete a profile from the list. 2. When the backup process is complete. Click Create Profile.1 Sourcefire 3D System Administrator Guide 418 . You can later select one of these profiles when you are backing up the files on your appliance.

punctuation. To include event data in addition to configuration data. Version 4. Click Sensor Backup on the toolbar. The Remote Backup page appears.9. 6. Configure the backup profile according to your needs. RNA Software for Red Hat Linux. 4. The System Backup Management page appears.1 Sourcefire 3D System Administrator Guide 419 . The Backup Profiles page appears and includes your new profile in the list. they change to underscores. Select Operations > Tools > Backup/Restore. and spaces. select the managed sensors that you want to back up. 3Dx800 sensors. Type a name for the backup profile. You cannot use remote backup and restore to manage data on Crossbeam-based software sensors. Note that the unified files are binary file that the Sourcefire 3D System uses to log event data. or Intrusion Agents. select the Include All Unified Files check box. Performing Sensor Backup with the Defense Center Requires: DC You can use the Defense Center to back up data on managed 3D Sensors. The default name for the backup file uses the name of the managed 3D Sensor. See Creating Backup Files on page 414 for more information about the options on this page. 5. 2. You can use alphanumeric characters. In the Sensors field.Using Backup and Restore Performing Sensor Backup with the Defense Center Chapter 12 4. TIP! If you use a backup file name containing spaces or punctuation characters. Click Save As New to save the backup profile. 3. To back up a managed sensor: Access: Maint/Admin 1.

When the backup is complete. Uploading Backups from a Local Host Requires: DC If you download a backup file to your local host using the download function described in the Backup Management table on page 421. On Series 2 Defense Centers. Check the task status for progress.9. Click Upload Backup. Select Operations > Tools > Backup/Restore. leave this check box unselected. To upload a backup from your local host: Access: Maint/Admin 1. see Managing Remote Storage on page 393. click Upload Backup. 3. you can upload it to a Defense Center. The System Backup Management page appears.Using Backup and Restore Uploading Backups from a Local Host Chapter 12 5. Click Browse. copy the backup via SCP to a remote host and retrieve it from there. The Upload Backup page appears. TIP! To save each sensor’s backup file on the sensor itself. and navigate to the backup file.1 Sourcefire 3D System Administrator Guide 420 . As an alternative. 2. Click Start Backup. After you select the file to upload. TIP! It can take several minutes to complete the backup. To save the backup file on the Defense Center. you can view the backup file on the Restoration Database page. select the Retrieve to DC check box. Version 4. 6. the backup file can be saved to and retrieved from a remote location. A success messages appears and the backup task is set up. TIP! Uploading a backup larger than 4GB from your local host does not work because web browsers do not support uploading files that large.

Note that you can only restore a backup to an identical appliance type and version.9. backup system. and backup directory are listed at the top of the page. On Series 2 Defense Centers. Version 4. After you complete the restoration process. and version. Click with the backup file selected to view a list of the files included in the compressed backup file. refresh the System Backup Management page to reveal detailed file system information. you must apply the latest SEU. type. the protocol. The date and time that the backup file was created The full name of the backup file The location of the backup file The size of the backup file. If you use local storage. TIP! After the Defense Center verifies the file integrity. select Enable Remote Storage for Backups to enable or disable remote storage at the top of the System Backup Management page. in megabytes “Yes” indicates the backup includes event data. Backup Management Column System Information Date Created File Name Location Size (MB) Events? View Restore Description The originating appliance name. backup files are saved to /var/sf/backup which is listed with the amount of disk space used in the /var partition at the top of the System Backup Management page. Click Backup Management on the toolbar to return to the System Backup Management page. The Backup Management table describes each column and icon on the System Backup Management page. Click with the backup file selected to restore it on the appliance. Restoring the Appliance from a Backup File Requires: IPS or DC/ MDC You can restore the appliance from backup files using the System Backup Management page. If you use remote storage.Using Backup and Restore Restoring the Appliance from a Backup File Chapter 12 4.1 Sourcefire 3D System Administrator Guide 421 . The backup file is uploaded and appears in the backup list.

Version 4. To restore the appliance from a backup file: Access: Admin 1. click to send the backup to the designated remote backup location.9. Select Operations > Tools > Backup/Restore.1 Sourcefire 3D System Administrator Guide 422 . A Series 2 Defense Center version of the page is shown.Using Backup and Restore Restoring the Appliance from a Backup File Chapter 12 Backup Management (Continued) Column Download Delete Move Description Click with the backup file selected to save it to your local computer. On a Series 2 Defense Center when you have a previouslycreated local backup selected. The System Backup Management page appears. Click with the backup file selected to delete it.

3.9.Using Backup and Restore Restoring the Appliance from a Backup File Chapter 12 2. On the toolbar. Select the backup file that you want to restore and click Restore. Version 4. The Defense Center version of the page is truncated to show a sample of the files that are backed up. on the 3D Sensor. 4. its owner and permissions. To view the contents of a backup file. WARNING! This procedure will overwrite all configuration files and. all event data. select the file and click View. 5. The manifest appears listing the name of each file. select either or both: • • Replace Configuration Data Restore Event Data Then click Restore to begin the restoration. and its file size and date. click Backup Management to return to the System Backup Management page.1 Sourcefire 3D System Administrator Guide 423 . The Restore Screen page appears. Requires: DC/MDC To restore files.

and system policies to the restored system. health. Apply the latest SEU to re-apply SEU rule and software updates. 8. Click Restore to begin the restoration. Requires: IPS If you want to restore intrusion event data. select the files that you want to include from the Unified File List box. click Cancel.9. RNA detection. The appliance is restored using the backup file you specified. TIP! To cancel the restoration. 9.1 Sourcefire 3D System Administrator Guide 424 . Version 4. 7.Using Backup and Restore Restoring the Appliance from a Backup File Chapter 12 6. Re-apply any intrusion. Reboot the appliance.

Version 4. including: • • • • • • • • • • • running backups Requires: IPS applying intrusion policies generating reports Requires: DC + RNA running Nessus scans Requires: DC + RNA synchronizing Nessus plugins Requires: DC + RNA running Nmap scans Requires: DC + RNA + IPS using RNA rule recommendations Requires: IPS importing Security Enhancement Updates (SEUs) downloading and installing software updates Requires: DC + RNA downloading and installing vulnerability database updates Requires: DC pushing downloaded updates to managed sensors You can schedule tasks to run once or on a recurring schedule. IMPORTANT! Some tasks (such as those involving automated software and SEU updates and those that require pushing updates or intrusion policies to managed sensors) can place a significant load on networks with low bandwidths.Scheduling Tasks Chapter 13 Administrator Guide You can schedule many different types of administrative tasks to run at scheduled times.9. You should always schedule tasks like these to run during periods of low network use.1 Sourcefire 3D System Administrator Guide 425 .

push. Automating Reports on page 448 provides procedures for scheduling reports. You must recreate the recurring task schedule on a newly activated Defense Center when it changes from inactive to active. Automating Nmap Scans on page 454 provides procedures for scheduling Nessus scans.9. Automating Vulnerability Database Updates on page 437 provides procedures for scheduling the download. Automating SEU Imports on page 444 provides procedures for scheduling rule updates. Viewing Tasks on page 458 describes how to view and manage tasks after they are scheduled. Automating Recommended Rule State Generation on page 456 provides procedures for scheduling automatic update of intrusion rule state recommendations based on RNA data. Version 4. Synchronizing Nessus Plugins on page 452 provides procedures for synchronizing your sensor with the Nessus server. Automating Nessus Scans on page 450 provides procedures for scheduling Nessus scans. Deleting Scheduled Tasks on page 461 describes how to delete one-time tasks and all instances of recurring tasks. Editing Scheduled Tasks on page 461 describes how to edit an existing task. Automating Software Updates on page 430 provides procedures for scheduling the download. IMPORTANT! You cannot configure a recurring task schedule on the inactive Defense Center in a high availability pair of Defense Centers. and installation of software updates. Automating Backup Jobs on page 428 provides procedures for scheduling backup jobs.1 Sourcefire 3D System Administrator Guide 426 . Automating Intrusion Policy Applications on page 446 provides procedures for scheduling intrusion policy applications. push. • • • • • • • • • • Configuring a Recurring Task Requires: IPS or DC/ MDC You set the frequency for a recurring task using the same process for all types of tasks. and installation of software updates.Scheduling Tasks Configuring a Recurring Task Chapter 13 See the following sections for more information: • • • • Configuring a Recurring Task on page 426 explains how to set up a scheduled task so that it runs at regular intervals.

1 Sourcefire 3D System Administrator Guide 427 . The Add Task page appears. or months. and year. specify the date when you want to start your recurring task. 6. TIP! You can either type a number or use the arrow buttons to specify the interval. In the Repeat Every field. 2. day. days. Further. That is. select the type of task that you want to schedule. select Recurring. recurring tasks that span the transition dates from DST to standard time and back do not adjust for the transition. specify how often you want the task to recur. type 2 and select Day(s) to run the task every two days. The Scheduling page appears. Click Add Task. it will run at 1am during standard time. You can use the drop-down list to select the month. 4. 5. if you create a task scheduled for 2am during DST. where appropriate. To configure a recurring task: Access: Maint/Admin 1. In the Start On field. Version 4.9. 7. the Defense Center or 3D Sensor with IPS automatically adjusts its local time display for daylight saving time (DST). The page reloads with the recurring task options. For example. Similarly. For the Schedule task to run option. Select Operations > Tools > Scheduling. it will run at 3am during DST. which is determined by using the time zone you specify in your system settings. From the Job Type list. if you create a task scheduled for 2am during standard time. specify the time when you want to start your recurring task. 3. Each of the types of tasks you can schedule is explained in its own section. weeks. However. You can specify a number of hours.Scheduling Tasks Configuring a Recurring Task Chapter 13 Note that the time displayed on most pages on the web interface is the local time. In the Run At field.

Select the check boxes next to the days of the week when you want to run the task. Use the drop-down list to select the day of the month when you want to run the task. a Repeat On field appears. 9. The Scheduling page appears. TIP! You must design a backup profile before you can configure it as a scheduled task. a Repeat On field appears. Version 4.Scheduling Tasks Automating Backup Jobs Chapter 13 8. see Creating Backup Profiles on page 418. Click Add Task. Select Operations > Tools > Scheduling. See the following sections for more information: • • • • • • • • • • Automating Backup Jobs on page 428 Automating Software Updates on page 430 Automating Vulnerability Database Updates on page 437 Automating SEU Imports on page 444 Automating Intrusion Policy Applications on page 446 Automating Reports on page 448 Automating Nessus Scans on page 450 Synchronizing Nessus Plugins on page 452 Automating Nmap Scans on page 454 Automating Recommended Rule State Generation on page 456 Automating Backup Jobs Requires: IPS or DC/ MDC You can use the scheduler to automate system backups of a Defense Center or a 3D Sensor with IPS.1 Sourcefire 3D System Administrator Guide 428 . 2. The remaining options on the Add Task page are determined by the task you are creating. If you selected Week(s) in the Repeat Every field. The Add Task page appears. For information on backup profiles. If you selected Month(s) in the Repeat Every field. To automate backup tasks: Access: Maint/Admin 1.9.

spaces. • For one-time tasks. select Backup. or dashes. select the appropriate backup profile. Once or Recurring. see Creating Backup Profiles on page 418. 5. 4. • For recurring tasks. From the Backup Profile list. use the drop-down lists to specify the start date and time. so you should try to keep it relatively short. Optionally. type a comment using up to 255 alphanumeric characters. you have several options for setting the interval between instances of the task. TIP! The Current Time field indicates the current time on the appliance. 7. 6. In the Job Name field. For more information on creating new backup profiles. Version 4. From the Job Type list. See Configuring a Recurring Task on page 426 for details. or periods. in the Comment field. type a name using up to 255 alphanumeric characters.Scheduling Tasks Automating Backup Jobs Chapter 13 3.1 Sourcefire 3D System Administrator Guide 429 . The page reloads to show the backup options.9. TIP! The comment field appears in the View Tasks section of the page. Specify how you want to schedule the backup. spaces.

if you schedule a task to install an update and the update has not finished copying from the Defense Center to the sensor. then install it on the sensor. Tasks should be scheduled at least 30 minutes apart. For example. type the email address (or multiple email addresses separated by commas) where you want status messages sent. you can schedule automatic software installation and. if you want to update the software for your Defense Center.9. push. you must schedule two tasks: 1. for example. However. you can just schedule the Install Latest Update task. So. IMPORTANT! You must have a valid email relay server configured to send status messages. Always allow enough time between tasks for the process to complete. if you want to automate software updates on your managed sensors. Note that the tasks for pushing the update to managed sensors (on the Defense Center) and installing the update (on any appliance) automatically check the Version 4. as long as the appliance has access to the Internet. the appliance automatically downloads the latest update when the installation task runs. in the Email Status To: field.1 Sourcefire 3D System Administrator Guide 430 . it queries the Sourcefire support site for the latest updates. you must always push the update to the sensor first. Click Save. If you use your Defense Center to automate software updates for managed 3D Sensors. if you want to update your 3D Sensor directly and it is connected to the internet. 9. Optionally. Automating Software Updates The tasks you schedule to automate download. You should schedule the push and install tasks to happen in succession. Similarly. When automating direct software updates for an appliance. The backup task is created.Scheduling Tasks Automating Software Updates Chapter 13 8. the installation task will not succeed. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. you can schedule Install Latest Update to download and install the latest Defense Center update. Note that when the Defense Center runs either the Push Latest Update or the Install Latest Update task. For example. Install the update on managed sensors. 2. as long as it has access to the Internet. Push the update to managed sensors. if the scheduled installation task repeats daily. and installation of software updates vary depending on whether you are updating an appliance directly or are using a Defense Center to perform the updates. it will install the pushed update when it runs the next day.

you must manually upload. For larger. if you manually download an update to an appliance that cannot access the Support site.1 or 4. On the Defense Center. If your appliance cannot access the Support site.9.2. push. Click Add Task.8. you can use the Once option to download and install updates during off-peak hours after you learn that an update has been released.9). To automate software updates: Access: Maint/Admin 1. you can also automate vulnerability database (VDB) updates. Select Operations > Tools > Scheduling. more comprehensive updates (such as 4. TIP! The automated update process allows you to download and install software patches and feature releases (generally when the last two digits in the four-digit version number change. 2.8. The Scheduling page appears. such as 4. See the following sections for more information: • • • Automating Software Downloads on page 431 Automating Software Pushes on page 433 Automating Software Installs on page 435 Automating Software Downloads Requires: IPS or DC/ MDC You can create a scheduled task that automatically downloads the latest software updates from Sourcefire.1 Sourcefire 3D System Administrator Guide 431 . The Add Task page appears. Version 4. and install the upgrade files. You can use this task to schedule download of updates you plan to push or install manually. This behavior also has implications for appliances that cannot access the Support site at all. the task does not complete.Scheduling Tasks Automating Software Updates Chapter 13 Support site to ensure that you have the latest version of the update.1). Specifically. If you want to have more control over this process. you cannot schedule either pushes to managed sensors (on the Defense Center) or installs (on any appliance).8 or 4. Instead you must manually push or install the updates as described in Updating System Software on page 398.

select Download Latest Update.Scheduling Tasks Automating Software Updates Chapter 13 3. Requires: DC Select Vulnerability Database to download the most recent vulnerability database update. The Defense Center version of the page is shown below. • For one-time tasks. Once or Recurring. use the drop-down lists to specify the start date and time.9.com/). 6. IMPORTANT! If your appliance is not directly connected to the Internet.1 Sourcefire 3D System Administrator Guide 432 . TIP! The Current Time field indicates the current time on the appliance. In the Job Name field. • For recurring tasks. 5. See Configuring a Recurring Task on page 426 for details. In the Update Items section. you have several options for setting the interval between instances of the task. specify which updates you want to download. Both options are selected by default. The Add Task page reloads to show the update options.sourcefire. • • Select Software to download the most recent software patch. spaces. Specify how you want to schedule the task. From the Job Type list. type a name using up to 255 alphanumeric characters. or dashes. Version 4. you should set up a proxy as described in Configuring Network Settings on page 377 to allow it to download updates from the Sourcefire Support site (https://support. 4.

Note that if you manually download an update to an appliance that cannot access the Support site. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host.Scheduling Tasks Automating Software Updates Chapter 13 7. Instead you must manually push the update as described in Updating System Software on page 398. Version 4. so you should try to keep it relatively short. TIP! The comment field appears in the View Tasks section of the page. Select Operations > Tools > Scheduling. Click Add Task. The Add Task page appears. The task is created. information about the push process status is reported on the Tasks page. The Scheduling page appears. Automating Software Pushes Requires: DC/MDC If you are installing software or vulnerability database updates on managed 3D Sensors. 9. 8. To push software updates to managed sensors: Access: Maint/Admin 1. 2. you must push the software to the managed sensors before installing. in the Comment field. IMPORTANT! You must have a valid email relay server configured to send status messages. type a comment using up to 255 alphanumeric characters. When you create the task to push software updates to managed sensors. When you push software updates to managed sensors. in the Email Status To: field. Optionally. Optionally. or periods. make sure you allow enough time between the push task and a scheduled install task for the updates to be copied to the sensor. you cannot schedule pushes to managed sensors. spaces. See Viewing the Status of Long-Running Tasks on page 600 for more information. Click Save. type the email address (or multiple email addresses separated by commas) where you want status messages sent.9.1 Sourcefire 3D System Administrator Guide 433 .

spaces.1 Sourcefire 3D System Administrator Guide 434 .Scheduling Tasks Automating Software Updates Chapter 13 3. Both options are selected by default. In the Update Items section. TIP! The Current Time field indicates the current time on the appliance. TIP! The comment field appears in the View Tasks section of the page. The page reloads to show the options for pushing updates. use the drop-down lists to specify the start date and time. From the Sensor list. specify which updates you want to push to your managed sensors. 4. 6. type a name using up to 255 alphanumeric characters. In the Job Name field. 7. Optionally. Version 4.9. Once or Recurring. select the sensor that you want to receive updates. Requires: DC + RNA Select Vulnerability Database to push the VDB update. so you should try to keep it relatively short. Specify how you want to schedule the task. 8. From the Job Type list. See Configuring a Recurring Task on page 426 for details. in the Comment field. or dashes. • For one-time tasks. spaces. or periods. • • Select Software to push the software update. • For recurring tasks. type a comment using up to 255 alphanumeric characters. you have several options for setting the interval between instances of the task. 5. select Push Latest Update.

2. Instead you must manually install the update as described in Updating System Software on page 398. you cannot schedule installation of that update. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. IMPORTANT! You must have a valid email relay server configured to send status messages. The Add Task page appears.1 Sourcefire 3D System Administrator Guide 435 . Version 4. See Viewing the Status of Long-Running Tasks on page 600 for more information. the appliance may reboot after the software is installed. The Scheduling page appears. in the Email Status To: field. Automating Software Installs Requires: IPS or DC/ MDC If you are using a Defense Center to create a task to install a software update on a managed sensor. Click Add Task. make sure you allow enough time between the task that pushes the update to the sensor and the task that installs the update. Note that if you manually download an update to an appliance that cannot access the Support site. Optionally. The task is added. See Automating Software Pushes on page 433 for information about pushing updates to managed sensors. 10. Select Operations > Tools > Scheduling. type the email address (or multiple email addresses separated by commas) where you want status messages sent.9. To schedule a software installation task: Access: Maint/Admin 1. Click Save. WARNING! Depending on the update being installed. You can check the status of a running task on the Task Status page.Scheduling Tasks Automating Software Updates Chapter 13 9.

• For recurring tasks. or periods. from the Sensor list. 6. If you are using a Defense Center. 5. The page reloads to show the options for installing updates. Once or Recurring. From the Job Type list. you have several options for setting the interval between instances of the task. Optionally. TIP! The Current Time field indicates the current time on the appliance. or dashes. TIP! The comment field appears in the View Tasks section of the page. type a name using up to 255 alphanumeric characters. Select the name of the Defense Center to install the update there. use the drop-down lists to specify the start date and time. In the Job Name field. See Configuring a Recurring Task on page 426 for details. 4. select Install Latest Update. The Defense Center version of the page is shown below. In the Update Items section. 8. select Software to install the software update.Scheduling Tasks Automating Software Updates Chapter 13 3. type a comment using up to 255 alphanumeric characters. so you should try to keep it relatively short.1 Sourcefire 3D System Administrator Guide 436 .9. Specify how you want to schedule the task. • For one-time tasks. Select the sensor where you want to install the update. spaces. spaces. you have the following options: • • 7. in the Comment field. Version 4.

you must automate two separate steps: 1. Install the VDB update on the Defense Center and on those managed sensors. 2. For example. if you schedule a task to install an update and the update has not fully Version 4. Push the VDB update to your managed 3D Sensors that are using the RNA component. This ensures that your Defense Center is correctly setting the impact flag on the intrusion events generated by the traffic on your network. Optionally. You can use the scheduling feature to download and install the latest VDB updates. in the Email Status To: field. 2. The scheduled software installation task is added.9. Installing the VDB update. 10. You can check the status of a running task on the Task Status page. When automating VDB updates for managed sensors with RNA.Scheduling Tasks Automating Vulnerability Database Updates Chapter 13 9. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. 3. Downloading the VDB update. Always allow enough time between tasks for the process to complete. Click Save. type the email address (or multiple email addresses separated by commas) where you want status messages sent. make sure that you download and install VDB updates and SEUs on a regular basis. TIP! If your Sourcefire 3D System deployment includes IPS and RNA monitoring the same network segments. you must schedule three tasks in this order: 1. thereby ensuring that RNA is using the most up-to-date information to evaluate the hosts on your network. Download the VDB update on your Defense Center. Automating Vulnerability Database Updates Sourcefire uses vulnerability database (VDB) updates to distribute new operating system fingerprints as we expand the list of operating systems that RNA recognizes. When automating VDB updates for your Defense Center. VDB updates also include new vulnerabilities discovered by the Sourcefire Vulnerability Research Team (VRT). IMPORTANT! You must have a valid email relay server configured to send status messages.1 Sourcefire 3D System Administrator Guide 437 . See Viewing the Status of Long-Running Tasks on page 600 for more information.

Instead you must manually push or install the updates as described in Updating System Software on page 398.Scheduling Tasks Automating Vulnerability Database Updates Chapter 13 downloaded. See the following sections for more information: • • • Automating VDB Update Downloads on page 438 Automating VDB Update Pushes on page 440 Automating VDB Update Installs on page 442 Automating VDB Update Downloads Requires: DC/MDC + RNA You can create a scheduled task that automatically downloads the latest vulnerability database updates from Sourcefire. The Scheduling page appears. if the scheduled installation task repeats daily. IMPORTANT! You cannot download the VDB using a scheduled task on a sensor. it will install the downloaded VDB update when it runs the next day. you cannot schedule either pushes to managed sensors (on the Defense Center) or installs (on any appliance). You must download the VDB on the Defense Center and push it to the sensor. 2. To automate VDB updates: Access: Maint/Admin 1. you can use the Once option to download and install VDB updates during off-peak hours after you learn that an update has been released. Select Operations > Tools > Scheduling. Version 4. If you want to have more control over this process. The Add Task page appears. Click Add Task. Note that if you manually download an update to an appliance that cannot access the Support site. However.9. the installation task will not succeed.1 Sourcefire 3D System Administrator Guide 438 .

type a name using up to 255 alphanumeric characters. In the Job Name field. you should set up a proxy as described in Configuring Network Settings on page 377 to allow it to download updates from the Sourcefire Support site (https://support. Version 4. In the Update Items section. 5.com/). From the Job Type list. make sure Vulnerability Database is selected. use the drop-down lists to specify the start date and time. spaces. IMPORTANT! If your appliance is not directly connected to the Internet. 4. • For recurring tasks.sourcefire. TIP! The comment field appears in the View Tasks section of the page.9. in the Comment field. Specify how you want to schedule the task. The Add Task page reloads to show the update options. Once or Recurring. you have several options for setting the interval between instances of the task. • For one-time tasks. type a comment using up to 255 alphanumeric characters. so you should try to keep it relatively short.Scheduling Tasks Automating Vulnerability Database Updates Chapter 13 3. See Configuring a Recurring Task on page 426 for details. or periods. 7. spaces. Optionally. or dashes. select Download Latest Update. Both the Software and Vulnerability Database options are selected by default.1 Sourcefire 3D System Administrator Guide 439 . TIP! The Current Time field indicates the current time on the appliance. 6.

See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. Version 4. type the email address (or multiple email addresses separated by commas) where you want status messages sent. 9. See Viewing the Status of Long-Running Tasks on page 600 for more information. Select Operations > Tools > Scheduling. The task is created. you must push the update to the managed sensors before installing. To push VDB updates to managed 3D Sensors with RNA: Access: Maint/Admin 1. you cannot schedule pushes to managed sensors. 2. Note that if you manually download an update to an appliance that cannot access the Support site. The Add Task page appears. information about the process status is reported on the Tasks page. Instead you must manually push the update as described in Updating System Software on page 398. When you push VDB updates to managed sensors. WARNING! You must download vulnerability database updates before you can push them to managed sensors.1 Sourcefire 3D System Administrator Guide 440 . Automating VDB Update Pushes Requires: DC/MDC + 3D Sensor + RNA If you are installing vulnerability database updates on managed 3D Sensors with RNA. The Scheduling page appears. Optionally. IMPORTANT! You must have a valid email relay server configured to send status messages. in the Email Status To: field.9. Click Add Task. Click Save.Scheduling Tasks Automating Vulnerability Database Updates Chapter 13 8.

or dashes. use the drop-down lists to specify the start date and time. TIP! The Current Time field indicates the current time on the appliance. • For recurring tasks. type a comment using up to 255 alphanumeric characters. Version 4. type a name using up to 255 alphanumeric characters. or periods. make sure Vulnerability Database is selected. 8. 6.9. in the Comment field.1 Sourcefire 3D System Administrator Guide 441 . spaces. Both the Software and Vulnerability Database options are selected by default. Optionally.Scheduling Tasks Automating Vulnerability Database Updates Chapter 13 3. select the sensor that you want to receive updates. In the Update Items section. 7. 4. The page reloads to show the options for pushing updates. • For one-time tasks. spaces. Specify how you want to schedule the task. From the Job Type list. so you should try to keep it relatively short. TIP! The comment field appears in the View Tasks section of the page. select Push Latest Update. 5. Once or Recurring. In the Job Name field. From the Sensor list. you have several options for setting the interval between instances of the task. See Configuring a Recurring Task on page 426 for details.

To schedule a software installation task: Access: Maint/Admin 1. The Scheduling page appears. Click Add Task. 2. you can schedule the installation process. You should allow enough time for a scheduled VDB update to download when you set up a scheduled task to install it.9. You can check the status of a running task on the Task Status page. The task is added. Version 4. you must allow enough time between the task that pushes the update to the sensor and the task that installs the update. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. See Viewing the Status of Long-Running Tasks on page 600 for more information. If you are creating a task to install a VDB update on a managed sensor. Select Operations > Tools > Scheduling.Scheduling Tasks Automating Vulnerability Database Updates Chapter 13 9. type the email address (or multiple email addresses separated by commas) where you want status messages sent. The Add Task page appears. Instead you must manually install the updates as described in Updating System Software on page 398. in the Email Status To: field. 10. you cannot schedule installation of that update.1 Sourcefire 3D System Administrator Guide 442 . Automating VDB Update Installs Requires: DC/MDC + RNA After you have downloaded a VDB update. Note that if you manually download an update to an appliance that cannot access the Support site. See Automating VDB Update Pushes on page 440 for information about pushing updates to managed sensors. Optionally. Click Save. IMPORTANT! You must have a valid email relay server configured to send status messages.

so you should try to keep it relatively short. If you want to install the update on the Defense Center.1 Sourcefire 3D System Administrator Guide 443 . From the Job Type list. 4. type a comment using up to 255 alphanumeric characters. you have several options for setting the interval between instances of the task. • For recurring tasks. • For one-time tasks. spaces. in the Comment field. 5. If you want to install the update on a managed sensor. or periods. See Configuring a Recurring Task on page 426 for details. Version 4. 6. 8. select Install Latest Update. Specify how you want to schedule the task. From the Sensor list.Scheduling Tasks Automating Vulnerability Database Updates Chapter 13 3. or dashes. type a name using up to 255 alphanumeric characters. you have the following options: • • 7. select the name of the sensor from the drop-down list. select Vulnerability Database to install the VDB update. use the drop-down lists to specify the start date and time. spaces. select the name of the Defense Center from the drop-down list. In the Update Items section. The page reloads to show the options for installing updates. Once or Recurring.9. TIP! The Current Time field indicates the current time on the appliance. In the Job Name field. Optionally. TIP! The comment field appears in the View Tasks section of the page.

however. The scheduled VDB installation task is added.9. Optionally. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. 10. 3. in the Email Status To: field. The selected subtasks present in the Import SEU task occur in the following order: download.Scheduling Tasks Automating SEU Imports Chapter 13 9. Applying an intrusion policy from a Defense Center to a managed sensor after you import an SEU does not apply the SEU to the sensor. Automating SEU Imports Requires: IPS or DC/ MDC + IPS As new vulnerabilities are identified. However. the Sourcefire Vulnerability Research Team (VRT) releases Security Enhancement Updates (SEUs). The Import SEU task allows you to schedule the following subtasks separately or to combine them into one scheduled task: 1. Re-apply your intrusion policy so that the new SEU takes effect. you also must re-apply your intrusion policies on your managed 3D Sensors with IPS. that if you changed a rule state. you also allow the Version 4. Note. IMPORTANT! You must have a valid email relay server configured to send status messages. Click Save. install. type the email address (or multiple email addresses separated by commas) where you want status messages sent. Once one subtask completes. the SEU does not override your change. If you allow SEUs to update your base policy. any new rules or features provided by the SEU that are enabled in the policy you apply to the sensor are also enabled on the sensor by that policy. those changes are also imported. You can automatically download and install SEUs. An SEU contains new and updated standard text rules and shared object rules and may contain updated versions of Snort® and features such as preprocessors and decoders. and policy re-apply. Download the latest SEU. VRT sometimes uses an SEU to change the default state of one or more rules in a default policy. You can check the status of a running task on the Task Status page. the next configured subtask begins. Import the SEU. See Viewing the Status of Long-Running Tasks on page 600 for more information. Note that on the Defense Center. If you enable Update when a new SEU is installed for the base policy of an existing policy and the SEU contains changes to the default rule states for existing rules in that base policy. 2. rule state update. Note that you can only re-apply policies applied from the appliance where the scheduled task is configured.1 Sourcefire 3D System Administrator Guide 444 .

Select Operations > Tools > Scheduling. In addition. Make sure your process for downloading and importing SEUs complies with your security policies. Version 4.8. For more information on the recurring SEU import feature and a comparison of the two methods of setting up recurring imports.2 or higher to import recurring SEUs on the Import SEU page. however. SEUs can be quite large. you can also use the recurring SEU import feature on the Import SEU page. The page reloads to show the options for importing SEUs. select Import SEU.1 Sourcefire 3D System Administrator Guide 445 .Scheduling Tasks Automating SEU Imports Chapter 13 SEU to change the default state of a rule in your policy when the default state changes in the default policy you used to create your policy (or in the default policy it is based on). Click Add Task. the SEU will not override your change. The Add Task page appears. see Importing SEUs and Rule Files in the Analyst Guide. Note. IMPORTANT! SEUs may contain new binaries. Note that you must be using Snort 2. To schedule an Import SEU task: Access: Maint/Admin 1. that if you have changed the rule state. In addition to configuring SEU imports on the Scheduling page. The Scheduling page appears.9. From the Job Type list. 3. 2. so make sure you schedule downloads during periods of low network use.

spaces. To use this task to install the latest downloaded SEU. use the drop-down lists to specify the start date and time. To use this task to download the latest SEU. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. 11. IMPORTANT! You must have a valid email relay server configured to send status messages. or periods. type a comment using up to 255 alphanumeric characters. in the Comment field. To re-apply intrusion policies after installing an SEU. 8.1 Sourcefire 3D System Administrator Guide 446 . 6. type the email address (or multiple email addresses separated by commas) where you want status messages sent. or dashes. spaces. select Install the latest downloaded SEU. Once or Recurring. See Configuring a Recurring Task on page 426 for details. Automating Intrusion Policy Applications Requires: IPS or DC/ MDC + IPS You can automatically apply intrusion policies at scheduled intervals. TIP! The comment field appears in the View Tasks section of the page. TIP! The Current Time field indicates the current time on the appliance. Version 4. 5. in the Email Status To: field. Optionally. • For recurring tasks. you have several options for setting the interval between instances of the task.Scheduling Tasks Automating Intrusion Policy Applications Chapter 13 4. select Reapply intrusion policies after the SEU import completes. Optionally. select Download the latest SEU from the support site. Specify how you want to schedule the task. Click Save. The task is created. 7. • For one-time tasks. In the Job Name field.9. type a name using up to 255 alphanumeric characters. 10. 9. This feature is useful if you need to use different policies during different times of the day. so you should try to keep it relatively short.

2. TIP! The Current Time field indicates the current time on the appliance. See Configuring a Recurring Task on page 426 for details. 6. 4. select the intrusion policy you want to apply from the drop-down list or select Policy Default to apply the policy to each detection engine targeted in the policy. 3. From the Job Type list. type a name using up to 255 alphanumeric characters. Click Add Task. • For recurring tasks. or dashes.Scheduling Tasks Automating Intrusion Policy Applications Chapter 13 To automate intrusion policy application: Access: Maint/Admin 1. Version 4. select Apply Policy.1 Sourcefire 3D System Administrator Guide 447 . • For one-time tasks. Select Operations > Tools > Scheduling. The page reloads to show the options for applying an intrusion policy. In the Policy Name field. In the Job Name field.9. use the drop-down lists to specify the start date and time. The Scheduling page appears. Specify how you want to schedule the task. 7. you have several options for setting the interval between instances of the task. 5. In the Detection Engine field. select the detection engine where you want to apply the policy. The Add Task page appears. spaces. Once or Recurring.

IMPORTANT! You must have a valid email relay server configured to send status messages. 10. Optionally. 9. in the Email Status To: field.1 Sourcefire 3D System Administrator Guide 448 . type a comment using up to 255 alphanumeric characters. You can check the status of a running task on the Task Status page. To automate a report: Access: Maint/Admin 1.Scheduling Tasks Automating Reports Chapter 13 8. Click Add Task. The Scheduling page appears. Automating Reports Requires: IPS or DC/ MDC You can automate reports so that they run at regular intervals. See Viewing the Status of Long-Running Tasks on page 600 for more information. Optionally. 2. Select Operations > Tools > Scheduling. Version 4. or periods. See Creating a Report Profile on page 246 for more information about using the report designer to create a report profile. However. Click Save. TIP! The comment field appears in the View Tasks section of the page. The Add Task page appears. type the email address (or multiple email addresses separated by commas) where you want status messages sent. in the Comment field. you must design a profile for your report before you can configure it as a scheduled task. The task is created. spaces.9. so you should try to keep it relatively short. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host.

type a name using up to 255 alphanumeric characters. in the Comment field. Once or Recurring. IMPORTANT! sensors. in the Remote Run field. 8. or periods. See Configuring a Recurring Task on page 426 for details. spaces. or dashes.Scheduling Tasks Automating Reports Chapter 13 3. The Defense Center version of the page is displayed below. From the Job Type list. The page reloads to show the options for setting up a report to run automatically. Specify how you want to schedule the task. 5. 6. spaces.1 Sourcefire 3D System Administrator Guide 449 . 4. In the Report Profile field. • For recurring tasks. TIP! The Current Time field indicates the current time on the appliance. type a comment using up to 255 alphanumeric characters. You cannot run remote reports on Crossbeam-based software Requires: DC If you want to run the report on a managed sensor.9. 7. TIP! The comment field appears in the View Tasks section of the page. • For one-time tasks. use the drop-down lists to specify the start date and time. In the Job Name field. Optionally. Version 4. select Reports. you have several options for setting the interval between instances of the task. select the report profile that you want to use from the drop-down list. so you should try to keep it relatively short. select the name of the sensor from the drop-down list.

Version 4. 1. in the Email Status To: field. Create a scan instance to define the Nessus server to be used by your scan. Automating Nessus Scans You can schedule regular Nessus scans of targets on your network. see Nessus Scan Remediations in the Analyst Guide. 2. see Creating a Nessus Scan Instance on page 643. You can also schedule scans to test for recurrent vulnerabilities to attacks that have happened in the past. If you do not have an existing external Nessus server. The task is created. Click Save. IMPORTANT! You must have a valid email relay server configured to send status messages.1 Sourcefire 3D System Administrator Guide 450 . Preparing Your System to Run a Nessus Scan If you have not used the Nessus scanning capability before. you need to complete several Nessus configuration steps prior to defining a scheduled scan. see Configuring a Local Nessus Server on page 641. set up the Nessus server on your Defense Center. Automated scans allow you to test periodically to make sure that operating system updates or other changes do not introduce vulnerabilities on your enterprise-critical systems. IMPORTANT! Make note of the name of the scan instance you create.Scheduling Tasks Automating Nessus Scans Chapter 13 9. 10. You need to select this name when prompted for the Nessus Remediation name when setting up the scheduled scan.9. For more information. For more information on setting up a Nessus server connection profile. See the following sections for more information: • • Preparing Your System to Run a Nessus Scan on page 450 Scheduling a Nessus Scan on page 451 Note that a Policy & Response Administrator can also use a Nessus scan as a remediation. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. Optionally. type the email address (or multiple email addresses separated by commas) where you want status messages sent. For more information on starting the server and configuring and activating a Nessus user.

Select Operations > Tools > Scheduling. 4.Scheduling Tasks Automating Nessus Scans Chapter 13 3. The page reloads to show the options for automating Nessus scans. For more information on setting up a remediation definition. Create a remediation definition to define what plugins and Nessus scan settings should be used when the scheduled scan runs. The Scheduling page appears. Continue with Scheduling a Nessus Scan. 2. see Creating a Nessus Remediation on page 646. Click Add Task. The Add Task page appears. Version 4.9. Scheduling a Nessus Scan Requires: DC + RNA You can automate Nessus scanning using a specific scan remediation by scheduling the scan. select Nessus Scan. To schedule Nessus scanning: Access: Maint/Admin 1. For more information on setting up a scan target. see Creating a Nessus Scan Target on page 645. 3. From the Job Type list. 5.1 Sourcefire 3D System Administrator Guide 451 . Create a scan target to define the target hosts and host ports to scan.

use the drop-down lists to specify the start date and time. or periods. • For recurring tasks. 9. TIP! The comment field appears in the View Tasks section of the page. In the Job Name field. See Configuring a Recurring Task on page 426 for details. Synchronizing Nessus Plugins Requires: DC + RNA You can automate synchronization with the Nessus server to obtain an up-to-date list of plugins before you scan. 8. In the Nessus Target field. Click Save. Version 4. or dashes.Scheduling Tasks Synchronizing Nessus Plugins Chapter 13 4. In the Nessus Remediation field. type the email address (or multiple email addresses separated by commas) where you want status messages sent. you have several options for setting the interval between instances of the task. type a comment using up to 255 alphanumeric characters. Specify how you want to schedule the task. You may want to schedule your plugin synchronization to occur shortly before your scheduled Nessus scans to make sure that you scan with the latest list of plugins. 10. Optionally. select the scan target that defines the target hosts you want to scan.9. in the Email Status To: field. type a name using up to 255 alphanumeric characters. 6. select the Nessus remediation for the Nessus server where you want to run the scan. spaces. Optionally. Once or Recurring. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. 7. 5.1 Sourcefire 3D System Administrator Guide 452 . IMPORTANT! You must have a valid email relay server configured to send status messages. spaces. so you should try to keep it relatively short. The task is created. • For one-time tasks. TIP! The Current Time field indicates the current time on the appliance. in the Comment field.

spaces. 5. 4. • For one-time tasks. 7. 6.Scheduling Tasks Synchronizing Nessus Plugins Chapter 13 To schedule Nessus plugin synchronization: Access: Maint/Admin 1.1 Sourcefire 3D System Administrator Guide 453 . or dashes. spaces. The page reloads to show the Nessus plugin synchronization options. The Current Time field indicates the current time on the appliance. 2. 3. Version 4. • For recurring tasks. TIP! The comment field appears in the View Tasks section of the page. In the Nessus Instance field. so you should try to keep it relatively short. See Configuring a Recurring Task on page 426 for details. or periods. Optionally. you have several options for setting the interval between instances of the task.9. Click Add Task. select Synchronize Nessus Plugins. Specify how you want to schedule the task. The Scheduling page appears. in the Comment field. The Add Task page appears. use the drop-down lists to specify the start date and time. type a comment using up to 255 alphanumeric characters. In the Job Name field. select the instances with the Nessus plugins that you want to synchronize. From the Job Type list. type a name using up to 255 alphanumeric characters. Once or Recurring. Select Operations > Tools > Scheduling.

For more information.9. see Creating an Nmap Scan Target in the Analyst Guide. Because RNA cannot update Nmap-supplied data. 2. For more information on setting up a scan target. You can also schedule scans to automatically test for unidentified services on hosts in your network. see Nmap Scan Remediations in the Analyst Guide. Create a scan instance to define the Nmap server to be used by your scan. Version 4. You need to select this name when prompted for the Nmap Configuration name when setting up the scheduled scan. Click Save. which resolves the conflict. you need to rescan periodically to keep that data up to date. IMPORTANT! Make note of the name of the scan instance you create. 1. see Creating an Nmap Scan Instance in the Analyst Guide. Automating Nmap Scans You can schedule regular Nmap scans of targets on your network. For more information on setting up a Nmap server connection profile.1 Sourcefire 3D System Administrator Guide 454 . Preparing Your System for an Nmap Scan If you have not used the Nmap scanning capability before. Automated scans allow you to refresh operating system and service information previously supplied by an Nmap scan. type the email address (or multiple email addresses separated by commas) where you want status messages sent. 9. that conflict can trigger an Nmap scan. in the Email Status To: field. Create a scan target to define the target hosts and host ports to scan. when an operating system conflict occurs on a host. you must complete several Nmap configuration steps prior to defining a scheduled scan. Optionally. IMPORTANT! You must have a valid email relay server configured to send status messages.Scheduling Tasks Automating Nmap Scans Chapter 13 8. Running the scan obtains updated operating system information for the host. See the following sections for more information: • • Preparing Your System for an Nmap Scan Scheduling an Nmap Scan Note that a Policy & Response Administrator can also use an Nmap scan as a remediation. The task is created. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. For example.

select Nmap Scan. Version 4. If you plan to scan a host using Nmap. any Nmap scan results are discarded and RNA resumes monitoring of all operating system and service data for the host.Scheduling Tasks Automating Nmap Scans Chapter 13 3. Click Add Task.1 Sourcefire 3D System Administrator Guide 455 . Scheduling an Nmap Scan Requires: DC + RNA You can schedule a scan of a host or hosts on your network using the Nmap utility. If the host is deleted from the network map and re-added. The page reloads to show the options for automating Nmap scans. Continue with Scheduling an Nmap Scan.9. RNA no longer updates the information replaced by Nmap for the host. Create a remediation definition to define what plugins and Nmap scan settings should be used when the scheduled scan runs. see Creating an Nmap Remediation in the Analyst Guide. The Add Task page appears. you may want to set up regularly scheduled scans to keep Nmap-supplied operating system and services up to date. For more information on setting up a remediation definition. 2. To schedule Nmap scanning: Access: Maint/Admin 1. Nmap-supplied service and operating system data remains static until you run another Nmap scan. Once Nmap replaces a host’s operating system or services detected by RNA with the results from an Nmap scan. Select Operations > Tools > Scheduling. 3. 4. The Scheduling page appears. From the Job Type list.

spaces. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. type a comment using up to 255 alphanumeric characters. 9. Optionally. Click Save. type the email address (or multiple email addresses separated by commas) where you want status messages sent. • For one-time tasks. in the Comment field. See Configuring a Recurring Task on page 426 for details. spaces. Version 4. select the Nmap remediation to use when running the scan. In the Job Name field. In the Nmap Remediation field. type a name using up to 255 alphanumeric characters. in the Email Status To: field. you must discard your changes in that policy and commit the policy if you want the policy to reflect the automatically generated recommendations. Once or Recurring. The task is created. Specify how you want to schedule the task. you have several options for setting the interval between instances of the task. IMPORTANT! You must have a valid email relay server configured to send status messages. 7. 8. or periods. use the drop-down lists to specify the start date and time.9. 5. TIP! The Current Time field indicates the current time on the appliance. • For recurring tasks. Automating Recommended Rule State Generation Requires: DC + RNA + IPS IMPORTANT! If the system automatically generates scheduled recommendations for an intrusion policy with unsaved changes. 6. so you should try to keep it relatively short. 10. select the scan target that defines the target hosts you want to scan.1 Sourcefire 3D System Administrator Guide 456 . In the Nmap Target field. Optionally. or dashes. See Committing Intrusion Policy Changes in the Analyst Guide for more information. TIP! The comment field appears in the View Tasks section of the page.Scheduling Tasks Automating Recommended Rule State Generation Chapter 13 4.

2. From the Job Type list. See Managing RNA Rule State Recommendations in the Analyst Guide for more information. 4.1 Sourcefire 3D System Administrator Guide 457 .9. 3. Optionally. the system automatically generates recommended rule states. To generate recommendations: Access: Maint/Admin 1. where you can configure RNA Recommended Rules in a policy. click the policies link in the Job Type field to display the Detection & Prevention page. The Add Task page appears. depending on the configuration of your policy. Select Operations > Tools > Scheduling. When the task runs. The page reloads to show the options for generating RNA-recommended rule states. Optionally. it also modifies the states of intrusion rules based on the criteria described in Managing RNA Rule State Recommendations in the Analyst Guide.Scheduling Tasks Automating Recommended Rule State Generation Chapter 13 You can automatically generate rule state recommendations based on RNA data for your network using the most recently saved configuration settings in your custom intrusion policy. select RNA Recommended Rules. Version 4. Click Add Task. Modified rule states take effect the next time you apply your intrusion policy. See Using RNA Recommendations in the Analyst Guide for more information. The Scheduling page appears.

in the Comment field. TIP! The Current Time field indicates the current time on the appliance.9. Once or Recurring. select one or more policies. Specify how you want to schedule the task. type the email address (or multiple email addresses separated by commas) where you want status messages sent. The task is created. Viewing Tasks After adding scheduled tasks. 10. you have several options for setting the interval between instances of the task. The View Options section of the page allows you to view scheduled tasks using a calendar and a list of scheduled tasks. IMPORTANT! You must have a valid email relay server configured to send status messages. • For recurring tasks. use the drop-down lists to specify the start date and time. Click Save.Scheduling Tasks Viewing Tasks Chapter 13 5. 6.1 Sourcefire 3D System Administrator Guide 458 . TIP! The comment field appears in the View Tasks section of the page. • For one-time tasks. 8. or dashes. Next to Policies. you can view them and evaluate their status. select one or more policies where you want to generate recommendations. type a comment using up to 255 alphanumeric characters. In the Job Name field. Click the All Policies check box to select all policies. You have the following options: • • In the Policies field. so you should try to keep it relatively short. Version 4. spaces. type a name using up to 255 alphanumeric characters. Optionally. or periods. Use the Shift and Ctrl keys to select multiple policies. Optionally. 7. in the Email Status To: field. 9. spaces. See Configuring a Recurring Task on page 426 for details. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host.

Version 4. To view scheduled tasks using the calendar: Access: Maint/Admin 1.Scheduling Tasks Viewing Tasks Chapter 13 See the following sections for more information: • • Using the Calendar on page 459 Using the Task List on page 460 Using the Calendar Requires: DC/MDC or 3D Sensor The Calendar view option allows you to view which scheduled tasks occur on which day. Click < to move back one month. You can perform the following tasks using the calendar view: • • Click << to move back one year.9. The Scheduling page appears. 2. Select Operations > Tools > Scheduling.1 Sourcefire 3D System Administrator Guide 459 .

(See Using the Calendar on page 459 for more information. Click a specific task on a date to view the task in a task list table below the calendar. Describes the current status for a scheduled task. Click >> to move forward one year.1 Sourcefire 3D System Administrator Guide 460 . Click Today to return to the current month and year. Version 4. you can access it by selecting a date or task from the calendar. • A check mark icon indicates that the task ran successfully.) Task List Columns Column Name Type Start Time Frequency Comment Status Description Displays the name of the scheduled task. see Using the Task List on page 460. Click a date to view all scheduled tasks for the specific date in a task list table below the calendar.Scheduling Tasks Viewing Tasks Chapter 13 • • • • • • Click > to move forward one month. Displays the comment that accompanies the scheduled task. • A red ! indicates that the task failed. Deletes the scheduled task. Creator Delete Displays the name of the user that created the scheduled task. Click Add Task to schedule a new task. The task list appears at below the calendar when you open the calendar.9. Using the Task List Requires: DC/MDC or 3D Sensor The Task List shows a list of tasks along with their status. • A question mark icon indicates that the task is in an unknown state. In addition. Displays the scheduled start date and time. Displays the type of scheduled task. IMPORTANT! For more information about using the task list. Displays how often the task is run.

Your change are saved and the Scheduling page appears again. 2. 4. The Scheduling page appears.9. once or recurring.Scheduling Tasks Editing Scheduled Tasks Chapter 13 Editing Scheduled Tasks Requires: DC/MDC or 3D Sensor You can edit a scheduled task that you previously created. Edit the task to meet your needs. See the following sections for more information: • • • • • • • • • • Automating Backup Jobs on page 428 Automating Software Updates on page 430 Automating Vulnerability Database Updates on page 437 Automating SEU Imports on page 444 Automating Intrusion Policy Applications on page 446 Automating Reports on page 448 Automating Nessus Scans on page 450 Synchronizing Nessus Plugins on page 452 Automating Nmap Scans on page 454 Automating Recommended Rule State Generation on page 456 5. and how often the task runs.1 Sourcefire 3D System Administrator Guide 461 . only that task is deleted. Locate the task you want to edit in the table and click Edit. This feature is especially useful if you want to test a scheduled task once to make sure that the parameters are correct. Later. the job name. Click either the task that you want to edit or the day on which the task appears. You can delete a specific one-time task that has not yet run or you can delete every instance of a recurring task. You cannot change the type of job. Click Save to save your edits. If you delete a task that is scheduled to run once. Select Operations > Tools > Scheduling. including the start time. The Edit Task page appears showing the details of the task you selected. you can change it to a recurring task. after the task completes successfully. Deleting Scheduled Tasks There are two types of deletions you can perform from the Schedule View page. The Task Details table containing the selected task or tasks appears. To edit an existing scheduled task: Access: Maint/Admin 1. If you delete an instance of a recurring task. Version 4. 3. The remaining options are determined by the task you are editing. all instances of the task are deleted.

Version 4.Scheduling Tasks Deleting Scheduled Tasks Chapter 13 The following sections describe how to delete tasks: • • To delete all instances of a task. see Deleting a Recurring Task on page 462. To delete a single task or. delete a task record: Access: Maint/Admin 1.9. 2. To delete a single instance of a task. The page reloads to display a table of tasks below the calendar. you automatically delete all instances of that task. The Scheduling page appears. Locate an instance of the recurring task you want to delete in the table and click Delete. Click the task that you want to delete or the day on which the task appears. The Scheduling page appears. The instance of the task you selected is deleted. if it has already run. select an instance of the recurring task you want to delete. 2. see Deleting a One-Time Task on page 462. Deleting a Recurring Task Requires: DC/MDC or 3D Sensor When you delete one instance of a recurring task. Select Operations > Tools > Scheduling.1 Sourcefire 3D System Administrator Guide 462 . Select Operations > Tools > Scheduling. On the calendar. 3. A table containing the selected task or tasks appears. To delete a recurring task: Access: Maint/Admin 1. All instances of the recurring task are deleted. Deleting a One-Time Task Requires: DC/MDC or 3D Sensor You can delete a one-time scheduled task or delete the record of a previously-run scheduled task using the task list. Locate the task you want to delete in the table and click Delete. 3.

For more information. intrusion event information. and statistics for the Data Correlator and RNA processes for the current day. on the Host Statistics page you can monitor basic host statistics. Version 4.9. you can also use the health monitor to monitor disk usage and alert on low disk space conditions. see Understanding Health Monitoring on page 483. You can also monitor both summary and detailed information on all processes that are currently running on the Defense Center or 3D Sensor. all on a single page.1 Sourcefire 3D System Administrator Guide 463 . The following sections provide more information about the monitoring features that the system provides: • Viewing Host Statistics on page 464 describes how to view host information such as: • • • • • • system uptime disk and memory usage RNA process statistics Data Correlator statistics system processes intrusion event information On the Defense Center. For example.Monitoring the System Chapter 14 Administrator Guide The Sourcefire 3D System provides many useful monitoring features to assist you in the daily administration of your system.

1 Sourcefire 3D System Administrator Guide 464 . Viewing RNA Performance Statistics on page 478 describes how to view RNA performance statistics and how to generate graphs based on these statistics.requires RNA). Version 4. Viewing IPS Performance Statistics on page 476 describes how to view IPS performance statistics and how to generate graphs based on these statistics. Understanding Running Processes on page 471 describes the basic system processes that run on the appliance. and minutes since the system was last started. see the RNA Process Statistics table on page 466 for details intrusion event information (requires IPS). and 15 minutes. Viewing System Process Status on page 468 describes how to view basic process status. see the Data Correlator Process Statistics table on page 465 for details RNA process statistics (Defense Center only . Host Statistics Category Time Uptime Memory Usage Load Average Description The current time on the system. 5 minutes. see the Intrusion Event Information table on page 467 for details The Host Statistics table describes the host statistics listed on the Statistics page.Monitoring the System Viewing Host Statistics Chapter 14 • • • • Monitoring System Status and Disk Space Usage on page 468 describes how to view basic event and disk partition information. hours. • Viewing Host Statistics Requires: Any The Statistics page lists the current status of following: • • • • general host statistics. see the Host Statistics table on page 464 for details Data Correlator statistics (Defense Center only . The average number of processes in the CPU queue for the past 1 minute.9.requires RNA). The percentage of system memory that is being used. The number of days (if applicable).

in kilobytes Average amount of memory used by the Data Correlator for the current day. decoding. Click the arrow to view more detailed host statistics.User (%) CPU Usage .System (%) VmSize (KB) VmRSS (KB) Description Number of RNA events that the Data Correlator receives and processes per second Number of flows that the Data Correlator receives and processes per second Average percentage of CPU time spent on user processes for the current day Average percentage of CPU time spent on system processes for the current day Average size of memory allocated to the Data Correlator for the current day. and creates the RNA network map. in kilobytes Version 4. Data Correlator Process Statistics Category Events/Sec Flows/Sec CPU Usage . generates events. and analysis. Processes If your Sourcefire 3D System deployment includes a Defense Center managing 3D Sensors with RNA.9. The Data Correlator analyzes the information from the binary files. See Monitoring System Status and Disk Space Usage on page 468 for more information. using statistics gathered between 12:00AM and 11:59PM for each detection engine.Monitoring the System Viewing Host Statistics Chapter 14 Host Statistics (Continued) Category Disk Usage Description The percentage of the disk that is being used. the RNA process correlates the data with the fingerprint and vulnerability databases. See Viewing System Process Status on page 468 for more information.1 Sourcefire 3D System Administrator Guide 465 . As the 3D Sensors perform data acquisition. The statistics that appear for RNA and the Data Correlator are averages for the current day. A summary of the processes running on the system. The Data Correlator Process Statistics table describes the statistics displayed for the Data Correlator process. you can also view statistics about the Data Correlator and RNA processes for the current day. and then produces binary files that are processed by the Data Correlator running on the Defense Center.

no intrusion event information is listed on this page. in kilobytes On 3D Sensors with IPS and on Defense Centers that manage sensors with IPS.9. you can also view the time and date of the last intrusion event.System (%) VmSize (KB) VmRSS (KB) Description Average percentage of packets dropped by the RNA process for the current day Average number of megabits per second processed by the RNA process for the current day Average number of packets per second processed by the RNA process for the current day Average percentage of CPU time spent by user processes for the current day Average percentage of CPU time spent by system processes for the current day Average size of memory allocated to the RNA process for the current day. This is also the case for 3D Sensors that cannot store events locally. The information in the Intrusion Event Information section of the Statistics page is based on intrusion events stored on the sensor rather than those sent to the Defense Center. RNA Process Statistics Category Packets Dropped (%) Mbits/Second Packets/Second CPU Usage . If you manage your sensor so that intrusion events are not stored locally.1 Sourcefire 3D System Administrator Guide 466 . in kilobytes Average amount of memory used by the RNA process for the current day.Monitoring the System Viewing Host Statistics Chapter 14 The RNA Process Statistics table describes the statistics displayed for the RNA process. Version 4. and the total number in the database. the total number of events that have occurred in the past hour and the past day.User (%) CPU Usage .

Intrusion Event Information Statistic Last Alert Was Total Events Last Hour Total Events Last Day Total Events in Database Description The date and time that the last event occurred The total number of events that occurred in the past hour The total number of events that occurred in the past twenty-four hours The total number of events in the events database To view the Statistics page: Access: Maint/Admin 1. The Statistics page appears.Monitoring the System Viewing Host Statistics Chapter 14 The Intrusion Event Information table describes the statistics displayed in the Intrusion Event Information section of the Statistics page.1 Sourcefire 3D System Administrator Guide 467 .9. The Defense Center version of the page is shown below. Select Operations > Monitoring > Statistics. Version 4.

TIP! On the Defense Center you can also use the health monitor to monitor disk usage and alert on low disk space conditions. To access disk usage information: Access: Maint/Admin 1. 2. The Disk Usage section expands. 2. Viewing System Process Status Requires: Any The Processes section of the Host Statistics page allows you to see the processes that are currently running on an appliance. and click Select Devices. You can monitor this page from time to time to ensure that enough disk space is available for system processes and the database. Select Operations > Monitoring > Statistics. For more information. If you are managing sensors with a Defense Center.9. Select the sensor name from the Select Device(s) box. Click the down arrow next to Disk Usage to expand it. you can use the Defense Center’s web interface to view the process status for any managed sensor. The Statistics page appears. You can use the Shift and Ctrl keys to select multiple devices at once. On the Defense Center. The page reloads.Monitoring the System Monitoring System Status and Disk Space Usage Chapter 14 2. Monitoring System Status and Disk Space Usage Requires: Any The Disk Usage section of the Statistics page provides a quick synopsis of partition status. Version 4. On the Defense Center. The Statistics page is updated with statistics for the devices that you selected. you can also list statistics for managed sensors. listing host statistics for each sensor you selected. It provides general process information and specific information for each running process. Click the down arrow next to Disk Usage to expand it.1 Sourcefire 3D System Administrator Guide 468 . From the Select Device(s) box and click Select Devices. see Understanding Health Monitoring on page 483. The Disk Usage section expands. to view disk usage information for a specific sensor: Access: Maint/Admin 1.

process is paging • X . unless the value is followed by m. which indicates megabytes) The process state: • D .process is being traced or stopped • W .process is in uninterruptible sleep (usually Input/Output) • N .process has a positive nice value • R . which is a value that indicates the scheduling priority of a process. Process Status Column Pid Username Pri Nice Description The process ID number The name of the user or group running the process The process priority The nice value. which indicates megabytes) The amount of resident paging files in memory (in kilobytes.9. Version 4.process is runnable (on queue to run) • S . Values range between -20 (highest priority) and 19 (lowest priority) The memory size used by the process (in kilobytes. Select Operations > Monitoring > Statistics. unless the value is followed by m. The Statistics page appears.process is in sleep mode • T .process has a negative nice value Time Cpu Command The amount of time (in hours:minutes:seconds) that the process has been running The percentage of CPU that the process is using The executable name of the process Size Res State To expand the process list: Access: Maint/Admin 1.Monitoring the System Viewing System Process Status Chapter 14 The Process Status table describes each column that appears in the process list.process is defunct • < .1 Sourcefire 3D System Administrator Guide 469 .process is dead • Z .

the current system uptime. indicating a higher priority) Nice values indicate the scheduled priority for system processes and can range between -20 (highest priority) and 19 (lowest priority). and swap information. The process list expands.9.1 Sourcefire 3D System Administrator Guide 470 . CPU.Monitoring the System Viewing System Process Status Chapter 14 2. Cpu(s) lists the following CPU usage information: • • • user process usage percentage system process usage percentage nice usage percentage (CPU usage of processes that have a negative nice value. the system load average. memory. On the Defense Center. Click the down arrow next to Processes. listing general process status that includes the number and types of running tasks. • • • • • • • • • idle usage percentage total number of kilobytes in memory total number of used kilobytes in memory total number of free kilobytes in memory total number of buffered kilobytes in memory total number of kilobytes in swap total number of used kilobytes in swap total number of free kilobytes in swap total number of cached kilobytes in swap Mem lists the following memory usage information: Swap lists the following swap usage information: IMPORTANT! For more information about the types of processes that run on the appliance. see Understanding Running Processes on page 471. 3. select the device or devices you want to view process statistics for and click Select Devices. Version 4. the current time. and specific information about each running process.

Monitoring the System Understanding Running Processes Chapter 14 To collapse the process list: Access: Maint/Admin Click the up arrow next to Processes.1 Sourcefire 3D System Administrator Guide 471 .9. and checks for working SSL and valid certificate authentication. The System Daemons table lists daemons that you may see on the Process Status page and provides a brief description of their functionality. They ensure that services are available and spawn processes when required. Daemons always run. runs in the background to provide secure web access to the appliance Manages Linux kernel event notification messages Manages the interception and logging of Linux kernel messages Manages Linux kernel swap memory keventd klogd kswapd Version 4. This table is not an exhaustive list of all processes that may run on an appliance. See the following sections for more information: • • Understanding System Daemons on page 471 Understanding Executables and System Utilities on page 473 Understanding System Daemons Daemons continually run on an appliance. The process list collapses. and executable files are run when required. Understanding Running Processes There are two different types of processes that run on an appliance: daemons and executable files. System Daemons Daemon crond dhclient fpcollect httpd httpsd Description Manages the execution of scheduled commands (cron jobs) Manages dynamic host IP addressing Manages the collection of client and server fingerprints Manages the HTTP (Apache web server) process Manages the HTTPS (Apache web server with SSL) service.

Currently used only by health monitoring to send health events and alerts from a 3D Sensor to a Defense Center or. in a high availability environment. restarts any process that fails unexpectedly Manages reports Manages RNA reports Manages safe mode operation of the database.Monitoring the System Understanding Running Processes Chapter 14 System Daemons (Continued) Daemon kupdated mysqld ntpd pm reportd rnareportd safe_mysqld SFDataCorrelator sfestreamer (Defense Center only) sfmgr sfreactd SFRemediateD (Defense Center only . which performs disk synchronization Manages Sourcefire 3D System database processes Manages the Network Time Protocol (NTP) process Manages all Sourcefire processes.1 Sourcefire 3D System Administrator Guide 472 . sfmb) to handle the request sftroughd Version 4. starts required processes. between Defense Centers Listens for connections on incoming sockets and then invokes the correct executable (typically the Sourcefire message broker. restarts the database daemon if an error occurs and logs runtime information to a file Manages data transmission Manages connections to third-party client applications that use the Event Streamer Provides the RPC service for remotely managing and configuring an appliance using an sftunnel connection to the appliance Manages Check Point OPSEC integration.requires RNA) sftimeserviced (Defense Center only) sfmbservice (requires IPS) Description Manages the Linux kernel update process. using an sftunnel connection to the appliance.9. only seen if Checkpoint SAM support is enabled Manages remediation responses Forwards time synchronization messages to managed sensors Provides access to the sfmb message broker process running on a remote appliance.

1 Sourcefire 3D System Administrator Guide 473 .Monitoring the System Understanding Running Processes Chapter 14 System Daemons (Continued) Daemon sftunnel sshd syslogd Description Provides the secure communication channel for all processes requiring communication with a remote appliance Manages the Secure Shell (SSH) process. The System Executables and Utilities table describes the executables that you may see on the Process Status page. supports extended set of regular expressions not supported in standard grep Version 4. and the network map Utility that copies files Utility that lists the amount of free space on the appliance Utility that writes content to standard output Utility that searches files and folders for specified input. System Executables and Utilities Executable awk bash cat chown chsh correlator (Defense Center only requires RNA) cp df echo egrep Description Utility that executes programs written in the awk programming language GNU Bourne-Again SHell Utility that reads files and writes content to standard output Utility that changes user and group file permissions Utility that changes the default login shell Analyzes binary files created by RNA to generate events. runs in the background to provide SSH access to the appliance Manages the system logging (syslog) process Understanding Executables and System Utilities There are a number of executables on the system that run when executed by other processes or through user action. flow data.9.

9. multiple instances may appear Indicates authentication certificate creation Indicates a perl process iptables-restore iptables-save kill killall ksh logger md5sum mv myisamchk mysql openssl perl Version 4.Monitoring the System Understanding Running Processes Chapter 14 System Executables and Utilities (Continued) Executable find grep halt httpsdctl hwclock ifconfig iptables Description Utility that recursively searches directories for specified input Utility that searches files and directories for specified input Utility that stops the server Handles secure Apache Web processes Utility that allows access to the hardware clock Indicates the network configuration executable.1 Sourcefire 3D System Administrator Guide 474 . Handles iptables file restoration Handles saved changes to the iptables Utility that can be used to end a session and process Utility that can be used to end all sessions and processes Public domain version of the Korn shell Utility that provides a way to access the syslog daemon from the command line Utility that prints checksums and block counts for specified files Utility that moves (renames) files Indicates database table checking and repairing Indicates a database process. See Configuring the Access List for Your Appliance on page 325 for more information about access configuration. Ensures that the MAC address stays constant Handles access restriction based on changes made to the Access Configuration page.

heartbeat used to maintain contact between a sensor and Defense Center Indicates a message broker process.Monitoring the System Understanding Running Processes Chapter 14 System Executables and Utilities (Continued) Executable ps RNA (requires RNA) Description Utility that writes process information to standard output Captures packets. which allows users other than root to run executables Utility that displays information about the top CPU processes Utility that can be used to change the access and modification times of specified files sed sfheartbeat sfmb sfsnort (requires IPS) sh shutdown sleep smtpclient snmptrap ssh sudo top touch Version 4.1 Sourcefire 3D System Administrator Guide 475 . indicating that the appliance is active. then generates binary files that the Data Correlator processes to generate the network map and to populate the database with events and flow data Utility used to edit one or more text files Identifies a heartbeat broadcast. handles communication between Defense Centers and sensor.9. correlating acquired data with the RNA fingerprint database. decodes and performs session reassembly. Indicates that Snort is running Public domain version of the Korn shell Utility that shuts down the appliance Utility that suspends a process for a specified number of seconds Mail client that handles email transmission when email event notification functionality is enabled Forwards SNMP trap data to the SNMP trap server specified when SNMP notification functionality is enabled Indicates a Secure Shell (SSH) connection to the appliance Indicates a sudo process.

Version 4. See the following sections for more information: • • Generating IPS Performance Statistics Graphs on page 476 Saving IPS Performance Statistics Graphs on page 478 Generating IPS Performance Statistics Graphs Requires: IPS or DC/MDC + IPS You can generate graphs that depict performance statistics for a Defense Center or a 3D Sensor with IPS based on the number of events per second. megabits per second. last week.Monitoring the System Viewing IPS Performance Statistics Chapter 14 System Executables and Utilities (Continued) Executable vim wc Description Utility used to edit text files Utility that performs line.1 Sourcefire 3D System Administrator Guide 476 . IPS performance statistics refer only to the data stored locally on the 3D Sensor. The Defense Center version of the page is shown below. average number of bytes per packet. and the percent of packets uninspected by Snort. To view the IPS performance statistics: Access: Maint/Admin Select Operations > Monitoring > Performance > IPS. The IPS page appears. last day. IMPORTANT! Because of the way traffic is processed on 3Dx800 sensors. These graphs can show statistics for the last hour. number of megabits per second. performance statistics for those sensors are under reported. Graphs can be generated to reflect number of intrusion events per second. word. and byte counts on specified files Viewing IPS Performance Statistics Requires: IPS or DC/MDC + IPS The IPS performance statistics page allows you to generate graphs that depict performance statistics for IPS over a specific period of time.9. or last month of operation. or average bytes per packet.

if you reload a graph quickly. IPS Performance Statistics Graph Types Graph Type Events/Sec Mbits/Sec Avg Bytes/Packet Percent Packets Dropped Output Displays a graph that represents the number of events that are generated on the sensor per second Displays a graph that represents the number of megabits of traffic that pass through the sensor per second Displays a graph that represents the average number of bytes included in each packet This graph depicts the average percentage of uninspected packets across all detection resources (instances of Snort) assigned to the selected detection engine. The IPS Performance Statistics Graph Types table lists the available graph types.1 Sourcefire 3D System Administrator Guide 477 .9. Select Operations > Monitoring > Performance > IPS. then an average of 50% may indicate that one segment has a 90% drop rate and the other has a 10% drop rate. It may also indicate that both segments have a drop rate of 50%. The Defense Center version of the page is shown below. the data may not change until the next five-minute increment occurs. From the Select Graph(s) list. The graph only represents the total % drop when there is a single detection resource assigned to a selected detection engine. Therefore. 2. To generate IPS performance statistics graphs: Access: Maint/Admin 1. The IPS page appears. Version 4. From the Select Device list. If you assign two detection resources to a detection engine that has two interface sets and each interface set is connected to a different network segment.Monitoring the System Viewing IPS Performance Statistics Chapter 14 New data is accumulated for statistics graphs every five minutes. 3. select the type of graph you want to create. select the detection engines whose data you want to view.

You can choose from last hour. Graphs can be generated to display: • • • • the number of events generated by the Data Correlator per second the number of megabits analyzed by the RNA process per second average number of bytes included in each packet analyzed by the RNA process the percentage of packets dropped by RNA Version 4. To save the graph: Access: Maint/Admin Right-click on the graph and follow the instructions for your browser to save the image. displaying the information you specified. or last month. last week. Viewing RNA Performance Statistics Requires: DC + RNA The RNA Performance page allows you to generate graphs that display RNA-related performance statistics over a specific period of time.Monitoring the System Viewing RNA Performance Statistics Chapter 14 4. you can save the graph as a graphic file for later use.9. Saving IPS Performance Statistics Graphs Requires: IPS or DC/MDC + IPS After you have generated an IPS performance statistics graph.1 Sourcefire 3D System Administrator Guide 478 . 5. The graph appears. From the Select Time Range list. select the time range you would like to use for the graph. Click Graph. last day.

Therefore. last day. The RNA Performance Statistics Graph Types table lists the available graph types. The RNA page appears. last week. in thousands. or last month of operation. if you reload a graph quickly. New data is accumulated for statistics graphs every five minutes.9. To access the RNA Performance page: Access: Maint/Admin Select Operations > Monitoring > Performance > RNA. the data may not change until the next five-minute increment occurs.Monitoring the System Viewing RNA Performance Statistics Chapter 14 • • the number of packets. See the following sections for more information: • • Generating RNA Performance Statistics Graphs on page 479 Saving RNA Performance Statistics Graphs on page 481 Generating RNA Performance Statistics Graphs Requires: DC + RNA You can generate graphs that display performance statistics for managed 3D Sensors with RNA. analyzed by the RNA process per second the number of established connections analyzed by the RNA process per second These graphs can show statistics for the last hour. RNA Performance Statistics Graph Types Graph Type Processed Events/Sec Output Displays a graph that represents the number of events that the Data Correlator processes per second Displays a graph that represents the number of flows that the Data Correlator processes per second Displays a graph that represents the number of events that RNA generates per second Processed Flows/Sec Generated Events/Sec Version 4.1 Sourcefire 3D System Administrator Guide 479 .

or the detection engines that you want to include. 4. Depending on whether you select a detection engine or a sensor.9. TIP! You can select multiple graphs by holding down the Ctrl or Shift keys while clicking on the graph type. the managed 3D Sensors. Select Operations > Monitoring > Performance > RNA. select the time range you would like to use for the graph. From the Select Time Range list.Monitoring the System Viewing RNA Performance Statistics Chapter 14 RNA Performance Statistics Graph Types (Continued) Graph Type Mbits/Sec Output Displays a graph that represents the number of megabits of traffic that are analyzed by the RNA process per second Displays a graph that represents the average number of bytes included in each packet analyzed by the RNA process Displays a graph that represents the percentage of packets dropped by RNA Displays a graph that represents the number of packets analyzed by the RNA process per second. select the type of graph you want to create. last day. 2.1 Sourcefire 3D System Administrator Guide 480 . From the Select Graph(s) list. in thousands Displays a graph that represents the number of established connections observed by the RNA process per second Avg Bytes/Packet Percent Packets Dropped K Packets/Sec Syn/Ack/Sec To generate RNA performance statistics graphs: Access: Maint/Admin 1. or last month. From the Select Target list. Version 4. last week. the Select Graph(s) list adjusts to display the available graphs. select the Defense Center. You can choose from last hour. The RNA page appears. 3.

Right-click on the graph and follow the instructions for your browser to save the image. each graph appears on the page. Saving RNA Performance Statistics Graphs Requires: DC + RNA After you have generated an RNA performance statistics graph. If you selected multiple graphs.9. Click Graph. Create an RNA performance statistic graph as described in Generating RNA Performance Statistics Graphs on page 479. Version 4. 2.Monitoring the System Viewing RNA Performance Statistics Chapter 14 5. displaying the information you specified. To save the graph: Access: Maint/Admin 1. The graph appears. you can save the graph as a graphic file for later use.1 Sourcefire 3D System Administrator Guide 481 .

you can also configure email. SNMP or syslog alerting in response to health events. These event views allow you to search and view event data and to access other information that may be related to the events you are investigating. you can view health status information for the entire system or for a particular appliance.1 Sourcefire 3D System Administrator Guide 482 . Optionally. or use one of the default health policies. Fully customizable event views allow you to quickly and easily analyze the health status events gathered by the health monitor. You can also import a health policy exported from another Defense Center. and apply the health policy to one or more appliances. At the Defense Center. You can also run all tests or a specific test on demand. You can create one health policy for every appliance in your system. See the following sections for more information: • • Understanding Health Monitoring on page 483 Configuring Health Policies on page 489 Version 4.9. The tests. referred to as health modules. You can also suppress messages from selected appliances by blacklisting them. . are scripts that test for criteria you specify. You can also generate troubleshooting files for an appliance if you are asked to do so by Support. and you can delete health policies that you no longer need.Using Health Monitoring Chapter 15 Administrator Guide The health monitor provides numerous tests for determining the health of an appliance from the Defense Center. customize a health policy for the specific appliance where you plan to apply it. The health monitor collects health events based on the test conditions configured. The tests in a health policy run automatically at the interval you configure. You can modify a health policy by enabling or disabling tests or by changing test settings. referred to as a health policy. You can use the health monitor to create a collection of tests.

Monitor the health of your entire Sourcefire 3D System through the Defense Center by applying health policies to each of the managed appliances and collecting the resulting health data at the Defense Center. You can use the health monitor to access health status information for the entire system or for a particular appliance. You can set alerting thresholds to minimize the number of repeating alerts you receive. You can then create a health alert that triggers that email alert whenever CPU. if you want to see all the occurrences of CPU usage with a certain percentage. You can also configure email. A health alert is an association between a standard alert and a health status level. You can also view health events in the standard Sourcefire 3D System table view.9. events. so you can check status at a glance. disk.1 Sourcefire 3D System Administrator Guide 483 . The Health Monitor page provides a visual summary of the status of all appliances on your system. or you can retrieve all the health events for that appliance. you can set up an email alert.Using Health Monitoring Understanding Health Monitoring Chapter 15 • • Using the Health Monitor Blacklist on page 534 Configuring Health Monitor Alerts on page 539 Understanding Health Monitoring You can use the health monitor to check the status of critical functionality across your Sourcefire 3D System deployment. you can search for the CPU usage module and enter the percentage value. SNMP or syslog alerting in response to health . For example. you can open a table view of occurrences of a specific event. or memory usage reaches the Warning level you configure in the health policy applied to that appliance. For example. if you need to make sure an appliance never fails due to hardware overload. then drill down into status details if needed. Individual appliance health monitors let you drill down into health details for a specific appliance. Version 4. You can also search for specific health events. From an individual appliance’s health monitor. Pie charts and status tables on the Health Monitor page visually represent the health status for monitored appliances.

You can also apply one of the five default health policies to each appliance. the Data Correlator process. If you want to monitor the health of a managed appliance.1 Sourcefire 3D System Administrator Guide 484 . see Predefined Health Policies on page 490. Version 4.Using Health Monitoring Understanding Health Monitoring Chapter 15 Because health monitoring is an administrative activity. you can create a policy that monitors just the intrusion event rate and the IPS process. disk. see Applying Health Policies on page 528. which also monitors CPU. see Creating Health Policies on page 497. For more information on creating customized health policies. see Modifying User Privileges and Options on page 306. or you can apply the default policy. For more information on assigning user privileges. For more information on health policies and the health modules you can run to test system health. and memory usage. The health monitor tracks a variety of health indicators to ensure that your Sourcefire 3D System hardware and software are working correctly.9. see the following topics: • • • Understanding Health Policies on page 484 Understanding Health Modules on page 485 Understanding Health Monitoring Configuration on page 489 Understanding Health Policies A health policy is a collection of health module settings you apply to an appliance to define the criteria that the Defense Center uses when checking the health of the appliance. IMPORTANT! Except for the Defense Center. For example. you have to apply a health policy to that appliance. Sourcefire 3D System appliances do not have health monitoring policies applied to them by default. When you create health policies. For more information on available default health policies you can apply to an appliance. For details on applying policies. you choose which tests to run to determine appliance health. only users with Admin access privileges can access system health data. to monitor the health of a 3D Sensor with IPS. and traffic status.

The alert level also lowers by one level (for example. the alert level resets to Normal. also sometimes referred to as health tests. the module resets the counter to zero. The available health modules are described in the Health Modules table. This module only runs on 3Dx800 sensors. This module determines if the Data Correlator process (SFDataCorrelator) is restarting too often. regardless of the limits set for the module. which may indicate a problem with the process. the module only increments the restart counter by one each time it checks. the module adds one to the restart count. The module checks if any restarts occurred during the period between tests. This module checks for network cards which have restarted due to hardware failure and alerts when a reset occurs. This module determines if the CPU on the sensor is overheated and alerts when the temperature exceeds temperatures configured for the module. The first time the module checks and no restarts have occurred since the last test. the module sets status according to the restart counter value and the configured limits for the module. but sets the module status to Critical for that test. Even if multiple restarts occur between tests. The second time the module checks and no restarts have occurred since the last test. The status remains Critical until the module finds that the process is running.9. This module checks that the CPU on the appliance is not overloaded and alerts when CPU usage exceeds the percentages configured for the module. Critical is reduced to Warning or Warning is reduced to Normal). it increments the restart counter by one. This module determines if a detection engine has been bypassed because it did not respond within the number of seconds set in the bypass threshold. are scripts that test for the criteria you specify in a health policy. For more information on system daemons such as SFDataCorrelator. The restart counter does not count actual restarts. and alerts when a bypass occurs. CPU Usage Card Reset Data Correlator Process Version 4. Health Modules Module Appliance Heartbeat Automatic Application Bypass Status CPU Temperature Description This module determines if an appliance heartbeat is being heard from the sensor and alerts based on the sensor heartbeat status.Using Health Monitoring Understanding Health Monitoring Chapter 15 Understanding Health Modules Health modules. and alerts when the number of restarts exceeds limits configured for the module. If any restarts occur. If the module finds that the process is not running at all.1 Sourcefire 3D System Administrator Guide 485 . At that point. see Understanding System Daemons on page 471.

Fan Alarm Hardware Alarms This module determines if fans need to be replaced on the sensor and alerts based on the fan status. regardless of the limits set for the module. The alert level also lowers by one level (for example. the module only increments the restart counter by one each time it checks.9. If any restarts occur. The status remains Critical until the module finds that the process is running. The second time the module checks and no restarts have occurred since the last test. This module determines if hardware needs to be replaced on a 3Dx800 or 3D9900 sensor and alerts based on the hardware status. If the module finds that the process is not running at all. Disk Usage This module compares disk usage on the appliance to the limits configured for the module and alerts when usage exceeds the percentages configured for the module.Using Health Monitoring Understanding Health Monitoring Chapter 15 Health Modules (Continued) Module Defense Center Status Description This module ensures that there are heartbeats from connected Defense Centers and alerts based on the Defense Center status. see Interpreting Hardware Alert Details for 3D9900 Sensors on page 560. Critical is reduced to Warning or Warning is reduced to Normal).1 Sourcefire 3D System Administrator Guide 486 . Event Stream Status This module compares the number of events per second to the limits configured for this module and alerts if the limits are exceeded. This module determines if the eStreamer process is restarting too often. This module only runs on 3Dx800 sensors and 3D9900 sensors. and alerts when the number of restarts exceeds limits configured for the module. The module checks if any restarts occurred during the period between tests. This module only runs on 3Dx800 sensors. it increments the restart counter by one. the module adds one to the restart count. the eStreamer process may be down or the Defense Center may not be sending events. This module only runs on Master Defense Centers. Even if multiple restarts occur between tests. but sets the module status to Critical for that test. On the 3D9900. This module only runs on Defense Centers. the module sets status according to the restart counter value and the configured limits for the module. the module resets the counter to zero. If the Event Stream is zero. eStreamer Process Version 4. This module only runs on Master Defense Centers. which may indicate a problem with the process. At that point. the alert level resets to Normal. the module also reports on the status of hardware-related daemons. For more information on the details reported for 3D9900 sensors. The first time the module checks and no restarts have occurred since the last test. The restart counter does not count actual restarts.

Using Health Monitoring Understanding Health Monitoring

Chapter 15

Health Modules (Continued) Module Health Monitor Process Description This module monitors the status of the health monitor itself and alerts if the number of minutes since the last health event received by the Defense Center exceeds the Warning or Critical limits. This module only runs on Defense Centers. IPS Event Rate This module compares the number of intrusion events per second to the limits configured for this module and alerts if the limits are exceeded. If the IPS Event Rate is zero, the IPS process may be down or the 3D Sensor may not be sending events. Select Analysis & Reporting > Event Summary > Intrusion Event Statistics to check if events are being received from the sensor. This module determines if the IPS process (snort) has been restarting too often, which may indicate a problem with the process, and alerts when the number of restarts exceeds the limits configured for the module. The IPS process (also known as snort) is the packet decoder on a 3D Sensor with that is licensed for IPS component. If the IPS process is down or has been restarting, the IPS Event Rate results may be inaccurate. The restart counter does not indicate the number of restarts. Instead, the module checks if any restarts occurred during the period between tests. Even if multiple restarts occur between tests, the module only increments the restart counter by one each time it checks. If any restarts occur, the module adds one to the restart count. The first time the module checks and no restarts have occurred since the last test, the module resets the counter to zero. The alert level also lowers by one level (for example, Critical is reduced to Warning or Warning is reduced to Normal). The second time the module checks and no restarts have occurred since the last test, the alert level resets to Normal. If the module finds that the process is not running at all, it increments the restart counter by one, but sets the module status to Critical for that test, regardless of the limits set for the module. The status remains Critical until the module finds that the process is running. At that point, the module sets status according to the restart counter value and the configured limits for the module. Link State Propagation MDC Event Service Memory Usage This module determines when a link in a paired inline interface set fails and triggers the link state propagation mode. This module monitors the health of the internal eStreamer process used to transmit events to the Master Defense Center from the Defense Center. This module compares memory usage on the appliance to the limits configured for the module and alerts when usage exceeds the levels configured for the module. This module monitors the application of PEP rules to interface sets on a 3D9900. If PEP rules cannot be applied to interfaces in an interface set, the module generates an alert.

IPS Process

PEP Status

Version 4.9.1

Sourcefire 3D System Administrator Guide

487

Using Health Monitoring Understanding Health Monitoring

Chapter 15

Health Modules (Continued) Module Power Supply Description This module determines if power supplies on the sensor require replacement and alerts based on the power supply status. This module only runs on the Series 2 DC3000, MDC3000, 3Dx800, 3D9900, 3D3500, 3D4500, and 3D6500 appliances. This module indicates whether a specified period of time has passed since any RNA events have been detected by a sensor. This module determines if sufficient RNA host licenses remain and alerts based on the warning level configured for the module. This module determines if the RNA process (rna) is restarting too often, which may indicate a problem with the process, and alerts based on the number of restarts configured for the module. The restart counter does not count actual restarts. The module checks if any restarts occurred during the period between tests. Even if multiple restarts occur between tests, the module only increments the restart counter by one each time it checks. If any restarts occur, the module adds one to the restart count. The first time the module checks and no restarts have occurred since the last test, the module resets the counter to zero. The alert level also lowers by one level (for example, Critical is reduced to Warning or Warning is reduced to Normal). The second time the module checks and no restarts have occurred since the last test, the alert level resets to Normal. If the module finds that the process is not running at all, it increments the restart counter by one, but sets the module status to Critical for that test, regardless of the limits set for the module. The status remains Critical until the module finds that the process is running. At that point, the module sets status according to the restart counter value and the configured limits for the module. Time Synchronization Status Traffic Status This module tracks the synchronization of a sensor clock that obtains time using NTP with the clock on the NTP server and alerts if the difference in the clocks is more than ten seconds. This module determines if the sensor currently collects traffic and alerts based on the traffic status.

RNA Event Status RNA Host License Limit RNA Process

Version 4.9.1

Sourcefire 3D System Administrator Guide

488

Using Health Monitoring Configuring Health Policies

Chapter 15

Understanding Health Monitoring Configuration
There are several steps to setting up health monitoring on your Sourcefire 3D System, as indicated in the following procedure: 1. Create health policies for your appliances. You can set up specific policies for each kind of appliance you have in your Sourcefire 3D System, enabling only the appropriate tests for that appliance. TIP! If you want to quickly enable health monitoring without customizing the monitoring behavior, you can apply one of the default policies provided for that purpose. For more information on setting up health policies, see Configuring Health Policies on page 489. 2. Apply a health policy to each appliance where you want to track health status. For information on the default health policies available for immediate application, see Predefined Health Policies on page 490. 3. Optionally, configure health monitor alerts. You can set up email, syslog, or SNMP alerts that trigger when the health status level reaches a particular severity level for specific health modules. For more information on setting up health monitor alerts, see Configuring Health Monitor Alerts on page 539. After you set up health monitoring on your system, you can view the health status at any time on the Health Monitor page or the Health Table Events View. For more information about viewing system health data, see the following topics: • • • Using the Health Monitor on page 545 Using Appliance Health Monitors on page 547 Working with Health Events on page 555

Configuring Health Policies
A health policy contains configured health test criteria for several modules. You can control which health modules run against each of your appliances and configure the specific limits used in the tests run by each module. For more information on the health modules you can configure in a health policy, see Understanding Health Monitoring on page 483. You can create one health policy that can be applied to every appliance in your system, customize each health policy to the specific appliance where you plan to apply it, or use the default health policies provided for you. You can also import a health policy exported from another Defense Center.

Version 4.9.1

Sourcefire 3D System Administrator Guide

489

Using Health Monitoring Configuring Health Policies

Chapter 15

When you configure a health policy, you decide whether to enable each health module for that policy. You also select the criteria that control which health status each enabled module reports each time it assesses the health of a process. For more information on the default health policy, which is applied to the Defense Center and Master Defense Center automatically, see Default Health Policy on page 493. For more information, see the following topics: • • • • • Predefined Health Policies on page 490 Creating Health Policies on page 497 Applying Health Policies on page 528 Editing Health Policies on page 530 Deleting Health Policies on page 533

Predefined Health Policies
The Defense Center health monitor includes several default health policies to make it easier for you to quickly implement health monitoring for your appliances. The Default Health Policy is automatically applied to the Defense Center. To also monitor sensor health, you can push health policies to 3D Sensors. IMPORTANT! You cannot apply a health policy to RNA Software for Red Hat Linux or Crossbeam-based software sensors. For more information, see the following topics: • • • • • • • Default 3D Sensor Health Policy on page 491 Default 3Dx800 Health Policy on page 491 Suggested 3D9900 Health Policy on page 492 Default Health Policy on page 493 Default Intrusion Sensor Health Policy on page 495 Default IPS (3Dx800 only) Health Policy on page 495 Default RNA Sensor Health Policy on page 496

Version 4.9.1

Sourcefire 3D System Administrator Guide

490

Using Health Monitoring Configuring Health Policies

Chapter 15

Default 3D Sensor Health Policy
Use the Default 3D Sensor Health Policy to monitor health on any 3D Sensor. Enabled health modules for this policy are listed in the Enabled Health Modules: 3D Sensor Health Policy table. Enabled Health Modules: 3D Sensor Health Policy Module Automatic Application Bypass Status Data Correlator Process Disk Usage IPS Event Rate IPS Process Link State Propagation Memory Usage Power Supply RNA Process Traffic Status For more information, see... Configuring Automatic Application Bypass Monitoring on page 502 Configuring Data Correlator Process Monitoring on page 506 Configuring Disk Usage Monitoring on page 508 Configuring IPS Event Rate Monitoring on page 515 Configuring IPS Process Monitoring on page 516 Configuring Link State Propagation Monitoring on page 518 Configuring Memory Usage Monitoring on page 520 Configuring Power Supply Monitoring on page 522 Configuring RNA Process Monitoring on page 525 Configuring Traffic Status Monitoring on page 527

Default 3Dx800 Health Policy
Use the Default 3Dx800 Health Policy to monitor health on 3Dx800 sensors. Enabled health modules for this policy are listed in the Enabled Health Modules: Default 3Dx800 Health Policy table. Note that the Hardware Alarm module should

Version 4.9.1

Sourcefire 3D System Administrator Guide

491

Using Health Monitoring Configuring Health Policies

Chapter 15

be used instead of the Power Supply module to monitor power supply health on the 3Dx800 sensor models. Enabled Health Modules: Default 3Dx800 Health Policy Module Automatic Application Bypass Status CPU Temperature Disk Usage Fan Alarm Hardware Alarms IPS Event Rate IPS Process Memory Usage RNA Process Traffic Status For more information, see... Configuring Automatic Application Bypass Monitoring on page 502 Configuring CPU Temperature Monitoring on page 503 Configuring Disk Usage Monitoring on page 508 Configuring Fan Monitoring on page 512 Configuring Hardware Monitoring on page 513 Configuring IPS Event Rate Monitoring on page 515 Configuring IPS Process Monitoring on page 516 Configuring Memory Usage Monitoring on page 520 Configuring RNA Process Monitoring on page 525 Configuring Traffic Status Monitoring on page 527

Suggested 3D9900 Health Policy
The Defense Center interface does not include a default health policy specifically for 3D9900 sensors. Sourcefire recommends that you start with the default 3D Sensor policy and enable the Hardware Alarms module. If the sensor will be running RNA, enable the RNA Process module as well. Health modules that should be enabled when creating a policy for this type of sensor are listed in the Suggested Health Modules: 3D9900 Health Policy table. Note that the CPU Usage module cannot be enabled when monitoring 3D9900

Version 4.9.1

Sourcefire 3D System Administrator Guide

492

Using Health Monitoring Configuring Health Policies

Chapter 15

sensor models. CPU usage for a 3D9900 may reach 100% during normal sensor operation, so the data provided by the module would generate misleading events. Suggested Health Modules: 3D9900 Health Policy Module Data Correlator Process Disk Usage Hardware Alarms IPS Event Rate IPS Process Link State Propagation Memory Usage PEP Status Power Supply RNA Process Traffic Status For more information, see... Configuring Data Correlator Process Monitoring on page 506 Configuring Disk Usage Monitoring on page 508 Configuring Hardware Monitoring on page 513 Configuring IPS Event Rate Monitoring on page 515 Configuring IPS Process Monitoring on page 516 Configuring Link State Propagation Monitoring on page 518 Configuring Memory Usage Monitoring on page 520 Configuring PEP Status Monitoring on page 521 Configuring Power Supply Monitoring on page 522 Configuring RNA Process Monitoring on page 525 Configuring Traffic Status Monitoring on page 527

Default Health Policy
Use the Default Health Policy to monitor health on a Defense Center. Enabled health modules for this policy are listed in the Enabled Defense Center Health Modules - Default Health Policy table. Enabled Defense Center Health Modules - Default Health Policy Module Automatic Application Bypass Status Appliance Heartbeat For more information, see... Configuring Automatic Application Bypass Monitoring on page 502 Configuring Appliance Heartbeat Monitoring on page 501

Version 4.9.1

Sourcefire 3D System Administrator Guide

493

Using Health Monitoring Configuring Health Policies

Chapter 15

Enabled Defense Center Health Modules - Default Health Policy (Continued) Module Data Correlator Process Disk Usage Link State Propagation Memory Usage Time Synchronization Status Power Supply RNA Host License Limit For more information, see... Configuring Data Correlator Process Monitoring on page 506 Configuring Disk Usage Monitoring on page 508 Configuring Link State Propagation Monitoring on page 518 Configuring Memory Usage Monitoring on page 520 Configuring Time Synchronization Monitoring on page 526 Configuring Power Supply Monitoring on page 522 Configuring RNA Host Usage Monitoring on page 524

Use the Default Health Policy to monitor health on a Master Defense Center. Enabled health modules for this policy are listed in the Enabled MDC Health Modules - Default Health Policy table. Enabled MDC Health Modules - Default Health Policy Module Data Correlator Process Defense Center Status Disk Usage eStreamer Process Event Stream Memory Usage RNA Host License Limit For more information, see... Configuring Data Correlator Process Monitoring on page 506 Configuring Defense Center Status on page 507 Configuring Disk Usage Monitoring on page 508 Configuring eStreamer Process Monitoring on page 509 Configuring Event Stream Monitoring on page 511 Configuring Memory Usage Monitoring on page 520 Configuring RNA Host Usage Monitoring on page 524

Version 4.9.1

Sourcefire 3D System Administrator Guide

494

Using Health Monitoring Configuring Health Policies

Chapter 15

Default Intrusion Sensor Health Policy
Use the Default IPS Health Policy to monitor health on legacy Intrusion Sensors that you have not upgraded to Version 4.9.1. Enabled health modules for this policy are listed in the Enabled Health Modules: Default Intrusion Sensor Health Policy table. Enabled Health Modules: Default Intrusion Sensor Health Policy Module Automatic Application Bypass Status Data Correlator Process Disk Usage Health Monitor Process IPS Event Rate IPS Process Link State Propagation Memory Usage Power Supply Traffic Status For more information, see... Configuring Automatic Application Bypass Monitoring on page 502 Configuring Data Correlator Process Monitoring on page 506 Configuring Disk Usage Monitoring on page 508 Configuring Health Status Monitoring on page 514 Configuring IPS Event Rate Monitoring on page 515 Configuring IPS Process Monitoring on page 516 Configuring Link State Propagation Monitoring on page 518 Configuring Memory Usage Monitoring on page 520 Configuring Power Supply Monitoring on page 522 Configuring Traffic Status Monitoring on page 527

Default IPS (3Dx800 only) Health Policy
Use the Default IPS (3Dx800 only) Health Policy to monitor IPS health on 3Dx800 sensors. Enabled health modules for this policy are listed in the Enabled Health Modules: Default IPS (3Dx800 only) Health Policy table. Note that the Hardware

Version 4.9.1

Sourcefire 3D System Administrator Guide

495

Using Health Monitoring Configuring Health Policies

Chapter 15

Alarm module should be used instead of the Power Supply module to monitor power supply health on the 3Dx800 sensor models. Enabled Health Modules: Default IPS (3Dx800 only) Health Policy Module Automatic Application Bypass Status CPU Temperature Data Correlator Process Disk Usage Fan Alarm Hardware Alarms IPS Event Rate IPS Process Memory Usage Traffic Status For more information, see... Configuring Automatic Application Bypass Monitoring on page 502 Configuring CPU Temperature Monitoring on page 503 Configuring Data Correlator Process Monitoring on page 506 Configuring Disk Usage Monitoring on page 508 Configuring Fan Monitoring on page 512 Configuring Hardware Monitoring on page 513 Configuring IPS Event Rate Monitoring on page 515 Configuring IPS Process Monitoring on page 516 Configuring Memory Usage Monitoring on page 520 Configuring Traffic Status Monitoring on page 527

Default RNA Sensor Health Policy
Use the Default RNA Sensor Health Policy to monitor health on legacy RNA Sensors that you have not upgraded to Version 4.9.1. Enabled health modules for

Version 4.9.1

Sourcefire 3D System Administrator Guide

496

Using Health Monitoring Configuring Health Policies

Chapter 15

this policy are listed in the Enabled Health Modules: Default RNA Sensor Health Policy table. Enabled Health Modules: Default RNA Sensor Health Policy Module Automatic Application Bypass Status Data Correlator Process Disk Usage Link State Propagation Memory Usage Power Supply RNA Host License Limit RNA Process Traffic Status For more information, see... Configuring Automatic Application Bypass Monitoring on page 502 Configuring Data Correlator Process Monitoring on page 506 Configuring Disk Usage Monitoring on page 508 Configuring Link State Propagation Monitoring on page 518 Configuring Memory Usage Monitoring on page 520 Configuring Power Supply Monitoring on page 522 Configuring RNA Host Usage Monitoring on page 524 Configuring RNA Process Monitoring on page 525 Configuring Traffic Status Monitoring on page 527

Creating Health Policies
Requires: DC/MDC If you want to customize a health policy to use with your appliances, you can create a new policy. The settings in the policy initially populate with the settings from the health policy you select as a basis for the new policy. You can enable or disable modules within the policy and change the alerting criteria for each module as needed. TIP! Instead of creating a new policy, you can export a health policy from another Defense Center and then import it onto your Defense Center. You can then edit the imported policy to suit your needs before you apply it. For more information, see Importing and Exporting Objects on page 583. To create a health policy: Access: Maint/Admin 1. Select Operations > Monitoring > Health. The Health Monitor page appears.

Version 4.9.1

Sourcefire 3D System Administrator Guide

497

Using Health Monitoring Configuring Health Policies

Chapter 15

2. On the toolbar, click Health Policy. The Health Policy page appears.

3. Click Create Policy to create a new policy. The Create Health Policy page appears.

4. Select the existing policy that you want to use as the basis for the new policy from the Copy Policy drop-down list. 5. Enter a name for the policy. 6. Enter a description for the policy.

Version 4.9.1

Sourcefire 3D System Administrator Guide

498

9. 8. Select Save to save the policy information. Configure settings on each module you want to use to test the health status of your appliances. The Health Policy Configuration page appears. including a list of the modules. as described in the following sections: • • • • • • • • • • • • Configuring Policy Run Time Intervals on page 500 Configuring Appliance Heartbeat Monitoring on page 501 Configuring Automatic Application Bypass Monitoring on page 502 Configuring CPU Temperature Monitoring on page 503 Configuring CPU Usage Monitoring on page 504 Configuring Card Reset Monitoring on page 505 Configuring Data Correlator Process Monitoring on page 506 Configuring Defense Center Status on page 507 Configuring Disk Usage Monitoring on page 508 Configuring eStreamer Process Monitoring on page 509 Configuring Event Stream Monitoring on page 511 Configuring Fan Monitoring on page 512 Version 4.1 Sourcefire 3D System Administrator Guide 499 .Using Health Monitoring Configuring Health Policies Chapter 15 7.

Configuring Policy Run Time Intervals Requires: DC/MDC You can control how often health tests run by modifying the Policy Run Time Interval for the health policy. On the Health Policy Configuration page. You must apply the policy to each appliance for it to take effect. The maximum run time interval you can set is 99999 minutes. Disabled modules do not produce health status feedback. For more information on applying health policies.1 Sourcefire 3D System Administrator Guide 500 . select Policy Run Time Interval. To configure a policy run time interval: Access: Maint/Admin 1.Using Health Monitoring Configuring Health Policies Chapter 15 • • • • • • • • • • • • • • Configuring Hardware Monitoring on page 513 Configuring Health Status Monitoring on page 514 Configuring IPS Event Rate Monitoring on page 515 Configuring IPS Process Monitoring on page 516 Configuring Link State Propagation Monitoring on page 518 Configuring MDC Event Service Monitoring on page 519 Configuring Memory Usage Monitoring on page 520 Configuring PEP Status Monitoring on page 521 Configuring Power Supply Monitoring on page 522 Configuring RNA Event Status Monitoring on page 523 Configuring RNA Host Usage Monitoring on page 524 Configuring RNA Process Monitoring on page 525 Configuring Time Synchronization Monitoring on page 526 Configuring Traffic Status Monitoring on page 527 IMPORTANT! Make sure you enable each module that you want to run to test the health status on each Health Policy Configuration page as you configure the settings. 9.Policy Run Time Interval page appears. The Health Policy Configuration . Version 4. Click Save to save the policy. even if the policy that contains the module has been applied to an appliance. see Applying Health Policies on page 528. WARNING! Do not set a run interval of less than five minutes.9.

Version 4. whichever comes first. You must apply the health policy to the appropriate appliances if you want your settings to take effect. select Appliance Heartbeat. as an indicator that the appliance is running and communicating properly with the Defense Center. In the Run Interval (mins) field. To return to the Health Policy page without saving any of your settings for this module. You have three options: • • • To save your changes to this module and return to the Health Policy page. 3. If you click Save Policy and Exit when you are done. The Health Policy Configuration . That status data feeds into the health monitor. If the Defense Center does not detect a heartbeat from a appliance. In the Health Policy Configuration page. click Save Policy and Exit.1 Sourcefire 3D System Administrator Guide 501 . you discard all changes. if you click Cancel. Select On for the Enabled option to enable use of the module for health status testing.9. To configure Appliance Heartbeat health module settings: Access: Maint/Admin 1. See Applying Health Policies on page 528 for more information. the status classification for this module changes to Critical. click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify.Appliance Heartbeat page appears. select the other module from the list at the left of the page.Using Health Monitoring Configuring Health Policies Chapter 15 2. Configuring Appliance Heartbeat Monitoring Requires: DC Supported Platforms: Defense Center The Defense Center receives heartbeats from its managed appliances once every two minutes or every 200 events. Use the Appliance Heartbeat health status module to track whether the Defense Center receives heartbeats from managed appliances. 2. enter the time in minutes that you want to elapse between automatic repetitions of the test. all changes you made will be saved.

For more information on automatic application bypass. Select On for the Enabled option to enable use of the module for health status testing. The Automatic Application Bypass Status page appears. select the other module from the list at the left of the page. That status data feeds into the health monitor. select Automatic Application Bypass Status. You have three options: • • • To save your changes to this module and return to the Health Policy page. To temporarily save your changes to this module and switch to another module’s settings to modify. To return to the Health Policy page without saving any of your settings for this module. In the Health Policy Configuration page. click Save Policy and Exit.1 Sourcefire 3D System Administrator Guide 502 .9.Using Health Monitoring Configuring Health Policies Chapter 15 3. all changes you made will be saved. Configuring Automatic Application Bypass Monitoring Requires: DC/MDC Supported Platforms: 3D Sensors except 3D9900 Use this module to detect when a detection engine is bypassed because it did not respond within the number of seconds configured as the bypass threshold. if you click Cancel. click Cancel. Version 4. To configure automatic application bypass monitoring status: Access: Maint/Admin 1. If you click Save Policy and Exit when you are done. this module generates an alert. see Automatic Application Bypass on page 212. You must apply the health policy to the appropriate appliances if you want your settings to take effect. If a bypass occurs. 2. you discard all changes. See Applying Health Policies on page 528 for more information.

select the other module from the list at the left of the page. the status classification for that module changes to Critical. click Save Policy and Exit. and the Critical limit must be greater than the Warning limit. Use the CPU Temperature health status module to set CPU temperature limits. all changes you made will be saved.1 Sourcefire 3D System Administrator Guide 503 . In the Health Policy Configuration page. That status data feeds into the health monitor. Version 4. You must apply the health policy to the appropriate 3D Sensor if you want your settings to take effect. WARNING! Sourcefire recommends that you do not set the Critical limit higher than 65 degrees Celsius and that you do not set the Warning limit higher than 55 degrees Celsius.Using Health Monitoring Configuring Health Policies Chapter 15 3. You have three options: • • • To save your changes to this module and return to the Health Policy page. To configure CPU temperature health module settings: Access: Maint/Admin 1. To temporarily save your changes to this module and switch to another module’s settings to modify. the Critical limit is set to 52 degrees Celsius and the Warning limit is set to 50 degrees Celsius. Configuring CPU Temperature Monitoring Requires: DC/MDC Supported Platforms: 3Dx800 The temperature of the central processing unit (CPU) on your 3Dx800 sensor provides an important barometer for the health of your sensor.9. If you click Save Policy and Exit when you are done. The maximum temperature you can set for either limit is 100 degrees Celsius. The Health Policy Configuration . Overheating a CPU can damage the processing unit. if you click Cancel. click Cancel. To return to the Health Policy page without saving any of your settings for this module. the status classification for that module changes to Warning. select CPU Temperature.CPU Temperature page appears. you discard all changes. By default. If the CPU temperature on the monitored sensor exceeds the Critical limit. See Applying Health Policies on page 528 for more information. If the CPU temperature on the monitored sensor exceeds the Warning limit.

The maximum percentage you can set for either limit is 100 percent. the status classification for that module changes to Warning. Version 4. 5. click Save Policy and Exit. Configuring CPU Usage Monitoring Requires: DC/MDC Supported Platforms: All except 3D9900 Excessive CPU usage can indicate that you need to upgrade your hardware or that there are processes that are not functioning correctly. select the other module from the list at the left of the page.1 Sourcefire 3D System Administrator Guide 504 . Select On for the Enabled option to enable use of the module for health status testing. you discard all changes. and the Critical limit must be higher than the Warning limit. If the CPU usage on the monitored appliance exceeds the Critical limit. that should trigger a warning health status. 4. You have three options: • • • To save your changes to this module and return to the Health Policy page. that should trigger a critical health status. in Celsius. the status classification for that module changes to Critical. if you click Cancel. 3. all changes you made will be saved. To return to the Health Policy page without saving any of your settings for this module. enter the number of degrees. Note that this module is not available for health policies applied to 3D9900 sensors. If you click Save Policy and Exit when you are done. enter the number of degrees. To temporarily save your changes to this module and switch to another module’s settings to modify.Using Health Monitoring Configuring Health Policies Chapter 15 2. You must apply the health policy to the appropriate sensors if you want your settings to take effect. click Cancel. In the Warning Threshold Celsius field. In the Critical Threshold Celsius field.9. If the CPU usage on the monitored appliance exceeds the Warning limit. See Applying Health Policies on page 528 for more information. That status data feeds into the health monitor. Use the CPU Usage health status module to set CPU usage limits. in Celsius.

You must apply the health policy to the appropriate appliances if you want your settings to take effect.CPU Usage page appears. click Save Policy and Exit.Using Health Monitoring Configuring Health Policies Chapter 15 To configure CPU Usage health module settings: Access: Maint/Admin 1. See Applying Health Policies on page 528 for more information. In the Warning Threshold % field. this module generates an alert. In the Health Policy Configuration page. Version 4.9. select the other module from the list at the left of the page. 4. all changes you made will be saved. select Card Reset. That status data feeds into the health monitor. To return to the Health Policy page without saving any of your settings for this module. you discard all changes. select CPU Usage.3D6500 except 3Dx800 Use the card reset monitoring health status module to track when the network card restarts because of hardware failure. The Health Policy Configuration . On the Health Policy Configuration page. 2. The Card Reset Monitoring page appears. If a reset occurs. enter the percentage of CPU usage that should trigger a warning health status. 5. Select On for the Enabled option to enable use of the module for health status testing. click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify. enter the percentage of CPU usage that should trigger a critical health status. If you click Save Policy and Exit when you are done. Configuring Card Reset Monitoring Requires: DC/MDC Supported Platforms: 3D500 .1 Sourcefire 3D System Administrator Guide 505 . if you click Cancel. 3. You have three options: • • • To save your changes to this module and return to the Health Policy page. In the Critical Threshold % field. To configure card reset monitoring: Access: Maint/Admin 1.

the status classification for that module changes to Warning. To temporarily save your changes to this module and switch to another module’s settings to modify. The status remains Critical until the module finds that the process is running. it increments the restart counter by one. The module checks if any restarts occurred during the period between tests. Use the Data Correlator Process health status module to set limits for the number of restarts that trigger a change in the health status. the module resets the counter to zero. manages data transmission. regardless of the limits set for the module. If the module checks the Data Correlator process as many times as configured in the Warning Number of restarts limit. all changes you made will be saved. You have three options: • • • To save your changes to this module and return to the Health Policy page.1 Sourcefire 3D System Administrator Guide 506 . The first time the module checks and no restarts have occurred since the last test. but sets the module status to Critical for that test. To return to the Health Policy page without saving any of your settings for this module. The restart counter does not count actual restarts.Using Health Monitoring Configuring Health Policies Chapter 15 2. See Applying Health Policies on page 528 for more information. Even if multiple restarts occur between tests. The second time the module checks and no restarts have occurred since the last test. the module only increments the restart counter by one each time it checks. and each time one or more restarts have occurred. click Save Policy and Exit. if you click Cancel. You must apply the health policy to the appropriate Defense Center if you want your settings to take effect.9. Select On for the Enabled option to enable use of the module for health status testing. Configuring Data Correlator Process Monitoring Requires: DC/MDC Supported Platforms: All The Data Correlator. If any restarts occur. the alert level resets to Normal. 3. At that point. If the module checks the Data Correlator process as many times as configured in the Critical Number of restarts limit. Version 4. you discard all changes. That status data feeds into the health monitor. click Cancel. If you click Save Policy and Exit when you are done. and each time one or more restarts have occurred. the module adds one to the restart count. select the other module from the list at the left of the page. short for the system daemon SFDataCorrelator. If the module finds that the process is not running at all. Critical is reduced to Warning or Warning is reduced to Normal). the status classification for that module changes to Critical. The alert level also lowers by one level (for example. the module sets status according to the restart counter value and the configured limits for the module.

Data Correlator Process page appears. To temporarily save your changes to this module and switch to another module’s settings to modify. Configuring Defense Center Status Requires: MDC Supported Platforms: Master Defense Center Use the Defense Center Status health status module to monitor the status of a Defense Center or Defense Centers managed by the Master Defense Center where the health policy is applied. If you click Save Policy and Exit when you are done. Select On for the Enabled option to enable use of the module for health status testing. 5. You must apply the health policy to the appropriate appliances if you want your settings to take effect. 4. if you click Cancel. To configure Data Correlator Process health module settings: Access: Maint/Admin 1. If a heartbeat is not obtained from the managed Defense Center or Defense Centers. and the Critical limit must be higher than the Warning limit.9. click Save Policy and Exit. Version 4. In the Critical Number of restarts field. select the other module from the list at the left of the page. enter the number of process restarts that should trigger a warning health status. all changes you made will be saved. you discard all changes.Using Health Monitoring Configuring Health Policies Chapter 15 The maximum number of restarts you can set for either limit is 100. See Applying Health Policies on page 528 for more information. click Cancel. You have three options: • • • To save your changes to this module and return to the Health Policy page. In the Warning Number of restarts field. The Health Policy Configuration . To return to the Health Policy page without saving any of your settings for this module. On the Health Policy Configuration page. That status data feeds into the health monitor. this module generates an alert. select Data Correlator Process. enter the number of process restarts that should trigger a critical health status.1 Sourcefire 3D System Administrator Guide 507 . 3. 2.

2. the status classification for that module changes to Warning. In the Health Policy Configuration page.Using Health Monitoring Configuring Health Policies Chapter 15 To configure Defense Center Status: Access: Maint/Admin 1. If the disk usage on the monitored appliance exceeds the Warning limit.1 Sourcefire 3D System Administrator Guide 508 . and the Critical limit must be higher than the Warning limit. To temporarily save your changes to this module and switch to another module’s settings to modify. if you click Cancel. Version 4. If you click Save Policy and Exit when you are done. The maximum percentage you can set for either limit is 100 percent. select the other module from the list at the left of the page. To return to the Health Policy page without saving any of your settings for this module. click Save Policy and Exit. click Cancel. the size of the partition is static so the module does not alert on the boot partition. select Defense Center Status. you discard all changes. Select On for the Enabled option to enable use of the module for health status testing.9. IMPORTANT! Although the disk usage module lists the /boot partition as a monitored partition. Use the Disk Usage health status module to set disk usage limits for the / and / volume partitions on the appliance. If the disk usage on the monitored appliance exceeds the Critical limit. That status data feeds into the health monitor. The health monitor can identify low disk space conditions on your appliances before the space runs out. an appliance cannot run. all changes you made will be saved. You have three options: • • • To save your changes to this module and return to the Health Policy page. You must apply the health policy to the appropriate Defense Center if you want your settings to take effect. Configuring Disk Usage Monitoring Requires: DC/MDC Supported Platforms: All Without sufficient disk space. See Applying Health Policies on page 528 for more information. the status classification for that module changes to Critical. 3. The Defense Center Status page appears.

To return to the Health Policy page without saving any of your settings for this module. the module adds one to the restart count. You must apply the health policy to the appropriate appliances if you want your settings to take effect. 2. select the other module from the list at the left of the page. Version 4. 5. short for the Sourcefire Event Streamer. On the Health Policy Configuration page. 3. You have three options: • • • To save your changes to this module and return to the Health Policy page. enter the percentage of disk usage that should trigger a warning health status. To temporarily save your changes to this module and switch to another module’s settings to modify. enter the percentage of disk usage that should trigger a critical health status. 4. select Disk Usage. In the Warning Threshold % field. If you click Save Policy and Exit when you are done. The module checks if any restarts occurred during the period between tests. click Cancel.Using Health Monitoring Configuring Health Policies Chapter 15 To configure Disk Usage health module settings: Access: Maint/Admin 1. the module only increments the restart counter by one each time it checks. The restart counter does not count actual restarts. click Save Policy and Exit.Disk Usage page appears. Even if multiple restarts occur between tests.1 Sourcefire 3D System Administrator Guide 509 .9. eStreamer. The Health Policy Configuration . you discard all changes. allows you to stream Sourcefire 3D System intrusion and network discovery data from the Sourcefire Defense Center to an eStreamer client. You can set limits for the number of restarts that trigger a change in the health status. Select On for the Enabled option to enable use of the module for health status testing. if you click Cancel. See Applying Health Policies on page 528 for more information. In the Critical Threshold % field. all changes you made will be saved. If any restarts occur. Configuring eStreamer Process Monitoring Requires: DC/MDC Supported Platforms: Defense Center Use the eStreamer Process health status module to monitor the health of the eStreamer process on the Defense Center.

regardless of the limits set for the module. In the Critical Number of restarts field. but sets the module status to Critical for that test. Critical is reduced to Warning or Warning is reduced to Normal). and each time one or more restarts have occurred. In the Warning Number of restarts field. If the module checks the eStreamer process as many times as configured in the Critical Number of restarts limit. the module resets the counter to zero. The alert level also lowers by one level (for example. and each time one or more restarts have occurred. and the Critical limit must be higher than the Warning limit. To configure eStreamer Process health module settings: Access: Maint/Admin 1. select eStreamer Process. The second time the module checks and no restarts have occurred since the last test. it increments the restart counter by one. The status remains Critical until the module finds that the process is running. Select On for the Enabled option to enable use of the module for health status testing. If the module finds that the process is not running at all. 3. 4.1 Sourcefire 3D System Administrator Guide 510 . On the Health Policy Configuration page. the module sets status according to the restart counter value and the configured limits for the module. That status data feeds into the health monitor.9. Version 4.eStreamer Process page appears. 2. The Health Policy Configuration . enter the number of process restarts that should trigger a critical health status. the status classification for that module changes to Warning. the status classification for that module changes to Critical. At that point. enter the number of process restarts that should trigger a warning health status. If the module checks the eStreamer process as many times as configured in the Warning Number of restarts limit.Using Health Monitoring Configuring Health Policies Chapter 15 The first time the module checks and no restarts have occurred since the last test. The maximum number of restarts you can set for either limit is 100. the alert level resets to Normal.

enter the maximum number of seconds to wait between events. See Applying Health Policies on page 528 for more information. That status data feeds into the health monitor. 3. the status classification for that module changes to Critical. and the Critical limit must be higher than the Warning limit. select Event Stream Status. To configure Event Stream Status health module settings: Access: Maint/Admin 1. The minimum number of seconds is 300. Select On for the Enabled option to enable use of the module for health status testing. all changes you made will be saved.Using Health Monitoring Configuring Health Policies Chapter 15 5. Configuring Event Stream Monitoring Requires: DC/MDC Supported Platforms: Master Defense Center Use the Event Stream Status module to monitor the health of the event stream process on a Defense Center by generating alerts when too many seconds elapse between events received by the Master Defense Center. If you click Save Policy and Exit when you are done. Version 4. The Health Policy Configuration . If the wait exceeds the Critical Seconds since last event limit. before triggering a critical health status. In the Critical Seconds since last event field. click Cancel. You must apply the health policy to the appropriate appliances if you want your settings to take effect. in seconds. select the other module from the list at the left of the page. If the wait exceeds the number of seconds configured in the Warning Seconds since last event limit. click Save Policy and Exit. you discard all changes. You can configure the elapsed duration between events. that causes an alert to be generated. if you click Cancel. You have three options: • • • To save your changes to this module and return to the Health Policy page. The maximum number of seconds you can set for either limit is 600. To temporarily save your changes to this module and switch to another module’s settings to modify. the status classification for that module changes to Warning.1 Sourcefire 3D System Administrator Guide 511 .9. In the Health Policy Configuration page.Event Stream Status page appears. 2. To return to the Health Policy page without saving any of your settings for this module.

1 Sourcefire 3D System Administrator Guide 512 .Using Health Monitoring Configuring Health Policies Chapter 15 4. If the Fan Alarm module finds a fan that has failed. select the other module from the list at the left of the page. To return to the Health Policy page without saving any of your settings for this module. You must apply the health policy to the Master Defense Center for your settings to take effect. enter the maximum number of seconds to wait between events. If you click Save Policy and Exit when you are done. See Applying Health Policies on page 528 for more information. before triggering a warning health status. 5. click Cancel. select Fan Alarm. the status classification for that module changes to Critical. In the Health Policy Configuration page. You have three options: • • • To save your changes to this module and return to the Health Policy page. all changes you made will be saved. In the Warning Seconds since last event field. To temporarily save your changes to this module and switch to another module’s settings to modify. if you click Cancel. 2. click Save Policy and Exit. To configure Fan Alarm health module settings: Access: Maint/Admin 1.9. Version 4. you discard all changes. The Health Policy Configuration . That status data feeds into the health monitor. Configuring Fan Monitoring Requires: DC/MDC Supported Platforms: 3Dx800 Use the Fan Alarm health status module to warn of fan failure on a 3Dx800 sensor.Fan Alarm monitor page appears. Select On for the Enabled option to enable use of the module for health status testing.

If you click Save Policy and Exit when you are done. click Save Policy and Exit. the status classification for that module changes to Critical. you discard all changes. You have three options: • • • To save your changes to this module and return to the Health Policy page.Hardware Alarm monitor page appears. For more information on the hardware status conditions that can cause hardware alerts on 3D9900 sensors. See Applying Health Policies on page 528 for more information. To return to the Health Policy page without saving any of your settings for this module. The Health Policy Configuration . see Interpreting Hardware Alert Details for 3D9900 Sensors on page 560.Using Health Monitoring Configuring Health Policies Chapter 15 3. Select On for the Enabled option to enable use of the module for health status testing. 3D9900 Use the Hardware Alarm health status module to detect hardware failure on a 3Dx800 or 3D9900 sensor. If the Hardware Alarm module finds a hardware component that has failed. To temporarily save your changes to this module and switch to another module’s settings to modify. if you click Cancel. click Cancel. all changes you made will be saved.9. select Hardware Alarms. 2. In the Health Policy Configuration page. Version 4. To configure Hardware Alarm health module settings: Access: Maint/Admin 1. That status data feeds into the health monitor. select the other module from the list at the left of the page. You must apply the health policy to the appropriate sensors if you want your settings to take effect. Configuring Hardware Monitoring Requires: DC/MDC Supported Platforms: 3Dx800. Note that the Hardware Alarm module can be used in addition to the Power Supply module to monitor power supply health on the 3Dx800 sensor models.1 Sourcefire 3D System Administrator Guide 513 .

example. in minutes. That status data feeds into the health monitor.com) monitors a sensor (dogwood. and the Critical limit must be higher than the Warning limit. Version 4. The minimum number of minutes is 5. that causes an alert to be generated. If the wait exceeds the Critical Minutes since last event limit. You must apply the health policy to the appropriate sensors if you want your settings to take effect. You have three options: • • • To save your changes to this module and return to the Health Policy page. the status classification for that module changes to Warning.1 Sourcefire 3D System Administrator Guide 514 . You can configure the elapsed duration between events. If the wait exceeds the number of minutes configured in the Warning Minutes since last event limit. Configuring Health Status Monitoring Requires: DC/MDC Supported Platforms: Defense Center Use the Health Monitor Process module to monitor the health of the health monitor on a Defense Center by generating alerts when too many minutes elapse between health events received from monitored appliances.com). click Cancel.Health Monitor Process page appears. In the Health Policy Configuration page. if a Defense Center (myrtle.Using Health Monitoring Configuring Health Policies Chapter 15 3. 3. enter the maximum number of minutes to wait between events. click Save Policy and Exit. To temporarily save your changes to this module and switch to another module’s settings to modify. select Health Monitor Process. To return to the Health Policy page without saving any of your settings for this module. If you click Save Policy and Exit when you are done. See Applying Health Policies on page 528 for more information. In the Critical Minutes since last event field.com. the status classification for that module changes to Critical. To configure Health Monitor Process module settings: Access: Maint/Admin 1. 2.example. The Health Policy Configuration . The Health Monitor Process module then reports events that indicate how many minutes have elapsed since the last event was received from dogwood.example.example. Select On for the Enabled option to enable use of the module for health status testing.com. if you click Cancel. For example. you apply a health policy with the Health Monitor Process module enabled to myrtle. before triggering a critical health status. all changes you made will be saved. you discard all changes. select the other module from the list at the left of the page. The maximum number of minutes you can set for either limit is 144.9.

If the event rate for the IPS process on the monitored sensor exceeds the number of events per second configured in the Events per second (Warning) limit. the status classification for that module changes to Warning. 5. To temporarily save your changes to this module and switch to another module’s settings to modify. If you click Save Policy and Exit when you are done. That status data feeds into the health monitor. For a network segment with this average rate. click Save Policy and Exit. Version 4.1 Sourcefire 3D System Administrator Guide 515 . click Cancel. Typically. You must apply the health policy to the Defense Center for your settings to take effect. if you click Cancel.5 Events per second (Warning) = Events/Sec *1.Using Health Monitoring Configuring Health Policies Chapter 15 4. If the event rate exceeds the number of events per second configured in the Events per second (Critical) limit. and the Critical limit must be higher than the Warning limit. select the other module from the list at the left of the page.9. before triggering a warning health status. You have three options: • • • To save your changes to this module and return to the Health Policy page. To return to the Health Policy page without saving any of your settings for this module. enter the maximum number of minutes to wait between events. the status classification for that module changes to Critical. the event rate for a network segment averages 20 events per second. Events per second (Critical) should be set to 50 and Events per second (Warning) should be set to 30. then calculate the limits using these formulas: • • Events per second (Critical) = Events/Sec * 2. To determine limits for your system. find the Events/Sec value on the Statistics page for your sensor (Operations > Monitoring > Statistics). all changes you made will be saved. In the Warning Minutes since last event field.5 The maximum number of events you can set for either limit is 999. you discard all changes. Configuring IPS Event Rate Monitoring Requires: DC/MDC Supported Platforms: IPS Use the IPS Event Rate health status module to set limits for the number of packets per second that trigger a change in the health status. See Applying Health Policies on page 528 for more information.

Using Health Monitoring Configuring Health Policies Chapter 15 To configure IPS Event Rate Monitor health module settings: Access: Maint/Admin 1. all changes you made will be saved. the module resets the counter to zero. Configuring IPS Process Monitoring Requires: DC/MDC Supported Platforms: IPS The IPS process (also known as Snort) is the packet decoder on a 3D Sensor with the IPS component.9. To temporarily save your changes to this module and switch to another module’s settings to modify. you discard all changes. the module only increments the restart counter by one each time it checks. select IPS Event Rate. In the Health Policy Configuration page. 3. if you click Cancel. You have three options: • • • To save your changes to this module and return to the Health Policy page. the module adds one to the restart count. 2. The module checks if any restarts occurred during the period between tests. If you click Save Policy and Exit when you are done. Select On for the Enabled option to enable use of the module for health status testing. In the Events per second (Warning) field. See Applying Health Policies on page 528 for more information. click Save Policy and Exit. If any restarts occur. You can configure how many restarts trigger a change in the health status for the process. 4. Even if multiple restarts occur between tests. The first time the module checks and no restarts have occurred since the last test. You must apply the health policy to the appropriate sensors if you want your settings to take effect. select the other module from the list at the left of the page.1 Sourcefire 3D System Administrator Guide 516 . The alert level also lowers by one level (for Version 4. 5. To return to the Health Policy page without saving any of your settings for this module.IPS Event Rate page appears. The Health Policy Configuration . The restart counter does not count actual restarts. enter the number of events per second that should trigger a warning health status. click Cancel. Use the IPS Process health status module to monitor the health of the IPS process on a sensor. enter the number of events per second that should trigger a critical health status. In the Events per second (Critical) field.

If the module finds that the process is not running at all. it increments the restart counter by one. The second time the module checks and no restarts have occurred since the last test. and each time one or more restarts have occurred. select IPS Process. 3. To configure IPS Process Monitor health module settings: Access: Maint/Admin 1. but sets the module status to Critical for that test. The maximum number of restarts you can set for either limit is 100. and the Critical limit must be higher than the Warning limit. Critical is reduced to Warning or Warning is reduced to Normal). In the Health Policy Configuration page. The Health Policy Configuration . If the module checks the IPS process as many times as configured in the Critical Number of restarts limit. If the module checks the IPS process as many times as configured in the Warning Number of restarts limit. the module sets status according to the restart counter value and the configured limits for the module. At that point. 2. In the Critical Number of restarts field.Using Health Monitoring Configuring Health Policies Chapter 15 example. enter the number of process restarts that should trigger a warning health status.1 Sourcefire 3D System Administrator Guide 517 . 4. and each time one or more restarts have occurred. In the Warning Number of restarts field. Select On for the Enabled option to enable use of the module for health status testing. the status classification for that module changes to Critical. the status classification for that module changes to Warning. That status data feeds into the health monitor. the alert level resets to Normal. The status remains Critical until the module finds that the process is running. regardless of the limits set for the module.IPS Process page appears.9. Version 4. enter the number of process restarts that should trigger a critical health status.

click Cancel. select the other module from the list at the left of the page. select Link State Propagation. The Health Policy Configuration . Configuring Link State Propagation Monitoring Requires: DC/MDC Supported Platforms: IPS Use the Link State Propagation health status module to detect the interface link state propagation status on an inline interface pair. You must apply the health policy to the appropriate sensors if you want your settings to take effect.1 Sourcefire 3D System Administrator Guide 518 .Using Health Monitoring Configuring Health Policies Chapter 15 5. To temporarily save your changes to this module and switch to another module’s settings to modify. all changes you made will be saved. To configure Link State Propagation health module settings: Access: Maint/Admin 1.Link State Propagation monitor page appears. On the Health Policy Configuration page. See Applying Health Policies on page 528 for more information. Version 4. Select On for the Enabled option to enable use of the module for health status testing. you discard all changes. To return to the Health Policy page without saving any of your settings for this module. click Save Policy and Exit. If a link state propagates to the paired interface.9. the status classification for that module changes to Critical and the state reads: Module Link State Propagation: ethx_ethy is Triggered where x and y are the paired interface numbers. 2. If you click Save Policy and Exit when you are done. You have three options: • • • To save your changes to this module and return to the Health Policy page. if you click Cancel.

Using Health Monitoring Configuring Health Policies

Chapter 15

3. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate sensors if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring MDC Event Service Monitoring
Requires: DC/MDC Supported Platforms: Defense Center Use the MDC health status module to monitor the health of the internal eStreamer process on the Defense Center that is used to transmit events to the Master Defense Center. You can set limits for the number of restarts that trigger a change in the health status. The restart counter does not count actual restarts. The module checks if any restarts occurred during the period between tests. Even if multiple restarts occur between tests, the module only increments the restart counter by one each time it checks. If any restarts occur, the module adds one to the restart count. The first time the module checks and no restarts have occurred since the last test, the module resets the counter to zero. The alert level also lowers by one level (for example, Critical is reduced to Warning or Warning is reduced to Normal). The second time the module checks and no restarts have occurred since the last test, the alert level resets to Normal. If the module finds that the process is not running at all, it increments the restart counter by one, but sets the module status to Critical for that test, regardless of the limits set for the module. The status remains Critical until the module finds that the process is running. At that point, the module sets status according to the restart counter value and the configured limits for the module. If the module checks the MDC event service as many times as configured in the Warning Number of restarts limit, and each time one or more restarts have occurred, the status classification for that module changes to Warning. If the module checks the MDC event service as many times as configured in the Critical Number of restarts limit, and each time one or more restarts have occurred, the status classification for that module changes to Critical. That status data feeds into the health monitor. The maximum number of restarts you can set for either limit is 100, and the Critical limit must be higher than the Warning limit.

Version 4.9.1

Sourcefire 3D System Administrator Guide

519

Using Health Monitoring Configuring Health Policies

Chapter 15

To configure MDC Event Service health module settings: Access: Maint/Admin 1. On the Health Policy Configuration page, select MDC Event Service. The Health Policy Configuration - MDC Event Service Process page appears.

2. Select On for the Enabled option to enable use of the module for health status testing. 3. In the Critical Number of restarts field, enter the number of process restarts that should trigger a critical health status. 4. In the Warning Number of restarts field, enter the number of process restarts that should trigger a warning health status. 5. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate appliances if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring Memory Usage Monitoring
Requires: DC/MDC Supported Platforms: All Use the Memory Usage health status module to set memory usage limits. The module calculates free memory by adding free memory and cached memory. If the memory usage on the monitored appliance exceeds the Warning limit, the status classification for that module changes to Warning. If the memory usage on the monitored appliance exceeds the Critical limit, the status classification for that module changes to Critical. That status data feeds into the health monitor. The maximum percentage you can set for either limit is 100 percent, and the Critical limit must be higher than the Warning limit.

Version 4.9.1

Sourcefire 3D System Administrator Guide

520

Using Health Monitoring Configuring Health Policies

Chapter 15

To configure Memory Usage health module settings: Access: Maint/Admin 1. On the Health Policy Configuration page, select Memory Usage. The Health Policy Configuration - Memory Usage page appears.

2. Select On for the Enabled option to enable use of the module for health status testing. 3. In the Critical Threshold % field, enter the percentage of memory usage that should trigger a critical health status. 4. In the Warning Threshold % field, enter the percentage of memory usage that should trigger a warning health status. 5. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate appliances if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring PEP Status Monitoring
Requires: DC/MDC Supported Platforms: 3D9900 Use the PEP Status health status module to monitor the application of PEP rules to interface sets on a 3D9900. If PEP rules cannot be applied to interfaces in an interface set, this module generates an alert. That status data feeds into the health monitor.

Version 4.9.1

Sourcefire 3D System Administrator Guide

521

Using Health Monitoring Configuring Health Policies

Chapter 15

To configure PEP Status health module settings: Access: Maint/Admin 1. In the Health Policy Configuration page, select PEP Status. The Health Policy Configuration - PEP Status monitor page appears.

2. Select On for the Enabled option to enable use of the module for health status testing. 3. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate sensors if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring Power Supply Monitoring
Requires: DC/MDC Supported Platforms: Series 2 DC3000, MDC3000, 3D9900, 3Dx800, 3D3500, 3D4500, 3D6500 Use the Power Supply health status module to detect a power supply failure on a Series 2 DC3000, MDC3000, 3Dx800, 3D9900, 3D3500, 3D4500, or 3D6500 sensor. If the Power Supply module finds a power supply that has no power, the status classification for that module changes to No Power. If the module cannot detect the presence of the power supply, the status changes to Critical Error. That status data feeds into the health monitor. You can expand the Power Supply item on the Alert Detail list in the health monitor to see specific status items for each power supply. Note that the Hardware Alarm module can be used in addition to the Power Supply module to monitor power supply health on the 3Dx800 sensor models. To configure Power Supply health module settings: Access: Maint/Admin 1. In the Health Policy Configuration page, select Power Supply. The Health Policy Configuration - Power Supply monitor page appears.

Version 4.9.1

Sourcefire 3D System Administrator Guide

522

Using Health Monitoring Configuring Health Policies

Chapter 15

2. Select On for the Enabled option to enable use of the module for health status testing. 3. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate sensors if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring RNA Event Status Monitoring
Requires: DC/MDC Supported Platforms: DC Use the RNA Event Status module to monitor the health of the RNA process on a sensor from the Defense Center by generating alerts when too many seconds elapse between RNA events received by the Defense Center. You can configure the elapsed duration between events, in seconds, that causes an alert to be generated. If the wait exceeds the number of seconds configured in the Warning Seconds since last event limit, the status classification for that module changes to Warning. If the wait exceeds the Critical Seconds since last event limit, the status classification for that module changes to Critical. That status data feeds into the health monitor. The maximum number of seconds you can set for either limit is 7200, and the Critical limit must be higher than the Warning limit. The minimum number of seconds is 3600. Note that the RNA Health module was renamed to the RNA Event Status module in 4.9.1 and that the supported platforms changed from 3D Sensor to Defense Center in 4.9.1. To configure RNA Event Status module settings: Access: Maint/Admin 1. In the Health Policy Configuration page, select RNA Event Status. The Health Policy Configuration - RNA Event Status page appears.

Version 4.9.1

Sourcefire 3D System Administrator Guide

523

Using Health Monitoring Configuring Health Policies

Chapter 15

2. Select On for the Enabled option to enable use of the module for health status testing. 3. In the Critical Seconds since last event field, enter the maximum number of seconds to wait between events, before triggering a critical health status. 4. In the Warning Seconds since last event field, enter the maximum number of seconds to wait between events, before triggering a warning health status. 5. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the Defense Center for your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring RNA Host Usage Monitoring
Requires: DC/MDC Supported Platforms: RNA Use the RNA Host License Limit health status module to set RNA Host shortage limits. If the number of remaining RNA Hosts on the monitored sensor falls below the Warning Hosts limit, the status classification for that module changes to Warning. If the number of remaining RNA Hosts on the monitored sensor falls below the Critical Hosts limit, the status classification for that module changes to Critical. That status data feeds into the health monitor. The maximum number of hosts you can set for either limit is 999, and the Critical limit must be higher than the Warning limit. To configure RNA Host License Limit health module settings: Access: Maint/Admin 1. In the Health Policy Configuration page, select RNA Host License Limit. The Health Policy Configuration - RNA Host License Limit page appears.

2. Select On for the Enabled option to enable use of the module for health status testing.

Version 4.9.1

Sourcefire 3D System Administrator Guide

524

Using Health Monitoring Configuring Health Policies

Chapter 15

3. In the Critical number Hosts field, enter the remaining number of available hosts that should trigger a critical health status. 4. In the Warning number Hosts field, enter the remaining number of available hosts that should trigger a warning health status. 5. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate sensors if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring RNA Process Monitoring
Requires: DC/MDC Supported Platforms: RNA Use the RNA Process health status module to set limits for the number of restarts that trigger a change in the health status. The restart counter does not count actual restarts. The module checks if any restarts occurred during the period between tests. Even if multiple restarts occur between tests, the module only increments the restart counter by one each time it checks. If any restarts occur, the module adds one to the restart count. The first time the module checks and no restarts have occurred since the last test, the module resets the counter to zero. The alert level also lowers by one level (for example, Critical is reduced to Warning or Warning is reduced to Normal). The second time the module checks and no restarts have occurred since the last test, the alert level resets to Normal. If the module finds that the process is not running at all, it increments the restart counter by one, but sets the module status to Critical for that test, regardless of the limits set for the module. The status remains Critical until the module finds that the process is running. At that point, the module sets status according to the restart counter value and the configured limits for the module. If the module checks the RNA process as many times as configured in the Warning Number of restarts limit, and each time one or more restarts have occurred, the status classification for that module changes to Warning. If the module checks the RNA process as many times as configured in the Critical Number of restarts limit, and each time one or more restarts have occurred, the status classification for that module changes to Critical. That status data feeds into the health monitor.

Version 4.9.1

Sourcefire 3D System Administrator Guide

525

Using Health Monitoring Configuring Health Policies

Chapter 15

The maximum number of restarts you can set for either limit is 100, and the Critical limit must be higher than the Warning limit. To configure RNA Process health module settings: Access: Maint/Admin 1. In the Health Policy Configuration page, select RNA Process. The Health Policy Configuration - RNA Process page appears.

2. Select On for the Enabled option to enable use of the module for health status testing. 3. In the Critical Number of restarts field, enter the number of process restarts that should trigger a critical health status. 4. In the Warning Number of restarts field, enter the number of process restarts that should trigger a warning health status. 5. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate sensors if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring Time Synchronization Monitoring
Requires: DC/MDC Supported Platforms: Defense Center Use the Time Synchronization Status module to detect when the time on a managed sensor that uses NTP to obtain time from an NTP server differs by 10 seconds or more from the time on the server.

Version 4.9.1

Sourcefire 3D System Administrator Guide

526

Using Health Monitoring Configuring Health Policies

Chapter 15

To configure time synchronization monitoring settings: Access: Maint/Admin 1. In the Health Policy Configuration page, select Time Synchronization Status. The Health Policy Configuration - Time Synchronization Status monitor page appears.

2. Select On for the Enabled option to enable use of the module for health status testing. 3. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate sensors if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring Traffic Status Monitoring
Requires: DC/MDC Supported Platforms: IPS, RNA Use the Traffic Status health status module to detect whether a sensor receives traffic. If the Traffic Status module determines that a sensor does not receive traffic, the status classification for that module changes to Critical. That status data feeds into the health monitor. WARNING! If you enable the Traffic Status module on a sensor where there are unused interfaces that are included in an interface set associated with a detection engine, the module interprets the idleness of the port as a traffic failure and alerts on traffic status. To prevent alerting on idle interfaces, remove those interfaces from all interface sets associated with detection engines. For more information on managing interface sets, see Editing an Interface Set on page 221.

Version 4.9.1

Sourcefire 3D System Administrator Guide

527

Using Health Monitoring Configuring Health Policies

Chapter 15

To configure Traffic Status health module settings: Access: Maint/Admin 1. In the Health Policy Configuration page, select Traffic Status. The Health Policy Configuration - Traffic Status monitor page appears.

2. Select On for the Enabled option to enable use of the module for health status testing. 3. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate sensors if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Applying Health Policies
Requires: DC/MDC When you apply a health policy to an appliance, the health tests for all the modules you enabled in the policy automatically monitor the health of the processes and hardware on the appliance. Health tests then continue to run at the intervals you configured in the policy, collecting health data for the appliance and forwarding that data to the Defense Center. If you enable a module in a health policy and then apply the policy to an appliance that does not require that health test, the health monitor reports the status for that health module as disabled. If you apply a policy with all modules disabled to an appliance, it removes all applied health policies from the appliance so no health policy is applied. When you apply a different policy to an appliance that already has a policy applied, expect some latency in the display of new data based on the newly applied tests. IMPORTANT! Default health policies are not replicated between Defense Centers in a high availability pair. Each appliance uses the local default health policy configured for that appliance.

Version 4.9.1

Sourcefire 3D System Administrator Guide

528

Using Health Monitoring Configuring Health Policies

Chapter 15

You cannot apply a health policy to RNA Software for Red Hat Linux. To apply a health policy: Access: Maint/Admin 1. Select Operations > Monitoring > Health. The Health Monitor page appears. 2. Click Health Policy in the health monitor toolbar. The Health Policy page appears.

3. Click Apply next to the policy you want to apply. The Health Policy Apply page appears.

TIP! The status icon next to the Health Policy column ( ) indicates the current health status for the appliance. The status icon next to the System Policy column ( ) indicates the communication status between the Defense Center and the sensor. Note that you can remove the currently applied policy by clicking the remove icon ( ).

4. Check the appliances where you want to apply the health policy. 5. Click Apply to apply the policy to the selected appliances. The Health Policy page appears, with a message indicating if the application of the policy was successful. Monitoring of the appliance starts as soon as the policy is successfully applied.

Version 4.9.1

Sourcefire 3D System Administrator Guide

529

Using Health Monitoring Configuring Health Policies

Chapter 15

To unapply a health policy: Access: Maint/Admin 1. Select Operations > Monitoring > Health. The Health Monitor page appears. 2. Click Health Policy in the health monitor toolbar. The Health Policy page appears.

3. Click Apply next to the policy you want to apply. The Health Policy Apply page appears.

4. You have two options: • • Apply a health policy with all modules disabled. Click the x next to the health policy.

Under Health Policy the status of None appears.

Editing Health Policies
Requires: DC/MDC You can modify a health policy by enabling or disabling modules or by changing module settings. If you modify a policy that is already applied to an appliance, the changes do not take effect until you reapply the policy.

Version 4.9.1

Sourcefire 3D System Administrator Guide

530

3D3500. Health Modules Applicable to Appliances Module Appliance Heartbeat Automatic Application Bypass Status CPU Temperature CPU Usage Card Reset Data Correlator Process Defense Center Status Disk Usage eStreamer Process Event Stream Status Fan Alarm Hardware Alarms Health Monitor Process IPS Event Rate IPS Process Link State Propagation MDC Event Service Memory Usage PEP Status Power Supply Applicable Appliance Defense Center 3D Sensors. except 3D9900 3Dx800 Only All except 3D9900 All All Master Defense Center All Defense Center Master Defense Center 3Dx800 3Dx800 and 3D9900 Defense Center 3D Sensors with IPS 3D Sensors with IPS 3D Sensors with IPS Master Defense Center All 3D9900 Series 2 DC3000.1 Sourcefire 3D System Administrator Guide 531 . MDC3000. 3D4500. and 3D6500 Version 4.9. 3Dx800.Using Health Monitoring Configuring Health Policies Chapter 15 Applicable health modules for various appliances are listed in the Health Modules Applicable to Appliances table.

Click Edit next to the policy you want to modify. 4. as described in the following sections: • • • • • • • • Configuring Policy Run Time Intervals on page 500 Configuring Appliance Heartbeat Monitoring on page 501 Configuring Automatic Application Bypass Monitoring on page 502 Configuring CPU Temperature Monitoring on page 503 Configuring CPU Usage Monitoring on page 504 Configuring Card Reset Monitoring on page 505 Configuring Data Correlator Process Monitoring on page 506 Configuring Defense Center Status on page 507 Version 4.Using Health Monitoring Configuring Health Policies Chapter 15 Health Modules Applicable to Appliances (Continued) Module RNA Health RNA Host License Limit RNA Process Time Synchronization Status Traffic Status Applicable Appliance Defense Center Defense Center 3D Sensors with RNA Defense Center 3D Sensors with IPS. The Health Policy Configuration page appears.1 Sourcefire 3D System Administrator Guide 532 . Click Health Policy in the health monitor toolbar. 3. with the Policy Run Time Interval settings selected. The Health Policy page appears. The Health Monitor page appears. 2. 3D Sensors with RNA To edit a health policy: Access: Maint/Admin 1. Select Operations > Monitoring > Health.9. Modify settings as needed.

all changes you made will be saved. If you click Save Policy and Exit when you are done. if you click Cancel. click Cancel. Reapply the policy to the appropriate appliances as described in Applying Health Policies on page 528. click Save Policy and Exit. If you delete a policy that is still applied to an appliance.Using Health Monitoring Configuring Health Policies Chapter 15 • • • • • • • • • • • • • • • • • • Configuring Disk Usage Monitoring on page 508 Configuring eStreamer Process Monitoring on page 509 Configuring Event Stream Monitoring on page 511 Configuring Fan Monitoring on page 512 Configuring Hardware Monitoring on page 513 Configuring Health Status Monitoring Configuring IPS Event Rate Monitoring on page 515 Configuring IPS Process Monitoring on page 516 Configuring Link State Propagation Monitoring on page 518 Configuring MDC Event Service Monitoring on page 519 Configuring Memory Usage Monitoring on page 520 Configuring PEP Status Monitoring on page 521 Configuring Power Supply Monitoring on page 522 Configuring RNA Event Status Monitoring on page 523 Configuring RNA Host Usage Monitoring on page 524 Configuring RNA Process Monitoring on page 525 Configuring Time Synchronization Monitoring on page 526 Configuring Traffic Status Monitoring on page 527 To save your changes to this module and return to the Health Policy page.1 Sourcefire 3D System Administrator Guide 533 .9. any health monitoring alerts in effect for the sensor remain active until you Version 4. In addition. You have three options: • • • 6. if you delete a health policy that is applied to a sensor. select the other module from the list at the left of the page. To return to the Health Policy page without saving any of your settings for this module. you discard all changes. Deleting Health Policies Requires: DC/MDC You can delete health policies that you no longer need. To temporarily save your changes to this module and switch to another module’s settings to modify. the policy settings remain in effect until you apply a different policy. 5.

1 Sourcefire 3D System Administrator Guide 534 . you disable appliances or make them temporarily unavailable. To temporarily disable health events from an appliance. the events that were generated during the blacklisting continue to show a status of disabled. For more information on applying health policies. or detection engine from the blacklist. Select Operations > Monitoring > Health. The Health Monitor Appliance Status Summary lists the appliance as disabled. or detection engine. After the setting takes effect the appliance no longer includes the appliance when calculating the overall health status. but they have a disabled status and do not affect the health status for the health monitor. 2. For example. when you run out of Version 4. To delete a health policy: Access: Maint/Admin 1. For example. 3. see Applying Health Policies on page 528. health events are still generated. Click Delete next to the policy you want to delete. Using the Health Monitor Blacklist In the course of normal network maintenance. and add an appliance to the blacklist. The Health Monitor page appears. A message appears. When you disable health monitoring status. If you remove the appliance. see Activating and Deactivating Alerts in the Analyst Guide. see Creating Health Policies on page 497. You can use the health monitor blacklist feature to disable health monitoring status reporting on an appliance. Click Health Policy in the health monitor toolbar. go to the Blacklist configuration page. For more information on deactivating alerts. you do not want the health status from those appliances to affect the summary health status on your Defense Center or Master Defense Center. if you know that a segment of your network will be unavailable. create a health policy with all modules disabled and apply it to the appliance. The Health Policy page appears. Because those outages are deliberate. For more information on creating health policies. module. indicating if the deletion was successful. At times it may be more practical to just blacklist an individual health monitoring module on an appliance or detection engine.Using Health Monitoring Using the Health Monitor Blacklist Chapter 15 deactivate the underlying associated alert.9. module. TIP! To stop health monitoring for an appliance. you can temporarily disable health monitoring for a 3D Sensor on that segment to prevent the health status on the Defense Center from displaying a warning or critical state because of the lapsed connection to the 3D Sensor.

Version 4. the blacklist settings remain persistent. you can blacklist a managed sensor on one HA peer and not the other.1 Sourcefire 3D System Administrator Guide 535 . The newly re-registered sensor remains blacklisted. Note that on the main Health Monitor page you can distinguish between appliances that are blacklisted if you expand to view the list of appliances with a particular status by clicking the arrow in that status row. Note that if your Defense Center is in a high availability configuration. On the toolbar. You can also blacklist the HA peer to cause it to mark events generated by it and the sensors from which it receives health events as disabled. Make sure to remove all unused sensing interfaces from any interface sets in use by a detection engine so health monitoring alerts do not generate for those interfaces. the appliances report a disabled status in the Appliance Status Summary.9. Once the blacklist settings take effect. A blacklist icon ( ) and a notation are visible once you expand the view for a blacklisted or partially blacklisted appliance. click Blacklist. you can blacklist the RNA Host License Limit status messages until you install a new license with more hosts. The Blacklist page appears. If you need to disable the results of a group of appliances’ health monitoring. 2. you can blacklist the group of appliances. not a Master Defense Center.Using Health Monitoring Using the Health Monitor Blacklist Chapter 15 RNA host licenses on an appliance. The Health Monitor page appears. you can blacklist the policy. Health Monitor blacklist settings are system settings. To blacklist an entire health policy or group of appliances: Access: Maint/Admin 1. TIP! You can blacklist 3D Sensors only from a Defense Center. Therefore if you blacklist a sensor. You cannot blacklist intrusion agents. then delete it and later re-register it with the Defense Center. Select Operations > Monitoring > Health. For more information on expanding that view. see Using the Health Monitor on page 545. IMPORTANT! On a Defense Center. Blacklisting Health Policies or Appliances Requires: DC/MDC If you want to set health events to disabled for all appliances with a particular health policy.

4.9. On the toolbar. the appliance shows as disabled in the Health Monitor Appliance Module Summary and health events for the appliance have a status of disabled. Groups on a Master Defense Center are appliances. (On a Master Defense Center. sort the list by group. (On a Master Defense Center. or policy category. model.Using Health Monitoring Using the Health Monitor Blacklist Chapter 15 3. Select Operations > Monitoring > Health. select the category then click Apply. policy or model. policy. or by policy. Note that you can remove the currently applied policy by clicking the remove icon ( ).) The page refreshes. click Blacklist. model. manager. Groups on a Defense Center are 3D Sensors. 2.1 Sourcefire 3D System Administrator Guide 536 . or model. Use the drop-down list on the right to sort the list by group. 3. The status icon next to the System Policy column ( ) indicates the communication status between the Defense Center and the sensor. Once the blacklist settings take effect. Use the drop-down list on the right to sort the list by appliance group. policy or model. you can blacklist the appliance. sort the list by group. now indicating the blacklisted state of the appliances. select the manager then click Apply. Blacklisting an Appliance If you need to set the events and health status for an individual appliance to disabled.) Version 4. manager. The Blacklist page appears. (On a Master Defense Center. To blacklist all appliances in a group. The Health Monitor page appears. to blacklist all appliances associated with a manager. To blacklist an individual appliance: Access: Maint/Admin 1.) TIP! The status icon next to the Health Policy column ( ) indicates the current health status for the appliance.

Click Edit and see Blacklisting a Health Policy Module on page 537 to blacklist individual health policy modules. Defense Center Only Specific health policy modules operate for a Defense Center. Note that modules that allow you to select a specific detection engine have an arrow next to the module. When any part of a module is blacklisted. the line for that module appears in boldface type in the Defense Center web interface.Using Health Monitoring Using the Health Monitor Blacklist Chapter 15 4. select and expand a category folder. then click Apply.9. if you know you are going to disable the RNA detection engine on a sensor and do not want traffic status alerts to change the status for the sensor. You may want to do this to prevent events from the module from changing the status for the appliance to warning or critical. you can blacklist that module for a specific detection engine. Blacklisting a Health Policy Module Requires: DC/MDC You can blacklist individual health policy modules on appliances. In addition. When blacklisting modules for Defense Centers. For some modules. the interface indicates the following information in parentheses after each module with detection engines: number of blacklisted detection engines/maximum number of detection engines.1 Sourcefire 3D System Administrator Guide 537 . you can blacklist the Traffic Status module for that detection engine. The page refreshes then indicates the blacklisted state of the appliances. To blacklist an individual appliance. For example. select the box next to the appropriate appliance. only include the following modules: • • • • • • • • • Appliance Heartbeat CPU Usage Data Correlator Process Disk Usage eStreamer Process Health Monitor Process MDC Event Service Memory Usage Time Synchronization Status Version 4.

9. click Blacklist. Make sure that you keep track of individually blacklisted modules so you can reactivate them when you need them. The Health Monitor page appears. Version 4. see the Health Modules Applicable to Appliances table on page 531.1 Sourcefire 3D System Administrator Guide 538 . the appliance shows as Part Blacklisted or All Modules Blacklisted in the Blacklist page and in the Appliance Health Monitor Module Status Summary but only in expanded views on the main Appliance Status Summary page. On the toolbar. You may miss necessary warning or critical messages if you accidentally leave a module disabled. To blacklist an individual health policy module: Access: Maint/Admin 1. 2. TIP! Once the blacklist settings take effect. only include the following modules: • • • • • • • CPU Usage Data Correlator Process Defense Center Status Disk Usage Event Stream Status Memory Usage Power Supply For details about applicable modules on all appliances.Using Health Monitoring Using the Health Monitor Blacklist Chapter 15 • • Power Supply RNA Host License Limit Master Defense Center Only Specific health policy modules operate for a Master Defense Center. The Blacklist page appears. When blacklisting modules for Master Defense Centers. Select Operations > Monitoring > Health.

Sort by Group. The health policy modules appear.1 Sourcefire 3D System Administrator Guide 539 . 5. You have two options: • • Select each module that you want to blacklist.Using Health Monitoring Configuring Health Monitor Alerts Chapter 15 3. system log when the status changes for the modules in a health policy. 4. then select each detection engine for which you want to blacklist the module. Version 4. Expand the detection engine list by clicking on the arrow next to modules with detection engine lists. Configuring Health Monitor Alerts You can set up alerts to notify you through email. You can associate an existing alert with health event levels to cause that alert to trigger when health events of a particular level occur.9. or Model. then click Edit to display the list of health policy modules. Policy. Click Save. through SNMP or through the .

Create email.Using Health Monitoring Configuring Health Monitor Alerts Chapter 15 For example. Creating Health Monitor Alerts Requires: DC/MDC When you create a health monitor alert. and an alert. you also need to set up your email relay host in your system policy and re-apply that policy. • • • Continue with Creating Health Monitor Alerts on page 540. If you want to use email alerting. In the policy. To prepare your system for alerting: Access: Admin 1. see Creating Email Alerts in the Analyst Guide. Create a new policy or click Edit next to an existing one. a health module. Click Save Policy and Exit. if you are concerned that your appliances may run out of hard disk space. Enter the name of the Mail Relay Host. see Creating SNMP Alerts in the Analyst Guide. see the following topics: • • • • • Preparing to Create a Health Alert on page 540 Creating Health Monitor Alerts on page 540 Interpreting Health Monitor Alerts on page 542 Editing Health Monitor Alerts on page 543 Deleting Health Monitor Alerts on page 544 Preparing to Create a Health Alert Requires: DC/MDC If you want to create a health alert. 2. For more information on creating syslog alerts. If you plan to use email alerting: • • • • • • Select Operations > System Policy. see Creating Syslog Alerts in the Analyst Guide. you create an association between a severity level. For more information on creating email alerts. For more information on creating SNMP alerts. you can send a second email when the hard drive reaches the critical level.9. For more information Version 4. you can automatically send an email to a system administrator when the remaining disk space reaches the warning level. Click Apply and apply the policy to the Defense Center where you plan to create the health alert.1 Sourcefire 3D System Administrator Guide 540 . click Email Notification. For more information. If the hard drive continues to fill. SNMP or syslog alerts you want to associate with health alerts: . You can use an existing alert or configure a new one specifically to report on system health. you first need to create the underlying alert that you associate to the health alert.

the associated alert triggers. When duplicate thresholds exist. the health monitor uses the threshold that generates the fewest alerts and ignores the others. 4. you are notified of the conflict.294. The timeout value for the threshold must be between 5 and 4. The Health Monitor page appears.967 . 3. select the modules for which you want the alert to apply. Select Operations > Monitoring > Health.Using Health Monitoring Configuring Health Monitor Alerts Chapter 15 on creating the alert.1 Sourcefire 3D System Administrator Guide 541 . see Preparing to Create a Health Alert on page 540. 5.295 minutes. From the Module list. The Health Monitor Alerts page appears. Version 4. To create health monitor alerts: Access: Admin 1. Click Health Monitor Alerts in the health monitor toolbar. Type a name for the health alert in the Health Alert Name field.9. select the severity level you want to use to trigger the alert. Note that if you create or update a threshold in a way that duplicates an existing threshold. 2. TIP! To select multiple modules. From the Severity list. press Shift + Ctrl and click the module names. When the severity level occurs for the selected module.

Version 4. Description. TIP! Click Alerts in the toolbar to open the Alerts page. The health test results met the criteria to trigger a Warning alert status.9. Click Save to save the health alert. The Active Health Alerts list now includes the alert you created. The health test did not run. see Creating Alerts in the Analyst Guide. which includes the health test results that triggered the alert. 7. For more information on health modules. see the Alert Severities table. Interpreting Health Monitor Alerts The alerts generated by the health monitor contain the following information: • • • Severity.Using Health Monitoring Configuring Health Monitor Alerts Chapter 15 6. For more information on health alert severity levels.1 Sourcefire 3D System Administrator Guide 542 . A message appears. From the Alert list. which specifies the health module whose test results triggered the alert. select the alert which you want to trigger when the selected severity level is reached. type the number of minutes that should elapse before each threshold period ends and the threshold count resets. For more information on creating alerts. The health test results met the criteria to return to a normal alert status. see Understanding Health Modules on page 485. indicating if the alert configuration was successfully saved. which indicates the severity level of the alert. 8. Alert Severities Severity Critical Warning Normal Error Recovered Description The health test results met the criteria to trigger a Critical alert status. The health test results met the criteria to trigger a Normal alert status. following a Critical or Warning alert status. In the Threshold Timeout field. Module.

For more information. The Health Monitor page appears. Version 4. Click Save to save the modified health alert. indicating if the alert configuration was successfully saved. 5.Using Health Monitoring Configuring Health Monitor Alerts Chapter 15 Editing Health Monitor Alerts Requires: DC/MDC You can edit existing health monitor alerts to change the severity level.1 Sourcefire 3D System Administrator Guide 543 . health module. 3. see Creating Health Monitor Alerts on page 540. A message appears. Modify settings as needed.9. Select the alert you want to modify in the Active Health Alerts list. 4. 2. Click Health Monitor Alerts in the health monitor toolbar. Select Operations > Monitoring > Health. The Health Monitor Alerts page appears. To edit health monitor alerts: Access: Admin 1. 6. or alert associated with the health monitor alert. Click Load to load the configured settings for the selected alert.

For more information on deactivating alerts. Click Health Monitor Alerts in the health monitor toolbar. Select Operations > Monitoring > Health. You must deactivate or delete the underlying alert to ensure that alerting does not continue.9. The Health Monitor page appears. The Health Monitor Alerts page appears.Using Health Monitoring Configuring Health Monitor Alerts Chapter 15 Deleting Health Monitor Alerts Requires: DC/MDC You can delete existing health monitor alerts. 2. see Activating and Deactivating Alerts in the Analyst Guide. 4. Click Delete. Version 4. For more information on deleting alerts. To delete health monitor alerts: Access: Admin 1. IMPORTANT! Deleting a health monitor alert does not delete the associated alert.1 Sourcefire 3D System Administrator Guide 544 . see Deleting Alerts in the Analyst Guide. 3. A message appears. Select the alert you want to delete in the Active Health Alerts list. indicating if the alert configuration was successfully deleted.

The pie chart supplies another view of the health status breakdown. For more information on viewing the health status of your appliance.Reviewing Health Status Chapter 16 Administrator Guide You can obtain information about the health of your Sourcefire 3D System through the Health Monitor. Version 4. indicating the percentage of appliances currently in each health status category. The Health Monitor then generates health events to indicate the current status of any aspects of appliance health that you chose to monitor. The Status table provides a count of the managed appliances for this Defense Center by overall health status.1 Sourcefire 3D System Administrator Guide 545 . see the following topics: • • • Using the Health Monitor on page 545 Using Appliance Health Monitors on page 547 Working with Health Events on page 555 Using the Health Monitor Requires: DC/MDC The Health Monitor page provides the compiled health status for all sensors managed by the Defense Center.9. Administrators can create and apply a health policy to an appliance. plus the Defense Center.

Click Health Monitor on the toolbar. If the arrow points right.9. the appliance list for that status shows in the lower table. TIP! If the arrow in the row for a status level points down.Reviewing Health Status Using the Health Monitor Chapter 16 To use the health monitor: Access: Maint/Admin/ Any Analyst except Restricted 1. Select the appropriate status in the Status column of the table or the appropriate portion of the pie chart to the list appliances with that status. The Health Monitor page appears. the appliance list is hidden. 2.1 Sourcefire 3D System Administrator Guide 546 . The following topics provide details on the tasks you can perform from the Health Monitor page: • • • • Interpreting Health Monitor Status on page 547 Using Appliance Health Monitors on page 547 Configuring Health Policies on page 489 Configuring Health Monitor Alerts on page 539 Version 4.

1 Sourcefire 3D System Administrator Guide 547 . Health Status Indicator Status Level Error Status Icon Status Color White Description Indicates that at least one health monitoring module has failed on the appliance and has not been successfully re-run since the failure occurred. Contact your technical support representative to obtain an update to the health monitoring module.Reviewing Health Status Using Appliance Health Monitors Chapter 16 Interpreting Health Monitor Status Available status categories. including modules that were in a Critical or Warning state. IMPORTANT! Your browser session will not be automatically timed out while you are viewing the Health Monitor page. Normal. Indicates that warning limits have been exceeded for at least one health module on the appliance and the problem has not been corrected. Version 4. Critical. and Disabled. Indicates that an appliance is disabled or blacklisted. as described in the Health Status Indicator table. include Error. Indicates that all health modules on the appliance are running within the limits configured in the health policy applied to the appliance. by severity. Critical Red Warning Yellow Normal Green Recovered Green Disabled Blue Using Appliance Health Monitors Requires: DC/MDC The Appliance health monitor provides a detailed view of the health status of an appliance. Indicates that all health modules on the appliance are running within the limits configured in the health policy applied to the appliance.9. Warning. that the appliance does not have a health policy applied to it. Indicates that the critical limits have been exceeded for at least one health module on the appliance and the problem has not been corrected. or that the appliance is currently unreachable.

The Health Monitor Appliance page appears. For more information. click the color for the event status category you want to view.9. 2. In the Appliance column of the appliance list.1 Sourcefire 3D System Administrator Guide 548 . If the arrow points right. 3. see the following sections: • • • Interpreting Appliance Health Monitor Status on page 549 Viewing Alerts by Status on page 549 Running All Modules for an Appliance on page 550 Version 4. 4. click the arrow in that status row.Reviewing Health Status Using Appliance Health Monitors Chapter 16 To view the status summary for a specific appliance: Access: Maint/Admin/ Any Analyst except Restricted 1. The Alert Detail list toggles the display to show or hide events. click the name of the appliance for which you want to view details in the health monitor toolbar. the appliance list is hidden. To show the list of appliances with a particular status. Optionally. The Health