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

......... 598 Viewing the Status of Long-Running Tasks ................9...... Exporting an Intrusion Policy.................................................................................... Exporting a Custom Table .......................................................................1 Sourcefire 3D System Administrator Guide 13 ............................................ Exporting a Dashboard............................................................................... 583 Exporting Objects ............................................................................................................... Exporting a Custom Workflow........................................................................... 629 Version 4........................................................ 600 Managing the Task Queue ............................................................ 603 Index ........................................................................................................................................ Exporting an RNA Detection Policy.... Exporting a System Policy............................ 600 Viewing the Task Queue ............................ Exporting Multiple Objects ................................ Exporting a Health Policy ............................................................ Exporting a PEP Policy ...Table of Contents Appendix A: Importing and Exporting Objects ................................................................................... 593 Appendix B: Appendix C: Purging the RNA and RUA Databases.................................................................................................................................. Exporting a User-Defined RNA Detector................................................................................................................................................................................. 602 Glossary .................................... 584 584 585 585 586 586 588 588 588 589 590 Importing 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. Using the Context Menu on page 36 explains how to display a context-specific menu of shortcuts on certain pages in the web interface. Sourcefire 3D System has the tools you need to: • • • discover the changing assets and vulnerabilities on your network determine the types of attacks against your network and the impact they have to your business processes defend your network in real time The topics that follow introduce you to the Sourcefire 3D System and describe some of the key components that contribute to its value as a part of any security strategy for your network. account password. time zone. • • • Components of the Sourcefire 3D System on page 15 provides descriptions of each of the components that may be in your Sourcefire 3D System. Specifying Your User Preferences on page 25 explains how to configure the preferences that are tied to a single user account.9. dashboard. • • • Version 4. 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. such as the home page. Logging Out of the Appliance on page 24 explains how to log out of the web interface. and event viewing preferences.1 Sourcefire 3D System Administrator Guide 14 . 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.

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

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

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

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

you can view the current status of the Defense Centers across your enterprise from a single web interface. See Using the Master Defense Center on page 156 for more information about managing your Defense Centers with a Master Defense Center.9. If the network map on the Defense Center has entries for the target host in a given event.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 manage up to 25 physical and Virtual 3D Sensors with a Virtual Defense Center.1 million default and 10 million maximum RNA Flows . compliance events. Intrusion Agents If you have an existing installation of Snort®. You can use the Master Defense Center to aggregate and analyze intrusion events. For more information. In this way.1 million default and 100 million maximum RNA Flows .2 million default and 10 million maximum Master Defense Centers The Sourcefire Master Defense Center is a key component in the Sourcefire 3D System.Introduction to the Sourcefire 3D System Components of the Sourcefire 3D System Chapter 1 Key DC3000 database quantities are: • • • Intrusion Events . you can install an Intrusion Agent to forward intrusion events to a Defense Center. You cannot use a Virtual Defense Center in high availability configurations or as a Master Defense Center. Key Virtual Defense Center database quantities are: • • • Intrusion Events . The Master Defense Center can also aggregate events related to the health of the Defense Centers it is managing.1 million default and 100 million maximum RNA Flow Summaries . you can do analysis and reporting on those events. see the Sourcefire 3D System Virtual Defense Center and 3D Sensor Installation Guide. and white list events from up to ten Defense Centers within your Sourcefire 3D System deployment.1 Sourcefire 3D System Administrator Guide 19 .1 million default and 10 million maximum RNA Flow Summaries . You can then analyze the events detected by Snort alongside your other data. the Defense Center Version 4. Although you cannot manage policies or rules for an Intrusion Agent from the 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. eStreamer You can access event data within your own applications through the eStreamer Application Programming Interface (API).Introduction to the Sourcefire 3D System Components of the Sourcefire 3D System Chapter 1 assigns impact flags to the events.9. eStreamer integration requires custom programming. IMPORTANT! You must have a Defense Center in your Sourcefire 3D System deployment to use RNA for Red Hat Linux. See the eStreamer Integration Guide for more information. but allows you to request specific data from a Defense Center. for example. you display network host data within one of your network management applications. 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. IMPORTANT! Because the 3D Sensor Software for X-Series does not have a web interface. Separate installation and configuration guides are available for the 3D Sensor Software for X-Series. 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. Version 4.1 Sourcefire 3D System Administrator Guide 20 . you could write a program to retrieve host criticality or vulnerability data from the Defense Center and add that information to your display. register all Intrusion Agents to the primary Defense Center. RNA for Red Hat Linux The Sourcefire 3D System currently supports a software-only version of the RNA component on your server hardware running Red Hat Enterprise Linux 5 (RHEL5) or CentOS 5. you must use a Defense Center to manage it. See the Sourcefire RNA Software on Red Hat Linux Configuration Guide for more information. IMPORTANT! When using Intrusion Agents registered to Defense Centers configured for high availability and managed by a Master Defense Center. If. You can continue to manually tune Snort rules and preprocessors with the Intrusion Agent in place.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Refer to Access Requirements Conventions on page 39 for the meaning of the Access statement at the beginning of each procedure.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.9. 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. DC1000. Platform requirement information for specific aspects of a feature is provided where needed. Virtual Defense Center. 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. Refer to Platform Requirements Conventions on page 38 for the meaning of the Requires statement at the beginning of each section. or DC3000 appliance used as a Defense Center Version 4. All platform information is formatted with an orange typeface.

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

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

0.0 10. For example. the following table lists the private IPv4 address spaces in CIDR notation. the Sourcefire 3D System uses 10.576 65.0.16.0. As a result.216 1. the Access setting for the procedure in the Setting Threshold Options within the Packet View topic is IPS + P&R Admin/Admin. but the web interface continues to display 10.0/8 172.2.048. the Sourcefire 3D System uses only the masked portion of the network IP address you specified.31.0/12 192.0 255.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.0.777 .0.3/8.3/8.255 Subnet Mask 255.0. variables. Version 4.0 192.0.255 192.168.Introduction to the Sourcefire 3D System IP Address Conventions Chapter 1 from the packet view.0.2. For example. without changing your user input.0.0.1 Sourcefire 3D System Administrator Guide 41 . CIDR Notation Syntax Examples CIDR Block 10. 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.1.255 172.168.168.0 255. including but not limited to the following: • • • • • • • • RNA detection policies custom topologies auto-assigned networks for user-defined host attributes traffic profiles compliance rules and white lists active scan targets intrusion policies.0 Number of IP Addresses 16.0 172.240.0.16.255.0/8.536 When you use CIDR notation to specify a range of IP addresses.255.255.1.255.0.0.0/16 IP Addresses in CIDR Block 10. if you type 10.255.9.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

9. User accounts with Restricted Event Analyst access cannot use User Roles and Dashboard Widget Availability Widget Appliance Information Appliance Status Compliance Events Current Interface Status Current Sessions Custom Analysis Disk Usage Interface Traffic Intrusion Events Network Compliance Product Licensing Administrator X X X X X X X X X X X X X X X X X X X X X X X X X Maintenance X X P&R Admin X IPS Analyst X X X X RNA Analyst X X X X Version 4. An X indicates the user can view the widget.1 Sourcefire 3D System Administrator Guide 63 .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. IMPORTANT! dashboards.

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

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

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

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

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

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

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

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

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

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

Aggregate the aggregation method for the widget. Defense Center predefined dashboard uses Version 4. the table of events which contains the event data the widget displays. Search the saved search you want to use to further constrain the data that the widget displays.. It also indicates which. Show Results whether you want to display the most frequently occurring events (Top) or the least frequently occurring events (Bottom). You do not have to specify a search. The time zone appears whenever you select a time-based field. Color the color of the bars in the widget background that show the relative number of occurrences of each result.9. although some presets use predefined searches. TIP! To display a graph over time. the default aggregation criterion is Count. select Time. The aggregation method configures how the widget groups the data it displays. if any. The following table describes the available presets for the Custom Analysis widget. which time zone you want to use to display results. For most event types. Table Field To control. in increments of five. the number of results rows you want to display.1 Sourcefire 3D System Administrator Guide 74 . the specific field of the event type you want to display.... Show Movers Time Zone whether you want to display the icons that indicate additions or movement from the most recent results. You can display from 10 to 25 result rows.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. 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. based on the number of detected flows.) . based on the number of flows where the host was the responder in the session. Predefined Dashboards Default Dashboard Detailed Dashboard Detailed Dashboard Requires IPS or DC/MDC + IPS All Intrusion Events (Not Dropped) IPS or DC/MDC + IPS Client Applications Detailed Dashboard DC + RNA Dropped Intrusion Events Default Dashboard IPS or DC/MDC + IPS Flows by Initiator IP Flow Summary DC + RNA Flows by Port Flow Summary DC + RNA Flows by Responder IP Flow Summary DC + RNA Flows by Service Flow Summary DC + RNA Version 4. Displays the most active ports on your monitored network.Using Dashboards Understanding the Predefined Widgets Chapter 3 each preset. Displays the most active hosts on your monitored network. by classification. where the packet was not dropped as part of the event. based on the number of detected flows. where the packet was dropped. based on the number of flows where the host initiated the session. Displays the most active services on your monitored network.1 Sourcefire 3D System Administrator Guide 75 . Displays the most frequently occurring types of intrusion events. by classification. Displays the most active client applications on your monitored network. Displays counts for the most frequently occurring intrusion events. by application type.9.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

because these models do not have a web interface and because configuration and event data cannot be stored on the sensors.conf files • Process management • Registration of remote manager • Rules tuning Not Supported • Detection engine management • Event storage on sensor • Health policy apply • High availability synchronization • Host Statistics • Interface set management • Intrusion policy apply • Network interface management • Network settings • Performance Statistics • Remote backup and restore • Remote reports • Sensor information management (System Settings) • SEU updates • Software updates • System policy apply • Time settings Managing 3Dx800 Sensors Requires: DC + 3D Sensor Sourcefire 3D Sensor 3800. and 3D Sensor 9800 models (usually referred to as the 3Dx800 sensors) provide many of the features found on other 3D Sensors.1 Sourcefire 3D System Administrator Guide 107 .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 . Version 4.9. 3D Sensor 5800.

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

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

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

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

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

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

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

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

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

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

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.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. Registration Key. Unique NAT ID .9. Select Operations > System Settings. You must begin the procedure for setting up the management relationship between a Defense Center and a sensor on the sensor.1 Sourcefire 3D System Administrator Guide 118 . Three fields are provided for setting up communications between appliances: • • • Management Host . Registration Key.for a unique alphanumeric ID. 2.for registration key.for the hostname or IP address. Log into the web interface of the sensor you want to add. Management Host and Registration Key used on both appliances Registration Key and Unique NAT ID used on the 3D Sensor with Host. you need: • the sensor’s IP address or hostname (in the connection context “hostname” is the fully qualified domain name or the name that resolves through the local DNS to a valid IP address) the Defense Center’s IP address or hostname to decide if you want to store the events generated by the sensor only on the Defense Center. Registration Key . Version 4. 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. and Unique NAT ID used on the 3D Sensor with Registration Key and Unique NAT ID used on the Defense Center. Management Host. To add a sensor to a Defense Center: Access: Admin 1.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

if the system policy applied to the managed sensor allows you to set the time manually. Version 4. Click Edit next to the name of the sensor where you want to set the time. 2. Click Disable next to the name of the sensor.9.1 Sourcefire 3D System Administrator Guide 139 . The Information page for that sensor appears. 3. Click Edit next to the name of the sensor that you want to manage. Click Remote Management in the list to the left of the page. The Information page for that sensor appears. 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. then you can change it as part of the system settings. then you cannot change the time manually. The Sensors page appears. To set the time for a managed sensor: Access: Admin 1. Select Operations > Sensors. click Enable. For information about editing the remote management communications from a sensor see Configuring Remote Access to the Defense Center on page 386. The Remote Management page appears.Using the Defense Center Editing a Managed Sensor’s System Settings Chapter 4 2. You must use the command line interface (CLI) to manage time settings on Crossbeam-based software sensors and RNA Software for Red Hat Linux. You cannot manage time settings on Intrusion Agents. Communications between the two appliances are interrupted. you can manage time settings on a managed sensor using the Defense Center’s web interface. 4. TIP! To enable communications between the two appliances again. However. which is the recommended setting for a managed sensor and its Defense Center. For 3D Sensors. 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 the following: • • • • • year month day hour minute 5. Select your time zone and click Save and. Changing the time zone with this option is equivalent to changing the time zone using the Time Zone Settings option in the user preferences. After you do the cabling.Using the Defense Center Managing a Clustered Pair Chapter 4 3. This setting does not affect the time zone setting on the managed sensor. click the time zone link located next to the date and time. A pop-up window appears. The time is updated.1 Sourcefire 3D System Administrator Guide 140 . If you want to change the time zone.9. In other words. shared configuration. From the Set Time drop-down lists. When you establish a clustered pair configuration. click Close to close the pop-up window. 4. this time zone option changes the time setting your user account uses on the Defense Center web interface. Click Time in the list to the left of the page. use a Defense Center to establish the clustered pair relationship between the two sensors and manage their joint resources. 7. The Time page appears showing the current time. you combine the 3D9900 sensors resources into a single. When you connect the two 3D9900 sensors you determine which is the master. Click Apply. Managing a Clustered Pair Requires: DC + 3D9900 You can increase the amount of traffic inspected on a network segment by connecting two fiber-based 3D9900 sensors in a clustered pair. You connect the master to the network segment you wish to analyze. after the time zone setting is saved. Version 4. 6.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

9. Understanding Global Policy Management on page 161 explains which policies you can send from your Master Defense Center to 3D Sensors and Defense Centers. The settings on the Filter Configuration page determine which events are forwarded from the Defense Center to the Master Defense Center. In this way. the Sourcefire 3D System checks the SEU on the managing Defense Center. although most deployments will use the same configuration across the enterprise. The Master Defense Center can also aggregate events related to the health of managed Defense Centers. Adding and Deleting Defense Centers on page 164 explains how to configure a Defense Center to communicate with a Master Defense Center. 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 . • • • • 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. 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. You can set up a different configuration for each Defense Center. The following sections explain more about using a Master Defense Center in your Sourcefire 3D System deployment. When you apply intrusion policies from a Master Defense Center. You can also choose whether to include the packet data collected with the intrusion events.Using the Master Defense Center Understanding Event Aggregation Chapter 5 You can use the Master Defense Center to build and dispatch global detection and intrusion policies. Editing Settings for a Managed Defense Center on page 175 explains how to change some of the settings for a Defense Center from the Master Defense Center’s web interface. • Understanding Event Aggregation on page 157 explains which types of events you can send from your Master Defense Centers to your Master Defense Center. IMPORTANT! The Product Compatibility section of the release notes for each version describes which versions of the Defense Center you can manage with a Master Defense Center. You can configure a Defense Center to send intrusion events based on their flag. If it finds an older SEU.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

hosts in your accounting department in the address range 10. IPS can use the value of the detection engine-specific variable in rules you enable in your policy to monitor network traffic and generate events.0/16 In the detection engine named DE_DMZ: HOME_NET = 10. which includes a mixed address space.90. In the system default variable used in the intrusion policy: HOME_NET = 10.9. you can use detection engine-specific variable values to tailor your detection capabilities to more closely match your infrastructure.10. You can associate a system default variable with a specific detection engine and give the resulting detection engine-specific variable an explicit value for that detection engine. The Detection Engines page appears.10. However. 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. 2.1 Sourcefire 3D System Administrator Guide 199 .0/24 If you later create another detection engine that monitors the rest of your network.10. you can use the system default Version 4.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 Deleting Detection Engine Groups Requires: DC/MDC or 3D Sensor When you delete a detection engine group.0/24). To delete a detection engine group: Access: Admin 1. You can define HOME_NET in your system default variable to encompass your internal address range (for example. The detection engine group is deleted.10.0/16). if you have created your detection engines so that one detection engine monitors one class of hosts (in this example.0/24 In the detection engine named DE_ACCT: HOME_NET = 10. Click Delete next to the name of the detection engine group.30. Select Operations > Configuration > Detection Engines > Detection Engines.0/24) and another monitors a different class (for example. they are not deleted.10. For information on policy-specific variables. For example. When you apply an intrusion policy to that detection engine. which are specific to the policy in which they are created. any detection engines in the group are automatically ungrouped.90. see Creating New Policy-Specific Variables in the Analyst Guide. 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.30.0. hosts in your network’s DMZ in the range 10. 10.10.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Default Settings for the Blocked Events Report Profile Field Report Category Report Type Detection Engine Search Query Workflow Setting IPS Intrusion Events All Blocked Events Impact and Priority (on the Defense Center) Destination Port (on the 3D Sensor) Time Add Summary Report Impact Based Event Summary (on the Defense Center) Drill Down of Source and Destination IPS (on the Defense Center) Drill Down of Destination Port (on the 3D Sensor) Drill Down of Events (on the 3D Sensor) Table View of Events Packets (limit 50 pages) Last day.9.Working with Event Reports Understanding Report Profiles Chapter 7 The Blocked Events report profile provides information on blocked intrusion events for all detection engines for the past twenty-four hours. This report profile is available on the Defense Center or on a 3D Sensor with IPS.1 Sourcefire 3D System Administrator Guide 244 . 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Managing Users Managing User Accounts Chapter 8 To modify user account privileges: Access: Admin 1. The Edit User page appears. See Managing User Password Settings on page 303 for information on changing password settings for internally authenticated users.9. Version 4. for users with event analyst roles. See Adding New User Accounts on page 300 for information about adding new user accounts. Click Edit next to the user you want to modify. select or clear the Only delete items created by user option to manage the user’s ability to delete of items not created by that user. 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. Select Operations > User Management. 3. See Configuring User Roles on page 304 for more information on configuring roles to grant access for Sourcefire 3D System functions. You can specify this information only after the user is added. • • • 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.1 Sourcefire 3D System Administrator Guide 307 . 2. Optionally.

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

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

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

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

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

Analysis & Reporting Menu Menu Admin Maint RNA/ RNA-RO Event Analyst X IPS/ IPS-RO Event Analyst X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Restricted Event Analyst P&R Admin Event Summary Intrusion Event Statistics Event Graphs Dashboards RNA Statistics Flow Summary IPS Events Reviewed Events Clipboard Incidents RNA Network Map | Hosts Network Map | Network Devices Network Map | Services Network Map | Vulnerabilities Network Map | Host Attributes X X X X X X X X X X X X X X X X X X Version 4. An X indicates that the user can access the option.9. Users with only Rules or Maintenance access cannot see the Analysis & Reporting menu at all.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 313 .

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

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

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

Event Analyst P&R Admin Configuration RNA/RUA Event Purge Detection Engines High Availability eStreamer Login Authentication X X X X X X X Version 4.1 Sourcefire 3D System Administrator Guide 317 . An X indicates that the user can access the option.9. 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. Operations Menu Menu Admin Maint RNA/ RNA-RO Event Analyst IPS/ IPS-RO Event Analyst Res.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. All users can access at least some options on the Operations menu.

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.Managing Users Managing User Accounts Chapter 8 Operations Menu (Continued) Menu Admin Maint RNA/ RNA-RO Event Analyst IPS/ IPS-RO Event Analyst Res.1 Sourcefire 3D System Administrator Guide 318 .9.

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. 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. 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. 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 . An X indicates that the user can access the option.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

with a system policy. 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. which are likely to be specific to a single appliance. Version 4.1 Sourcefire 3D System Administrator Guide 360 . which controls aspects of an appliance that are likely to be similar across a deployment.

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

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

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

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

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

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

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

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

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

1 Sourcefire 3D System Administrator Guide 370 .com/). it will not receive data from your NetFlow-enabled devices. 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. 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. you can request it from the web interface. 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. If one Defense Center does not have a NetFlow license. If you do not have the serial number. Feature licenses include: • • • • • • NetFlow licenses. See the following sections for more information: • • • Adding Feature Licenses on page 370 Viewing Feature Licenses on page 372 Configuring Network Settings on page 377 Adding Feature Licenses Requires: DC If you need to obtain a feature license for a feature you purchased. you must add them to the Defense Center from the web interface.9. which allow you to use the RUA feature Intrusion Agent licenses. The serial number appears in the Sourcefire Software & Licenses section. then clicking Products & Contracts.sourcefire. clicking Account. Version 4. you should have the 12-digit feature license serial number provided by Sourcefire when you purchased the licensable feature. which specify the number of NetFlow-enabled devices you can use to gather flow data RNA host licenses. you can find it by logging into the Sourcefire Support Site (https://support. which allow you to use intrusion agents 3D Virtual Sensors.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The Remote Storage Device page appears. The Remote Storage Device page appears. Enter the path to your storage area in the Directory field. At Storage Type. 4. At Storage Type. 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. The Information page appears.Configuring System Settings Managing Remote Storage Chapter 10 2. To store backups and reports using NFS: Access: Admin 1. Click Remote Storage Device. 4. The page refreshes to display the NFS storage configuration options. Your storage location choice is saved. select Local (No Remote Storage). Click Save. 3. Click Remote Storage Device. Using NFS for Remote Storage Requires: Series 2 DC You can select Network File System (NFS) protocol to store your reports and backups.9. select NFS. Version 4. Select Operations > System Settings. 3. 2.1 Sourcefire 3D System Administrator Guide 394 .

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

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

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

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

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

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

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

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

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

for most detection engines with inline interface sets. if necessary. If this occurs. Instead. Clear your browser cache and force a reload of the browser. see Creating a Detection Engine on page 193). Updating Managed Sensors. push the update to the sensors from the Defense Center. do not restart the update. If the update is still running. You can monitor the update's progress in the task queue (Operations > Monitoring > Task Status). 12.9. confirm that you want to install the update and reboot the Defense Center. applying an intrusion policy causes IPS detection engines to restart. Re-apply intrusion policies to the IPS detection engines on your managed 3D Sensors. Continue with the next section. First. WARNING! Do not use the web interface to perform any other tasks until the update has completed and (if necessary) the Defense Center reboots. After the update finishes. log in again to view the task queue. 10. If prompted. Finally. the user interface may exhibit unexpected behavior. Updating managed sensors is a multi-step process. 13. or the Defense Center may log you out. Select Operations > Help > About and confirm that the software version is listed correctly. Before the update completes. 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. Updating Managed Sensors Requires: DC + 3D Sensor After you update your Defense Centers.Updating System Software Installing Software Updates Chapter 11 7. 11. install the software. the web interface may become unavailable. may cause a few packets to pass through the sensor uninspected. contact Support. see Updating the Vulnerability Database on page 410. 14. Sourcefire strongly recommends that you use them to update the sensors they manage. The update process begins. This can cause a short pause in processing and. to update the Sourcefire software on the sensors that the Defense Center manages.1 Sourcefire 3D System Administrator Guide 404 . If you encounter issues with the update (for example. Under Selected Update. 9. log into the Defense Center. 8. Next. select the Defense Center and click Install. This is expected behavior. if the task queue indicates that the update has failed or if a manual refresh of the task queue shows no progress). Otherwise. Note that you can update Version 4. Verify that all managed sensors are successfully communicating with the Defense Center. continue to refrain from using the web interface until the update has completed. Update the VDB on your Defense Centers and the 3D Sensors with RNA that they manage. download the update from the Support Site and upload it to the managing 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. its version number. IMPORTANT! You must use the Defense Center to update sensors that do not have a web interface. The Patch Update Management page shows the type of update you just uploaded. and 3Dx800 sensors. select Operations > Update. For information on the updates you can download. If you transfer an update file by email. making sure you have enough free disk space to perform the update. The update is uploaded to the Defense Center. Click Upload Update to browse to the update you downloaded. you have set aside adequate time to perform the update. 4. The page also indicates whether a reboot is required as part of the update. see the release notes for more information. see Updating a Defense Center or Master Defense Center on page 402. For information on updating the 3D Sensors in your deployment. then click Upload. Read the release notes for the update and complete any required pre-update tasks. RNA for Red Hat Linux. To update managed 3D Sensors: Access: Admin 1. IMPORTANT! Download the update directly from the Support Site. you may need to uninstall the previous version and install the new version. Update the Sourcefire software on the sensors’ managing Defense Center. making sure that the 3D Sensors are running the correct version of the Sourcefire software. On the managing Defense Center. Pre-update tasks can include updating your managing Defense Center. and so on. 7. see the release notes. Click Push next to the update. Different 3D Sensor models use different updates.9.Updating System Software Installing Software Updates Chapter 11 multiple 3D Sensors at once. The Push Update page appears. and date and time it was generated.1 Sourcefire 3D System Administrator Guide 405 . However. including Crossbeam-based software sensors. Version 4. it may become corrupted. see the release notes. backing up event and configuration data. 6. making sure software sensors are running the correct version of their operating systems. Download the update from the Sourcefire Support Site. for major updates to software sensors. but only if they use the same update. 5. The Patch Update Management page appears. 2. 3.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

and executable files are run when required. 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.1 Sourcefire 3D System Administrator Guide 471 . Understanding Running Processes There are two different types of processes that run on an appliance: daemons and executable files. and checks for working SSL and valid certificate authentication.9. This table is not an exhaustive list of all processes that may run on an appliance. The System Daemons table lists daemons that you may see on the Process Status page and provides a brief description of their functionality. Daemons always run. System Daemons Daemon crond dhclient fpcollect httpd httpsd Description Manages the execution of scheduled commands (cron jobs) Manages dynamic host IP addressing Manages the collection of client and server fingerprints Manages the HTTP (Apache web server) process Manages the HTTPS (Apache web server with SSL) service. The process list collapses. 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.

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

The System Executables and Utilities table describes the executables that you may see on the Process Status page. 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. and the network map Utility that copies files Utility that lists the amount of free space on the appliance Utility that writes content to standard output Utility that searches files and folders for specified input.9.1 Sourcefire 3D System Administrator Guide 473 . flow data. 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.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. supports extended set of regular expressions not supported in standard grep Version 4.

See Configuring the Access List for Your Appliance on page 325 for more information about access configuration.1 Sourcefire 3D System Administrator Guide 474 . 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. 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.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.

correlating acquired data with the RNA fingerprint database. indicating that the appliance is active.9.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. decodes and performs session reassembly. Indicates that Snort is running Public domain version of the Korn shell Utility that shuts down the appliance Utility that suspends a process for a specified number of seconds Mail client that handles email transmission when email event notification functionality is enabled Forwards SNMP trap data to the SNMP trap server specified when SNMP notification functionality is enabled Indicates a Secure Shell (SSH) connection to the appliance Indicates a sudo process. heartbeat used to maintain contact between a sensor and Defense Center Indicates a message broker process.1 Sourcefire 3D System Administrator Guide 475 . handles communication between Defense Centers and sensor. 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. 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.

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

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

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

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

From the Select Time Range list. Select Operations > Monitoring > Performance > RNA.1 Sourcefire 3D System Administrator Guide 480 . the Select Graph(s) list adjusts to display the available graphs. Depending on whether you select a detection engine or a sensor. Version 4. 3. 4. The RNA page appears.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. From the Select Graph(s) list.9. last week. in thousands Displays a graph that represents the number of established connections observed by the RNA process per second Avg Bytes/Packet Percent Packets Dropped K Packets/Sec Syn/Ack/Sec To generate RNA performance statistics graphs: Access: Maint/Admin 1. select the time range you would like to use for the graph. You can choose from last hour. 2. or last month. select the Defense Center. select the type of graph you want to create. the managed 3D Sensors. TIP! You can select multiple graphs by holding down the Ctrl or Shift keys while clicking on the graph type. From the Select Target list. or the detection engines that you want to include. last day.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Using Health Monitoring Configuring Health Policies Chapter 15 Applicable health modules for various appliances are listed in the Health Modules Applicable to Appliances table. MDC3000. 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. 3Dx800. and 3D6500 Version 4. Health Modules Applicable to Appliances Module Appliance Heartbeat Automatic Application Bypass Status CPU Temperature CPU Usage Card Reset Data Correlator Process Defense Center Status Disk Usage eStreamer Process Event Stream Status Fan Alarm Hardware Alarms Health Monitor Process IPS Event Rate IPS Process Link State Propagation MDC Event Service Memory Usage PEP Status Power Supply Applicable Appliance Defense Center 3D Sensors.9.1 Sourcefire 3D System Administrator Guide 531 . 3D3500.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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. Click Health Monitor on the toolbar. the appliance list is hidden.Reviewing Health Status Using the Health Monitor Chapter 16 To use the health monitor: Access: Maint/Admin/ Any Analyst except Restricted 1. Select the appropriate status in the Status column of the table or the appropriate portion of the pie chart to the list appliances with that status. the appliance list for that status shows in the lower table.9.1 Sourcefire 3D System Administrator Guide 546 . 2. The Health Monitor page appears. If the arrow points right.

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

Optionally. The Alert Detail list toggles the display to show or hide events. Select Operations > Monitoring > Health. in the Module Status Summary graph. click the arrow in that status row. click the color for the event status category you want to view. the appliance list for that status shows in the lower table.9. TIP! If the arrow in the row for a status level points down. The Health Monitor Appliance page appears. In the Appliance column of the appliance list. 4.Reviewing Health Status Using Appliance Health Monitors Chapter 16 To view the status summary for a specific appliance: Access: Maint/Admin/ Any Analyst except Restricted 1. The Health Monitor page appears. 3.1 Sourcefire 3D System Administrator Guide 548 . To show the list of appliances with a particular status. For more information. the appliance list is hidden. 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. If the arrow points right. click the name of the appliance for which you want to view details in the health monitor toolbar. 2.

Normal Green Indicates that the monitored item is running within the limits configured in the health policy applied to the appliance. and Disabled. Recovered Green Indicates that the health for the monitored item is back within the limits configured in the health policy applied to the appliance. include Error.1 Sourcefire 3D System Administrator Guide 549 . Critical Red Warning Yellow Indicates that warning limits have been exceeded for the health module on the appliance and the problem has not been corrected. Viewing Alerts by Status Requires: DC/MDC You can show or hide categories of alerts by status. Version 4. or that the appliance is currently unreachable.Reviewing Health Status Using Appliance Health Monitors Chapter 16 • • • Running a Specific Health Module on page 551 Generating Health Module Alert Graphs on page 553 Generating Appliance Troubleshooting Files on page 554 Interpreting Appliance Health Monitor Status Available status categories. Disabled Blue Indicates that a module is disabled or blacklisted. Contact your technical support representative to obtain an update to the health monitoring module. Warning. as described in the Appliance Health Status Indicator table that follows. Appliance Health Status Indicator Status Level Error Status Icon Status Color White Description Indicates that the health monitoring module has failed and has not been successfully re-run since the failure occurred. that the appliance does not have a health policy applied to it. Indicates that the critical limits have been exceeded for the health module on the appliance and the problem has not been corrected. Critical.9. by severity. Normal.

However. The alerts in the Alert Detail list for that category disappear. Version 4. The Health Monitor page appears.Reviewing Health Status Using Appliance Health Monitors Chapter 16 To show alerts by status: Access: Maint/Admin/ Any Analyst except Restricted Click the status icon or the color segment in the pie chart that corresponds to the health status of the alerts you want to view. To expand the appliance list to show appliances with a particular status. click the arrow in that status row. To hide alerts by status: Access: Maint/Admin/ Any Analyst except Restricted Click the status icon or the color segment in the pie chart that corresponds to the health status of the alerts you want to view. Select Operations > Monitoring > Health. The alerts for that category appear in the Alert Detail list. To run all health modules for the appliance: Access: Maint/Admin/ Any Analyst except Restricted 1.1 Sourcefire 3D System Administrator Guide 550 .9. 2. TIP! If the arrow in the row for a status level points down. you can also run all health module tests on demand to collect up-to-date health information for the appliance. If the arrow points right. the appliance list is hidden. Running All Modules for an Appliance Requires: DC/MDC Health module tests run automatically at the policy run time interval you configure when you create a health policy. the appliance list for that status shows in the lower table.

then the Health Monitor Appliance page refreshes. However. If the value has not changed for a module that you just ran manually. You can also wait for the page to refresh again automatically.Reviewing Health Status Using Appliance Health Monitors Chapter 16 3. 4. The status bar indicates the progress of the tests. Running a Specific Health Module Requires: DC/MDC Health module tests run automatically at the policy run time interval you configure when you create a health policy. Version 4. In the Appliance column of the appliance list. click the name of the appliance for which you want to view details in the health monitor toolbar. The Health Monitor Appliance page appears. then refresh the page by clicking the sensor name. wait a few seconds.9. the first refresh that automatically occurs may not reflect the data from the manually-run tests. Click Run All Modules. IMPORTANT! When you manually run health modules.1 Sourcefire 3D System Administrator Guide 551 . you can also run a health module test on demand to collect up-to-date health information for that module.

click the name of the appliance for which you want to view details in the health monitor toolbar. click Run. The Health Monitor page appears. the first refresh that automatically occurs may not reflect the data from the manually-run tests. The Health Monitor Appliance page appears. Version 4. If the value has not changed for a module that you just manually ran. the appliance list is hidden. TIP! If the arrow in the row for a status level points down. the appliance list for that status shows in the lower table.Reviewing Health Status Using Appliance Health Monitors Chapter 16 To run a specific health module: Access: Maint/Admin/ Any Analyst except Restricted 1. If the arrow points right.9. In the Alert Detail row for the alert for which you want to view a list of events. In the Module Status Summary graph of the Health Monitor Appliance page. click the color for the health alert status category you want to view. 3.1 Sourcefire 3D System Administrator Guide 552 . To expand the appliance list to show appliances with a particular status. In the Appliance column of the appliance list. Select Operations > Monitoring > Health. The status bar indicates the progress of the test. then refresh the page by clicking the sensor name. then the Health Monitor Appliance page refreshes. The Alert Detail list expands to list the health alerts for the selected appliance for that status category. 4. wait a few seconds. IMPORTANT! When you manually run health modules. click the arrow in that status row. 2. You can also wait for the page to refresh automatically again. 5.

the appliance list is hidden. click the color for the health alert status category you want to view. The Health Monitor Appliance page appears. In the Appliance column of the appliance list. If the arrow points right. Select Operations > Monitoring > Health. the appliance list for that status shows in the lower table. The Health Monitor page appears. click the name of the appliance for which you want to view details in the health monitor toolbar. To expand the appliance list to show appliances with a particular status.Reviewing Health Status Using Appliance Health Monitors Chapter 16 Generating Health Module Alert Graphs Requires: DC/MDC You can graph the results over a period of time of a particular health test for a specific appliance. 3. Version 4. To generate a health module alert graph: Access: Maint/Admin/ Any Analyst except Restricted 1.1 Sourcefire 3D System Administrator Guide 553 . 2. TIP! If the arrow in the row for a status level points down. The Alert Detail list expands to list the health alerts for the selected appliance for that status category.9. 4. click the arrow in that status row. In the Module Status Summary graph of the Health Monitor Appliance page.

TIP! If no events appear. showing the status of the event over time. The Health Monitor page appears. the appliance list for that status shows in the lower table. The Alert Detail section below the graph lists all health alerts for the selected appliance. If the arrow points right. Select Operations > Monitoring > Health. Generating Appliance Troubleshooting Files Requires: DC/MDC In some cases. To generate appliance troubleshooting files: Access: Maint/Admin/ Any Analyst except Restricted 1. Sourcefire Support may ask you to generate troubleshooting files to help them diagnose the problem.9.1 Sourcefire 3D System Administrator Guide 554 . To expand the appliance list to show appliances with a particular status. 2. you may need to adjust the time range.Reviewing Health Status Using Appliance Health Monitors Chapter 16 5. Version 4. A graph appears. click Graph. In the Alert Detail row for the alert for which you want to view a list of events. the appliance list is hidden. if you have a problem with your appliance. See Setting Event Time Constraints in the Analyst Guide for more information. TIP! If the arrow in the row for a status level points down. click the arrow in that status row.

The Health Monitor Appliance page appears. In the Appliance column of the appliance list. you can view health events. From the Operations > Monitoring > Health menu. A File Download dialog box appears. and can search for specific events. Click the folder for the file generation job entry to expand the entry. click the name of the appliance for which you want to view details in the health monitor toolbar. Working with Health Events The Defense Center provides fully customizable event views that allow you to quickly and easily analyze the health status events gathered by the health monitor. Select Operations > Monitoring > Task Status. The file generation task is added to the task status queue. Many functions that you can perform on the health event view pages are constant across all event view pages. 5. See Understanding Health Event Views on page 556 for more information about these common procedures.Reviewing Health Status Working with Health Events Chapter 16 3. Save the files to a location on your computer. Version 4. Select Click to retrieve generated files.9. These event views allow you to search and view event data and to easily access other information that may be related to the events you are investigating. The Task Status page appears.1 Sourcefire 3D System Administrator Guide 555 . 4. 6. 8. 7. Send the generated files to technical support to assist in troubleshooting your system. Click Generate Troubleshooting Files and confirm that you want to generate the files. 9.

For a description of the health modules that generated the events that you may see on this page.Reviewing Health Status Working with Health Events Chapter 16 See the following sections for more information about viewing events: • • • Understanding Health Event Views on page 556 describes the types of events that RNA generates. you can more effectively configure alerting for health events. If you understand what conditions each health module tests for. you retrieve all health events for all managed appliances. see Understanding Health Modules on page 485. see the following sections: • • • Viewing Health Events on page 556 Understanding the Health Events Table on page 561 Searching for Health Events on page 563 Viewing Health Events You can view the appliance health data collected by your health monitor in several ways. see Understanding Health Modules on page 485. see the following topics: • • • • Viewing All Health Events on page 556 Viewing Health Events by Module and Appliance on page 557 Working with the Health Events Table View on page 559 Searching for Health Events on page 563 Viewing All Health Events Requires: DC/MDC The Table View of Health Events page provides a list of all health events on the selected appliance. Understanding Health Event Views The Defense Center health monitor logs health events. When you access health events from the Health Monitor page on your Defense Center.9. Viewing Health Events on page 556 describes how to access and use the Event View page. For more information about viewing and searching for health events.1 Sourcefire 3D System Administrator Guide 556 . For more information on the different types of health modules that generate health events. which you can see on the Health Event View page. Searching for Health Events on page 563 describes how to search for specific events using the Event Search page. For more information. Version 4.

2. Select Operations > Monitoring > Health. the appliance list for that status shows in the lower table. TIP! You can bookmark this view to allow you to return to the page in the health events workflow containing the Health Events table of events. see Setting Event Time Constraints in the Analyst Guide. See Setting Event Time Constraints in the Analyst Guide for more information. click Health Events. If the arrow points right. If no events appear. TIP! If the arrow in the row for a status level points down.9. the appliance list is hidden. The bookmarked view retrieves events within the time range you are currently viewing. The Events page appears. The Health Monitor page appears. The Health Monitor page appears.Reviewing Health Status Working with Health Events Chapter 16 To view all health events on all managed appliances: Access: Maint/Admin/ Any Analyst except Restricted 1. For more information. but you can then modify the time range to update the table with more recent information if needed. 2. Select Operations > Monitoring > Health. click the arrow in that status row. To view the health events for a specific module: Access: Maint/Admin/ Any Analyst except Restricted 1. Viewing Health Events by Module and Appliance Requires: DC/MDC You can query for events generated by a specific health module on a specific appliance. In the toolbar.1 Sourcefire 3D System Administrator Guide 557 . Version 4. you may need to adjust the time range. To expand the appliance list to show appliances with a particular status. containing all health events.

you may need to adjust the time range. click Events. See Setting Event Time Constraints in the Analyst Guide for more information. click the color for the health alert status category you want to view. click the name of the appliance for which you want to view details in the health monitor toolbar. In the Alert Detail row for the alert for which you want to view a list of events. If you want to view all health events for the selected appliance. In the Module Status Summary graph of the Health Monitor Appliance page. In the Appliance column of the appliance list. 5. If no events appear. Version 4.1 Sourcefire 3D System Administrator Guide 558 . The Health Monitor Appliance page appears.Reviewing Health Status Working with Health Events Chapter 16 3. containing query results for a query with the name of the appliance and the name of the selected health alert module as constraints. 6. The Alert Detail list expands to list the health alerts for the selected appliance for that status category. The Health Events page appears.9. 4. expand Search Constraints and click the Module Name constraint to remove it.

select Analysis & Reporting > Bookmarks or. click Bookmark This Page.. find more information in Understanding the Health Events Table on page 561. click View Bookmarks.. select the check box next to the events you want to delete and click Delete. click Report Designer. find more information in Setting Event Time Constraints in the Analyst Guide. change what columns display in the table of events. from any event view. sort the events that appear. Health Event View Functions To.. or constrain the events that appear delete health events find more information in Sorting Drill-down Workflow Pages in the Analyst Guide. See Using Bookmarks in the Analyst Guide for more information.Reviewing Health Status Working with Health Events Chapter 16 Working with the Health Events Table View Requires: DC/MDC The Health Event View Functions table describes each action you can perform from the Event View page.1 Sourcefire 3D System Administrator Guide 559 . Note that events that were generated outside the appliance's configured time window (whether global or event-specific) may appear in an event view if you constrain the event view by time. navigate through event view pages navigate to other event tables to view associated events bookmark the current page so that you can quickly return to it navigate to the bookmark management page generate a report based on data in the table view Version 4. provide a name for the bookmark and click Save. click Delete All. See Using Bookmarks in the Analyst Guide for more information. learn more about the contents of the columns that appear in the Health event view modify the time and date range for events listed in the Health table view You can.9. This can occur even if you configured a sliding time window for the appliance. See Generating Reports from Event Views on page 235 for more information. find more information in Navigating to Other Pages in the Workflow in the Analyst Guide.. then confirm you want to delete all the events. To delete all the events in the current constrained view. find more information in Navigating between Workflows in the Analyst Guide.

health status for the Hardware Alarms module changes to red and the message details include a reference to the NFE temperature. See Selecting Workflows in the Analyst Guide for more information. NFE temperature Version 4. health status for the Hardware Alarms module changes to red and the message details include a reference to the daemon.1 Sourcefire 3D System Administrator Guide 560 .. select another health events workflow You can.. • If NFE temperature exceeds 99 degrees Fahrenheit.Reviewing Health Status Working with Health Events Chapter 16 Health Event View Functions (Continued) To. • If NFE temperature exceeds 89 degrees Fahrenheit. view the details associated with a single health event view event details for multiple health events view event details for all events in the view view all events of a particular status Interpreting Hardware Alert Details for 3D9900 Sensors For 3D9900 sensor models. select the check box next to the rows that correspond with the events you want to view details for and then click View. The triggering condition can be found in the message detail for the alert. click the down arrow link on the left side of the event. click the status icon in the Status column for an event with that status. health status for the Hardware Alarms module changes to red and the message details include a reference to the NFE card presence.9. health status for the Hardware Alarms module changes to yellow and the message details include a reference to the NFE temperature. NFE Platform daemon If the NFE Platform daemon goes down. Conditions Monitored for 3D9900 Sensors Condition Monitored NFE card presence Causes of Yellow or Red Error Conditions If NFE hardware is detected that is not valid for the appliance. click View All. hardware alarms generate in response to the events described in the Conditions Monitored for 3D9900 Sensors table.. click Workflows or select from the Workflows dropdown list in the toolbar..

health status for the Hardware Alarms module changes to red and the message details include a reference to the daemon. including hardware and software status. If the Psls daemon goes down. health status for the Hardware Alarms module changes to red and the message details include a reference to the daemon. If the Load-Balancing Interface Module (LBIM) switch assembly is not present or not communicating.Reviewing Health Status Working with Health Events Chapter 16 Conditions Monitored for 3D9900 Sensors (Continued) Condition Monitored NFE Message daemon Causes of Yellow or Red Error Conditions If the NFE Message daemon goes down. If the NFE TCAM daemon goes down.9. If the Scmd daemon goes down. which monitor a variety of aspects. health status for the Hardware Alarms module changes to red and the message details include a reference to the daemon. If the Rulesd daemon goes down. NFE TCAM daemon LBIM presence Scmd daemon Psls daemon Ftwo daemon Rulesd (host rules) daemon nfm_ipfragd (host frag) daemon Understanding the Health Events Table You can use the Defense Center’s health monitor to determine the status of critical functionality within the Sourcefire 3D System. health status for the Hardware Alarms module changes to red and the message details include a reference to the daemon. health status for the Hardware Alarms module changes to red and the message details include a reference to the LBIM presence. If the nfm_ipfragd daemon goes down. The Health Monitor modules you choose to enable Version 4. health status for the Hardware Alarms module changes to red and the message details include a reference to the daemon. health status for the Hardware Alarms module changes to red and the message details include a reference to the daemon. If the Ftwo daemon goes down. health status for the Hardware Alarms module changes to yellow and the message details include a reference to the daemon. You create and apply health policies to your appliances.1 Sourcefire 3D System Administrator Guide 561 .

For example. You can use the asterisk (*) to create wildcard searches. a health event is generated. Select Operations > Monitoring > Health.1 Sourcefire 3D System Administrator Guide 562 . The name of the test. the units is a percentage sign (%).Reviewing Health Status Working with Health Events Chapter 16 in your health policy run various tests to determine appliance health status. For example. The description of the health module that generated the event. The fields in the health events table are described in the Health Event Fields table. Yellow. Units The units descriptor for the result. Status Sensor The status (Critical. Health Event Fields Field Module Name Description The name of the health module that generated the event. The Health Monitor page appears. if the Defense Center generates a health event whenever a sensor it is monitoring is using 80 percent or more of its CPU resources. For example. health events generated when a process was unable to execute are labeled Unable to Execute. The value (number of units) of the result obtained by the health test that generated the event. When the health status meets criteria that you specify. the value could be a number from 80 to 100. see Monitoring the System on page 463. see the Health Modules table on page 485. Green. or Disabled) reported for the appliance. Test Name Time Description Value To display the table view of health events: Access: Maint/Admin/ Any Analyst except Restricted 1. The timestamp for the health event. This is typically the same as the module name. The appliance where the health event was reported. For more information on health monitoring. if the Defense Center generates a health event when a sensor it is monitoring is using 80 percent or more of its CPU resources. Version 4.9. For a list of health modules.

On the Select Workflow page. On the toolbar. Specify the value (number of units) of the result obtained by the health test for the events you want to view. The table view appears. You can create. You can use an asterisk (*) in this field to create wildcard searches. For example. click Health Events. For information on working with health events. For example.Reviewing Health Status Working with Health Events Chapter 16 2. to view events that measure CPU performance. type CPU. save. When creating new searches or modifying default searches. you retrieve events where the appliance CPU was running at 15% utilization at the time the test ran. see Working with Health Events on page 555. Health Event Search Criteria Search Field Module Name Description Specify the name of the module which generated the health events you want to view. The search should retrieve applicable CPU Usage and CPU temperature events. For example. click Health Events. TIP! If you are using a custom workflow that does not include the table view of health events. click Workflows.1 Sourcefire 3D System Administrator Guide 563 . Value Version 4. you could enter Unable to Execute to view any health events where a process was unable to execute. and re-use event searches. Description Specify the description of the events you want to view. if you specify a value of 15 and type CPU in the Units field.9. The Health Event Search Criteria table describes each search criterion you can specify. Searching for Health Events Requires: DC/MDC You can use Event Search to search for specific network discovery events. there are a number of options you can configure.

Enter your search criteria. The Search page appears. type Critical to retrieve all health events that indicate a critical status. one is created automatically when you save the search. Warning. if you type % in the Units field. See Health Event Search Criteria on page 563 for more information about the values you can enter for search criteria. For example. Valid status levels are Critical. You can use an asterisk (*) in this field to create wildcard searches.9. 3.1 Sourcefire 3D System Administrator Guide 564 . you retrieve all events for the Disk Usage modules. Status Specify the status for the health events that you want to view.Reviewing Health Status Working with Health Events Chapter 16 Health Event Search Criteria (Continued) Search Field Units Description Specify the units descriptor for the result obtained by the health test for the events you want to view. 2. Optionally. you retrieve all events for any modules that contain text followed by a “%” sign in the Units field. For example. Version 4. because the Disk Usage module has a “%” label in the Units field (and no additional text). Normal. and Disabled. Error. if you type *% in the Units field. if you want to save the search. If you do not enter a name. To run and save health event searches: Access: Any Analyst except Restricted/ Admin 1. Select Analysis & Reporting > Searches > Health Events. However. enter a name for the search in the Name field. Appliance Specify the name of appliance.

You have the following options: • Click Search to execute the search. including a custom workflow. • • Click Save if you are modifying an existing search and want to save your changes. Otherwise. 5. leave the check box selected to save the search as private. use the Workflows menu on the toolbar. For information on specifying a different default workflow.1 Sourcefire 3D System Administrator Guide 565 . if you want to save the search so that other users can access it. The search is saved and associated with your user account (if you selected Save As Private). see the following sections: • • Version 4. TIP! If you want to save a search as a restriction for restricted data users. disable the Save As Private check box. constrained by the current time range. so that you can run it at a later time.Reviewing Health Status Working with Health Events Chapter 16 4. Your search results appear in the default health events workflow. Loading a Saved Search in the Analyst Guide Deleting a Saved Search in the Analyst Guide For more information about searching. Click Save as New Search to save the search criteria. To use a different workflow. you must save it as a private search.9. see Configuring Event View Settings on page 27. Optionally.

9. including auditing data.1 Sourcefire 3D System Administrator Guide 566 . Managing Audit Records Requires: DC/MDC or 3D Sensor Defense Centers and 3D Sensors log read-only auditing information for user activity. and filter audit log messages based on any item in the audit view. and also record system status messages in the system log. which contains system status messages. The following sections provide more information about the monitoring features that the system provides: • • Managing Audit Records on page 566 describes how to view and manage system audit information.Auditing the System Chapter 17 Administrator Guide You can audit activity on your system in two ways. Viewing the System Log on page 578 describes how to view the system log. For more information. TIP! Defense Centers and 3D Sensors with IPS also provide full-featured reporting features that allow you to generate reports for almost any type of data accessible in an event view. Version 4. The appliances that are a part of the Sourcefire 3D System generate an audit record for each user interaction with the web interface. You can easily delete and report on audit information. Audit logs are presented in a standard event view that allows you to view. see Working with Event Reports on page 232. sort.

For information on creating a custom workflow.Auditing the System Managing Audit Records Chapter 17 The audit log stores a maximum of 100. learn more about the contents of the columns in the table modify the time range used when viewing audit records You can. Version 4.. find more information at Setting Event Time Constraints in the Analyst Guide. see Creating Custom Workflows in the Analyst Guide..1 Sourcefire 3D System Administrator Guide 567 .. For more information. the appliance prunes the oldest records from the database to reduce the number to 100. find more information in Navigating to Other Pages in the Workflow in the Analyst Guide. You can also create a custom workflow that displays only the information that matches your specific needs. The predefined workflow includes a single table view of events. When the number of audit log entries exceeds 100. Note that events that were generated outside the appliance's configured time window (whether global or event-specific) may appear in an event view if you constrain the event view by time.9. Audit Log Actions To. find more information in Understanding the Audit Log Table on page 574. you can manipulate the view depending on the information you are looking for. This can occur even if you configured a sliding time window for the appliance.000.. sort and constrain events on the current workflow page navigate within the current workflow page find more information in Sorting Table View Pages and Changing Their Layout in the Analyst Guide. see the following sections: • • • • Viewing Audit Records on page 567 Suppressing Audit Records on page 570 Understanding the Audit Log Table on page 574 Searching Audit Records on page 575 Viewing Audit Records Requires: DC/MDC or 3D Sensor You can use the appliance to view a table of audit records.000. The Audit Log Actions table below describes some of the specific actions you can perform on an audit log workflow page.000 entries. Then.

• To drill down to the next workflow page keeping the current constraints.. For more information.. select the checkboxes next to the events you want to view on the next workflow page. If you click a value on a drilldown page. Note that this only works on drill-down pages. click a value within a row.Auditing the System Managing Audit Records Chapter 17 Audit Log Actions (Continued) To.. then click View. For more information. TIP! Table views always include “Table View” in the page name. Version 4. Note that clicking a value within a row in a table view constrains the table view and does not drill down to the next page.1 Sourcefire 3D System Administrator Guide 568 .9. you move to t