Symantec Security Information Manager Administrator Guide

Transcription

1 Symantec Security Information Manager Administrator Guide

2 Symantec Security Information Manager Administrator Guide The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version: Legal Notice Copyright 2011 Symantec Corporation. All rights reserved. Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party ( Third Party Programs ). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Legal Notice Appendix to this Documentation or TPIP ReadMe File accompanying this Symantec product for more information on the Third Party Programs. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR and subject to restricted rights as defined in FAR Section "Commercial Computer Software - Restricted Rights" and DFARS , "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.

3 Symantec Corporation 350 Ellis Street Mountain View, CA Printed in the United States of America

4 Technical Support Contacting Technical Support Symantec Technical Support maintains support centers globally. Technical Support s primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantec s support offerings include the following: A range of support options that give you the flexibility to select the right amount of service for any size organization Telephone and/or Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers software upgrades Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis Premium service offerings that include Account Management Services For information about Symantec s support offerings, you can visit our Web site at the following URL: All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy. Customers with a current support agreement may access Technical Support information at the following URL: Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem. When you contact Technical Support, please have the following information available: Product release level

5 Hardware information Available memory, disk space, and NIC information Operating system Version and patch level Network topology Router, gateway, and IP address information Problem description: Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes Licensing and registration Customer service If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: Customer service information is available at the following URL: Customer Service is available to assist with non-technical questions, such as the following types of issues: Questions regarding product licensing or serialization Product registration updates, such as address or name changes General product information (features, language availability, local dealers) Latest information about product updates and upgrades Information about upgrade assurance and support contracts Information about the Symantec Buying Programs Advice about Symantec's technical support options Nontechnical presales questions Issues that are related to CD-ROMs, DVDs, or manuals

6 Support agreement resources If you want to contact Symantec regarding an existing support agreement, please contact the support agreement administration team for your region as follows: Asia-Pacific and Japan Europe, Middle-East, and Africa North America and Latin America

7 Contents Technical Support... 4 Section 1 Introducing the Information Manager Chapter 1 Overview About Symantec Security Information Manager What's new in this release New features Features of Information Manager About estimating system performance Chapter 2 Section 2 Understanding the Information Manager components About workflow in Information Manager About Information Manager components About security products and devices About event collectors About the Symantec Global Intelligence Network About the Information Manager Web service About Information Manager servers Managing roles, permissions, users, and organizational units Chapter 3 Managing roles and permissions About managing roles About planning for role creation About the administrator roles Creating a role Editing role properties Deleting a role About working with permissions About permissions... 56

8 8 Contents About the propagation of permissions Modifying permissions from the Permissions dialog box Chapter 4 Managing user and user groups About users and passwords Creating a new user Creating a user group About editing user properties Changing a user s password Specifying user business and contact information Managing role assignments and properties Managing user group assignments Specifying notification information About modifying user permissions Modifying a user group Deleting a user or a user group Customizing the password policy Chapter 5 Managing organizational units and computers About organizational units About managing organizational units Creating a new organizational unit About determining the length of the organizational unit name Editing organizational unit properties Deleting an organizational unit About managing computers within organizational units Creating computers within organizational units About editing computer properties Distributing configurations to computers in an organizational unit Moving a computer to a different organizational unit About modifying computer permissions Deleting a computer from an organizational unit About the Visualizer Chapter 6 Configuring a service provider About using Information Manager in a service provider context About the service provider environment from the client perspective

9 Contents 9 About the service provider environment from the provider perspective About customizing the Incidents view in a Service Provider Master console About responding to a client incident Creating Information Manager tickets in a Service Provider Master context Exporting incident information from the Client Incident viewer About setting up a Service Provider environment Configuring an instance of Information Manager as a Service Provider client Configuring an Information Manager server as a Service Provider Master Configuring service provider client management accounts Synchronizing the Service Provider Master with client incidents Disconnecting a client from a Service Provider Master Section 3 Planning for security management Chapter 7 Managing the correlation environment About the Correlation Manager About the Correlation Manager knowledge base About the default rules set Chapter 8 Defining rules strategy About creating the right rule set for your business About defining a rules strategy About correlation rules About rule conditions About rule types About event criteria About the Event Count, Span, and Table Size rule settings About the Tracking Key and Conclusion Creation fields About the Correlate By and Resource fields Importing existing rules Creating custom correlation rules About automatically assigning incidents Assigning incidents automatically to the least busy member in a user group

10 10 Contents Creating a multicondition rule Creating a correlation rule based on the X not followed by Y rule type Creating a correlation rule based on the X not followed by X rule type Creating a correlation rule for the Y not preceded by X rule type Creating a correlation rule for the Lookup Table Update Enabling and disabling rules Working with the Lookup Tables window Creating a user-defined Lookup Table Importing Lookup Tables and records Section 4 Understanding event collectors Chapter 9 Introducing event collectors About Event Collectors and Information Manager Components of collectors Chapter 10 Installing event collectors Before you install collectors Requirements for point products and the collectors Updating the hosts file About installation and configuration tasks for collectors Registering Collectors Installing the Symantec Event Agent Preinstallation requirements About installing the Event Agent Installing the Event Agent on Windows Installing the Event Agent on Solaris Installing the Event Agent on Linux About uninstalling the Event Agent About uninstalling the Event Agent on Windows About uninstalling the Event Agent on Linux and Solaris Event Agent Management with agentmgmt.bat utility Verifying Symantec Event Agent installation Verifying Symantec Event Agent operation Installing the collector on a remote computer Installing collectors on an Information Manager server Verifying collector installation Verifying collector configuration

11 Contents 11 About Symantec Universal Collectors Downloading and installing the Symantec Universal Collectors Chapter 11 Configuring point products and collectors About configuring a point product to work with a collector Creating and configuring sensors Creating a new sensor configuration Configuring the collector sensor to receive security events Adding, renaming, deleting, and disabling sensors Importing and exporting sensor properties Updating sensor properties globally Configuring collector raw event logging Chapter 12 Section 5 Configuring collectors for event filtering and aggregation Configuring event filtering Configuring event aggregation Working with events and event archives Chapter 13 Managing event archives About events, conclusions, and incidents About the Events view About the event lifecycle About event archives About multiple event archives Creating new event archives Restoring event archives Specifying event archive settings Creating a local copy of event archives on a network computer Viewing event data in the archives About the event archive viewer right pane Manipulating the event data histogram Setting a custom date and time range About viewing event details Modifying the format of the event details table Searching within event query results Filtering event data About working with event queries

12 12 Contents Using the Source View query and Target View query Creating query groups Creating custom queries Querying across multiple archives Managing the color scheme that is used in query results Editing queries Importing queries Exporting queries Publishing queries About querying for IP addresses Deleting queries Scheduling queries that can be distributed as reports Chapter 14 Forwarding events to an Information Manager server About forwarding events to an Information Manager server About registering a security directory Registering the Information Manager with a security domain Activating event forwarding Stopping event forwarding Chapter 15 Understanding event normalization About event normalization About normalization (.norm) files Chapter 16 About Effects, Mechanisms, and Resources About Effects, Mechanisms, and Resources (EMR) About Effects values About Mechanisms values About Resources values EMR examples Chapter 17 Collector-based event filtering and aggregation About collector-based event filtering and aggregation About identifying common events for collector-based filtering or aggregation About preparing to create collector-based rules Accessing event data in the Information Manager console

13 Contents 13 Creating collector-based filtering and aggregation specifications Examples of collector-based filtering and aggregation rules Filtering events generated by specific internal networks Filtering common firewall events Filtering common Symantec AntiVirus events Filtering or aggregating vulnerability assessment events Filtering Windows Event Log events Chapter 18 Working with the Assets table About the Assets table About how event correlation uses Assets table entries About CIA values in the Assets table Importing assets into the Assets table Searching, filtering, and sorting assets Visual identification of the IP addresses also on the IP Watchlist About vulnerability information in the Assets table About using a vulnerability scanner to populate Assets table About locked and unlocked assets in the Assets table Using the Assets table to help reduce false positives About filtering events based on the operating system About using CIA values to identify critical events About using Severity to identify events related to critical assets About using the Services tab About associating policies with assets to reduce false positives or escalate events to incidents Section 6 Configuring the Information Manager Chapter 19 Configuring the Console About configuring Information Manager Identifying critical systems Adding a policy Specifying networks

14 14 Contents Chapter 20 Configuring general settings in the Web configuration interface About the Settings view Editing the Hosts file Changing the network settings Changing date and time settings Changing a Network Time Protocol Server About the Password view Changing the password for Linux accounts Changing the password for symcmgmt Linux account About the Global Intelligence Network configuration view About running LiveUpdate Running LiveUpdate from the Information Manager Web configuration interface About integrating Active Directory with the Information Manager server Managing Active Directory configurations Adding the CA root certificate Shutting down the Information Manager server Restarting the Information Manager server About using the multipath feature for storage options About External Storage Creating NAS Configuration Deleting NAS configuration Connecting Information Manager to a SAN Connecting Information Manager to a DAS Configuring Information Manager with DAS/SAN Storage Extending the storage capacity of an existing DAS/SAN configuration Unmounting the DAS/SAN configuration Restoring a DAS/SAN configuration Deleting a DAS/SAN configuration Chapter 21 Managing Global Intelligence Network content About managing Global Intelligence Network content Registering a Global Intelligence Network license Viewing the status of Global Intelligence Network content Receiving Global Intelligence Network content updates

15 Contents 15 Chapter 22 Working with Information Manager configurations About agent configurations About Agent Connection Configurations Configuring Agent to Manager failover About the Information Manager configurations About the Manager components configurations Setting up blacklisting for logon failures Modifying administrative settings About Manager configurations Increasing the minimum free disk space requirement in high logging volume situations About Manager connection configurations About configuring Information Manager directories About configuring LiveUpdate About Java LiveUpdate Creating Java LiveUpdate configurations Scheduling LiveUpdate requests Modifying Java LiveUpdate configurations Editing Java LiveUpdate configuration properties Distributing a Java LiveUpdate configuration Section 7 Managing application data Chapter 23 Maintaining the Information Manager database About database maintenance Checking database status About the database health monitor service About purging event summary, alerts, and incident data Adjusting parameters for automated purges Setting the safe level and the alarm level for automated purges Chapter 24 Managing data backup, restore, and purge About backup, restore, and purge Performing a complete LDAP directory server backup Performing a complete LDAP directory server restore Performing a complete database backup Performing a complete database restore

16 16 Contents Performing a selective backup Performing a selective restore Scheduling a backup Editing a scheduled backup Deleting a scheduled backup Purging incident or event summary data Purging selective backup files Section 8 Appendix Appendix A Firewall Settings for the Information Manager Firewall settings Index

17 Section 1 Introducing the Information Manager Chapter 1. Overview Chapter 2. Understanding the Information Manager components

18 18

19 Chapter 1 Overview This chapter includes the following topics: About Symantec Security Information Manager What's new in this release Features of Information Manager About estimating system performance About Symantec Security Information Manager Information Manager provides real-time event correlation and data archiving to protect against security threats and to preserve critical security data. Information Manager collects and archives security events from across the enterprise. These events are correlated with the known asset vulnerabilities and current security information from the Global Intelligence Network. The resulting information provides the basis for real-time threat analysis and security incident identification. Information Manager archives the security data for forensic and regulatory compliance purposes. Information Manager collects, analyzes, and archives information from security devices, critical applications, and services, such as the following: Firewalls Routers, switches, and VPNs Enterprise antivirus Intrusion detection systems and Intrusion Prevention Systems Vulnerability scanners Authentication servers

20 20 Overview What's new in this release Windows and UNIX system logs Information Manager provides the following features to help you recognize and respond to threats in your enterprise: Normalization and correlation of events from multiple vendors. Event archives to retain events in both their original (raw) and normalized formats. Distributed event filtering and aggregation to ensure that only relevant security events are correlated. Real-time security intelligence updates from Global Intelligence Network. These updates keep you apprised of global threats and let you correlate internal security activity with external threats. Customizable event correlation rules to let you fine-tune threat recognition and incident creation for your environment. Security incident creation, ticketing, tracking, and remediation for quick response to security threats. Information Manager prioritizes incidents based upon the security policies that are associated with the affected assets. An Event Viewer that lets you easily mine large amounts of event data and identify the computers and users that are associated with each event. A client-based console from which you can view all security incidents and drill down to the related event details. These details include affected targets, associated vulnerabilities, and recommended corrective actions. Predefined and customizable queries to help you demonstrate compliance with the security and the data retention policies in your enterprise. A Web-based configuration interface that lets you view and customize the dashboard, configure settings, and manage events, incidents, and tickets remotely. You can download various utilities and perform routine maintenance tasks such as backup and restore. You can use the custom logs feature with the universal collectors to collect and map information from devices for which standard collectors are not available. See Features of Information Manager on page 22. What's new in this release Information Manager contains enhanced features. It also includes fixes for the known issues that existed in the previous versions. See New features on page 21.

21 Overview What's new in this release 21 New features Information Manager includes the following new features in addition to known issues and fixes: Symantec SIEM 9700 Series appliances SSIM Web Start Client Role-based access to the Event Query Templates Navigation option for Event Storage Rules list Symantec SIEM 9700 Series appliances Symantec SIEM 9700 Series appliances are scalable security information and event management appliances. These appliances provide reliable performance with Information Manager software. The SIEM 9700 Series is comprised of three models; the 9750, the 9751, and the Each model provides 3.9TB of redundant event storage and dedicated Remote Management Module features to allow remote management of the appliance. In addition, the 9751 and 9752 provide enterprise connectivity through 8GB Fibre Channel. Each physical appliance can be combined seamlessly with virtual appliances to ease interoperability. For more information, see the following guides: Symantec SIEM 9700 Series Appliances Maintenance Guide Symantec SIEM 9700 Series Appliances Installation Guide Symantec SIEM 9700 Series Appliances Product Description Guide Symantec SIEM 9700 Series Appliances Hardware Troubleshooting Guide Symantec SIEM 9700 Series Appliances Safety Guide See New features on page 21. SSIM Web Start Client By using SSIM Web Start Client, you can now reach the Information Manager console directly without downloading and installing the Information Manager console. The Launch SSIM Web Start Client link, that is located on the logon page of the Information Manager Web configuration interface, launches the Information Manager console. You can also access this link from the Downloads option on the Home view of the Web configuration interface. See New features on page 21.

22 22 Overview Features of Information Manager Role-based access to the Event Query Templates In Information Manager, an administrator can restrict the access of a user to Event Query Templates. Access to Event Query Templates can be controlled based on the View Event Query Templates permission that is granted to a role. By default, this permission is enabled for new roles. If the View Event Query Templates permission is disabled for a role, the user who is assigned with this role cannot access the Templates folder on the Events view. If the View Event Query Templates permission is enabled for a role, the user who is assigned with this role can access and run the Event Query Templates. See Enabling access to the Event Query Templates on page 46. See New features on page 21. Navigation option for Event Storage Rules list A Move to top option and a Move to bottom option are now available in the Event Storage rules list. These options can be used to move a rule directly to the top or to the bottom of the list. See New features on page 21. Features of Information Manager Symantec Security Information Manager 4.7 offers several new features over previous versions of Information Manager. You can find the following new features in the 4.7 release of the Information Manager: Information Manager is now hardware independent. You can now install the Information Manager software on the hardware of your choice subject to the minimum requirements. To identify the critical incidents and threats in your environment, the Information Manager lets you drill down into the reports and dashboards. Using the drill-down feature (available only on the console of the client), you can view the resources that are associated with an incident. This feature provides insights into the parts of the organization that the incident affects and the background information regarding the resources that are implicated. The drill-down feature helps simplify organizing, searching, and prioritizing specific assets or sets of assets, to assist in monitoring identity and access activities. The drill-down feature is supported on the following types of queries in the reports and dashboards:

23 Overview Features of Information Manager 23 Top N by field Trending for Top N by field Summary data queries The Information Manager now ships with version of the Symantec Event Agent. Active Directory Integration This feature allows the users of the Active Directory to access the Information Manager. This feature lets you configure the Information Manager server to use the Active Directory to perform user authentication. Report Templates The Information Manager has report content ready for regulatory compliance standards. These reports can automate the collection and analysis of log data. Therefore, businesses can provide the accountability and the transparency that is required to comply with stringent mandates and regulations. Report Templates are available for the following categories: HIPAA NERC SOX FISMA UK-DPA PCI-DSS ISO GLBA MISC Custom Log Management Using the Custom Log Management feature, you can now gather and correlate log data for applications universally for which collectors are not available. The Custom Log Management feature lets you collect logs from an application that the Information Manager does not support. You can analyze the received log data and adjust the fields where necessary so that the Information Manager can interpret the data. This feature helps in interpreting the log data that is collected from the application that the Information Manager does not support. The Information Manager provides Universal Collectors that you can use to collect the logs of applications that the Information Manager does not support. You can install the Universal Collectors on the computers on which Symantec Event Agent is installed. From the Custom Logs view on the Web configuration

24 24 Overview Features of Information Manager interface, you can map the application log data. Universal collectors collect this data to the fields that are defined in the Events view in the Information Manager. Advanced Event Correlation The Advanced Event Correlation feature now lets you define and use a combination of multiple rules to correlate events. The Advanced Event Correlation feature enables you to define multiple conditions in a rule. Multi-conditioning lets you define the rules that support up to five user activities in a sequence. You can create a conclusion when a sequence of a specified pattern is detected for one combination of one-to-many fields within a specified time period. Multi-conditioning provides flexibility and extensibility of the correlation rules. This flexibility significantly extends the ability of Information Manager to detect attacks and to identify the threats. Event definition with negatives is possible in the Information Manager server. You now have the ability to generate incidents based on negative occurrences. This means that the Information Manager can generate incidents based on expected events not occurring. Information Manager supports the definition of a rule that creates a conclusion when two user activities occur after one another that can be harmful. In addition to this type of rule definition, Information Manager also supports the definition of rules when a certain user activity does not occur after a valid user activity. The ability of Information Manager to generate events based on negative occurrences extends the possibility of threat detection. The Information Manager server supports the following rule types: Lookup Table Update Many Sources, One Target Many Symantec Signatures, One Source Many Symantec Signatures, One Target Many Targets, One Event Many Targets, One Source Many to One Multi-condition Single Event Symmetric Traffic Transitive Traffic

25 Overview Features of Information Manager 25 X not followed by X X not followed by Y Y not preceded by X Trending Queries The Information Manager lets you create a new query based on trends. The Trending Queries feature gives you a breakup of trend data for the Top N Events by Category (such as Product or Organizational Units) over a selected time frame. For example, you can view the Top Five Events Counts by Product over the last week. The results of the trending query can be displayed in a table, line bar, stacked, or multiple pie graphs. The user can query the trends over the following time slice parameters: Last 5 minutes Last 10 minutes Last 15 minutes Last 30 minutes Last 45 minutes Last hour Last 8 hours Last 12 hours Last 24 hours Last 48 hours Last 7 days Last 14 days Trend for the last five minutes plotted for each minute of the last five minutes. Trend for the last 10 minutes plotted for each minute of the last 10 minutes. Trend for the last 15 minutes plotted for each minute of the last 15 minutes. Trend for the last 30 minutes plotted for each minute of the last 30 minutes. Trend for the last 45 minutes plotted for each minute of the last 45 minutes. Trend for the last hour that is plotted for each minute of the last hour. Trend for the last eight hours plotted for each hour of the last eight hours. Trend for the last 12 hours plotted for each hour of the last 12 hours. Trend for the last 24 hours plotted for each hour of the last 24 hours. Trend for the last 48 hours plotted for each hour of the last 48 hours. Trend for the last seven days that is plotted for each day of the last seven days. Trend for the last 14 days that is plotted for each day of the last 14 days.

26 26 Overview Features of Information Manager Last 30 days Today Yesterday This week Last Week This Month This Month (Daily Trend) Last Month Last Month (Daily Trend) This Quarter This Quarter (Weekly trend) Last Quarter Last Quarter (Weekly Trend) This Year Last Year Trend for the last 30 days that is plotted for each day of the last 30 days. Trend for the present day that is plotted for every hour. Trend for the day before today that is plotted for every hour. Trend for this week that is plotted for each day of the week. Trend for the last week that is plotted for each day of the week. Trend for this month that is plotted for each week of the month. Trend for this month that is plotted for each day of the month. Trend for the last month that is plotted for each week of the month. Trend for the last month that is plotted for each day of the month. Trend for this quarter that is plotted for each month of the quarter. Trend for this quarter that is plotted for each week of the quarter. Trend for the last quarter that is plotted for each month of the quarter. Trend for the last quarter that is plotted for each week of the quarter. Trend for this year that is plotted for each month of the year Trend for the last year that is plotted for each month of the year. Information Manager lets you back up and restore data selectively. You can select the items for backup from the various components available for backup. From the list of backup files, you can select the components that need to be restored. You can select and restore only those data items that you require,

27 Overview About estimating system performance 27 instead of restoring all the data to an earlier state. Further you can also select and purge the backup files. Only those backup files that were selectively backed up can be purged. About estimating system performance To determine the performance of an Information Manager server or set of servers. consider your unique environment. Information Manager integrates with a wide range of event collectors, and by nature requires the customization of settings to match each environment. Hence, the physical performance depends greatly on the collectors and settings that you choose. The observed events per second (EPS) rates under optimal circumstances are provided here which can be used for general planning purposes. You can create a rough estimate of system performance by using the information available in these tables. However, you must note that the system performance may vary widely from these figures depending on your specific environment. Your estimates need to be adjusted over time as your policies, settings, and storage requirements are refined. Note: The performance figures are currently being updated. An addendum to Symantec Security Information Manager Administrator Guide will be available soon with the new performance figures. See About Symantec Security Information Manager on page 19.

28 28 Overview About estimating system performance

29 Chapter 2 Understanding the Information Manager components This chapter includes the following topics: About workflow in Information Manager About Information Manager components About workflow in Information Manager The Symantec Security Information Manager workflow includes the following steps: Event collectors gather events from Symantec and third-party point products. See About Event Collectors and Information Manager on page 163. Events are filtered and aggregated. See Configuring event filtering on page 197. See Configuring event aggregation on page 200. Symantec Event Agent forwards both the raw and the processed events to the Information Manager server. See About forwarding events to an Information Manager server on page 241. See Activating event forwarding on page 245. The Information Manager server stores the event data in event archives. See About event archives on page 210. The Information Manager server correlates the events with threat and asset information based on the various correlation rules.

30 30 Understanding the Information Manager components About Information Manager components See About the Correlation Manager on page 115. Information Manager security events trigger a correlation rule and create a security incident. About Information Manager components Symantec Security Information Manager has the following components: Security products and devices See About security products and devices on page 31. Event collectors See About event collectors on page 31. Information Manager servers See About Information Manager servers on page 32. Global Intelligence Network See About the Symantec Global Intelligence Network on page 32. Web service See About the Information Manager Web service on page 32. Figure 2-1 Components in an Information Manager setup

31 Understanding the Information Manager components About Information Manager components 31 About security products and devices About event collectors The security products and devices in your enterprise can generate overwhelming amounts of security data. Many firewalls can generate over 500 GB of security data per day; intrusion detection systems can trigger over 250,000 alerting incidents per week. Most security products store event data in a proprietary format, accessible only by the tools that the security products provide. To secure your enterprise effectively, you need to collect, normalize, and analyze the data from all parts of your enterprise. See About Information Manager components on page 30. Event collectors gather security events from a variety of event sources, such as databases, log files, and syslog applications. Event collectors translate the event data into a standard format, and optionally filter and aggregate the events. The event collectors then send the events to Symantec Security Information Manager. You can configure event collectors to also send the event data in its original format. You install event collectors either on the security product computer or at a location with access to the security product events. To facilitate installation and setup, event collectors for third-party firewalls are preinstalled on the Information Manager server. After the event collector is registered with Information Manager, you can configure event collector settings from the Information Manager console. The event collector settings include the event source specification and any event filter or aggregation rules. Symantec provides event collectors for the following types of products: Firewalls Routers, switches, and VPNs Intrusion detection and prevention systems Vulnerability scanners Web servers, filters, and proxies Databases Mail and groupware Enterprise antivirus Microsoft authentication services Windows and UNIX system logs

32 32 Understanding the Information Manager components About Information Manager components For access to the extensive library of event collectors, visit Symantec support at the following Web site: See About Information Manager components on page 30. About the Symantec Global Intelligence Network Information Manager has access to current vulnerability, attack pattern, and threat resolution information from the Threat and Vulnerability Management Service. The Symantec Global Intelligence Network powers the Threat and Vulnerability Management Service. The Symantec Global Intelligence Network is a comprehensive collection of vendor-neutral security data sources. The service is an authoritative source of information about known and emerging vulnerabilities, threats, risks, and global attack activity. See About Information Manager components on page 30. About the Information Manager Web service The Web service of Symantec Security Information Manager lets you securely access and update the data that is stored on a server. You can use the Web service to publish event, asset, incident, ticket, and system setting information. You can also use the Web service to integrate Information Manager with help desk, inventory, or notification applications. See About Information Manager components on page 30. For more information on interfacing your application to use the Web service, see the application documentation or your application vendor. About Information Manager servers Symantec Security Information Manager is hardware independent. You can install the Information Manager server on any approved hardware that meets the minimum system requirements. You can deploy one or more Information Manager servers in various roles to satisfy the event gathering, archiving, and event correlation requirements for your enterprise. To account for traffic variation, a single Information Manager is only recommended for a security environment that generates up to 1,000 events per second (EPS) on average and that requires a maximum of 4 MB to 8 MB per day of event data storage. To increase the overall event processing rate, you can add multiple load sharing Information Managers to your deployment. You can configure each server for dedicated event collection, event archiving, or event

33 Understanding the Information Manager components About Information Manager components 33 correlation. In most cases, a combination of multiple servers that share the event and the incident processing load is preferred. See About Information Manager components on page 30.

34 34 Understanding the Information Manager components About Information Manager components

35 Section 2 Managing roles, permissions, users, and organizational units Chapter 3. Managing roles and permissions Chapter 4. Managing user and user groups Chapter 5. Managing organizational units and computers Chapter 6. Configuring a service provider

36 36

37 Chapter 3 Managing roles and permissions This chapter includes the following topics: About managing roles About working with permissions About managing roles A role is a group of access rights for a product. Users who are members of a role have access to the event viewing and management capabilities that are defined for that role. A user can be a member of more than one role. See About planning for role creation on page 38. You create new roles in the Symantec Security Information Manager console. When you click Roles on the System view of the console, you can perform the following tasks: Create a role. See Creating a role on page 40. Edit role properties. See Editing role properties on page 48. Delete a role. See Deleting a role on page 55. Note: Only members of the SES Administrator role and the Domain Administrator role can add or modify roles. See About the administrator roles on page 39.

38 38 Managing roles and permissions About managing roles About planning for role creation Roles control user access; therefore, before you create roles you should plan carefully. You need to identify the tasks that are done in your security environment, and who performs them. The tasks determine the type of roles that you must create. The users who perform these tasks determine which users should be members of each role. See About managing roles on page 37. Consider the following issues: Who allocates responsibilities within your security environment? If these users need to create roles, they must be members of the Domain Administrator role. Who administers your security network by creating management objects such as users and organizational units? These users must be members of the roles that provide management access and the ability to access the System view. Which products are installed, and who is responsible for configuring them? These users must be members of management roles for the products for which they are responsible. They may need access to the System view only. Who is responsible for monitoring events and incidents? These users must be members of event viewing roles for the products for which they are responsible. Users who monitor events must have access to the Events view. Users who monitor incidents must have access to the Events view and the Incidents view. Who responds to problems and threats? These users must have access to the Events view and the Incidents view. Users who create and manage help desk tickets must also have access to the Tickets view. Table 3-1 lists the common roles in a security environment and the responsibilities that belong to each role. Table 3-1 Role name Typical roles and responsibilities Responsibilities Domain Administrator System Administrator Defines the user roles and role authority. Manages Information Manager. Verifies that events flow into the system and that the system functions normally.

39 Managing roles and permissions About managing roles 39 Table 3-1 Role name Typical roles and responsibilities (continued) Responsibilities User Administrator Creates the correlation rules and collection filters. Performs the user and the device administration. Information Manager Views all incidents, events, reports, and actions. Report Writer Views the incidents, events, and reports for assigned devices. Reviews and validates incident response. Provides the affirmation of incident review and response by administrators to GAO and others. Report User Rule Editor Views the events and reports for assigned devices. Creates, edits, and deploys rules. About the administrator roles When you install the Information Manager, the following default administrator roles are created: SES Administrator Domain Administrator This role has full authority over all of the domains in the environment. This role has full authority over one specific domain in the environment. If you have only one domain, the rights of the SES Administrator role and the Domain Administrator role are the same. If you have multiple domains (for example one for each geographic region of your company), each domain has a Domain Administrator. Members of this role can perform functions such as creating users and additional roles within that domain. The SES Administrator role can perform these functions for all of the domains that you configure. The default user, administrator, is also created when Information Manager is installed. The administrator is automatically a member of the SES Administrator and Domain Administrator roles. To access Information Manager for the first time, you must log on as this default user. The password for the administrator user account is specified at the time of installation. You can add users to the administrator roles, but you cannot change any other characteristics of these roles. If a user is a member of the SES Administrator role, that user should not be assigned to any other roles.

40 40 Managing roles and permissions About managing roles Creating a role See Editing role properties on page 48. You can create roles using the Role Wizard in the Information Manager console. Only a user who has either the Domain Administrator role or the SES Administrator role can create roles. See About planning for role creation on page 38. Note: If the Role members will have access to all archives option is selected, role members can access new archives automatically. If the Role members will have access to only the selected archives option is selected, role members cannot access new archives automatically. To create a role 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and click Roles. 3 On the toolbar, click + (the plus icon). 4 In the first panel of the Role Wizard, click Next. 5 In the General panel, do the following, and click Next: In the Role name text box, type a name for the role. In the Description text box, type a description of the role (optional). 6 In the Products panel, do one of the following: To give the role members access to all of the listed products, click Role members will have access to all products, and click Next. To limit the role member's access to certain products, click Role members will have access to only the selected products and select the appropriate products. Then click Next. Symantec Security Information Manager is checked by default in the Product List. 7 In the SSIM Permissions panel, do one of the following: To give role members all permissions that apply to Information Manager, click Enable all Permissions, and click Next. To give role members a limited set of permissions, click Enable specific Permissions. From the permissions list, uncheck the permissions that you do not want to enable and click Next.

41 Managing roles and permissions About managing roles 41 8 In the Console Access Rights panel, do one of the following: To give role members the ability to see all parts of the Information Manager console, click Role members will have all console access rights, and click Next. To limit what role members can see when they display the console, click Role members will have only the selected console access rights. From the list, enable at least one of the console access rights, and click Next. See Modifying Information Manager console access rights on page In the Organizational Units panel, do one of the following: To give role members access to all organizational units, click Role members will have access to all organizational units, and click Next. To give role members access to specific organizational units, click Role members will have access to only the selected organizational units. In the organizational unit tree, select at least one organizational unit to associate with this role, and click Next. When you select an organizational unit that has additional organizational units, users of the role are given access to those additional organizational units also. If you add an organizational unit to a role, the following users can see the events that are generated by the security products: Users who are role members Users who have event viewing access These users can view only those events that are generated by the security products that are installed on the computers of that organizational unit. Role members can see events only from computers in the organizational units that have been added to their roles. 10 In the Servers panel, do one of the following: To give role members access to all of the Information Manager servers in your security environment, click Role members will have access to all servers, and click Next. To limit role members' access to certain servers, click Role members will have access to only the selected servers. In the server tree, select at least one server to associate with this role, and click Next. Members of the role can modify configurations on the selected servers. The role members can also view event archives that reside on the selected servers. 11 In the Members panel, do one of the following:

42 42 Managing roles and permissions About managing roles To add individual users to the role now, click Add Members. In the Find Users dialog box, add one or more users, from the Available Users list to the Selected Users list and click OK. In the Members panel, click Next. To add the users who are members of a specific user group, click Add Members From Groups. In the Find User Groups dialog box, add one or more user groups, and click OK. The users that are associated with the groups you selected are added to the Selected Users list. When you are finished, click Next. To continue without adding users to the role, click Next. You can add users to the role later by editing the role s properties. See Adding a user to a role on page 43. You can also associate a role with a user by editing the user s properties. You can assign users to a role only if you have already created those users. See Creating a new user on page In the Role Summary panel, review the information that you have specified, and click Finish. The role properties that are created are shown in the list at the bottom of the panel. A green check mark next to a task indicates that it was successfully completed. 13 Click Close. Editing role properties After you create a role in Information Manager, you can modify it by editing its properties. For example, as you create new organizational units or users, you can add them to existing roles. You can edit the properties of a role by selecting the role in the right pane. You can also edit the role properties from any dialog box that displays the role s properties. To edit role properties 1 On the System view, in the left pane of the Administration tab, navigate to the relevant domain, and click Roles. 2 In the right pane, right-click the role to edit, and select Properties. 3 Use the Editing Role Properties dialog box to make changes to the role. 4 To save changes and close the dialog box, click OK. See Adding a user to a role on page 43.

43 Managing roles and permissions About managing roles 43 See Modifying Information Manager console access rights on page 47. See Modifying product access rights on page 44. See Modifying server access rights on page 48. See Modifying access permissions in roles on page 49. Adding a user to a role When a user logs on to Information Manager, the user s role membership determines the user's access to the various products and event data. You can assign a user to a role in the following ways: Assign each user individually to one or more roles. Assign users to groups, and assign user groups to roles. When you assign a user group to a role, all of the users who are currently in the group are assigned to that role. However, if you later add more users to the user group, those users are not automatically added to the role. You must assign each user to the role individually. Note: Before you assign users and user groups to roles, you must create users and user groups in the Directory. See Creating a new user on page 63. See Creating a user group on page 65. To add a user to a role 1 On the System view, in the left pane of the Administration tab, navigate to the relevant domain, and click Roles. 2 In the right pane, right-click the role to edit, and select Properties. 3 In the Editing Role Properties dialog box, in the left pane, click Members. 4 Click Add Members. 5 In the Find Users dialog box, in the list of available users, search for a user within a domain or a user group. You can also search for a user by entering the logon name, last name, or first name and then click Start Search. All of the users who meet the criteria you entered appear in the available users list. Select a user name (or Ctrl + click multiple user names), and click Add. The user name appears in the Selected users list. 6 To view or edit the properties of a user, click the user name, and click Properties.

44 44 Managing roles and permissions About managing roles 7 In the User Properties dialog box, view or make changes to the properties, and click OK. 8 In the Find Users dialog box, click OK. 9 In the Editing Role Properties dialog box, click OK. To add a user group to a role 1 On the System view, in the left pane of the Administration tab, navigate to the relevant domain, and click Roles. 2 In the right pane, right-click the role to edit, and select Properties. 3 In the Editing Role Properties dialog box, in the left pane, click Members. 4 Click Add Members From Groups. 5 In the Find User Groups dialog box, select the domain of the group from the drop-down list. 6 In the list of available user groups, click a user group name (or Ctrl + click multiple user names), and click Add. The user group name appears in the Selected user groups list. 7 To view or edit the properties of a user group, click the user group name, and click Properties. 8 In the User Group Properties dialog box, view or make changes to the properties, and click OK. 9 In the Find User Groups dialog box, click OK. 10 In the Editing Role Properties dialog box, click OK. See Editing role properties on page 48. Modifying product access rights The Products property lets you select and modify the products to which role members have access. To modify product access rights 1 On the System view, in the left pane of the Administration tab, navigate to the relevant domain, and click Roles. 2 In the right pane, right-click the role to edit, and select Properties. 3 In the left pane, click Products. 4 Do one of the following: To give the role members access to all of the listed products, click Role members will have access to all products.

45 Managing roles and permissions About managing roles 45 To limit the role members' access to specified products, click Role members will have access to only the selected products. Enable (check) or disable (uncheck) access to individual products in the list. Consider the tasks that role members perform as you select products from the list. Modifying access permissions in roles describes the access requirements of typical enterprise security roles. 5 Click OK. See Editing role properties on page 48. Modifying SIM permissions Use the SIM Permissions property to enable or disable several types of Information Manager permissions that are assigned to a role. See About managing roles on page 37. To modify SIM permissions 1 On the System view, in the left pane of the Administration tab, navigate to the relevant domain, and click Roles. 2 In the right pane, right-click the role to edit, and select Properties. 3 In the left pane click SIM Permissions. 4 Do one of the following: 5 Click OK. To assign all Information Manager permissions to the role, click Enable all Permissions. To limit the permissions that are assigned to the role, click Enable specific Permissions. Then click the check boxes as needed to enable or disable permissions for the role. Table 3-2 lists the permissions that the users who perform specific functions need. About the Bypass Event RBAC option When you create or modify a role, you can choose to enable the Bypass Event RBAC option. Bypass Event RBAC gives unrestricted access to all of the event archives for which role a user has been granted access. When a user with this role performs an event query, the query bypasses any additional permission settings based on Organizational Unit, Domain, or Product settings. The query returns a complete data set from the archives for which the user has been given access. Enabling Bypass Event RBAC enhances query

46 46 Managing roles and permissions About managing roles performance by reducing the set of permissions criteria against which the query must be processed. See About managing roles on page 37. About the Bypass Event RBAC option When you create or modify a role, you can choose to enable the Bypass Event RBAC option. Bypass Event RBAC gives unrestricted access to all of the event archives for which role a user has been granted access. When a user with this role performs an event query, the query bypasses any additional permission settings based on Organizational Unit, Domain, or Product settings. The query returns a complete data set from the archives for which the user has been given access. Enabling Bypass Event RBAC enhances query performance by reducing the set of permissions criteria against which the query must be processed. See About managing roles on page 37. Enabling access to the Event Query Templates The View Event Query Templates permission in a role controls the access to the Templates folder in the Events view. If this permission is enabled for a role, the user who is assigned with the role can access the Event Query Templates. For example, the Information Manager administrator creates two roles, IncidentAnalyst and EventAnalyst. The View Event Query Templates permission is disabled for the IncidentAnalyst role, and enabled for the EventAnalyst Role. The IncidentAnalyst role is assigned to user A and the EventAnalyst role is assigned to user B. From the Events view, user A who is assigned with the IncidentAnalyst role cannot view the Event Query Templates. User B who is assigned with the EventAnalyst role can view the Event Query Templates and run the corresponding queries. You can edit the existing roles to enable the View Event Query Templates permission. To enable View Event Query Templates permission for existing roles 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and click Roles. 3 On the right panel, right-click the role that you want to edit and select Properties. 4 In the Editing Role Properties dialog box, select SIM Permissions. 5 Click Enable specific permissions.

47 Managing roles and permissions About managing roles 47 6 From the permissions list, check View Event Query Templates. 7 Click Save and then click OK. By default, this permission is enabled for new roles. While creating a role, you can disable the View Event Query Templates permission for a new role. Select the Enable specific permissions option from the SIM Permissions panel and then uncheck View Event Query Templates. See Creating a role on page 40. See Role-based access to the Event Query Templates on page 22. Modifying Information Manager console access rights Console access rights control the views that a role member can access when they log on to the Information Manager console. You can modify the Console access rights that you assigned when you created the role. Based on the Console access rights, various views of the console are visible to the role members whenever they log on to Information Manager. To modify console access rights 1 On the System view, in the left pane of the Administration tab, navigate to the relevant domain, and click Roles. 2 In the right pane, right-click the role to edit, and select Properties. 3 In the left pane, click Console Access Rights. 4 Do one of the following: To give members of the role the ability to see all components of the Information Manager console, click Role members will have all console access rights. To limit what members of the role can see when they display the Information Manager console, click Role members will have only the selectedconsoleaccessrights. From the list that appears, enable or disable console access rights as you want. The following table describes the tiles (views in the Information Manager console) that are available to members: Show Assets Tile Show Dashboard Tile Displays the Assets view in the console. Displays the Dashboard view in the console.

48 48 Managing roles and permissions About managing roles Show Events Tile Show Incidents Tile Show Intelligence Tile Show Reports Tile Show Rules Tile Show Statistics Tile Show System Tile Show Tickets Tile Displays the Events view in the console. Displays the Incidents view in the console. Displays the Intelligence view in the console. Displays the Reports view in the console. Displays the Rules view in the console. Displays the Statistics view in the console. Displays the System view in the console. Displays the Tickets view in the console. Modifying access permissions in roles lists the console access rights that the users who perform specific functions need. 5 Click OK. See Editing role properties on page 48. Modifying server access rights Use the Servers property to select the servers to which role members have access. The selections for this property determine the servers that the role members can see on the following console locations: The Testing tab on the Rules view that can be used for testing a specific rule. The servers and archives that are available for each query on the Events view. The Server Configurations tab on the System view. To modify server access rights 1 On the System view, in the left pane of the Administration tab, navigate to the relevant domain, and click Roles. 2 In the right pane, right-click the role to edit, and select Properties.

49 Managing roles and permissions About managing roles 49 3 In the left pane, click Servers. 4 Do one of the following: To give role members access to all Information Manager servers in the network configuration, click Role members will have access to all servers. To limit role members' access to certain servers, click Role members will have access to only the selected servers. In the server tree, select at least one server to associate with this role, and click OK. See Editing role properties on page 48. Modifying access permissions in roles Roles include the permissions that determine the types of access (for example, Read and Delete) for a role member. Based on these permissions a role member can access various functions on the Information Manager console. Permissions are assigned to roles on various functions and the users belonging to those roles can perform tasks accordingly. You can change the access permissions for the following types of objects: Container objects that were created when you installed Information Manager, such as organizational units. The new objects that you create within the container objects. When you view the properties of a role, you can view and modify the permissions by selecting tabs in the Editing Role Properties dialog box. Warning: Permission modification is an advanced feature. You should customize permissions only if you have a clear understanding of how access control works. See About working with permissions on page 55. Table 3-2 describes the access requirements of typical enterprise security roles.

50 50 Managing roles and permissions About managing roles Table 3-2 Access requirements for roles Role Products Symantec Security Information Manager permissions Console access Access permissions SES Administrator and Domain Administrator All All All All Note: You cannot modify access permissions of the SES Administrator and Domain Administrator roles. System Administrator Information Manager Allow Asset Edits Move Computers Show Dashboard Tile Show Intelligence Tile Show Statistics Tile Read and Search on Published / System Query groups Show System Tile User Administrator All Allow Dashboard Auto Refresh Move Computers Allow Asset Edits Manage Networks Manage Policies Manage Services Show Assets Tile Show Dashboard Tile Show Intelligence Tile Show Rules Tile Show System Tile Read and Search on Published /System Query groups Read and Write on users and user groups Read and Write on rules and roles

51 Managing roles and permissions About managing roles 51 Table 3-2 Access requirements for roles (continued) Role Products Symantec Security Information Manager permissions Console access Access permissions Information Manager Information Manager Create Incidents Write My Incidents Write All Incidents Change Assignee and Team on My Incidents Change Assignee and Team on All Incidents Change Assignee/Team to self or own team on unassigned incidents Change Status My Incidents Change Status All Incidents Read My Incidents Show Assets Tile Show Dashboard Tile Show Events Tile Show Incidents Tile Show Intelligence Tile Show Reports Tile Show Tickets Tile Read and Write on Published/System Query groups. In addition, Read and Write on Report groups based on the Symantec Security Information Manager permissions that are granted to the role. Read All Incidents Read Unassigned Incidents View Event Query Templates Create new queries Create new reports Publish queries Publish reports Allow Dashboard Auto Refresh Move Computers Allow Asset Edits Manage Networks Manage Policies Manage Services

52 52 Managing roles and permissions About managing roles Table 3-2 Access requirements for roles (continued) Role Products Symantec Security Information Manager permissions Console access Access permissions Report Writer Information Manager Write My Incidents Write All Incidents Change Assignee and Team on My Incidents Change Assignee and Team on All Incidents Change Assignee/Team to self or own team on unassigned incidents Change Status My Incidents Change Status All Incidents Read My Incidents Show Dashboard Tile Show Events Tile Show Incidents Tile Show Intelligence Tile Show Reports Tile Show Tickets Tile Read and Write on Published /System Query groups Read and Write on Report groups Read All Incidents Read Unassigned Incidents Create new queries Create new reports Publish queries Publish reports Allow Dashboard Auto Refresh Move Computers Allow Asset Edits Manage Networks Manage Policies Manage Services Report User Information Manager Create new queries Create new reports Allow Dashboard Auto Refresh Show Dashboard Tile Show Events Tile Show Reports Tile Read and Search on Published /System Query groups Read and Write on Report groups

53 Managing roles and permissions About managing roles 53 Table 3-2 Access requirements for roles (continued) Role Products Symantec Security Information Manager permissions Console access Access permissions Rule Editor Information Manager Create new queries Show Events Tile Show Rules Tile Show Statistics Tile Read and Write on Rules and Roles Read and Search on Published /System Query groups Read and Search on Report groups Note: When a role s access permissions to a Published Query Group or a System Query Group are changed, the role s database permissions may be incorrectly modified. If a user cannot view queries on the Events view, it may be because the user s role lacks the necessary database permissions. To correct this problem, do the following: Log on as a Domain Administrator or SES Administrator and open the Editing Role Properties dialog box for the user s role. On the DataStores tab, check the role s database permissions. If the role does not have both Read and Search permissions, add the missing permissions. See To modify access permissions in roles on page 53. To modify access permissions in roles 1 On the System view, in the left pane of the Administration tab, navigate to the relevant domain, and click Roles. 2 In the right pane, right-click the role to edit, and select Properties. 3 In the Editing Role Properties dialog box, in the left pane, click the type of permissions to modify. For example, to change the role members' directory permissions, choose Directories. 4 When you finish setting permissions, click OK. See Editing role properties on page 48. Using examples of modifying permissions in roles You can modify permissions for the following purposes, among others: To hide a query group from members of a role. When members of this role open the Query Chooser on the dashboard, they cannot see the restricted query group in the query tree.

54 54 Managing roles and permissions About managing roles To hide all users from members of a role. When members of this role view the System view, they do not see users in the left pane. To prevent role members from adding and deleting user groups Role members can view and modify user groups, but they cannot add and delete user groups. See About permissions on page 56. To hide a query group from members of a role 1 On the System view, in the left pane of the Administration tab, navigate to the relevant domain, and click Roles. 2 In the right pane, right-click the role to restrict, and select Properties. 3 In the left pane, click System Query Groups. 4 Click Add. 5 In the Find System Query Groups window, select Product Queries.Symantec Client Security, and click Add. 6 Click OK. 7 On the Product Queries.Symantec Client Security row, uncheck Read and Search. 8 Click OK. Members of this role cannot view Symantec Client Security queries. If a role member selects System Queries > Product Queries in the Query Chooser on the dashboard, the role member cannot view Symantec Client Security in the tree. To hide all users from members of a role 1 On the System view, in the left pane of the Administration tab, navigate to the relevant domain, and click Roles. 2 In the right pane, right-click the role to restrict, and select Properties. 3 In the left pane, click Users. 4 Under Default permissions for all users, uncheck all permission types (for example, Read and Add). 5 Click OK. When role members click Users in the left pane of the System view, they see only their own details in the right pane. Other users are not listed.

55 Managing roles and permissions About working with permissions 55 Deleting a role To prevent role members from adding and deleting user groups 1 On the System view, in the left pane of the Administration tab, navigate to the relevant domain, and click Roles. 2 In the right pane, right-click the role to restrict, and select Properties. 3 In the left pane, click User Groups. 4 On the top line of permissions, check Read, Write, and Search. Make sure that Add and Delete are not checked. 5 Click OK. Role members can view, search, and modify all user groups in the domain. They cannot create new user groups or delete user groups. You can delete roles when they are no longer in use. Before you delete a role, you can view the properties of the role to ensure that none of your users requires it. To delete a role 1 On the System view, in the left pane of the Administration tab, navigate to the relevant domain, and click Roles. 2 In the right pane, right-click the role to delete, and select Properties. 3 Review the role properties to make sure that no users require this role. 4 Click Cancel. 5 If you still want to delete the role, on the toolbar, click - (the minus symbol). A message warns you that all members of the selected role would be removed. Then, although the user accounts are not deleted, the users no longer have access to the role. 6 In the confirmation dialog box, click Yes to delete the role. See About managing roles on page 37. About working with permissions Permissions define the access that members of a role have to specific objects. Along with other role properties, permissions control what users can see and do when they log on to the Information Manager console.

56 56 Managing roles and permissions About working with permissions As with roles, you can work with permissions only if you are a member of the SES Administrator or Domain Administrator role. The permissions of objects are defined initially when you create roles and when you create new objects. You can then modify the permissions to fine-tune your roles. Warning: You should customize permissions only if you have a clear understanding of how access control works in the security (LDAP) directory. About permissions See About permissions on page 56. Permissions are always associated with roles and are applied when a member of a role logs on to the console. Table 3-3 shows the permissions that role members can have to view and work with objects. Table 3-3 Object permissions Permission Read Description Lets the role members see the attributes of objects. Read must be enabled for the other access permissions to work. Write Add Delete Search Lets the role members modify objects. Lets the role members create a new child object within the selected container. Lets the role members delete objects. Lets the role members search the database or the LDAP directory for objects. Search must be enabled for the other access permissions to work. The following objects have permissions: Container objects Container objects are created when the Datastore (database) and Directory are installed. These objects contain all of the new objects that you create.

57 Managing roles and permissions About working with permissions 57 In the console, container objects appear in the left pane of the Administration tab on the System view. Examples of the container objects that have permissions are users, user groups, roles, and organizational units. Objects that you create within container objects When you create new objects to represent your security environment, they are stored within the container objects. On the System view, the objects that you create appear in the right pane when you select their container object in the left pane. For example, when you select Users in the left pane, the individual users that you have created within the Users container are displayed. These created objects are sometimes known as child or leaf objects. You must understand the relationship between the permissions of container objects and the permissions of the objects you create within these containers. See About the propagation of permissions on page 57. About the propagation of permissions As you create new management objects, it is important to understand the relationship between the permissions of container objects and the permissions of the objects you create within these containers. In most cases, the permissions of a container object propagate to all new objects that you create within the container. When you create new objects on a role-by-role basis, the current permissions of the container object are propagated to the new objects. For example, in Role A, on the Users tab, you disable Write permission for the Users container. In Role B, you disable Delete permission for the Users container. When you create new users, members of Role A do not have Write permission, so they cannot modify the properties of the new users. Members of Role B do not have Delete permission, so they cannot delete the new users. However, if a user is assigned to two roles A and B. Role A that has the Add access for users and Role B that do not have Add access for users. In this case, the user who is assigned to these roles can add new users. Permissions of Role A take precedence over permissions of Role B

58 58 Managing roles and permissions About working with permissions Note: Most roles should have at least Read and Search permissions for all objects. These permissions allow role members to view information about the objects and perform searches for the objects. For example, if you enable Write access for a container object and disable Read access, the role members cannot modify the objects, because they cannot view the objects. Propagation occurs only when you create new objects. For example, you may create several users and assign them to role A before you disable the Write permission in role A. These permissions are not disabled for the original users unless you disable them explicitly for the existing user's of Role A. See About permissions on page 56. Modifying permissions from the Permissions dialog box You can use the following methods to modify permissions: Edit the role using the Editing Role Properties dialog box. Use this method to modify permissions for several objects within one role. See Modifying access permissions in roles on page 49. You can edit the permissions of software products and their configurations through the Products Tab on the Editing Role Properties dialog box. Use the Permissions dialog box for a particular object. Use this method to modify the permissions for a specific object. Note: Some objects do not have permissions. To modify permissions for a container object 1 On the System view, in the left pane of the Administration tab, navigate to the relevant domain. 2 In the left pane, right-click the container object (for example, Users) and select Permissions. In the Permissions dialog box, roles are listed if they have already been assigned to this object. Some container objects do not have permissions. 3 Do any of the following: To modify permissions for this object, check (enable) or uncheck (disable) the permissions corresponding to the listed roles, as needed.

59 Managing roles and permissions About working with permissions 59 You should not disable the Search permission. To add a role to this object, click Add. In the Find Roles dialog box, select a role, then click Add, and click OK. The role you added appears in the Permissions dialog box, where you can then enable or disable its permissions. To remove a role, click the role name, and click Remove. To edit a role s properties, click the role name, and click Properties. 4 Click OK when you finish modifying permissions. To modify permissions for a created object 1 On the System view, in the left pane of the Administration tab, navigate to the relevant domain. 2 In the left pane, click the container that contains the created object. For example, click Users. 3 In the right pane, right-click the object whose permissions you want to modify, and select Permissions. In the Permissions dialog box, roles are listed if they have already been assigned to this object. Some created objects do not have permissions, such as Policies. 4 Do any of the following: To modify permissions for this object, check (enable) or uncheck (disable) the permissions corresponding to the listed roles, as needed. You should not disable the Search permission. To add a role to this object, click Add. In the Find Roles dialog box, select a role, then click Add, and click OK. The role you added appears in the Permissions dialog box, where you can then enable or disable its permissions. To remove a role, click the role name, and click Remove. To edit a role s properties, click the role name, and click Properties. 5 Click OK when you finish modifying permissions.

60 60 Managing roles and permissions About working with permissions

61 Chapter 4 Managing user and user groups This chapter includes the following topics: About users and passwords Creating a new user Creating a user group About editing user properties About modifying user permissions Modifying a user group Deleting a user or a user group Customizing the password policy About users and passwords The Symantec Security Information Manager server uses accounts from Linux and the IBM DB2 Service. Both types of accounts use the password that is specified during installation. The default password is password. By default, the installation program creates the following Linux accounts: root simuser Default Linux administrative account Used by the Information Manager text console process

62 62 Managing user and user groups About users and passwords sesuser db2admin dasusr1 symcmgmt Used by the HTTP and the Tomcat processes Used by the database process Used for the DB2 Admin Tools database Used by the database process Warning: For security, change the Linux passwords periodically, according to your company's security policy. The password for all Linux accounts must be changed using the Change Password option (available under Settings > Passwords) from the Web configuration interface. Do not change these account passwords or permissions by standard Linux commands as it may result in errors with server operation. The password for the symcmgmt Linux account cannot be changed from the Web configuration interface. The password for a symcmgmt Linux account can be changed by using the standard Linux commands. This change in the password must be followed with an update in the Information Manager console under System > Administration > Data Stores. See Changing the password for Linux accounts on page 309. See Changing the password for symcmgmt Linux account on page 310. Usually, you are not required to create new Linux accounts. However, you may want to create an account with limited permissions to a file share to allow a user or process to copy LDAP backups. Refer to your Linux documentation for information on how to create Linux accounts. By default, the installation program also creates the administrator account in the IBM LDAP directory. This account is used for logging in to the Information Manager console and Information Manager Web configuration interface initially. With the proper permissions, you can also create new LDAP directory accounts for users who use the Information Manager console and Web configuration interface. These accounts are for the administrators of your security products, contacts for notifications, or both. Users who are administrators are members of the roles that define their administrative permissions. All users who need access to the Information Manager console must be members of one or more roles. If a user tries to log on to the console using an account that is not a member of a role, an error message is displayed. Users who only receive notifications do not have to be members of a role. See Creating a new user on page 63.

63 Managing user and user groups Creating a new user 63 Creating a new user See About editing user properties on page 66. See About modifying user permissions on page 72. See Deleting a user or a user group on page 74. See Creating a user group on page 65. See Modifying a user group on page 73. See Deleting a user or a user group on page 74. Use the Create a new User wizard to create a user. The wizard prompts you for the required information that the user needs to log on to Symantec Security Information Manager. It also lets you specify notification information, permissions, and other user properties. You can provide all the information at the time that you create the user. Alternatively, you can provide only the required information and add more information later by editing the user s properties. See About editing user properties on page 66. To create a new user 1 In the console of the Information Manager client, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and click Users. 3 On the toolbar, click + (the plus symbol) or right-click the Users node and select New. 4 In the first panel of the Create a new User wizard, click Next. 5 In the General panel, do the following: Logon name Last name First name Type the logon name for the new user. Type the user s last name. Type the user s first name. The other fields on this panel are optional. Click Next after you enter the details.

64 64 Managing user and user groups Creating a new user 6 In the Password panel, type a password in the Password text box and type the same characters in the Confirm password box. Click Next. The password that you choose must comply with the policy settings chosen by the administrator. The password is case sensitive. Green check marks under Password rules indicate that your password meets the requirements. 7 (Optional) In the Business panel, specify business information for the user, and click Next. See Specifying user business and contact information on page (Optional) In the Contact Information panel, specify contact information for the user, and click Next. 9 (Optional) In the Notifications panel, specify addresses and pager numbers for the user, and times when those contacts can be used for notifications. Click Next. See Specifying notification information on page In the Roles panel, you can assign the user to one or more roles that define the user s permissions, and click Next. You can also assign or change a user's roles later. A new user cannot log on unless a role is assigned to the user. See Managing role assignments and properties on page 68. You must create roles before you can assign users to roles. See Creating a role on page In the UserGroups panel, you can assign the user to one or more user groups, and click Next. You can also assign users to groups later. See Managing user group assignments on page 69. You must create user groups before you can assign users to groups. If no groups appear on the Find User Groups panel, you have not yet created any groups. See Creating a user group on page In the User Summary panel, review the information that you have specified, and click Finish. The user properties that are created are shown in the task status list at the bottom of the panel. A green check mark next to a task indicates that it was successfully completed. 13 Click Close.

65 Managing user and user groups Creating a user group 65 Creating a user group After you create users, you can assign them to groups. User groups are particularly useful when you have large numbers of users who need to have the same system roles. You can assign an entire user group to a role. All of the users in the group inherit the rights and the permissions that are assigned to that role. Implementing user groups also facilitates the auto-assignment of incidents, using correlation rules. The Create a new User Group wizard enables you to create user groups and add users to the groups. You can assign users at the time you create a group, or you can add users to the group later. Note: If you create a user group and assign it to a role, the users who are currently in the group are assigned to that role. However, if you later add more users to the user group, those users are not automatically added to the role. You must assign each user to the role individually. To create a user group 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and click User Groups. 3 On the toolbar, click + (the plus symbol). 4 In the first panel of the Create a new User Group wizard, click Next. 5 In the General panel, type a name and (optional) description for the user group, and click Next. 6 In the Members panel, click Add. In the Find Users dialog box, the Available Users list shows all users for the domain, up to the number of users that the Maximum search count text box indicates. 7 Select one or more users from the Available Users list, and click Add. The users appear in the Selected users list. 8 If you want to review information about a specific user, click the user name, and click Properties. You can view or change the user's properties, and click OK. 9 When you finish adding users to the group, click OK. 10 In the Members panel, click Next.

66 66 Managing user and user groups About editing user properties 11 In the User Group Summary panel, click Finish. Properties for the created user group are shown in the task status list at the bottom of the panel. A green check mark next to a task indicates that it was successfully completed. 12 Click Close. See Modifying a user group on page 73. About editing user properties Changing a user s password User properties are the attributes that can be added for a user when you create a new user or edit the user properties. User properties include general information about the user, change password facility, and the role that can be assigned to a user. User properties also include the user group to which a user can be assigned, business and contact information about the user, and contact methods and schedule for alert notifications. After you create a user, you can edit the user properties to perform the following tasks: Change a user's password. See Changing a user s password on page 66. Specify user business and contact information. See Specifying user business and contact information on page 67. Assign roles to a user. See Managing role assignments and properties on page 68. Assign user to a user group. See Managing user group assignments on page 69. Specify contact methods and schedule for alert notifications. See Specifying notification information on page 70. Passwords can be changed in the following ways: Users can change their own passwords by using the Change Password option on the Tools menu in the Information Manager console. Administrators can change a user s password by editing the user s properties. To change a user s password 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and click Users.

67 Managing user and user groups About editing user properties 67 3 In the right pane, right-click the user whose password you want to change, and select Properties. 4 In the User Properties dialog box, on the Password tab, in the Password text box, type a new password. The password that you choose must comply with the policy settings that the administrator chooses. 5 In the Confirm password text box, type the password again to confirm it. 6 Click OK. See About editing user properties on page 66. Specifying user business and contact information In the User Properties dialog box, the Business tab and the Contact Information tab let you supply detailed information about the user. You can specify this information when you create a user or by editing an existing user s properties. See About editing user properties on page 66. To specify user business and contact information 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and click Users. 3 In the right pane, right-click the user whose information you want to change, and select Properties. 4 In the User Properties dialog box, on the Business tab, type the business information for the user. 5 To identify the user s manager, click the browse button (...) next to the Manager text box to display the Find Users dialog box. The manager must exist as a user in the LDAP directory. 6 In the Find Users dialog box, select the user who is the manager, and click OK. The Available users list shows all users for the domain, up to the number of users that the Maximum search count text box indicates. 7 To identify the user s administrative assistant, click the browse button (...) next to the Administrative assistant text box. In the Find Users dialog box, select the administrative assistant. The administrative assistant must exist as a user in the LDAP directory.

68 68 Managing user and user groups About editing user properties 8 On the Contact Information tab, type the contact information for the user. 9 Click OK. Managing role assignments and properties The roles that a user is assigned define the user s permissions in the console. Roles are product-specific and are created as one or both of the following: Roles that allow the management of policies and configurations for a product. Users who are members of these roles can change the security configurations of an integrated product and distribute them to specific computers and organizational units. Roles that allow the viewing of the events that a product generates. Users who are members of these roles can view alerts and events for a product, and create alerts and customized reports. Note: You must be a member of the Domain Administrator role to make a user a member of a role. Also, the role must exist in the LDAP directory before you can add a user to the role. See Creating a role on page 40. To manage role assignments and properties 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and click Users. 3 In the right pane, right-click the user whose information you want to change, and select Properties. 4 In the User Properties dialog box, on the Roles tab, click Add. 5 In the Find Roles dialog box, from the Look in drop-down list, select the domain in which to find the role. Users can have access to roles in multiple domains. 6 In the Available roles list, select one or more roles, and click Add. The Find Roles dialog box displays a list of roles only if you are a member of the Domain Administrator role. 7 Click OK.

69 Managing user and user groups About editing user properties 69 8 To remove a user from a role, click the role name and click Remove. This action does not remove the role from the LDAP directory. 9 To view or edit the properties of a role, click the role name and click Properties. 10 (Optional) Use the Editing Role Properties dialog box to make changes to the role. See Editing role properties on page Click OK until you return to the System view. Managing user group assignments You can modify the composition of a user group by adding users to the group and removing users from the group. You can also view and modify user group properties. You can manage user group assignments in the following ways: Manage one user's assignment by adding to or removing from one or more user groups. Manage a single user group by adding or removing multiple users at one time. See About editing user properties on page 66. To manage a single user's user group assignments 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and click Users. 3 In the right pane, right-click the user whose user group assignment you want to manage, and select Properties. 4 In the User Properties dialog box, on the User Groups tab, click Add. 5 In the Find User Groups dialog box, from the Look in drop-down list, select the domain in which to find the user group. 6 In the Available user groups list, select one or more user groups, and click Add. The user groups that you selected appear in the Selected user groups list. 7 Click OK. 8 To remove a user from a user group, click the user group name and click Remove. This action does not remove the user group from the LDAP directory.

70 70 Managing user and user groups About editing user properties 9 To view or edit the properties of a user group, click the user group name and click Properties. 10 (Optional) Use the User Group Properties dialog box to make changes to the user group. For example, you can add members to the group and remove users from the group. 11 Click OK until you return to the System view. To manage multiple users' user group assignments 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and click User Groups. 3 In the right pane, right-click the user group whose membership you want to manage, and select Properties. 4 In the User Group Properties dialog box, on the Members tab, click Add. 5 In the Find Users dialog box, from the Look in drop-down list, select the domain in which to find the users. 6 In the Available users list, select one or more users, and click Add. The users that you selected appear in the Selected users list. 7 Click OK. 8 To remove a user from a user group, click the user name and click Remove. This action does not remove the user from the LDAP directory. 9 To view or edit the user's properties, click the user name and click Properties. 10 (Optional) Use the User Properties dialog box to make changes to the user. 11 Click OK until you return to the System view. Specifying notification information When you create custom correlation rules, you can identify users to notify when particular incidents or alerts occur. See Creating custom correlation rules on page 136. For each user, you can specify the addresses and pager numbers that are used to send these notifications. You can also specify when the user is notified. For example, you can specify one address to be used Monday through Friday from 8:00 A.M. to 5:00 P.M., and a pager to be used during off-hours. You can specify the following: addresses

71 Managing user and user groups About editing user properties 71 Pager numbers The day and the time ranges when the contact method can be used to send user notifications of alerts. Note: The number of addresses and pager numbers cannot exceed five for a single rule. To specify a user s address 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and click Users. 3 In the right pane, right-click the user whose address you want to change, and select Properties. 4 In the User Properties dialog box, on the Notifications tab, in the drop-down list, click . 5 Click Add. 6 In the dialog box, in the address text box, type an address. 7 If the user receives on a device with a small screen, such as a handheld device, check Send shortened message. This option sends an abbreviated message that is easier to read. 8 Click OK. 9 (Optional) Specify notification times. 10 Do any of the following: To add additional addresses, repeat steps 5 through 9. To edit an existing address, click it and click Properties. To remove an existing address, click it and click Delete. 11 When you finish, click OK. To specify a user s pager number 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and click Users. 3 In the right pane, right-click the user whose pager number you want to change, and select Properties.

72 72 Managing user and user groups About modifying user permissions 4 In the User Properties dialog box, on the Notifications tab, in the drop-down list, click Pager. 5 Click Add. 6 In the Pager dialog box, in the Number text box, type a pager number. 7 In the Notification service drop-down list, select the notification service to use. If you do not see the service that you want to select, you can add it using the Paging Services node. This node is located in the left pane of the System view. 8 Click OK. 9 (Optional) Specify notification times. 10 Do any of the following: To add more pager numbers, repeat steps 5 through 8. To edit an existing pager number, click it and click Properties. To remove an existing pager number, click it and click Delete. 11 Click OK. To specify notification times 1 In the User Properties dialog box, on the Notifications tab, click an address or pager number. 2 Using the Day controls, check the days when the contact method can be used to contact the user. 3 Using the From and To controls, specify the range of time when the contact method can be used. 4 Repeat these steps to establish notification times for other addresses and pager numbers. 5 When you finish, click OK. About modifying user permissions When you create a role, permissions are assigned for each user with regard to that role. These permissions control whether role members who log on to the console can view, modify, or delete the user. You can modify these permissions in the following ways: By displaying and editing the roles that contain the permissions.

73 Managing user and user groups Modifying a user group 73 See Modifying access permissions in roles on page 49. By displaying the Permissions dialog box for the User container object or an individual user. See Modifying permissions from the Permissions dialog box on page 58. Note: To modify permissions, you must be logged on as a member of the Domain Administrator role. Modifying a user group You can modify a user group by adding and removing members, and by changing the user group name and description. You can also modify individual group members' properties. To modify a user group 1 In the Information Manager console, click System. 2 On Administration tab, in the left pane, navigate to the relevant domain, and then click User Groups. 3 In the right pane, right-click the user group to modify, and click Properties. 4 On the General tab, add or change the user group's name and description. 5 On the Members tab, you can do the following: Add members Click Add. In the FindUsers dialog box, select one or more users from the Available Users list, and click Add. When you finish adding members, click OK. Remove members Select the member name, and click Remove. Modify a member's properties Select the member name, and click Properties. In the User Properties dialog box, use the tabs to modify the properties of individual user group members. When you finish modifying properties, click OK. 6 Click OK. See Creating a user group on page 65.

74 74 Managing user and user groups Deleting a user or a user group Deleting a user or a user group You can delete users who are no longer participants in your security network. You can also delete the user groups that are no longer needed. See Creating a new user on page 63. See Creating a user group on page 65. To delete a user or a user group 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and click Users or User Groups. 3 In the right pane, right-click the user or the user group to delete, and click Delete. 4 In the confirmation dialog box, click Yes. Customizing the password policy The Information Manager includes the ability to enforce strong password requirements for all users. As an administrator, you can customize the password policy for Information Manager to match the password standards that apply to your environment. You must provide the LDAP cn=root password to change the password settings. When the password policy changes, users whose existing passwords are non-compliant with the new policy are prompted to change their password at the next logon. Note: When you enable the EAL4 password policy and a user locks their account the same day that they change it, you cannot reset the password for 24 hours. This behavior is a result of the value that is defined for the setting Minimumtime between password changes (seconds). This setting is set at 24 hours in the EAL4 password policy. This behavior is expected due to the strict EAL4 password policy definition. If you do not want to enable the EAL4 policy, you can choose the Custom password policy option, change the Minimum time between password changes (seconds) setting to a lower value, and save the configuration. You can configure the password policy by using any of the following methods:

75 Managing user and user groups Customizing the password policy 75 Default EAL4 Custom The default settings that Information Manager uses. The settings that comply with Evaluation Assurance Level 4 (EAL4) standards. User-defined settings. Note: If you choose this column but do not change any settings, clicking Save reverts to the policy that was previously enabled. To change the Information Manager password policy 1 Log on to the Web configuration interface using administrator credentials, and click Settings > Password. In the tree pane, click Password Policy. 2 In the LDAP cn=root Password field, type the password, and click Enter Admin Mode. 3 In the User Password Settings and Administrator Password Settings tables, choose the type of password management you want to use. If you choose Custom, configure each option, and check Password policy enabled:. 4 Click Save. 5 Click Leave Admin Mode. See About users and passwords on page 61.

76 76 Managing user and user groups Customizing the password policy

77 Chapter 5 Managing organizational units and computers This chapter includes the following topics: About organizational units About managing organizational units About managing computers within organizational units About organizational units Organizational units are a useful way to structure your security environment in Symantec Security Information Manager. Before you create organizational units, it is important that you understand your security network and create a security plan. See About managing organizational units on page 77. Organizational units let you group the computers and servers that you manage. You can then add configurations for the Information Manager components that may be installed on those computers. These capabilities enable the distribution of the configurations to all computers and servers in the organizational unit. About managing organizational units On the Administration tab of the System view, select Organizational Units to perform the following tasks: Create a new organizational unit. See Creating a new organizational unit on page 78.

78 78 Managing organizational units and computers About managing organizational units Edit organizational properties. See Editing organizational unit properties on page 80. Delete an organizational unit. See Deleting an organizational unit on page 80. Creating a new organizational unit Organizational units are logical groupings. You can create them to organize the computers that are in the same physical location or belong to structural groups within your corporation: for example, divisions or task groups. However, it is not required that an organizational unit reflect these relationships. See About organizational units on page 77. You can create all the organizational units that you require at a single level, or you can create a hierarchy of nested organizational units. The combined maximum length of the distinguished name of an organizational unit must be no longer than 170 bytes. Keep in mind that some characters, such as accented characters or Japanese characters, take more space to store. The distinguished name of an organizational unit is a concatenation of the names that precede it in the hierarchy. Therefore, nesting organizational units with long names can exceed this limit. A screen message informs you if you exceed the limit. To create a new organizational unit 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and click Organizational Units. 3 Take one of the following actions: To create a new organizational unit at the top level of the tree, click + (the plus icon) on the toolbar. Go to step 5. To create a new organizational unit within an existing organizational unit, expand the organizational unit tree and select the level that you want. Then click + (the plus icon) on the toolbar. Go to step 4. 4 In the Computer or Organizational Unit dialog box, click Organizational Unit, and click OK. 5 In the first panel of the Create a new Organizational Unit wizard, click Next. 6 In the General panel, do the following: In the Organizational Unit Name text box, type a name for the organizational unit.

79 Managing organizational units and computers About managing organizational units 79 (Optional) In the Description text box, type a description of the organizational unit. 7 Click Next. 8 In the Organizational Unit Summary panel, review the information that you have specified, and click Finish. 9 Click Close. About determining the length of the organizational unit name Information Manager imposes limits on the length of the name of an organizational unit. It also imposes limits on the total length of the distinguished name that is stored in the LDAP directory. These limits become important when you nest organizational units. See About organizational units on page 77. The distinguished name for a nested organizational unit includes the following: The name you give the organizational unit when you create it The names of each organizational unit that precedes it in the hierarchy The name of the top node in the organizational unit tree The name of the domain within which you create the organizational unit hierarchy Additional bytes of overhead You can view the distinguished name of an organizational unit by looking at the organizational unit s properties. The maximum length of the name you assign in the Create a new Organizational Unit wizard is 64 UTF-8 bytes. For the Roman character set, this means that the name cannot exceed 64 characters. Some characters take more space to store. For example, accented characters take two bytes to store, and Japanese characters take three bytes or four bytes to store. When these characters are used, fewer characters are allowed in the name. Information Manager adds other information for internal use to the distinguished name. Therefore, the maximum recommended length of the distinguished name of an organizational unit in the security directory is 170 bytes. If a distinguished name is longer than 256 characters, performance issues occur. Table 5-1 describes how to calculate the UTF-8 byte length of the distinguished name of the organizational unit.

80 80 Managing organizational units and computers About managing organizational units Table 5-1 Name string Determining the organizational unit name length Formula and example Domain name length sum(4+domain component name length) + 17 bytes Example: usa.ses 4 + length(usa) + 4 +length(ses) + 17 bytes overhead or = 31 bytes Organizational unit (OU) name length sum(4 + OU name length) + domain name length + 13 bytes For example: Paris OU under the Sales OU in the usa.ses domain 4 + length(paris) + domain name length + 13-bytes overhead or = 53 bytes Editing organizational unit properties You can modify an existing organizational unit's description. You cannot change the name or the distinguished name of the organizational unit. See About organizational units on page 77. To edit organizational unit properties 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and expand the Organizational Units navigation tree. 3 Right-click the name of the organizational unit to edit, and click Properties. 4 In the Organizational Unit Properties dialog box, change the description. 5 When you finish, click OK. Deleting an organizational unit Before you can delete an organizational unit, you must move or delete all computers that belong to the organizational unit. See Moving a computer to a different organizational unit on page 93. See Deleting a computer from an organizational unit on page 94.

81 Managing organizational units and computers About managing computers within organizational units 81 Note: When you delete an organizational unit, all of the organizational units that are below it in the navigational structure are also deleted. To delete an organizational unit 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and expand the Organizational Units navigation tree. 3 Right-click the name of the organizational unit to delete, and click Delete. 4 To confirm to delete the organizational unit and its subgroups, click Yes. About managing computers within organizational units Organizational units contain computer objects representing the computers that run your security products. Note: The term computer covers a variety of equipment, from traditional desktop computers to servers and handheld devices. In the context of the Information Manager console, a computer is any device that you manage as part of your enterprise security environment. Computers are placed in organizational units in the following ways: When an agent is installed. When you install Symantec Event Agent on a computer, it is represented as a computer within an organizational unit. Symantec Event Agent is added to the default organizational unit. You can move the agent to a different organizational unit later. When you create the computer using the Create a new Computer wizard. You can use this method to create computers other than the agent computers. Note: Do not create a computer using the wizard if you plan to install the Symantec Event Agent on the computer at a later time. If you do, a duplicate instance of the computer is added to the LDAP directory.

82 82 Managing organizational units and computers About managing computers within organizational units A computer can belong to only one organizational unit at a time. However, based on the requirements of your network, you can easily move computers from one organizational unit to another. When you select a computer in the right pane, you can perform the following tasks: Create computers within organizational units. Creating computers within organizational units Edit computer properties. About editing computer properties Move a computer to a different organizational unit. Moving a computer to a different organizational unit Modify computer permissions. About modifying computer permissions Delete a computer from an organizational unit. Deleting a computer from an organizational unit Creating computers within organizational units Computers are defined in the LDAP directory as part of the organizational units in which you create them. If you delete a computer from an organizational unit, it is permanently removed from the LDAP directory. See About managing computers within organizational units on page 81. To create a computer within an organizational unit 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and expand the Organizational Units navigation tree. 3 Right-click the name of the organization unit, and click New > Computer. 4 In the first panel of the Create a new Computer wizard, click Next. 5 In the General panel, do the following, and click Next: In the Computer name text box, type the computer name. (Optional) In the Description text box, type a description. 6 In the Information panel, do one of the following: Type information in some or all of the optional text boxes, and click Next. Supply the information later by editing the computer s properties.

83 Managing organizational units and computers About managing computers within organizational units 83 7 In the Identification panel, do one of the following: Provide the host name, IP addresses, and MAC addresses of the computer, and click Next. Provide the identification information later by editing the computer s properties. 8 In the Configurations panel, do one of the following: To directly associate configurations with the computer, click Add. When you are finished, click Next. Add configurations later by editing the computer s properties. 9 In the Computer summary panel, review the information that you have specified, and click Finish. 10 Click Close. About editing computer properties The computer properties that you can view and change depend on whether Symantec Event Agent is installed on the computer. If the computer has Symantec Event Agent, you can associate configurations with the computer and view the services running on the computer. However, you cannot change the identification information for the computer. See Editing the agent computer on page 83. See Viewing the services running on a computer on page 91. If the computer does not have an agent, you can edit the network identification information for the computer. However, you cannot view services running on the computer. See Editing a computer that does not have an agent on page 84. See Providing identification information for a computer on page 85. Editing the agent computer When a computer has an agent installed, most of the identification information about the computer is captured during the installation. You can learn about the computer by viewing the information that the agent provides. This information includes the state of the services running on the computer and the computer s heartbeat status. You can also specify configurations to be associated with the computer. If the computer is an Information Manager server, you can add access to other domains.

84 84 Managing organizational units and computers About managing computers within organizational units To edit the agent computer 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and expand the Organizational Units navigation tree. 3 Click the name of the organizational unit that contains the computer to be edited. 4 In the right pane, right-click the name of the computer, and click Properties. 5 In the Computer Properties dialog box, on the General tab, you can type a new description. 6 On the Information tab, you can modify the Primary Owner and Owner contact information text boxes. The remaining information is provided during the agent installation. 7 On the Configurations tab, do any of the following: To directly associate configurations with the computer, click Add. See Associating configurations directly with a computer on page 86. To remove a configuration, select it, and click Remove. To view a configuration s properties, select it, and click Properties. See About agent configurations on page You can view information on any of the following tabs: On the Identification tab, view the host name, IP addresses, and MAC addresses of the computer. On the Services tab, view information about the services running on the computer. See Viewing the services running on a computer on page Click OK. Editing a computer that does not have an agent When you create a computer using the Create a New Computer wizard, you can modify most of the computer s properties. Services are reported only if an agent is installed on the computer.

85 Managing organizational units and computers About managing computers within organizational units 85 To edit a computer that does not have an agent 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and expand the Organizational Units navigation tree. 3 Click the name of the organizational unit that contains the computer to be edited. 4 In the right pane, right-click the name of the computer, and click Properties. 5 In the Computer Properties dialog box, on the General tab, you can type a new description. 6 On the Information tab, modify the text boxes as you want. To enable the Other OS Type text box, select OTHER from the operating system type drop-down list. 7 On the Identification tab, change the host name and add or remove IP addresses and MAC addresses, as needed. See Providing identification information for a computer on page On the Configurations tab, do any of the following: To directly associate configurations with the computer, click Add. See Associating configurations directly with a computer on page 86. To remove a configuration, select it, and click Remove. To view a configuration s properties, select it, and click Properties. 9 On the Services tab, view information about the services running on the computer. See Viewing the services running on a computer on page Click OK. Providing identification information for a computer After you create a computer using the Create a new Computer wizard, you can provide the network identification information for the computer by editing its properties. When you create a computer by installing a collector, the identification information is supplied automatically by the installation. See About editing computer properties on page 83.

86 86 Managing organizational units and computers About managing computers within organizational units To provide identification information for a computer 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and expand the Organizational Units navigation tree. 3 Click the name of the organizational unit that contains the computer to be edited. 4 In the right pane, right-click the name of the computer, and click Properties. 5 In the Computer Properties dialog box, on the Identification tab, in the Host name text box, type an FQDN or a DNS host name. 6 To add an IP address, under IP addresses, click Add. 7 In the IP addresses dialog box, type the IP address of the computer, and click OK. 8 If the computer has multiple network interface cards, repeat steps 6 and 7 for each IP address. 9 To add a MAC address, under MAC addresses, click Add. 10 In the MAC addresses dialog box, type the MAC address of the computer, and click OK. The MAC address must consist of six hexadecimal pairs. 11 If the computer has multiple network interface cards, repeat steps 9 and 10 for each MAC address. 12 Click OK. Associating configurations directly with a computer Configurations control the behavior of Information Manager components. To distribute configurations to a computer, you can associate a configuration with the computer. You can then distribute the configuration either immediately or at a later date, depending on your needs. See About editing computer properties on page 83. Associating configurations directly with a computer defines each of the available configurations that can be associated directly with a computer. Note: Only those configurations that are shipped with the default installation of Information Manager are listed here. If additional collectors or products are added to your Information Manager, the configurations list may be different.

87 Managing organizational units and computers About managing computers within organizational units 87 Configuration Symantec Event Agent and Manager Manager Configurations Symantec Event Agent and Manager Manager Component Configurations Symantec Event Agent and Manager Manager Connection Configurations Description Contains the common Information Manager server settings, which may affect one or more components on an Information Manager server. For example, configuration settings define which directory service and database the server should use. Contains the settings for services within the Information Manager server, such as the event logging subsystem or the configuration service. Lets you control how failover is performed from the Information Manager server to directory service and Information Manager server to database. Symantec Event Agent and Manager Agent Connection Configurations Symantec Event Agent and Manager Agent Configurations Sets the agent to Information Manager server failover. Failover is the ability of Information Manager components to automatically switch to designated secondary resources if the primary resource fails or terminates abnormally. Lets the agent communicate with the corresponding Information Manager server. They include which primary and secondary server to connect to and how to get configuration information and report inventory. In addition, they include how these computers should receive LiveUpdate information. Symantec Critical System Protection Event Collector LiveUpdate 1.0 LiveUpdate Configures Symantec Critical System Protection Event Collector to collect DB sensor data from various platforms. Configures LiveUpdate to obtain software updates for the various software components of Information Manager, such as event collectors, relays, security content, rules, and filters.

88 88 Managing organizational units and computers About managing computers within organizational units Configuration LiveUpdate 1.0 Java LiveUpdate ISS SiteProtector Event Collector Check Point Firewall 1 Event Collector Cisco ASA Event Collector Generic Syslog Event Collector Juniper NSM Event Collector Juniper Netscreen Firewall Event Collector Snare for Windows Event Collector Snort Syslog Event Collector Symantec Endpoint Protection 11.0 Event Collector Symantec Endpoint Protection State 11.0 Event Collector Description Configures Java LiveUpdate to obtain software updates for the various software components of Information Manager, such as event collectors, relays, security content, rules, and filters. Configures the Internet Security Systems RealSecure SiteProtector Event Collector to collect DB sensor data from various platforms. Configures Check Point FireWall-1 Event Collector to collect OpsecLea sensor data from various platforms. Configures Cisco ASA Event Collector to collect Syslog sensor data from various platforms. Configures Generic Syslog Event Collector to collect Syslog sensor from various platforms. Configures Juniper Networks NetScreen Security Manager Event Collector to collect Syslog sensor data from various platforms. Configures Juniper NetScreen Event Collector to collect Syslog sensor data from various platforms. Configures Snare for Windows Event Collector to collect Syslog sensor data from various platforms. Configures Snort Event Collector to collect SyslogFile sensor data from various platforms. Configures Symantec Endpoint Protection 11.0 Event Collector to collect DB sensor data from various platforms. Configures Symantec Endpoint Protection State 11.0 Event Collector to collect DB sensor data from various platforms.

89 Managing organizational units and computers About managing computers within organizational units 89 Configuration Symantec Security Information Manager Local Event Collector Syslog Director Universal Logfile Event Collector UNIX OS Event Collector Description Configures the Information Manager Event Collector to collect SyslogFile sensor data. The Local Event Collector tracks the events that the Linux operating system that runs Information Manager generates. Examples include ssh commands and wrong password entries. Configures Syslog Director. Configures the Universal Logfile Event Collector to collect events from the products that log to text files. Configures UNIX OS Event Collector to collect syslog data from various platforms. In addition, the UNIX Event Collector collects data from ISC BIND9, Linux iptables, and the Linux Audit daemon AUDITD. Universal Syslog Event Collector Universal Event Collector for Microsoft Windows Vista Universal Event Collector for Microsoft Windows Qualys Guard Event Collector Configures the Universal Syslog Event Collector to collect events from the products that log events by using the Syslog protocol. Configures Universal Event Collector for Microsoft Windows Vista to collect events from Microsoft Windows Vista, Windows Server 2008, and Windows 7 event logs. Configures Universal Event Collector for Microsoft Windows to collect events from Microsoft Windows event logs. Configures QualysGuard Event Collector to collect QualysGuard sensor data from various platforms. For more details about the Collectors you must refer to the specific Collector guides. To associate configurations directly with the computer 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and expand the Organizational Units navigation tree.

90 90 Managing organizational units and computers About managing computers within organizational units 3 Click the name of the organizational unit that contains the computer that you want to edit. 4 In the right pane, right-click the name of the computer, and click Properties. 5 In the Computer Properties dialog box, on the Configurations tab, click Add. 6 In the Find Configurations dialog box, in the Look-in drop-down list, select the product whose configurations you want to associate with the computer. The configurations are displayed in the Available configurations list. See Associating configurations directly with a computer on page In the Available configurations list, select a configuration, and click Add. The selected configuration is listed in the Selected configuration list. If the computer already contains a configuration, and you now select a different configuration, the new configuration replaces the old one. 8 To select a configuration for a different product, repeat steps 6 and 7. 9 When you finish adding configurations, click OK. 10 In the Computer Properties dialog box, do one of the following: To remove a configuration, select it, and click Remove. To view a configuration s properties, select it, and click Properties. 11 Click OK. Making a computer a member of a configuration group In addition to belonging to an organizational unit, a computer can be a member of a configuration group. Configuration groups are used to distribute special configurations to their member computers. A computer can belong only to one configuration group. To make a computer a member of a configuration group 1 In the Information Manager console, on the System tab, in the left pane, expand the Organizational Units navigational tree until you can select the organizational unit containing the computer that you want to edit. 2 In the right pane, select the computer. 3 On the Selection menu, click Properties. 4 In the Computer Properties dialog box, on the Configuration Groups tab, click Add.

91 Managing organizational units and computers About managing computers within organizational units 91 5 In the Available Configuration Groups list, select a configuration group. If the computer is already a member of a configuration group, the configuration group you select here replaces the original configuration group. 6 Click Add. 7 Click OK. 8 On the Configuration Groups tab, do any of the following, as needed: To remove a computer from configuration group membership, select the configuration group, and click Remove. To view a configuration group s properties, select it, and click Properties. 9 Click OK. Viewing the services running on a computer You can view information about the services running on a computer: for example, which configurations are in use and whether the configurations are up-to-date. See About editing computer properties on page 83. To view the services running on a computer 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and expand the Organizational Units navigation tree. 3 In the left pane, select the organizational unit that contains the computer whose services you want to view. 4 In the right pane, right-click the computer name, and click Properties. 5 In the Computer Properties dialog box, on the Services tab, review the In Sync column to determine whether the correct configurations are in use. If the value for a specific service is Yes, the current configuration and the expected configuration are synchronized. That is, they are identical. If the value for a specific service is No, the configurations are not synchronized. Double-click the row to view the information on the Configuration tab of the Service Properties dialog box. You may need to distribute the latest configurations to this computer. 6 Take any of the following actions:

92 92 Managing organizational units and computers About managing computers within organizational units In the Computer Properties dialog box, to notify the computer that it should download new configurations, click Distribute. Then click Yes to confirm your intention to distribute configurations. To refresh the Computer Properties dialog box display, click Refresh. Click Details to open the Service Properties dialog box and view the details of services. 7 When you finish, click OK. Distributing configurations to computers in an organizational unit Information Manager includes a Distribute option, which sends a message to all the computers in an organizational unit to check for new configurations. When a computer receives this message, it contacts Information Manager to request a download of the configurations. See About managing computers within organizational units on page 81. Using the Distribute feature is optional. When you change a product configuration or move a computer to a different organizational unit, the change is distributed when you click Save. You can do the following to distribute configurations to computers in an organizational unit: You can distribute the configurations that are associated with an organizational unit to all computers that belong to the organizational unit. You can select specific computers to receive the latest configurations. Note: The timing of configuration distribution varies depending on the amount of Information Manager traffic. To distribute configurations to all computers in an organizational unit 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and then expand the Organizational Units navigation tree. 3 Right-click the name of the organizational unit to which you want to distribute configurations, and then click Distribute. 4 In the confirmation message box, click Yes.

93 Managing organizational units and computers About managing computers within organizational units 93 To distribute configurations to selected computers in an organizational unit 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and then expand the Organizational Units navigation tree. 3 In the left pane, select the organizational unit that contains the computer or computers to which you want to distribute configurations. 4 In the right pane, select only those computers that you want to notify. 5 Right-click on the selected computers, and then click Distribute. 6 To confirm your intention to distribute configurations, click Yes. Moving a computer to a different organizational unit Although a computer can only belong to one organizational unit, you can move computers from one organizational unit to another. See About organizational units on page 77. Warning: Before you move a computer, make sure that the security products you manage let you move computers. To move a computer to a different organizational unit 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and then expand the Organizational Units navigation tree. 3 In the left pane, select the organizational unit that contains the computer or computers that you want to move. 4 In the right pane, right-click a computer, and then click Move. You may select multiple computers if you want to move all of them to the same organizational unit. 5 To confirm that you want to move the computers, click Yes.

94 94 Managing organizational units and computers About managing computers within organizational units 6 In the Find Organizational Units dialog box, select the organizational unit to which you want to move the computers, and then click OK. 7 To verify that the move was successful, in the left pane, select the organizational unit to which you moved the computers. Look at the right pane to see if the computers that you moved are now in the list. If you move a computer that is an Information Manager server, you may have to log on again before you see the computer in the organizational unit. Agents that connect to the Information Manager server may need to be restarted. About modifying computer permissions When you create a role, permissions are assigned for each computer with regard to that role. These permissions control whether role members who log on to the Information Manager console can view, modify, or move the computer. To modify the permissions for a computer, you must display the Permissions dialog box for the computer. You cannot modify permissions for computers using the Role Properties dialog box. See Modifying permissions from the Permissions dialog box on page 58. Note: To modify permissions, you must be logged on as a member of the Domain Administrator role. Deleting a computer from an organizational unit If you want to delete an organizational unit, you must first remove any computers within the organizational unit by moving them or deleting them. You may also want to delete a computer that you no longer want to have under Information Manager management. If the computer was created by installing an agent as part of a security product installation, you should uninstall the collectors and agent from the computer before you delete the computer from the Organizational Units container in the Information Manager console. See Creating computers within organizational units on page 82. Deleting a computer from an organizational unit removes it from the LDAP directory.

95 Managing organizational units and computers About managing computers within organizational units 95 Warning: If you delete a computer that is an Information Manager server, you must perform extra steps to add it to an organizational unit again. To restore a deleted Information Manager server to the LDAP directory, you must do one of the following: re-register the deleted server with the LDAP directory in which it was previously registered, or reinstall the Information Manager on the server. About the Visualizer To delete a computer from an organizational unit 1 In the Information Manager console, click System. 2 On the Administration tab, in the left pane, navigate to the relevant domain, and then expand the Organizational Units navigation tree. 3 In the left pane, select the organizational unit that contains the computer that you want to delete. 4 In the right pane, right-click the computer name, and then click Delete. 5 To confirm your intention to delete the computer from the organizational unit, click Yes. The Visualizer provides a convenient way to view your Symantec Security Information Manager environment, including the computers that are assigned to organizational units. You can use it to monitor events per second (EPS) rates and CPU usage on your network devices. You can also view and modify properties of elements such as the Information Manager server and agents. See About using the Visualizer on page 95. See Viewing and modifying element properties on page 98. About using the Visualizer The Visualizer provides a graphical view of your Information Manager environment. When you click the Visualizer tab on the System view, you see a set of icons. The icons represent such elements as correlation servers, collection servers, agents, and directories. The Icons tab in the Legend pane illustrates and defines each type of icon that can appear in the diagram. See About the Visualizer on page 95. The Overview pane that is located on the top left corner provides a visual summary of the layout in which the various components are arranged in your Information Manager environment. You can click a specific item in the overview and easily reach the selected item in the graphical view.

96 96 Managing organizational units and computers About managing computers within organizational units Colored lines join elements to indicate the nature of their interactions. For example, a green line appears between an Information Manager server and its event archive. A blue line indicates that event forwarding is configured between a collection server and the correlation server. The arrow shows the direction in which the event data flows. To see an explanation of each color, click the Edges tab in the Legend pane. You can place the icons where you want them by dragging them with the mouse. The associated text moves with the icon. You can also move the text to a different position relative to its icon. Click and hold the mouse over the text, and then move the mouse. Empty text boxes appear on each side of the icon. Drag the text into one of the boxes and release the mouse. The toolbar includes tools to help you examine the graphic. The colored dots that appear next to an element indicate the activity level of these elements. Some dots reflect the volume of EPS, and other dots reflect the percentage of appliance CPU in use. The meaning of each color is as follows: EPS Green = less than or equal to 2.5 K Yellow = 2.5 K to 5 K Red = greater than 5 K CPU usage Green = less than 60% Yellow = 60% to 80% Red = greater than 80% Note: The EPS display on the Visualizer tab depends on the value of the Agent Queue Statistics Report Interval setting under System > Product Configuration > SSIM Agent and Manager > Agent Configurations > Logging. By default, this value is set to 300 seconds and the EPS is updated after that interval only. You can configure it to a lower interval. However, setting a lower value may result in a lower performance by the agent. You must update (push) the configuration to the agent for the change to take effect. Table 5-2 describes the tools in the toolbar.

97 Managing organizational units and computers About managing computers within organizational units 97 Table 5-2 Tool Layout menu Visualizer tools Purpose This option lets you view your network topology using the following layouts: Organic Circular Hierarchic Orthogonal Tree Refresh Zoom in Zoom out Zoom selected Fit to window Save as Export Image Print This option lets you update the display after you make configuration changes. For example, after you add a collector, click Refresh to re-draw the diagram and show a new icon for the added collector. This option lets you expand the diagram view. This option lets you minimize the diagram view. This option lets you enlarge the view of a selected portion in the diagram. Select a portion of the diagram by clicking the mouse and dragging a box around the required area. Then click the ZoomSelected icon to enlarge the area that you selected. This option returns the diagram to its original size, to fit the entire diagram in the right pane of the System view. This option lets you save the information in the diagram as an XML file. Symantec Technical Support may request this file to assist in troubleshooting. This option lets you export the Visualizer image as a.gif or.jpg file. You can also adjust the image width and height, and define the clip area as a view or a graph. This option lets you print the diagram. On the Print Options dialog box, you can select the height (Poster Rows) and width (Poster Columns) if you print a very large diagram. The default setting (one poster row and one poster column) prints the entire diagram on a single page.

98 98 Managing organizational units and computers About managing computers within organizational units Table 5-2 Tool Table view Visualizer tools (continued) Purpose This option displays a table with one row for each element that is involved in processing events. The table dynamically displays such information as EPS and the total number of events that the element has processed since it was last started. The details that are displayed in the table view can be saved into CSV format. A green check mark means that the element is running; a red X means that the element is not responding. Use Magnifier This option lets you magnify any selected portion of the diagram. Viewing and modifying element properties You can view the properties of many of the elements in the Visualizer diagram. You can also modify some of these properties. See About using the Visualizer on page 95. The same properties are also accessible through other tabs on the System view. You use these tabs to add and delete elements, such as collectors. After you add an element, you distribute it; the element appears in the Visualizer. Table 5-3 explains how to access each of the element categories on other System view tabs. Table 5-3 Category Computers Accessing element properties on System view tabs How to access This category includes appliances, agents, and collectors. Directories Select Administration > Organizational Units. Select an organizational unit. In the list in the right pane, double-click the name of a computer. A dialog box displays the computer's properties. Select Administration > Directories. In the list in the right pane, double-click the name of a directory. A dialog box displays the directory's properties. Products This category includes products such as collectors and firewalls. Select Product Configurations. In the left pane, click the name of a product. The right pane displays the product's properties.

99 Managing organizational units and computers About managing computers within organizational units 99 To view and modify element properties 1 On the System view of the Information Manager console, click the Visualizer tab. 2 Right-click on an icon in the diagram, and then click Properties. A dialog box displays a set of tabs that let you access the element's properties. The displayed properties depend on the type of element that you selected. For example, a collection appliance has different properties than an agent. 3 View and modify any of the available properties in the dialog box, using the tabs to navigate through the properties. 4 When you finish viewing and modifying properties, click OK.

100 100 Managing organizational units and computers About managing computers within organizational units

101 Chapter 6 Configuring a service provider This chapter includes the following topics: About using Information Manager in a service provider context About responding to a client incident About setting up a Service Provider environment Disconnecting a client from a Service Provider Master About using Information Manager in a service provider context Information Manager can be used to offer services to manage security incidents to multiple business clients and physical locations. In a service provider context, Information Manager can be used to gather, correlate, monitor, and initiate resolution of security incidents in real time. An instance of Information Manager that is configured as a service provider can also create and work with tickets. It can also generate and deliver custom reports. See About using Information Manager in a service provider context on page 101. Correlation can now be enabled on the Service Provider Master. This feature can be used to trigger the rules on the Service Provider Master and create incidents based on local Service Provider events. Using Information Manager in a service provider context has the following minimum requirements: For a service provider client: At least one instance of Information Manager must be configured to monitor and correlate security events, and forward the

102 102 Configuring a service provider About using Information Manager in a service provider context resulting incidents. A copy of the incidents that are created at the client correlation server is forwarded to the Service Provider Master. For a service provider: At least one instance of Information Manager must be configured as a Service Provider Master. You can add multiple correlation servers for a single domain through the client configuration user interface on the console of the Service Provider Master. The Service Provider Master receives a copy of the incident data that the client server forwards. Using the Information Manager console, a Service Provider Master provides a centralized view of all of the incidents that each client generates. If the service provider uses more than one Service Provider Master to manage clients, each master operates independently from any other Service Provider servers. Figure 6-1 displays the relationship between multiple clients that use instances of Information Manager and a service that manages incident management using the server of the Service Provider Master. Each client maintains their own event and incident management policies and topologies. The only requirement is that the client configures the primary correlation server to forward any incidents that are generated to the Service Provider Master.

103 Configuring a service provider About using Information Manager in a service provider context 103 Figure 6-1 Service Provider Master with Correlation Service enabled About the service provider environment from the client perspective When a client uses the services of an Information Manager service provider, the client environment is configured as a completely autonomous Information Manager solution. All raw event data is gathered, stored, managed, and correlated within the environment of the client. All the information about the client Information Manager's asset, ticket, incident, and users is exclusive to the client environment. See About using Information Manager in a service provider context on page 101. The key connection to the Service Provider is through a primary correlation server, which is configured to gather and forward a copy of incidents to the Service Provider Master Server. The service provider that receives the copy of client incidents then processes, analyzes, and monitors the incidents. When necessary, the service provider then initiates the appropriate remediation steps by notifying the client.

104 104 Configuring a service provider About using Information Manager in a service provider context About the service provider environment from the provider perspective Incident management on the Service Provider Master begins as soon as the following conditions are met: At the client site, incident forwarding is enabled on the primary correlation server and network connectivity with the off-site management service is established. The Information Manager server at the service provider management site is configured to receive incidents as a Service Provider Master. The Service Provider Master is also configured with a client account. This account includes the client location, the service provider analyst who is assigned to the account, and the contact information for the client. When these prerequisites are met and incident forwarding is enabled, the incidents that a client server creates can be managed at the Service Provider Master. Incidents that were created before the enabling of incident forwarding can be forwarded. To forward these incidents, use the Incident Synchronization feature in the Web configuration interface for the client. See Synchronizing the Service Provider Master with client incidents on page 110. About customizing the Incidents view in a Service Provider Master console When you configure a server to perform the duties of a Service Provider Master Server, the view in the Information Manager console is modified. The view is modified to match the features that are available in a service provider context. The primary differences in the console appear on the Incidents view. A Service Provider Server uses a configurable single incident that is a streamlined version of the Incidents view. See About using Information Manager in a service provider context on page 101. The client configuration user interface on the console of the Service Provider Master lets you add multiple correlation servers for a single domain. The Incidents view on the Service Provider Master displays the host name with a domain that corresponds to a particular incident of a client. When you view incidents in a Service Provider console, the Original ID and the Reference ID are for two distinct purposes. If you use multiple clients, the Original ID is the incident number that the client generates and then forwards to the Service Provider. The Reference ID is the incident number that the Service Provider generates. Changes to the Incidents view include the following:

105 Configuring a service provider About responding to a client incident 105 Contacts, Tickets, and Remediation tabs are now available from within the incident details. The Contacts tab is not available for clients having the same domain as Service Provider Master. Incident details are now displayed in a separate Information Manager console window, unlike the browser window that is displayed in earlier versions of Information Manager. About responding to a client incident In the Incidents view of the Information Manager console, when you click an incident that a Service Provider client generates, you can use the fields and information on the tabs available to take the appropriate action. See About using Information Manager in a service provider context on page 101. To view the incident details, you can quickly review the incident by double-clicking the incident in the summary table. Double-clicking an incident in this view opens the Client Incident viewer, which is a browser instance that communicates over a secure browser session (HTTPS). This console lets you analyze the incident without having to open an additional Information Manager console session. The Client Incident viewer provides a streamlined view of the incident details. The viewer also lets you perform tasks to address the incident immediately, such as selecting an Assignee, State, Priority, Severity, and so forth. Creating Information Manager tickets in a Service Provider Master context When you view client incidents on a Service Provider Master, you can view, create, and resolve the following types of tickets: See About using Information Manager in a service provider context on page 101. An Information Manager Service Provider ticket. When you work in an Information Manager console that is logged on to a Service Provider Master, the ticket that is displayed in the Incidents or Tickets view is exclusive to the environment of the Service Provider Master. A service provider analyst or administrator uses the information in this ticket to perform certain duties: For example, following the steps that are required to notify a client that an incident has occurred. An Information Manager client ticket. When you open the Client Incident viewer, a ticket that is displayed in that browser session is local to the client environment. A client uses the information in this ticket to perform certain duties: For example, the tasks that are necessary to address the incident within the client environment.

106 106 Configuring a service provider About responding to a client incident To create an Information Manager Service Provider ticket, you use the Information Manager console that is logged on to the Service Provider Master. The service provider analysts or administrators used the Service Provider Master ticket. The client does not see Service Provider tickets. To create an Information Manager client ticket, you use the Client Incident viewer browser session. Alternatively, you can use a separate instance of the Information Manager console that is logged directly on to the client's correlation Server. The Client Incident viewer and the Information Manager console instance that is logged on to the client server share the same client ticket information. A ticket that is created from within the Client Incident viewer is local to that client, applies only to the client's resources, and so forth. For example, this type of ticket may include the instructions that client IT personnel must act upon to reduce the spread of an outbreak. To create a ticket for the client environment 1 In the Information Manager console for the Service Provider Master, on the Incidents view, double-click the incident. 2 In the Client Incident viewer, click Create Ticket. 3 In the Ticket Details area, enter the ticket information for the client in the available fields. The Summary field is required. 4 In the Creator area, enter the contact information for the appropriate service provider contact in the available fields. 5 In the Help Desk Assignee area, assign the ticket to the appropriate client assignee. 6 (Optional) Add any necessary instructions. 7 Click Save. After the ticket is saved, you can view, add, or remove any associated tasks using the Tasks tab. You can also add a note on the Log tab. To create a ticket for the Service Provider Master environment 1 In the Information Manager console for the Service Provider Master, on the Incidents view, click the incident. 2 In the lower pane, on the Tickets tab, click Create Ticket. 3 In the Ticket Details window, use the available fields to provide the necessary ticket information. The Summary field is required. The Assignee field provides a list of Service Provider environment users. 4 When you are finished, click OK.

107 Configuring a service provider About setting up a Service Provider environment 107 Exporting incident information from the Client Incident viewer You can export incident data from the Client Incident viewer using the Export button and the save feature of the browser that you use. See About responding to a client incident on page 105. To export incident information from the Client Incident viewer 1 In the Information Manager console, on the Incidents view, double-click the incident that you want to export. 2 In the Client Incident viewer, click Export. Specify a new name or accept the default name for the CSV file. 3 Save the exported CSV file in the required location. About setting up a Service Provider environment When you configure Information Manager servers in a Service Provider context, you must configure the following: The client server that creates incidents. In distributed client environments, this server is generally the primary correlation server. The service provider server that receives the forwarded incidents. See About using Information Manager in a service provider context on page 101. Configuring an instance of Information Manager as a Service Provider client To configure an instance of Information Manager as a client of a Service Provider Master, configure the client server to forward incidents to the Service Provider Master. See About using Information Manager in a service provider context on page 101. To configure an instance of Information Manager as a Service Provider client 1 Using the Information Manager console, connect to the client instance of Information Manager. 2 On the System view, click the Server Configurations tab and expand the server to configure as the Service Provider client. 3 Click Incident Forwarding Rules, and then click the Add icon. 4 In the Incident Forwarding Rules window, type a name for the rule in the Rule name field.

108 108 Configuring a service provider About setting up a Service Provider environment 5 Enter the server host name or IP address of the Service Provider Master. 6 Click OK. 7 Ensure that Enabled is checked and then click Apply to apply the incident forwarding rule. Configuring an Information Manager server as a Service Provider Master To enable an Information Manager server to perform the duties of a Service Provider Master, you enable this feature in the System view. See About setting up a Service Provider environment on page 107. Correlation can now be enabled on the Service Provider Master. This feature can be used to trigger the rules on the Service Provider Master and create incidents based on local Service Provider events. Note: Ensure that the Event Forwarding rule is enabled if Correlation Service is enabled on the Service Provider Master. To configure a server as a Service Provider Master 1 Using the Information Manager console, connect to the instance of Information Manager that is to be the Service Provider Master. 2 On the System view, on the Server Configurations tab, expand the server that is to be configured as the Service Provider Master. 3 Click the server folder. 4 In the right tile, under Service Provider, check Service Provider Master. 5 Click Apply. 6 Close and restart the Information Manager console. To enable the correlation service on a Service Provider server 1 Using the Information Manager console, connect to the Service Provider Master and log on as an administrator. 2 On the System view, on the Server Configurations tab, click on the server folder. 3 In the Server options area, select the option for Enable Correlation. 4 Click Apply.

109 Configuring a service provider About setting up a Service Provider environment 109 Configuring service provider client management accounts To manage a service provider client, you configure a client account. The account must include the network and physical location, the assigned service provider analyst, and contact information that is associated with the client. See About setting up a Service Provider environment on page 107. You can add multiple clients that have the same domain as the Service Provider Master. You can also add multiple clients that have a different domain, and provide a single incident view for incidents from all Correlation Servers. To add a service provider Client management account 1 Using the Information Manager console, connect to the instance of Information Manager that is to be the Service Provider Master. 2 On the System view, expand the domain, and click Clients. 3 Click New (+). 4 In the Add Client wizard, in the Client Information window, describe the client using the fields provided, and then click Next. 5 In the Client Setup window, click New. 6 In the Client Account fields, do the following for each analyst to assign to this account: In the Client Username and Client Password fields, enter the appropriate client user name and password information. In the Analyst field, use the ellipses (...) to open the Find Users dialog box and choose the analyst (or analysts) to whom the account is to be assigned. If you want the assigned analyst to receive notifications for incidents, select Analyst Notification. The settings for the user determine the notifications. 7 Click Save to add the analyst to the list. 8 When you are finished, click Next. 9 In the Contact Information window, click New. 10 In the Add/Edit Contact area, enter the relevant client contact information. This contact is the client representative that is contacted when an incident requires remediation, for example. You can add multiple contacts if necessary. 11 Click Finish.

110 110 Configuring a service provider Disconnecting a client from a Service Provider Master To delete a service provider client management account 1 Using the Information Manager console, connect to the Service Provider Master. 2 On the System view, expand the domain, and click Clients. 3 Click Delete (-). 4 In the Delete Client Configurations dialog box, click Yes. Synchronizing the Service Provider Master with client incidents The correlation server for a Service Provider client can create Information Manager incidents when the client and Service Provider Master are not connected. You can synchronize the Service Provider Master when the connection is available. When you synchronize client and Service Provider Master incidents, you forward an updated set of incident data. The data is forwarded from the client's correlation server to the Service Provider Master. See About setting up a Service Provider environment on page 107. The synchronization tool is available in the Web configuration interface for the client's correlation server. To synchronize the Service Provider Master with client incidents 1 On the Correlation Server that forwards incidents to the Service Provider Master, log on to the Web configuration interface using administrator credentials. 2 On the Maintenance view, click Incident Synchronization. 3 In the details pane, click Start. Disconnecting a client from a Service Provider Master You can disconnect a client from a Service Provider Master by disabling Incident Forwarding on the client instance of Information Manager. See About setting up a Service Provider environment on page 107. To disconnect a client from a Service Provider Master 1 Using the Information Manager console, connect to the client instance of Information Manager. 2 In the System view, on the Server Configurations tab, expand the domain that you want to disconnect from the Service Provider Master.

111 Configuring a service provider Disconnecting a client from a Service Provider Master On the Incident Forwarding Rules view, select the forwarding rule that forwards incidents to the Service Provider Master, and click Delete (-). 4 Click Apply. 5 If you want to delete the client configuration, do the following: Using the Information Manager console, connect to the Service Provider Master On the System view, on the Administration tab, click Clients. Choose the client configuration that you want to remove, and click Delete. In the Delete Configurations dialog box, click Yes.

112 112 Configuring a service provider Disconnecting a client from a Service Provider Master

113 Section 3 Planning for security management Chapter 7. Managing the correlation environment Chapter 8. Defining rules strategy

114 114

115 Chapter 7 Managing the correlation environment This chapter includes the following topics: About the Correlation Manager About the Correlation Manager knowledge base About the default rules set About the Correlation Manager The Correlation Manager component of Information Manager performs automated real-time event correlation, aggregation, filtering, and incident creation. To perform these functions, it uses a set of rule files and a knowledge base to compare events to patterns of common network security threats. See About the Correlation Manager knowledge base on page 116. To facilitate security analysis, the Correlation Manager filters false positive events from networks, including the events that your company security policy permits. The Correlation Manager also identifies attacks based on patterns of firewall, Intrusion Detection System, and antivirus activity across desktops, gateways, and servers. The Correlation Manager can then declare the incidents that warrant further action and closure. The Correlation Manager can provide conclusions regarding the overall analysis or cause of attacks. It also aggregates information about source, destination, attack types, and all related events into the incident record for forensic analysis. See About the default rules set on page 116.

116 116 Managing the correlation environment About the Correlation Manager knowledge base About the Correlation Manager knowledge base The Correlation Manager knowledge base consists of the tables that contain information about the network, security policies, and normalized event categories and subcategories. The Information Manager default rules reference this information to allow the correlation engine to make a more effective evaluation of incoming security events. Custom rules can also reference the information in the Correlation Manager knowledge base tables. The information in the knowledge base is a combination of the following: Updated information from Symantec DeepSight Threat Management System and the information that you can edit from the Lookup Tables option of the Rules view. If you have a valid DeepSight license, you can receive frequent updates directly from DeepSight. If you do not have a license, you receive updates to security content through LiveUpdate packages. See About the Correlation Manager on page 115. See About managing Global Intelligence Network content on page 327. About the default rules set Information Manager includes a set of rules that identify the most common security threats. Information Manager also provides default filters to help reduce common false positives. New rules are developed regularly and are distributed through the LiveUpdate process. You can also create your own rules from the Rules view of the Information Manager console. See About the Correlation Manager on page 115. See About the Correlation Manager knowledge base on page 116. Table 7-1 lists the default rules and the types of security products with which they are usually associated.

117 Managing the correlation environment About the default rules set 117 Table 7-1 Security product Correlation Manager rules by security product type Associated rules Antivirus Firewall AntiVirus Disabled Critical Malicious Code Detection Incomplete AV Scan Malicious Code via Not Quarantined Malicious Code Not Quarantined Malicious Code Outbreak Malicious Code Propagation Outbound Spam Zombie Spyware Not Quarantined Spyware Outbreak Worm Activity Block Scan Check FTP Transfers Distributed DoS High Volume DoS High Volume External Port Sweep Internal Port Sweep IP Watchlist Destination IP Watchlist Source IRC Bot Net Malicious URL Organization IP in Watchlist Activity Outbound Spam Zombie Ping Scan Detector Port Scan Detector Potential Staged Attack Scan Followed By Exploit Single Event DoS Smurf Attack Firewall Traffic to a Monitored Address Trojan Connections Unauthorized Outbound Domain Unauthorized Port Inbound Unauthorized Port Outbound Traffic to a Monitored Address Watchlist Potential Policy Violators

118 118 Managing the correlation environment About the default rules set Table 7-1 Security product Correlation Manager rules by security product type (continued) Associated rules Network intrusion detection system (NIDS) Attempted DNS Exploit Attempted FTP Exploit Attempted WWW Exploit Attempted Service Exploit Block Scan Departed Employee Username DoS High Volume Distributed DoS High Volume Intrusion Threshold (Disabled by default) IP Watchlist Destination IP Watchlist Source IRC Bot Net Malicious Code Propagation NULL Login Authentication Violation Ping Scan Detector Return Trojan Traffic Scan Followed By Exploit Single Event DoS Smurf Attack IDS TFTP from WebServer Traffic to a Monitored Address Vulnerability Scan Vulnerability Scan Detector Watchlist Potential Policy Violators Web Vulnerability Scan

119 Managing the correlation environment About the default rules set 119 Table 7-1 Security product Correlation Manager rules by security product type (continued) Associated rules Host intrusion detection system (HIDS) Account Guessing Attack Departed Employee Username DoS High Volume IP Watchlist Destination IP Watchlist Source Multiple Files Modified NULL Login Authentication Violation Password Guessing Attack Potential Staged Attack Scan Followed By Exploit Single Event DoS Trojan Connections Vulnerability Scan Vulnerability Scan Detector Watchlist Potential Policy Violators Web Vulnerability Scan Vulnerability assessment Potential Staged Attack Vulnerability Scan Policy compliance Departed Employee user name Activity Policy Compliance Violation Windows Events Account guessing attack Non Business Hours Logins Password guessing attack Potential Staged Attack Windows Account Lockout (Disabled by default) Windows Audit Log Cleared Windows Privileged Activities by user Windows Privileged User Created Windows Security Violation (Disabled by default) Windows Sensitive File Access

120 120 Managing the correlation environment About the default rules set Table 7-1 Security product Correlation Manager rules by security product type (continued) Associated rules Information Manager System Agent Queue Monitor Cert Expiration Warning Incident Creation Alert (Disabled by default) Invalid Event Date Alert Low Disk Space Warning MultiEvent Rule Example Negative Rule Type Example Password Guessing Attack Validate Archive

121 Chapter 8 Defining rules strategy This chapter includes the following topics: About creating the right rule set for your business About defining a rules strategy About correlation rules About rule conditions About the Event Count, Span, and Table Size rule settings About the Tracking Key and Conclusion Creation fields About the Correlate By and Resource fields Importing existing rules Creating custom correlation rules Enabling and disabling rules Working with the Lookup Tables window About creating the right rule set for your business A good approach to creating custom rules is to start with the generalized rules provided by Symantec and fine-tune them. Another good approach is to add new rules based upon real event data from your network. See About defining a rules strategy on page 123. The customizations usually belong to one of the following categories:

122 122 Defining rules strategy About creating the right rule set for your business Incidents stemming from machine-generated events Incidents relating to human events or policies These include all of the security devices on your network that generate the events that you collect. For example, firewall products such as Checkpoint Firewall generate a huge amount of event data. In most cases, you should edit default rules or create new rules to filter out false positive incidents. These incidents include your corporate IT security policies and regulatory compliance requirements. They also include any unique characteristics about user activity in your network that machine-generated events would typically miss, or that result in false positive incidents. The following is a general overview of the process for developing rules: Set up Information Manager in a lab environment. Update the Assets view to include the IP addresses of hosts that are mission-critical or that host sensitive information. Collect event data from your network for a week. This data should include events from all of the security products that you want Information Manager to correlate. For example, antivirus, host intrusion detection systems, network intrusion detection systems, and firewalls. Run the default rules and review the incidents created. Look for any false positives that you can easily filter out. Following are examples of good candidates for filtering: Incidents from the failed connections that the firewall reports, and the Windows-only attacks that computers running Linux report. Look at any known security incidents that occurred during the week that you collected the data. Adjust the filters and rules if there are any incidents that should have been created and were not. Look for the incidents that are the result of firewall rules being too lax. Tuning firewall and Information Manager rules is an on-going process based upon the changes in your network. Opening a firewall port to enable an essential line-of-business application may suddenly result in a huge number of false-positive incidents. When that occurs, you need to create a new rule to filter out events from an approved use of that application. You may also discover that there is a port that is still open long after the application that required it has been retired. Create rules to support security practices in your company. For example, you can create a rule to assign a weekly help desk ticket for security IT to contact users who are not running antivirus software.

123 Defining rules strategy About defining a rules strategy 123 As you change rules, use the Information Manager rule test feature to assess whether the customizations work. Of particular concern should be any rules that never create conclusions or those that create conclusions too often. With your Information Manager server still in a test environment, forward live network events to it. Continue to refine your rules. After you are satisfied with the incidents that are declared, migrate the server to your live network. About defining a rules strategy To develop a security plan that incorporates correlation rules and filters, you must understand the business needs of your organization from a security perspective. See About creating the right rule set for your business on page 121. For example, if your implementation protects and monitors network resources relating to financial transactions, you can develop and refine your rule set accordingly. Your area of concern might focus on authentication on the servers that contain sensitive financial data. In addition, you may need to evaluate the rules that you deploy based on regulatory compliance concerns. This evaluation ensures that the event data that is evaluated is handled in a way that meets the requirements of the policies. About correlation rules Correlation rules describe the logic that is applied to an event or a set of events to detect possible security concerns. See About creating the right rule set for your business on page 121. Conceptually, correlation rules can be classified into the following general categories: An event identifies an attacker who attempts to intrude on a specific computer or resource. Some unknown system or a number of systems that attempts to cause a specific system to malfunction or cease functioning. The organization or analyst wants to group events into particular types of incidents to make viewing and analysis simpler. For example, these types of rules may aggregate the events that are related to policies or products. Correlation rules consist of the following:

124 124 Defining rules strategy About rule conditions Rule type Identifies the pattern that best describes the event. See About rule types on page 125. Event criteria The specific values or threats that the rule applies to, including the number of events that occurs over a specified period of time. See About event criteria on page 129. Rule settings Conclusion and correlation settings (Actions tab) Auto assignment and notification settings The event count, span, table size, tracking keys, and description of an event. The fields that are used to correlate existing event conclusions with new events as they occur within the specified time period. If the number of events that are specified in the Count field is met, the conclusion is escalated to an incident. In addition, the incident is then correlated with existing incidents where applicable. Additionally the severity of a match for the rule is determined. Additional details are also available by the variables that you can specify in the Description field. Describes how alert and incident assignment tasks are handled when an incident is created. The Auto Assignment area incidents can be assigned to a specific user or user group (team). The Notification area let you notify to the additional recipients that the incident has occurred. For example, an Antivirus Disabled incident might be assigned to a response technician who is responsible for immediately assessing the event. An additional notification can be sent to the network administrator who monitors the overall health of the network segment from which the incident occurred. About rule conditions The rule conditions describe the fields and conditions that the rule is processed against to determine if the event applies to a conclusion. See About correlation rules on page 123.

125 Defining rules strategy About rule conditions 125 About rule types The Rule Conditions panel provides access to all available event and schema field data. The analyst can use this data to further identify and define the events that should be escalated as a potential security threat. A rule type determines the underlying behavioral patterns that a rule uses to identify a match. For example, if the rule type is set to Single Event, the rule evaluates each event for a criteria match. It only requires a single event to trigger a conclusion. A rule that uses the Many to One rule type evaluates each event against the criteria. However, it then creates a conclusion when a specified number of matching events have aggregated over a predetermined period of time. See About rule conditions on page 124. Conclusions that involve more than one event use the One to Many and Many to One event correlation tables. In addition, the Tracking field is provided. It identifies the element that is used as the basis for additional events to be correlated to existing events and conclusions. Table 8-1 describes the rule types that are available and provides examples. Table 8-1 Rule types Rule Type Trigger Condition Possible Scenarios Many Sources, One Target Creates a conclusion when the events that match the specified criteria are detected from multiple unique source IP addresses to a single destination IP address within the specified period. Denial-of-service events can often be identified using this rule type. A Smurf attack uses ICMPEchoReply events from a large number of source computers to a single target. Predefined rule examples: Distributed DoS High Volume, Smurf Attack Many Symantec Signatures, One Source Creates a conclusion when the events of different types that match the specified criteria are detected from a single source IP address within the specified period. A rule that detects a vulnerability scan can use this rule type. Within the criteria for that rule, EMR values can be set to identify multiple exploit events (such as Mechanism: Buffer Overflow, or Application Exploitation). In this example, the criteria for this rule includes multiple types of Mechanisms. Therefore, the rule would track multiple types of exploit events coming from the same source. Predefined rule example: Vulnerability Scan Detector

126 126 Defining rules strategy About rule conditions Table 8-1 Rule types (continued) Rule Type Trigger Condition Possible Scenarios Many Symantec Signatures, One Target Many Targets, One Event Many Targets, One Source Creates a conclusion when events of different types matching the specified criteria are detected to a single destination IP address within the specified period. Creates a conclusion when events of the same type matching the specified criteria are detected from many unique destination IP addresses within the specified period. Creates a conclusion when events matching the specified criteria are detected from a single source IP address to multiple unique destination IP addresses within the specified period. A rule that detects malicious IP hopping activity can use this rule type. To conceal scanning activity, an attacker may attempt one type of attack from one IP address. The attacker then changes to a different IP address to try a different attack until the most useful vulnerabilities have been identified. Attackers use this method to avoid detection as a vulnerability scan. Attackers know that vulnerability scanners often operate from a single source. Using this rule type, you can detect conditions where multiple attack types are targeted at a single host, regardless of the attack origin. A rule that detects a Malicious Code Outbreak can use this rule type. To identify a Malicious Code Outbreak, a rule can be configured to identify instances of a particular virus on multiple targets. Using the EMR fields, the criteria can be set to Virus. Since the rule looks for the same event type, this rule would trigger only if it was the same virus event on each target. A rule that identifies a reconnaissance attack on multiple targets (such as a port scan) can use this rule type. To configure this example, you would choose the Many Targets, One Source rule type, and then set the EMR criteria value to Portscan. Predefined rule examples: Block Scan, IRC Bot Net, Ping Scan Detector

127 Defining rules strategy About rule conditions 127 Table 8-1 Rule types (continued) Rule Type Trigger Condition Possible Scenarios Many to One Creates a conclusion when events matching the specified criteria are detected in a pattern that is set using the Many To One Fields, and the One To Many Field options. In addition to the Event Criteria, the fields that must contain the same information for each event (One-Many Fields) and the fields that can contain different values in each event (Many-One Fields) are used to correlate similar events occurring within a predetermined timeframe. A rule to create a port sweep can use this rule type. A port sweep is typically described as a single IP address that scans for a specific port on multiple computers. After you choose this rule type and set the event criteria for the rule, you set the One-Many and the Many-One field options. In the One-Many Fields area, select IP Source Address and IP DestinationPort. This selection means that the event originates from the same IP address that is evaluating the same port). In the Many-One Fields area select the IP Destination Address option. (Note that the event destination can be a different IP address for each event.) The Many to One rule requires the Tracking field to be populated. For this type of rule, the Tracking field generally matches a One-Many Fields entry. Predefined rule examples: MaliciousCodeOutbreak, SpywareOutbreak, DoS High Volume, External Port Sweep, Internal Port Sweep, Port Scan Detector, Intrusion Threshold, MultipleFilesModified, AccountGuessingAttack, Password Guessing Attack Multi-condition Single Event Creates a conclusion when a sequence of specified patterns is detected for one combination of one-to-many fields within a specified time period. Creates a conclusion if an event matches the specified criteria. This rule type requires the Tracking field to be populated. User logs on to a Windows computer and establishes an SSH connection to a UNIX computer. The user then logs on the FTP server, and downloads files from the FTP location. Predefined rule examples: AntiVirus Disabled, Malicious Code Not Quarantined, Spyware Not Quarantined, Check FTP Transfers, Malicious URL, Trojan Connections, AttemptedDNSExploit, Attempted FTPExploit, AttemptedWWWExploit, TFTPfrom WebServer, WindowsSecurityViolationWindows Account Lockout, Windows Audit Log Cleared, Windows Privileged Activities by User

128 128 Defining rules strategy About rule conditions Table 8-1 Rule types (continued) Rule Type Trigger Condition Possible Scenarios Symmetric Traffic Creates a conclusion when the specified pattern of events is detected from a single source IP address to a single destination IP address, then from that destination IP address back to the original source IP address within the specified period. A rule that identifies BackOrifice exploit traffic between a single target and source can use this rule type. To monitor for BackOrifice symmetric traffic events, after you choose the Symmetric Traffic rule type, set the criteria to Symantec Signature for BackOrifice (attackid 1414). The rule triggers if an Intrusion Detection System logs both the connection from a source to a target, and from that target back to the source as being BackOrifice traffic. Transitive Traffic Creates a conclusion when the specified pattern of events is detected from a single source IP address to a single destination IP address. Then, the pattern is detected from that destination IP address to a new destination IP address within the specified period. Predefined rule example: Return Trojan Traffic A rule that identifies the BackOrifice exploit traffic that moves from one source to a target backdoor, and then the targeted computer becomes the source that accesses the backdoor of a new target can use this rule type. To monitor for BackOrifice transitive traffic events, after you choose the TransitiveTraffic rule type, set the criteria to Symantec Signature for BackOrifice (attackid 1414). The rule triggers if an Intrusion Detection System logs both the connection from a source to a target as BackOrifice traffic and then identifies the target connecting to a new target with the same event signature. Predefined rule example: Malicious Code Propagation X followed by Y Creates a conclusion when a specified pattern is detected from a single source IP address to a single destination IP address. This pattern is followed by a different pattern from the same source IP address to the same destination IP address within the specified time period. Predefined rule examples: Scan Followed by Exploit, Null Login Authentication Violation Note: This rule is deprecated and is not supported. Use a Multi-condition rule type.

129 Defining rules strategy About rule conditions 129 Table 8-1 Rule types (continued) Rule Type Trigger Condition Possible Scenarios X not followed by X X not followed by Y Y not preceded by X Lookup Table Update Creates a conclusion when an event that matches the defined criteria cannot be detected in a pattern during a predefined number of times during timeout. Creates a conclusion when an event occurs that is defined by an X rule criteria. However, an event that is defined by the Y rule criteria does not. Creates a conclusion when an event that is defined by an X rule criteria does not occur. However, the next event that is defined by the Y rule criteria occurs. Updates the configured lookup table if an event matches the specified criteria. A rule to monitor user authentication failure for a specific period of time can use this rule type. User logon fails for a specific period of time and the user does not log in again. A rule to detect a non-occurrence of a user action after a valid user action can use this rule type. User logs on to a critical server but does not log off for a long time. A rule to detect a deletion of user before the user is added can use this rule type. A rule to dynamically update the lookup table with the configured event field values for the specified event criteria. About event criteria The Event Criteria field contains a vast array of possible values that a rule can use to identify an event pattern. The Event Criteria field includes event data and schema information. See About rule conditions on page 124. Table 8-2 describes the tabs available in the drop-down list. Table 8-2 Event Criteria tabs Name Common Description Contains the data from the Normalization fields, the Symantec DeepSight Threat Management System database (using the Symantec Signature), and the Asset and the Network tables.

130 130 Defining rules strategy About rule conditions Table 8-2 Event Criteria tabs (continued) Name Derived Events Other Fields Table Lookups Description Contains the customized data from the Normalization fields, the DeepSight database (using the Symantec Signature), and the Asset and the Network tables. The system applies logic to the source and the destination IP addresses that results in several fields or flags being added to the event. For fields, this information is primarily data from the Asset and Network table. For flags, this information includes: traffic direction, Source is Internal, Destination is Internal, service info, Destination Port is Open, whether the Asset entry has the destination_port value that is listed as available, whether the asset is Vulnerable, or whether the Asset entry for the event s destination_ip value is listed as being vulnerable to one or more of the BugTraq IDs associated with the event s Symantec Event Code. Includes all of the events that have been identified for each product that is associated with your installation of Information Manager. This information is based on a combination of the default set of events (the Information Manager schema) and any SIPs that have been installed. These fields do not contain the Information Manager normalized values. Provides a means of creating a product-specific field that uses a string or an integer value that may not be accessible through the schema provided. Event data is included with some of the events that are sent to Information Manager that a specific point product uses. However, this data is not accounted for as an identified field in the Information Manager schema that the collector uses (also known as out-of-band data). This data can be included either by the collector or it can be added during normalization. Provides access to the fields that are associated with the knowledge base tables that Information Manager and the environment provide. Also provides access to the resource-specific data that the user provides. For example, the Asset and Network tables. These fields are dynamically generated based on the current state of each of the knowledge base tables. The Event Criteria rows include a logical decision field that provides the operator that is used to determine how the event criteria are evaluated. Table 8-3 describes the decision option operators available. Note: The available operators vary with each criteria type. Table 8-3 Event Criteria operators Name Equal Not Equal Greater than Description The field value is an exact match to the criteria value. The field value does not match the criteria value. The field value is greater than the specified value.

131 Defining rules strategy About rule conditions 131 Table 8-3 Event Criteria operators (continued) Name Less than Greater than or equal to Less than or equal to Null Not Null Is in Is not in True False Contains Doesn't contain Matches Doesn't match Description The field value is less than the specified value. The field value is greater than or equal to the specified value. The field value is less than or equal to the specified value. The field is empty. The field contains a value. The field value contains a value that is contained in the specified table. The field value does not match a value that is contained in the specified table. The field value is True. The field value is False. The field value contains the specified string. The usage of this operator varies with the field against which the data is compared. For example, if you use EMR values, a drop-down list of possible values appears. However, if you evaluate the string data in a field such as target_resource, the value that you type is used to perform a substring search. For example, if you want to find out if the string root.exe was contained in the target_resource field, if target_resource field contained root.exe is identified and causes a match. The field value does not contain the specified string. The usage of this operator varies with the field that the data is compared with. For example, if you use EMR values, a drop-down list of possible values appear. However, if you evaluate the string data in a field such as target_resource, the value that you type is used to perform a substring search. For example, if you wanted to verify that the string root.exe was not included in the target_resource field, if target_resource field contained root.exe is identified and indicates that Doesn't contain condition is not met. The field value matches the value that is specified as a regular expression. The field value does not match the value that is specified as a regular expression.

132 132 Defining rules strategy About the Event Count, Span, and Table Size rule settings About the Event Count, Span, and Table Size rule settings The Rules Editor includes the settings that let you specify how many events must occur within a specified period of time to meet the criteria for the rule. In addition, you can also determine the table size for the event data that is stored. See About correlation rules on page 123. Table 8-4 Event Count, Span, and Table Size rule settings Setting Event Count Span Table Size Description Determines the number of events that must occur within a specific time period to trigger an incident. The time period is specified in the Span settings. This setting is used primarily with the Many-One Field area on the Actions tab. Indicates the time period for the number of events that are specified in the Event Count field to occur. Specifies the state table size, in rows, that is maintained in memory for each rule. For example, the Account Guessing Attack predefined rule requires that two events be identified within 10 minutes for the rule to trigger an incident. After the first event matches the rule criteria, an internal aggregation table is created that contains the event details. When the second matching event occurs, data from the second event is added to the same aggregation table. In this case, the Table Size setting is relatively small. However, if the Event Count were raised to a much larger number, the aggregation table could potentially run out of space. In that case, the table wraps (the new event data begins to overwrite the original event data in sequential order). To prevent the data from being overwritten, the Table Size should be adjusted according to the event size expectations for the rule. Event data sizes vary widely with each implementation, but using the predefined rules as a starting point helps to identify general size parameters. About the Tracking Key and Conclusion Creation fields The Tracking Key and Conclusion Creation fields are used to further refine rules settings. Use these fields to establish whether an event should be correlated to the existing events that are tracked in aggregation tables. In addition, the Tracking Key and Conclusion Creation fields include the Severity and the Description fields. These fields provide a means for security analysts to escalate conclusions based on severity, and to include additional extracted information within the Conclusion Description. Table 8-5 describes the Tracking Key fields on the Conditions tab.

133 Defining rules strategy About the Tracking Key and Conclusion Creation fields 133 Table 8-5 Tracking Key fields (Conditions tab) Field One-Many Fields Description Describes the elements that must remain consistent across each event in order for the event to be correlated to an existing event aggregation table. For example, to define a rule that tracks a single user name connecting to multiple target IP addresses (in other words, one user name to many IP addresses), set the rule type to One to Many, and in the One-Many Fields area, select User Name. This field must be the same in each event for any subsequent events to be correlated with previous events. Many-One Fields Describes the elements that must be different for each event in order for the event to be correlated to an existing event aggregation table. This field is used with the Event Count field to determine when the conditions for a One to Many rule have been met. For example, you want to define a rule that tracks a single user name connecting to multiple target IP addresses: in other words, one user name to many IP addresses. Set the rule type to One to Many, and in the Many-One Fields select Target IP. The IP address in this field must be different in each event for any subsequent events to be correlated with previous events. Tracking Fields Describes the field upon which a matching event is correlated to an existing conclusion. If an event matches the criteria for a rule, it is compared against the tracking fields for any existing conclusion. If the event matches an existing conclusion it is correlated to that event rather than being considered for a new conclusion. Required with the ManytoOne and Single Event rule types. With OnetoMany rules, this field is typically used to track the same value as in the One-Many Field area. The event field data that must remain the same across each new event that is to be added to the aggregation table. Table 8-6 describes the Conclusion Creation fields on the Actions tab. Table 8-6 Conclusion Creation fields (Actions tab) Field Alerting Incident Description Describes whether an incident should be treated as an alert rather than a security incident.

134 134 Defining rules strategy About the Correlate By and Resource fields Table 8-6 Conclusion Creation fields (Actions tab) (continued) Field Severity Description Describes the severity of the event conclusion which can determine whether an incident is created. The Severity values include the following: 1- Informational: Purely informational events. 2 - Warning: User decides if any action is needed. 3 - Minor: Action is required, but the situation is not serious at this time. 4 - Major/Critical: Action is required immediately and the scope may be broad. 5 - Fatal: An error occurred, but it is too late to take remedial action and the scope is broad. Description Remediation Provides a user input area for security analysts to further define the conditions that led to the creation of the conclusion. This field also supports the use of field name variables that can be populated with event data. Provides a user input area for security analysts to include remediation notes for each incident that is created. The notes appear on the Remediation tab for the incident. About the Correlate By and Resource fields The Correlate By field determines whether a conclusion that is created should be mapped to an existing incident. See About correlation rules on page 123. For example, if a Virus Outbreak incident is in progress, using the appropriate setting in the Correlate By field causes each Virus Outbreak conclusion with the same virus name to be mapped to the existing incident. In addition, you can use the Resource field drop-down list to further refine the characteristics of the correlation requirements for the incident. Table 8-7 describes the Correlation types available in the Correlate By field. Table 8-7 Correlate By fields Type None Resource and Conclusion Type Description Correlation does not occur for the new incidents that match this rule. Correlation is based on the Resource and the Conclusion type. For example, the same Virus Outbreak Conclusion type occurs on the same host that is specified in the Resource field. Therefore, the new conclusion is correlated to an existing incident.

135 Defining rules strategy Importing existing rules 135 Table 8-7 Correlate By fields (continued) Type Source and Destination Source and Conclusion Type Source Destination and Conclusion Type Destination Conclusion Type Description Correlation is based on the Source and the Destination fields. For example, a new conclusion is created and the source IP and destination IP are the same. Therefore, the conclusion is correlated to the existing incident. Correlation is based on the Source and the Conclusion type. For example, the same IP address causes PortScan conclusions. Therefore, any new PortScan conclusion that originates from the same source is mapped to the existing incident. Correlation is based on the Source field. If the Source matches, any conclusion that originates from that source is correlated to the existing incident. Correlation is based on the Destination and the Conclusion type. For example, the conclusion is a denial-of-service attack that targets the same destination IP. Therefore, the conclusion is mapped to the existing incident. Correlation is based on the Destination field. If the Destination is the same, any conclusion that applies to that destination is correlated to the existing incident. Correlation is based on the Conclusion type. For example, all AntiVirusDisabled conclusions are mapped to the existing incident regardless of source or destination values. Importing existing rules You can import rules from separate instances of Information Manager using the Import and the Export features available in each version. If import a rule that references custom lookup tables, you must also import those tables. See About correlation rules on page 123. If you import a rule from a previous supported version of Information Manager, use the Rules view to delete any imported policy information. Then, apply the current policies. Java-based rules are imported as jar files. Note: In the User Monitor folder, you can import only those monitors that are created by using Information Manager version 4.5. When you import rules from a previous version of Information Manager that include user, team, or role assignments, verify that the assignments are configured correctly after the import completes. Sometimes a user, team, or role that existed in a previous version is not identical to the version that exists in the upgraded version. If so, you may need to reconfigure the rule assignment values to match the assignee information in the upgraded version.

136 136 Defining rules strategy Creating custom correlation rules To import an existing rule 1 In the console from which you want to export the rules, navigate to the Rules view. Then, export the rules you want to apply to the new console. 2 In the current Information Manager console, on the Rules view, expand the Correlation Rules folder. 3 Under the Correlation Rules folder, expand the User Rules folder. 4 Click Import from disk. 5 In the Select File(s) to Import dialog box, locate the file or files to import, and click Import... To import a Java-based rule 1 In the Information Manager console, on the Rules view, click the User Monitors folder and then click Import from disk. 2 In the Select File(s) to Import dialog box, locate the jar file or files to import. 3 Click Import... Creating custom correlation rules The correlation rules describe the logic that is applied to an event or a set of events to detect possible security concerns. See About creating the right rule set for your business on page 121. You can create correlation rules from the Rules view of the console of the Information Manager client. See About correlation rules on page 123. The process for creating the correlation rules is as follows: Define a name for the rule. See To define a name for the rule on page 137. Configure rule condition. See To configure the rule conditions on page 137. Configure the rule action. See To configure the rule actions on page 138. Deploy the rule on the server. See To deploy the rule on the server on page 140.

137 Defining rules strategy Creating custom correlation rules 137 To define a name for the rule 1 On the Information Manager console, click Rules. 2 In the left navigation pane, under the Correlation Rules folder, click User Rules. 3 On the Rules tab, click Create new filter or rule (+). 4 In the Input dialog box, type a name for the rule. You can now define a rule condition. A conclusion is generated if the set of events satisfies the defined conditions. Note: You can configure multi-conditioned rules. Multi-conditioning lets you define the rules that support up to five user activities in a sequence. You can create a conclusion when a sequence of specified pattern is detected for one combination of one-to-many fields within a specified time period. See Creating a multicondition rule on page 141. To configure the rule conditions 1 On the Conditions tab, in the Description window, type a description for the rule. 2 On Conditions > Rule Type, click the entry that best matches the type of event and target combination that applies to the new rule. For example, to declare an incident whenever a specific event is detected, select Single Event. To declare an incident after a specific number of events are detected from a specific IP address, select Many Targets, One Source. See About rule types on page In the Event Criteria area, click Add. 4 Select the left column of the new entry, and then choose an event field. 5 Select the center column and specify the operator. 6 Select the right column. Based on the operator that you chose, specify the value that must be true for the event type. 7 Repeat steps 3 through 6 for any other event criteria that you want applied to the rule. You can select multiple event criteria and apply logical operators (AND/OR) to them. 8 In Event Count, specify the number of times that the event criteria that you specified must be true for an incident to be declared.

138 138 Defining rules strategy Creating custom correlation rules 9 In Span, specify the time that is required for the number of events that are specified in the Event Count to occur. For example, you can specify that 30 events of a specific type must occur within 60 minutes, before an incident is declared. 10 In Table Size, specify the maximum number of events that the rule can track at any one time. The table size should generally be a multiple of the Event Count setting. The Table Size setting divided by the Event Count setting is equal to the maximum number of event groups that the rule can manage. 11 In the Tracking Keys area, specify the fields to include in the incident. This field can be any of the One-Many, Many-One, or Tracking fields that are associated with the incident. You can now define the rule actions. A conclusion is generated if the set of events satisfies the defined conditions. Note: You can create rules to detect threats based on the absence of the events that you expect to occur. See Creating a correlation rule based on the X not followed by Y rule type on page 145. To configure the rule actions 1 On the Actions tab, check Alerting Incident (not a Security Incident) to specify that an incident is an alert incident and not a security incident. Alerting incidents notify about a situation that requires your attention if there is a discrepancy on a system. Security incidents notify about a situation where there is a potential threat due to a security breach in the organization. 2 From the Severity options, select the severity that you want to be associated with the incident. 3 In the Description area, type a description of the problem. This information appears to users who are assigned the incidents or the tickets based upon the incidents that this rule triggers. (Optional) Click Add(+) to include the fields from the final event that triggered the conclusion. When a conclusion is generated, these fields are replaced with their corresponding values in the description. 4 (Optional) Click Remediation to populate the Custom Remediation library for this conclusion and to instruct the analysts with a remedy that is specific for your organization.

139 Defining rules strategy Creating custom correlation rules In the Correlate By list box, select the method by which conclusions are grouped into incidents. 6 If you selected Resource and Conclusion Type from the Correlate By list box, you can select a field in Resource Field. This field is used to correlate conclusions within an incident. Conclusions can be correlated together into incidents based on the value of the resource field. 7 To specify that a user or team is automatically assigned to incidents that this rule creates, do the following: Turn on Enable Auto Assign and then click Add. If you want to assign incidents based upon the IP address of the affected target computer, in the left column select IP Address or Network options. Any Address is the default option. Retain the default option to ensure that all the occurrences of the incident get assigned irrespective of the IP address. To assign incidents to an individual user, in the User column, select the user who should be assigned with the incidents. To assign incidents to a group of users, in the User Group column, select the team that should be assigned with the incidents. At any time, you can click Clear to clear the selections. If you want to automatically assign incidents to the least busy member in a user group, check Assign to least busy user and then select the corresponding user group. See About automatically assigning incidents on page In the Notification area, check Enable if you want to notify users about the incident activity. If you want to notify users only when an incident is created, check Send notification for incident creation only. 9 Click Recipients to select the method of notification for each recipient. The options are Address Entry, User, User Group, Syslog, SNMP Trap. Once the method of notification is selected, you are prompted to enter details corresponding to the option that you selected. After you specify the condition and the action, you can test the rule and then deploy it on the server.

140 140 Defining rules strategy Creating custom correlation rules To deploy the rule on the server 1 On the Testing tab, select the archive containing event data, and then click Start Test. 2 When you are satisfied with the incidents and the conclusions that the rule creates, turn on the rule in the Rules list. 3 On the top toolbar, click Deploy to the server. See Enabling and disabling rules on page 152. About automatically assigning incidents In Information Manager, an incident is created when an event matches a criterion that is specified in the Rules and Monitors. Based on the rules that are set, these incidents can be automatically assigned to a specific user group or an individual user. Rules or Monitors can be set to assign incidents automatically to the least busy member in a user group. See Assigning incidents automatically to the least busy member in a user group on page 141. Incidents are automatically assigned to the individual with the lowest load factor. The load factor is calculated based on the incident count and the incident state. Each incident state is assigned a value. Incidents that are in the New state are assigned the highest value, whereas incidents in the Waiting state are assigned the lowest value. A user group member who has many incidents in the New state is considered busy. Therefore the incidents in the New state have the highest value. The incidents in the Working state have lower value and the incidents in the Waiting state has the lowest value. The number of incidents that are already assigned to a user and the value that is assigned to the incident state determines the load factor. The members with the lowest load factor are given priority when they assign an incident. When two or more users have the same load factor, Information Manager uses the timestamp to determine which user is the least busy. Table 8-8 shows how Information Manager calculates the incident load factor. Three users are assigned the same count of incidents in different incident states. Although each user has the same number of incidents, their load factors are different because the values of their incidents are different. In the example, Information Manager automatically assigns incidents to User C because User C has the lowest load factor.

141 Defining rules strategy Creating custom correlation rules 141 Table 8-8 Incident load factor User Incidents: New Incidents: Working Incidents: Waiting Formula (incident count * value of incident state) Load Factor A (4*3) + (2*2) + (1*1) 17 B (2*3) + (4*2) + (1*1) 15 C (1*3) + (2*2) + (4*1) 11 Assigning incidents automatically to the least busy member in a user group Rules and Monitors can be set to assign incidents automatically to a user group or a user within the user group. You can also set rules and monitors to automatically assign incidents to the least busy member in a user group. Only user groups are considered when incidents are automatically assigned to the least busy member. The member with the lowest incident load factor is considered the least busy member in a user group. See About automatically assigning incidents on page 140. When incidents are assigned automatically to a user group for the first time, the first user in the user group becomes eligible for incident assignment. When an incident gets assigned to a member in the user group, a log entry is created for that incident. In the Incident log, this entry is listed as SSIM against the user name of that member. To assign incidents automatically to the least busy user 1 In the Information Manager console, click Rules. 2 Select a rule or a monitor that must be automatically assigned. 3 On the Actions tab, check Enable Auto Assign. 4 Check Assign to least busy user and then select the corresponding user group. When the rule is deployed, the incidents are automatically assigned to the least busy member in the user group. Creating a multicondition rule Consider a sample scenario for creating an event when a combination of conditions is fulfilled. See About rule conditions on page 124.

142 142 Defining rules strategy Creating custom correlation rules If the following conditions are met, then an event must be triggered: The user logs on to a Windows domain controller. The user creates a new user. The user modifies the privileges for the newly created user. (For example, the user gives the new user domain admin privileges.) The user logs out. Note: The event codes in the procedures are applicable to Microsoft Windows They may vary for other operating systems. To create a new rule 1 On the console of the Information Manager client, click Rules. 2 In the left navigation pane, under the Correlation Rules folder, click User Rules. 3 On the Rules tab, click Create new filter or rule (+). 4 In the Input dialog box, type a name for the rule. The rule name appears in red color under the User Rules folder. 5 In the description box, type the description for the rule. (For example, monitor for the events that occur when all the conditions that are specified are fulfilled.) Once you create a new rule, you must configure the rule conditions that are required based on the scenario. To configure the rule conditions 1 On the Conditions tab, in the Description window, type a description for the rule. 2 On the Conditions tab, on the Rule Type menu, click MultiCondition as it applies to the new rule. 3 In the Event Criteria area, click Add. Add the conditions that are required to trigger the rule. To add Condition 1 1 Select the left column of the new entry. From the drop-down list that appears, select the Events tab and click on the Host Intrusion Activity folder. From the collapsible list that is displayed, select Intrusion Action ID. 2 Select the center column and select the = operator.

143 Defining rules strategy Creating custom correlation rules Select the right column, and then select Login. This value corresponds to the logon action. 4 If the events must occur more than once for an incident to be declared, specify the count of events in the EventCount list that is located in the EventCriteria area. Add the other conditions that are required to trigger the rule. To add Condition 2 1 Under Rule Type, click Add to add a second condition. 2 Select the left column of the new entry for Condition 2. From the drop-down list that appears, click the Common tab and select Symantec Event Code. 3 Select the center column and select the = operator. 4 Select the right column, and then select 722. This value corresponds to a new user account created. 5 If the events must occur more than once for an incident to be declared, in the Event Criteria area, specify the count of events in the Event Count. Add the other conditions that are required to trigger the rule. To add Condition 3 1 Under Rule Type, click Add to add a third condition. 2 Select the left column of the new entry for Condition 3. From the drop-down list that appears, click the Common tab and select Vendor Signature. 3 Select the center column and select the = operator. Select the right column, and then select 632. This value corresponds to a new user account being added to domain admin group for the third condition. 4 If the events must occur more than once for an incident to be declared, in the Event Criteria area, specify the count of events in the Event Count list. Add the other conditions that are required to trigger the rule. To add Condition 4 1 Under Rule Type, click Addto add a fourth condition. 2 Select the left column of the new entry for Condition 4. From the drop-down list that appears, click the Common tab and select Symantec Event Code. 3 Select the center column and select the = operator. 4 Select the right column, and then select 720. This value corresponds to the user account Log-off for the fourth condition.

144 144 Defining rules strategy Creating custom correlation rules 5 In the Tracking Keys area, under the One-Many field, click Add and select Agent Host. Under the Tracking field, click Add and select IP destination address. 6 If the events must occur more than once for an incident to be declared, in the Event Criteria area, specify the count of events in the Event Count list. 7 In Span, set the time span equal to 20 minutes. 8 In Table Size, specify the maximum number of events that the rule can track at any one time. After you configure the rule conditions you must configure the rule actions. To configure the rule actions 1 On the Actions tab, in the Conclusion Severity option, specify the severity that you want associated with the incident. 2 In the Conclusion Description area, type a description of the problem. This information appears to users who are assigned the incidents or the tickets that are based upon the incidents that this rule triggers. (Optional) Click Add (+) to include the values of fields from the final event that triggered the conclusion. 3 In the Correlate By drop-down list, specify the method by which conclusions are grouped into incidents. 4 In the Resource Field menu, choose the desired event fields. Conclusions can be correlated together into the incidents that are based on the value of this resource field. 5 To specify that a user or team is automatically assigned to incidents that this rule creates, do the following: Turn on Enable Auto Assign. If you want to automatically assign incidents to the least busy member in a user group, check Assign to least busy user and then select the corresponding user group. To assign the incident that is based upon the IP address of the affected target computer, in the left column, type the IP address or netmask. In the User column, click the user to whom you want to assign the incidents. In the User Group column, click the help desk team to which you want to assign the incidents.

145 Defining rules strategy Creating custom correlation rules 145 After you specify the conditions and the actions, you can test the rule and then deploy it on the server. To deploy the rule on the server 1 On the Testing tab, specify the location of a file containing event data, and then click Start Test. 2 When you are satisfied with the incidents and conclusions that this rule creates, turn on the rule in the Rules list. 3 On the top toolbar, click Deploy to the server. Creating a correlation rule based on the X not followed by Y rule type Consider a sample scenario wherein a user logs on to a critical system and carries out some activity. However, the user fails to log off within an hour. Normally such a logon should last for less than an hour. If the user does not log off within an hour, this suspicious activity results in an event with a conclusion. This sample scenario is an example of Y not following X. See About rule types on page 125. To create a correlation rule for X not followed by Y 1 On the console of the Information Manager client, click Rules. 2 In the left navigation pane, under the Correlation Rules folder, click User Rules. 3 On the Rules tab, click Create new filter or rule (+). 4 In the Input dialog box, type a name for the rule. The rule name appears in red color under the User Rules folder. Example: Rule for Event Definition with negatives 5 In the Descriptions box, type the description for the rule. Example: Monitor for the events that have not occurred in a defined sequence. You can now define the required rule condition. An event is generated if the set of user actions satisfies the defined condition. In this example, X is the normal activity of a logon. Y is an activity of a logoff. Normally, Y follows X. However, in this example the logoff does not happen even after an hour. Therefore, use the rule type of X not followed by Y to trigger an event.

146 146 Defining rules strategy Creating custom correlation rules To configure the rule conditions and actions 1 On the Conditions tab, on the Rule Type menu, click the rule X not followed by Y. 2 In the Event Criteria area, click + to add a criteria for X. 3 Select the left column of the new entry, and then choose the event type as Mechanisms. 4 Select the center column and select the operator contains. 5 Select the right column, and then specify the value Login. 6 To add the criteria for Y, in the Event Criteria Postcondition area, select the left column of the new entry, and then choose the Mechanisms event type. 7 Select the center column and select the operator contains. 8 Select the right column, and then specify the value Logout. 9 In the Tracking Keys area under the One-Many fields, click Add to specify the fields that you want to track: for example, the Source IP address. Under the Tracking field's column, if you want to track the date of the event, you can add Event Date. 10 In the Event Count box, specify the number of times that the event criteria that you specified must be true for an incident to be declared. 11 In the Span box, specify the amount of time for the two events X and Y that are specified to occur. For example, you can specify that the two events X and Y must occur within 60 minutes, failing which an incident is declared. 12 In the Table Size box, specify the maximum number of events that the rule can track at any one time. The table size should generally be a multiple of the Event Count setting. 13 On the Actions tab, you can specify whether the incident is an Alerting incident and not a security incident. You can add the description and the remediation for that incident. 14 In the following areas for Autoassignments and Notifications you can specify whether the incident should be assigned automatically to the users or groups selected. 15 In the Notification area, you can enable notifications and specify the address of the recipients. You can add one or more recipients to receive the notifications. You must deploy the rule after you have created and configured the rule.

147 Defining rules strategy Creating custom correlation rules 147 To deploy the rule 1 On the console of the Information Manager client, click Rules. 2 In the left navigation pane, place a check mark in the box next to the rule that you want to deploy. 3 In the top toolbar, click Deploy. Creating a correlation rule based on the X not followed by X rule type Consider a sample scenario wherein a user tries to log on, fails, and does not attempt to log on again for 30 minutes. Normally, an authorized user tries to log on again within 30 minutes. However, this user waits for more than 30 minutes before attempting to log on again. This behavior indicates the suspicious activity that results in an event with a conclusion. This sample scenario is an example of X not following X. See About rule conditions on page 124. To create a correlation rule for X not followed by X 1 On the console of the Information Manager client, click Rules. 2 In the left navigation pane, under the Correlation Rules folder, click User Rules. 3 On the Rules tab, click Create new filter or rule (+). 4 In the Input dialog box, type a name for the rule. Example: Rule for Event Definition with negatives 5 In the Descriptions box, type a brief description for the rule. Example: Monitors for predefined behavior of events. You can now define the required rule condition. An event is generated if the set of user actions satisfies the defined condition. In this example, X is the normal activity of a logon. Normally, a failed logon attempt is followed by another logon attempt within a 30-minute period. However, in this example the user does not attempt to log on for more than 30 minutes. Therefore, you can use the rule type XnotfollowedbyX to trigger an event. To configure the rule conditions and actions 1 On the Conditions tab, on the Rule Type menu, click the rule X not followed by X. 2 In the Event Criteria area, click + to add a criteria for X.

148 148 Defining rules strategy Creating custom correlation rules 3 Select the left column of the new entry, and then choose the event type as Mechanisms. 4 Select the center column and select the operator contains. 5 Select the right column and then specify the value Login. 6 Click Add to add the second criteria for X. Then select the left column of the new entry, and in the drop-down list under Events, collapse the Intrusion Activity folder. Select Intrusion Outcome ID. 7 Select the center column and select the operator =. 8 Select the right column, and then specify the value Failed. 9 In the Tracking Keys area under the One-Many fields, click Add to specify the fields to track: for example, the Source IP address. Under the Tracking fields column, if you want to track the date of the event, add Event Date. 10 In the Event Count box, specify the number of times that the event criteria that you specified must be true for an incident to be declared. 11 In the Span box, specify the amount of time for the event. For example, you can specify 30 minutes, failing which an incident is declared. 12 In the Table Size box, specify the maximum number of events that the rule can track at any one time. The table size should generally be a multiple of the Event Count setting. 13 On the Actions tab, specify whether the incident is an Alerting incident and not a security incident. Add the description and the remediation for that incident. 14 In the following areas for Auto assignments and Notifications, specify whether the incident should be assigned automatically to the users or groups selected. 15 In the Notification area, enable notifications and specify the address of the recipients. You can add one or more recipients to receive the notifications. You must deploy the rule after you have created and configured the rule. To deploy the rule 1 On the console of the Information Manager client, click Rules. 2 In the left navigation pane, place a check mark in the box next to the rule to deploy. 3 In the top toolbar, click Deploy.

149 Defining rules strategy Creating custom correlation rules 149 Creating a correlation rule for the Y not preceded by X rule type Consider a sample scenario wherein a user logs on to a Linux system. The user uses putty or another secure connection mode to log on the su (superuser) role and creates another user. Normally, to create a new user role, you log on as the root. However, this uses bypasses the root logon and a new user account is created. This sample scenario is an example of X not preceding Y. To create a correlation rule for Y not preceded by X 1 On the console of the Information Manager client, click Rules. 2 In the left navigation pane, under the Correlation Rules folder, click User Rules. 3 On the Rules tab, click Create new filter or rule (+). 4 In the Input dialog box, type a name for the rule. Example: Rule for Event Definition with negatives 5 In the Descriptions box, enter a brief description for the rule. Example: Monitors for the events occurring in correct sequence. In this example, X is an activity of the root logon. Y corresponds to the creation of a new user account. Normally, a new user is created by logging on as root. However, in this example, the user does not log on as root but as a normal user. The user is able to create a new user account. Therefore, you can use the rule type of Y not preceded by X to trigger an event. You can now define the required rule condition. An event is generated if the set of user actions satisfies the defined condition. To configure the rule conditions and actions 1 On the Conditions tab, on the Rule Type menu, click the rule Y not preceded by X. 2 In the Event Criteria area, click + to add a criteria for X. 3 Select the left column of the new entry, and then choose the event type as Symantec Event Code. 4 Select the center column and then select the operator =. 5 Select the right column, and then specify the value 733 which correspond to the user action. 6 Click Add to add the second criteria for X. Then select the left column of the new entry, and in the drop-down list under the Events tab, collapse the folder for Intrusion Activity. Select Intrusion Outcome ID. 7 Select the center column and select the operator =.

150 150 Defining rules strategy Creating custom correlation rules 8 Select the right column, and then specify the value Failed. 9 In the Tracking Keys area under the One-Many fields, click Add to specify the fields to track: for example, the source IP address. Under the Tracking fields column, to track the date of the event, add Event Date. 10 In the Event Count box, specify the number of times that the event criteria that you specified must be true for an incident to be declared. 11 In the Span box, specify the amount of time for the event. For example, you can specify 30 minutes, failing which an incident is declared. 12 In the Table Size box, specify the maximum number of events that the rule can track at any one time. The table size should generally be a multiple of the Event Count setting. 13 On the Actions tab, you can specify whether the incident is an Alerting incident and not a security incident. You can add the description and the remediation for that incident. 14 In the following areas for Autoassignments and Notifications you can specify whether the incident should be assigned automatically to the users or groups selected. 15 In the Notification area, you can enable notifications and specify the address of the recipients. You can add one or more recipients to receive the notifications. You must deploy the rule after you have created and configured the rule. To deploy the rule 1 On the console of the Information Manager client, click Rules. 2 In the left navigation pane, place a check mark in the box next to the rule to deploy. 3 In the top toolbar, click Deploy. Creating a correlation rule for the Lookup Table Update The Lookup Table Update rule is set to dynamically collect information in the lookup tables. Any rule can refer to this information to generate incidents, tickets, and assets. You can create a correlation rule which refers to an existing lookup table that gets dynamically updated. After you create a rule, you can configure the rule conditions and actions and deploy it. This rule is created only for updating the lookup table. Therefore, conclusions are not created for the Lookup Table Update rule. See About rule types on page 125.

151 Defining rules strategy Creating custom correlation rules 151 Consider a sample scenario wherein a stack of intentionally bad credit cards is distributed to serve as bait for malicious users. A malicious user intending to commit fraud can use one of the bait cards that have been distributed. A list of such baited credit cards is maintained in a lookup table. Whenever a credit card usage event contains any of these baited credit card numbers, the source IP address of this event is immediately stored in the lookup table of the Information Manager. Later, if a legitimate usage event originates from the stored source IP address, it indicates fraudulence by the malicious user. A correlation rule that is set to refer to the dynamically updated lookup table generates an incident for the events that occur from the stored source IP address. Here a lookup table must be configured with a Lookup Table Update rule to get updates of the source IP address. To create a correlation rule for Lookup Table Update 1 In the console of the Information Manager client, click Rules. 2 In the left navigation pane, under the Correlation Rules folder, click User Rules. 3 On the Rules tab, click Create new rule (+). 4 In the Descriptions box, enter a brief description for the rule. You can now configure the required rule conditions and actions. An event is generated whenever the lookup table is updated with the specified event criteria. To configure the rule conditions and actions 1 On the Conditions tab, on the Rule Type menu, select Lookup Table Update Rule. 2 In the Event Criteria area, click + and specify the event criteria. 3 On the Actions tab, configure the actions for the Lookup Table Update rule by editing any of the following properties: Lookup Table Table Column Event Field Timeout in hours Lets you select the User Lookup Table that is modified dynamically if the event satisfies the specified event criteria. Automatically updates the key column in the Lookup Table. Lets you select the existing event fields. If an event satisfies the specified event criteria, the value of this event field is used to populate the key column in the Lookup Tables. Lets you specify the period after which an entry in the configured Lookup Tables is removed. The value can be specified in hours. If the value specified is 0, entries in the Lookup Tables do not expire.

152 152 Defining rules strategy Enabling and disabling rules After configuring the rule conditions, you must enable and deploy the rule. To deploy the rule 1 In the console of the Information Manager client, click Rules. 2 In the left navigation pane, place a check mark in the box next to the rule to deploy. 3 In the top toolbar, click Deploy. Enabling and disabling rules By enabling or disabling rules in the Rules view of the Information Manager console, you can temporarily filter certain network events. You can also change the way the Correlation Manager declares incidents. See About correlation rules on page 123. Note: In some cases, such as when the server is under a heavy event load, disabling or deleting a rule may not take effect immediately. To enable or disable a rule 1 From the Information Manager console, click Rules. 2 In the left navigation pane, check or uncheck the box next to a rule. A check mark against the rule indicates that the rule is selected to be enabled. 3 In the top toolbar, click Deploy. Working with the Lookup Tables window You can view and update the lookup table information from the Rules view. List entries change over time due to updates from LiveUpdate. You can also create user-defined lookup tables under the User Lookup Tables folder. See About correlation rules on page 123. The Lookup Tables provide a set of configurable tables that let you extend the functioning of rules. To ensure that some correlation rules function properly, you must populate the Lookup Tables with the information that is applicable to your network and resources. Key settings include the domains that apply to your network, files to be monitored, and users to be monitored. If required, additional user tables can be added based on your specifications. Table 8-9 lists the Lookup Tables and the types of information that they contain.

153 Defining rules strategy Working with the Lookup Tables window 153 Table 8-9 Lookup Tables Category Administrative Users Authorized Ports Inbound Authorized Ports Outbound Critical Servers default usernames ip watchlist Description List of users who can perform administrative activities. List of authorized ports through which incoming traffic is allowed as per the policies. List of authorized ports through which outgoing traffic is allowed as per the policies. List the IP addresses of the servers that are critical from business perspective. List of authorized users. Lists the IP addresses of known attackers. An incident is created if an event is detected from one of these IP addresses. TheIPWatchList table is a configurable table that is available for manually tracking known bad IP addresses. DeepSight and LiveUpdate updates maintain separate internal IP Watch List. The list contains IP addresses known to be malicious in the larger Internet environment. IP Whitelist Table Monitored Logging Devices Organization Domains P2P Programs Potential Policy Violation IPs Rapid Response Monitored Address Traffic sensitive files Lists the Whitelist IP addresses. These IP addresses and domain names are reputed and can be trusted. You can add your trusted domain names and IP addresses to the list. Lists the logging devices that must be monitored after a specific time span for idle state. Provides a table for the user to describe the organizational domains monitored. Lists the P2P programs. Lists the IP addresses of the hosts that can potentially violate the policy. Lists of all the bad IP addresses on which your sensitive data can communicate. Lists the file names to monitor during FTP transfers.

154 154 Defining rules strategy Working with the Lookup Tables window Table 8-9 Category sensitive urls services trojans user watchlist Weekdays Weekend windows events Lookup Tables (continued) Description Lists the text strings that are often included in malicious URLs. Lists the services that are associated with each port number. Lists known Trojan horse exploits. Provides a table in which you can list users and the user names that formerly had access to the network. Lists the days of the week to allow further refinement of queries based on the day or days associated with an event. Lists the days of the weekend to allow further refinement of queries based on the day or days associated with an event. Lists the windows events that may indicate violations of security policies or other malicious activities. Note: Additional lookup tables can be downloaded into the system through LiveUpdates. To add an entry to the Organization Domains watchlist 1 On the Information Manager console, click Rules. 2 In the left navigation pane, expand the Lookup Tables folder. 3 Expand the System Lookup Tables folder. 4 Click Organization Domains. 5 Click New Record (+). 6 In the spaces provided, type a name and description. 7 Click Deploy to Server. 8 In the Deployed Modified Items dialog box, enter a comment which describes the addition of the entry and then click OK to deploy the change.

155 Defining rules strategy Working with the Lookup Tables window 155 To add an entry to the IP watchlist 1 On the Information Manager console, click Rules. 2 In the left navigation pane, expand the Lookup Tables folder. 3 Expand the System Lookup Tables folder. 4 Click ip watchlist (if it is not selected). 5 Click New Record (+). 6 In the spaces provided, type the desired IP address and description. 7 Click Deploy to Server. 8 In the Deployed Modified Items dialog box, enter a comment which describes the addition of the entry and then click OK to deploy the change. To add an entry to the sensitive files list 1 On the Information Manager console, click Rules. 2 In the left navigation pane, expand the Lookup Tables folder. 3 Expand the System Lookup Tables folder. 4 Click sensitive files. 5 Click New Record (+). 6 In the space that is provided, type the name of the file. 7 Click Deploy to Server. 8 In the Deployed Modified Items dialog box, enter a comment which describes the addition of the entry and then click OK to deploy the change. To add an entry to the sensitive urls list 1 On the Information Manager console, click Rules. 2 In the left navigation pane, expand the Lookup Tables folder. 3 Expand the System Lookup Tables folder. 4 Click sensitive urls. 5 Click New Record (+). 6 In the URL Substring column, type the URL. 7 In the Attack Type column, type the kind of attack that is associated with this URL. 8 Click Deploy to Server. 9 In the Deployed Modified Items dialog box, enter a comment which describes the addition of the entry and then click OK to deploy the change.

156 156 Defining rules strategy Working with the Lookup Tables window To add an entry to the services list 1 On the Information Manager console, click Rules. 2 In the left navigation pane, expand the Lookup Tables folder. 3 Expand the System Lookup Tables folder. 4 Click services. 5 Click New Record (+). 6 In the Service column, type a description. 7 In the Port column, type the port number to add. 8 Click Deploy to Server. 9 In the Deployed Modified Items dialog box, enter a comment which describes the addition of the entry and then click OK to deploy the change. To add an entry to the Trojan horses list 1 On the Information Manager console, click Rules. 2 In the left navigation pane, expand the Lookup Tables folder. 3 Expand the System Lookup Tables folder. 4 Click trojans. 5 Click New Record (+). 6 In the Port column, type the port number that is associated with the attack. 7 In the Protocol column, type the network protocol (such as TCP or UDP) that is associated with the attack. 8 In the Trojan Name(s) column, type the name of the Trojan horse. 9 Click Deploy to Server. 10 In the Deployed Modified Items dialog box, enter a comment which describes the addition of the entry and then click OK to deploy the change. To add an entry to the user watchlist 1 On the Information Manager console, click Rules. 2 In the left navigation pane, expand the Lookup Tables folder. 3 Expand the System Lookup Tables folder. 4 Click user watchlist. 5 Click New Record (+). 6 In the spaces provided, type the user name, name, and departure date of the employee or account to add.

157 Defining rules strategy Working with the Lookup Tables window Click Deploy to Server. 8 In the Deployed Modified Items dialog box, enter a comment which describes the addition of the entry and then click OK to deploy the change. To add an entry to the Windows Events list 1 On the Information Manager console, click Rules. 2 In the left navigation pane, expand the Lookup Tables folder. 3 Expand the System Lookup Tables folder. 4 Click windows events. 5 Click New Record (+). 6 In the ID column, type the desired Microsoft Windows event type. 7 In the Category column, type the kind of activity that is associated with the event. 8 In the Description column, type a description for this kind of event. 9 Click Deploy to Server. 10 In the Deployed Modified Items dialog box, enter a comment which describes the addition of the entry and then click OK to deploy the change. To delete an entry from the Lookup Tables 1 On the Information Manager console, click Rules. 2 In the left navigation pane, expand the Lookup Tables folder. 3 Expand the System Lookup Tables folder. 4 Click the table with the entry to be deleted and select the entry. 5 Click Delete Records. 6 Click Yes to confirm the deletion. 7 Click Deploy to Server. 8 In the Deployed Modified Items dialog box, enter a comment which describes the deletion of the entry. 9 Click OK to deploy the change. Creating a user-defined Lookup Table To create a user-defined lookup table, you first define the columns in the table, and then you add the data. See Working with the Lookup Tables window on page 152.

158 158 Defining rules strategy Working with the Lookup Tables window To create a user-defined lookup table 1 On the Information Manager console, click Rules. 2 In the left navigation pane, expand the User Lookup Tables folder. 3 Click Create new filter or rule (+). 4 In the Input dialog that appears, type the name of the table you want to create, and click OK. The name of the table must not match the name of an existing table or rule. 5 On the Content tab, click Add Records (+). Enter the Name, Type, and Description values for a column that you want to use in your table. You can select any of the following types of values for a record in a column: Float IP Mask Date String IP address Integer 6 For each additional column, repeat step 5. 7 After creating the columns, select the Key option button corresponding to the column that forms the primary column in the table. 8 Click Done. 9 To add data to the table that you have created, do one of the following: Click Add Records and enter the information in the available fields. Click Import Records. After you choose the file that you want to import, a wizard guides you through the steps to map the data that is stored in the file to the columns that you have added in the Lookup Table. 10 When you are finished, click Deploy. 11 In the Deploy Modified Items dialog box, choose the items that you want to deploy. You can enter an optional comment in the available field. 12 Click OK.

159 Defining rules strategy Working with the Lookup Tables window 159 Importing Lookup Tables and records You can import a previously exported Information Manager Lookup Table from a file. Alternatively, you can import the records that are stored in comma-separated or tabbed format into an existing Lookup Table. See Working with the Lookup Tables window on page 152. Note: When you import records into an existing Lookup Table, you can import a maximum of 1024 entries. To import an exported Lookup Table 1 On the Information Manager console, click Rules. 2 In the left navigation pane, click the User Lookup Tables folder. 3 Click Import from Disk. 4 In the Select File(s) to Import dialog, choose the file, and click Import. To import records into an existing Lookup Table 1 On the Information Manager console, click Rules. 2 In the left navigation pane, expand the User Lookup Tables folder. 3 In the table into which you want to import records, on the Content tab, click Import Records. 4 In the Open dialog box, choose the file that contains the data to be imported, and click Open. 5 In the Import Lookup Table Records wizard, choose the delimiter that is used in the file, and the appropriate options. The preview pane displays a representation of your choices. 6 Click Next. 7 In the next pane, use the Field Options area to specify how the data in the file maps to the columns in the Lookup Table. Click Next. 8 In the next pane, click Start. 9 When the import process is finished, click Finish.

160 160 Defining rules strategy Working with the Lookup Tables window

161 Section 4 Understanding event collectors Chapter 9. Introducing event collectors Chapter 10. Installing event collectors Chapter 11. Configuring point products and collectors Chapter 12. Configuring collectors for event filtering and aggregation

162 162

163 Chapter 9 Introducing event collectors This chapter includes the following topics: About Event Collectors and Information Manager Components of collectors About Event Collectors and Information Manager Security products and operating systems generate many kinds of events. Some events are informational, such as a user logging on, and others may indicate a security threat, such as antivirus software being disabled. Symantec Event Collectors gather, filter, and aggregate these events and forward both the raw and the processed events to Information Manager. See Components of collectors on page 164. Event Collectors collect information from security devices, critical applications, and services, such as the following product types: Firewalls Routers, switches, and VPNs Enterprise Antivirus Intrusion detection and intrusion prevention Vulnerability scanners Authentication servers Windows and UNIX system logs Information Manager stores the event data in event archives and correlates the events with threat and asset information. If a security event triggers a correlation rule, Information Manager creates a security incident.

164 164 Introducing event collectors Components of collectors Information Manager provides real-time event correlation and data archiving to protect against security threats and to preserve critical security data. For more details on event collectors, refer to Symantec Event Collectors Integration Guide. Components of collectors Event collectors gather, filter, and aggregate security events and forward both the raw and the processed events to Information Manager. See About Event Collectors and Information Manager on page 163. Table 9-1 Component Major components of collectors Description Information Manager Symantec Event Agent Collector Sensor Security or Point product Refers to the Symantec Security Information Manager where events are processed, filtered, and stored. Allows for the centralized collection, classification, and normalization of events to enable alerts and reports across managed security products. Refers to the Java application that performs the communication functions for the Information Manager components on the system on which it is installed. Refers to an application that collects events from security products, processes them, and passes them to the Agent. Refers to the component that reads events from a file, database, syslog, Windows event log, or other medium. The sensor then passes the events to the remaining collector components. The information is then delivered to the Agent to be sent to Information Manager. Refers to the software product, such as a firewall, antivirus software, or an operating system. The security product ensures that data is not vulnerable to unauthorized use or access and is the source of events to the collector. See About Event Collectors and Information Manager on page 163.

165 Chapter 10 Installing event collectors This chapter includes the following topics: Before you install collectors About installation and configuration tasks for collectors Registering Collectors Installing the Symantec Event Agent Installing the collector on a remote computer Installing collectors on an Information Manager server About Symantec Universal Collectors Downloading and installing the Symantec Universal Collectors Before you install collectors You must perform the following tasks before you install the collector: Meet requirements for both the point product and the collector. See Requirements for point products and the collectors on page 165. Update the hosts file. See Updating the hosts file on page 166. Run LiveUpdate before upgrading an earlier collector. Requirements for point products and the collectors Each collector is compatible with specific versions of a point product. Collectors can generally be installed on a variety of operating systems. Please refer to the specific collector guide to confirm compatibility with the operating system.

166 166 Installing event collectors Before you install collectors See Before you install collectors on page 165. In general, the following operating systems are supported: Microsoft Windows 2000 with Service Pack 4 or later Microsoft Windows Advanced Server 2000 with Service Pack 4 or later Microsoft Windows Server 2003 Enterprise Edition with Service Pack 1 or later Microsoft Windows Server 2003 Standard Edition with Service Pack 2 or later Windows XP with Service Pack 2 or later Red Hat Enterprise Linux AS 3.0 Red Hat Enterprise Linux AS 4.0 Red Hat Enterprise Linux AS 5.0 Sun Solaris (SPARC) 8.0, 9.0, and 10.0 Note: You can install version 4.3 collectors and later on both 32-bit and 64-bit versions of Windows Server 2000/2003. You can install version 4.2 collectors only on the 32-bit version of Windows Server 2000/2003. Minimum system requirements for a remote collector installation are as follows: Intel Pentium 133-MHz processor (up to and including Xeon processor), or SPARC IIIi or later 512-MB minimum; 1 GB of memory for the Symantec Event Agent 35 MB of available hard disk space for collector program files 95 MB of available hard disk space to accommodate the Symantec Event Agent, the JRE and the collector TCP/IP connection to a network from a static IP address Updating the hosts file The hosts file contains IP address and host name mapping information. You must manually update the hosts file if there is no fully-qualified domain name for the Information Manager server. You must also manually update the hosts file if you do not use a Domain Name System (DNS) server. You must add the IP address and host name information that is relevant to Information Manager and to the collectors that collect event data. Host names must be fully qualified domain names. See Before you install collectors on page 165.

167 Installing event collectors About installation and configuration tasks for collectors 167 To update the hosts file 1 Navigate to the directory of the hosts file as follows: On Windows, the hosts file is located in C:\WINDOWS\system32\drivers\etc folder. On UNIX, the hosts file is located in the /etc directory. 2 Use a text editor such as Notepad in Windows or vi on UNIX to open the hosts file. 3 Add the IP address and host name entries for the Information Manager server. Follow the instructions that are provided in the hosts file to add IP address and host name mapping information to the file. Use a tab between the IP address and host name. 4 After you have added the IP address and host name, save and close the file. You should ensure that the text editor that you use does not add a file extension. About installation and configuration tasks for collectors See About Event Collectors and Information Manager on page 163. Collector installation and configuration include the following major tasks: Preinstallation requirements Depending on the collector, a collector can run on various operating systems. See Requirements for point products and the collectors on page 165. You must manually update the hosts file if there is no fully qualified domain for the Information Manager server. See Updating the hosts file on page 166. Registration of the collector For all off-server collector installations, the Information Manager server requires you to register the collector for configuration settings and event schema. See Registering Collectors on page 170.

168 168 Installing event collectors About installation and configuration tasks for collectors Installation of the Symantec Event Agent You must install the Symantec Event Agent on the same computer as the collector computer. You should also verify Symantec Event Agent installation and operation. Installation of the collector component You must install the collector component to read data from the point product. You can install all collectors on a remote computer. You can install most collectors on the Information Manager server itself. However, universal collectors are installed by default on the Information Manager server. You do not need to install the universal collectors on the server. See Installing the collector on a remote computer on page 181. See Installing collectors on an Information Manager server on page 182. You should also verify collector installation. See Verifying collector installation on page 182. Configuration of the point product See About configuring a point product to work with a collector on page 189.

169 Installing event collectors About installation and configuration tasks for collectors 169 Configuration of the collector Depending on the collector, you can configure the collector in the following ways: Create and configure the sensor. See Creating and configuring sensors on page 190. You can enable the collector to collect the entire raw event message from the point product instead of the parsed fields. See Configuring collector raw event logging on page 195. Configure event filtering and aggregation. See Configuring event filtering on page 197. See Configuring event aggregation on page 200. You should also verify collector configuration. See Verifying collector configuration on page 184. The following installation and configuration tasks depend on various factors: A collector that uses a database sensor to collect events requires the completion of additional tasks. Before you use a database sensor collector, you must complete the various installation and configuration tasks that are related to the database that is used. A collector that uses a Syslog sensor to collect events can possibly use Syslog Director. Syslog Director accepts syslog events from any point product that is installed on the Information Manager server. You can configure a Logfile sensor to read logs from the log files. Agent service must have access to the file which will be read by the agent. Retrieval of support for new events and query updates. You can run LiveUpdate to receive collector updates such as support for new events and query updates. Deploying many collectors. If you need to configure many collectors at once, you can create a csv-formatted file.

170 170 Installing event collectors Registering Collectors Uninstallation of the collector and its components. You can uninstall the collector and its components. Registering Collectors The Information Manager Web configuration interface provides a page to register and to unregister the configuration settings and event schema. The Information Manager server requires these settings and schema to recognize and to log events from the point product. You must register the collector for all remote installations. If you use a collector that resides on the Information Manager server, you do not need to install the agent and you do not need to register the collector. To register a collector 1 Launch the Information Manager Web configuration interface at the following URL: Symantec recommends that you use the Fully Qualified Domain Name of the Information Manager. If you have the Information Manager Client console open, you should close it. 2 From the Information Manager Web configuration interface, click Settings > Collector Registration. 3 On the page that appears, click Register. 4 In the first box provided, type (or click Browse to select) the path to the collector_name.sip file that was provided with your collector installation package. You can select paths for up to 5 files. The default location for this file is the sip/ subdirectory of the collector installation package. 5 Click Begin Registration. Installing the Symantec Event Agent The Symantec Event Agent sends the data that the collector collects to the Information Manager server. The agent is always installed on the same computer as the collector component. In some cases, you may need to install agents on the

171 Installing event collectors Installing the Symantec Event Agent 171 Preinstallation requirements same computer as the security product is installed on for which it collects events. In other cases, you can install the collector on a separate computer from the security product for which it collects events. This computer must have network access to the Information Manager server. See About installation and configuration tasks for collectors on page 167. The prerequisites for installing the Symantec Event Agent 4.7 are as follows: The host name should be resolvable from the computer on which you want to install Symantec Event Agent 4.7. The installation process stops if any previous installations of the Event Agent are detected. You must uninstall all previous versions of the Event Agent to continue. See About installation and configuration tasks for collectors on page 167. About installing the Event Agent You can install the Event Agent on the following platforms: Windows See Installing the Event Agent on Windows on page 172. Solaris See Installing the Event Agent on Solaris on page 173. Linux See Installing the Event Agent on Linux on page 175. See About installation and configuration tasks for collectors on page 167. Before you install the Symantec Event Agent, you should complete the following steps in the order presented: Uninstall any previous version of the agent. Ensure that there is network connectivity between the system where the agent is installed and the Information Manager server. If there is a firewall between the agent computer and the Information Manager server, ensure that the following ports are open: Note: Using this port is a new option with Symantec Event Agent 4.7 and it is optional.

172 172 Installing event collectors Installing the Symantec Event Agent TCP 5998 TCP 443 TCP 80 When you complete the Symantec Event Agent operation, you can verify installation by doing the following: Verify Symantec Event Agent installation. See Verifying Symantec Event Agent installation on page 178. Verify Symantec Event Agent operation. See Verifying Symantec Event Agent operation on page 179. Installing the Event Agent on Windows To install the Event Agent on Windows 1 Download the installation file for Windows and the corresponding md5 file from the Download page of the Web configuration interface. 2 Verify the integrity of the downloaded installation file using the downloaded md5 file. 3 Click on the install.exe file to start the installation process and then click Next. 4 The Choose Install folder panel displays. The installation process stops if any previous installations are detected. You can continue only after the detected installation is removed. See About uninstalling the Event Agent on page Browse and select the destination folder for the installation files or retain the default folder and click Next. 6 Enter the IP address or host name of the Information Manager server when prompted. Ensure that you check the option box for Run Connection and communication tests during installation and then click Next. 7 The connection to the Information Manager server is checked. On a successful connection to the server, a Connectivity Test was successful message is displayed. In case the connection is not successful, check the connectivity and try again. Click Next to continue. The panel to install a third-party CA root certificate displays.

173 Installing event collectors Installing the Symantec Event Agent Click Next to continue. If you want to install a third-party CA root certificate, enable the option box for installing the third-party CA root certificate and then click Next. 9 Click the Choose option and browse to the folder that contains the certificate. A list of available certificates in that folder is displayed. 10 Select the required certificate and then click Next. The Pre-Installation Summary panel displays the product name, installation folder, the Information Manager server IP address and the disk space information. 11 Click Install. The Verify Agent communications panel displays. 12 Click Next to continue. The Install Complete panel displays with the installation folder. Installing the Event Agent on Solaris To install the Event Agent on Solaris 1 Connect to the Information Manager server using an account with administrative privileges either by using an SSH client or by logging on locally. You must log on as root to install the Event Agent. 2 Download the following files to the /tmp folder from the download links for Solaris Client. The download links are found on the download page of the thin client of the Information Manager server. symevtagent_solaris_r xx.md5sum symevtagent_solaris_r xx.tar.gz and xx should be replaced with the build number of the release. You must use binary mode when transferring the files to the Information Manager server. Some FTP utilities use ASCII mode by default, which corrupts the installation file. 3 Verify the integrity of the downloaded.tar file by using md5sum. Both the.md5sum and.gz files must be present in the same directory for md5sum to execute correctly. For more information on md5sum, see the man pages.

174 174 Installing event collectors Installing the Symantec Event Agent 4 To unpack the Event Agent 4.7 release, execute the commands: gunzip symevtagent_solaris_r xx.tar.gz tar -xvf symevtagent_solaris_r xx.tar xx should be replaced with the build number of the release. This command creates an Agent directory and unpacks the installation file to it. 5 Change directories to the Event Agent 4.7 release folder as shown: cd Agent 6 Execute the following commands: chmod + x install.sh./install.sh The installation process stops if any previous installations are detected. You can continue only after the detected installation is removed. See About uninstalling the Event Agent on page Enter the destination folder path or accept the default path to continue when prompted. 8 Enter the IP address or host name of the Information Manager server when prompted. The connection to the Information Manager server is checked and a message is displayed if the connection is successful. 9 If you want to install third-party CA root certificates, enter the path for the folder that contains the certificates when prompted.

175 Installing event collectors Installing the Symantec Event Agent 175 Installing the Event Agent on Linux To install the Event Agent on Linux 1 Connect to the Information Manager server using an account with administrative privileges either by using an SSH client or by logging on locally. You must log on as root to install the Event Agent. 2 Download the following files to the /tmp folder from the download links for Linux Client. The download links are found on download page of the Web configuration interface of the Information Manager. symevtagent_linux_r xx.tar.gz symevtagent_linux_r xx.md5sum and xx should be replaced with the build number of the release. Use binary mode to transfer the files to the Information Manager server. Some FTP utilities use ASCII mode by default, which corrupts the installation file. 3 Verify the integrity of the downloaded.tar file by using md5sum. Both the.md5sum and.gz files must be present in the same directory for md5sum to execute correctly. For more information on md5sum, see the man pages. 4 Unpack the Event Agent 4.7 release by executing the following command: gunzip symevtagent_linux_r xx.tar.gz tar -xvf symevtagent_linux_r xx.tar xx should be replaced with the build number of the release. This command creates an Agent directory and unpacks the installation file to it. 5 Change directories to the Event Agent 4.7 release folder by executing the following command: cd Agent 6 Execute the following command: sh install.sh The installation process stops if any previous installations are detected. You can continue only after the detected installation is removed. See About uninstalling the Event Agent on page Enter the destination folder path or accept the default path to continue when prompted.

176 176 Installing event collectors Installing the Symantec Event Agent 8 Enter the IP address or host name of the Information Manager server when prompted. The connection to the Information Manager server is checked and a message is displayed if the connection is successful. 9 If you want to install third-party CA root certificates, enter the path for the folder which contains the certificates when prompted. About uninstalling the Event Agent You can uninstall the Event Agent installation on Windows, Linux, or Solaris if required using the following options. Uninstalling the Event Agent on Windows See About uninstalling the Event Agent on Windows on page 176. Uninstalling the Event Agent on Linux and Solaris See About uninstalling the Event Agent on Linux and Solaris on page 176. About uninstalling the Event Agent on Windows Use one of the following methods to uninstall the Event Agent: Remove the Event Agent program through the Add or Remove Programs. This feature is applicable only for Symantec Event Agent 4.7 release. Note: Add or Remove Programs is known as Programs and Features in all the versions of Windows Execute the Uninstall Symantec Event Agent.exe file in the Event Agent folder. See About installation and configuration tasks for collectors on page 167. About uninstalling the Event Agent on Linux and Solaris If you want to uninstall the Event Agent, change to the Event Agent installation folder and run the install.sh script with the u switch as follows:./install.sh -u See About installation and configuration tasks for collectors on page 167. Event Agent Management with agentmgmt.bat utility Table 10-1 lists the options that are available when you run the agentmgmt.bat utility.

177 Installing event collectors Installing the Symantec Event Agent 177 See About installation and configuration tasks for collectors on page 167. Table 10-1 Option Option 1 Show Agent Status Option 2 Flush Agent Queue Options available with the agentmgmt.bat utility Information Shows the following information about the agent status: Port to which it is connected Connection status Number of events received Number of events sent Name of the server it is connected to Forces the agent to reconnect and send data to the server. If agent is in disconnected mode, then flushing the queue resets the agent to connected mode and send events to the server. Option 3 Reload Agent Configurations Option 4 Force Agent to send its Software Inventory and state Updates Option 5 View log files Option 6 Force Re-Bootstrap of Agent to same or to different server Option 7 Gather data for Technical Support Option 8 Reloads the agent configuration from the Information Manager server without restarting the agent Forces the agent to send information about software inventory and state updates to LDAP directory. Opens the log files to see using Swing based UI. Note: Selecting this option displays an error if UI is not supported on the Linux and Solaris terminal. Re-bootstraps the agent to the existing or to different server, used to reconnect to the same server or different server. Gathers the data such as logs, configurations which are added into a compress file named sesa-<hostname>-<guid>.zip. Changes the log level to debug. Enable or disable Collector Debug

178 178 Installing event collectors Installing the Symantec Event Agent Table 10-1 Option Option 9 Options available with the agentmgmt.bat utility (continued) Information Starts the agent. Start the Agent Option 10 Stops the agent. Stop the Agent Option 11 Quits the menu-based script file. Quit the menu Verifying Symantec Event Agent installation To verify installation of the Symantec Event Agent, you can perform the following tasks in the order presented: Verify Symantec Event Agent connectivity from Information Manager. Verify the Information Manager IP address and Symantec Event Agent port. See About installation and configuration tasks for collectors on page 167. To verify Symantec Event Agent connectivity from Information Manager 1 From a Windows computer that has the Information Manager Client installed, log on with an Information Manager user account with sufficient rights to view events. The Information Manager user must belong to a role that has rights to the Information Manager-integrated collector. 2 In the Information Manager console, in the left pane, click System. 3 On the Administration tab, expand the tree until you see Organizational Units. 4 Expand Organizational Units > Default. 5 Verify that the name of the collector computer is listed. 6 Right-click the computer name, and then click Properties. 7 In the Computer Properties dialog box, on the Services tab, verify that the Agent Service displays Yes in the Started column.

179 Installing event collectors Installing the Symantec Event Agent 179 To verify the Information Manager IP address and the Symantec Event Agent port 1 From the collector computer, navigate to the Symantec Event Agent installation folder. On Windows, the default location is C:\Program Files\Symantec\Event Agent On UNIX, the default location is /opt/symantec/sesa/agent On UNIX, you must become superuser. 2 In a text editor, such as Notepad on Windows or vi on UNIX, open the configprovider.cfg file. 3 Verify that the following options contain the correct settings for the collector product to which you want to send events: MgmtServer contains the correct Symantec Security Information Manager IP address. MgmtPort contains the correct Symantec Event Agent port number (default value is 443). Verifying Symantec Event Agent operation You can verify that the Symantec Event Agent is operating correctly by running the Show Agent Status script. To run the Show Agent Status script Symantec Event Agent operation 1 On the collector computer, navigate to the Agent directory as follows: On Windows, the default location is C:\Program Files\Symantec\Event Agent. On UNIX, the default location is /opt/symantec/sesa/agent. On UNIX, you must become superuser. 2 To access the Collector and Agent Management scripts, at the command prompt, do one of the following steps: On Windows, type the following command: agentmgmt.bat On UNIX, type the following command:./agentmgmt.sh 3 At the SSIM Collector / Agent Management Scripts menu, select the following option: 1. Show Agent Status If the Agent is not running, the following message appears:

180 180 Installing event collectors Installing the Symantec Event Agent The agent command cannot be executed. Failed to make a connection to the agent. The Symantec Event Agent is possibly not running. If the Agent is running, something similar to the following message appears: Symantec Event Agent (v ) - Copyright(c) - Symantec Corporation Symantec Event Agent status: running Listening on: :8086 SSL: Off SESA Manager URL: Outbound Thread State: CONNECTED Java Version Queue Status Total events accepted: 502 Total events forwarded: 502 Entries waiting in queue: 0 Direct events accepted: 0 Queue File:.\agent.que Flush Size (KB): 2000 Flush Count: 1000 Flush Time (sec): 4 Spool Size (KB): Max Queue Size (KB): Forwarding Provider: Symc_SESAEventForwardingProvider Post failures due to unexpected response code: 6 Total number of post failures: 0 Event Acceptor HTTP ThreadPool: Thread 0 state = IDLE Thread 1 state = IDLE Thread 2 state = IDLE Thread 3 state = IDLE Last state update time: Mon Apr 28 18:24:17 PDT 2008 Last configuration download request time: Mon Apr 28 18:24:17 PDT 2008 Last configuration update invocation time: Mon Apr 28 18:24:17 PDT 2008 Last configuration update completion time: Mon Apr 28 18:24:17 PDT 2008

181 Installing event collectors Installing the collector on a remote computer 181 Installing the collector on a remote computer The collector component reads the data from the security product, formats the data, and forwards it to the Symantec Event Agent. The collector computer must have access to the product to monitor. Before you install the collector component, you must complete the following tasks in the order shown: Register the collector. Refer the online Help on the Web configuration interface for more information on how to register the collectors. Install the Symantec Event Agent. Note: You must install the agent for all remote installations. If you use a collector that resides on the Information Manager server, you do not have to install the agent. See About installation and configuration tasks for collectors on page 167. When you have completed the installation of the collector on a remote computer, you should verify that the Symantec Event Agent and collector are running. See Verifying collector installation on page 182. To install the collector on a remote computer 1 On the collector computer, navigate to install subdirectory of the collector installation files. The installation files are located in a temporary directory. You must install some collectors on the same computer as the product for which it collects events. 2 At a command prompt, do one of the following steps: On Windows, type the following command: install.bat On UNIX, type the following command: sh./install.sh 3 Follow the installation wizard prompts. Symantec recommends that you run LiveUpdate at the end of the installation.

182 182 Installing event collectors Installing collectors on an Information Manager server Installing collectors on an Information Manager server If you install the collector on the server, you do not need to register the collector nor install the Symantec Event Agent. See About installation and configuration tasks for collectors on page 167. To install a collector on an Information Manager server 1 Unzip the installation package onto your Information Manager client computer. You can obtain the collector package from The installation package includes a subdirectory that is named server. The server subdirectory contains a file that is named as follows: install-collector_name collector.jar where collector_name represents the name of the collector. 2 On the Web configuration interface, click Maintenance > System Updates. 3 Click Install in the tree pane, and then browse to the server directory where you unzipped the installation package. 4 Select the install-collector_name collector.jar file and click Upload and Install. 5 On the Confirm Installation page, click Continue. The status of the install process is displayed. 6 When you have completed the steps required, close the Information Manager Web configuration interface. Verifying collector installation To verify the collector installation, you must complete the following procedures in the order presented: On the collector computer, verify that the appropriate services or daemons are started. On a Windows computer, you verify that services have started. On a UNIX computer, you verify that daemons have started. See To verify that the appropriate services have started on Windows on page 183. See To verify that the appropriate daemons have started on UNIX on page 183. Verify that the Symantec Event Agent and collector are running.

183 Installing event collectors Installing collectors on an Information Manager server 183 See To verify that the Symantec Event Agent and collector are running on page 183. To verify that the appropriate services have started on Windows 1 On the collector computer, on the Start menu, click Settings > Control Panel. 2 In the Control Panel window, select Administrative Tools. 3 In the Administrative Tools window, select Services. 4 In the Services dialog box, verify that the Symantec Event Agent Service is listed and is started. To verify that the appropriate daemons have started on UNIX 1 On the collector computer, log on as superuser. 2 At the command prompt, type the following command: ps -ef grep sesagentd 3 Verify that the sesagentd process exists. To verify that the Symantec Event Agent and collector are running 1 On the collector computer, navigate to the agent directory as follows: On Windows, the default location is C:\Program Files\Symantec\Event Agent On UNIX, the default location is /opt/symantec/sesa/agent On UNIX, you must become superuser. 2 To access the Collector and Agent Management scripts, on the command prompt, do one of the following: On Windows, type the following command: agentmgmt.bat On UNIX, type the following command:./agentmgmt.sh 3 On the SSIM Collector / Agent Management Scripts menu, select the following option: 1. Show Agent Status If the Agent is not running, the following message appears: The agent command cannot be executed. Failed to make a connection to the agent. The Symantec Event Agent is possibly not running. If the Agent is running, something similar to the following message appears:

184 184 Installing event collectors Installing collectors on an Information Manager server Symantec Event Agent (v ) - Copyright(c) Symantec Corporati Symantec Event Agent status: running Listening on: :8086 Sending on Port: SSL: Off SSIM Server URL: Outbound Thread State: CONNECTED Java Version 1.6.0_26 Queue Status Total events accepted: Total events forwarded: Entries waiting in queue: 0 Queue File:./QueueFiles/filequeue que Flush Size (KB): 2000 Flush Count: 512 Flush Time (sec): 4 Spool Size (KB): Max Queue Size (KB): HTTP forwarding statistics: Post failures due to HTTP response code 400: 12 Total number of HTTP post failures: 12 Event Acceptor HTTP ThreadPool: Thread 0 state = IDLE Thread 1 state = IDLE Thread 2 state = IDLE Thread 3 state = IDLE Last state update time: Mon Aug 29 16:11:49 IST 2011 Last configuration download request time: none Last configuration update invocation time: Tue Aug 30 07:59:36 IST 2011 Last configuration update completion time: Tue Aug 30 07:59:39 IST 2011 Verifying collector configuration You verify collector configuration by performing the following procedures in the order shown: View audit events. The audit events display whether or not a successful connection was made to the data source. You can view audit events again to troubleshoot a problem. See To view audit events on page 185.

185 Installing event collectors Installing collectors on an Information Manager server 185 Verify that the Symantec Event Agent and sensor are up. See To verify that the Symantec Event Agent and Sensor are up on page 185. To view audit events 1 On a Windows computer that has the Information Manager console installed, start the console. 2 Log on with an administrator account. 3 In the Information Manager console, in the left pane, click Events. 4 In the tree, click System Queries > SSIM > SSIM system > Audit events for SSIM. 5 In the right pane, check the name of the Information Manager server, and then click Run Query. 6 Check for the following entry in the Event Type ID column: Successful Connection to Data Source. The Severity ID for this type of event is 1 - Informational. 7 Right-click on rows with a Severity ID that is higher than 1, and click Event Details. The EventDetails window includes a more detailed description of the problem. Following is an example of an event with a Severity ID of 6: Report file rename failed. To verify that the Symantec Event Agent and Sensor are up 1 On a Windows computer that has the Information Manager Java client installed, start the client. 2 Log on with an administrator account. 3 In the Information Manager console, in the left pane, click System. 4 On the Visualizer tab, click Table View. 5 In the Statistics Viewer, locate the collector by the Product ID field, and the sensor and agent in the Type field. 6 In the Status field, check for the following entries: Agent Up Sensor Up If the Agent and Sensor are not up, the status field displays the following entry: Unknown

186 186 Installing event collectors About Symantec Universal Collectors About Symantec Universal Collectors Symantec provides universal collectors. These universal collectors gather, filter, and aggregate events from security devices, critical applications, and services. The collectors then forward both the raw and the processed events to Information Manager. Universal collectors are used in scenarios where standard options are not available. You can use the Custom Logs view on the Web configuration interface to map the log information to the fields that the Information Manager supports. Universal collectors are installed on an Information Manager by default. To install the universal collectors on an off-box system, you can download the following universal collectors from the Downloads option on the Home view of the Web configuration interface: Universal Collector for Windows Universal Collector for Windows Vista Universal Collector for Syslog Universal Collector for Log file See Downloading and installing the Symantec Universal Collectors on page 186. Downloading and installing the Symantec Universal Collectors To collect logs from a proprietary application, first download and install the universal collectors on the computer on which Symantec Event Agent is installed. See About Symantec Universal Collectors on page 186. To download the universal collectors 1 Log on to the Web configuration interface as an administrator. 2 In the Web configuration interface of Information Manager, click Home > Downloads. 3 Click the download link for the universal collector that you want to download. 4 Save the installation zip file for the universal collector on the computer where you want to install the collector.

187 Installing event collectors Downloading and installing the Symantec Universal Collectors 187 To install the universal collector on a remote computer that has Symantec Event Agent installed 1 On the computer on which Symantec Event Agent is installed, log on as administrator. 2 Unzip the installation package. The installation package includes a subdirectory that is named install. The installation files are located in a temporary directory. You must install some collectors on the same computer as the product for which it collects events. 3 On the command prompt, do one of the following: On Windows, type the following command: install.bat On UNIX, type the following command: sh./install.sh 4 Follow the installation wizard prompts. All the universal collectors are installed by default on the Information Manager server. The universal log file and syslog collectors are also installed by default on the Information Manager server.

188 188 Installing event collectors Downloading and installing the Symantec Universal Collectors

189 Chapter 11 Configuring point products and collectors This chapter includes the following topics: About configuring a point product to work with a collector Creating and configuring sensors Creating a new sensor configuration Configuring the collector sensor to receive security events Adding, renaming, deleting, and disabling sensors Importing and exporting sensor properties Updating sensor properties globally Configuring collector raw event logging About configuring a point product to work with a collector After you have installed the necessary collector components, you may need to configure the point product to make the event information available to the collector. For example, if the collector uses a syslog sensor, you must configure the point product to send syslog events to the collector. See Requirements for point products and the collectors on page 165.

190 190 Configuring point products and collectors Creating and configuring sensors Creating and configuring sensors You must create a new sensor configuration for each collector. See About configuring a point product to work with a collector on page 189. The creation of sensor configurations includes the following tasks: Creating a new sensor configuration. All collectors include a sensor configuration named Default that you cannot use. You must create a new one. See Creating a new sensor configuration on page 191. Configuring the collector sensor to receive security events. After you create a sensor configuration, you create and configure the sensor. Adding, renaming, deleting, and disabling sensors. See Configuring the collector sensor to receive security events on page 192. You can add, rename, delete, and disable sensors. Note: Avoid using the special characters such as <, &, and ' (single quotes) for sensor names. See Adding, renaming, deleting, and disabling sensors on page 193. Configuring sensor properties. Most collectors use one of the following sensor types, that you must configure: Syslog sensor Database sensor Log sensor Syslog file sensor Log file sensor Windows Event Log sensor OPSEC Lea sensor Importing and exporting sensor properties, optional. Some database sensor collectors are compatible with more than one type of database. An alternate sensor property file is provided for this purpose. See Importing and exporting sensor properties on page 193.

191 Configuring point products and collectors Creating a new sensor configuration 191 Globally updating sensor properties. If you have many sensors that are within the same configuration, you can update them all at once. See Updating sensor properties globally on page 194. See About installation and configuration tasks for collectors on page 167. Creating a new sensor configuration Collectors use the sensors that you configure to receive security events. The sensors are grouped according to the sensor configurations. The collectors include a sensor configuration named Default. You cannot use this configuration; you must create a new configuration. See Creating and configuring sensors on page 190. See Configuring the collector sensor to receive security events on page 192. Note: In case of custom logs, Administrators can create the sensor configuration through the Information Manager console only after the log type is added and the direct and the literal mappings are specified through the Custom Logs view in the Web configuration interface. Note: Avoid using the special characters such as <, &, and ' (single quotes) for sensor names. To effectively use the custom log management feature, you must maintain unique sensor names across different configurations for each universal collector type. To create a new sensor configuration 1 In the Information Manager console, in the left pane, click System. 2 From the Product Configurations tab, expand the tree until you see the collector name. 3 Right-click the collector name, and choose New. 4 On the Create a New Configuration wizard page, click Next. 5 On the General page, enter a name and a description for the new configuration, and click Next. 6 On the Computers page, do the following steps in the order given: Click Add.

192 192 Configuring point products and collectors Configuring the collector sensor to receive security events Under the Available computers column, click a system from the list, and click Add. In order for a computer to be listed, the Symantec Event Agent on that computer must be bootstrapped to the Information Manager Click OK, and then click Next. 7 On the Configuration summary panel, make changes to any of your previous selections. 8 Click Finish, and then click Close. Configuring the collector sensor to receive security events Before you configure a sensor, you must create a sensor configuration. See Creating a new sensor configuration on page 191. After you create a sensor configuration, you must configure its sensor or sensors to receive security events. After the sensors are configured, or when a change is made to sensor properties, the sensor properties are distributed to the collector computers. See Creating and configuring sensors on page 190. To configure the collector sensor to receive security events 1 In the Information Manager console, in the left pane, click System. 2 Select the Product Configurations tab, and then expand the tree until you see the collector name. 3 In the left pane, select the appropriate configuration. 4 In the right pane, on the Sensor tab, under the list of sensors, click the sensor. You can rename the sensor, add new sensors, and delete sensors. See Adding, renaming, deleting, and disabling sensors on page In the sensor property table under the Value column, change any of the information. 6 Click Save. 7 In the left pane, right-click the appropriate configuration, and then click Distribute. 8 When you are prompted to distribute the configuration, click Yes.

193 Configuring point products and collectors Adding, renaming, deleting, and disabling sensors 193 Adding, renaming, deleting, and disabling sensors When you create a new sensor configuration, a sensor is automatically created for you. You may create additional sensors, rename the sensor, delete the sensor, or disable the sensor. Note: Avoid using the special character <, &, and ' (single quote) for sensor names. See Creating a new sensor configuration on page 191. See Creating and configuring sensors on page 190. To add, rename, delete, or disable a sensor 1 In the Information Manager console, in the left pane, click System. 2 Select the Product Configurations tab, and then expand the tree until you see the collector name. 3 In the left pane, select the appropriate configuration. 4 In the right pane, select the sensor tab, and then, under the list of sensors, do one of the following: To add a sensor, click the + (plus sign) icon. By default, the sensors that you create are named Sensor 0, Sensor 1, Sensor 2, Sensor 3, and so on. To rename a sensor, double-click in the sensor name box, and type in a new name. To delete a sensor, click the - (minus sign) icon. You cannot delete the default sensor. You are required to have at least one sensor. To delete all sensors, click the trash can icon. To disable a sensor without deleting it, uncheck the sensor. 5 Click Save. 6 In the left pane, right-click the appropriate sensor, and then click Distribute to update the collector on the target computer with new properties. 7 When you are prompted to distribute the configuration, click Yes. Importing and exporting sensor properties Some database sensor collectors are compatible with more than one type of database. An alternate sensor property file is provided.

194 194 Configuring point products and collectors Updating sensor properties globally You can both import sensor properties from an XML file and export sensor properties to an XML file. See Creating and configuring sensors on page 190. To import and export sensor properties 1 In the Information Manager console, in the left pane, click System. 2 Select the Product Configurations tab, and then expand the tree until you see the collector name. 3 In the left pane, select the appropriate configuration. 4 In the right pane, on the sensor tab, do one of the following tasks: To import a configuration from an XML file, click the Import Sensors icon. Then, in the Import Configuration From File window that appears, specify the XML file from which you want to import the configuration. To export the selected configuration to an XML file, click the Export Sensors icon. Then, in the Export Configuration to File window that appears, specify a file name to which to export the configuration. Updating sensor properties globally You can copy the selected sensor properties to other sensors that are within the same configuration. You can use the Global Update function if you have many sensors that you need to update. See Configuring the collector sensor to receive security events on page 192. See Creating and configuring sensors on page 190. To globally update sensor properties 1 In the Information Manager console, in the left pane, click System. 2 Select the Product Configurations tab, and then expand the tree until you see the collector name. 3 In the left pane, select the appropriate configuration. 4 In the right pane, on the sensor tab, select a sensor so that it appears highlighted. 5 In the right pane, on the lower right, click Global Update. 6 In the Select Properties for Global Update window, place a checkmark next to the property whose value you want to propagate to all other sensors within the same configuration. 7 Click OK to complete the global update process.

195 Configuring point products and collectors Configuring collector raw event logging Proceed to change the sensor properties as needed. 9 In the left pane, right-click the configuration, and then click Distribute. 10 When you are prompted to distribute the configuration, click Yes. Configuring collector raw event logging You can enable the collector to collect the entire raw event message from the point product instead of the parsed fields. Raw event messages are useful for forensics, incident investigation, and log retention requirements. It also lets you preserve unaltered event messages. See About configuring a point product to work with a collector on page 189. Note: Raw event logging substantially increases event sizes.

196 196 Configuring point products and collectors Configuring collector raw event logging

197 Chapter 12 Configuring collectors for event filtering and aggregation This chapter includes the following topics: Configuring event filtering Configuring event aggregation Configuring event filtering You can use event filtering to exclude events from being forwarded to Information Manager. Event filters let you reduce the event traffic and the number of events that are stored in the event database. Filters also let you discard the data that is less important to your organization s security. You can also import and export filtering configurations. Filtering configurations are exported in an XML file format; you must use the same XML file format to import the configuration. Event filtering is not advisable for all collectors. The XML file for filtering should be in the following format: <?xml version="1.0" encoding="utf-8"?> <filter> <filter-spec enabled="false" index="0" name="specification 0"> <filter-field comparator="eq" name="queue_product_id">1</filter-field> </filter-spec> <filter-spec enabled="true" index="1" name="specification 1">

198 198 Configuring collectors for event filtering and aggregation Configuring event filtering <filter-field comparator="eq" name="server">33</filter-field> </filter-spec> </filter> Event filter configuration consists of the following actions: Adding and enabling the event filtering rules See To add and enable event filtering rules on page 198. Changing the existing event filtering rules See To change existing event filtering rules on page 199. Importing and exporting the event filtering rules See To import and export event filtering rules on page 200. Some collectors include predefined filtering rules. Some of these predefined filtering rules are also pre-enabled. To add and enable event filtering rules 1 In the Information Manager console, in the left pane, click System. 2 On the Product Configurations tab, in the middle pane, expand the tree until you reach the sensor configuration of a collector. 3 In the right pane, on the Filter tab, click Add. 4 Double-click Specification n (where n is 0, 1, 2, and so on), type a name for the rule, and click OK. 5 Under the rule properties table, click Add, and perform the following tasks in the order shown: In the Name column, type a name for the event filter property (for example, IP Destination Port). You can also double-click in the Name text box to bring up an Information Manager fields window. You can choose from the list of items that are presented in the expanded directories of the Information Manager fields window. In the Operator column, select an operator from the drop-down list (for example, equal to). In the Value column, type a value or select a preset value for the event filter property (for example, 80 for the port number). You can filter events by pattern by using a regular expression function. For example, to filter all events that contain "SUCCESS", enter the following in the Value column: regex(.*success.*)

199 Configuring collectors for event filtering and aggregation Configuring event filtering 199 Where all characters within the parentheses are part of the regular expression "." and "*" are both metacharacters "." matches any character "*" matches zero or more occurrences of the preceding element. Therefore, match zero or more occurrences of any character, followed by the literal string SUCCESS, followed by zero or more occurrences of any character. To rephrase, match the literal string SUCCESS anywhere within the field. 6 Repeat step 5 to add more event filtering information for the rule. All rules within a given specification use the Boolean AND to determine whether an event is a candidate for filtering. If there are multiple specifications, each specification uses the Boolean OR. 7 When you are finished adding information for the rule, in the filter list, check the filter name. 8 Click Save. 9 In the left pane, right-click the appropriate configuration, and then click Distribute. 10 When you are prompted to distribute the configuration, click Yes. 11 In the Configuration Viewer window, click Close. To change existing event filtering rules 1 In the Information Manager console, in the left pane, click System. 2 On the Product Configurations tab, in the middle pane, expand the tree until you reach a sensor configuration of a collector. 3 In the right pane, on the Filter tab, perform any of the following tasks: To add a specification, click Add. To delete a specification, select the specification, and then click Remove. To delete all specifications, click Remove All. 4 Perform any of the following tasks: To determine the order in which Information Manager invokes the event filters, next to the list of specifications, click the arrow icons. To change the name of the specification, double-click the specification in the specification list, and then, in the Name text box, type a new name. If you want to disable a specification, but you do not want to delete it, in the filter list, uncheck the filter name.

200 200 Configuring collectors for event filtering and aggregation Configuring event aggregation 5 In the rule properties table, change the information in any of the following columns: Name Operator Value 6 Under the rule properties table, perform any of the following tasks: To add a rule property, click Add. To delete a rule property, select the rule property, and click Remove. To delete all rule properties, click Remove All. 7 Click Save. 8 In the left pane, right-click the appropriate collector configuration, and then click Distribute. 9 When you are prompted to distribute the configuration, click Yes. 10 In the Configuration Viewer window, click Close. To import and export event filtering rules 1 In the Information Manager console, in the left pane, click System. 2 On the Product Configurations tab, in the middle pane, expand the tree until you reach a sensor configuration of a collector. 3 In the right pane, on the Filter tab, perform one of the following tasks: If you want to import, click Import configuration from XML file. If you want to export, click Export configuration to XML file. 4 Perform one of the following tasks: In the Import Configuration From File window that appears, specify the XML file to import into the collector. In the Export Configuration to File window that appears, specify a file name to export the configurations. Configuring event aggregation Collectors include a feature that lets you group similar events. By grouping events, you reduce event traffic and the number of events that are stored in the event datastore. The first event of a given type is sent to Symantec Security Information Manager immediately. All subsequent events of the same type are sent as one

201 Configuring collectors for event filtering and aggregation Configuring event aggregation 201 aggregated event. Aggregated events contain start and end times, but all other event fields are taken from the first event in the aggregated set. Not all collectors should use event aggregation. You can also import and export aggregation configurations. Aggregation configurations are exported in an XML file format; you must import configurations in the same XML file format. See About Event Collectors and Information Manager on page 163. The XML file for aggregation should be in the following format: <?xml version="1.0" encoding="utf-8"?> <aggregator maxbuffer="0"> <aggregator-spec enabled="true" index="0" name="specification 0" time="124"> <aggregator-fields> <aggregator-field name="display_id" operator="eq">15</aggregator-field> </aggregator-fields> <similarity-fields> <similarity-field name="data_scan_guid"/> </similarity-fields> </aggregator-spec> <aggregator-spec enabled="false" index="1" name="specification 1" time="234"> <aggregator-fields> <aggregator-field name="connection_type_name" operator="neq">1 </aggregator-field> </aggregator-fields> <similarity-fields/> </aggregator-spec> </aggregator> Event aggregation configuration includes the following actions: Adding and enabling event aggregation rules See To add and enable event aggregation rules on page 202. Changing existing event aggregation rule configurations See To change existing event aggregation rule configurations on page 202. Importing and exporting event aggregation rules See To import and export event aggregation rules on page 203. This feature is not advisable with all collectors. Event aggregation rules are not configured by default. You must add the rules before you can enable or configure them.

202 202 Configuring collectors for event filtering and aggregation Configuring event aggregation To add and enable event aggregation rules 1 In the Information Manager console, in the left pane, click System. 2 On the Product Configurations tab, in the middle pane, expand the tree until you reach the sensor configuration of a collector. 3 In the right pane, on the Aggregator tab, click Add. 4 Double-click Specification n (where n is 0, 1, 2, and so on), type a name for the rule. 5 Under the rule properties table, click Add, and perform the following tasks in the order shown: In the Name column, select or type a name for the event aggregation property (for example, Event Date). You can also double-click in the Name text box to open an Information Manager fields window. You can choose a name from the list of items that are presented in the expanded directories of the Information Manager fields window. In the Operator column, select an operator from the drop-down list (for example, greater than). In the Value column, type a value or select a preset value for the event aggregation property (for example, :18:31). 6 Repeat step 5 to add more event aggregation information for the rule. All rules within a given specification use the Boolean AND to determine whether or not an event is a candidate for aggregation. If there are multiple specifications, each specification uses the Boolean OR. 7 In the Aggregationtime(ms) text box, type the time in milliseconds by which a subsequent event should occur to be aggregated by this rule. The default value is 100. This property applies to all aggregation rules. 8 When you are finished adding information for the rule, in the aggregator list, check the aggregator name. 9 Click Save. 10 In the left pane, right-click the appropriate configuration, and click Distribute. 11 When you are prompted to distribute the configuration, click Yes. To change existing event aggregation rule configurations 1 In the Information Manager console, in the left pane, click System. 2 On the Product Configurations tab, in the middle pane, expand the tree until you reach a sensor configuration of a collector.

203 Configuring collectors for event filtering and aggregation Configuring event aggregation In the right pane, on the Aggregator tab, under the list of rules, perform any of the following tasks: To add a specification, click Add. To delete a specification, select the rule, and click Remove. To delete all specifications, click Remove All. 4 To determine the order in which Information Manager follows the event aggregation specifications, next to the list of specifications, click the arrow icons. 5 To change the name of the specification, double-click the specification in the specification list, and, in the Name box, type a new name. 6 To change the time by which a subsequent event should occur for aggregation by this rule, in the Aggregation time (ms) box, type the new time in milliseconds. The default value is 100. This property applies to all aggregation rules. 7 To disable a specification without deleting it, in the aggregator list, uncheck the aggregator name. 8 In the rule properties table, change information in any of the following columns: Name Operator Value 9 Under the rule properties table, perform any of the following tasks: To add a rule property, click Add. To delete a rule property, select the rule property, and click Remove. To delete all rule properties, click Remove All. 10 Click Save. 11 In the left pane, right-click the appropriate collector configuration, and click Distribute. 12 When you are prompted to distribute the configuration, click Yes. To import and export event aggregation rules 1 In the Information Manager console, in the left pane, click System. 2 On the Product Configurations tab, in the middle pane, and expand the tree until you see a sensor configuration of a collector.

204 204 Configuring collectors for event filtering and aggregation Configuring event aggregation 3 In the left pane, select the appropriate configuration. 4 In the right pane, on the Aggregator tab, perform one of the following tasks: If you want to import, click Import configuration from XML file. If you want to export, click Export configuration to XML file. 5 Perform one of the following tasks: If you want to import, in the Import Configuration From File window that appears, specify the XML file you want to import into the collector. If you want to export, in the Export Configuration to File window that appears, specify a file name to which to export the configurations.

205 Section 5 Working with events and event archives Chapter 13. Managing event archives Chapter 14. Forwarding events to an Information Manager server Chapter 15. Understanding event normalization Chapter 16. About Effects, Mechanisms, and Resources Chapter 17. Collector-based event filtering and aggregation Chapter 18. Working with the Assets table

206 206

207 Chapter 13 Managing event archives This chapter includes the following topics: About events, conclusions, and incidents About the Events view About the event lifecycle About event archives About multiple event archives Creating new event archives Restoring event archives Specifying event archive settings Creating a local copy of event archives on a network computer Viewing event data in the archives About working with event queries About events, conclusions, and incidents Security products and operating systems generate many kinds of events. Some events are informational, such as a user logging on, and others may indicate a security threat, such as antivirus software being disabled. A conclusion occurs when one or more events match a correlation rule pattern. Information Manager normalizes events from multiple security products and looks for the patterns that indicate potential threats. An incident is the result of one or more conclusions that are identified as a type of an attack. There can be many conclusions that are mapped to a single incident.

208 208 Managing event archives About the Events view For example, if a single attacker causes a number of different patterns to be matched; those are grouped into a single incident. Similarly, if a vulnerability scan uncovers a computer that suffers from a number of different vulnerabilities; these are all grouped into a single incident. Or, if a number of different computers report the same virus, Information Manager creates a single outbreak incident. About the Events view See About security products and devices on page 31. The Events view provides access to all of the event archives used by Information Manager server. Each archive stores events that are based on the Event Storage Rules that you configure on the System view. To view the events that are stored in any archive, you can do the following: Use the preconfigured query templates or system queries. The preconfigured templates and queries provide the parameters that you can set. You can choose the archive that you want to search, the time period within which you want to search for events, and so forth. Some templates and queries have more parameters than others depending on the purpose of the query. Save a copy of any preconfigured template query with the parameters that you have chosen, and customize the copy. Create a new query using the Query Wizard. Schedule queries to be distributed as CSV reports. When a template or query is run, the results are displayed in the results pane of the Events view. The results pane enables you to view and search for information about archived events in both graphical formats and text formats. You select the archive you want to research, and the viewer displays a histogram that represents the data that are stored in that archive. You can then narrow the display to a particular historical period (for example, the previous month or a specific one-hour period). You can display event details in a table and drill down to get all details about one event at a time. You can also filter the results in this view. See About events, conclusions, and incidents on page 207. About the event lifecycle Figure 13-1 shows the lifecycle of an Information Manager event.

209 Managing event archives About the event lifecycle 209 Figure 13-1 Event lifecycle Information Manager processes security event data in the following manner: The event collector collects the raw event data from the security product. The event collector normalizes the event data and filters and aggregates the events according to the event collector configuration settings. The agent sends the normalized events and if configured, the raw event data to the designated Information Manager. Information Manager stores the event in the event archive. Information Manager updates the event summary tables with the event information. Information Manager correlates the event, and, if the event triggers a correlation rule, creates an incident. Information Manager stores the incident in the incident database. Information Manager console users view incident and event reports. See About events, conclusions, and incidents on page 207.