P. 1
Sourcefire_3D_System_Administrator_Guide_v4.9.1

Sourcefire_3D_System_Administrator_Guide_v4.9.1

|Views: 8,860|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

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

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. dashboard. • • • Version 4. account password. • • • Components of the Sourcefire 3D System on page 15 provides descriptions of each of the components that may be in your Sourcefire 3D System.9. Using the Context Menu on page 36 explains how to display a context-specific menu of shortcuts on certain pages in the web interface. 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. Specifying Your User Preferences on page 25 explains how to configure the preferences that are tied to a single user account. and event viewing preferences. such as the home page.1 Sourcefire 3D System Administrator Guide 14 . time zone. Logging Out of the Appliance on page 24 explains how to log out of the web interface. 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.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.

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. and traffic profiles to protect your company’s infrastructure by monitoring network traffic for unusual patterns or behavior and automatically responding as needed.9. You must use a Defense Center to manage a 3D Sensor if it is running RNA. 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. You can set up compliance policies. using information from detected packets to build a comprehensive map of the devices on the network. IP Address Conventions on page 41 explains how the Sourcefire 3D System treats IP address ranges specified using Classless Inter-Domain Routing (CIDR) notation. compliance white lists. Documentation Conventions on page 38 explains typeface conventions used throughout the guide to convey specific types of information visually. listening to the network segments you specify.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.1 Sourcefire 3D System Administrator Guide 15 . As RNA passively observes traffic. RNA monitors traffic on your network. • • • • • • • • • 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.

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

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

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

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

IMPORTANT! Because the 3D Sensor Software for X-Series does not have a web interface. but allows you to request specific data from a Defense Center. 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.Introduction to the Sourcefire 3D System Components of the Sourcefire 3D System Chapter 1 assigns impact flags to the events. for example.9. 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. You can continue to manually tune Snort rules and preprocessors with the Intrusion Agent in place. Version 4. If. you could write a program to retrieve host criticality or vulnerability data from the Defense Center and add that information to your display. you display network host data within one of your network management applications.1 Sourcefire 3D System Administrator Guide 20 . See the Sourcefire RNA Software on Red Hat Linux Configuration Guide for more information. eStreamer integration requires custom programming. IMPORTANT! When using Intrusion Agents registered to Defense Centers configured for high availability and managed by a Master Defense Center. register all Intrusion Agents to the primary Defense Center. you must use a Defense Center to manage it. See the eStreamer Integration Guide for more information. eStreamer You can access event data within your own applications through the eStreamer Application Programming Interface (API). 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. 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. Separate installation and configuration guides are available for the 3D Sensor Software for X-Series. IMPORTANT! You must have a Defense Center in your Sourcefire 3D System deployment to use RNA for Red Hat Linux.

Version 4.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.9.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. RNA for Red Hat Linux.1 Sourcefire 3D System Administrator Guide 21 . 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.0 Microsoft Internet Explorer 8. If you are the first user to log into the appliance after it is installed. make sure you allow the script to continue until it finishes. management. The current version of the web interface supports the browsers listed in the following table. If your 3D Sensor is not licensed for IPS. and Virtual 3D Sensors) do not have a web interface.5.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 . you are presented with a more complete web interface that you can use to perform additional configuration and event analysis. You must use the Defense Center’s web interface to manage these sensors. you must log in using the admin user account. You can access the web interface by logging into the appliance using a web browser. The initial setup process is described in Setting Up 3D Sensors on page 44. Intrusion Agents. Note that 3Dx800 and software sensors (Crossbeam-based software sensors. Browser Requirements Browser Firefox 3. If your 3D Sensor is licensed for IPS. and analysis tasks. If this occurs.

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

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

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

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. You can change your password at any time. Specifying Your Home Page on page 35 explains how to use one of the existing pages as your default home page.1 Sourcefire 3D System Administrator Guide 25 . Specifying Your Default Dashboard on page 35 explains how to choose which of the dashboards you want to use as your default dashboard. Configuring Event View Settings on page 27 describes how the event preferences affect what you see as you view events. month.5 hours of inactivity. Specifying Your User Preferences Requires: Any Users can specify certain preferences for their user account. see Changing an Expired Password on page 26.Introduction to the Sourcefire 3D System Last Successful Login Chapter 1 Note that your session automatically logs you out after 3. and home page preferences. To log out of the appliance: Access: Any Click Logout on the toolbar. this is the first page you see upon logging into the appliance. • • Changing Your Password Requires: Any All user accounts are protected with a password. you may have to change your password periodically. See the following sections for more information: • • • Changing Your Password on page 25 explains how to change the password for your user account. After setting this value. and depending on the settings for your user account. event viewing preferences. you can view information about the last login session for the appliance. Last Successful Login Requires: Any The first time you visit the appliance home page during a web session.9. 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. Version 4. time zone settings. including passwords. You can see the following information about that user account last login: • • • day of the week. 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 26 . In the toolbar. Also. passwords must be at least eight alphanumeric characters of mixed case and must include at least one numeric character. If your password has exired.9. To change your password: Access: Any 1. The Change Password page appears. Version 4. In the Current Password field. If you have zero warning days left. passwords must be at least eight alphanumeric characters of mixed case and must include at least one numeric character. 3. type your new password. 2. Passwords cannot be a word that appears in a dictionary or include consecutive repeating characters. the Password Expiration Warning page appears. To respond to the password expiration warning: Access: Any You have two choices: • Click Change Password to change your password now. your password can expire. A success message appears on the page when your new password is accepted by the system. 5. Changing an Expired Password Requires: DC/MDC or 3D Sensor Depending on the settings for your user account. Click Change. click Preferences. In the New Password and Confirm fields. The User Preferences page appears. IMPORTANT! If you are an LDAP or a RADIUS user. Click Change Password. you cannot change your password through the web interface. 4. Note that the password expiration time period is set when your account is created and cannot be changed. Passwords cannot be a word that appears in a dictionary or include consecutive repeating characters • Click Skip to change your password later. you must change your password. if password strength-checking is enabled.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 Note that if password strength-checking is enabled. type your current password and click Change.

Configure default workflows. 5. For more information. Your changes are implemented. Click Event View Settings.9. To configure event preferences: Access: Any 1.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. 6. see Default Workflows on page 32. 2. 4.1 Sourcefire 3D System Administrator Guide 27 . see Event Preferences on page 27. see Default Time Windows on page 29. Version 4. The User Preferences page appears. The Event View Settings page appears. For more information. 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. Click Save. click Preferences. Configure the default time window or windows. In the toolbar. For more information. 3. Configure the basic characteristics of event views.

Any IPS or DC/MDC + IPS IPS or DC/MDC Requires Any Version 4. see Using the Packet View in the Analyst Guide.expand only the Packet Bytes subsection • All . 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. By default. 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. Expand Packet View Allows you to configure how the packet view for intrusion events appears. Event Preferences Setting Confirm ‘All’ Actions Description Controls whether the appliance forces you to confirm actions that affect all events in an event view.expand only the Packet Text subsection • Packet Bytes . • None .1 Sourcefire 3D System Administrator Guide 28 . Note also that for this setting to take effect. you must have a DNS server configured in the system settings.expand all sections Regardless of the default setting. the appliance displays a collapsed version of the packet view. For more information on the packet view. Resolve IP Addresses Whenever possible.9.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 The Event Preferences table describes the settings you can configure. Rows Per Page Controls how many rows of events per page you want to appear in drill-down pages and table views. see Configuring Network Settings on page 377.collapse all subsections of the Packet Information section of the packet view • Packet Text . if this setting is enabled and you click Delete All on an event view. For example. 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.

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

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

For static time windows (enable the Use End Time check box). the time window expands to the present time. the appliance displays all the events generated from a specific start time (for example. As you change event views. 1 hour ago) to the present. For expanding time windows (disable the Use End Time check box). As you change event views. 1 hour ago). 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. to the present. Version 4.1 Sourcefire 3D System Administrator Guide 31 . the time window “slides” so that you always see events from the last hour. 1 hour ago). the appliance displays all the events generated from a specific start time (for example. IMPORTANT! The maximum time range for all time windows is from midnight on January 1.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. As you change event views.9. 1970 (UTC) to 3:14:07 AM on January 19. Show the Last Static/Expanding This setting allows you to configure either a static or expanding default time window of the length you specify. the time window stays fixed so that you see only the events that occured during the static time window. The appliance displays all the events generated from a specific start time (for example. to the time when you first viewed the events. 2038 (UTC).

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

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

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

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

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

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

DC1000.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. or DC3000 appliance used as a Defense Center Version 4. Refer to Platform Requirements Conventions on page 38 for the meaning of the Requires statement at the beginning of each section.9. 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.1 Sourcefire 3D System Administrator Guide 38 . All platform information is formatted with an orange typeface. Virtual Defense Center. 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. Refer to Access Requirements Conventions on page 39 for the meaning of the Access statement at the beginning of each procedure. Any DC Any appliance with any combination of licenses A DC500.

9. 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. All access information is formatted with a green typeface. so the Adding a Master Defense Center topic has a Requires statement of MDC + DC.1 Sourcefire 3D System Administrator Guide 39 . you can change an expired password on a Defense Center or Master Defense Center or on a 3D Sensor. 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. For example. A “+” conjunction indicates that the platforms are required in combination. you need both a Defense Center and a Master Defense Center. so the Changing an Expired Password topic has a Requires statement of DC/MDC or 3D Sensor. In contrast.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. to manage a Defense Center with a Master Defense Center.

For example. The Access setting for the procedure in the Working with the Hosts Network Map topic is Any RNA/Admin. Rule thresholding in the packet view provides an example of required combined access roles.9. to view the Hosts network map. 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.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.1 Sourcefire 3D System Administrator Guide 40 . 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.

0.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.0. variables. the Sourcefire 3D System uses only the masked portion of the network IP address you specified.048.168.16. the Sourcefire 3D System uses 10.0.255.255.0.0.0.0/16 IP Addresses in CIDR Block 10.0 172. the following table lists the private IPv4 address spaces in CIDR notation.255.240.2. 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.0.777 .Introduction to the Sourcefire 3D System IP Address Conventions Chapter 1 from the packet view.0/8 172. without changing your user input.0 255. 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. if you type 10.1.255 172.255.0 255. Version 4.2.1.9.0.255 192. As a result.0.0/8. the Access setting for the procedure in the Setting Threshold Options within the Packet View topic is IPS + P&R Admin/Admin.16.0 10.216 1.0.255 Subnet Mask 255.3/8.0/12 192.1 Sourcefire 3D System Administrator Guide 41 . but the web interface continues to display 10.3/8.0.31. For example.168. For example.0. CIDR Notation Syntax Examples CIDR Block 10.255.0.576 65.0 Number of IP Addresses 16.536 When you use CIDR notation to specify a range of IP addresses.0 192.

9. although Sourcefire recommends the standard method of using a network IP address on the bit boundary when using CIDR notation. Version 4.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. Note that if you purchased your sensor prior to 2008.1 Sourcefire 3D System Administrator Guide 43 . provide a rapid set up feature and a status page. 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. you are presented with a series of start-up pages. Consult your original documentation or contact Sourcefire Support for information about performing the initial setup on those sensor models. you may have a Series 1 3D Sensor. Setting up Defense Centers on page 47 explains how to complete the setup process for Defense Centers. What’s Next? on page 52 provides detailed lists of the next tasks to be performed by each type of user. To perform the initial setup of a Virtual 3D Sensor. called Series 2 sensors. see the Sourcefire 3D System Virtual Defense Center and 3D Sensor Installation Guide.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. Newer models of the 3D Sensor.9.

in the New Password and Confirm fields.1 Sourcefire 3D System Administrator Guide 44 . After physically installing the 3D Sensor. The same password is used for both accounts. Version 4.9. enter a new password for the admin user account and for the root password for the shell account. If the initial setup is interrupted or if a second user logs in while it is underway. Sourcefire strongly recommends that your password is at least eight alphanumeric characters of mixed case and includes at least one numeric character. Use the command line interface on the appliance for subsequent changes to the root password. 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. Defense Centers use the setup process in Setting up Defense Centers on page 47. the Install page appears so that you can continue the setup process. TIP! The initial change to the admin user password changes the root password for the shell account. the results can be unpredictable. and logging into the 3D Sensor’s web interface (as described in the 3D Sensor Installation Guide). Avoid using words that appear in a dictionary. Series 2 sensors) provide a simple web form to collect information about your network environment and how you intend to deploy the sensor.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. To complete the initial setup: Access: Admin 1. Under Change Password. WARNING! Prepare for the initial setup and complete it promptly after you begin. setting up the IP address for the management interface.

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

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

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

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

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

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

Refer to the Required Open Ports table for more information on functions and their associated ports. 80 162 389. Open this port only if you are using a remote syslog server. Open this port for communicatiosn between the Defense Center and RUA Agents.Performing the Initial Setup Communication Ports Chapter 2 certain functionality within the network deployment. 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 for communications between the Defense Center and Intrusion Agents.1 Sourcefire 3D System Administrator Guide 51 . 21 22 23 25 53 67 68 . Notes Version 4. Open this port when you connect to a remote web server through the RSS widget. Required Open Ports Ports 20.9.

• • Version 4. Policy & Response Administrator user. 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. or RUA. Intrusion Event Analyst user.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. deployments that do not include a Defense Center and do not use RNA). IMPORTANT! Tasks that must be completed on specific hardware or software platforms are indicated by special text: For example. which are based on the user account privileges required for the task. you can perform much of the process on the Defense Center itself. if your Defense Center or 3D Sensor must be licensed for IPS. tasks that require a Defense Center are preceded with Requires: DC. or RNA Event Analyst user) and what appliance you are using.1 Sourcefire 3D System Administrator Guide 52 .8.9. RNA. Requires: RNA. • 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. Similarly. the task is preceded with Requires: IPS. For deployments that include a Defense Center. or Requires: RUA. 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. For standalone 3D Sensor deployments (that is. 4. Notes What’s Next? Requires: Any After you complete the initial setup for the Sourcefire 3D System. See Managing Users on page 264 for more information about user roles. a user with Administrator access must perform the first steps.x 3D Sensors. your next steps depend on the role assigned to your user account (Administrator user. Maintenance user. Review the tasks in the following sections.

Version 4. 3. 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. but you cannot use high availability mode directly on the Master Defense Center itself. The first steps for the Administrator user are as follows: Access: Admin 1. In most network environments. the sensors you add to the primary Defense Center are automatically added to the secondary Defense Center. Tasks essential to initial setup are listed below. you should set it up now.9. 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. TIP! After you set up management. Requires: DC If you are deploying two Defense Centers in high availability mode.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. 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. 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.1 Sourcefire 3D System Administrator Guide 53 . 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. 2. Administrator User Tasks Requires: Any Administrator users have a superset of tasks. you must create an authentication object for that server as described in Creating LDAP Authentication Objects on page 269. TIP! You can use high availabilty mode on Defense Centers which are managed by a Master Defense Center. set up high availability as explained in Configuring High Availability on page 145. Requires: DC If you want to authenticate users using an external authentication server.

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

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

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

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

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

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

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

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

the Current Interface Status widget on a 3D Sensor displays the status of its sensing interfaces. You can delete or minimize unauthorized and invalid widgets. but on Defense Centers and Master Defense Centers the widget displays only the status of the management interface. 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. see Minimizing and Maximizing Widgets on page 97 and Deleting Widgets on page 97. as well as widgets that display no data. the content of a widget can differ depending on the type of appliance you are using. The Sourcefire Appliances and Dashboard Widget Availability table lists the valid widgets for each appliance.9.Using Dashboards Understanding Dashboard Widgets Chapter 3 Similarly. For more information. An X indicates that the appliance can display the widget. keeping in mind that modifying a widget on a shared dashboard modifies it for all users of the appliance.1 Sourcefire 3D System Administrator Guide 62 . Note than any content generated in table format can be sorted by clicking on the table column header. For example.

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. An X indicates the user can view the widget.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.9.1 Sourcefire 3D System Administrator Guide 63 . IMPORTANT! dashboards.

which displays the current status of the network interfaces for the appliance. The preferences section for that widget appears. Widget preferences can also be more complex.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. Version 4. On the title bar of the widget whose preferences you want to change. which is a highly customizable widget that allows you to display detailed information on the events collected and generated by the Sourcefire 3D System. the following graphic shows the preferences for the Current Interface Status widget. To modify a widget’s preferences: Access: Any except Restricted 1. click the show preferences icon ( ). Widget preferences can be simple. For example. For example.9. the following graphic shows the preferences for the Custom Analysis widget.1 Sourcefire 3D System Administrator Guide 64 . You can only configure the update frequency for this widget.

Your changes take effect immediately. For more information. Make changes as needed. see Understanding Widget Availability on page 61.9. For detailed information on the widgets delivered with the Sourcefire 3D System. as well as information about the status and overall health of the appliances in your deployment. click the hide preferences icon ( preferences section. when used on dashboards. 3.1 Sourcefire 3D System Administrator Guide 65 . including data about the events collected and generated by the Sourcefire 3D System. Version 4. ) 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. see Understanding the Predefined Widgets on page 65. For information on the preferences you can specify for individual widgets.Using Dashboards Understanding the Predefined Widgets Chapter 3 2. 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. can provide you with at-a-glance views of current system status.

9. Version 4. module pack. SEU. The widget provides: • • the name. 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. the name. and vulnerability database (VDB) installed on the appliance for managed appliances. management interface IP address.1 Sourcefire 3D System Administrator Guide 66 . operating system. rule pack. see Understanding Widget Preferences on page 64. and Sourcefire 3D System software and operating system versions of the peer Defense Center. Snort.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. For more information. and model of the appliance the versions of the Sourcefire 3D System software. model. the name and status of the communications link with the managing appliance for Defense Centers in a high availability pair. the preferences also control how often the widget updates.

You can configure the widget to display appliance status as a pie chart or in a table by modifying the widget preferences. Version 4. For more information. see Understanding Widget Preferences on page 64. 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.1 Sourcefire 3D System Administrator Guide 67 . The preferences also control how often the widget updates. 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. you must manually apply a health policy or their status appears as Disabled. Note that because the Defense Center does not automatically apply a health policy to managed sensors. over the dashboard time range.9. For more information.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.

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

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

if you are using Sourcefire RNA as part of your deployment. 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. Microsoft Windows. Aggregating this data by Count tells you how many hosts are running each operating system. 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. constraining the first example (operating systems Version 4. how many unique versions of Linux.Using Dashboards Understanding the Predefined Widgets Chapter 3 For example. Mac OS X. For example. On the other hand.9.1 Sourcefire 3D System Administrator Guide 70 . and so on). you can further constrain the widget using a saved search. Optionally.

On the other hand. The up-arrow icon ( ) indicates that the event has moved up in the standings since the last time the widget updated. The direction icon ( ) indicates and controls the sort order of the display. if you set the dashboard time range to an hour. click the icon. the widget updates every five minutes. you can configure the Custom Analysis widget to display a line graph. • The widget displays the last time it updated. A downward-pointing icon indicates descending order. the widget updates once a week. You can change the color of the bars as well as the number of rows that the widget displays. A number indicating how many places the event has moved down appears next to the icon. The colored bars in the widget background show the relative number of occurrences of each event. Next to each event. To determine when the dashboard will update next. If you want information on events or other collected data over time. 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 down-arrow icon ( ) indicates that the event has moved down in the standings since the last time the widget updated. To change the sort order. an upwards-pointing icon indicates ascending order. The widget updates with a frequency that depends on the dashboard time range.1 Sourcefire 3D System Administrator Guide 71 . A number indicating how many places the event has moved up appears next to the icon.9. You can also configure the widget to display the most frequently occurring events or the least frequently occurring events. such as one that displays the total number of intrusion events generated in your deployment over Version 4. based on the local time of the appliance. For example.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. 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. if you set the dashboard time range to a year.

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

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

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

Displays the most active hosts on your monitored network. Displays the most active hosts on your monitored network. based on the number of flows where the host initiated the session. (The predefined dashboards on the Master Defense Center and 3D Sensor do not include Custom Analysis widgets. 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. Displays the most frequently occurring types of intrusion events. Displays the most active services on your monitored network. where the packet was not dropped as part of the event. by classification. based on the number of flows where the host was the responder in the session.9. where the packet was dropped.Using Dashboards Understanding the Predefined Widgets Chapter 3 each preset. based on the number of detected flows. Displays the most active ports on your monitored network. by application type. Displays counts for the most frequently occurring intrusion events. by classification.) .1 Sourcefire 3D System Administrator Guide 75 . 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. Displays the most active client applications on your monitored network.

Displays the most common operating system. based on the number of hosts running each operating system within your network.9. Displays the most common RNA service vendors. Displays the most active hosts on your monitored network. Displays the most frequently occurring types of intrusion events.1 Sourcefire 3D System Administrator Guide 76 .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. Displays the most active hosts on your monitored network. based on event classification. based on frequency of intrusion events. based on the number of intrusion events occurring on high criticality hosts. Displays the most active hours of the day. based on the number of intrusion events where the host was the targeted host in the flow that caused the event. over the dashboard time range. 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 hosts on the network running services made by that vendor. based on the number of intrusion events where the host was the attacking host in the flow that caused the event. Displays a count of intrusion event requiring analysis.

based on the total number of kilobytes of data received by the hosts where those users are logged in. Displays the most active RUA users on your monitored network.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 by the hosts.9. Displays a graph of the total kilobytes of data transmitted on your monitored network over the dashboard time range. based on the number of kilobytes per second of data transmitted by the service. 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 responder ports on your monitored network.1 Sourcefire 3D System Administrator Guide 77 . based on the number of kilobytes per second of data received by the hosts. based on the number of kilobytes per second of data transmitted via the port. Displays the most active hosts on your monitored network.

depending on how many time windows you have configured and on what type of event you are trying to view. For example. the events appear in the default health events workflow. For more information on time windows. you can invoke an event view (that is. As another example. see Default Time Windows on page 29 and Specifying Time Constraints in Searches in the Analyst Guide. constrained by the dashboard time range. if you configure a single time window and then access any type of event from the Custom Analysis widget. based on the number of unique intrusion events per targeted host. the events appear in the default workflow for that event type.9. and the health monitoring time window changes to the dashboard time range. and the global time window changes to the dashboard time range. the events appear in the default workflow for that event type. Displays the hosts with the most white list violations. 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. When you invoke an event view from the dashbaord. Version 4. This also changes the appropriate time window for the appliance. a workflow) that provides detailed information about the events displayed in the widget.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. if you configure multiple time windows on your Defense Center and then access health events from a Custom Analysis widget. Displays the number of unique intrusion event types associated with each impact flag level.1 Sourcefire 3D System Administrator Guide 78 .

remember that not all users can view data of all event types. For Version 4. constrained by the widget preferences. depending on the user’s account privileges. click any event to view associated events constrained by the widget preferences.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. as well as by that event. depending on how you configured the widget: • On widgets configured to show relative occurrences of events (that is. bar graphs). click the View All icon in the lower right corner of the widget to view all associated events. constrained by the widget preferences. For example. Similarly. Intrusion Event Analysts cannot view RNA events. If you are configuring the widget on a shared dashboard. if you are using a dashboard imported from another appliance. 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.1 Sourcefire 3D System Administrator Guide 79 .9. • For information on working with specific event types. On widgets configured to show flow data over time. You can also click the View All icon in the lower right corner of the widget to view all associated events. remember that not all appliances have access to data of all event types.

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

On the Defense Center and Master Defense Center. Note that for managed 3D Sensors. On the 3D Sensor. the widget can display statistics for dropped intrusion events. you cannot configure the widget to display Version 4. On the 3D Sensor. On 3D Sensors. you must enable local event storage or the widget will not have any data to display. 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. or both. The widget preferences control how often the widget updates. For more information. Note that only 3D Sensors have interfaces other than the management interface.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. the widget only displays the traffic rate for interfaces that belong to an interface set). you can configure the widget to display intrusion events of different impacts by modifying the widget preferences.1 Sourcefire 3D System Administrator Guide 81 . see Understanding Widget Preferences on page 64.9. the preferences also control whether the widget displays the traffic rate for unused interfaces (by default. this includes statistics on intrusion events of different impacts. all intrusion events.

see Viewing Intrusion Events in the Analyst Guide. see Understanding Widget Preferences on page 64. On either appliance. the widget displays a pie chart that shows the Version 4. select All to display an additional graph for all intrusion events.9. accessing intrusion events via the dashboard changes the events (or global) time window for the appliance. 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). you can display dropped events. regardless of impact or rule state. 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. On the Intrusion Events widget.1 Sourcefire 3D System Administrator Guide 82 .Using Dashboards Understanding the Predefined Widgets Chapter 3 intrusion events by impact. 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. For more information on intrusion events. For more information. The following graphic shows the Defense Center version of the widget preferences. In the widget preferences. you can: • Requires: DC/MDC select one or more Event Flags check boxes to display separate graphs for events of specific impacts. By default.

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

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

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

or VDB.9. as well as whether you want to show descriptions of the stories along with the headlines. the widget shows a feed of Sourcefire company news. you can: • manually update an appliance by clicking the current version of the Sourcefire 3D System software. keep in mind that not all RSS feeds use descriptions. You can also configure the widget to display a preconfigured feed of Sourcefire security news. Version 4. or you can create a custom connection to any other RSS feed by specifying its URL in the widget preferences. or VDB by clicking either the latest version or the Unknown link in the Latest column. When you configure the widget.1 Sourcefire 3D System Administrator Guide 86 . you can also choose how many stories from the feed you want to show in 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. see Scheduling Tasks on page 425 • Understanding the RSS Feed Widget Requires: Any The RSS Feed widget adds an RSS feed to a dashboard. By default. SEU. SEU. 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.Using Dashboards Understanding the Predefined Widgets Chapter 3 On the Product Updates widget. 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.

measured by the number of processes waiting to execute) on the appliance. For more information. Understanding the System Time Widget Requires: Any The System Time widget shows the local system time. see Understanding Widget Preferences on page 64. see Understanding Widget Preferences on page 64. You can configure the widget to show or hide the load average by modifying the widget preferences. both currently and over the dashboard time range. memory (RAM) usage. For more information. and system load (also called the load average. uptime.9.1 Sourcefire 3D System Administrator Guide 87 . The preferences also control how often the widget updates. 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. The preferences also control how often the widget synchronizes with the appliance’s clock. Version 4. and boot time for the appliance.Using Dashboards Understanding the Predefined Widgets Chapter 3 On the RSS Feed widget.

Version 4.1 Sourcefire 3D System Administrator Guide 88 . accessing white list events via the dashboard changes the events (or global) time window for the Defense Center. over the dashboard time range. You can click a graph to view white list events of a specific priority. 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.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. In either case.9. For more information. the events are constrained by the dashboard time range. In the widget preferences. you can: • • • select one or more Priorities check boxes to display separate graphs for events of specific priorities. see Understanding Widget Preferences on page 64. You can configure the widget to display white list events of different priorities by modifying the widget preferences. For more information on white list events. including events that do not have a priority select Show All to display an additional graph for all white list events. or click the All graph to view all white list events. see Viewing White List Events in the Analyst Guide.

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

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

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

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

and rename tabs. click the pause icon ( The dashboard is paused until you unpause it. For more information. which include its name and description. as well as rearrange the widgets on a tab. ). You can add. Note that you cannot change the order of dashboard tabs. can modify shared dashboards. click the play icon ( The dashboard is unpaused.Using Dashboards Working with Dashboards Chapter 3 To pause the dashboard: Access: Any except Restricted On the time range control. 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. and whether you want to share the dashboard with other users. ). which include its name and description. add and remove widgets from tabs. the tab cycle and page refresh intervals. delete. Version 4. You can also change the basic dashboard properties. 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.9. Modifying Dashboards Requires: Any Each dashboard has one or more tabs. make sure to set it as a private dashboard in the dashboard properties. You can minimize and maximize widgets. regardless of role. IMPORTANT! Any user.1 Sourcefire 3D System Administrator Guide 93 . To unpause the dashboard: Access: Any except Restricted On the time range control of a paused dashboard. the tab cycle and page refresh intervals. Each tab can display one or more widgets in a three-column layout.

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

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

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

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

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

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

For example.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. The sections that follow explain some of the concepts you need to know as you plan your Sourcefire 3D System deployment. Editing a Managed Sensor’s System Settings on page 133 describes the sensor attributes you can edit and explains how to edit them. you can create an intrusion policy on the Defense Center and apply it to all your managed 3D Sensors with IPS. Managing a Clustered Pair on page 140 describes how to create a clustered pair of 3D9900s and how to remove 3D9900s from clusters. you can use the Defense Center’s web interface to accomplish nearly any task on any sensor it manages. and change the state of managed sensors and how to reset management of a sensor. Instead of managing each sensor using its own local web interface. Managing Sensor Groups on page 131 describes how to create sensor groups as well as how to add and remove sensors from groups. 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.9. First. Working in NAT Environments on page 112 describes the principles of setting up the management of your sensors in Network Address Translation environments. It also explains how to add. Working with Sensors on page 113 describes how to establish and disable connections between sensors and your Defense Center. • • • • • 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. delete.1 Sourcefire 3D System Administrator Guide 100 . you can use the Defense Center as a central point of management. 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. This saves you from having Version 4.

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. so you must use the Defense Center to manage it. 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. 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 create the policy on the Defense Center and push it to the appropriate sensors instead of replicating it locally. The Defense Center can then assign impact flags to each intrusion event. Fourth. You can also create and apply system policies to your managed sensors. You can use user information from an external server to authenticate users on your Sourcefire 3D System appliances. You can also generate reports based on events from multiple sensors.1 Sourcefire 3D System Administrator Guide 101 . You can also apply a health policy to the Defense Center to monitor its health. when you manage a sensor with a Defense Center. all the intrusion events and RNA events are automatically sent to the Defense Center. Second.Using the Defense Center Management Concepts Chapter 4 to replicate the intrusion policy on each sensor. Finally. if your Defense Center manages sensors with IPS and RNA. 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. and those sensors view the same network traffic. There is a similar savings when you create and apply RNA appliance and detection policies to managed 3D Sensors with RNA. The impact flag indicates how likely it is that an intrusion attempt will affect its target. then the Defense Center can correlate the intrusion events it receives with the information about hosts that RNA provides. 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. By pushing a system policy with configured authentication objects to your sensor. A system policy controls several appliance-level settings such as the login banner and the access control list. External authentication cannot be managed on the sensor. Because most of the sensors in your deployment are likely to have similar settings in the system policy. you push the external authentication object to the sensor.9. which can be a laborious task depending on how many of the thousands of intrusion rules you want to enable or disable. Third.

If you apply a policy on a sensor before you begin managing it with a Defense Center. Note that the types of events and policies that are sent between the appliances are based on the sensor type. 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. SSL-encrypted TCP tunnel. For details on DC500 database limitations see Database Event Limits on page 333. Version 4. as well as intrusion agents and RNA software on approved platforms.9.1 Sourcefire 3D System Administrator Guide 102 . information is transmitted between the Defense Center and the sensor over a secure. When you manage a sensor (or a software sensor). you can see a read-only version of the policy on the Defense Center’s web interface. You can also use a DC500 to manage Sourcefire 3D Sensor software on approved platforms.

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

the following graphic shows the Detection Engine page on a 3D Sensor with IPS. 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. Version 4.example. The Sample Intrusion Policy that is currently applied to the sensor’s two detection engines was created on the Defense Center (pine. after communications are set up. TIP! After you set up management with a Defense Center.1 Sourcefire 3D System Administrator Guide 104 . If you want to edit a policy. Sourcefire recommends that you use only the Defense Center’s web interface to view events and manage policies for your managed sensors.com).9. you must do it on the appliance where the policy was created.Using the Defense Center Management Concepts Chapter 4 Then. For example.

for more information. 3D3800. RNA Software for Red Hat Linux . see Managing 3D Sensor Software with RNA for Crossbeam on page 110 3D Sensor Software with IPS for Crossbeam X-Series . and 3D9800 sensors . they are automatically shared with managed 3D Sensors with RNA. A software-based sensor is a software-only installation of Sourcefire 3D System sensor software.for more information. if you delete an intrusion event from the Defense Center. Understanding Software Sensors Requires: DC Several of the sensors you can manage with a Defense Center are softwarebased sensors.for more information. Also note that operations you perform on data on one appliance are not transmitted to other appliances.9.for more information. The following Sourcefire 3D System sensors are software-based: • • • • Intrusion Agents for various platforms .for more information. Similarly. see Managing RNA Software for Red Hat Linux on page 109 3D Sensor Software with RNA for Crossbeam X-Series .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. see Managing 3D Sensor Software with IPS for Crossbeam on page 110 • Version 4. see Managing Intrusion Agents on page 106 3D5800. deleting an intrusion event from a sensor does not delete it from the Defense Center. see Managing 3Dx800 Sensors on page 107. the event remains on the sensor that discovered it. For example.1 Sourcefire 3D System Administrator Guide 105 .

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

and 3D Sensor 9800 models (usually referred to as the 3Dx800 sensors) provide many of the features found on other 3D Sensors.1 Sourcefire 3D System Administrator Guide 107 .9.Using the Defense Center Management Concepts Chapter 4 See the Supported Features for Intrusion Agents table for more information. 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 . 3D Sensor 5800. Version 4. because these models do not have a web interface and because configuration and event data cannot be stored on the sensors.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.

1 Sourcefire 3D System Administrator Guide 108 .9. 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.Using the Defense Center Management Concepts Chapter 4 certain features cannot be used with these sensors. See the Supported Features for 3Dx800 Sensors table for more information.

See the Supported Features for RNA Software for Red Hat Linux table for more information.9.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. 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. not all of the features function in the same manner.1 Sourcefire 3D System Administrator Guide 109 .

However.9. because the Crossbeam sensors do not have a user interface and because configuration and event data cannot be stored on Version 4. See the Supported Features for RNA on Crossbeam table for more information. 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.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. However.1 Sourcefire 3D System Administrator Guide 110 . not all of the features function in the same manner.

Audit events are stored locally Version 4. certain features cannot be used with this software. Backing Up a Sensor If you are storing event data on your sensor in addition to sending it to the Defense Center.1 Sourcefire 3D System Administrator Guide 111 . you can also perform other sensor-related tasks on the Defense Center.Using the Defense Center Management Concepts Chapter 4 the sensors. 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. Running Remote Reports You can create a report profile on the Defense Center and run it remotely using the data on a managed sensor.9. See Performing Sensor Backup with the Defense Center on page 419 for more information. See the Supported Features for IPS on Crossbeam table for more information. This is particularly useful if you want to generate a report for the audit events on a managed sensor. you can use the Defense Center’s web interface to back up those events from the sensor.

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

SSL-encrypted communication channel between the Defense Center and the sensor. As the sensor evaluates the traffic. you must use a unique NAT ID when adding the New York 3D Sensor to the Defense Center. you set up a two-way. You can create the following policies on your Defense Center and apply them to managed sensors: • • • health policies system policies RUA policies Version 4. Each NAT ID has to be unique among all NAT IDs used to register sensors on the Defense Center. it generates events and sends them to the Defense Center using the same channel. However. 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. 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.9.

See Managing a 3Dx800 Sensor on page 125 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. Confirm that you are receiving the events generated by your sensors. (Deleting Sensors on page 121 explains how to remove a sensor from the Defense Center. See Using Intrusion Policies in the Analyst Guide for more information. • IPS detection engines require an intrusion policy that determines which types of attacks 3D Sensor with IPS detect.) 2. Version 4.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. See What is an RNA Detection Policy? in the Analyst Guide for more information. You can also create and apply system policies. and the Intrusion Agents are slightly different. 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. Note that the system policy applied to the Defense Center controls the types of RNA events that are logged to the database. See Adding Sensors to the Defense Center on page 117 for more information. 1. RNA detection engines require an RNA detection policy. which control certain appliance-level features on your sensors. TIP! The process for setting up communications between the Defense Center and other products such as the Crossbeam-based software sensors. This is a two-step process. See Managing System Policies on page 320 for more information. Refer to the configuration guides for those products for more information.1 Sourcefire 3D System Administrator Guide 114 . RNA Software for Red Hat Linux.9. Begin by setting up a communications channel between the two appliances. 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. which controls the networks that 3D Sensors with RNA monitor. • • • 3. See Configuring Health Policies on page 489 for more information.

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

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

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

1 Sourcefire 3D System Administrator Guide 118 .9. and Unique NAT ID used on the 3D Sensor with Registration Key and Unique NAT ID used on the Defense Center. Version 4. The Information page appears. Registration Key .for a unique alphanumeric ID. Management Host and Registration Key used on both appliances Registration Key and Unique NAT ID used on the 3D Sensor with Host. To add a sensor to a Defense Center: Access: Admin 1. or on both the Defense Center and the sensor • • TIP! Set up the managed appliance first. Log into the web interface of the sensor you want to add. Select Operations > System Settings. and Unique NAT ID used on the Defense Center.Using the Defense Center Working with Sensors Chapter 4 To add a sensor. Unique NAT ID . Valid combinations include: • • • IMPORTANT! The Management Host or Host field (hostname or IP address) must be used on at least one of the appliances.for registration key.for the hostname or IP address. 2. 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. Registration Key. Three fields are provided for setting up communications between appliances: • • • Management Host . Registration Key. You must begin the procedure for setting up the management relationship between a Defense Center and a sensor on the sensor. Refer to Working in NAT Environments on page 112 for more information. Management Host.

6. The Add Remote Management page appears. Click Add Manager. In the Management Host field. 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. type a unique alphanumeric ID that you want to use to identify the sensor. Click Remote Management. type the IP address or the host name of the Defense Center that you want to use to manage the sensor. After the sensor confirms communication with the Defense Center. In the Registration Key field.9. 4. Version 4. In that case. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. Optionally. the Pending Registration status appears. 7. 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. 8. The Remote Management page appears. in the Unique NAT ID field. 5.1 Sourcefire 3D System Administrator Guide 119 .Using the Defense Center Working with Sensors Chapter 4 3. Click Save.

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

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

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

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

1 Sourcefire 3D System Administrator Guide 124 . The Add New Sensor page appears. type a unique ID that you want to use to identify the sensor. the Pending Registration status appears. 11. Click Save. 10.Using the Defense Center Working with Sensors Chapter 4 4. Log into the Defense Center’s web interface using a user account with Admin access. packet data is not retained.9. type the same one-time use registration key that you used in step 3. in the Unique NAT ID field. After the sensor confirms communication with the Defense Center. Click New Sensor. In the Registration Key field. 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. The Sensors page appears. 5. Version 4. By default. 7. 6. 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. 9. Packet data is often important for forensic analysis. and select Operations > Sensors. 8. You can prevent packet data from leaving a sensor by checking the Prohibit Packet Transfer to the Defense Center check box. Optionally. data is stored only on the Defense Center and not on the sensor. If you elect to prohibit sending packets and you do not store events on the 3D Sensor. 12. If you used a unique NAT ID in step 4.

1 Sourcefire 3D System Administrator Guide 125 . Contact technical support for more information. For more information about groups. In some high availability deployments where network address translation is used. sensor. you may need to use the Add Manager feature a second time to add the secondary Defense Center. see Managing Sensor Groups on page 131. 14.Using the Defense Center Working with Sensors Chapter 4 13. This procedure assumes that you have completed the setup steps described in the sensor’s Installation Guide. The CLI prompt appears. To add the sensor to a group.9. Click Add. The sensor is added to the Defense Center. 3D Sensor 5800. Managing a 3Dx800 Sensor Requires: DC + 3D Sensor Because the Sourcefire 3D Sensor 3800. and 3D Sensor 9800 (usually called the 3Dx800 sensors) do not have their own web interfaces. select the group from the Add to Group list.domain [admin] Version 4. To manage a 3Dx800 sensor with a Defense Center: Access: Admin 1. It can take up to two minutes for the Defense Center to verify the sensor’s heartbeat and establish communication. Log into the 3D Sensor using the admin account. You can view the sensor’s status on the Sensors page (Operations > Sensors). 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.

Using the Defense Center Working with Sensors Chapter 4 2. reg_key is a unique single-use alphanumeric registration key. Enter the following at the CLI prompt: [admin] configure sensor 3. 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. The NAT ID together with the registration key must uniquely identify the communications channel between the sensor and the Defense Center.9. 5. If you changed the management port on the Defense Center. 4. 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. In either case.1 Sourcefire 3D System Administrator Guide 126 . the sensor may be managed by another Defense Center. Use the following command to determine whether remote management is already enabled: [admin:sensor] show management If management is already enabled. • If you are deploying your sensor in a network that does use network address translation. a message appears indicating that remote management is enabled. Version 4. 6. and nat_id is a unique alphanumeric string. 8. Use the following command to exit the CLI and return to the login prompt: [admin:sensor] exit 7. 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 Sensors page appears. 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. Using a user account with Admin access. 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. Select Operations > Sensors. log into the web interface of the Defense Center where you want to add the sensor. The IP address and registration key pair must uniquely identify the communications channel between the sensor and the Defense Center.

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

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

• If your sensor is in a network that does use network address translation. Enter the following command to disable remote management: [admin:sensor] set management disable Remote management is disabled. reg_key is a unique single-use alphanumeric registration key. In the Host field. Communications are restarted and the sensor is re-added to the Defense Center. re-add the sensor by clicking New Sensor.1 Sourcefire 3D System Administrator Guide 129 . 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. The NAT ID together with the registration key must uniquely identify the communications channel between the sensor and the Defense Center. Click Add. 8. The Sensors page appears. In either case. 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. and nat_id is a unique alphanumeric string. Version 4.9. Use one of the following commands to enable remote management. 11.Using the Defense Center Working with Sensors Chapter 4 5. 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. Enter the following command to exit the CLI and return to the login prompt: [admin:sensor] exit 9. 10. 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. On the Defense Center’s Sensors page. 7. remote management is enabled again.

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

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

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

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

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

Sensor Information Field Name Description The assigned name for the managed sensor. see Blacklisting a Health Policy Module on page 537. The IPv4 address of the managed sensor. For more information. 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. The version of the operating system currently running on the managed sensor. Enable this check box to store event data on the Defense Center. the fields are slightly different. Enable this check box to prevent the managed sensor from sending packet data with the events. Note that is the name of the sensor in the Defense Center web interface. see Managing Communication on a Managed Sensor on page 138. For more information. • • 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. not the hostname. The version of the software currently installed on the managed sensor. When you view the Information page for a managed Defense Center from the Master Defense Center’s web interface. The model name for the managed sensor. but not the managed sensor. The version level of the vulnerability database currently loaded on the managed sensor. manage time settings 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. Clear this check box to store event data on both appliances. The operating system currently running on the managed sensor. See Editing Settings for a Managed Defense Center on page 175.1 Sourcefire 3D System Administrator Guide 135 . Clear this check box to allow packet data to be stored on the DC with events. blacklist individual health policy modules on the managed sensor.9. For more information. see Setting the Time on a Managed Sensor on page 139.

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

The Information page for that sensor appears. Stopping and Restarting a Managed Sensor Requires: DC For 3D Sensors.Using the Defense Center Editing a Managed Sensor’s System Settings Chapter 4 2. 4. RNA Software for Red Hat Linux. See the Sensor Information table on page 135 for a description of each field. 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 . 3.9. 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. Click Edit next to the name of the sensor whose system settings you want to edit. You must use the command line interface (CLI) to manage processes on Crossbeam-based software sensors. and Intrusion Agents. Change the sensor’s attributes as needed. Version 4. Click Save.

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

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

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

see the Cluster Interconnect table. shared detection configuration. For information about the connections between the master and slave 3D9900 sensors. interface set. and data from a clustered pair. they act like two separate sensors with a single. 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. and local management is blocked on the shared portion of the clustered pair. Cluster Interconnect Master Interface ethb2 RX ethb2 TX Slave Interface ethb0 TX ethb0 RX Version 4. The following diagram shows interfaces on the master and slave sensors.Using the Defense Center Managing a Clustered Pair Chapter 4 After you establish the relationship between the two sensors.9.1 Sourcefire 3D System Administrator Guide 141 .

you must edit and reapply your detection policy after you establish clustering. You determine the master/slave designation by the way you cable the pair. you must: • • • decide which unit will be the master have SEU 2.8.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. IMPORTANT! You cannot connect the slave’s ethb2 and ethb3 pair when you establish the clustered pairing. Before you begin. you cannot change which sensor is the master or slave unless you break and reestablish the relationship using the Defense Center.1 Sourcefire 3D System Administrator Guide 142 . see the Sourcefire 3D Sensor Installation Guide. After you establish the relationship. For more information about cabling. 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. Version 4.9. the detection engines and interface set are combined on the two sensors. After you establish the master/slave relationship.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. For more information. Connect the master’s ethb2 and ethb3 pair to the slave’s ethb0 and ethb1 pair as shown in the Cluster Interconnect table. 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.

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

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

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

• • RNA detection policies RNA custom service detectors Version 4. RNA. make sure you register all intrusion agents to the primary Defense Center. see Health and System Policies on page 147 feature license operation in a high availability pair. because both Defense Centers must have an admin account. such as the sensor’s host name. make sure you remove duplicate user accounts from one of the Defense Centers. 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.Using the Defense Center Configuring High Availability Chapter 4 For more information on: • • • • sensor attributes and user information shared in a high availability pair. • • • • • • • • • • custom dashboards authentication objects for Sourcefire 3D System user accounts custom workflows custom tables sensor attributes. 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. you must make sure that the admin account uses the same password on both Defense Centers. Also. and the group in which the sensor resides intrusion. where events generated by the sensor are stored.9.1 Sourcefire 3D System Administrator Guide 146 . see Sensor Configurations and User Information on page 146 health and system policies shared in a high availability pair. if you have any user accounts with the same name on both Defense Centers.

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

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

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

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

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

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

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

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

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

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

The settings on the Filter Configuration page determine which events are forwarded from the Defense Center to the Master 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. 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. • Understanding Event Aggregation on page 157 explains which types of events you can send from your Master Defense Centers to your Master Defense Center.9.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. 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. although most deployments will use the same configuration across the enterprise. When you apply intrusion policies from a Master Defense Center. In this way. You can also choose whether to include the packet data collected with the intrusion events. The following sections explain more about using a Master Defense Center in your Sourcefire 3D System deployment. You can set up a different configuration for each Defense Center. • • • • 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.1 Sourcefire 3D System Administrator Guide 157 . You can configure a Defense Center to send intrusion events based on their flag. Understanding Global Policy Management on page 161 explains which policies you can send from your Master Defense Center to 3D Sensors and Defense Centers. 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. the Sourcefire 3D System checks the SEU on the managing Defense Center. it updates the managing Defense Center’s SEU. Adding and Deleting Defense Centers on page 164 explains how to configure a Defense Center to communicate with a Master Defense Center. If it finds an older SEU.

RNA events. along with any related packets. Events and Packet Data . If your 3D Sensors are deployed inline and you are using intrusion rules set to Drop and Generate Events. you may want to limit the intrusion events on the Master Defense Center to only those with the greatest impact.1 Sourcefire 3D System Administrator Guide 158 . If you do not deploy 3D Sensors with RNA on your network.Intrusion events are not forwarded to the Master Defense Center. Packet decoders. then intrusion events are limited to gray impact flags to indicate unknown impact.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. flow data. When you use the Filter Configuration page to specify which events are forwarded to the Master Defense Center.9. Events Only . 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. For example. any packets captured for the event are not sent. you can choose one of the following options: • • Do Not Send . are forwarded to the Master Defense Center. the red impact flag. however. and intrusion rules are all able to generate intrusion events. The conditions that can trigger a compliance rule include intrusion events. 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. that is. and anomalous network traffic. For example. preprocessors. 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. IMPORTANT! You must deploy both RNA and IPS on your network to generate intrusion events with meaningful impact flags. Version 4.The intrusion events specified in the Flags section. • You can use the Flags section of the Filter Configuration page to forward only the intrusion events that are important to your analysis. you can greatly reduce the number of events sent from a Defense Center by excluding events with the blue or gray impact flags.

users. However. there are certain limitations that you should take into consideration when you design your Master Defense Center deployment. white list events. hosts. health events. remediation status. Master Defense Center and Defense Center Functional Comparison Function License provisions Master Defense Center provides product license Defense Center provides product license. and NetFlow. you can choose to send or not send compliance events. network interfaces. Analysis and reporting search Version 4. 3D Sensor configuration allows you to configure detection engines allows you to search for intrusion events. SEU import log. RNA and RUA feature licenses allows you to configure detection engines. The Master Defense Center and Defense Center Functional Comparison table compares and contrasts Defense Center and Master Defense Center functional areas. white list events. scan results. health events. audit log. and RUA events.9. compliance events. white list violations. RNA events. interface sets. allows you search for intrusion events.1 Sourcefire 3D System Administrator Guide 159 . client applications. host attributes. audit log. SEU import log. vulnerabilities. services.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. compliance events. flow data.

you can gain insight into RNA-detected activity across your enterprise. because you can forward compliance events and white list events from your managed Defense Centers to your Master Defense Center. Event Rate The event rate limit for the Master Defense Center is the same rate limit on Defense Centers. You can also limit the amount of data transferred between a Defense Center and its Master Defense Center by sending only intrusion event data. To take advantage of this.9. For example. the Master Defense Center does not build a network map or host data for the hosts on your network. Version 4. In addition. and not sending the packet data. 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 might want to adjust the filter to send only intrusion events with red impact flags. Intrusion Agents Intrusion events generated by intrusion agents are not forwarded to the Master Defense Center. 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.1 Sourcefire 3D System Administrator Guide 160 . in cases where the intrusion event rate is high. you must adjust the event filter on the Master Defense Center so that only the most important events are forwarded from the Defense Centers. However. This means that if your Defense Centers are accepting events from their 3D Sensors up to the rate limit. 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.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.

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

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. edit. • Using RNA Detection Policies on a Master Defense Center Requires: MDC You can create. 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 for brief descriptions of those modules that are used. 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 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. export. and apply default health policies to the Master Defense Center and to connected Defense Centers. delete. and apply RNA detection policies from a Master Defense Center. delete. This section also explains how to configure rules in inline intrusion policies so that they drop malicious packets. Refer to the following.9. 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. Note that SEUs can also contain new and updated decoders and preprocessors.1 Sourcefire 3D System Administrator Guide 162 .

they are updated. The Defense Center and Master Defense Center do not handle these policies in the same manner. delete. and apply intrusion detection and prevention policies from a Master Defense Center. You cannot apply a non-filtered policy from a Defense Center then add filters to it from a managing Master Defense Center. 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. RNA Detection Policies RNA analysis and reporting functions such as using the network map. the Sourcefire 3D System checks for any older SEUs on Defense Center(s) managing those detection engines. However. TIP! Before applying a filtered policy. if your Version 4. 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. edit.1 Sourcefire 3D System Administrator Guide 163 . listing RNA hosts and events.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. a warning message with a check box appears. When you apply an intrusion policy to a 3D Sensor’s detection engines from a Master Defense Center. and listing client applications and vulnerabilities are performed on Defense Centers and not on Master Defense Centers. RUA detection. RNA detection. The Sourcefire 3D System bases intrusion policies on SEUs residing on the appliance where the policy is built. After you acknowledge the message by clicking its check box.9. Therefore. export. and health policies. you must apply a non-filtered policy to the detection engine from the same Defense Center or Master Defense Center. If it finds SEUs older than those on the Master Defense Center. the Apply button activates.

Default IPS. For a listing of the health policy modules that apply to Master Defense Centers. only the generic Default Health Policy is available for editing and application to appliances.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 deployment includes RNA. Health Policies The Master Defense Center monitors its health and the health of connected Defense Centers. Master Defense Centers apply health policies only to Master Defense Centers and Defense Centers. System Policies System policies are applied only to Master Defense Centers and Defense Centers from a Master Defense Center. For details about editing appropriate health policies. For a listing of the health policy modules that apply to Defense Centers. 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. it evaluates which events. RUA Detection Policies There are currently no Real-Time User Awareness functions on a Master Defense Center. • • • 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. Currently. based on filter configuration. The Defense Center uses this channel to send events to the Master Defense Center. see the Enabled MDC Health Modules . RUA functions are available only on properly licensed Defense Centers.1 Sourcefire 3D System Administrator Guide 164 . it should send to the Master Defense Center using the same channel. As the Defense Center receives events from its sensors. see the Enabled Defense Center Health Modules . Default IPS (3Dx800 only). 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. Default 3D Sensor. and Default RNA Health Policies are not used on the Master Defense Center.Default Health Policy table on page 494. Adding and Deleting Defense Centers Requires: MDC + DC When you manage a Defense Center with your Master Defense Center. see Editing Health Policies on page 530.Default Health Policy table on page 493. SSL -encrypted communication channel between the appliances.9.

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

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

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

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

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

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

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

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

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

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

The Information page for a managed Defense Center includes the fields described in the Defense Center Information table. The Vulnerability Database version on the managed Defense Center. then click Edit next to the Defense Center. Defense Center Information Field Name Description The assigned name for the Defense Center. not the hostname. 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. See the following sections for more information. The operating system currently running on the managed Defense Center. Product Model Software Version Operating System Operating System Version VDB Version IP Address Version 4.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. select Appliances from the Operations menu.1 Sourcefire 3D System Administrator Guide 175 . • • • • • 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. Note that this is the name of the Defense Center in the Master Defense Center web interface.9. The model name for the managed Defense Center. The IP address of the managed Defense Center. The version of the software currently installed on the managed Defense Center.

2. You can click Refresh to update the Status icon and its accompanying pop-up message. If you hover your cursor over the icon.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. minutes.1 Sourcefire 3D System Administrator Guide 176 . a pop-up message indicates how long it has been (in hours. See the Impact Flags table in the Analyst Guide for an explanation of what each impact Version 4. Change the Defense Center’s attributes as needed.9. To edit a managed Defense Center’s settings: Access: Admin 1. If you want to send intrusion events (with or without packet data). Click Save. and seconds) since the Defense Center communicated with the Master Defense Center. The updated Defense Center attributes are saved. Model Number Current Group The model number for the Defense Center. Your options are to send intrusion events. 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. and compliance events. you can also specify which intrusion events are sent based on their impact flag. 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. intrusion events and related packet data. if any. The group that the Defense Center belongs to. This number can be important for troubleshooting.

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

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

An HA pair is listed as a group with the name of the active Defense Center. The Appliances page appears. 2. Click Edit next to the appropriate Defense Center. 3. The high availability page appears with the paired Defense Centers. The System Settings page for that Defense Center appears.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. TIP! High availability Defense Center pairs are automatically listed as an appliance group. Version 4.1 Sourcefire 3D System Administrator Guide 179 . register all Intrusion Agents to the primary Defense Center. 4. TIP! A light bulb icon shows which of the high availability paired Defense Centers is currently active. TIP! When using Intrusion Agents registered to Defense Centers configured for high availability and managed by a Master Defense Center. Select Operations > Appliances. Click High Availability. The redundant Defense Center is activated. Click Activate to activate the redundant Defense Center. you can activate Defense Center High Availability from a Master Defense Center.9. 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. To activate a redundant Defense Center: Access: Admin 1.

9. In the Group Name field. On the Master Defense Center. Moving an appliance to a new group does not change any of its policies or configurations. type the name of the group you want to create. Click Save. 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. The group is added. 6. The Appliances page appears. 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 appliances are added to the group and the Appliances page appears again. The Create Appliance Group page appears.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. 7. 3. The Appliance Group Edit page appears. return to the Appliances page (Operations > Appliances) and click Edit next to the name of the group. Editing Appliance Groups Requires: MDC You can change the set of appliances that reside in any appliance group. Click Create New Appliance Group. Deleting Appliance Groups on page 181 explains how to delete a Defense Center group. Editing Appliance Groups on page 180 explains how to modify the list of Defense Centers in a Defense Center group. Version 4. To add appliances to the group.1 Sourcefire 3D System Administrator Guide 180 . 2. select Operations > Appliances. TIP! You must remove an appliance from its current group before you can add it to a new group. 4. 5. To create an appliance group and add appliances to it: Access: Admin 1.

• • • • 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. The appliances group is removed from the Master Defense Center. Select Operations > Appliances.Using the Master Defense Center Editing Master Defense Center System Settings Chapter 5 To edit an appliance group: Access: Admin 1. 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. the Master Defense Center system settings are the same as those of a Defense Center.1 Sourcefire 3D System Administrator Guide 181 . select it from the list in the group you are editing and click the arrow pointing to the Available Appliances list. Click Edit next to the Appliance group you want to edit. To delete an appliance group: Access: Admin 1. the appliances are moved to Ungrouped on the Appliances page. Deleting Appliance Groups Requires: MDC If you delete a group that contains appliances. select it from the Available Appliances list and click the arrow pointing toward the group you are editing. 2. Select the appliance you want to move and click the arrow to add or remove it from the group.9. Editing Master Defense Center System Settings Requires: MDC With a few exceptions. select Operations > Appliances. To remove an appliance from a group. 3. • • To add an appliance to the group. They are not deleted from the Master Defense Center. Click Save. On the Master Defense Center. The Appliances page appears. The Appliance Group Edit page appears. The Appliances page appears. Click Delete next to the group you want to delete. 4. 2.

The License page appears.9. You can: • • • shut down the appliance reboot the appliance restart the appliance Version 4. WARNING! The name must be made up of a combination of alphanumeric characters and should not be made up of numeric characters only. Configuring Network Settings Requires: MDC The network settings are identical to those of the Defense Center. Click License. Viewing a Master Defense Center License Requires: MDC Unlike a Defense Center. see Defense Center Information on page 175. see Configuring Network Settings on page 377. To view information about the Master Defense Center license: Access: Admin 1. a Master Defense Center cannot manage the licenses of Defense Centers or 3D Sensors. 2. Shutting Down and Restarting the System Requires: MDC You have several options for controlling the processes on your Master Defense Center. 2. The updated Master Defense Center attributes are saved. For information on configuring the Master Defense Center network settings.1 Sourcefire 3D System Administrator Guide 182 . Select Operations > System Settings. 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. Click Save. To edit a Master Defense Center’s settings: Access: Admin 1. The Information page appears.

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

see Synchronizing Time on page 354. Blacklisting Health Policies Requires: MDC You can blacklist health policy modules when required. if DNS is enabled. see Blacklisting a Health Policy Module on page 537. For more information about setting system time.9. type the IP address of the NTP server or. select Manually in the System Settings. To receive time through NTP from a different server. WARNING! If the appliance is rebooted and your DHCP server sets an NTP server record different than the one you specify here. Version 4. in the text box. you should configure your DHCP server to set the same NTP server. To avoid this situation.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 fully qualified host and domain name. the DHCP-provided NTP server will be used instead. 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.1 Sourcefire 3D System Administrator Guide 184 . select Via NTP Server from and.

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

1 Sourcefire 3D System Administrator Guide 186 . This section also describes how default detection engines are configured. The Available Detection Engines page appears. You can sort the available detection engines by group. detection engine type. and delete detection engines. The figure below shows the Defense Center version of the page. policy. Using Interface Sets on page 207 describes how to create interface sets and how to use them with detection engines. 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. or interface set type.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. To list the available detection engines: Access: Admin Select Operations > Configuration > Detection Engines > Detection Engines. including some of the limitations based on the sensor model. • • • • • • • 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. Managing Detection Engines on page 193 explains how to create. Using Clustered 3D Sensors on page 227 explains how to use detection engines and interface sets in a clustered 3D9900 sensor pairing.9. Using Interface Set Groups on page 223 describes how to create and use interface sets groups. 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. Version 4. edit. sensor. Using Detection Engine Groups on page 197 explains how to create and use detection engine groups.

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

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

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

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 Combination Restrictions column indicates the permitted combinations of detection resources that you can allocate to detection engines on the same sensor. The Maximum column indicates the total number of detection resources available on the sensor. RNA and RUA. • 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.9. 3D Sensors can run combinations of IPS.1 Sourcefire 3D System Administrator Guide 190 . 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. It also indicates the maximum number of detection resources you can assign a single detection engine.

Understanding Default Detection Engines Requires: DC or 3D Sensor When you install a new 3D Sensor.1 Sourcefire 3D System Administrator Guide 191 . you have several deployment options for 3D Sensor Software. Refer to the Sourcefire 3D Sensor Software for X-Series Installation Guide for information on deployment scenarios. As with other 3D Sensors. and detection resources available on Crossbeam System hardware. Version 4. Crossbeam-based Software Sensor Considerations Depending upon the capabilities of your X-Series and the products you are licensed to use.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. the maximum number of detection engines that you can create is equal to the number of available detection resources. The number of detection resource depends on the Crossbeam System hardware. you can use initial interface sets and default detection engines to quickly begin evaluating network traffic. current Crossbeam System hardware and software support.9. After initial installation can modify interface sets and detection engines. then distribute the detection engines and detection resources across all operative interfaces on the sensor. you can reduce latency by distributing your network traffic across all available interfaces on the sensor. Consider how your network is configured and how you want to deploy the Sourcefire 3D System within it.

However. on some of the older models.1 Sourcefire 3D System Administrator Guide 192 . 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. Version 4.9. and you have deployed it in a high-bandwidth environment where the traffic load is likely to reach the design limits of the appliance. the detection engine may not provide optimum performance. IMPORTANT! For the 3D3000 on the IBM xSeries 346 appliance. 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. Choose from these initial interface sets based on how you deployed the sensor. Select Passive Mode if the sensing interfaces are not cabled inline. typically you pair adjacent interfaces. less the management interface. the second on-board interface cannot support the same high-performance standards as the interfaces on the network interface cards. If your appliance has one of these extra interfaces. that is automatically included in the default detection engine. note that the default detection engine does not include the second on-board interface. Sourcefire recommends that you remove the second on-board interface from the detection engine for improved performance. If you want to change either the number of detection resources or the interfaces assigned to the default detection engine. see Editing a Detection Engine on page 194. usually near the management interface.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. 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. If you modify the default detection engine to include it. Depending on the 3D Sensor. With this configuration. Select Inline with Fail-Open Mode if you cabled the sensing interfaces inline on your network as an IPS. Passive that builds a single passive interface set for all 3D Sensor interfaces. less the management interface. Second On-Board Interface Some Sourcefire sensors have a second on-board interface. for example. the default that builds paired fail-open interface sets on all 3D Sensor interfaces.

edit. punctuation. and delete detection engines. enter a name and description for the new detection engine. when they are available on your 3D Sensor. The figure below shows the Defense Center version of the page. • • • 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. You can use interface sets that include multiple inline interface pairs. The Create Detection Engine page appears.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. You can use alphanumeric characters. and spaces. 2. Click Create Detection Engine.9. The Detection Engines page appears. In the Name and Description fields. Select Operations > Configuration > Detection Engines > Detection Engines. 3. The following sections explain how to create.1 Sourcefire 3D System Administrator Guide 193 . Version 4. To create a detection engine: Access: Admin 1.

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

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

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

Select Operations > Configuration > Detection Engines > Detection Engines. however. For information on modifying compliance rules. you should first delete (or modify) the constraint in all rules in which it is used. 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. Version 4. The Detection Engines page appears. see Modifying a Rule in the Analyst Guide.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. confirm that you want to delete the detection engine. a record of the detection engine is retained so that events generated by that detection engine are viewable. Using Detection Engine Groups Requires: DC/MDC or 3D Sensor You can use detection engine groups to combine similar detection engines. To create a detection engine group: 1. These groups make it easier to apply policies to detection engines that have similar purposes. The Detection Engines page appears. you should not delete a detection engine that is used as a constraint in one or more compliance rules. Also. At the prompt. To delete a detection engine: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 197 . The detection engine is deleted. WARNING! Do not delete a detection engine that is in use. 3.9. Click Delete next to the detection engine you want to delete. 2. Select Operations > Configuration > Detection Engines > Detection Engines.

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

The Detection Engines page appears.0/16 In the detection engine named DE_DMZ: HOME_NET = 10. 10. 2. When you apply an intrusion policy to that detection engine. hosts in your network’s DMZ in the range 10.30.30. you can use detection engine-specific variable values to tailor your detection capabilities to more closely match your infrastructure.0.90.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. Click Delete next to the name of the detection engine group. In the system default variable used in the intrusion policy: HOME_NET = 10.10. hosts in your accounting department in the address range 10.90.10. Select Operations > Configuration > Detection Engines > Detection Engines. they are not deleted. 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. if you have created your detection engines so that one detection engine monitors one class of hosts (in this example. For information on policy-specific variables. which includes a mixed address space. You can define HOME_NET in your system default variable to encompass your internal address range (for example. 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. The detection engine group is deleted.10. However. see Creating New Policy-Specific Variables in the Analyst Guide. you can use the system default Version 4.0/24).0/24 If you later create another detection engine that monitors the rest of your network.0. To delete a detection engine group: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 199 . any detection engines in the group are automatically ungrouped.0/24) and another monitors a different class (for example.0/24 In the detection engine named DE_ACCT: HOME_NET = 10. 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. For example.0/16).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.10. which are specific to the policy in which they are created.10.9.

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.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.1 Sourcefire 3D System Administrator Guide 200 . You can view the explicit detection engine-specific value you configured in the list of variables for the detection engine within each policy. IMPORTANT! You cannot use variables with RNA detection engines. the definition reverts to the definition in the intrusion policy the next time you apply the policy. 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. you can modify the variable in the intrusion policies and detection engines where it is added automatically to give it a specific definition. 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. For an explanation see Using Variables within Detection Engines on page 199. Configuration details in this section relate to the detection engine Variable List page. 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. See Creating New Variables in the Analyst Guide and Modifying Variables in the Analyst Guide for more information. For more information. Version 4. or on the detection engine Variable List page for the detection engine. 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. When they exist. see Creating New Variables in the Analyst Guide. and on the Variable list page for all other detection engines where it is listed with the value set to Policy Defined. For configuration details related to setting detection engine-specific variables within an intrusion policy.9. You can also create new variables for use only within the context of the detection engine. a detection engine-specific variable value takes precedence over a policy-specific or system default value for the same variable. Optionally. If you disable a variable defined on the Variable List page by resetting the variable.

Click Variables next to the detection engine where you want to define a variable value. as described in Applying an Intrusion Policy in the Analyst Guide.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. 2. 3. 4. Enter a value for the variable and click Save. The Detection Engines page appears. See Creating New Variables in the Analyst Guide for information about variable syntax. The variable takes effect the next time you apply an intrusion policy to the detection engine. The value for each of the variables defaults to the value within the intrusion policy that is applied to the detection engine. The Variable Binding page appears. Click Edit next to the variable you want to define. The Variable List page appears again and shows the new value for the variable. Version 4. Select Operations > Configuration > Detection Engines > Detection Engines. The Variable List page appears.9.1 Sourcefire 3D System Administrator Guide 201 .

For an explanation see Using Variables within Detection Engines on page 199. Click Variables next to the detection engine where you want to define a variable value. The Variable page appears. The Detection Engines page appears. select IP Port. • • • See Defining IP Addresses in Variables and Rules in the Analyst Guide for more information if you are defining a IP address-based variable. From the Variable Type drop-down list. In the Variable Name field. Select Operations > Configuration > Detection Engines > Detection Engines. 4. . 5. 2. See Defining Ports in Variables and Rules in the Analyst Guide for more information if you are defining a port-based variable. To create a new variable for a detection engine: Access: Admin 1. The Variable List page appears. 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.1 Sourcefire 3D System Administrator Guide 202 . or Custom.9.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. you can associate detection engine-specific variable definitions with the policy. Click Add Variable. Version 4. enter a name for the variable. 3.

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

see Understanding Custom Variables in the Analyst Guide. 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. Click Variables next to the detection engine where you want to delete or reset a variable value.9. You can set an explicit detection engine value for the predefined SNORT_BPF custom system variable. Version 4. You can add a new USER_CONF detection engine variable using the reserved name USER_CONF . or by creating a variable using a specific reserved name. The variable is deleted from the detection engine the next time you apply an intrusion policy to the detection engine. • To delete a locally created variable. For more information. 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. The Variable List page appears. 3. You create a detection engine-specific custom variable by setting an explicit value for a reserved predefined system variable. click Delete next to the name of the variable. You then define the variable value with a set of instructions appropriate to the function the variable provides.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 2.1 Sourcefire 3D System Administrator Guide 204 . The variable is reset and Policy Defined appears in the Value column. click Reset next to the name of the variable.

a portion of the traffic that the 3D Sensor sees is directed to each detection resource for processing. Create an IPS portscan-only detection engine and assign one detection resource to it. Version 4. 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. Internal logic on the sensor ensures that packets belonging to the same session are directed to the same resource for analysis. inline. However. 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. see Assigning Values to System Default Variables in Detection Engines on page 200. Engines on page 202. 1. Using the Defense Center’s web interface.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. which is a requirement for the portscan preprocessor. Multiple detection engines will use this interface set. or inline with fail open depending on how your sensor is deployed.9. Depending on the traffic mix on your network. Make sure you use the interface set that you created in step 1. 3. the sensor can process more packets with greater efficiency. To overcome this issue.1 Sourcefire 3D System Administrator Guide 205 . 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. The interface set can be passive. 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. you may need to adjust the number of resources in the multi-resource detection engine. 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 . 2. 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. In this way. create an interface set that includes the network interfaces you want to use on the sensor. One downside to using multiple detection resources is that no single resource sees all the traffic on a network segment.

6. Note that all rules are disabled on the Rules page. See Enabling and Disabling Advanced IPS Features in the Analyst Guide for more information. You should not change the default settings for Checksum Verification or Packet Decoding (under Transport/Network Layer Preprocessors). Ensure that the DCE/RPC Configuration preprocessor. items listed under Performance Statistics. Ensure that OPSEC Configuration (under External Responses) is disabled. Create and apply an intrusion policy for the multi-resource detection engine. the SMTP Configuration preprocessor (under Application Layer Preprocessors). 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. • • • • • • IMPORTANT! Note that when portscan detection is enabled. 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. 5. or Rule Processing Configuration. Version 4. Also. 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. make sure you disable portscan detection in this policy. See Detecting Portscans in the Analyst Guide for more information. Make sure portscan rules are enabled for the types of portscans you configure.1 Sourcefire 3D System Administrator Guide 206 . the HTTP Configuration preprocessor. 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. See Selecting the Base Policy in the Analyst Guide for more information. See the Portscan Detection SIDs (GID:122) table in the Analyst Guide for more information. Enable Portscan Detection and configure it for your network environment.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 4. Create and apply an intrusion policy to the portscan-only detection engine. Review the resulting intrusion events to ensure that you are receiving the events you expect. Working with Layers.9. Make sure you match the type of intrusion policy to the type of interface set that you created in step 1.

The Virtual 3D Sensor supports only passive mode operation. To list the available interface sets: Access: Admin Select Operations > Configuration > Detection Engines > Interface Sets. • • • • • • • Version 4. sensor. you can set up any of your 3D Sensor interfaces in passive. set type. 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.1 Sourcefire 3D System Administrator Guide 207 . Some installations require that the link state be propagated and most sensor interfaces provide that option. 3D Sensors deployed in networks that are highly sensitive to latency can use the automatic application bypass option. or PEP policy. Only 3D9900 sensors provide a fail-safe option that works with inline interface sets.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. inline. On selected sensors you can set interfaces to tap mode.9. • With the exception of the Virtual 3D Sensor. or inline with fail-open mode. You can sort the available interface sets by group. Sensors with Gigabit Ethernet interfaces can employ jumbo frames. You can also set interfaces on most sensors in transparent inline mode. Only 3D9900 sensors provide the PEP feature. For more information on the PEP feature. see Using PEP to Manage Traffic in the Analyst Guide.

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 .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.9.

an inline with fail open 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. If you choose the Inline or Inline with Fail Open option. However. an inline interface set on a 3D3800 or 3D5800 sensor can include up to four interface pairs. an inline interface set can include any two interfaces.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 Types of Interface Sets When you create an interface set. 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. • Inline with Fail Open For most sensors.1 Sourcefire 3D System Administrator Guide 209 . Version 4. if the power fails or the Snort process halts. IMPORTANT! If you include an on-board sensing interface (instead of. the Transparent Inline Mode option is enabled by default. interfaces on the network cards). then apply different policies to the detection engines. However. except for the 3D500 and the Virtual 3D Sensor. • Inline For most sensors. an inline with fail open interface set must include exactly one interface pair. It is not available on the 3D500 and available but not a default configuration on the Virtual 3D Sensor. Transparent Inline Mode Transparent inline mode is a feature for inline interface sets and is not available for Passive interface sets.9. and an inline interface set on a 3D9800 sensor can include up to the total number of interface pairs on the sensor. one for an IPS and the other for RNA. you can choose one of three types: • Passive A passive interface set can encompass any number of the available sensing interfaces on a sensor. you could create a single passive interface set and create two detection engines. That is. For example. but you should avoid using an on-board interface. which only supports a single IPS detection engine. network traffic continues to flow through the sensor as it would for an inline with fail open interface set. 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. 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. The interfaces do not have to be on the same network cards.

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

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

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

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

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

12.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 10. A list of network interfaces on the sensor appears. Defense Center Only Select one of the sensors from the list. A list of sensors appears.1 Sourcefire 3D System Administrator Guide 215 . Version 4. You can also select the ungrouped sensors. On the Defense Center only. Optionally. 11. including a list of ungrouped sensors. Defense Center Only Select the sensor group containing the sensors where you want to create the interface set. a list of sensor groups 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.9. inclusive. You can set any jumbo frame size between 1518 and 9018 bytes. The following shows a 3D9900 interface set.

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

You can also use multiple interface pairs when your network employs asynchronous routing. TIP! Although the default interface set on 3D Sensors includes all the available inline interface pairs. Later. If you include only one interface pair in an interface set. you can refine policies for specific connected network segments and their requirements. the sensor might not correctly analyze your network traffic because a detection engine might see only half of the traffic.9. 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. as shown in the following graphic.1 Sourcefire 3D System Administrator Guide 217 . Version 4.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 3D Sensor deployment. in many cases you can improve performance by modifying the interface set to include only the inline interface pairs your network requires.

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

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

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

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

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

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

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

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

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

1 Sourcefire 3D System Administrator Guide 227 . For information on establishing and separating clustered pairs. Log in as root onto the sensor and.pl close eth#:eth# For example. Enter the following at the command line: failopen_pair.9. the following message appears: Mode changed for interfaces eth2:eth3 The interfaces switch to bypass mode and the traffic is no longer analyzed.. if the interfaces in the interface set are eth2 and eth3.Using Detection Engines and Interface Sets Using Clustered 3D Sensors Chapter 6 4. if you specified the correct interfaces. the following message appears: No failopen interface set configured for interfaces eth2:eth3. Enter the following at the command line: failopen_pair. 2. shared configuration. you can identify them on the Sensor list page. enter the following: failopen_pair. Select Operation > Sensors and note that clustered sensors have a peer icon. see Managing a Clustered Pair on page 140.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. When you establish a clustered pair configuration. if the interfaces in the interface set are eth2 and eth3.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. Then. at the prompt. 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.pl open eth#:eth# For example. enter the correct password. Version 4. you combine the 3D9900 sensors resources into a single. To return an inline fail open interface set to normal mode: Access: Admin 1.. enter the following: failopen_pair. After the cluster is established. If you did not specify the correct interfaces.

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

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

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

collect the data from both 3D9900s and ensure that you configure each 3D9900 identically.9.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.1 Sourcefire 3D System Administrator Guide 231 . Version 4. The eStreamer settings are not automatically synchronized over the pair.

The Report Types table describes the reports you can create and the components required for producing them. Event reports include the data that you see on the event view pages for each type of event presented in a report format. 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. and you must configure the RNA component for that sensor to collect RNA events. 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.1 Sourcefire 3D System Administrator Guide 232 . Similarly. the Intrusion Events report appears under the IPS report category and requires the IPS component on a 3D Sensor. You must have an RNA host license on the Defense Center managing your 3D Sensor.9. the RNA Events report appears under the RNA report category on the Report Designer page.

For more information on how to create and save report profiles. see Editing Report Profiles on page 263.1 Sourcefire 3D System Administrator Guide 233 . 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. Version 4. see Understanding Report Profiles on page 241.9.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. You can create a new report profile through the use of the Report Designer. For information on modifying a predefined or existing report profile.

You can run reports remotely from the Defense Center using the data on the sensors for the report.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. Working with Report Profiles Requires: IPS or DC/ MDC You can use a predefined report profile to generate your report. For more information on how to manage your reports. For information on how to generate a report for the data that appears in an event view. if you use a Defense Center to manage your sensors. as well as move reports to a remote storage location. or delete previously generated reports. download. For more information on how to how to generate reports on managed sensors and view the results on the Defense Center. 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. see Managing Remote Storage on page 393. You can also specify which detection engine to use when generating the report. For more information on how to create and save report profiles. see Using a Report Profile on page 260. You can view. see Editing Report Profiles on page 263. see Generating Reports from Event Views on page 235. For more information on how to configure a Defense Center to store reports in a remote location using SSH. or SMB. You can create a new report profile through the use of the Report Designer.9. see Running Remote Reports on page 240. For information on how to generate a report from a report profile view. For information on how to modify a report profile.1 Sourcefire 3D System Administrator Guide 234 . You can store reports locally or remotely. see Managing Generated Reports on page 237. NFS. see Creating a Report Profile on page 246. Version 4.

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

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

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

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

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

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

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

Version 4. As with custom report profiles that you create (see Creating a Report Profile on page 246). you can use a predefined report profile as a template for an event report.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.9.1 Sourcefire 3D System Administrator Guide 242 . You can modify field settings as appropriate. save the report with the new values.

and Host Audit.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. High Priority Events.9. The Report Options area is not included in these charts. Version 4. The following graphic shows the Blocked Events report profile on the Defense Center version of the page.1 Sourcefire 3D System Administrator Guide 243 . Note that if you modify the default settings. you must save the report profile with a new name to preserve your new settings. you have created a new report profile.

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.1 Sourcefire 3D System Administrator Guide 244 .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. This report profile is available on the Defense Center or on a 3D Sensor with IPS.9.

1 Sourcefire 3D System Administrator Guide 245 . This report profile is available only on the Defense Center that manages 3D Sensors with RNA.Working with Event Reports Understanding Report Profiles Chapter 7 twenty-four hours. 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. This report profile is available only on a Defense Center that manages 3D Sensors with RNA and IPS. 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.9. and Host Criticality Last day. 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.

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.1 Sourcefire 3D System Administrator Guide 246 . in the IPS report category. configure the options in each of three report areas (Report Information. Report Sections. the criteria for the search. selecting the Intrusion Events report type gives you the option to select which detection engines to search. second. and which workflows to examine. Creating a Report Profile Requires: IPS or DC/ MDC You can create the report profile by defining category and type. queries. but not all options are available for all reports. and workflows to apply. such as a drill down of events. Not all options are available for all reports. Note that all reports contain the option for a summary report and an image file. For example. . or an image file. see Editing Report Profiles on page 263. table view of events. and Report Options). finally. selecting the Intrusion Events with Source Criticality report type does not provide that option. You perform three steps to create the a report profile: first. and then specifying which detection engines to search. Version 4. and.9. Working with Report Sections on page 255 explains how to specify which the sections to be included in the report. create the report profile in the system.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. and saving the report with the new values. save the report profile. Criticality Table View of Events Packets (limit 50 pages) Setting Operating System Summary Last week. Working with Report Information on page 248 explains how to set the type of report and how to specify which detection engines. For more information on how to modify a predefined report profile.

9. Version 4. 3. The following graphic shows the Defense Center version of the page. Continue with Defining Report Information on page 254. To create a report profile: Access: Any Analyst/ Admin 1. and how to use the option which emails the report. The Report Designer page appears. footer or logo. The Report Profiles page appears. Click Create Report Profile. TIP! You can also reach the Report Designer page from any event view by clicking Report Designer on the toolbar.1 Sourcefire 3D System Administrator Guide 247 . 2. Select Analysis & Reporting > Report Profiles.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). adds a custom .

such as detection engine. The following graphic is an example of the Report Information section. parentheses. and then selecting the report category and type. dashes.1 Sourcefire 3D System Administrator Guide 248 . search query.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.9. The Report Name can be any name using 1-80 alphanumeric characters. Version 4. Depending upon your choices. Note that not all options are available for all categories or types. periods. and spaces. you will have other options to define. and workflow.

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

such a intrusion. RNA. This option is available when searching for events. For more information.9. or sliding time frame. expanding. However. host attributes. or when searching the network for RNA hosts. Click in the current time field to open a pop-up window from which you can select a static.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. 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. have limited report types and are self-explanatory. see Setting Event Time Constraints in the Analyst Guide. such as the Compliance or Audit Log report categories. Options vary depending upon Report Type. 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. and IP-Specific or Impact and Priority. Options for the report type vary depending upon which Report Category is selected. or compliance events. Detection Engine. and health monitoring. Options vary depending upon which options you selected for Report Type. The Time option allows you to define the period of time for which the report is generated. client applications.1 Sourcefire 3D System Administrator Guide 250 . and Search Query. The Workflow allows you to select which workflow to examine. See the following sections for more information: • • IPS Category Report Types on page 251 RNA Category Report Types on page 252 Version 4. and can include such options as Network Services by Count or Host Violations. the report types available to the IPS and RNA report categories are extensive and provide detailed options for defining your report profile. white list. The Search Query identifies the search criteria for the report. Some 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

3. The Report Designer page appears and contains the current settings for the report profile.9. 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. and saving the report with the new values. 4. follow the instructions for your browser to save the report profile. When prompted. Click Edit next to the profile that you want to delete. Select Analysis & Reporting > Report Profiles.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. Version 4. Click Save Report Profile. The report profile is saved with the name you specified in the Report Name field. Select Analysis & Reporting > Report Profiles. 2. Access: Any Analyst/ Admin To edit a report profile: 1. remember to change the name of the report profile in the Report Name field. modifying the field settings as appropriate. Click Delete next to the profile that you want to delete. Make changes to the report areas as needed. The Report Profiles page appears. Deleting Report Profiles Requires: IPS or DC/ MDC Access: Any Analyst/ Admin Use the following procedure to delete a report profile. To delete a report profile: 1.1 Sourcefire 3D System Administrator Guide 263 . The Report Profiles page appears. Use the following procedure to edit a report profile. The report profile is deleted. You can also edit a report profile to make changes to the resulting report. 2.

the process checks the local database to see if the user exists there and.9. it queries an external server. 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.Managing Users Chapter 8 Administrator Guide If your user account has Administrator access. the appliance looks for a match for the user name and password in the local list of users. 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.1 Sourcefire 3D System Administrator Guide 264 . This process is called authentication. rather than through the internal database. There are two kinds of authentication: internal and external. you can also set up user authentication via an external authentication server. For more information. If the user’s account uses internal authentication. if the user is not found locally. On the Defense Center. If the account uses external authentication. such as a Lightweight Directory Version 4.

1 Sourcefire 3D System Administrator Guide 265 .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. 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. for a list of users.9. unless you change the user permissions manually. For users with either internal or external authentication. Users with external authentication receive the permissions either for the group or access list they belong to. Version 4.

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

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

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

host statistics. containing connection settings and authentication filter settings for those servers.1 Sourcefire 3D System Administrator Guide 269 . and responses. Creating LDAP Authentication Objects Requires: DC You can create LDAP authentication objects to provide user authentication services for an appliance. Multiple applications can then access those credentials and the information used to describe them. you define settings that let you connect to an authentication server. and system logs) and maintenance functions (including task scheduling and backing up the system). Maintenance Administrators can access monitoring functions (including health monitoring. policies. allows you to set up a . manage. you can configure shell access authentication. When you create an authentication object. such as user credentials. you can change them in one place.Managing Users Managing Authentication Objects Chapter 8 • • Policy & Response Administrators can manage intrusion rules. and responses. directory on your network that organizes objects. Version 4. 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.9. and delete authentication objects on the Defense Center. You also select the directory context and search criteria you want to use to retrieve user data from the server. in a centralized location. You can create. policies. rather than having to change them on the local appliances as well as on any other application that uses them. If you ever need to change a user's credentials. 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. performance data. Optionally. as well as compliance rules. Managing Authentication Objects Requires: DC Authentication objects are server profiles for external authentication servers.

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

Version 4. IPv6 addresses are not supported. the appliance then queries the backup server. 4. Configuring LDAP Authentication Settings Requires: DC If you specify a backup authentication server. Optionally. for example.Managing Users Managing Authentication Objects Chapter 8 To identify an LDAP authentication server: Access: Admin 1. 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). 3. Continue with Configuring LDAP Authentication Settings. 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.9. however. you can set a timeout for the connection attempt to the primary server. IMPORTANT! If you are using a certificate to connect via TLS or SSL. 7. Type a name and description for the authentication server in the Name and Description fields. modify the port used by the primary authentication server in the Backup Server Port field. 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. If. the appliance would query the backup server.1 Sourcefire 3D System Administrator Guide 271 . Select LDAP from the Authentication Method drop-down list. 5. Optionally. Optionally. the failover to the backup server does not occur. 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. the host name in the certificate must match the host name used in this field. the primary server has LDAP disabled. 2. 6. modify the port used by the primary authentication server in the Primary Server Port field. In addition.

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

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

into the User Name Template field. type the attribute type. and the attribute value you want to use as a filter. 9. If your LDAP server uses uid. type (physicalDeliveryOfficeName=NewYork). To set a filter that retrieves only specific objects within the namespace you specified as the Base DN. You can use any attribute. Version 4. Valid user names are unique. For example. However. 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. 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. The Pluggable Authentication Module (PAM) login attribute of your LDAP Server acts as a shell access attribute. to retrieve only users in the New York office. Setting a UI access attribute tells the local appliance to match the value of that attribute rather than the value of the uid attribute.dc=com. enclosed in parentheses. Re-type the password in the Confirm Password field. 8. when a user logs in. Type the user distinguished name. 6.1 Sourcefire 3D System Administrator Guide 274 . For example.com.ou=security. Configuring Attribute Mapping Requires: DC If your LDAP Server uses a default UI access attribute of uid.ou=security.dc=example.9. if the value of the attribute is a valid user name for either the Sourcefire 3D System web interface or for shell access. For a Microsoft Active Directory server. 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.example. with the string conversion character (%s) in place of the shell access attribute value.Managing Users Managing Authentication Objects Chapter 8 5. 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. For example. you would type uid=%s. you must explicitly set the Shell Access Attribute to match the attribute value. 7. have no spaces and no periods in them. a comparison operator. you would type uid=NetworkAdmin.dc=example. you could type %s@security. If the shell access attribute for a server is something other than uid. Continue with Configuring Attribute Mapping. you do not need to specify a UI access attribute. the local appliance checks the user name entered on login against the attribute value of uid. and do not begin with a numeral. in the Base Filter field. If you want to filter on uid. 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.dc=com in the User Name Template field. you can map a different attribute for the local appliance to search.

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

the user is assigned the default minimum access role specified in the Group Controlled Access Roles section of the authentication object. the Sourcefire 3D System limits the number of recursions of a search to four to prevent search syntax errors from causing infinite loops. the default access role defined in the Group Controlled Access Roles section is granted to the user. IMPORTANT! If you use a dynamic group.Locally Modified. 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. however. If you configure any group settings. You can. When you modify the access rights for an externally authenticated user.9. assign additional rights. • • • 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. 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. If a user’s group membership is not established in those recursions. Version 4. the user receives the access role for the group with the highest access as a minimum access role. If a user belongs to more than one configured group. the Authentication Method column on the User Management page provides a status of External .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. when a new user logs in.1 Sourcefire 3D System Administrator Guide 276 . For this reason.

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

9. 8. Specify a search filter that will retrieve entries for users you want to grant shell access.Managing Users Managing Authentication Objects Chapter 8 5. or Crossbeam-based software sensors. see Configuring Authentication Profiles on page 329. type memberURL.9. 11. Type the LDAP attribute that designates membership in a static group in the Group Member Attribute field. Continue with Configuring Administrative Shell Access on page 278. TIP! Press the Ctrl key while clicking role names to select multiple roles in the list. if the member attribute is used to indicate membership in the static group you reference for default Policy & Response Administrator access. Optionally.1 Sourcefire 3D System Administrator Guide 278 . 10. Intrusion Agents. IMPORTANT! Sourcefire does not support external authentication for RNA Software for Red Hat Linux. 6. if the memberURL attribute contains the LDAP search that retrieves members for the dynamic group you specified for default Admin access. 3Dx800 sensors. For more information on user access roles. Version 4. For more information on managing authentication object order. 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. 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. type member. Select the default minimum access role for users that do not belong to any of the specified groups from the Default User Role 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). Note that you can only configure shell access for the first authentication object in your system policy. 7. 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. 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. see Adding New User Accounts on page 300. For example.

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

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

DC=example. • OU=security.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.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.10. This example illustrates important aspects of LDAP configuration.4.3. 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.5. Version 4.3.10. Note that the connection uses port 389 for access and that connections to the server time out after 30 seconds of disuse. with a backup server that has an IP address of 10.9.1 Sourcefire 3D System Administrator Guide 281 .

Note that all objects in the directory are checked because no base filter is set.1 Sourcefire 3D System Administrator Guide 282 . • • • To support shell access. Version 4. the CN attribute is set as the shell access attribute. Because the user names to be retrieved are contained in the default uid attribute.4. with a backup server that has an IP address of 10.3. followed by the base distinguished name for the server directory.11. allowing only those users who have a common name attribute value of jsmith to log into the appliance using a shell account. 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).11.3. the user name template for the connection uses CN=%s. 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. Like the OpenLDAP server. 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. A shell access filter has been applied to this configuration. Aspects of this example illustrate important differences in this LDAP configuration from the configuration discussed in the OpenLDAP Example on page 281. no UI access attribute is specified.Managing Users Managing Authentication Objects Chapter 8 • Because this is an OpenLDAP server that uses CN as a part of each user’s name.5.9. to indicate the template used to format user names retrieved from the server.

because this server is a Microsoft Active Directory server. because no base filter is applied to this server.DC=com for the security organization in the information technology domain of the Example company. 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. As a result. the user name template for the connection uses address specification syntax documented in RFC 822 rather than the typical LDAP naming syntax.Managing Users Managing Authentication Objects Chapter 8 • Like the OpenLDAP server.DC=it.9. 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. However. the Sourcefire 3D System checks attributes for all objects in the directory indicated by the base distinguished name. this example shows a connection using a base distinguished name of OU=security. it uses the userPrincipalName attribute to store user names rather than the uid attribute. Note that the configuration includes a UI Access Attribute of userPrincipalName. • • In addition. Version 4.DC=example.1 Sourcefire 3D System Administrator Guide 283 . • Because this is a Microsoft Active Directory Server.

Version 4.3.9.DC=it. However. a shell access filter has been specified for this server. • As in the OpenLDAP server.12. with a backup server that has an IP address of 10.Managing Users Managing Authentication Objects Chapter 8 • This example also has group settings in place. as noted above. 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.5.1 Sourcefire 3D System Administrator Guide 284 .12. a shell access attribute value of sAMAccountName must be set for shell access to work on a Microsoft Active Directory server.4.DC=example.3. 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.DC=com. allowing only those users who have a common name attribute value of jsmith to log into the appliance using a shell account.

Because user names can be retrieved from the uid attribute on this server. Version 4.1 Sourcefire 3D System Administrator Guide 285 . the uid attribute is named as the Shell Access Attribute and the Same as Base Filter option for the shell access filter is set. no UI access attribute is specified. the Server Port is set to 636. • • The user name template shown uses the uid attribute value as the user name. • To allow shell access on the server. allowing all users with a common name ending in smith to log in using a shell account as well.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. However.DC=com for the security organization in the information technology domain of the Example company. A certificate has been uploaded to allow the SSL connection.DC=it.DC=example. Note that all objects in the directory are checked because no base filter is set. 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. note that this server does have a base filter of (cn=*smith). 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.9. The filter restricts the users retrieved from the server to those with a common name ending in smith. • This example shows a connection using a base distinguished name of OU=security.

the settings in place at the time the policy was applied stay in effect until you re-apply the policy. Click Edit next to the object you want to edit. Version 4. If the object is in use in a system policy. The Create Authentication Object page appears. 2. Select Operations > Configuration > Login Authentication. For more information. To edit an authentication object: Access: Admin 1.Managing Users Managing Authentication Objects Chapter 8 Editing LDAP Authentication Objects Requires: DC You can edit an existing authentication object.9.1 Sourcefire 3D System Administrator Guide 286 . upload the new certificate and re-apply the system policy to your appliances to copy over the new certificate. 3. The Login Authentication page appears. 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. Modify the object settings as needed.

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

For more information. Configuring RADIUS Connection Settings Requires: DC When you create a RADIUS authentication object. you can set a timeout for the connection attempt to the primary server. Optionally. 7. 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. specify the users or user attribute values for users that you want to receive specific Sourcefire 3D System access roles. define those attributes. Identify the primary and backup authentication servers where you want to retrieve user data for external authentication and set timeout and retry values. Optionally. see Configuring Administrative Shell Access on page 292. Your changes are saved. 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. see Testing User Authentication on page 294. If you specify a backup authentication server. If. see Configuring RADIUS Connection Settings on page 288. For more information.9. For more information. configure administrative shell access. Set the default user role. For more information. Test your configuration by entering the name and password for a user who should successfully authenticate.Managing Users Managing Authentication Objects Chapter 8 3. the primary server has RADIUS disabled. for example. IMPORTANT! For FreeRADIUS to function correctly. 4. 6. see Configuring RADIUS User Roles on page 290. For more information. 5. the appliance then re-queries the primary server. If the profiles for any of the users to authenticate return custom RADIUS attributes. the appliance then rolls over to the backup server. see Configuring Authentication Profiles on page 329 and Applying a System Policy on page 324. the appliance would query the backup server. For more information. you need to open both ports 1812 and 1813 on your firewall and on the FreeRADIUS server. see Defining Custom RADIUS Attributes on page 293. 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. 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.1 Sourcefire 3D System Administrator Guide 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.

Type the number of seconds that should elapse before retrying the connection in the Timeout field.9. Optionally. Select RADIUS from the Authentication Method drop-down list. Type a name and description for the authentication server in the Name and Description fields. however. 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. 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. To identify a RADIUS authentication server: Access: Admin 1. 3.1 Sourcefire 3D System Administrator Guide 289 . 5. 2. 9. modify the port used by the primary RADIUS authentication server in the Primary Server Port field. Version 4. the failover to the backup server does not occur. 6. 4.Managing Users Managing Authentication Objects Chapter 8 misconfiguration or other issues). 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. IMPORTANT! IPv6 addresses are not supported. 7. Optionally. 8.

if you know all users who should be RNA Analysts have the value Analyst for their User-Category attribute. • • You can also use attribute-value pairs. rather than usernames. WARNING! If you want to change the minimum access setting for a user. 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. You can. 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.Managing Users Managing Authentication Objects Chapter 8 10. you can also configure a default access setting for those users detected by RADIUS that are not specified for a particular role. however. You can select multiple roles on the Default User Role list. when a new user logs in. 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. see Configuring User Roles on page 304. 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. the user is assigned those access roles. see Defining Custom RADIUS Attributes on page 293. that user receives all assigned access roles. and you must remove the assigned user right on the user management page. 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. 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 assign a default user role (or roles) to be assigned to any users that are authenticated externally but not listed for a specific role. Version 4. you must reapply the system policy. Continue with Configuring RADIUS User Roles.9. 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. 11. to identify users who should receive a particular user role.1 Sourcefire 3D System Administrator Guide 290 . When you do so. For more information on the user roles supported by the Sourcefire 3D System. For more information. If you add a user to the list for one or more specific role. Note that you need to define any custom attributes before you use them to set user role membership. you can type User-Category=Analyst in the RNA Analyst List field to grant that role to those users. When a user logs in. For example.

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

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

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

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

Intrusion Event Analysts see the main toolbar and IPS analysis-related options on the Analysis & Reporting and Operations menus. 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. Provides access to rules and policy configuration.9. however. including intrusion event views. For externally authenticated users. See Modifying Restricted Event Analyst Access Properties on page 307 for more information. or passwords at any time. However. You manage those settings on the external server. 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. you can modify access privileges. you must configure access rights for all accounts. incidents.1 Sourcefire 3D System Administrator Guide 306 . incidents.Locally Modified. and reports. Note that password management options do not apply to users who authenticate to an external directory server. You can.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. Intrusion Event Analysts see the main toolbar and IPS analysis-related options on the Analysis & Reporting and Operations menus. including those that are externally authenticated. When you modify the access rights for an externally authenticated user. Policy & Response Administrator Access Modifying User Privileges and Options Requires: DC/MDC or 3D Sensor After adding user accounts to the system. Version 4. assign additional rights. Policy & Response Administrators have access to the main toolbar and rule and policy-related options on the Policy & Response and Operations menus. you must supply a new password for the 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. the Authentication Method column on the User Management page provides a status of External . Restricted event analyst users see only the main toolbar and analysis-related options on the Analysis & Reporting and Operations menus. including intrusion event views. and reports. account options.

Optionally.9. 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 Managing User Password Settings on page 303 for information on changing password settings for internally authenticated users. for users with event analyst roles. 2. See Adding New User Accounts on page 300 for information about adding new user accounts. The User Management page appears. 3. • • • 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. Version 4. Click Edit next to the user you want to modify. 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. See Configuring User Roles on page 304 for more information on configuring roles to grant access for Sourcefire 3D System functions.1 Sourcefire 3D System Administrator Guide 307 . The Edit User page appears. You can specify this information only after the user is added. Select Operations > User Management.

1 Sourcefire 3D System Administrator Guide 308 .. view the network map When these platforms are present. Restricted Event Analyst Settings To allow the restricted event analyst to.. The Restricted Event Analyst Settings table shows the correlation between platform and access requirements for the restricted event analyst..9.Managing Users Managing User Accounts Chapter 8 Restricted event analyst users have access to only a few sections of the web interface..included in the base set of rights for the restricted analyst role Version 4. 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 .

and event view settings create custom workflows and.. Searches must be private. generate (but not view) reports create (but not modify) incident reports change user-specific preferences such as the account password.. To restrict event analyst access to events: Access: Admin 1.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. The User Management page appears.. Click Edit next to the user to whom you want to grant restricted event analyst rights.. Select Operations > User Management. Version 4. IMPORTANT! You must have saved private searches available before you can add restricted event analyst values to a user account.9. time zone. custom tables create and manage bookmarks view events from a custom table When these platforms are present. one for each of the event types. create multiple private saved searches. 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 . restricted event analyst users could delete the searches and enhance their access privileges. on the Defense Center.1 Sourcefire 3D System Administrator Guide 309 . and then apply each saved search to the account as described in the following procedure.Managing Users Managing User Accounts Chapter 8 Restricted Event Analyst Settings (Continued) To allow the restricted event analyst to. 2. If they are saved as public. See Searching for Events in the Analyst Guide for more information.

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

click Edit. The Edit User page appears. In the Password field. To change a user’s password: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 311 . TIP! If you want to force a user to change the password on the next log-in. 2. Next to the user name. Version 4.9. The User Management page appears. click Reset Password next to the user account on the User Management page. 3. Select Operations > User Management.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. Note that you must manage externally authenticated user passwords on the LDAP or RADIUS server. type the new password (up to 32 alphanumeric characters).

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

1 Sourcefire 3D System Administrator Guide 313 . An X indicates that the user can access the option. Users with only Rules or Maintenance access cannot see the Analysis & Reporting menu at all. 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.9.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.

9.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.

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.1 Sourcefire 3D System Administrator Guide 315 .9.

Users with Intrusion Event Analyst. or Maintenance access can not see the Policy & Response menu at all.1 Sourcefire 3D System Administrator Guide 316 . 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. RNA Event Analyst.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. 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.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. An X indicates that the user can access the option. 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.1 Sourcefire 3D System Administrator Guide 317 .9. All users can access at least some options on the Operations menu. Operations Menu 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.

9. 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.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 IPS/ IPS-RO Event Analyst Res.

1 Sourcefire 3D System Administrator Guide 319 . 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. All users can access at least some of the options on the toolbar.9. 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. An X indicates that the user can access the option.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. 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.

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. For example.9. your organization’s security policies may require that Version 4. 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.1 Sourcefire 3D System Administrator Guide 320 .

see Importing and Exporting Objects on page 583.1 Sourcefire 3D System Administrator Guide 321 . if you have different mail relay hosts that you use under different circumstances. 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. For more information. IMPORTANT! You cannot apply system policies to Crossbeam-based software sensors or Intrusion Agents. you can create several system policies and switch between them rather than editing a single policy. 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 configure the various aspects of the policy. which are likely to be specific to a single appliance.Managing System Policies Creating a System Policy Chapter 9 your appliances have a “No Unauthorized Use” message when a user logs in. you can export a system policy from another appliance and then import it onto your appliance. You can then edit the imported policy to suit your needs before you apply it. Version 4. or if you want to test different database limits. For example. you assign it a name and a description. Instead of creating a new policy. Contrast a system policy. See Configuring System Settings on page 360 for more information. You can also benefit from having multiple policies on a 3D Sensor. Next. each of which is described in its own section. With system policies. with system settings.9.

5. Click Save. Your system policy is saved and the Access List page appears. For information about configuring each aspect of the 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. The System Policy page appears.Managing System Policies Creating a System Policy Chapter 9 To create a system policy: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 322 . From the drop-down list.9. The Create page appears. Click Create Policy. 2. The Policy Name column includes its description. select an existing policy to use as a template for your new system policy. 4. 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. Select Operations > System Policy. 3. Type a name and description (up to 40 alphanumeric characters and spaces each) for your new policy.

With the Policy Name and Policy Description fields at the top. For information about configuring each aspect of the system policy.9. 2. The System Policy page appears.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. You can change the policy name and description. Click Edit next to the system policy that you want to edit. Access List. To edit an existing system policy: Access: Admin 1. including a list of the existing system policies. appears. the first section of the system policy. Select Operations > System Policy.1 Sourcefire 3D System Administrator Guide 323 . 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.

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

it is used until a new policy is applied. The System Policy page appears. port 443 (Hypertext Transfer Protocol Version 4. The policy is deleted. Select Operations > System Policy. Click Delete next to the system policy that you want to delete. If the policy is still in use.9. Configuring the Parts of Your System Policy Requires: Any You can change various parts of your system policy. 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. For information about configuring each aspect of the system policy. To delete a system policy: Access: Admin 1. Default system policies cannot be deleted.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. 2. including a list of the existing system policies.1 Sourcefire 3D System Administrator Guide 325 . By default.

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

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

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

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

you have to modify the policy on the Defense Center and then push it to the sensor again. the user login attempt is rejected. select Operations > System Policy. and click Save. If an external user attempts to log in. 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. On the Defense Center. the system policy on the sensor does not display authentication profile settings. If the user is a new external user. Note that you can only enable external authentication on Defense Centers and 3D Sensors. 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. the appliance checks the username and password against the external database. however. 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. If the username and password match results from an external server. Provide a name and description for the system policy as described in Creating a System Policy on page 321. You have two options: • • To modify the authentication profile settings in an existing system policy. 2.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 sensor.9. If the login fails. the user logs in successfully. click Edit next to the system policy. To enable authentication of users on external servers: Access: Admin 1. and external authentication is enabled. The System Policy page appears. the appliance then checks the username and password against the local database. Version 4. click Create Policy. so you cannot manage them on the sensor itself. the appliance first checks if that user is in the local user database. an external user account is created in the local database with the default privileges for the external authentication object. the appliance checks the user against each external authentication server in the authentication order shown in the system policy. To configure the authentication profile settings as part of a new system policy. To make changes to the authentication profile settings. If a match is found.1 Sourcefire 3D System Administrator Guide 330 . If a match is found. However. If the user exists. If the login fails. the Access List page appears. the user logs in successfully. In either case. eligible externally authenticated users can log into the sensor. To disable authentication on a managed sensor.

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

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

and health events. database limits that do not apply to a particular appliance are silently ignored. flow summaries. Virtual Defense Center. the maximum limit for the appliance is silently enforced. 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.. In addition.9. 2. or DC1000 100 million events on the DC3000 10 million events on the DC500... as well as flow events.. The Database Event Limits on page 333 below describes the maximum number of records you can store in the databases on your appliance.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. any health alert limits you set in the policy have no effect on the sensors. 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. IMPORTANT! You cannot apply system policies to Crossbeam-based software sensors or Intrusion Agents..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. Note that if you apply a system policy to an appliance that does not support the maximum limit you specify (for example. For example. Virtual Defense Center..1 Sourcefire 3D System Administrator Guide 333 . 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. if you specify 100 million intrusion events and apply that policy to a 3D Sensor). if you use the Defense Center to apply the same system policy to itself and the 3D Sensors it manages.

9. Provide a name and description for the system policy as described in Creating a System Policy on page 321. 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. beginning with the oldest files... audit records remediation status events on a Defense Center the white list violation history of the hosts on your network. 2.1 Sourcefire 3D System Administrator Guide 334 . see Purging the RNA and RUA Databases on page 598. 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. click Create Policy. In addition.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. the oldest events and packet files are pruned until the database is back within limits. Select Operations > System Policy..Managing System Policies Configuring the Parts of Your System Policy Chapter 9 Database Event Limits (Continued) The. In either case. To configure the database settings as part of a new system policy. See Configuring a Mail Relay Host and Notification Address on page 338 for information about generating automated email notifications when events are automatically pruned... unified files are deleted from the system. the Access List page appears. and click Save. The System Policy page appears. Version 4. You have two options: • • To modify the database settings in an existing system policy. click Edit next to the system policy. For information on manually pruning the RNA and RUA databases. if the /volume disk partition reaches 85% of its capacity.. 100. To configure the maximum number of records in the database: Access: Admin 1.

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

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

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

click Edit next to the system policy. In addition. The System Policy page appears. You have two options: • • To modify the email settings in an existing system policy. WARNING! Although DNS caching is enabled for the appliance. See Applying a System Policy on page 324 for more information. In either case. To configure the email 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. Select Operations > System Policy.requires IPS) use email for health event alerting (Defense Center only) you must configure a mail host. and click Save.9. and compliance event alerting (Defense Center only . The system policy is updated. 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. Your changes do not take effect until you apply the system policy.1 Sourcefire 3D System Administrator Guide 338 . 2. click Create Policy. you can configure an email address that will receive notifications when intrusion events and audit logs are pruned from the database.requires RNA) use email for intrusion event alerting (Defense Center only . Click Save Policy and Exit.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 6. Version 4. 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. the Access List page appears. impact flag. To configure a mail relay host: Access: Admin 1.

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

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

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

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

This option is especially valuable if you want to prevent spoofed hosts from taking the place of valid hosts in the network map. Select this check box if you want you want to combine flow summaries involving external hosts. see Creating RNA Detection Policies in the Analyst Guide. if you enable this option and you attempt to drill down to the table view of flow data (that is. For more information. Version 4. protocol. For more information. This can reduce the space required to store flow data and can also speed up the rendering of flow data graphs. instead of an individual IP address. graphs. 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. the table view contains no information. before RNA drops a client application from the network map due to inactivity. in minutes.1 Sourcefire 3D System Administrator Guide 343 . 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.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 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. 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. access data on individual flows) for a flow summary that involves an external responder. IMPORTANT! Make sure that the client application timeout value is longer than the update interval in the RNA detection policy. which can reduce the number of events sent to the Defense Center. However. 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. The default setting is 10080 minutes(7 days). and reports use external to indicate the hosts outside your monitored network. keep in mind that setting this option in the RNA detection policy requires that you set your flow data mode to Summary. However. service. Event views. see Combining Flow Summaries from External Responders in the Analyst Guide as well as Configuring RNA Detection Policy Settings in the Analyst Guide. 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.9.

see Drop Duplicate RNA Flow Events. Duplicate flow events can also be created if you overlap network segment coverage with your RNA detection engines in your RNA detection policy.1 Sourcefire 3D System Administrator Guide 344 . not following best practices can degrade performance as the Defense Center attempts to resolve the conflicts. and can also use excessive bandwidth. for example. only the reporting detection engine for the flow initiator generates a flow event. For more information. if you use one policy to monitor both networks. Note that best practices are to use only one detection policy and to not overlap network segment coverage. Version 4. each of which is monitoring a separate network segment using separate detection engines. In that scenario. 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. Duplicate flow events can be created if you use two RNA detection policies. 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. On the other hand. best practices are to avoid creating duplicate NetFlow events. if two NetFlow-enabled devices export information about the same session.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.9. Duplicate NetFlow events can be created. Just as with RNA flow events.

For example. 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. the intrusion event will be marked with the red (Vulnerable) impact flag. You can select any or all of the check boxes in this section. Version 4. 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.9. see Understanding Nessus Scans in the Analyst Guide or the Sourcefire 3D System Host Input API Guide. • Select the Third Party Vulnerability Mappings check box if you want to use third-party vulnerability references to perform impact flag correlation. 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.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. see Mapping Third-Party Vulnerabilities in the Analyst Guide. if you scan using Nessus. see Using Impact Flags to Evaluate Events in the Analyst Guide. Note that if you clear all the check boxes. • 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. For more information. • Select the Use RNA Vulnerability Mappings check box if you want to use RNA vulnerability information to perform impact flag correlation. select this option to use the Nessus vulnerability mappings. control which vulnerability types to use for impact assessment. For more information. 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. For more information. as described in the following table. intrusion events will never be marked with the red impact flag. 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. To provide the most reliable operating system and service identity information.1 Sourcefire 3D System Administrator Guide 345 . See Understanding RNA Host Input Event Types in the Analyst Guide for information about each event type.

however.9. 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. identity data added by a scanner or application overrides identity data detected by RNA. that user input data overrides scanner and application data regardless of priority. For more information on current identities and how RNA selects the current identity. unless there is an identity conflict.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.1 Sourcefire 3D System Administrator Guide 346 . but does allow integration of imported application or scan results. RNA retains one identity for each source. Note. but only data from the highest priority application or scanner source is used as the current identity. or change the priority or timeout settings for existing sources. as indicated in the Multiple Fingerprint Settings table. remember to make sure that you map vulnerabilities from the source to the RNA vulnerabilities in the network Version 4. By default. If you import data from a third-party application or scanner. see Enhancing Your Network Map in the Analyst Guide. Note that adding a scanner to this page does not add the full integration capabilities that exist for the Nmap and Nessus scanners. However. You can use the Multiple Fingerprinting page to rank scanner and application fingerprint sources by priority. 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. You can add new active sources through this page. 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. By default.

select Active from the Automatically Resolve Conflicts drop-down list. To specify RNA settings: Access: Admin 1. • 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. select Passive from the Automatically Resolve Conflicts drop-down list. The System Policy page appears. select Scanner or Application. from the Type drop-down list. Scanner/ Application List You have several options: • To add a new source. click the up arrow next to the source name. • To promote a source and cause the operating system and service identities to be used in favor of sources below it in the list. For more information. You have the following options: • To force manual conflict resolution of identity conflicts.9. Type a name for the source. Select Operations > System Policy.1 Sourcefire 3D System Administrator Guide 347 . • 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. 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. see Mapping Third-Party Vulnerabilities in the Analyst Guide. • To use the current identity from the highest priority active source when an identity conflict occurs. select Disabled from the Automatically Resolve Conflicts drop-down list. click the down arrow next to the source name. or Weeks from the Timeout drop-down list and type the appropriate duration. Configuring Settings for RNA Requires: DC + RNA Use the following procedure to configure RNA settings in the system policy. Version 4. click Add in the Multiple Fingerprints page of the system policy. select Hours. • To use the RNA fingerprint when an identity conflict occurs. Days.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 map. • To change the type of source.

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

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

or.1 Sourcefire 3D System Administrator Guide 350 . The following diagram illustrates the automated subnet detection process.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. flow data.9. you must explicitly assign an RNA detection engine to monitor that subnet. and so on. including operating system and service identity data. if you configured the Defense Center to automatically apply recommendations. Note that you can configure the Defense Center to notify you of subnet recommendations via email so that you can make the changes manually. Version 4. to notify you of any changes made. To get detailed information about the hosts in a subnet.

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

In addition. 7. obtaining usernames through protocols such as AIM. Restricting RUA helps minimize username clutter and preserve RUA licenses. and SIP logins always create duplicate user records. When RUA detects a user login for a user who is not already 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. Your changes do not take effect until you apply the system policy. Enable the Automatically Apply Daily Recommendations check box to automatically update and apply your RNA detection policies after RNA generates subnet recommendations. Note that this option has no effect unless you enable daily recommendations. Version 4. an RUA user is added to the Defense Center user database. RUA stops adding new users to the Defense Center database. and other guests. 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.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 6.1 Sourcefire 3D System Administrator Guide 352 . The system policy is updated.9. the Defense Center does not record them unless there is already a user with a matching email address in the database. For example. visitors. 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. 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. AIM. See Applying a System Policy on page 324 for more information. After you reach your licensed limit. 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. and IMAP can introduce usernames not relevant to your organization due to network access from contractors. Click Save Policy and Exit. Oracle. POP3.

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

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

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

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

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

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

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

which controls aspects of an appliance that are likely to be similar across a deployment. with a system policy.9. which are likely to be specific to a single appliance. Version 4.1 Sourcefire 3D System Administrator Guide 360 . Contrast the system settings.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. See Managing System Policies on page 320 for more information.

You can also change the appliance name. See Configuring Remote Access to the Defense Center on page 386 for more information.Configuring System Settings Chapter 10 The System Settings Options table describes the options you can configure in the system settings. enables you to establish communications with a Defense Center from the sensor. Provides you with options for managing your current licenses and for adding additional feature licenses on the platforms that support them. then you can use this page to change the time. Time Displays the current time. hostname. License Network Network Interface Process Version 4.9. See Viewing and Modifying the Appliance Information on page 362 for more information. See Setting the Time Manually on page 389 for more information. On the Defense Center. Allows you to view and modify the settings for the network interfaces on your appliance. Enables you to change options such as the IP address. 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. 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. Remote Management On the 3D Sensor. See Configuring the Communication Channel on page 383 for more information. and proxy settings of the appliance that were initially set up as part of the installation.1 Sourcefire 3D System Administrator Guide 361 . System Settings Options Option Information Description Allows you to view current information about the appliance. See Editing Network Interface Configurations on page 380 for more information. If the time synchronization settings in the current system policy for the appliance is set to Manual. See Understanding Licenses on page 364 for more information. See Configuring Network Settings on page 377 for more information.

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

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

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

. use IPS on that appliance. and Sourcefire Defense Center Installation Guide. Virtual License a Defense Center at any time use virtual machines.. For information on how to use virtual appliances. TIP! You can view your licenses by using the Product Licensing widget in the dashboard. To understand why and when to use these licenses.. RUA. For information on adding a product license. see Sourcefire Virtual Defense Center and 3D Sensor Installation Guide. see Understanding Feature Licenses on page 366.9. Product License to. For information on how to add a feature license.. See Understanding the Product Licensing Widget on page 84 for more information.1 Sourcefire 3D System Administrator Guide 365 . a 3D Sensor or a Defense Center during installation so that you can. 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. Version 4. For information on how the various features function.. see the Sourcefire Licenses table on page 365.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. and so on. see Adding Feature Licenses on page 370. see Sourcefire 3D Sensor Installation Guide. For information on IPS. Sourcefire Licenses You apply a.

NetFlow is available not only on Cisco networking devices. RUA Users. and your deployment must include at least one 3D Sensor with RNA that can communicate with your NetFlow-enabled devices. up-to-the-minute profile of your network correlate threat. You can deploy NetFlow-enabled devices on networks that your sensors cannot monitor. NetFlow NetFlow is an embedded instrumentation within Cisco IOS Software that characterizes network operation.. and use NetFlow data to monitor those networks. RNA Hosts.. For more information. but can also be embedded in Juniper. and OpenBSD devices. NetFlows. endpoint. and network intelligence with user identity information identify the source of policy breaches.9.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. 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. Although you can use NetFlow-enabled devices exclusively to monitor your network. the Sourcefire 3D System uses RNA detection engines on 3D Sensors to analyze NetFlow data. Version 4. attacks.. 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. Standardized through the RFC process. You must use a Defense Center to configure NetFlow data collection and to view the collected data. see Introduction to NetFlow in the Sourcefire 3D System Analyst Guide.. Intrusion Agents. 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.1 Sourcefire 3D System Administrator Guide 366 . Feature Licenses If you want to. FreeBSD. NetFlow-enabled devices are widely used to capture and export data about the traffic that passes through those devices. RUA Users and either RNA Hosts or the product license (or both). IPS Software Sensors.

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

To verify the product license file: Access: Admin 1. In most cases. Version 4. and deleting feature licenses. viewing. see Sourcefire Crossbeam Installation Guide XOS. Click License. The License page appears. For more information. Select Operations > System Settings. see Managing Your Feature Licenses on page 370. 2.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. Verifying Your Product License Requires: Any During installation. the user who sets up the appliance adds the software license as part of the process.9. For information on adding. you do not need to re-install the license. The Information page appears.1 Sourcefire 3D System Administrator Guide 368 .

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

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

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

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

Lists the number of monitored hosts added by the license. invalid. Displays the feature serial 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.9. Version 4. Displays the appliance model number. The RNA Host License Columns table describes each column that appears in an RNA host license. Lists the number of NetFlow-enabled devices that the license allows you to use. Indicates if the license is valid. Displays the appliance’s MAC address. Indicates if the license is valid. or if a temporary license has expired. Displays the appliance model number. invalid. or if a temporary license has expired. Displays the appliance’s MAC address. Displays the feature serial number. 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. Displays the date and time that the feature license expires.1 Sourcefire 3D System Administrator Guide 373 .

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. Displays the appliance model number. The Intrusion Agent License Columns table describes each column that appears in an intrusion agent license.1 Sourcefire 3D System Administrator Guide 374 . or if a temporary license has expired. Allows you to delete the feature license by clicking Delete.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. Displays the feature serial number. Displays the date and time that the feature license expires.9. Indicates if the license is valid. invalid. Lists the number of monitored users added by the license. Version 4. 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. The RUA License Columns table describes each column that appears in an RUA host license. Displays the appliance’s MAC address. Displays the feature serial number.

1 Sourcefire 3D System Administrator Guide 375 . Displays the appliance’s MAC address. Indicates if the license is valid. Displays the appliance model number. 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. Maximum throughput is limited by other factors such as number of Virtual Machines on your VMware server. Allows you to delete the feature license by clicking Delete. 45. invalid. Displays the date and time that the feature license expires. 100. invalid. Displays the appliance model number. Lists the maximum number of software agent connections allowed by the license. Displays the appliance’s MAC address. or 250MB). its connections. Displays the feature serial number.9. or if a temporary license has expired.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. Displays the maximum capacity licensed for processing by the Virtual 3D Sensor (20. IMPORTANT! These speeds are not a guaranteed throughput for the Virtual 3D Sensor you license. and other physical hardware constraints. Lists the maximum number of Virtual 3D Sensors allowed by the license. Version 4. The Virtual 3D Sensor License Columns table describes each column that appears in an intrusion agent license. or if a temporary license has expired.

Displays the appliance’s MAC address. The IPS Software License Columns table describes each column that appears in an IPS Software license. Indicates if the license is valid. Displays the appliance model number.1 Sourcefire 3D System Administrator Guide 376 . invalid. 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. Displays the feature serial number. Displays the date and time that the feature license expires.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. or if a temporary license has expired. Allows you to delete the feature license by clicking Delete. Select Operations > System Settings. Version 4. To view or delete your feature licenses: Access: Admin 1. The Information page appears. Allows you to delete the feature license by clicking Delete.9.

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

you must set the address and netmask in dotted decimal form (for example: a netmask of 255. you specify Router assigned.0).255. in the case of IPv6. 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. • For IPv4. Version 4. By default.1 Sourcefire 3D System Administrator Guide 378 . protected network. 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). 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. The Information page appears.9. the new name is not reflected in the syslog until after you reboot the appliance. If. Select Operations > System Settings.Configuring System Settings Configuring Network Settings Chapter 10 local DHCP server. the management interface is connected to an internal. • For IPv6.0. To configure network settings: Access: Admin 1. the appliance retrieves its network settings from a local router. This is the network through which Defense Centers and sensors communicate. In most installations. the appliance is configured to directly connect to the Internet. 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 can configure a proxy server to be used when downloading updates and SEUs.

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

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

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

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

The Defense Center version of the page is shown below.0/ 16.16. The communication on port 8305 is bi-directional. The default port for communications between the Defense Center. click Run Command next to Reboot Appliance.1 Sourcefire 3D System Administrator Guide 383 . Note that restarting the Defense Center may cause deleted hosts to reappear in the network map. and if high availability is enabled. its high availability peer is 8305/tcp. 2.9. click Run Command next to Restart Appliance Console. click Run Command next to Reboot Defense Center. Note that this logs you out of the 3D Sensor. click Run Command next to Shutdown Defense Center. To restart the Snort and RNA processes.0. To restart the Defense Center. For 3D Sensor • • • • Configuring the Communication Channel Requires: DC + 3D Sensor Version 4. click Run Command next to Restart Detection Engines. click Run Command next to Restart Defense Center Console. 3. The default address range is 172. To restart the 3D Sensor. to its Defense Center peer. Note that this logs you out of the Defense Center. To shut down the 3D Sensor. in high availability deployments. To reboot the system. 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. The Appliance Process page appears. Select Operations > System Settings. The Information page appears. its managed sensors. Click Process. To reboot the system.Configuring System Settings Configuring the Communication Channel Chapter 10 To shut down or restart your appliance: Access: Admin 1. Specify the command you want to perform: For DC/MDC • • • To shut down the Defense Center.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. click Run Command next to Shutdown Appliance.

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

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

5. To edit the remote management virtual network: Access: Admin 1. 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. Version 4. click Regenerate VIP to regenerate the IP address used by the virtual network. 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. The Information page appears. which provides for a much greater number of appliances.1 Sourcefire 3D System Administrator Guide 386 .registration key Unique NAT ID . Select Operations > System Settings. See Working in NAT Environments on page 112 for more information. click Save.9. Registration Key . 4. After appropriate management virtual network edits are made. 2. The Remote Management page appears.the hostname of IP address. The Edit Remote Management page appears. 3.Configuring System Settings Configuring Remote Access to the Defense Center Chapter 10 version uses a default /16 (sixteen bit) CIDR address space.a unique alphanumeric ID for use when registering sensors in NAT environments. 6. Optionally. Click Remote Management. Click Edit next to the host whose Management Virtual Network you want to change. Three fields are provided for setting up communications between appliances: • • • Management Host . Edit the name or host ID in the Name or Host fields as required.

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

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 same value in the Unique NAT ID field. Optionally. If you used a unique ID in step 6. After the sensor confirms communication with the Defense Center. type a unique alphanumeric NAT ID that you want to use to identify the sensor. Click New Sensor. 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.9. in the Unique NAT ID field. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. 12. 9. the Pending Registration status appears. Access the Defense Center web interface and select Operations > Sensors. The Add New Sensor page appears. 5. In the Registration Key field. use both the Registration Key and the Unique NAT ID fields. In the Registration Key field. Click Save. 8.1 Sourcefire 3D System Administrator Guide 388 . Version 4. Type the IP address or the hostname of the sensor you want to add in the Host field. 6. 7. type the same one-time use registration key that you used in step 5. 10. In that case. The Sensors page appears. 11.

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

For example.1 Sourcefire 3D System Administrator Guide 390 . if you see larger update times such as 300 seconds. Version 4. The status of the NTP server time synchronization. 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. Last Update See Synchronizing Time on page 354 for more information about the time settings in the system policy. The number of seconds that have elapsed since the time was last synchronized with the NTP server. To manually configure the time: Access: Admin 1. The Information page appears. Instead. • Available indicates that the NTP server is available for use but time is not yet synchronized. The following states may appear: • Being Used indicates that the appliance is synchronized with the NTP server. Negative values indicate that the appliance is behind the NTP server. • Pending indicates that the NTP server is new or the NTP daemon was recently restarted. The NTP daemon automatically adjusts the synchronization times based on a number of conditions. Select Operations > System Settings. or Not Available. Over time. 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. its value should change to Being Used. Available. and positive values indicate that it is ahead. • 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.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.9. time manually.

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

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). TIP! To remove a NetFlow-enabled device. The NetFlow Devices page appears. see Introduction to NetFlow in the Analyst Guide.1 Sourcefire 3D System Administrator Guide 392 . Click Save. 4. you should also remove it from your RNA detection policy. To add NetFlow-enabled devices for flow data collection: Access: Admin 1. 2. 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. click Delete next to the device you want to remove. You must configure these NetFlow-enabled devices to export NetFlow version 5 data. Version 4. Click NetFlow Devices. Select Operations > System Settings. 5. 6. 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. including information on additional prerequisites. Keep in mind that if you remove a NetFlow-enabled device from the system policy. The Information page appears. To add additional NetFlow-enabled devices. In the IP Address field. For more information on using NetFlow data with the Sourcefire 3D System. For more information. 3. The list of NetFlow-enabled devices is saved.9. see Editing an RNA Detection Policy in the Analyst Guide. Click Add Device to add a NetFlow-enabled device. enter the IP address of the NetFlow-enabled device you want to use to collect flow data. repeat steps 3 and 4.

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

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

select either or both of the following: • • 7. Click Save. click Test. Select Enable Remote Storage for Backups to store backups on the designated host. The Remote Storage Device page appears. A Command Line Options field appears where you can enter the commands. The test ensures that the Defense Center can access the designated host and directory. 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. select Use Advanced Options. If there are any required command line options. Under System Usage. At Storage Type. Optionally. Select Operations > System Settings. select SSH. To store backups and reports using SSH: Access: Admin 1. The Information page appears. The page refreshes to display the SSH storage configuration options. 3.9. Select Enable Remote Storage for Reports to store reports on the designated host. Click Remote Storage Device. 6. 8. Your remote storage configuration is saved. 2. Version 4.1 Sourcefire 3D System Administrator Guide 395 .

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

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

and services that RNA detects. 4.0). for example. • • IMPORTANT! You cannot use the Update feature to update the SEU or Intrusion Agents. 4. 4.0.9.1 Sourcefire 3D System Administrator Guide 398 . for example.9.9 or 5. client applications. 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. Version 4. see the Intrusion Agent Configuration Guide. for example. Feature updates are more comprehensive than patches and generally include new features (and usually change the third digit in the version number.1).9.Updating System Software Chapter 11 Administrator Guide Use the Update feature to update the Sourcefire 3D System.1). Vulnerability database (VDB) updates affect the vulnerabilities reported by RNA as well as the operating systems. see Importing SEUs and Rule Files in the Analyst Guide. For information on updating your SEU. 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. For information on Intrusion Agents.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.1 Sourcefire 3D System Administrator Guide 413 .9. 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. WARNING! Do not use the backup and restore process to copy the configuration files between sensors. Version 4. system configuration files are saved in the backup file. The configuration files include information that uniquely identifies a sensor and cannot be shared.Using Backup and Restore Chapter 12 Administrator Guide Backup and restoration is an essential part of any system maintenance plan. By default. those updates are not backed up. You need to apply the latest SEU update after you restore. 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 can also choose to back up the following.

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

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

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

1 Sourcefire 3D System Administrator Guide 417 .Using Backup and Restore Creating Backup Files Chapter 12 7. 10. to use secure copy (scp) to copy the backup archive to a different machine. If you want to include an additional file in the backup. 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. Version 4. TIP! You can repeat this step to add additional files. 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. 9. 8. Often.9. 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. the file will be smaller. to be notified when the backup is complete. Optionally. select the Email when complete check box and type your email address in the accompanying text box. TIP! The compressed value that appears in the Selected Sum field is a conservative estimate of the size of the compressed file. type the full path and file name in the Additional Files field and click the plus sign (+). Optionally.

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

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

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

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

To restore the appliance from a backup file: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 422 . Click with the backup file selected to delete it.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. click to send the backup to the designated remote backup location. Version 4.9. The System Backup Management page appears. Select Operations > Tools > Backup/Restore. On a Series 2 Defense Center when you have a previouslycreated local backup selected. A Series 2 Defense Center version of the page is shown.

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

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

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.1 Sourcefire 3D System Administrator Guide 425 . You should always schedule tasks like these to run during periods of low network use. 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. Version 4.

push. Automating Nessus Scans on page 450 provides procedures for scheduling Nessus scans.1 Sourcefire 3D System Administrator Guide 426 . and installation of software updates. Synchronizing Nessus Plugins on page 452 provides procedures for synchronizing your sensor with the Nessus server. Automating Reports on page 448 provides procedures for scheduling reports.9. Automating Vulnerability Database Updates on page 437 provides procedures for scheduling the download. Automating Backup Jobs on page 428 provides procedures for scheduling backup jobs. and installation of software updates. push. Automating Software Updates on page 430 provides procedures for scheduling the download. Automating SEU Imports on page 444 provides procedures for scheduling rule updates. • • • • • • • • • • 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. Automating Intrusion Policy Applications on page 446 provides procedures for scheduling intrusion policy applications. Deleting Scheduled Tasks on page 461 describes how to delete one-time tasks and all instances of recurring tasks. You must recreate the recurring task schedule on a newly activated Defense Center when it changes from inactive to active. Automating Recommended Rule State Generation on page 456 provides procedures for scheduling automatic update of intrusion rule state recommendations based on RNA data. Automating Nmap Scans on page 454 provides procedures for scheduling Nessus scans. Viewing Tasks on page 458 describes how to view and manage tasks after they are scheduled. IMPORTANT! You cannot configure a recurring task schedule on the inactive Defense Center in a high availability pair of Defense Centers. Version 4.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. Editing Scheduled Tasks on page 461 describes how to edit an existing task.

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

9. 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. The remaining options on the Add Task page are determined by the task you are creating. see Creating Backup Profiles on page 418. If you selected Month(s) in the Repeat Every field.1 Sourcefire 3D System Administrator Guide 428 . 2. To automate backup tasks: Access: Maint/Admin 1. a Repeat On field appears. a Repeat On field appears. TIP! You must design a backup profile before you can configure it as a scheduled task. Select Operations > Tools > Scheduling. The Add Task page appears.9. Use the drop-down list to select the day of the month when you want to run the task.Scheduling Tasks Automating Backup Jobs Chapter 13 8. Click Add Task. For information on backup profiles. Select the check boxes next to the days of the week when you want to run the task. If you selected Week(s) in the Repeat Every field. Version 4. The Scheduling page appears.

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

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

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.8.Scheduling Tasks Automating Software Updates Chapter 13 Support site to ensure that you have the latest version of the update. such as 4. you can use the Once option to download and install updates during off-peak hours after you learn that an update has been released. you cannot schedule either pushes to managed sensors (on the Defense Center) or installs (on any appliance). push. Instead you must manually push or install the updates as described in Updating System Software on page 398.9). To automate software updates: Access: Maint/Admin 1. On the Defense Center.2. This behavior also has implications for appliances that cannot access the Support site at all. If your appliance cannot access the Support site.8. The Scheduling page appears. the task does not complete. and install the upgrade files. Click Add Task. if you manually download an update to an appliance that cannot access the Support site. You can use this task to schedule download of updates you plan to push or install manually. you must manually upload. If you want to have more control over this process.9. Select Operations > Tools > Scheduling.1 or 4. For larger. you can also automate vulnerability database (VDB) updates. Specifically.1). The Add Task page appears. more comprehensive updates (such as 4. 2.8 or 4. Version 4.1 Sourcefire 3D System Administrator Guide 431 . 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.

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

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

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

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

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

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

The Add Task page appears. 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.1 Sourcefire 3D System Administrator Guide 438 . Instead you must manually push or install the updates as described in Updating System Software on page 398. However. If you want to have more control over this process. it will install the downloaded VDB update when it runs the next day. You must download the VDB on the Defense Center and push it to the sensor. 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.Scheduling Tasks Automating Vulnerability Database Updates Chapter 13 downloaded. The Scheduling page appears. Select Operations > Tools > Scheduling. Version 4. 2. To automate VDB updates: Access: Maint/Admin 1.9. if the scheduled installation task repeats daily. Click Add Task. you cannot schedule either pushes to managed sensors (on the Defense Center) or installs (on any appliance). the installation task will not succeed. Note that if you manually download an update to an appliance that cannot access the Support site. IMPORTANT! You cannot download the VDB using a scheduled task on a sensor.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

To view scheduled tasks using the calendar: Access: Maint/Admin 1. Click < to move back one month. You can perform the following tasks using the calendar view: • • Click << to move back one year. Select Operations > Tools > Scheduling. 2.9.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. The Scheduling page appears.1 Sourcefire 3D System Administrator Guide 459 . Version 4.

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

Click Save to save your edits. including the start time. only that task is deleted.9. all instances of the task are deleted. Later. 2. 4. To edit an existing scheduled task: Access: Maint/Admin 1. Deleting Scheduled Tasks There are two types of deletions you can perform from the Schedule View page. 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. Locate the task you want to edit in the table and click Edit. Click either the task that you want to edit or the day on which the task appears. This feature is especially useful if you want to test a scheduled task once to make sure that the parameters are correct. after the task completes successfully. If you delete an instance of a recurring task. The Scheduling page appears. The Task Details table containing the selected task or tasks appears.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.1 Sourcefire 3D System Administrator Guide 461 . The Edit Task page appears showing the details of the task you selected. the job name. If you delete a task that is scheduled to run once. Version 4. Your change are saved and the Scheduling page appears again. Select Operations > Tools > Scheduling. You can delete a specific one-time task that has not yet run or you can delete every instance of a recurring task. you can change it to a recurring task. Edit the task to meet your needs. once or recurring. 3. and how often the task runs. The remaining options are determined by the task you are editing. You cannot change the type of job.

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

and statistics for the Data Correlator and RNA processes for the current day.1 Sourcefire 3D System Administrator Guide 463 . see Understanding Health Monitoring on page 483. For more information. you can also use the health monitor to monitor disk usage and alert on low disk space conditions.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. on the Host Statistics page you can monitor basic host statistics. Version 4. all on a single page.9. You can also monitor both summary and detailed information on all processes that are currently running on the Defense Center or 3D Sensor. For example. intrusion event information. 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.

Version 4. Host Statistics Category Time Uptime Memory Usage Load Average Description The current time on the system. • Viewing Host Statistics Requires: Any The Statistics page lists the current status of following: • • • • general host statistics.1 Sourcefire 3D System Administrator Guide 464 . The number of days (if applicable). The percentage of system memory that is being used. Viewing System Process Status on page 468 describes how to view basic process status. and minutes since the system was last started. see the Data Correlator Process Statistics table on page 465 for details RNA process statistics (Defense Center only . hours. 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. see the Intrusion Event Information table on page 467 for details The Host Statistics table describes the host statistics listed on the Statistics page. see the Host Statistics table on page 464 for details Data Correlator statistics (Defense Center only .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. and 15 minutes. 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).requires RNA). 5 minutes. see the RNA Process Statistics table on page 466 for details intrusion event information (requires IPS). The average number of processes in the CPU queue for the past 1 minute.9.

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

Monitoring the System Viewing Host Statistics Chapter 14 The RNA Process Statistics table describes the statistics displayed for the RNA process. in kilobytes On 3D Sensors with IPS and on Defense Centers that manage sensors with IPS. the total number of events that have occurred in the past hour and the past day.9. Version 4. If you manage your sensor so that intrusion events are not stored locally.User (%) CPU Usage . This is also the case for 3D Sensors that cannot store events locally.1 Sourcefire 3D System Administrator Guide 466 . you can also view the time and date of the last intrusion event. 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. in kilobytes Average amount of memory used by the RNA process for the current day. and the total number in the database.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. no intrusion event information is listed on this page. RNA Process Statistics Category Packets Dropped (%) Mbits/Second Packets/Second CPU Usage .

The Defense Center version of the page is shown below.9.1 Sourcefire 3D System Administrator Guide 467 . Select Operations > Monitoring > Statistics. The Statistics page appears. 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. Version 4.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.

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

process is in uninterruptible sleep (usually Input/Output) • N . Select Operations > Monitoring > Statistics. unless the value is followed by m.process has a positive nice value • R . Values range between -20 (highest priority) and 19 (lowest priority) The memory size used by the process (in kilobytes.process is runnable (on queue to run) • S .process is in sleep mode • T .process is paging • X . The Statistics page appears. which indicates megabytes) The process state: • D .Monitoring the System Viewing System Process Status Chapter 14 The Process Status table describes each column that appears in the process list. which indicates megabytes) The amount of resident paging files in memory (in kilobytes.9.1 Sourcefire 3D System Administrator Guide 469 . unless the value is followed by m. Version 4. which is a value that indicates the scheduling priority of a process.process is being traced or stopped • W .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.process is defunct • < . 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.process is dead • Z .

listing general process status that includes the number and types of running tasks. select the device or devices you want to view process statistics for and click Select Devices. 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. Version 4. • • • • • • • • • 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. On the Defense Center. and swap information.Monitoring the System Viewing System Process Status Chapter 14 2. CPU. 3. see Understanding Running Processes on page 471. and specific information about each running process.9. memory. the current system uptime.1 Sourcefire 3D System Administrator Guide 470 . the current time. The process list expands. the system load average. Click the down arrow next to Processes. indicating a higher priority) Nice values indicate the scheduled priority for system processes and can range between -20 (highest priority) and 19 (lowest priority).

This table is not an exhaustive list of all processes that may run on an appliance.9.1 Sourcefire 3D System Administrator Guide 471 . 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. 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. The process list collapses. They ensure that services are available and spawn processes when required. Understanding Running Processes There are two different types of processes that run on an appliance: daemons and executable files.Monitoring the System Understanding Running Processes Chapter 14 To collapse the process list: Access: Maint/Admin Click the up arrow next to Processes. The System Daemons table lists daemons that you may see on the Process Status page and provides a brief description of their functionality. and checks for working SSL and valid certificate authentication. 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. and executable files are run when required. Daemons always run.

9. 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. Currently used only by health monitoring to send health events and alerts from a 3D Sensor to a Defense Center or. sfmb) to handle the request sftroughd Version 4. in a high availability environment.1 Sourcefire 3D System Administrator Guide 472 .requires RNA) sftimeserviced (Defense Center only) sfmbservice (requires IPS) Description Manages the Linux kernel update process. restarts any process that fails unexpectedly Manages reports Manages RNA reports Manages safe mode operation of the database. 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.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 . starts required processes. using an sftunnel connection to the appliance. which performs disk synchronization Manages Sourcefire 3D System database processes Manages the Network Time Protocol (NTP) process Manages all Sourcefire processes.

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.9.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. flow data. 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.

9.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. Ensures that the MAC address stays constant Handles access restriction based on changes made to the Access Configuration page. See Configuring the Access List for Your Appliance on page 325 for more information about access configuration. 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.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.

indicating that the appliance is active.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. correlating acquired data with the RNA fingerprint database. heartbeat used to maintain contact between a sensor and Defense Center Indicates a message broker process.9. 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.1 Sourcefire 3D System Administrator Guide 475 . 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. handles communication between Defense Centers and sensor. decodes and performs session reassembly. 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.

last day. The IPS page appears. number of megabits per second. performance statistics for those sensors are under reported.9. IPS performance statistics refer only to the data stored locally on the 3D Sensor.1 Sourcefire 3D System Administrator Guide 476 . last week. or average bytes per packet. word. To view the IPS performance statistics: Access: Maint/Admin Select Operations > Monitoring > Performance > IPS. average number of bytes per packet. or last month of operation. and the percent of packets uninspected by Snort. Version 4. The Defense Center version of the page is shown below. IMPORTANT! Because of the way traffic is processed on 3Dx800 sensors.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. 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. Graphs can be generated to reflect number of intrusion events per second. megabits per second. 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. These graphs can show statistics for the last hour.

From the Select Graph(s) list. It may also indicate that both segments have a drop rate of 50%. if you reload a graph quickly. The graph only represents the total % drop when there is a single detection resource assigned to a selected detection engine. Therefore. Version 4. The IPS page appears. select the type of graph you want to create. To generate IPS performance statistics graphs: Access: Maint/Admin 1. select the detection engines whose data you want to view. the data may not change until the next five-minute increment occurs. From the Select Device list. 2. The IPS Performance Statistics Graph Types table lists the available graph types. Select Operations > Monitoring > Performance > IPS. 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. 3.1 Sourcefire 3D System Administrator Guide 477 .9. The Defense Center version of the page is shown below. 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. then an average of 50% may indicate that one segment has a 90% drop rate and the other has a 10% drop rate.Monitoring the System Viewing IPS Performance Statistics Chapter 14 New data is accumulated for statistics graphs every five minutes.

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. 5. displaying the information you specified.Monitoring the System Viewing RNA Performance Statistics Chapter 14 4. select the time range you would like to use for the graph. From the Select Time Range list. To save the graph: Access: Maint/Admin Right-click on the graph and follow the instructions for your browser to save the image. Saving IPS Performance Statistics Graphs Requires: IPS or DC/MDC + IPS After you have generated an IPS performance statistics graph. The graph appears. Click Graph.9. 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. you can save the graph as a graphic file for later use. last day.1 Sourcefire 3D System Administrator Guide 478 .

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. 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. The RNA page appears. The RNA Performance Statistics Graph Types table lists the available graph types. Therefore.Monitoring the System Viewing RNA Performance Statistics Chapter 14 • • the number of packets. last week. New data is accumulated for statistics graphs every five minutes.9. 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. the data may not change until the next five-minute increment occurs. last day. in thousands. To access the RNA Performance page: Access: Maint/Admin Select Operations > Monitoring > Performance > RNA.1 Sourcefire 3D System Administrator Guide 479 . if you reload a graph quickly. or last month of operation.

1 Sourcefire 3D System Administrator Guide 480 . Version 4. the Select Graph(s) list adjusts to display the available graphs. the managed 3D Sensors.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 Defense Center. From the Select Target list. TIP! You can select multiple graphs by holding down the Ctrl or Shift keys while clicking on the graph type. The RNA page appears. last day. or last month. Depending on whether you select a detection engine or a sensor.9. Select Operations > Monitoring > Performance > RNA. or the detection engines that you want to include. 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. select the time range you would like to use for the graph. select the type of graph you want to create. From the Select Graph(s) list. last week. You can choose from last hour. 3. 4. From the Select Time Range list. 2.

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

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

For example. The Health Monitor page provides a visual summary of the status of all appliances on your system. You can set alerting thresholds to minimize the number of repeating alerts you receive. Individual appliance health monitors let you drill down into health details for a specific appliance. A health alert is an association between a standard alert and a health status level. You can also search for specific health events. events. You can use the health monitor to access health status information for the entire system or for a particular appliance. you can search for the CPU usage module and enter the percentage value.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 open a table view of occurrences of a specific event. if you need to make sure an appliance never fails due to hardware overload. For example. You can also configure email. disk. you can set up an email alert. Version 4. if you want to see all the occurrences of CPU usage with a certain percentage. or you can retrieve all the health events for that appliance. Pie charts and status tables on the Health Monitor page visually represent the health status for monitored appliances. 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 also view health events in the standard Sourcefire 3D System table view. then drill down into status details if needed.1 Sourcefire 3D System Administrator Guide 483 . From an individual appliance’s health monitor.9. or memory usage reaches the Warning level you configure in the health policy applied to that appliance. You can then create a health alert that triggers that email alert whenever CPU. SNMP or syslog alerting in response to health . so you can check status at a glance.

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

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

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

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

8. The Health Policy Configuration page appears. Configure settings on each module you want to use to test the health status of your appliances. Select Save to save the policy information.1 Sourcefire 3D System Administrator Guide 499 . 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.Using Health Monitoring Configuring Health Policies Chapter 15 7.9. including a list of the modules.

1 Sourcefire 3D System Administrator Guide 500 .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. The Health Policy Configuration . On the Health Policy Configuration page. For more information on applying health policies. You must apply the policy to each appliance for it to take effect. 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. Version 4. The maximum run time interval you can set is 99999 minutes.Policy Run Time Interval page appears.9. select Policy Run Time Interval. WARNING! Do not set a run interval of less than five minutes. see Applying Health Policies on page 528. 9. To configure a policy run time interval: Access: Maint/Admin 1. Disabled modules do not produce health status feedback. Click Save to save the policy. even if the policy that contains the module has been applied to an appliance.

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

In the Health Policy Configuration page. select the other module from the list at the left of the page. Select On for the Enabled option to enable use of the module for health status testing. 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. select Automatic Application Bypass Status. this module generates an alert. click Save Policy and Exit.9. you discard all changes. see Automatic Application Bypass on page 212. If a bypass occurs.Using Health Monitoring Configuring Health Policies Chapter 15 3. You must apply the health policy to the appropriate appliances 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. That status data feeds into the health monitor. 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. To temporarily save your changes to this module and switch to another module’s settings to modify. The Automatic Application Bypass Status page appears. Version 4. click Cancel. See Applying Health Policies on page 528 for more information. For more information on automatic application bypass.1 Sourcefire 3D System Administrator Guide 502 . if you click Cancel. all changes you made will be saved. To configure automatic application bypass monitoring status: Access: Maint/Admin 1. 2.

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

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

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

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

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

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

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

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

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

2. select Hardware Alarms. To configure Hardware Alarm health module settings: Access: Maint/Admin 1. all changes you made will be saved. you discard all changes.1 Sourcefire 3D System Administrator Guide 513 . You must apply the health policy to the appropriate sensors if you want your settings to take effect. In the Health Policy Configuration page. If you click Save Policy and Exit when you are done. 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. For more information on the hardware status conditions that can cause hardware alerts on 3D9900 sensors. click Save Policy and Exit. Version 4. You have three options: • • • To save your changes to this module and return to the Health Policy page. That status data feeds into the health monitor. 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. The Health Policy Configuration . 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. the status classification for that module changes to Critical.Hardware Alarm monitor page appears. See Applying Health Policies on page 528 for more information. Configuring Hardware Monitoring Requires: DC/MDC Supported Platforms: 3Dx800.Using Health Monitoring Configuring Health Policies Chapter 15 3. see Interpreting Hardware Alert Details for 3D9900 Sensors on page 560. To return to the Health Policy page without saving any of your settings for this module.9. if you click Cancel. click Cancel.

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

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

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

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

all changes you made will be saved. To return to the Health Policy page without saving any of your settings for this module. click Save Policy and Exit.1 Sourcefire 3D System Administrator Guide 518 . you discard all changes. See Applying Health Policies on page 528 for more information.9. 2. Select On for the Enabled option to enable use of the module for health status testing. To configure Link State Propagation health module settings: Access: Maint/Admin 1. 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. Version 4.Link State Propagation monitor page appears. The Health Policy Configuration . select Link State Propagation. select the other module from the list at the left of the page. 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. if you click Cancel.Using Health Monitoring Configuring Health Policies Chapter 15 5. You must apply the health policy to the appropriate sensors if you want your settings to take effect. If a link state propagates to the paired interface. If you click Save Policy and Exit when you are done. On the Health Policy Configuration page. 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. 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

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. MDC3000. 3D3500. 3Dx800. and 3D6500 Version 4. 3D4500.Using Health Monitoring Configuring Health Policies Chapter 15 Applicable health modules for various appliances are listed in the Health Modules Applicable to Appliances table.1 Sourcefire 3D System Administrator Guide 531 . 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.9.

Modify settings as needed.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.1 Sourcefire 3D System Administrator Guide 532 . The Health Policy page appears. Click Health Policy in the health monitor toolbar. 2. The Health Monitor page appears. 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. Select Operations > Monitoring > Health.9. 4. 3D Sensors with RNA To edit a health policy: Access: Maint/Admin 1. 3. Click Edit next to the policy you want to modify. with the Policy Run Time Interval settings selected. The Health Policy Configuration page appears.

click Cancel. In addition. 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. select the other module from the list at the left of the page. If you delete a policy that is still applied to an appliance.9. you discard all changes. if you delete a health policy that is applied to a sensor. To return to the Health Policy page without saving any of your settings for this module. Deleting Health Policies Requires: DC/MDC You can delete health policies that you no longer need. if you click Cancel. You have three options: • • • 6.1 Sourcefire 3D System Administrator Guide 533 . If you click Save Policy and Exit when you are done.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. 5. click Save Policy and Exit. any health monitoring alerts in effect for the sensor remain active until you Version 4. Reapply the policy to the appropriate appliances as described in Applying Health Policies on page 528. all changes you made will be saved.

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

9. Once the blacklist settings take effect. 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. TIP! You can blacklist 3D Sensors only from a Defense Center. you can blacklist the policy. To blacklist an entire health policy or group of appliances: Access: Maint/Admin 1.Using Health Monitoring Using the Health Monitor Blacklist Chapter 15 RNA host licenses on an appliance. The newly re-registered sensor remains blacklisted. Version 4. Health Monitor blacklist settings are system settings. then delete it and later re-register it with the Defense Center. Note that if your Defense Center is in a high availability configuration. you can blacklist the group of appliances. click Blacklist. A blacklist icon ( ) and a notation are visible once you expand the view for a blacklisted or partially blacklisted appliance. you can blacklist a managed sensor on one HA peer and not the other. 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. For more information on expanding that view. the appliances report a disabled status in the Appliance Status Summary. not a Master Defense Center. 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. IMPORTANT! On a Defense Center. The Blacklist page appears. the blacklist settings remain persistent. You cannot blacklist intrusion agents. 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. Select Operations > Monitoring > Health. The Health Monitor page appears. 2. you can blacklist the RNA Host License Limit status messages until you install a new license with more hosts.1 Sourcefire 3D System Administrator Guide 535 . If you need to disable the results of a group of appliances’ health monitoring. On the toolbar. Therefore if you blacklist a sensor. see Using the Health Monitor on page 545.

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

To blacklist an individual appliance. Defense Center Only Specific health policy modules operate for a Defense Center. For some modules. 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. The page refreshes then indicates the blacklisted state of the appliances. you can blacklist the Traffic Status module for that detection engine. When blacklisting modules for Defense Centers.9. 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.1 Sourcefire 3D System Administrator Guide 537 . Note that modules that allow you to select a specific detection engine have an arrow next to the module. 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. For example. then click Apply. When any part of a module is blacklisted. select and expand a category folder. select the box next to the appropriate appliance. the interface indicates the following information in parentheses after each module with detection engines: number of blacklisted detection engines/maximum number of detection engines. Click Edit and see Blacklisting a Health Policy Module on page 537 to blacklist individual health policy modules. 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. In addition.

Make sure that you keep track of individually blacklisted modules so you can reactivate them when you need them. see the Health Modules Applicable to Appliances table on page 531. When blacklisting modules for Master Defense Centers. 2. 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. Version 4. You may miss necessary warning or critical messages if you accidentally leave a module disabled. TIP! Once the blacklist settings take effect. The Health Monitor page appears.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. On the toolbar. Select Operations > Monitoring > Health. To blacklist an individual health policy module: Access: Maint/Admin 1.9. click Blacklist.1 Sourcefire 3D System Administrator Guide 538 . The Blacklist page appears. 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.

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

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

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

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

Click Load to load the configured settings for the selected alert.1 Sourcefire 3D System Administrator Guide 543 . Click Health Monitor Alerts in the health monitor toolbar. 5. 2.9. Select Operations > Monitoring > Health. For more information. 3. 6. health module. see Creating Health Monitor Alerts on page 540. To edit health monitor alerts: Access: Admin 1. Select the alert you want to modify in the Active Health Alerts list. A message appears.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. Click Save to save the modified health alert. Version 4. 4. Modify settings as needed. The Health Monitor page appears. The Health Monitor Alerts page appears. or alert associated with the health monitor alert. indicating if the alert configuration was successfully saved.

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

9. Version 4. The Status table provides a count of the managed appliances for this Defense Center by overall health status. The Health Monitor then generates health events to indicate the current status of any aspects of appliance health that you chose to monitor.Reviewing Health Status Chapter 16 Administrator Guide You can obtain information about the health of your Sourcefire 3D System through the Health Monitor. indicating the percentage of appliances currently in each health status category. 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.1 Sourcefire 3D System Administrator Guide 545 . For more information on viewing the health status of your appliance. Administrators can create and apply a health policy to an appliance. plus the Defense Center. The pie chart supplies another view of the health status breakdown.

If the arrow points right. the appliance list is hidden. Click Health Monitor on the toolbar. TIP! If the arrow in the row for a status level points down.9. 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.Reviewing Health Status Using the Health Monitor Chapter 16 To use the health monitor: Access: Maint/Admin/ Any Analyst except Restricted 1.1 Sourcefire 3D System Administrator Guide 546 . the appliance list for that status shows in the lower table. 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. The Health Monitor page appears. 2.

or that the appliance is currently unreachable.Reviewing Health Status Using Appliance Health Monitors Chapter 16 Interpreting Health Monitor Status Available status categories. Normal. Contact your technical support representative to obtain an update to the health monitoring module. IMPORTANT! Your browser session will not be automatically timed out while you are viewing the Health Monitor page. that the appliance does not have a health policy applied to it.1 Sourcefire 3D System Administrator Guide 547 . Indicates that all health modules on the appliance are running within the limits configured in the health policy applied to the appliance. by severity. Version 4.9. Indicates that all health modules on the appliance are running within the limits configured in the health policy applied to the appliance. Indicates that an appliance is disabled or blacklisted. Indicates that the critical limits have been exceeded for at least one health module on the appliance and the problem has not been corrected. and Disabled. 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. Critical. include Error. including modules that were in a Critical or Warning state. 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. Warning. Indicates that warning limits have been exceeded for at least one health module on the appliance and the problem has not been corrected. as described in the Health Status Indicator table.

TIP! If the arrow in the row for a status level points down. For more information. click the arrow in that status row. click the color for the event status category you want to view. 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 name of the appliance for which you want to view details in the health monitor toolbar. The Alert Detail list toggles the display to show or hide events.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. in the Module Status Summary graph. Optionally. the appliance list for that status shows in the lower table. Select Operations > Monitoring > Health. To show the list of appliances with a particular status. The Health M