Symantec Security Information Manager 4.8 User Guide

Transcription

1 Symantec Security Information Manager 4.8 User Guide

2 Symantec Security Information Manager User 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: 4.8 Legal Notice Copyright 2012 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 Symantec Security Information Manager Chapter 1 Overview About Symantec Security Information Manager About workflow in Information Manager About Information Manager components About security products and devices About event collectors About Information Manager servers About the Symantec DeepSight About the Information Manager Web service Chapter 2 Symantec Security Information Manager Console About the Information Manager console About the Dashboard view About the Intelligence view About the Incidents view About the Events view About the Tickets view About the Assets view About the Reports view About the Rules view About the System view About the Statistics view About the features of the Information Manager console About the incident and the alert monitors About the event activity monitor About the Notes feature Creating and editing notes Searching the notes... 61

8 8 Contents About user actions Creating and modifying user actions Opening the Information Manager console from the command line Changing a password Chapter 3 Symantec Security Information Manager Web configuration interface About the Information Manager Web interface Accessing the Web configuration interface About the features of the Web configuration interface Section 2 Planning for security management Chapter 4 Managing the correlation environment About the Correlation Manager About the Correlation Manager knowledge base About the default rules set Chapter 5 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 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

9 Contents 9 Creating a user-defined Lookup Table Importing Lookup Tables and records Section 3 Getting started with the Information Manager Chapter 6 Configuring the Console About configuring Information Manager Identifying critical systems Adding a policy Specifying networks About customizations for a Service Provider Master console Chapter 7 Managing roles and permissions About managing roles About the administrator roles About the default roles in the Information Manager server About planning for role creation Creating a role Editing role properties Deleting a role About working with permissions About permissions About the propagation of permissions Modifying permissions from the Permissions dialog box Chapter 8 Managing users and user groups About users and passwords Customizing the password policy 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

10 10 Contents About integrating Active Directory with the Information Manager server Managing Active Directory configurations Changing the password for Linux accounts Changing the password for symcmgmt Linux account Chapter 9 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 About modifying organizational unit permissions 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 Section 4 Understanding event collectors Chapter 10 Introducing event collectors About Event Collectors and Information Manager Collectors About Symantec Universal Collectors About Custom Log Management Downloading and installing the Symantec Universal Collectors Correlating the logs collected in a file from a proprietary application Chapter 11 Configuring collectors for event filtering and aggregation Configuring the event filtering rules Configuring event aggregation

11 Contents 11 Section 5 Working with events and event archives Chapter 12 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 Specifying event archive settings Creating a local copy of event archives on a network computer Restoring event archives 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 Using the Source View query and Target View query Creating query groups Querying across multiple archives Creating custom queries Editing queries Managing the color scheme that is used in query results About querying for IP addresses Importing queries Exporting queries Publishing queries Scheduling queries that can be distributed as reports Deleting queries Chapter 13 Forwarding events to the Information Manager Server About forwarding events to an Information Manager server About registering a security directory Registering Collectors Registering with a security domain

12 12 Contents Activating event forwarding Stopping event forwarding Chapter 14 Understanding event normalization About event normalization About normalization (.norm) files Chapter 15 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 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 Section 6 Working with incidents Chapter 16 Managing Incidents About incident management Incident identification Example: Information Manager automates incident management during a Blaster worm attack Threat containment, eradication, and recovery Follow-up Viewing incidents About the incident list Viewing and modifying the incident list About creating and modifying incidents Creating incidents manually Modifying incidents Merging incidents Closing an incident Reopening a closed incident

13 Contents 13 Printing incident details Printing the incident, ticket, or asset list Exporting the incident, ticket, or asset list Assigning incidents automatically to the least busy member in a user group Chapter 17 Working with filters in the Incidents view About filtering incidents Modifying a custom filter Creating a custom filter Deleting a custom filter Searching within incident filtering results Section 7 Working with tickets Chapter 18 Managing tickets About tickets About creating tickets Creating a ticket manually Creating a ticket category Viewing tickets About the Ticket Details window Viewing tickets associated with a specific incident Setting ticket task dispositions Changing the priority of a ticket Adding a ticket note Closing a ticket Printing the ticket list Chapter 19 Working with filters in Tickets view Filtering tickets Modifying a custom ticket filter Deleting a custom ticket filter Chapter 20 Working with Assets About the Assets view Importing assets into the Assets table

14 14 Contents Section 8 Working with reports and dashboards Chapter 21 Managing reports Working with reports About reports Creating custom reports Creating a report group or folder Editing tabular queries in reports Publishing reports Enabling the distribution of reports Scheduling and distributing reports Modifying the report distribution Viewing reports Configuring a report for portrait or landscape mode Printing and saving reports Exporting reports Importing reports Performing a drill-down on reports Chapter 22 Managing dashboards About the dashboard Viewing dashboards Viewing queries in the Dashboard Performing a drill-down on dashboards Refreshing the dashboard Customizing the dashboard Index

15 Section 1 Introducing Symantec Security Information Manager Chapter 1. Overview Chapter 2. Symantec Security Information Manager Console Chapter 3. Symantec Security Information Manager Web configuration interface

16 16

17 Chapter 1 Overview This chapter includes the following topics: About Symantec Security Information Manager About workflow in Information Manager About Information Manager components 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 Symantec DeepSight. 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: Information Manager provides the following features to help you recognize and respond to threats in your enterprise: Normalization of events from multiple vendors. 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.

18 18 Overview About workflow in Information Manager Real-time security intelligence updates from Symantec DeepSight. 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 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. 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 199. Events are filtered and aggregated. See Configuring the event filtering rules on page 207. See Configuring event aggregation on page 210. 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 251. See Activating event forwarding on page 256. The Information Manager server stores the event data in event archives. See About event archives on page 220.

19 Overview About Information Manager components 19 The Information Manager server correlates the events with threat and asset information based on the various correlation rules. See About the Correlation Manager on page 75. Information Manager security events trigger a correlation rule and create a security incident. See About incident management on page 285. About Information Manager components Symantec Security Information Manager has the following components: Security products and devices See About security products and devices on page 20. Symantec Event Agent Event collectors See About event collectors on page 20. Information Manager servers See About Information Manager servers on page 21. DeepSight See About the Symantec DeepSight on page 22. Web service See About the Information Manager Web service on page 22.

20 20 Overview About Information Manager components Figure 1-1 Components in an Information Manager setup 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 19. 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.

21 Overview About Information Manager components 21 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 For access to the extensive library of event collectors, visit Symantec support at the following Web site: See About Information Manager components on page 19. About Information Manager servers Information Manager server can be installed 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 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 19.

22 22 Overview About Information Manager components About the Symantec DeepSight Information Manager has access to current vulnerability, attack pattern, and threat resolution information from the Threat and Vulnerability Management Service. The Symantec DeepSight powers the Threat and Vulnerability Management Service. The Symantec DeepSight 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 19. 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 19. For more information on interfacing your application to use the Web service, see the application documentation or your application vendor.

23 Chapter 2 Symantec Security Information Manager Console This chapter includes the following topics: About the Information Manager console About the features of the Information Manager console About the Information Manager console You must install the Java client of the Information Manager on a Microsoft Windows, 2003, XP, Vista, Windows 2008 R2, or Windows 7 computer to access the console. The client can be downloaded from the Home > Downloads view of the Information Manager Web interface. The console of the Information Manager client enables you to perform the following security monitoring functions: Define rules to identify security incidents. Identify critical network hosts. View Symantec Global Intelligence Network information Manage incidents Manage tickets Create reports Connect Symantec Information Manager with Symantec Managed Security Services (MSS).

24 24 Symantec Security Information Manager Console About the Information Manager console MSS combines global threat intelligence, enterprise-wide monitoring, advanced analytics, and expert staff to provide 24x7 security monitoring and protection for enterprises from known and emerging threats. Perform Service Provider management tasks The console consists of the following views that help you manage the Information Manager Server: Dashboard view Intelligence view Incidents view Events view Tickets view Assets view Reports view Rules view System view Statistics view See About Information Manager components on page 19. About the Dashboard view The Dashboard view on the console of the Information Manager client provides a high-level view of the critical security information in your environment. Information Manager users can customize the dashboard to display the required event, ticket, and incident information. The Dashboard view provides an overview of the incident activity that is presented in the following default set of queries: Closed incident count for each assignee by priority Closed incident count for each assignee by severity Open incident count for each assignee by severity Open incident count for each assignee by priority Count of both open incident and closed incident by assignee Incidents count for each of the last seven days The toolbar of the Dashboard view presents the following options:

25 Symantec Security Information Manager Console About the Information Manager console 25 Refresh Turn Auto Refresh On Refreshes the queries Toggles the automatic refresh of the dashboard queries. When Auto Refresh is on, the dashboard queries are refreshed every five minutes, by default. Add Delete Lets you add a new query to the dashboard. Lets you remove a query from the dashboard. You can also remove the query by closing the query window. Tile Cascade Tiles the dashboard charts. Cascades the dashboard charts. About the Intelligence view See Viewing dashboards on page 344. See Customizing the dashboard on page 348. The Intelligence view displays the security information that the Symantec Global Intelligence Network gathers. 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. The Intelligence view provides information about the current ThreatCon level. It also provides advice and instructions on how to guard against and respond to the current threats. The Intelligence view presents detailed information under the following tabs: Analyst Watch IDS Statistics TheAnalystWatch tab provides information about IP addresses and URLs known to be involved in malicious activity. The IDSStatistics tab displays the five most frequently occurring intrusion detection events. It also lists offending ISPs, IP addresses, destination ports, attack products, and source and destination countries.

26 26 Symantec Security Information Manager Console About the Information Manager console Firewall Statistics AntiVirus Statistics Honeynet The Firewall Statistics tab displays the top five ports on the rise and lists offending ISPs, IP addresses, destination ports, and source and destination countries. The AntiVirus Statistics tab displays the five most frequent corporate and consumer virus sample submissions. The Honeynet tab displays up-to-date information from the Symantec Global Intelligence Network and data analysis of threats in the wild. Note: The features that appear on the Intelligence view may vary depending on the type of Global Intelligence Network services subscription that you have purchased. Contact your Symantec sales representative for more information. About the Incidents view See About the Information Manager console on page 23. The Incidents view lets you look at and manage Information Manager incidents. You can customize the Incidents view by selecting from the security filters or the alert filters or by creating your own custom filter. When you select an incident filter, the incident list displays only the incidents that satisfy the filter criteria. Selecting an incident in the list updates the incident pane with the detailed information for the selected incident. To update the incident, modify the incident attributes and click Save. To maximize or minimize the display area for the incident pane, click the expand and collapse arrows correspondingly in the upper-left corner. Double-clicking an incident in the list opens the Incident Details dialog box. To update the incident, modify the incident information and then click the Save icon. To export the incident details, click the Export icon. The incident details are exported to a CSV file that you can save to the desired location on your computer. To edit multiple incidents, highlight the incidents, and edit settings in the Details tab. From the Incidents view, you can perform the following tasks: Select a filter to apply to the Incidents view. The filters available for you depend on the roles to which you are assigned. The filters are grouped by Security Incidents, Alerts, and Custom filters in various states.

27 Symantec Security Information Manager Console About the Information Manager console 27 See Table 2-1 on page 27. Create a custom incident view filter. Search for an incident by incident Reference ID. Create a new incident. Open the Incident Details dialog box for the selected incident. Create a ticket for the selected incident or incidents. Export the incident list to a file. You can export the list in HTML, CSV, and XML format, as required. Merge the selected incidents. Close the selected incidents. You must provide the disposition (for example, normal, false-positive, resolved, duplicate, or merged) and provide notes when you close an incident. Lock the incident list. You can lock the incident list to prevent the display of newly created or recently assigned incidents in the list. When you unlock the list, it is updated with the latest incidents. Table 2-1 describes the Logical Groups for the filters. Table 2-1 My Incidents My Team Incidents All Incidents Logical Groups for filters The incidents that are assigned to the current user. Following are the states of this group of incidents: Open, New, In-Work, Waiting, and Closed. The incidents that are assigned to the current user's teams. Teams are created in the UserGroups section of the System view, on the Administration tab. Following are the states of this group of incidents: Open, New, In-Work, Waiting, and Closed. All incidents that have been created, both assigned and unassigned. Following are the states of this group of incidents: Open, New, In-Work, Waiting, and Closed. Unassigned Open Incidents My Alerts All incidents which are open and unassigned. The incident alerts assigned to the current user. Following are the states of this group of incidents: Open, New, In-Work, Waiting, and Closed.

28 28 Symantec Security Information Manager Console About the Information Manager console Table 2-1 My Team Alerts All Alerts Logical Groups for filters (continued) The incident alerts assigned to the current user's teams. Teams are created in the UserGroups section of the System view, on the Administration tab. Following are the states of this group of incident: Open, New, In-Work, Waiting, and Closed. All incident alerts that have been created, both assigned and unassigned. Following are the states of this group of incidents: Open, New, In-Work, Waiting, and Closed. Unassigned Open Alerts Custom Filters All incident alerts that are open and unassigned. All user-defined incident and alert filters. The Incidents view details pane contains tabs from which you can view or update the selected incident. Table 2-2 lists the details pane tabs and their functions. Table 2-2 Tab Details Conclusions Incident view details pane tabs Description Displays the incident details that include the ID, status, severity, description, creator, assignee, and priority. Displays the event conclusions that are associated with the incident. To view the details of a conclusion that is associated with the incident, select a conclusion and click the Conclusion Details icon. You can also select an event from the list and view the particular event details. Events Targets Sources Attack Diagram Displays the events that are associated with the incident. To view the details of an event that is associated with the incident, select the event and click the Event Details icon. Displays the target computers that are associated with the incident. To view the details for a target computer, select the target computer and click the Details icon. To create an asset from a target computer, select the target computer and click the Create Asset icon. Displays the source computers that are associated with the incident. To view details for a source computer, select the source computer and click the Details icon. Displays a visual representation of the progress of the attack that generated the incident along with the Symantec Event Code.

29 Symantec Security Information Manager Console About the Information Manager console 29 Table 2-2 Tab Intelligence Tickets Incident view details pane tabs (continued) Description Displays Symantec signature information, including the malicious code or vulnerability information that may be associated with the event. You can view the intelligence information that is organized by associated signatures or by target computers. Displays the tickets that have been created for the incident. To view the details of the tickets that are associated with the incident, select the ticket and click the Ticket Details icon. To create a ticket based on this incident, click the Create Ticket icon. When you create a ticket, the Create Ticket dialog box includes the following tabs: Details: Provides the fields that describe the characteristics of the ticket: A summary description, the priority, the ticket category, the creator of the ticket, the assignee of the ticket, and the related incidents. Instructions: Lets you correlate Intelligence data from the Global Intelligence Network with the ticket, if information is available. Tasks: Provides the fields to describe any additional remediation tasks that the creator of the ticket recommends. Note that the Tasks tab of the Create Ticket dialog differs from the steps that are listed in the Remediation tab for the incident. The Remediation tab contains the instructions that are automatically created when the incident is created, based on settings in the rule that triggered the incident. Remediation Log Displays the remediation suggestions that have been associated with the rule that triggered the incident. Remediation entries can be added to a rule on the Rules view. Displays the information that is available on the history of the incident. The incident history contains entries for incident creation, modifications, and closure. You can add entries to the log to record the information and the activities that are related to the incident. See About the Information Manager console on page 23. About the Events view The Events view lets you explore the Information Manager event archives. Event archives contain correlated and uncorrelated event data from the security products that are set up to forward events to Symantec Security Information Manager. You can create multiple event archives that can be stored on any instance of

30 30 Symantec Security Information Manager Console About the Information Manager console Information Manager. When you perform an event query, you can search across any available combination of archives, regardless of on which instance of Information Manager the archive is stored. The archives that are visible on the Events view are created with an ordered series of event storage rules. These rules are created on the System view. To view the events that are stored in the event archives, you can use templates and queries to search for events you need to view. Templates are generally more complex preconfigured queries that can be customized with chosen parameters. System queries are the queries that focus on specific products or common aspects of security management. When you run a template or a query, you set the parameters for the query, including which archives to search. Each template and query contains the parameters specific to data that the query harvests: for example, a specific IP address or a time range in which the search is to be conducted. After you run the query, the results are displayed in the right pane of the Events view. The presentation of data depends on each query, and can include graphs, pie charts, and lists of events. If a query returns a list of events, you can click on a particular event to see the event details. You can change table columns if you want to see different information about the events. You can view details about a particular event by double-clicking the table row. You can also filter data in the table so that it displays only the events that interest you. You can filter on a particular event parameter by right-clicking a cell and clicking Filter on cell. You can also filter results based on a unique column value. Alternatively, you can use the advanced filtering option to create a more complex query. You can also use the Query Builder Wizard to query the event archives. This wizard helps you create the following types of queries: Event queries Trending queries The trending feature is available only after you select the Event Query option. Summary queries Advanced SQL queries Note: The Query Builder Wizard icon is available only when the folder for My Queries or Published Queries is selected. Table 2-3 describes the items that are in the left pane of the Events view.

31 Symantec Security Information Manager Console About the Information Manager console 31 Table 2-3 Item Local Event Archives Templates Events view left pane items Description Access the static copies of the events that are archived and that are stored somewhere other than the Information Manager server. Local event archives are often created as a backup copy of an active archive. Local event archives are not updated after the copy of the archive has been made. Provides a set of preconfigured query templates that generally provide a system-wide view of event activity. The templates use the parameters you choose, such as the event archives or the time period from which the query gathers information. A template can be customized by placing a copy in either the My Queries or the Published Queries folder and then adjusting the copy. Access to the Template queries are controlled based on the roles. My Queries Displays a list of queries that you have created for your own use. You can move any of these queries into the Published Queries folder to make them available to others. PublishedQueries Displays a list of the queries that have been created at your site and that you want some or all of your users to be able to use. System Queries Displays a list of queries that are included in the Information Manager package. You can use any of these queries as a template for a customized query. To create a customized query, export the selected query as a QML file, and then copy or import the query in the My Queries folder or the Published Queries folder. You can modify it as required. About the Tickets view You can schedule queries to be distributed in a report as a CSV file. See About working with event queries on page 236. See Viewing event data in the archives on page 226. The Tickets view lets you view and manage Information Manager tickets. You can customize the ticket view by selecting from one of several ticket filters, or by creating a custom ticket filter. The filters that are available to you depend upon the roles to which you have been assigned. When you select a ticket filter, the ticket list displays only the tickets that satisfy the filter criteria.

32 32 Symantec Security Information Manager Console About the Information Manager console Selecting a ticket in the ticket list updates the ticket pane with the detailed information for the selected ticket. To update the ticket, modify the ticket attributes and click Apply. Double-clicking a ticket in the ticket list opens the Ticket Details dialog box. To update the ticket, modify the ticket information, and click Save or OK. You can edit multiple tickets simultaneously by opening a Ticket Details dialog box for each ticket to view or modify. The Tickets view toolbar contains icons for the following tasks: Select a filter to apply to the ticket view. The filters that are available to you depend upon the roles to which you are assigned, and may include one or more of the following: My Open Tickets My Closed Tickets All Open Tickets All Closed Tickets All Unassigned Tickets Lists the open tickets that are associated with the incidents assigned to the current user. Lists the closed tickets that are associated with the incidents assigned to the current user. Lists all the open tickets. Lists all the closed tickets. Lists all the unassigned tickets. Create a custom ticket view filter. Search for a ticket by ticket ID. Refresh the tickets view. Open the Ticket Details dialog box for the selected ticket. Export the list of tickets to a file. The ticket preview pane contains tabs from which you can view or update the selected ticket. Table 2-4 lists the preview pane tabs and their functions. Table 2-4 Ticket preview pane tabs Tab Details Description Displays the ticket details such as the ID, summary, category, status, priority, timestamp, creator, and help desk assignee.

33 Symantec Security Information Manager Console About the Information Manager console 33 Table 2-4 Tab Incidents Ticket preview pane tabs (continued) Description Displays the incidents that are associated with the ticket. To associate a new incident with a ticket, click the Add icon. To disassociate an incident from the ticket, select the incident and click the Remove icon. To view the incident details, click the Incident Details icon. To close the incident from the tickets view, select the incident and click the Close icon. Tasks Displays the user tasks that are assigned to each ticket. To add a new task to the ticket, click the Add icon. To remove a task from the ticket, select the task and click the Remove icon. To edit tasks, select the task and click the Edit icon. To add intelligence to the task, click the Intelligence icon. Instructions Displays the instructions that are associated with the ticket. To add or modify the instructions, edit the field and click Save. The instruction field accepts a maximum of 3000 characters. The Instructions tab also displays the Reset icon. You can also use the Add Intelligence to Instructions icon. Log Displays the ticket history that contains entries for ticket creation, ticket modifications, and ticket closure. To add log entries to record information and the activities that are related to the ticket, click the Add icon. See About the Information Manager console on page 23.

34 34 Symantec Security Information Manager Console About the Information Manager console About the Assets view The Assets view lets you view and manage Information Manager assets. Use the Assets view to identify critical assets in your environment, and track the incidents and the tickets that are related to those assets. Identify the network assets that have one or more of the following attributes: Host critical information or services Host confidential information Have specific roles on the network, such as firewall or vulnerability scanning devices Require high availability Comply with regulatory policies The correlation manager uses the asset information to identify and prioritize incidents. The correlation manager creates an incident when a threat exploits an asset's vulnerabilities. The correlation manager sets the incident priority based upon the confidentiality, integrity, and availability ratings that you assign to the asset. The correlation rules depend upon the asset information, so identifying key network assets on the Assets view is a critical configuration step. You can populate the list of assets in any of the following ways: Manually add entries in the Assets view. On the Incidents view, in the Targets tab for an incident, create assets based upon computers. On the Events view, under System Queries > SSIM > SSIM System, create assets from the query results of the Source view query and Target view query. On the Assets view, import a list of assets in XML or CSV format. For example, you can export a list of network computers from Microsoft Active Directory, convert the file to CSV format, and then import the file into the Information Manager. Create assets by integrating Information Manager with a policy compliance assessment tool, such as Symantec Control Compliance Suite or Symantec Enterprise Security Manager. Create assets by integrating Information Manager with a network vulnerability scanner. Use the Asset Detector rule under Monitor > System Monitors on the Rules view to choose the vulnerability scan products that automatically populate the assets table.

35 Symantec Security Information Manager Console About the Information Manager console 35 If you run vulnerability scans periodically on your network, lock the asset information for particular computers. If you lock an asset, the vulnerability scan does not modify the list of the services that are hosted on the asset. A vulnerability scan always updates the asset vulnerabilities, regardless of the asset lock status. You can filter the view of the assets in your environment using the filtering options or asset groups. Search for an asset from each of the views by entering the IP address host name in the Search Asset field, and then clicking the Search icon. Double-clicking an asset in the asset list opens the Asset Details dialog box. To update the asset, modify the asset fields and then click the Save icon. You can update multiple assets simultaneously by opening the Asset Editor dialog box for each asset to modify. Table 2-5 lists the Assets view tabs and their functions. Table 2-5 Tab Details Policies Services Incidents Tickets Assets view tabs Description Displays the network identification, description, priority, organization, operating system, and lock information for the selected asset. Displays any policy that is applied to the selected asset. You can add policies to an asset from a customizable list of regulatory policies. To customize the list of available policies, select the Administration tab on the System view. You can also delete policies from the asset. Displays the network services that the selected computer hosts. You can add services to an asset from a customizable list of well-known services. To customize the list of services, select the Administration tab on the System view. You can also delete services from the asset. Lists any incidents that pertain to the selected asset. Using the incident list is a convenient way to monitor the security activity that is related to an asset. Lists any tickets that pertain to the selected asset. The ticket list is a convenient way to monitor the work-order activity that is related to an asset.

36 36 Symantec Security Information Manager Console About the Information Manager console Table 2-5 Tab Vulnerabilities Assets view tabs (continued) Description Displays the discovery date, CVE ID, BugTraq ID, and description of any vulnerability that is discovered on the asset. The vulnerability information is tracked when the assets are imported from a vulnerability scanner. About the Reports view See About the Information Manager console on page 23. The Reports view lets you create and manage Information Manager reports. To create a report, you insert one or more queries into a report template. You can also add graphic elements and text, including a header and footer. Reports can span multiple views, or you can subdivide a single view and insert multiple queries on that view. You can distribute a report immediately, or you can schedule it to be generated at a specific time and then distributed automatically. You can also export and import reports in RML format. The Reports toolbar contains icons for report management tasks. The tasks available to you depend upon the roles to which you have been assigned, and may include one or more of the following: Refresh the Explorer pane. Create a folder. Create a report. Save a report. Remove the selected report or folder. Import a report from an RML format file. Export the selected report to an RML format file. Adjust the view settings for a report, including the view size and orientation. Publish the selected report by placing the report in the Published Reports folder. The Reports view has the following panes: Explorer The Explorer pane lets you manage the My Reports folder and the Published Reports folders, as well as any new folders that you create. When you create

37 Symantec Security Information Manager Console About the Information Manager console 37 a report in the My Reports folder, it is only available to the user who created it. When you create a report in the Published Reports folder, it is available to all of the users who have the applicable permissions for the contents of the report. To publish a report, drag it from your private folder to the Published Reports folder. When you publish a report by dragging it into the Published Reports folder, the two reports are not linked. In addition to creating, publishing, and deleting reports, you can create and delete report folders. You can also import reports, export reports, and move reports from one folder to another. Properties The Properties pane lets you view and edit the selected report property values, such as the background color or line thickness. Report The Report pane provides the tabs that let you design, preview, and distribute the selected report. Table 2-6 describes the tabs that appear in the right pane when you create a new report or select an existing report from the list in the left pane. Table 2-6 Tab Design Preview Report pane tabs Description Lets you specify and format the contents of your report. You can include multiple data queries, images, annotation text, and grids in your report. The queries that are available to you depend upon the roles to which you are assigned. For example, you may have access to queries that pertain to firewall and VPN data, but may not have access to queries on antivirus data. Displays a preview of the report. You can also save or print the report from the Preview tab. You can also drill down on the following query types by clicking on the reports that are displayed: Top N by Field Trending for Top N by Field Summary Data Queries See Performing a drill-down on reports on page 339.

38 38 Symantec Security Information Manager Console About the Information Manager console Table 2-6 Tab Distribute Report pane tabs (continued) Description Lets you schedule the report and specify report recipients. You can compose an report notification message, attach the report as a PDF and RTF, or include a URL link to the report. Note: When the recipient clicks on the URL link, the report can be accessed directly if the user has already logged on to the Web configuration interface using the host name of Information Manager. However if the user has logged on using the IP address of Information Manager, then the user is prompted for authentication to access the report. You can also test the report distribution configuration with the Test option. The reports are immediately distributed after you perform the testing. To schedule a report for distribution, you must first publish the report by placing it in the Published Reports folder. Note: The Distribute option is available only for the Published Reports. About the Rules view See About the Information Manager console on page 23. The Rules view lets you create, test, and manage the rules that Information Manager uses to filter known false positives and declare security incidents. Default rules provide a starting point for determining the most common kinds of security incidents, including denial-of-service attacks and blended threats. The default filtering rules provide a set of common filters that can also be used to create customized filters. You can enable, disable, and fine-tune the default rules and filters based on the needs of your organization and the security products that are running. The Rules view also includes folders for monitors and lookup tables. Monitoring rules are used to detect unexpected security-related changes to systems or periods of inactivity from the systems that are monitored. The lookup tables provide a set of tables that can be configured to list known malicious IP addresses, sensitive files, sensitive URLs, services, Trojan horses, and Windows events that can be used to fine-tune rules and filters. For example, if you have detected a set of IP addresses that routinely attempt to maliciously infiltrate your network, you can add these IP addresses to an IP address lookup table. You can then create a custom rule that checks the table for these known malicious IP addresses during rules processing.

39 Symantec Security Information Manager Console About the Information Manager console 39 When you define the actions that take place when an incident is triggered, you can create remediation notes. These notes appear on the Remediation tab for an incident that is created. When you add remediation information to a rule and save the changes, the remediation information is updated for the new and the existing incidents. The Rules view toolbar contains icons for the following tasks: Refresh the Rules list. Create a rule. Create a new folder. Delete a rule. Import rules Export rules Copy a rule. Deploy a rule. Revert changes to a rule. Enable rules. Disable rules. Each folder in the navigation tree includes two subfolders: a System subfolder and a User subfolder. By default, the System subfolder contains the predefined rules, filters, monitors, and lookup tables that are included with Information Manager. You can enable or disable the items in the System subfolders However, you cannot make changes to these predefined elements. To create a modified version of a preconfigured rule, filter, monitor, or lookup table, you can create a custom version of the rule and save it in the corresponding User folder. If you create a custom rule or lookup table, you must deploy and enable the new element before it can be used during event processing. Table 2-7 describes the items that are displayed in the Event Filters list in the left pane. It also describes the tabs that appear in the right pane when you make a selection from this list.

40 40 Symantec Security Information Manager Console About the Information Manager console Table 2-7 Item Event Filters list Conditions tab Testing tab History tab Event filters Description Displays the list of default filters in the System Filters folder and custom filtering rules in the User Filters folder. Use the checkboxes to turn on the rules and turn off the rules. Displays the event criteria that the filtering rules use to filter events. If you create a custom filter, you can add or remove event criteria from this pane. Lets you test filtering rules with saved event data so that you can evaluate whether the rule filters when it should. This tool helps you fine-tune a rule to filter out the events that cause false positives. You can also debug the errors that prevent the rule from filtering events. Shows the date and the time that a user last edited a rule. Table 2-8 describes the items that are displayed in the Monitors list in the left pane. It also describes the tabs that appear in the right pane when you make a selection from this list. Table 2-8 Category Monitors list Properties tab Actions tab Monitors Description Displays the list of default monitors in the System Monitors folder and custom monitors in the UserMonitors folder. Use the checkboxes to turn on the rules and turn off the rules Lists the monitor properties that let you configure the system monitors. Lets you specify the follow-up actions that are required to resolve the incident. You can also specify the user or the team that is assigned to investigate and resolve the incident. See About automatically assigning incidents on page 55. See Assigning incidents automatically to the least busy member in a user group on page 298. History tab Shows the date and time when a user last edited a monitoring rule. Table 2-9 describes the items that are displayed in the Correlation Rules list in the left pane. It also describes the tabs that appear in the right pane when you make a selection from this list.

41 Symantec Security Information Manager Console About the Information Manager console 41 Table 2-9 Category Rules list Conditions tab Actions tab Correlation rules Description Displays the list of default rules in the SystemRules folder and custom rules in the UserRules folder. Use the checkboxes to turn on the rules and turn off the rules. Displays the event criteria that the rules use to declare a security incident. If you create a custom rule, you can add or remove event criteria from this pane. Specify the follow-up actions that are required to resolve the incident. You can specify the user or the team that is assigned to investigate and resolve the incident. See About automatically assigning incidents on page 55. See Assigning incidents automatically to the least busy member in a user group on page 298. You can also create the remediation notes that are associated with each incident that this rule creates. You can also configure the notifications when the rule conditions are triggered. Testing tab History tab Lets you test rules with saved event data to let you evaluate whether the rule declares incidents when it should. This tool helps you fine-tune a rule to filter out the events that cause false positives. You can also debug the errors that prevent the rule from declaring incidents when it should. Shows the date and time when a user last edited a rule. Table 2-10 describes the items that are displayed in the Lookup Tables list in the left pane. It also describes each of the lookup tables that are listed under System Lookup Tables. Table 2-10 Lookup tables Tables Lookup Tables list Administrative Users Description Lists the default lookup tables in the System Lookup Tables folder and custom tables in the User Lookup Tables folder. Lists the users who can perform administrative activities.

42 42 Symantec Security Information Manager Console About the Information Manager console Table 2-10 Tables Lookup tables (continued) Description Authorized Ports Inbound Authorized Ports Outbound Critical Servers default usernames IP Watch List Lists the authorized ports through which incoming traffic is allowed as per the policies. Lists the authorized ports through which outgoing traffic is allowed as per the policies. Lists the IP addresses of the servers that are critical from business perspective. Lists the authorized users. Lists the IP addresses of known attackers. An incident is created if an event is detected from one of these IP addresses. 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 Monitored Logging Devices Organization Domains P2P Programs Potential Policy Violation IPs RapidResponseMonitoredAddressTraffic 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 that are monitored. Lists the P2P programs. Lists the IP addresses of the hosts that can potentially violate the policy. Lists of all of the bad IP addresses on which your sensitive data can communicate. Lists the file names to monitor during FTP transfers.

43 Symantec Security Information Manager Console About the Information Manager console 43 Table 2-10 Tables 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 the 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. The following tables list the event criteria available and their descriptions. Table 2-11 Field Agent Host Agent IP Agent Mac Agent Numeric IP Agent Subnet Event Criteria: Common tab Description The host name of the computer on which the agent is installed. The IP address of the computer on which the agent is installed. The MAC address of the computer on which the agent is installed. The numeric IP address of the computer on which the agent is installed. The subnet to which the agent computer belongs.

44 44 Symantec Security Information Manager Console About the Information Manager console Table 2-11 Field Category ID Event Criteria: Common tab (continued) Description Lets you select the criteria on category of the event from among Application, Communication, Device, Diagnostics, Environment, QS, and Security. Collection Device Host Collection Device IP Collection Device ID Collection Device Mac Collection Device Numeric IP Collector Sensor Configuration ID Created Date The host name of computer on which the product (collector) is installed. The IP address of computer on which the product (collector) is installed. The device ID of computer on which the product (collector) is installed. The MAC address of computer on which the product (collector) is installed. The numeric IP of computer on which the product (collector) is installed. Identifies the sensor that recorded the event that a collector sent. The ID of the configuration. The date that the event was created. Server Time - When the event occurs, the time zone of the server is considered for the event correlation. Source Network Time Zone - When the event occurs, the time zone of the source network is considered for the event correlation. Destination Network Time Zone - When the event occurs, the time zone of the destination network is considered for the event correlation. If the time zone is not specified, by default the time zone of the server is considered for the event correlation. The valid format to enter the date is mm/dd/yyyy. The valid format to enter the time is HH:MM[AM][PM]. CVSS Description Destination Host name The numeric value that describes the CVS score for the vulnerability, if detected. A description of the event. The destination host name.

45 Symantec Security Information Manager Console About the Information Manager console 45 Table 2-11 Field Device Action Domain Effects Event ending date Event Criteria: Common tab (continued) Description Describes the action that the point product took (the event was prevented, permitted, failed, successful, or denied ). The domain from which the data object originated. The effects of malicious activity. The date when event ended. Server Time - When the event occurs, the time zone of the server is considered for the event correlation. Source Network Time Zone - When the event occurs, the time zone of the source network is considered for the event correlation. Destination Network Time Zone - When the event occurs, the time zone of the destination network is considered for the event correlation. If the time zone is not specified, by default the time zone of the server is considered for the event correlation. The valid format to enter the date is mm/dd/yyyy. The valid format to enter the time is HH:MM[AM][PM]. Event Archive ID Event class ID Event Count The ID of the archive to which the event belongs (used in summarizers). The possible values: symc_hdr_tkt_update_class or symc_hdr_task_update_class. The number of times that an event occurred to cause the event to be logged.

46 46 Symantec Security Information Manager Console About the Information Manager console Table 2-11 Field Event Date Event Criteria: Common tab (continued) Description The date when the event occurred. Server Time - When the event occurs, the time zone of the server is considered for the event correlation. Source Network Time Zone - When the event occurs, the time zone of the source network is considered for the event correlation. Destination Network Time Zone - When the event occurs, the time zone of the destination network is considered for the event correlation. If the time zone is not specified, by default the time zone of the server is considered for the event correlation. The valid format to enter the date is mm/dd/yyyy. The valid format to enter the time is HH:MM[AM][PM]. Event Day The day when the event occurred. Server Time - When the event occurs, the time zone of the server is considered for the event correlation. Source Network Time Zone - When the event occurs, the time zone of the source network is considered for the event correlation. Destination Network Time Zone - When the event occurs, the time zone of the destination network is considered for the event correlation. If the time zone is not specified, by default the time zone of the server is considered for the event correlation. The valid format to enter the date is mm/dd/yyyy. The valid format to enter the time is HH:MM[AM][PM]. Event Type ID Host Domain IP Destination Address IP Destination Port IP Source Address IP Source Port The event type such as Host Intrusion Event, or Vulnerability Detected. The domain of the computer on which the product is installed. The IP address of the destination. The port of the destination or target. The IP address of the source. The port address of the source.

47 Symantec Security Information Manager Console About the Information Manager console 47 Table 2-11 Field Logged at Event Criteria: Common tab (continued) Description The location where the event was created. Server Time - When the event occurs, the time zone of the server is considered for the event correlation. Source Network Time Zone - When the event occurs the time zone of the Source Network is considered for the event correlation. Destination Network Time Zone - When the event occurs the time zone of the Destination Network is considered for the event correlation. If the time zone is not specified, by default the time zone of the server is considered for the event correlation. The valid format to enter the date is mm/dd/yyyy. The valid format to enter the time is HH:MM[AM][PM]. Logging Device IP Logging Device Mac Logging Device Name Logging Device Numeric IP Logging User Mechanisms Network Protocol Network Traffic Direction NumericIPDestinationAddress Numeric IP Source Address Organizational Unit The IP of the device that logged the event. The MAC of the device that logged the event. The name of the device that logged the event. The numeric IP of the device that logged the event. The account name that was used to log the event. The comma-separated integer values that represent the mechanisms categorization. Contains a normalized protocol value. This field is populated by the developer based on mapping the value of nw_protocol or network_protocol_id to a standardized protocol identifier such as TCP, UDP, ICMP, IGMP, or ARP. The direction of the network traffic such as external, internal, inbound, outbound, or unknown. The numeric IP of the destination address. The numeric IP of source address. The Information Manager organizational unit of the computer.

48 48 Symantec Security Information Manager Console About the Information Manager console Table 2-11 Field Event Criteria: Common tab (continued) Description Original Ending Event Date Original Event Date The data that the event ended if the event end date was replaced during normalization. The date that the event occurred if the event date was replaced during normalization Server Time - When the event occurs, the time zone of the server is considered for the event correlation. Source Network Time Zone - When the event occurs, the time zone of the source network is considered for the event correlation. Destination Network Time Zone - When the event occurs the time zone of the Destination Network is considered for the event correlation. If the time zone is not specified, by default the time zone of the server is considered for the event correlation. The valid format to enter the date is mm/dd/yyyy. The valid format to enter the time is HH:MM[AM][PM]. Point Product Version Posted at Product Raw Event Resources Severity ID Software Feature ID Source Host Name The version of the point product from which you collect logs. The timestamp that the agent sets before it sends the event to the event service. The name of the product from which you collect logs. The raw event as it is received from the logging device or application. The comma-separated integer values that represent the resources categorization. Severity of the event being reported. The value is in parentheses. The software feature ID as defined for the collector. Each collector must have at least one software feature that is defined for logging and configuration purposes. The host name of the source of the event. SSIM Event Insert

49 Symantec Security Information Manager Console About the Information Manager console 49 Table 2-11 Field Event Criteria: Common tab (continued) Description Symantec Event Code Symantec Vendor Signature ID Target Resource Time adjustment in seconds Unique Event ID User name Vendor Device ID Vendor Severity Vendor Signature Version A standard ID event code that Symantec has approved Information Manager use to report the associated event. The signature ID that is used to identify Symantec vendors. The target of the attack. This information can be the URL for an HTTP or an FTP connection, or a file name or server name. The number of seconds to adjust the event date that was logged on the agent when events are collected from another time zone. Unique ID assigned to each event. Contains the user name or group account of the user or group at which the event is targeted. The Global Intelligence Network cross-reference of the vendor product. This ID is a two-digit code that is only available in certified, Tier 1, and Premium collectors. The event severity identifier that the point product uses. Contains the unique event signature from the point product. This signature is used in retrieving data from the Global Intelligence Network integration. The version of the collector. Note: For an event criteria that involves an IP address you can enter either the IPv6 address or the IPv4 address. Table 2-12 Field Bugtraq ID List Events Criteria: Derived tab Description A security mailing list that includes a detailed discussion and announcement of computer security vulnerabilities,. The list describes what they are, how to exploit them, and how to fix them.

50 50 Symantec Security Information Manager Console About the Information Manager console Table 2-12 Field CVE ID List Events Criteria: Derived tab (continued) Description A publicly known list of information security vulnerabilities and exposures. Destination Host Availability Destination Host Bid List Destination Confidentiality Contains the Availability setting for the destination host at which the event was targeted. List of Bugtraq IDs that are known for the destination address (asset). Contains the Confidentiality setting for the destination host at which the event was targeted. The Confidentiality values include the following: 1 - Non-critical Medium Critical Destination CVE List Destination Host Integrity Destination Host is internal Destination Host Location Destination Host OS Destination Host OS Version Destination Host Policies Destination Host Services List of the common vulnerabilities and the exposures that are known for the destination address (asset). Contains the Integrity setting for the destination host at which the event was targeted. The Integrity values include the following: 1 - Non-critical, 2 and 3 - Medium, and 4 and 5 - Critical. The Boolean value that describes whether the destination host is internal. The string value that describes the destination host location. The string value that describes the destination host operating system. The string value that describes the operating system version. Contains the host policy for the destination host. Policies are added in the Systems view, under the Policies tab. Contains the destination host service that the event affected. Services are added in the Systems pane, under the Services tab.

51 Symantec Security Information Manager Console About the Information Manager console 51 Table 2-12 Field Events Criteria: Derived tab (continued) Description Destination is critical Destination Network Logical Location Destination Network Name Destination Network Physical Location Destination Port is open Effects Mechanisms Resources Source Host Availability Source Host Bid List Source Host Confidentiality Source Host CVE List The Boolean value that describes whether the target of the event has been categorized as critical. This value is set to True if the Asset exists in the Assets table. The string value that describes the logical location of the destination of the event (as opposed to the physical location). The string value that contains the descriptive name of the destination network. The string value that describes the physical location of the destination of the event. The Boolean value that describes whether the port that was affected is still open. The Effects values describe the effects of the event from the detector's point of view (for example, Degradation or Reconnaissance). The Mechanisms values describe the method of attack that was used to generate an event from the detector's point of view: for example, Virus or Port Sweep. The EMR resource value indicates the type or types of resources that the event is like to affect: for example, Mail or Host. Contains the Availability setting for the host from which the event originated. The Availability values include the following: 1 - Non-critical, 2 and 3 - Medium, and 4 and 5 - Critical. List of Bugtraq IDs that are known for source address (asset). Contains the Confidentiality setting for the host from which the event originated. The Confidentiality values include the following: 1 - Non-critical, 2 and 3 - Medium, and 4 and 5 - Critical List containing the Common Vulnerabilities and Exposures ID for the source.

52 52 Symantec Security Information Manager Console About the Information Manager console Table 2-12 Field Events Criteria: Derived tab (continued) Description Source Host Integrity Source Host is internal Source Host Location Source Host OS Source Host Policies Source Host Services Source Host is critical Source Network Logical Location Source Network Name Vulnerable Contains the Integrity setting for the host from which the event originated. This value is set in the Asset table by the user. The Availability values include the following: 1 - Non-critical, 2 and 3 - Medium, and 4 and 5 - Critical. Boolean value that describes whether the source host is internal. String value that describes the host location. This value is set in the Network table by the user. String value that describes the host operating system. This value is set in the Asset table by the user. Contains the host policy for the source. Policies are added in the Systems pane, under the Policies tab. For a rule to use this value, the policy must be added to the asset that is referenced as the source IP in the event. Contains the service that the event affected. Services are added in the Systems pane, under the Services tab. For a complete list of the services available, see the drop-down list for this event field. Boolean value that describes whether the source of the event has been categorized as critical. This value is set in the Asset table by the user. String value that describes the logical location of the source of the event (as opposed to the physical location). String value that contains the descriptive name of the source network. Value that determines whether the system that is specified in the Target IP field is listed as vulnerable in the Asset table. The possible values for this field include the following: True, False, and Can't Determine.

53 Symantec Security Information Manager Console About the Information Manager console 53 Table 2-13 Field Events Criteria: Events tab Description Application Update Audit Activity Backup and Recovery Activity Common Event Compliance Activity Configuration Update Data Incident Data Virus Incident Definition Update Firewall Connection Statistics Application update is used for indicating the status of updates in versions. Possible values are current version and previous version. Lets you set the type of audit activity that is carried out. Examples are Audit Authentication, Audit Result, and so forth. Lets you select the device type, session name, integrity marker, or any other additional information under options 1, 2, and 3. Lets you select and set a value for from the common event types such as those available under the Common tab.. Lets you set a value for the compliance events that are logged by software components to determine if they meet certain security criteria. Lets you enter values for configuration change source, name, and revision. Lets you set the values for classes and event IDs for logging an incident in a top-level data object or one of its subcomponents. The single event that describes the top-level data object, the subcomponent name (if applicable), the incident rule that was triggered, why the incident rule was triggered, and the status of the top-level data object and the subcomponent (if applicable). Lets you enter the values for quarantine server, definition number, QS, or type of a known virus, unknown virus, worm, Trojan horse, or other type of malware that the virus scanner detected. Lets you set the values for the version, date, and information of the current and the previous versions. Lets you set the values about the events that provide details about a connection, for reporting on byte counts, services used, and connection durations.

54 54 Symantec Security Information Manager Console About the Information Manager console Table 2-13 Field Events Criteria: Events tab (continued) Description Firewall Network Event Host Intrusion Activity Lets you set the values for the base set of the fields that allow common data to be logged by all firewalls in a consistent manner. Lets you set the values for the information fields that are specific to activity that is detected at the host. Incident Message Intrusion Activity Lets you set the values for the information that is common to the intrusion activity that is detected at both the network and the host levels. Network Event Network Intrusion Activity Lets you enter the values for type, MAC ID of source, and destination. SAV Catalog SAV Snapshots Scan Events System Information VPN Connection Statistics VPN Network Event Vulnerability Vulnerability Audit Vulnerability Audit Error Windows and Novell Event Lets you enter the values for scan name, type, and GUID. Lets you enter the information about the system. Lets you enter the values for VPN index and ID. Lets you set the type of VPN network event. Lets you set the values for the fields that are associated with vulnerability. Lets you set the values for the vulnerability audit ID or the human readable name of the audit. Lets you enter a description of the error. Lets you enter the values for the fields that are related to all of the events that the Windows and Novell event logs generate. See About the Information Manager console on page 23.

55 Symantec Security Information Manager Console About the Information Manager console 55 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 298. 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 2-14 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. Table 2-14 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

56 56 Symantec Security Information Manager Console About the Information Manager console About the System view The System view includes information about the Information Manager configuration, the security products that you manage, and the event management. The System view also lets you create and maintain the objects such as users, roles, and policies. Table 2-15 lists the System view tabs and their functions. Table 2-15 System view tabs Tab Administration Server Configurations Description Lets you view and maintain administrative information, such as user accounts and roles, policies, and paging services. Lets you manage correlation, whether events are stored locally, whether Information Manager agent bootstrapping is enabled, and whether the server is designated as a Service Provider master. You can also configure event storage rules, event forwarding, and incident forwarding. Further, you can enable log forwarding to Symantec Managed Security Services. Product Configurations Visualizer Displays a list of all the security products that can be managed on your network. Right-click a product name to view or modify its properties and permissions. Displays an illustration that represents your Information Manager network. Right-click an object in the graphic to view or modify the properties. See About the Information Manager console on page 23.

57 Symantec Security Information Manager Console About the Information Manager console 57 About the Statistics view The Statistics view provides information about the health and performance of the Information Manager server. You can display statistics for the server to which the console is connected. Alternatively, you can select to view the statistics for an alternate server that shares the same directory. Table 2-16 lists the Statistics view tabs and their functions. Table 2-16 Statistics view tabs Tab System Status Correlation Filters Rules Event Service Description Displays the server's memory and CPU utilization, database statistics, and the status of any database jobs, such as backup and purge. Displays the processing rate statistics for processes such as correlating events, declaring conclusions, and inserting incident data into the Information Manager database. Displays the filtering statistics for the correlation engine. You can monitor the Filter tab to determine how many events are excluded from the correlation engine. Displays trigger statistics for each correlation rule. You can monitor the Rules tab to confirm that rules are triggered as expected. Displays the rate statistics for the following event services: Events received Event normalization Event archiving Event correlation forwarding In the upper right corner of the console, a graph is displayed. The graph displays the events being processed per second by the server. You can always see the overall event activity from any view in the console. See About the Information Manager console on page 23.

58 58 Symantec Security Information Manager Console About the features of the Information Manager console About the features of the Information Manager console You can download and install the Java client for Information Manager from the Web configuration interface. The console of the Information Manager client lets you perform the following tasks: Monitor the incident or the alert count for either the current user or all users. See About the incident and the alert monitors on page 58. Monitor event activity. See About the event activity monitor on page 59. Attach a note to a column-and-value pair in tabular data. See Creating and editing notes on page 60. Search for the notes that you or other users have created. See Searching the notes on page 61. Change your password. See Changing a password on page 65. Execute a predefined set of user actions. See About user actions on page 63. Create new user actions and edit existing user actions. See Creating and modifying user actions on page 63. About the incident and the alert monitors The incident and the alert monitors display in real time the number of incidents or alerts as they are created. The incident and the alert monitors appear at the bottom of the Information Manager console. You can choose which count you want to monitor using the right-click menu. The right-click menu also provides shortcuts to view details. The incident monitor and the alert monitor offer the following options: View My Open Incidents View All Open Incidents View My Open Alerts Displays the Incident details for the open incidents for the current user. Displays the incident details for the open incidents for all users. Displays the incident details for the open alerts for the current user.

59 Symantec Security Information Manager Console About the features of the Information Manager console 59 View All Open Alerts Count My Open Incidents Count All Open Incidents Count My Open Alerts Count All Open Alerts Displays the incident details for the open alerts for all users. Displays the open incident count for the current user. Displays the open incident count for all users. Displays the open alert count for the current user. Displays the open alert count for all users. See About the features of the Information Manager console on page 58. About the event activity monitor The event activity monitor provides a real-time display of event activity. The display includes the option to view real-time event statistics, and a shortcut option to open a standalone event details dialog. The event activity monitor appears at the bottom of the Information Manager console. To configure the event activity monitor, right-click the monitor and choose from the available options. The event activity monitor options include the following: Open Details Panel Display Total Received Events Display Average Rate Display Rate Color options Select view type Opens the Statistics view in a standalone dialog box. Displays the total number of events that have been received. Displays the average event rate. Displays the actual event rate. Provides you with options to customize the color of the graph that displays. Lets you choose the visual representation of the event count as follows: Bar graph Line graph See About the features of the Information Manager console on page 58. About the Notes feature The Information Manager console includes the Notes feature. This feature lets you create the notes that you associate with data fields on the console views that display tabular data. For example, you can create notes to explain the meaning

60 60 Symantec Security Information Manager Console About the features of the Information Manager console of each incident severity level. You can later search for these notes, using several search criteria. The Notes feature is enabled on the following console views: Incidents Events Tickets Assets Creating and editing notes See About the features of the Information Manager console on page 58. When you create a note, you can attach it to a particular value in a table column. For example, in the Event details table, you can annotate the value Host Intrusion Event in the EventTypeID column. The note is then associated with each instance of that particular value in any table that includes the Event Type ID column. These notes provide additional reference information about any column-and-value pair. See About the Notes feature on page 59. To create or edit a note 1 In the Information Manager console, open the view where you want to create a note. You can create a note on any of the following views: Incidents Events Tickets Assets 2 In the displayed table, identify the column-and-value pair that you want to annotate. 3 Right-click a table cell that contains the desired value, and then click Notes. 4 In the Notes dialog box, take any of the following actions: To add a note, click Add. In the Add Comment dialog box, type the note, and click OK. To edit an existing note, select the note in the text area, and then click Edit. In the Edit Comment dialog box, revise the note, and click OK.

61 Symantec Security Information Manager Console About the features of the Information Manager console 61 To remove an existing note, select the note in the text area, and then click Remove. Click Yes to confirm your intention to remove the note. Searching the notes 5 When you finish adding and editing notes, click OK. If you added any notes, the table displays a red triangular flag in each cell that contains the value that you selected. The Search Notes feature lets you search for specific notes, using a variety of search criteria. To search for notes 1 In the Information Manager console, open any of these views: Incidents Events Tickets Assets 2 On the Tools menu, click Search Notes.

62 62 Symantec Security Information Manager Console About the features of the Information Manager console 3 Define the search criteria by using any of the following non-case-sensitive data fields: Category Value Author Note Text Start Date End Date Type or use the drop-down menu to select the column name to search on. Clicking the drop-down arrow displays a list of all table columns for which notes exist. You must select the exact column name. For example, selecting Severity yields different results than selecting Severity ID. Type the full text of the value from the annotated column-and-value pair. For example, if the value in the Severity ID column is 2 - Warning, you must type it exactly this way, including the space before and after the hyphen. Type the user name of the person who created the note: for example, Administrator. Type all or any portion of the note text. For example, to find the note This severity level is for informational messages only, you can type this severity or information or any other text string from the note. Use the default start date and time or change it by using the calendar icon. The Search Notes feature looks for the notes that were created on or after this date and time. Use the default end date and time or change it by using the calendar icon. The Search Notes feature looks for the notes that were created on or before this date and time. 4 Click Search. The bottom pane displays a list of the notes that meet the search criteria. A recently created note may not appear in the list because the server clock time is different from the client clock time. To remedy this situation, expand the time range by using the Start Date and End Date fields, and click Search again. 5 Take one of the following actions: To further narrow the search, type additional search criteria in the fields that are described in step 3, and click Search. You can also clear the search fields and type different search criteria. To access the dialog box where you can add, edit, and remove notes, select a note and click Comment Details. 6 When you click Comment Details, you can take of the following actions:

63 Symantec Security Information Manager Console About the features of the Information Manager console 63 To add a note, click Add. In the Add Comment dialog box, type the note, and click OK. To edit an existing note, select the note in the text area, and click Edit. In the Edit Comment dialog box, revise the note, and click OK. To remove an existing note, select the note in the text area, and click Remove. Click Yes to confirm your intention to remove the note. About user actions 7 When you finish adding and editing notes, click OK. If you have added any notes, the table now displays a red triangular flag in each cell that contains the value that you selected. 8 To finish, click Close. Information Manager includes several predefined user actions. These actions can help you find the information that is related to IP addresses and the host names that are included in some tabular data. If you right-click a cell that contains an IP address or a host name, you can select from one of the following options: Finger Ping Trace route Displays the information about a user on the specified computer. Note that the output varies based on the remote system; therefore, the command is of limited value. Sends a ping message to the computer and reports the reply in a command window. Traces a route to the host, but does not perform DNS lookups on the hops from host to host. Reports the results in a command window. User actions are available in any table that displays IP addresses or host names. User actions are available in the tables on the Assets view and on the queries on the dashboard that include this type of data. You can also modify the existing user actions and create your own user actions. See Creating and modifying user actions on page 63. Creating and modifying user actions You can create your own user actions, and you can customize the standard user actions. You can create and modify user actions by using the Events view or the Tools menu on the console view. See About user actions on page 63.

64 64 Symantec Security Information Manager Console About the features of the Information Manager console To create a user action 1 In the Information Manager console, click Events. 2 From the Tools menu, select Preferences. 3 Click + (the plus icon). 4 Type a name for the user action in the Name box and the command to be executed in the Command box. 5 Select one or both of the following options: To make the user action available to all users, select Public. To provide a command-line window in which to view the command output, select Use Output Viewer. 6 Click OK. 7 In the Preferences dialog box, click OK. The new user action now appears in the pop-up menu that appears when you right-click on a table cell. To modify a user action 1 In the Information Manager console, click Events. 2 From the Tools menu, select Preferences. 3 Select the user action that you want to modify, and then click the Edit icon. 4 You can modify any of the following: Change the user action name in the Name box. Change the command syntax in the Command box. Select Public to make the user action available to all users. Select Use Output Viewer if you want Information Manager to provide a command-line window in which to view the command output. 5 Click OK. 6 In the Preferences dialog box, click OK. The modified user action now appears in the pop-up menu when you right-click a table cell. Opening the Information Manager console from the command line You can open the Information Manager console using the command line. See About the Information Manager console on page 23.

65 Symantec Security Information Manager Console About the features of the Information Manager console 65 To open the Information Manager console from the command line 1 On the client computer, open the command-line interface. 2 Change the directory to the location in which the console was installed. For example: C:\Program Files\Symantec\Security Information Manager 3 Type the following command and press Enter, where [user] is the user name for the console and [password] is the password for that account. Do not include the brackets. >"Security Information Manager.exe" -user [user] -pw [password] -address autologin Changing a password You can use the Information Manager console to change your own password at any time. If the administrator has changed the password settings to a stronger authentication policy, you may be required to change your password. You can change your password by logging out and then logging back in to the console. See About the features of the Information Manager console on page 58. To change your password 1 In the Information Manager console, open any view. 2 On the Tools menu, click Change Password. 3 In the Change Password text box, type your current password. 4 Type a new password in the New password text box, and then type exactly the same characters in the Confirm new password text box. 5 Click Save. 6 Click OK.

66 66 Symantec Security Information Manager Console About the features of the Information Manager console

67 Chapter 3 Symantec Security Information Manager Web configuration interface This chapter includes the following topics: About the Information Manager Web interface Accessing the Web configuration interface About the features of the Web configuration interface About the Information Manager Web interface The Information Manager Web interface provides several control features to help you work with ease and efficiency. You can use an Internet browser to access the Information Manager Web interface. You can use the Information Manager Web interface to view security information and manage critical tasks on the Information Manager server remotely. See Accessing the Web configuration interface on page 68. The Information Manager Web interface lets you perform various tasks: Monitor the vital parameters and perform maintenance tasks. Configure the Information Manager server. View reports remotely. Download the report templates, universal collectors, and other utilities. Install the licenses for Information Manager and Symantec DeepSight.

68 68 Symantec Security Information Manager Web configuration interface Accessing the Web configuration interface Use the Custom Logs feature to correlate the information from the devices that Information Manager does not support. Accessing the Web configuration interface You can use a Web browser to access the Web configuration interface of the Information Manager server. The Web configuration interface lets you view security information and manage critical tasks on the Information Manager server remotely. See About the features of the Web configuration interface on page 68. To access the Web configuration interface of the Information Manager server 1 Open a Web browser, and in the address bar, type the IP address of the Information Manager server. For example: By default, the server uses self-signed certificates, which cannot be verified by certificate authentication services such as VeriSign. If you are prompted, click Yes to accept the server certificate. 2 Log on to the Web configuration interface using the administrator credentials that you created during the Symantec Security Information Manager installation. About the features of the Web configuration interface The Web configuration interface of the Information Manager server provides several control features to help you work with ease and efficiency. See About the Information Manager Web interface on page 67. The Web configuration interface provides the following control features: Status bar The status bar appears across the top of the Web configuration interface. The status bar displays the name of the Information Manager server to which the Web configuration interface is connected. The status bar also displays the role of the connected user.

69 Symantec Security Information Manager Web configuration interface About the features of the Web configuration interface 69 View bar The view bar contains links to the views that allow access to the options that are outlined under that view. The following main views are available in the console: Home Monitor Manage Settings Maintenance Navigation bar The navigation bar appears on the top across the console. The navigation bar displays the links to available views under the selected parent view. Tree pane The tree pane appears on the left side of the console window under the navigation bar. The tree pane displays a hierarchical, folder-based structure of the options available under the view. View indicator The view indicator appears across the top of the tree pane and the details pane. The view indicator displays the selected task in the hierarchical structure. Details pane Timestamp bar The details pane appears in the right side of the console window under the taskbar. This pane displays details about the selected option. The timestamp bar appears at the lower end across the console. The timestamp displays the date and timestamp for the generated page. The Web configuration interface provides the views that allow control of the features of the Information Manager server.??? describes the various tasks that you can perform from each view.

70 70 Symantec Security Information Manager Web configuration interface About the features of the Web configuration interface View Home Menu Items Todays Status Event Statistics Event Monitor Threat level Deepsight Top Corporate Threats Description Provides detailed information on the status of Incidents, Alerts, and Device health for the current day. Provides statistics that are related to security events. A graphical interface that provides information related to events that are obtained as input and on the DSX user interface. The Symantec Threat Level rating is a measurement of the global threat exposure, delivered as part of Symantec DeepSight Threat Management System. Symantec DeepSight Threat Management System provides actionable intelligence covering the complete threat life-cycle, from initial discovery, and disclosure of a vulnerability to active attack. With personalized notification triggers and expert analysis, the system enables enterprises to prioritize IT resources to better protect critical information assets against a potential attack. As the first early warning solution provider to deliver spyware and adware alert and warning information, Symantec also helps organizations mitigate and remove these security risks. Lists the top five corporate security threats. Monitor SSIM System Statistics Network Statistics Lets you monitor various SSIM services, the system statistics, and the network statistics.

71 Symantec Security Information Manager Web configuration interface About the features of the Web configuration interface 71 View Manage Menu Items Reports Description Lets you view and download the standard reports that are scheduled on the Information Manager Server. You can view the Scheduled Query Reports on this view. Settings Deepsight Database Lets you configure the Information Manager Server. Directory Registration Collector Registration Custom Logs Active Directory External Storage. Maintenance Backup and Restore Incident Synchronization LiveUpdate Lets you perform various maintenance tasks such as LiveUpdate, Backup and Restore and purge on the Information Manager database. System Update

72 72 Symantec Security Information Manager Web configuration interface About the features of the Web configuration interface View System Menu Items Administration Certificate Downloads Managed Security Services Date Time Network Password Description Lets you start or shut down the Information Manager Server remotely. Lets you manage the licenses for the Information Manager server. Lets you manage certificates for the Information Manager. Lets you download the installers for Symantec Event Agent and the Information Manager client. You can also download the log files, Universal collectors, and other utilities. Lets you register Symantec Security Information Manager with Symantec Security Operations Center to forward security events. Lets you change the date and time of the Information Manager Server Lets you change the network card settings for all the network cards that are installed on the Information Manager server. Lets you edit the Hosts File on the Information Manager server. Lets you change the password of Linux accounts on server. Lets you set the password policy for the system. Note: The Web configuration interface does not support the use of Back and Refresh browser options. Using these options may produce unpredictable results.

73 Section 2 Planning for security management Chapter 4. Managing the correlation environment Chapter 5. Defining rules strategy

74 74

75 Chapter 4 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 76. 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 76.

76 76 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 75. 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 75. See About the Correlation Manager knowledge base on page 76. Table 4-1 lists the default rules and the types of security products with which they are usually associated.

77 Managing the correlation environment About the default rules set 77 Table 4-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

78 78 Managing the correlation environment About the default rules set Table 4-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

79 Managing the correlation environment About the default rules set 79 Table 4-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

80 80 Managing the correlation environment About the default rules set Table 4-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

81 Chapter 5 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 83. The customizations usually belong to one of the following categories:

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

83 Defining rules strategy About defining a rules strategy 83 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 81. 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 81. 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:

84 84 Defining rules strategy About rule conditions Rule type Identifies the pattern that best describes the event. See About rule types on page 85. 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 89. 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 83.

85 Defining rules strategy About rule conditions 85 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 84. 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 5-1 describes the rule types that are available and provides examples. Table 5-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

86 86 Defining rules strategy About rule conditions Table 5-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

87 Defining rules strategy About rule conditions 87 Table 5-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

88 88 Defining rules strategy About rule conditions Table 5-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.

89 Defining rules strategy About rule conditions 89 Table 5-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 84. Table 5-2 describes the tabs available in the drop-down list. Table 5-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.

90 90 Defining rules strategy About rule conditions Table 5-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 5-3 describes the decision option operators available. Note: The available operators vary with each criteria type. Table 5-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.

91 Defining rules strategy About rule conditions 91 Table 5-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.

92 92 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 83. Table 5-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 5-5 describes the Tracking Key fields on the Conditions tab.

93 Defining rules strategy About the Tracking Key and Conclusion Creation fields 93 Table 5-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 5-6 describes the Conclusion Creation fields on the Actions tab. Table 5-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.

94 94 Defining rules strategy About the Correlate By and Resource fields Table 5-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 83. 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 5-7 describes the Correlation types available in the Correlate By field. Table 5-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.

95 Defining rules strategy Importing existing rules 95 Table 5-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 83. 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.

96 96 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 81. You can create correlation rules from the Rules view of the console of the Information Manager client. See About correlation rules on page 83. 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 97. Configure rule condition. See To configure the rule conditions on page 97. Configure the rule action. See To configure the rule actions on page 98. Deploy the rule on the server. See To deploy the rule on the server on page 100.

97 Defining rules strategy Creating custom correlation rules 97 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 100. 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.

98 98 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. In case you specify a higher value of time in hours, the hours gets automatically rounded to 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 105. 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 Insert 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.

99 Defining rules strategy Creating custom correlation rules 99 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. 5 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, select IP Address or Network options from the Criteria column. Type an IPv4 or IPv6 address. 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.

100 100 Defining rules strategy Creating custom correlation rules 10 Type the subject of the in the Subject area. (Optional) Click Insert to include any of available fields in the subject. When the notification is sent these fields are replaced with their corresponding values. 11 Type the message in the Body area. (Optional) Click Insert to include any of the available fields in the message. When the notification is sent these fields are replaced with their corresponding values. After you specify the condition and the action, you can test the rule and then deploy it on the server. 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 112. 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 84. 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.

101 Defining rules strategy Creating custom correlation rules 101 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. 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. 3 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. This specification determines the number of events that must occur within the timeframe that is specified in the Span settings for the rule to trigger an incident. 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.

102 102 Defining rules strategy Creating custom correlation rules 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. This specification determines the number of events that must occur within the timeframe that is specified in the Span settings for the rule to trigger an incident. 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. This specification determines the number of events that must occur within the timeframe that is specified in the Span settings for the rule to trigger an incident. 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. 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. This specification determines the number of events that must occur within the timeframe that is specified in the Span settings for the rule to trigger an incident.

103 Defining rules strategy Creating custom correlation rules In Span, set the time span equal to 20 minutes. In case you specify a higher value of time in hours, the hours gets automatically rounded to In Table Size, specify the maximum number of events that the rule can track at any one time. Note: The Strict check box works only in three or more condition rules. It resets the collected sequence of events if an unexpected (in proper order) strict event is received. After you configure the rule conditions you must configure the rule actions. 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 Insert to include the values of 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. 5 In the Correlate By drop-down list, specify 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:

104 104 Defining rules strategy Creating custom correlation rules 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, select IP Address or Network options from the Criteria column. Type an IPv4 or IPv6 address. 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. 8 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. 10 Type the subject of the in the Subject area. (Optional) Click Insert to include any of available fields in the subject. When the notification is sent these fields are replaced with their corresponding values. 11 Type the message in the Body area. (Optional) Click Insert to include any of the available fields in the message. When the notification is sent these fields are replaced with their corresponding values. After you specify the conditions and the actions, you can test the rule and then deploy it on the server.

105 Defining rules strategy Creating custom correlation rules 105 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 85. 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. 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.

106 106 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 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 Auto assignments you can specify whether the incident should be assigned automatically to the users or groups selected. 15 In the Notification area, you can enable the notifications and specify the details of the notification. You can add one or more recipients to receive the notifications and edit the subject and the body of the notification. 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 that you want to deploy. 3 In the top toolbar, click Deploy.

107 Defining rules strategy Creating custom correlation rules 107 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 84. 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. 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.

108 108 Defining rules strategy Creating custom correlation rules 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, specify whether the incident should be assigned automatically to the users or groups selected. 15 In the Notification area, you can enable the notifications and specify the details of the notification. You can add one or more recipients to receive the notifications and edit the subject and the body of the notification. 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 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.

109 Defining rules strategy Creating custom correlation rules 109 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 =. 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.

110 110 Defining rules strategy Creating custom correlation rules 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 Auto assignments you can specify whether the incident should be assigned automatically to the users or groups selected. 15 In the Notification area, you can enable the notifications and specify the details of the notification. You can add one or more recipients to receive the notifications and edit the subject and the body of the notification. 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 85. 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.

111 Defining rules strategy Creating custom correlation rules 111 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. After configuring the rule conditions, you must enable and deploy the rule.

112 112 Defining rules strategy Enabling and disabling rules 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 83. 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 83. 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 5-8 lists the Lookup Tables and the types of information that they contain.

113 Defining rules strategy Working with the Lookup Tables window 113 Table 5-8 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.

114 114 Defining rules strategy Working with the Lookup Tables window Table 5-8 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.

115 Defining rules strategy Working with the Lookup Tables window 115 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.

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

117 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 112.

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

119 Defining rules strategy Working with the Lookup Tables window 119 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 112. 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.

120 120 Defining rules strategy Working with the Lookup Tables window

121 Section 3 Getting started with the Information Manager Chapter 6. Configuring the Console Chapter 7. Managing roles and permissions Chapter 8. Managing users and user groups Chapter 9. Managing organizational units and computers

122 122

123 Chapter 6 Configuring the Console This chapter includes the following topics: About configuring Information Manager Identifying critical systems Adding a policy Specifying networks About customizations for a Service Provider Master console About configuring Information Manager For the correlation rules to function properly, it is essential that you specify the information that is used to determine incident severity. Key settings include specifying the systems that host critical or sensitive information and the systems that require high availability. You can also specify the networks that exist in your organization so that you can increase the priority of incidents based on the affected network. For example, the incidents that affect the networks that reside within your firewall can be assigned a higher priority than those that reside outside the firewall. See Identifying critical systems on page 124. You can specify the policies that are used within your network. Symantec Security Information Manager includes default policies. You can also add custom policies. Once you have defined the available policies, you can associate them with network computers when you add entries to the Assets list. See Adding a policy on page 126. See Specifying networks on page 126.

124 124 Configuring the Console Identifying critical systems You should also create your list of response teams so that Information Manager can automatically assign incidents to these teams based on the rules settings. You use the Information Manager console to create the teams. However, the list of members that you can assign to those teams is maintained on the System view. Another key factor that lets you determine incident severity and the functioning of rules is the information that is stored in the knowledge base. The Global Intelligence Network Integration Manager provides some of this information. You can configure some settings. For example, you can add entries to the IP watchlist. See About customizations for a Service Provider Master console on page 127. Note: When you add a new policy or service to the Policies or Services lists, the new entries appear in the Event Criteria on the Rules view after you restart the console for the Information Manager. Identifying critical systems For the correlation rules to function properly, you must specify the information that is used to determine incident severity. Key settings include specifying the systems that host critical or sensitive information and the systems that require high availability. See About configuring Information Manager on page 123. Complete the following steps to identify critical systems in your organization. To identify critical systems 1 In Information Manager console, click Assets. 2 On the toolbar, click + (the plus icon). 3 In the Asset Editor dialog box, enter the IP address details in any one of the following fields. IPv4 If the system has an IPv4 address, specify the address here. IPv6 (1) If the system has an IPv6 address, specify the address here. IPv6 (2) If the system has an alternate IPv6 address, specify the address here. 4 Fill in the following optional information, if you want: In the Host Name box, type the host name of the system.

125 Configuring the Console Identifying critical systems 125 In the MAC Address box, type the MAC address of the system. In the DN box, type the Distinguished Name of the system. In the Description box, type a description of the system. 5 (Optional) In the Asset Priority area, select values for Confidentiality, Integrity, and Availability as follows: Confidentiality Integrity Availability Value range 1 5, where level 5 means that the computer hosts content that must be maintained with the highest level of confidentiality. Value range 1 5, where level 5 means that the computer hosts content that must be maintained with the highest level of integrity. Value range 1 5, where level 5 means that the computer hosts applications and the content that must always be available for your business. Note: Different assets can have different Confidentiality, Integrity, and Availability values. Therefore, you can select these values only for a single asset at a time. 6 (Optional) In the Additional Information area, provide in the following information: The name of the organization that uses this system The physical location of the system The name of the operating system that is running on the system The version of the OS that is running on the system The owner of the system External ID information if used 7 Select Lock for Auto Update if you do not want the Assets list entry for this host to be overwritten when new information is imported from a vulnerability scanner. 8 Click the Save Asset icon.

126 126 Configuring the Console Adding a policy Adding a policy You can add a policy against which you want to check the compliance. See About configuring Information Manager on page 123. You can add a policy from the Assets view. The policy is added for the specific asset that you select from the Assets view. To add a policy from the Assets view 1 In the console of the Information Manager client, click Assets. 2 Select an asset to which you want to add the policy. 3 Double-click the asset or go to the details pane in the Assets view. 4 In the Asset Details dialog box, under the Policies tab, click the (+) plus icon. 5 Select a policy and click OK. You can add an entirely new policy from the System view. To add a new policy from the System view 1 In the Information Manager console, click System. 2 On the Administration tab, click Policies. 3 On the toolbar, click + (the plus icon). 4 Type a name and description in the spaces that are provided. 5 Click OK. Specifying networks You can specify the networks that exist in your organization to be associated with the Information Manager server. See About configuring Information Manager on page 123. To specify a network 1 In the Information Manager console, click System. 2 On Administration tab, click Networks. 3 On the toolbar, click + (the plus icon). 4 In the Create New Network dialog box, type a name for the network in the Name box. 5 Select any of the following options for Netmask/Prefix: IPv4

127 Configuring the Console About customizations for a Service Provider Master console 127 Type the subnet IPv4 address and subnet mask for the network. IPv6 Type the decimal value that is the contiguous, higher-order bits of the address that form the network part of the IPv6 address. The prefix can be any integer value between 0 and 128. For example, 10FA:6604:8136:6502::/64 6 (Optional) In the Physical Location box, type the location of the network. Further details of the physical location can be provided such as, city, state, region, latitude, longitude, and country. 7 (Optional) From the Time Zone list, select a time zone to specify the time zone in which this network is situated. You can also type the time zone details in the GMT +/- HH:MM format. When the time zone is specified, the time information from where an event has originated can be tracked. 8 (Optional) In the Logical Location box, type the logical location or select the logical location of the network. 9 (Optional) In the Description box, type a description of the network. 10 Check Auto-Updateable if you want the new entry to be overwritten when the new network information is imported from a vulnerability scanner. 11 Click OK. About customizations for a Service Provider Master console Customizations to the Incidents view include the following: Contacts, Tickets, and Remediation tabs are available from within the incident details. The Contacts tab is not available for clients having the same domain as the Service Provider Master. Incident details are displayed in a separate Information Manager console window. See About configuring Information Manager on page 123.

128 128 Configuring the Console About customizations for a Service Provider Master console

129 Chapter 7 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 131. You create new roles in the Symantec Security Information Manager. When you click Roles on the System view of the Information Manager console, you can perform the following tasks: Create a role. See Creating a role on page 132. Edit role properties. See Editing role properties on page 135. Delete a role. See Deleting a role on page 147. 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 130.

130 130 Managing roles and permissions About managing roles 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. See Editing role properties on page 135. About the default roles in the Information Manager server The Information Manager server has the following predefined roles by default: SES Administrator This role grants ownership to the entire Symantec Enterprise Security directory tree. Top-level administrators use this role. Domain Administrator This role grants ownership to a Symantec Enterprise Security domain and its subdomains. Domain administrators use this role. External Users Role This role grants base access permissions for the users that are imported from an external LDAP server. You can integrate Active Directory with the Information Manager server and add the Active Directory users. After Active Directory synchronizes with

131 Managing roles and permissions About managing roles 131 Information Manager, the Active Directory users can access the Information Manager server. Members of the External Users role do not have any automatic Information Manager privileges. Only Active Directory users use this role for Pass-through Authentication. The user must be assigned another Information Manager role to log on to the Information Manager server. See About managing roles on page 129. 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 129. 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.

132 132 Managing roles and permissions About managing roles Table 7-1 lists the common roles in a security environment and the responsibilities that belong to each role. Table 7-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. 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. Creating a role You can create roles using the Role Wizard in the Information Manager Web interface. 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 131. 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, clicksystem. 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).

133 Managing roles and permissions About managing roles 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. 8 In the Console Access Rights panel, do one of the following: To give role members the ability to see all components of the Information Manager, click Role members will have all console access rights, and click Next. To give members of the role the ability to view only limited components of the Information Manger, click Rolememberswillhaveonlytheselected 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.

134 134 Managing roles and permissions About managing roles 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: 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 135. 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 156.

135 Managing roles and permissions About managing roles 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 In the Information Manager console, click System. 2 On the Administration tab, navigate to the relevant domain, and click Roles. 3 In the right pane, right-click the role to edit, and select Properties. 4 Use the Editing Role Properties dialog box to make changes to the role. 5 To save changes and close the dialog box, click OK. See Adding a user to a role on page 135. See Modifying Information Manager console access rights on page 137. See Modifying product access rights on page 138. See Modifying server access rights on page 139. See Modifying access permissions in roles on page 141. 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

136 136 Managing roles and permissions About managing roles 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 156. See Creating a user group on page 158. To add a user to a role 1 In the Information Manager console, click System. 2 On the Administration tab, navigate to the relevant domain, and click Roles. 3 In the right pane, right-click the role to edit, and select Properties. 4 In the Editing Role Properties dialog box, in the left pane, click Members. 5 Click Add Members. 6 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. 7 To view or edit the properties of a user, click the user name, and click Properties. 8 In the User Properties dialog box, view or make changes to the properties, and click OK. 9 In the Find Users dialog box, click OK. 10 In the Editing Role Properties dialog box, click OK. To add a user group to a role 1 In the Information Manager console, click System. 2 On the Administration tab, navigate to the relevant domain, and click Roles. 3 In the right pane, right-click the role to edit, and select Properties. 4 In the Editing Role Properties dialog box, in the left pane, click Members. 5 Click Add Members From Groups. 6 In the Find User Groups dialog box, select the domain of the group from the drop-down list.

137 Managing roles and permissions About managing roles 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. 8 To view or edit the properties of a user group, click the user group name, and click Properties. 9 In the User Group Properties dialog box, view or make changes to the properties, and click OK. 10 In the Find User Groups dialog box, click OK. 11 In the Editing Role Properties dialog box, click OK. See Editing role properties on page 135. 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 In the Information Manager console, click System. 2 On the Administration tab, navigate to the relevant domain, and click Roles. 3 In the right pane, right-click the role to edit, and select Properties. 4 In the left pane, click Console Access Rights. 5 Do one of the following: To give members of the role the ability to see all components of the Information Manager, click Role members will have all console access rights. To give members of the role the ability to view only limited components of the Information Manger, click Rolememberswillhaveonlytheselected console access rights. 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) that are available to members: Show Assets Tile Show Dashboard Tile Displays the Assets view. Displays the Dashboard view.

138 138 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. Displays the Incidents view. Displays the Intelligence view. Displays the Reports view. Displays the Rules view. Displays the Statistics view. Displays the System view. Displays the Tickets view. Modifying access permissions in roles lists the console access rights that the users who perform specific functions need. 6 Click OK. See Editing role properties on page 135. 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 In the Information Manager console, click System. 2 On the Administration tab, navigate to the relevant domain, and click Roles. 3 In the right pane, right-click the role to edit, and select Properties. 4 In the left pane, click Products. 5 Do one of the following: 6 Click OK. To give the role members access to all of the listed products, click Role members will have access to all products. 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.

139 Managing roles and permissions About managing roles 139 See Editing role properties on page 135. 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 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 In the Information Manager console, click System. 2 On the Administration tab, navigate to the relevant domain, and click Roles. 3 In the right pane, right-click the role to edit, and select Properties. 4 In the left pane, click Servers. 5 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 135. 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 129. To modify SIM permissions 1 In the Information Manager console, click System. 2 On the Administration tab, navigate to the relevant domain, and click Roles. 3 In the right pane, right-click the role to edit, and select Properties. 4 In the left pane click SIM Permissions. 5 Do one of the following:

140 140 Managing roles and permissions About managing roles 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 7-2 lists the permissions that the users who perform specific functions need. 6 Click OK. 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 129. 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.

141 Managing roles and permissions About managing roles 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. 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 132. 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 in the Information Manager. 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 147. Table 7-2 describes the access requirements of typical enterprise security roles.

142 142 Managing roles and permissions About managing roles Table 7-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

143 Managing roles and permissions About managing roles 143 Table 7-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

144 144 Managing roles and permissions About managing roles Table 7-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

145 Managing roles and permissions About managing roles 145 Table 7-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 145. To modify access permissions in roles 1 In the Information Manager console, click System. 2 On the Administration tab, navigate to the relevant domain, and click Roles. 3 In the right pane, right-click the role to edit, and select Properties. 4 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. 5 When you finish setting permissions, click OK. See Editing role properties on page 135. 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.

146 146 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 148. To hide a query group from members of a role 1 In the Information Manager console, click System. 2 On the Administration tab, navigate to the relevant domain, and click Roles. 3 In the right pane, right-click the role to restrict, and select Properties. 4 In the left pane, click System Query Groups. 5 Click Add. 6 In the Find System Query Groups window, select Product Queries.Symantec Client Security, and click Add. 7 Click OK. 8 On the Product Queries.Symantec Client Security row, uncheck Read and Search. 9 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 In the Information Manager console, click System. 2 On the Administration tab, navigate to the relevant domain, and click Roles. 3 In the right pane, right-click the role to restrict, and select Properties. 4 In the left pane, click Users. 5 Under Default permissions for all users, uncheck all permission types (for example, Read and Add). 6 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.

147 Managing roles and permissions About working with permissions 147 Deleting a role To prevent role members from adding and deleting user groups 1 In the Information Manager console, click System. 2 On the Administration tab, navigate to the relevant domain, and click Roles. 3 In the right pane, right-click the role to restrict, and select Properties. 4 In the left pane, click User Groups. 5 On the top line of permissions, check Read, Write, and Search. Make sure that Add and Delete are not checked. 6 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 In the Information Manager console, click System. 2 On the Administration tab, navigate to the relevant domain, and click Roles. 3 In the right pane, right-click the role to delete, and select Properties. 4 Review the role properties to make sure that no users require this role. 5 Click Cancel. 6 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. 7 In the confirmation dialog box, click Yes to delete the role. See About managing roles on page 129. 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 Information Manager.

148 148 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 148. Permissions are always associated with roles and are applied when a member of a specific role logs on to Information Manager. Table 7-3 shows the permissions that role members can have to view and work with objects. Table 7-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.

149 Managing roles and permissions About working with permissions 149 In the Information Manager, 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 149. 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

150 150 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 148. 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 141. 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 In the Information Manager console, click System. 2 On the Administration tab, navigate to the relevant domain. 3 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. 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.

151 Managing roles and permissions About working with permissions 151 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. To modify permissions for a created object 1 In the Information Manager console, click System. 2 On the Administration tab, navigate to the relevant domain. 3 In the left pane, click the container that contains the created object. For example, click Users. 4 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. 5 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. 6 Click OK when you finish modifying permissions.

152 152 Managing roles and permissions About working with permissions

153 Chapter 8 Managing users and user groups This chapter includes the following topics: About users and passwords Customizing the password policy 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 About integrating Active Directory with the Information Manager server Managing Active Directory configurations Changing the password for Linux accounts 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:

154 154 Managing users and user groups About users and passwords root simuser sesuser db2admin dasusr1 symcmgmt Default Linux administrative account Used by the Information Manager text console process 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 Information Manager Web 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 Information Manager Web 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 Web interface under System > Administration > Data Stores. See Changing the password for Linux accounts on page 170. See Changing the password for symcmgmt Linux account on page 171. 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 interface initially. With the proper permissions, you can also create new LDAP directory accounts for users who use the Information Manager console and Information Manager Web 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 must be members of one or more roles. If a user tries

155 Managing users and user groups Customizing the password policy 155 to log on to the Information Manager 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 156. See About editing user properties on page 159. See About modifying user permissions on page 166. See Deleting a user or a user group on page 167. See Creating a user group on page 158. See Modifying a user group on page 166. See Deleting a user or a user group on page 167. 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: Default The default settings that Information Manager uses.

156 156 Managing users and user groups Creating a new user EAL4 Custom 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 Information Manager Web interface using administrator credentials, and click System > 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. Creating a new user See About users and passwords on page 153. 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 159. To create a new user 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 On the toolbar, click + (the plus symbol) or right-click the Users node and select New.

157 Managing users and user groups Creating a new user 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. 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 must be 8 to 24 characters and 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 161. You must create roles before you can assign users to roles. See Creating a role on page 132.

158 158 Managing users and user groups Creating a user group 11 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 162. 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. 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.

159 Managing users and user groups About editing user properties 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. 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 166. About editing user properties 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 160. Specify user business and contact information. See Specifying user business and contact information on page 160. Assign roles to a user. See Managing role assignments and properties on page 161. Assign user to a user group.

160 160 Managing users and user groups About editing user properties See Managing user group assignments on page 162. Specify contact methods and schedule for alert notifications. See Specifying notification information on page 164. Changing a user s password 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. 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 159. 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 159. 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.

161 Managing users and user groups About editing user properties 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. 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 132.

162 162 Managing users and user groups About editing user properties 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. 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 159.

163 Managing users and user groups About editing user properties 163 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. 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.

164 164 Managing users and user groups About editing user properties 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 96. 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 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.

165 Managing users and user groups About editing user properties 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. 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.

166 166 Managing users and user groups About modifying user permissions 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. See Modifying access permissions in roles on page 141. 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 150. 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.

167 Managing users and user groups Deleting a user or a user group 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 158. 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 156. See Creating a user group on page 158. 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.

168 168 Managing users and user groups About integrating Active Directory with the Information Manager server About integrating Active Directory with the Information Manager server The Active Directory Integration feature on the Information Manager Web interface lets you synchronize the Information Manager server with an Active Directory server. This integration enables Active Directory users to access the Information Manager server. You can create and add more than one Active Directory configuration to the Information Manager server. You can set the synchronization schedule for each configuration as required so that the users are periodically refreshed with each synchronization cycle. The synchronized Active Directory users can log on to the Information Manager server through the console as well as the Information Manager Web interface. Members of the External Users role do not have any Information Manager privileges. This role is used only by Active Directory users for Pass-through Authentication. The Active Directory user must be assigned another Information Manager role to log on to the Information Manager server. See Managing Active Directory configurations on page 168. Managing Active Directory configurations The Active Directory Integration feature on the Settings view of the Information Manager Web interface lets you create and synchronize Information Manager with Active Directory servers. The view also lets you create, add, edit, or synchronize the Active Directory configurations as required. See About integrating Active Directory with the Information Manager server on page 168. Prerequisites for creating an Active Directory configuration are as follows: If the Active Directory server and Symantec Security Information Manager are not in the same DNS, you must add the FQDN and the IP address of the Active Directory server to the Information Manager hosts file. The root certificate that is issued by the Certificate authority (CA) must be installed on the domain controller with which Information Manager is to integrate. A third-party CA or the internal CA can issue the root certificate. If the internal CA issues the root certificate, a certificate request should be generated for the AD domain controller. This request must be sent to the CA. Refer to any of the following links to generate the certificate request:

169 Managing users and user groups Managing Active Directory configurations 169 The CA root certificate of the Active Directory that you want to synchronize must be added on the Information Manager server. Note: This step is required only if you are using the root certificate issued by an internal or an unknown CA. For more details on obtaining an Active Directory root certificate, refer to the Microsoft Web site. To create a new Active Directory configuration 1 In the Information Manager Web interface, click Settings > Active Directory. 2 On the details pane, click Create Configuration. 3 Fill in the required details of the host name, IP address, user name, and password. If possible, keep the port number as 636 ( the LDAP service runs on Port 636 by default). 4 In a scenario in which the Active Directory domain name and Information Manager domain name are identical, check the box for Active Directory overrides SSIM. This setting gives the Active Directory user a preference over the Information Manager user when the user logs on to the Information Manager server. 5 Enter the users and groups that you want to synchronize or exclude in the respective boxes. The default Active Directory group domain users cannot be added to the Information Manager because it is a special group that does not have member attributes for the users. 6 Enter the password. The user name appears by default and cannot be modified. 7 Check the Disable Scheduling box if you want to disable the synchronization. 8 Enter the synchronization schedule in minutes, hours, or days as required. 9 Click Save to apply. Configurations are saved and listed by the domain name. You can edit or delete the configurations that are listed. The ibmldap service of the Information Manager server restarts when you save the Active Directory configuration.

170 170 Managing users and user groups Changing the password for Linux accounts Note: The External Users Role on Information Manager grants access permission to Active Directory domain users. Therefore, this role must not be removed for Active Directory users. Members of the External Users Role do not have any Information Manager privileges. Therefore, the Active Directory user must be assigned another Information Manager role to log on to the Information Manager server. To edit an Active Directory configurationx 1 In the Information Manager Web interface, click Settings > Active Directory. 2 On the details pane, click List Configurations. 3 Select the configuration that you want to work with. 4 Click the Edit icon. 5 Change the details in appropriate fields as required. 6 Click Save. To remove an Active Directory configuration 1 In the Information Manager Web interface, click Settings > Active Directory. 2 On the details pane, click List Configurations. 3 Select the configuration that you want to remove. 4 Click the Remove icon. 5 Enter the cn=root password in the RemoveActiveDirectoryConfigurations dialog box, and click Ok. To synchronize an Active Directory configuration 1 On the Information Manager Web interface, click Settings>ActiveDirectory. 2 On the details pane, click List Configurations. 3 Select the configuration with which you want to synchronize Information Manager. 4 Click the Synchronize Now icon. 5 Click View Synchronization Log to see the results. Changing the password for Linux accounts You can use the Information Manager Web interface to change the password that is used for Linux administrative accounts of root and simuser. Console

171 Managing users and user groups Changing the password for Linux accounts 171 administrator accounts and other Information Manager accounts are changed in the Information Manager console. The current password for Linux accounts is the same password that is given during the Information Manager installation. To change system settings such as account passwords, do not a run the scripts that are included on the Information Manager server maually. You should use the Information Manager Web interface to accomplish system level tasks. Note: If you need to perform an operation on an Information Manager server that is not available through the Information Manager Web interface or the Information Manager console, contact technical support. To change the password for Linux accounts 1 On the Information Manager Web interface, click System > Password. 2 On the left pane, click Change Password. 3 In the details pane of the Change Password view, type the name of a user account on the Information Manager server in the box provided. 4 Type the current password for the account in the box provided. 5 Type the new password and then confirm the new password in the boxes that are provided. 6 Click Change Password. Note: The password for the symcmgmt Linux account cannot be changed from the Information Manager Web interface. You can change the symcmgmt password by using the standard Linux commands. Later, the symcmgmt password must be updated from the Information Manager console. See Changing the password for symcmgmt Linux account on page 171. Changing the password for symcmgmt Linux account The symcmgmt account is a Linux account, but must also have its password changed in the Information Manager client. You can change the symcmgmt password by using the standard Linux commands. Later, the symcmgmt password must be updated from the Information Manager console under Manage > System > Administration > Data Stores.

172 172 Managing users and user groups Changing the password for Linux accounts To change the symcmgmt account in Linux 1 Log on to Information Manager server as root or connect using db2admin credentials and then obtain the root environment. 2 Run the command passwd symcmgmt. 3 Enter the new password when prompted. 4 Confirm the new password. To update the symcmgmt account password in the Information Manager Client 1 From the Information Manager client, log on to the Directory server using the Administrator privileges. 2 Go to System > Administration and navigate to DataStores. 3 In the right pane, right-click the datastore for the appropriate Information Manager server and then click Properties. 4 Go to the Connection tab and type the new password in the Password text box. 5 Confirm the new password in the Confirm password text box. See Changing the password for Linux accounts on page 170.

173 Chapter 9 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 173. 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 In the Information Manager console, click System. 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 174.

174 174 Managing organizational units and computers About managing organizational units Edit organizational properties. See Editing organizational unit properties on page 176. Delete an organizational unit. See Deleting an organizational unit on page 177. 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 173. 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 Web interface, 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.

175 Managing organizational units and computers About managing organizational units 175 (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 173. 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 9-1 describes how to calculate the UTF-8 byte length of the distinguished name of the organizational unit.

176 176 Managing organizational units and computers About managing organizational units Table 9-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 173. To edit organizational unit properties 1 In the Information Manager Web interface, 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. About modifying organizational unit permissions When you create a role, permissions are assigned for each organizational unit with regard to that role. These permissions control whether role members who log on to the Information Manager can view, modify, or delete the organizational unit. You can modify these permissions in the following ways: By displaying and editing the roles that contain the permissions.

177 Managing organizational units and computers About managing computers within organizational units 177 See Modifying access permissions in roles on page 141. By displaying the Permissions dialog box for the organizational unit container object or an individual organizational unit. See Modifying permissions from the Permissions dialog box on page 150. Note: To modify permissions, you must be logged on as a member of the SES Administrator role or the Domain Administrator role. 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 193. See Deleting a computer from an organizational unit on page 194. 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 Web interface, 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, a computer is any device that you manage as part of your enterprise security environment.

178 178 Managing organizational units and computers About managing computers within organizational units 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. 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 177.

179 Managing organizational units and computers About managing computers within organizational units 179 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. 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. You can provide the IPv4 address or the IPv6 address whichever is applicable. 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.

180 180 Managing organizational units and computers About managing computers within organizational units See Editing the agent computer on page 180. See Viewing the services running on a computer on page 188. 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 181. See Providing identification information for a computer on page 182. 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. 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 183. To remove a configuration, select it, and click Remove. To view a configuration s properties, select it, and click Properties. 8 You can view information on any of the following tabs:

181 Managing organizational units and computers About managing computers within organizational units 181 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. 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 183. To remove a configuration, select it, and click Remove. To view a configuration s properties, select it, and click Properties.

182 182 Managing organizational units and computers About managing computers within organizational units 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 179. 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.

183 Managing organizational units and computers About managing computers within organizational units 183 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 179. 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. 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 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.

184 184 Managing organizational units and computers About managing computers within organizational units Configuration Description Symantec Event Agent and Manager Agent Configurations 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. LiveUpdate 1.0 LiveUpdate LiveUpdate 1.0 Java LiveUpdate Symantec Critical System Protection Event Collector Arcsight CEF Event Collector ISS SiteProtector Event Collector Cisco ASA Event Collector Cisco(R) IOS Event Collector Check Point(R) LEA Event Collector Configures LiveUpdate to obtain software updates for the various software components of Information Manager, such as event collectors, relays, security content, rules, and filters. 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 Symantec Critical System Protection Event Collector to collect DB sensor data from various platforms. Configures ArcSight Common Event Format Event Collector to collect Syslog sensor data from various platforms. Configures the Internet Security Systems RealSecure SiteProtector Event Collector to collect DB sensor data from various platforms. Configures Cisco ASA Event Collector to collect Syslog sensor data from various platforms. Configures Cisco Internetwork Operating System Event Collector to collect Syslog sensor data from various platforms. Configures Check Point Log Export API Event Collector to collect OpsecLea sensor data from various platforms.

185 Managing organizational units and computers About managing computers within organizational units 185 Configuration Generic Syslog Event Collector Juniper NSM Event Collector Juniper Netscreen Firewall Event Collector Snare for Windows Event Collector Snort Syslog Event Collector Sourcefire estreamer Event Collector Symantec Control Compliance Suite 10 Database Event Collector Symantec Critical System Protection Event Collector Symantec Endpoint Protection Event Collector Symantec Endpoint Protection State Event Collector Symantec Messaging Gateway Event Collector Universal Logfile Event Collector Description 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 Sourcefire estreamer Event Collector to collect Sourcefire estreamer sensor data from various platforms. Configures Symantec Control Compliance Suite 10 Database Event Collector to collect DB sensor data from various platforms. Configures Symantec Critical System Protection Event Collector to collect DB sensor data from various platforms. Configures Symantec Endpoint Protection Event Collector to collect DB sensor data from various platforms. Configures Endpoint Protection State Event Collector to collect DB sensor data from various platforms. Configures Symantec Messaging Gateway Event Collector to collect SMS sensor data from various platforms. Configures the Universal Logfile Event Collector to collect events from the products that log to text files.

186 186 Managing organizational units and computers About managing computers within organizational units Configuration UNIX(R) OS Logfile Event Collector UNIX OS Event Collector Description Configures UNIX OS Logfile Event Collector to collect Logfile sensor data from UNIX platforms. 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 WS Management Event Collector Universal Syslog Event Collector Universal Event Collector for Microsoft Windows VMware vsphere Event Collector WS Management Event Collector Configures Universal WS Management Event Collector to collect WS Management sensor data from Windows platforms. 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 to collect events from Microsoft Windows event logs. Configures VMware vsphere Event Collector to collect VMware vsphere sensor data from VMware platform. Configures WS Management Event Collector to collect WS Management sensor data from Windows 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 Web interface, click Mange > 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 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.

187 Managing organizational units and computers About managing computers within organizational units 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, click System. 2 ion the Administrator tab, expand the Organizational Units navigational tree until you can select the organizational unit containing the computer that you want to edit. 3 In the right pane, select the computer. 4 On the Selection menu, click Properties. 5 In the Computer Properties dialog box, on the Configuration Groups tab, click Add. 6 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. 7 Click Add.

188 188 Managing organizational units and computers About managing computers within organizational units 8 Click OK. 9 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. 10 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 179. 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: 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.

189 Managing organizational units and computers About managing computers within organizational units 189 Click Details to open the Service Properties dialog box and view the details of services. 7 When you finish, click OK. About the Visualizer 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 189. See Viewing and modifying element properties on page 191. 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 189. 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. 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.

190 190 Managing organizational units and computers About managing computers within organizational units 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 9-2 describes the tools in the toolbar. Table 9-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 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.

191 Managing organizational units and computers About managing computers within organizational units 191 Table 9-2 Tool Zoom selected Fit to window Save as Export Image Print Table view Visualizer tools (continued) Purpose 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. 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 189. 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 9-3 explains how to access each of the element categories on other System view tabs.

192 192 Managing organizational units and computers About managing computers within organizational units Table 9-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. 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. 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 177. 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.

193 Managing organizational units and computers About managing computers within organizational units 193 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. To distribute configurations to selected computers in an organizational unit 1 In the Information Manager Web interface, 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 173. Warning: Before you move a computer, make sure that the security products you manage let you move computers.

194 194 Managing organizational units and computers About managing computers within organizational units 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. 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 150. 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.

195 Managing organizational units and computers About managing computers within organizational units 195 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 178. Deleting a computer from an organizational unit removes it from the LDAP directory. 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. 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.

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

197 Section 4 Understanding event collectors Chapter 10. Introducing event collectors Chapter 11. Configuring collectors for event filtering and aggregation

198 198

199 Chapter 10 Introducing event collectors This chapter includes the following topics: About Event Collectors and Information Manager Collectors About Symantec Universal Collectors About Custom Log Management Downloading and installing the Symantec Universal Collectors Correlating the logs collected in a file from a proprietary application 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.After you install an event collector, you must first register it and then configure it before you can use it. 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

200 200 Introducing event collectors Collectors 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. 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. 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 199. Table 10-1 Component Roles played by different components Description Information Manager Symantec Event Agent Collector Sensor 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 Agent that sends the data that is collected by the Symantec Event Collector to the Information Manager server. 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.

201 Introducing event collectors About Symantec Universal Collectors 201 Table 10-1 Component Roles played by different components (continued) Description Security or Point product 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 199. 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 203. About Custom Log Management Information Manager uses the event collectors that can be installed on the Information Manager server or on a computer that runs Symantec Event Agent. The collectors translate the collected data before it is handed over to the event service for archival and correlation service for correlation. Information Manager provides collectors for over 250 products. If a collector does not exist for an application in an environment, it is not possible to collect and normalize the data for the application.

202 202 Introducing event collectors About Custom Log Management The custom log management feature lets you collect logs from an application from which Information Manager does not support collection. You can analyze the received log data and adjust the fields where necessary to prepare the data for interpretation by Information Manager. To collect the logs, you can download and install the universal collectors that are available on the Web configuration interface. You can install universal collectors on the computers on which Symantec Event Agent is installed. Custom log management works with the following components: Universal log collector Transports the log data that is collected from a point product or application to Information Manager. The universal log collectors can be installed on the Information Manager server on other computers that have Symantec Event Agent installed on them. See Downloading and installing the Symantec Universal Collectors on page 203. You can download the following universal collectors from the Home > Download view of the Web configuration interface of Information Manager. Universal Collector for Log File Collects the events that are from different log files. Universal Collector for Windows Collects the events that are from Windows logs. Universal Collector for Syslog Collects the events that are from syslog. Universal Collector for Windows Vista Collects the events that are from Windows Vista Note: The universal collectors are preinstalled on the Information Manager server. The Universal Collector for Windows is not installed on the Information Manager server because it cannot run on Linux.

203 Introducing event collectors Downloading and installing the Symantec Universal Collectors 203 Collector mapping tool Maps the log data that the universal collectors collect to the event fields that are defined within Information Manager. The mapping is done with the.norm files that are used for event normalization within Information Manager. See About normalization (.norm) files on page 263. You can provide the log data mappings in the following ways: Pattern mapping Lets you map the entire pattern of the log entries. The fields from the pattern are mapped to fields that Information Manager supports. Direct mapping Lets you map a field to another field. The mapped field is used to create new rules. In this case, both the fields have the same value. For example, you can map the Agent IP to Source IP. In this case, the value of the Source IP field always corresponds to the value of the Agent IP field. Literal mapping Lets you assign the Literal constant values to the output event fields. For example, you can assign a constant value <###> to the Source Host field. 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 201. 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.

204 204 Introducing event collectors Correlating the logs collected in a file from a proprietary application 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. 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. Correlating the logs collected in a file from a proprietary application By using the Custom Logs feature, you can correlate the logs that are collected from a proprietary application with the fields that Information Manager supports. Consider an example of a log entry from a Linux system. The log entry should be in the following format: <ip address>,<source host>,<user name> <operating system>. Assume that the log entry is as follows: ,ssim2,john,Linux

205 Introducing event collectors Correlating the logs collected in a file from a proprietary application 205 You can analyze the application log data that is collected from the Linux system in Information Manager. The custom log management feature lets you map the collected logs with the fields that Information Manager supports. Ensure that the following requirements are met before you begin the analysis of the application log data: Symantec Event Agent is installed on the computer on which the application logs are saved. The Universal Collector for Log Files is downloaded and installed from Home > Downloads view of the Web configuration interface. In a multi-server setup, Information Manager must be registered with the Correlation Manager. To achieve the objective of collecting and mapping the logs from a proprietary application, you must complete the following steps: Download and install the universal collector. See Downloading and installing the Symantec Universal Collectors on page 203. Create a new sensor configuration. Configure a reporting sensor from which the logs are collected. See Downloading and installing the Symantec Universal Collectors on page 203. Map the log fields to the fields that the Information Manager supports.

206 206 Introducing event collectors Correlating the logs collected in a file from a proprietary application

207 Chapter 11 Configuring collectors for event filtering and aggregation This chapter includes the following topics: Configuring the event filtering rules Configuring event aggregation Configuring the event filtering rules 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">

208 208 Configuring collectors for event filtering and aggregation Configuring the event filtering rules <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 208. Changing the existing event filtering rules See To change existing event filtering rules on page 209. Importing and exporting the event filtering rules See To import and export event filtering rules on page 210. 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. For all the IP address associated fields, you are prompted to select either an IPv4 address or an IPv6 address. 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.*)

209 Configuring collectors for event filtering and aggregation Configuring the event filtering rules 209 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.

210 210 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

211 Configuring collectors for event filtering and aggregation Configuring event aggregation 211 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 199. 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 212. Changing existing event aggregation rule configurations See To change existing event aggregation rule configurations on page 213. Importing and exporting event aggregation rules See To import and export event aggregation rules on page 214. 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.

212 212 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. For all the IP address associated fields, you are prompted to select either an IPv4 address or an IPv6 address. 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.

213 Configuring collectors for event filtering and aggregation Configuring event aggregation 213 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. 3 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.

214 214 Configuring collectors for event filtering and aggregation Configuring event aggregation 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. 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.

215 Section 5 Working with events and event archives Chapter 12. Managing event archives Chapter 13. Forwarding events to the Information Manager Server Chapter 14. Understanding event normalization Chapter 15. Collector-based event filtering and aggregation

216 216

217 Chapter 12 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 Specifying event archive settings Creating a local copy of event archives on a network computer Restoring event archives 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.

218 218 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 20. 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 217. About the event lifecycle Figure 12-1 shows the lifecycle of an Information Manager event.

219 Managing event archives About the event lifecycle 219 Figure 12-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 217.