P. 1
Sourcefire_3D_System_Administrator_Guide_v4.9.1

Sourcefire_3D_System_Administrator_Guide_v4.9.1

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 You can. on the Defense Center. Version 4. The following graphic shows the Defense Center version of the Default Workflows section. but also on your user role. As another example.9.1 Sourcefire 3D System Administrator Guide 33 . For general information on workflows. see Understanding and Using Workflows in the Analyst Guide. however. on a 3D Sensor without an IPS license. you can only configure the default workflow for the audit log. For example. change the default workflow for each event type using the Default Workflows sections of the Event View Settings page.

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

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

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

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

DC1000. Refer to Platform Requirements Conventions on page 38 for the meaning of the Requires statement at the beginning of each section. 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.9. Virtual Defense Center. All platform information is formatted with an orange typeface. Refer to Access Requirements Conventions on page 39 for the meaning of the Access statement at the beginning of each procedure. or DC3000 appliance used as a Defense Center Version 4.Introduction to the Sourcefire 3D System Documentation Conventions Chapter 1 Documentation Conventions This documentation includes information about which Sourcefire 3D System components are required for each feature and which user roles have permission to complete each procedure. Platform 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 . Any DC Any appliance with any combination of licenses A DC500. Platform requirement information for specific aspects of a feature is provided where needed.

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

A “+” conjunction indicates that the platforms are required in combination. 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.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. Rule thresholding in the packet view provides an example of required combined access roles. For example. The Access setting for the procedure in the Working with the Hosts Network Map topic is Any RNA/Admin.9. to view the Hosts network map.

without changing your user input. the Access setting for the procedure in the Setting Threshold Options within the Packet View topic is IPS + P&R Admin/Admin.0. 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.0 Number of IP Addresses 16.0. 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.777 .0. For example.0 10. As a result.31.0 192.0/8 172. Version 4.168.255.255. 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.255.0/12 192.9. but the web interface continues to display 10. the Sourcefire 3D System uses 10.255.0.255 192.Introduction to the Sourcefire 3D System IP Address Conventions Chapter 1 from the packet view.0 255.3/8.0. For example.168. the following table lists the private IPv4 address spaces in CIDR notation.255 Subnet Mask 255.0/8.0.0. the Sourcefire 3D System uses only the masked portion of the network IP address you specified.048.1.1 Sourcefire 3D System Administrator Guide 41 . CIDR Notation Syntax Examples CIDR Block 10.0.0.2.0 172.2.255 172. variables. if you type 10.255.240.16.216 1.0.0.0.16.168.0/16 IP Addresses in CIDR Block 10.1.0.0.3/8.536 When you use CIDR notation to specify a range of IP addresses.576 65.0 255.

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

To perform the initial setup of a Virtual 3D Sensor. Note that if you purchased your sensor prior to 2008. Consult your original documentation or contact Sourcefire Support for information about performing the initial setup on those sensor models. 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.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. 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.9. Newer models of the 3D Sensor. called Series 2 sensors. provide a rapid set up feature and a status page. you may have a Series 1 3D Sensor. Version 4. see the Sourcefire 3D System Virtual Defense Center and 3D Sensor Installation Guide.1 Sourcefire 3D System Administrator Guide 43 . you are presented with a series of start-up pages.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

9. over the dashboard time range. see Understanding Widget Preferences on page 64. For more information. For more information. Note that because the Defense Center does not automatically apply a health policy to managed sensors.1 Sourcefire 3D System Administrator Guide 67 . Version 4. see Using the Health Monitor on page 545. you must manually apply a health policy or their status appears as Disabled. Understanding the Compliance Events Widget Requires: DC/MDC The Compliance Events widget shows the average events per second by priority. 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. 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.Using Dashboards Understanding the Predefined Widgets Chapter 3 Understanding the Appliance Status Widget Requires: DC/MDC The Appliance Status widget indicates the health of the appliance and of any appliances it is managing.

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

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

Optionally.9. Microsoft Windows. constraining the first example (operating systems Version 4. either one of the predefined searches delivered with your appliance or a custom search that you created. 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. how many unique versions of Linux. 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. On the other hand. and so on).1 Sourcefire 3D System Administrator Guide 70 . if you are using Sourcefire RNA as part of your deployment. you can further constrain the widget using a saved search.Using Dashboards Understanding the Predefined Widgets Chapter 3 For example. For example. Mac OS X.

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

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

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

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

(The predefined dashboards on the Master Defense Center and 3D Sensor do not include Custom Analysis widgets. Displays the most active services on your monitored network. by classification. Displays the most active ports on your monitored network. based on the number of detected flows. based on the number of flows where the host was the responder in the session. Displays the most frequently occurring types of intrusion events. by classification. based on the number of detected flows. where the packet was not dropped as part of the event.) . by application type. based on the number of flows where the host initiated the session.9. Displays counts for the most frequently occurring intrusion events. Displays the most active client applications on your monitored network.Using Dashboards Understanding the Predefined Widgets Chapter 3 each preset. where the packet was dropped.1 Sourcefire 3D System Administrator Guide 75 . Displays the most active hosts on your monitored network. 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 active hosts on your monitored network. 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 common operating system. based on the number of hosts on the network running services made by that vendor. Displays the most common RNA service vendors. Displays the most active hosts on your monitored network. based on event classification. Displays the most frequently occurring types of intrusion events. based on the number of hosts running each operating system within your network.1 Sourcefire 3D System Administrator Guide 76 . Displays a count of intrusion event requiring analysis. based on the number of intrusion events occurring on high criticality hosts. based on the number of intrusion events where the host was the targeted host in the flow that caused the event. based on the number of intrusion events where the host was the attacking host in the flow that caused the event. based on frequency of intrusion events. Displays the most active hosts on your monitored network. Displays the most active hours of the day.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.9. 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. over the dashboard time range.

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

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

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. Intrusion Event Analysts cannot view RNA events.1 Sourcefire 3D System Administrator Guide 79 .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. For example. On widgets configured to show flow data over time. remember that not all users can view data of all event types.9. constrained by the widget preferences. • For information on working with specific event types. depending on how you configured the widget: • On widgets configured to show relative occurrences of events (that is. if you are using a dashboard imported from another appliance. click any event to view associated events constrained by the widget preferences. For Version 4. as well as by that event. remember that not all appliances have access to data of all event types. depending on the user’s account privileges. click the View All icon in the lower right corner of the widget to view all associated events. If you are configuring the widget on a shared dashboard. You can also click the View All icon in the lower right corner of the widget to view all associated events. bar graphs). Similarly. constrained by 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. or even delete the widget. Remember that only you can access searches that you have saved as private. save the dashboard as private. as well as whether it displays the current disk usage or collected disk usage statistics over the dashboard time range.9. The widget preferences also control how often the widget updates.Using Dashboards Understanding the Predefined Widgets Chapter 3 example. the widget resets to not using the search when another user logs in. It also shows the capacity of each partition. however. You enable or disable the Custom Analysis widget from the Dashboard settings in your system policy. see Configuring Dashboard Settings on page 331. or you can show these plus the /boot partition usage by modifying the widget preferences. You can configure the widget to display just the root (/) and /volume partition usage. the Master Defense Center does not store flow data. This affects your view of the widget as well. If your dashboard includes a Custom Analysis widget that displays data that you cannot see. For more information. Note. save the dashboard as private. Version 4. see Understanding Widget Preferences on page 64. For more information. 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.1 Sourcefire 3D System Administrator Guide 80 . If you configure the widget on a shared dashboard and constrain its events using a private search. the widget indicates that you are unauthorized to view the data. If you want to make sure that this does not happen. If you want to make sure that this does not happen.

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

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

and that have not been evaluated. Version 4. including white lists that are no longer in active compliance policies. delete the unused white lists. 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.9. by modifying the widget preferences. for all compliance white lists that you have created. You can click the pie chart to view the host violation count. You can also use the widget preferences to specify which of three different styles you want to use to display network compliance. and that have not been evaluated. see Viewing White List Violations in the Analyst Guide. or for a specific white list. Note that if you choose to display network compliance for all white lists.Using Dashboards Understanding the Predefined Widgets Chapter 3 number of hosts that are compliant. the widget considers a host to be non-compliant if it is not compliant with any of the white lists on the Defense Center. non-compliant. For more information. 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. non-compliant.1 Sourcefire 3D System Administrator Guide 83 .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

9. information is transmitted between the Defense Center and the sensor over a secure.1 Sourcefire 3D System Administrator Guide 102 . When you manage a sensor (or a software sensor). SSL-encrypted TCP tunnel. For details on DC500 database limitations see Database Event Limits on page 333. 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. You can also use a DC500 to manage Sourcefire 3D Sensor software on approved platforms. as well as intrusion agents and RNA software on approved platforms.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. you can see a read-only version of the policy on the Defense Center’s web interface. Version 4.

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

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

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

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

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

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

9.1 Sourcefire 3D System Administrator Guide 109 . See the Supported Features for RNA Software for Red Hat Linux table for more information. not all of the features function in the same manner.Using the Defense Center Management Concepts Chapter 4 Managing RNA Software for Red Hat Linux Requires: DC RNA Software for Red Hat Linux provides many of the features found on 3D Sensors with RNA. However. 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. However.9. 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. See the Supported Features for RNA on Crossbeam table for more information.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. because the Crossbeam sensors do not have a user interface and because configuration and event data cannot be stored on Version 4.1 Sourcefire 3D System Administrator Guide 110 .

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

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

you set up a two-way.9. and then use a different unique NAT ID when adding the Miami 3D Sensor.1 Sourcefire 3D System Administrator Guide 113 .Using the Defense Center Working with Sensors Chapter 4 be unique. However. SSL-encrypted communication channel between the Defense Center and the sensor. it generates events and sends them to the Defense Center using the same channel. 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 can create the following policies on your Defense Center and apply them to managed sensors: • • • health policies system policies RUA policies Version 4. 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. Each NAT ID has to be unique among all NAT IDs used to register sensors on the Defense Center.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

see Editing the Management Virtual Network on page 385. For information about editing the remote management communications between the two appliances.1 Sourcefire 3D System Administrator Guide 155 . The Peer Manager page appears.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. Version 4. 2. Click Enable to disable the communications channel between the two Defense Centers.9.

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

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

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

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

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

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

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

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

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

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

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

Type the IP address or the hostname of the Defense Center you want to add in the Host field. Under Filter Configuration. type the same value in the Unique NAT ID (optional) field.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 10. type the same one-time use registration key that you used in step 6.9. Click New Defense Center. If you chose to send compliance events to the Master Defense Center. The New Defense Center page appears. IMPORTANT! You must select at least one type of flag if you want to send intrusion events. In that case. you can send events or events and packet data. In the Registration Key field. See Editing the Event Filter Configuration on page 176 for more information. 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. If you used an unique NAT ID in step 6. Version 4. white list events are also sent.1 Sourcefire 3D System Administrator Guide 167 . 13. use both the Registration Key and the Unique NAT ID fields 12. You can leave the Host field empty if the 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. Note that if you select intrusion events. 11. 14.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

1 Sourcefire 3D System Administrator Guide 190 . It also indicates the maximum number of detection resources you can assign a single detection engine. RNA and RUA. The Combination Restrictions column indicates the permitted combinations of detection resources that you can allocate to detection engines on the same sensor. can be any type No restrictions No restrictions No restrictions No restrictions No restrictions No restrictions No restrictions No restrictions No restrictions No restrictions Version 4. 3D Sensors can run combinations of IPS. can be any type Maximum of two.9.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 Optimal column indicates the per-sensor total number of detection resources you should use if you want to maximize the performance of the sensor. • • 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. The Maximum column indicates the total number of detection resources available on the sensor.

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

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

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

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

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

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

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

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

10.30. 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. see Creating New Policy-Specific Variables in the Analyst Guide. you can use detection engine-specific variable values to tailor your detection capabilities to more closely match your infrastructure. For example. any detection engines in the group are automatically ungrouped. hosts in your network’s DMZ in the range 10.90. 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.0. Click Delete next to the name of the detection engine group. 10.10.10. The Detection Engines page appears. 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. However. Select Operations > Configuration > Detection Engines > Detection Engines. The detection engine group is deleted.0/24).1 Sourcefire 3D System Administrator Guide 199 .0/16). For information on policy-specific variables.0/16 In the detection engine named DE_DMZ: HOME_NET = 10.10. which are specific to the policy in which they are created. Using Variables within Detection Engines Requires: IPS or DC/MDC + IPS A system default variable sets a variable value on your Sourcefire 3D Sensor or Defense Center that IPS uses by default unless it is overridden by a policy-specific or detection engine-specific value for the same variable.0/24 If you later create another detection engine that monitors the rest of your network. You can define HOME_NET in your system default variable to encompass your internal address range (for example. they are not deleted.9.90. In the system default variable used in the intrusion policy: HOME_NET = 10. if you have created your detection engines so that one detection engine monitors one class of hosts (in this example. which includes a mixed address space. 2.0. hosts in your accounting department in the address range 10. When you apply an intrusion policy to that detection engine. To delete a detection engine group: Access: Admin 1.10.0/24 In the detection engine named DE_ACCT: HOME_NET = 10.0/24) and another monitors a different class (for example. you can use the system default Version 4.10.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.30.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

1 Sourcefire 3D System Administrator Guide 242 . 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. Version 4.9. As with custom report profiles that you create (see Creating a Report Profile on page 246). save the report with the new values. and run the report manually or automatically. You can modify field settings as appropriate.

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

Working with Event Reports Understanding Report Profiles Chapter 7 The Blocked Events report profile provides information on blocked intrusion events for all detection engines for the past twenty-four hours.1 Sourcefire 3D System Administrator Guide 244 .9. sliding time window Quick Enabled Enabled Enabled Enabled Disabled Disabled The High Priority Events report profile provides information on intrusion events as well as the host criticality of hosts involved in the intrusion events for the past Version 4. This report profile is available on the Defense Center or on a 3D Sensor with IPS. 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.

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

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

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

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

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

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

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

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

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

unless you change the user permissions manually. for a list of users. For users with either internal or external authentication. 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.Managing Users Understanding Sourcefire User Authentication Chapter 8 Access Protocol (LDAP) directory server or a Remote Authentication Dial In User Service (RADIUS) authentication server.1 Sourcefire 3D System Administrator Guide 265 . you can control user permissions. Version 4. Users with external authentication receive the permissions either for the group or access list they belong to.9.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

a shell access attribute value of sAMAccountName must be set for shell access to work on a Microsoft Active Directory server.12. a shell access filter has been specified for this server.Managing Users Managing Authentication Objects Chapter 8 • This example also has group settings in place.DC=it. allowing only those users who have a common name attribute value of jsmith to log into the appliance using a shell account. Version 4. • As in the OpenLDAP server.DC=example.5.4. as noted above.9. with a backup server that has an IP address of 10.DC=com. 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. However.12.3.3.1 Sourcefire 3D System Administrator Guide 284 . 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=it. • This example shows a connection using a base distinguished name of OU=security. A certificate has been uploaded to allow the SSL connection.DC=com for the security organization in the information technology domain of the Example company.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. 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. Note that all objects in the directory are checked because no base filter is set. • 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. However. 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.1 Sourcefire 3D System Administrator Guide 285 . note that this server does have a base filter of (cn=*smith). no UI access attribute is specified. the Server Port is set to 636.DC=example.9. Version 4. • • The user name template shown uses the uid attribute value as the user name. The filter restricts the users retrieved from the server to those with a common name ending in smith. Because user names can be retrieved from the uid attribute on this server. the uid attribute is named as the Shell Access Attribute and the Same as Base Filter option for the shell access filter is set.

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

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

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

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

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

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

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

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

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

Select Operations > User Management. Click Edit next to the user you want to modify.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. 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. 2.1 Sourcefire 3D System Administrator Guide 307 . The Edit User page appears.9. Version 4. 3. for users with event analyst roles. You can specify this information only after the user is added. Optionally. • • • 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. See Adding New User Accounts on page 300 for information about adding new user accounts. The User Management page appears. Modify the account or accounts as needed: • See Managing Externally Authenticated User Accounts on page 302 for a description of how users can be authenticated through external servers. See Managing User Password Settings on page 303 for information on changing password settings for internally authenticated users.

view the network map When these platforms are present.1 Sourcefire 3D System Administrator Guide 308 ...9.. The Restricted Event Analyst Settings table shows the correlation between platform and access requirements for the restricted event analyst. DC + RNA Set this data set or data sets to Show All or to a specific search One or more of the following: • Host Attributes Data • RNA Client Applications Data • RNA Hosts Data • RNA Services Data • Vulnerabilities Data view network discovery events view hosts view host attributes view services view vulnerabilities view client applications view flow data view compliance events view white list events view white list violations view users or user events view intrusion events use the clipboard DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RUA IPS IPS RNA Events Data RNA Hosts Data Host Attributes Data RNA Services Data Vulnerabilities Data RNA Client Applications Data Flow Data Compliance Events Data White List Events Data White List Violations Data Users Data Intrusion Events Data N/A . Restricted Event Analyst Settings To allow the restricted event analyst to.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..

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

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

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

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

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.1 Sourcefire 3D System Administrator Guide 313 . Analysis & Reporting Menu Menu Admin Maint RNA/ RNA-RO Event Analyst X IPS/ IPS-RO Event Analyst X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Restricted Event Analyst P&R Admin Event Summary Intrusion Event Statistics Event Graphs Dashboards RNA Statistics Flow Summary IPS Events Reviewed Events Clipboard Incidents RNA Network Map | Hosts Network Map | Network Devices Network Map | Services Network Map | Vulnerabilities Network Map | Host Attributes X X X X X X X X X X X X X X X X X X Version 4.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.

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

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

RNA Event Analyst. or Maintenance access can not see the Policy & Response menu at all.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. Users with Intrusion Event Analyst.9. 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.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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

See Uploading Backups from a Local Host on page 420 for information about uploading backup files from a local host. if you are using a Series 2 Defense Center. Additionally. data correlation is temporarily suspended. See Performing Sensor Backup with the Defense Center on page 419 for information about backing up managed sensors with the Defense Center. On Series 2 Defense Centers. 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. See Restoring the Appliance from a Backup File on page 421 for information about how to restore a backup file to the appliance. As an alternative or if your backup file is larger than 4GB. When your backup task is collecting RNA events. see Managing Remote Storage on page 393. Version 4. 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. the backup file can be saved to a remote location. See the following sections for more information.Using Backup and Restore Creating Backup Files Chapter 12 You can save backup files to the appliance or to your local computer. 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. you can use remote storage as detailed in Managing Remote Storage on page 393. in addition to event and packet data. 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.9. if needed.1 Sourcefire 3D System Administrator Guide 414 . • • • • • See Creating Backup Files on page 414 for information about backing up files from the appliance.

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

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

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

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

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

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

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

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

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

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

9. 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. Version 4. You should always schedule tasks like these to run during periods of low network use.1 Sourcefire 3D System Administrator Guide 425 . 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.Scheduling Tasks Chapter 13 Administrator Guide You can schedule many different types of administrative tasks to run at scheduled times.

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

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

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

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

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

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

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

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

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

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

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

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

9. 2. The Add Task page appears. Click Add Task. To automate VDB updates: Access: Maint/Admin 1. you can use the Once option to download and install VDB updates during off-peak hours after you learn that an update has been released. Note that if you manually download an update to an appliance that cannot access the Support site. You must download the VDB on the Defense Center and push it to the sensor. However.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. you cannot schedule either pushes to managed sensors (on the Defense Center) or installs (on any appliance). 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 installation task will not succeed. Version 4. The Scheduling page appears. Select Operations > Tools > Scheduling. IMPORTANT! You cannot download the VDB using a scheduled task on a sensor. it will install the downloaded VDB update when it runs the next day. If you want to have more control over this process. if the scheduled installation task repeats daily.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

You can perform the following tasks using the calendar view: • • Click << to move back one year. Select Operations > Tools > Scheduling.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 .9. Click < to move back one month. 2. Version 4. To view scheduled tasks using the calendar: Access: Maint/Admin 1.

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

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

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

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

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

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

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

Intrusion Event Information Statistic Last Alert Was Total Events Last Hour Total Events Last Day Total Events in Database Description The date and time that the last event occurred The total number of events that occurred in the past hour The total number of events that occurred in the past twenty-four hours The total number of events in the events database To view the Statistics page: Access: Maint/Admin 1. The Defense Center version of the page is shown below. Select Operations > Monitoring > Statistics.9. 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.1 Sourcefire 3D System Administrator Guide 467 . The Statistics page appears.

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

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

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

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

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

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.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. runs in the background to provide SSH access to the appliance Manages the system logging (syslog) process Understanding Executables and System Utilities There are a number of executables on the system that run when executed by other processes or through user action. flow data. supports extended set of regular expressions not supported in standard grep Version 4.1 Sourcefire 3D System Administrator Guide 473 . 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.9. The System Executables and Utilities table describes the executables that you may see on the Process Status page.

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

indicating that the appliance is active. handles communication between Defense Centers and sensor. 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.1 Sourcefire 3D System Administrator Guide 475 .9. decodes and performs session reassembly. 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.Monitoring the System Understanding Running Processes Chapter 14 System Executables and Utilities (Continued) Executable ps RNA (requires RNA) Description Utility that writes process information to standard output Captures packets. which allows users other than root to run executables Utility that displays information about the top CPU processes Utility that can be used to change the access and modification times of specified files sed sfheartbeat sfmb sfsnort (requires IPS) sh shutdown sleep smtpclient snmptrap ssh sudo top touch Version 4. correlating acquired data with the RNA fingerprint database. heartbeat used to maintain contact between a sensor and Defense Center Indicates a message broker process.

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

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

you can save the graph as a graphic file for later use. Saving IPS Performance Statistics Graphs Requires: IPS or DC/MDC + IPS After you have generated an IPS performance statistics graph. 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 choose from last hour.Monitoring the System Viewing RNA Performance Statistics Chapter 14 4.9. The graph appears. select the time range you would like to use for the graph. Click Graph.1 Sourcefire 3D System Administrator Guide 478 . 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. last week. displaying the information you specified. 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. 5. last day. or last month.

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

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

each graph appears on the page. Click Graph. you can save the graph as a graphic file for later use. To save the graph: Access: Maint/Admin 1.9. 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.Monitoring the System Viewing RNA Performance Statistics Chapter 14 5.1 Sourcefire 3D System Administrator Guide 481 . 2. The graph appears. Create an RNA performance statistic graph as described in Generating RNA Performance Statistics Graphs on page 479. displaying the information you specified. Version 4. If you selected multiple graphs.

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

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

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

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

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

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

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

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

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

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

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

9. In the Warning Threshold Celsius field. If the CPU usage on the monitored appliance exceeds the Critical limit. the status classification for that module changes to Warning. if you click Cancel. See Applying Health Policies on page 528 for more information. To return to the Health Policy page without saving any of your settings for this module. 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. in Celsius. Use the CPU Usage health status module to set CPU usage limits. The maximum percentage you can set for either limit is 100 percent. Note that this module is not available for health policies applied to 3D9900 sensors. To temporarily save your changes to this module and switch to another module’s settings to modify. If the CPU usage on the monitored appliance exceeds the Warning limit. click Save Policy and Exit. enter the number of degrees. all changes you made will be saved. and the Critical limit must be higher than the Warning limit. that should trigger a warning health status.Using Health Monitoring Configuring Health Policies Chapter 15 2. If you click Save Policy and Exit when you are done. click Cancel.1 Sourcefire 3D System Administrator Guide 504 . select the other module from the list at the left of the page. You have three options: • • • To save your changes to this module and return to the Health Policy page. enter the number of degrees. 4. that should trigger a critical health status. in Celsius. the status classification for that module changes to Critical. you discard all changes. 3. In the Critical Threshold Celsius field. Select On for the Enabled option to enable use of the module for health status testing. Version 4. 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. 5.

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

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

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

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

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

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

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

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

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

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

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

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

You must apply the health policy to the appropriate sensors if you want your settings to take effect.1 Sourcefire 3D System Administrator Guide 518 . To return to the Health Policy page without saving any of your settings for this module. if you click Cancel. click Cancel. On the Health Policy Configuration page. If a link state propagates to the paired interface. To temporarily save your changes to this module and switch to another module’s settings to modify. If you click Save Policy and Exit when you are done. The Health Policy Configuration . 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. click Save Policy and Exit. you discard all changes.Link State Propagation monitor page appears. You have three options: • • • To save your changes to this module and return to the Health Policy page. the status classification for that module changes to Critical and the state reads: Module Link State Propagation: ethx_ethy is Triggered where x and y are the paired interface numbers. Version 4. 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.Using Health Monitoring Configuring Health Policies Chapter 15 5. To configure Link State Propagation health module settings: Access: Maint/Admin 1. all changes you made will be saved. 2.9. See Applying Health Policies on page 528 for more information. select Link State Propagation.

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

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

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

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

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

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

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

Click Edit and see Blacklisting a Health Policy Module on page 537 to blacklist individual health policy modules. you can blacklist the Traffic Status module for that detection engine. For some modules. 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. The page refreshes then indicates the blacklisted state of the appliances. Note that modules that allow you to select a specific detection engine have an arrow next to the module. In addition. Defense Center Only Specific health policy modules operate for a Defense Center.9. When any part of a module is blacklisted.1 Sourcefire 3D System Administrator Guide 537 . you can blacklist that module for a specific detection engine. select and expand a category folder. You may want to do this to prevent events from the module from changing the status for the appliance to warning or critical. 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. For example.Using Health Monitoring Using the Health Monitor Blacklist Chapter 15 4. select the box next to the appropriate appliance. To blacklist an individual appliance. then click Apply. the interface indicates the following information in parentheses after each module with detection engines: number of blacklisted detection engines/maximum number of detection engines. the line for that module appears in boldface type in the Defense Center web interface. Blacklisting a Health Policy Module Requires: DC/MDC You can blacklist individual health policy modules on appliances. When blacklisting modules for Defense Centers.

Version 4.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. click Blacklist.1 Sourcefire 3D System Administrator Guide 538 . Select Operations > Monitoring > Health. When blacklisting modules for Master Defense Centers. On the toolbar. TIP! Once the blacklist settings take effect. only include the following modules: • • • • • • • CPU Usage Data Correlator Process Defense Center Status Disk Usage Event Stream Status Memory Usage Power Supply For details about applicable modules on all appliances. The Blacklist page appears. You may miss necessary warning or critical messages if you accidentally leave a module disabled. Make sure that you keep track of individually blacklisted modules so you can reactivate them when you need them. To blacklist an individual health policy module: Access: Maint/Admin 1. The Health Monitor page appears. 2.9. see the Health Modules Applicable to Appliances table on page 531. 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. or Model. You can associate an existing alert with health event levels to cause that alert to trigger when health events of a particular level occur. 5. 4. The health policy modules appear. Configuring Health Monitor Alerts You can set up alerts to notify you through email. Expand the detection engine list by clicking on the arrow next to modules with detection engine lists.1 Sourcefire 3D System Administrator Guide 539 . then select each detection engine for which you want to blacklist the module. system log when the status changes for the modules in a health policy. Click Save.9. through SNMP or through the . Sort by Group. You have two options: • • Select each module that you want to blacklist. then click Edit to display the list of health policy modules.Using Health Monitoring Configuring Health Monitor Alerts Chapter 15 3. Policy.

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

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

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

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

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

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

the appliance list is hidden. TIP! If the arrow in the row for a status level points down. 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. 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. the appliance list for that status shows in the lower table. If the arrow points right.9.1 Sourcefire 3D System Administrator Guide 546 . The Health Monitor page appears. 2. Click Health Monitor on the toolbar.

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

To show the list of appliances with a particular status.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. TIP! If the arrow in the row for a status level points down. The Health Monitor Appliance page appears. 2. The Alert Detail list toggles the display to show or hide events.9. For more information. the appliance list for that status shows in the lower table. 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. click the color for the event status category you want to view. 3. in the Module Status Summary graph.1 Sourcefire 3D System Administrator Guide 548 . Select Operations > Monitoring > Health. In the Appliance column of the appliance list. If the arrow