background image

530-025628-01

Resolved Issues

5

Resolved Issues

This section describes the resolved issues in STRM Log Management 2008.2:

Changing Network Settings No Longer Causes System Failure

Previously, if you changed your network settings (for more information, see the 

Changing Network Settings Technical Note)

, a failure occurred when you 

attempted to access the system. This no longer occurs. 

During Installation Process, Error No Longer Occurs When Root Password is 
Not Changed

During the installation process, a message appears indicating that you are able to 
use the default root password. However, if you attempted to use the default 
password, a message appeared indicating that you must enter a new password. 
This no longer occurs. 

Hostname that Includes Underscores and Special Characters No Longer 
Causes Error

Previously, if the hostname of your STRM Log Management system included 
underscores and/or special characters (except dashes), the Host Context 
component failed to start. Once this occurred, STRM Log Management failed to 
collect data. This no longer occurs. 

Now Able to Deploy License Key Once Current Key Expires

Previously, if your license key expired and you uploaded a new license key, STRM 
Log Management did not provide the option to deploy the new license key. 

Changing the Authentication to STRM Log Management Authentication No 
Longer Requires Edits to Passwords 

Previously, if you changed your authentication from TACACS, RADIUS, or LDAP/ 
Active Directory to STRM Log Management Authentication, you were required 
configure access for users on the system before they are able to login to STRM 
Log Management. No message appeared in STRM Log Management stating this 
requirements. In STRM Log Management 2008.2, you must define passwords for 
all users that do not have a password defined. 

Updating License Key When Using Internet Explorer 6 No Longer Causes 
Error

Previously, when you updated your license key using an Internet Explorer 6 
browser, a window appeared stating “The page cannot be displayed” when you 
click 

Save

. This no longer occurs. 

New Administrative User Now Able to Access Deployment Editor

A STRM Log Management administrative (admin) user can create multiple admin 
accounts for a STRM Log Management system. A administrative user should have 
unrestricted access to all components of your deployment. Previously, when a new 
administrative user attempted to access the deployment editor, an error message 
appeared and access was denied.

Summary of Contents for SECURITY THREAT RESPONSE MANAGER 2008.2 - CATEGORY OFFENSE INVESTIGATION GUIDE REV 1

Page 1: ...ager Log Management Only STRM LM provides a comprehensive log management solution for organizations that want to implement a distributed log management solution to collect archive and analyze network...

Page 2: ...ch system in your deployment New Device Extensions Functionality You can now modify how a DSM parses logs For example you can use a device extension to detect an event that has missing or incorrect fi...

Page 3: ...re information on Release 2008 2 refer to the on line documentation STRM Log Management Installation Guide STRM Log Management Administration Guide STRM Log Management Users Guide STRM Log Management...

Page 4: ...a device requires STRM to forward logs through NSM Note For STRM to correctly process logs from SA and IC the logs should be sent from the devices in WELF format To enable WELF format on the device Un...

Page 5: ...if your license key expired and you uploaded a new license key STRM Log Management did not provide the option to deploy the new license key Changing the Authentication to STRM Log Management Authentic...

Page 6: ...nagement 2008 2 the limit of CIDR ranges you can add is approximately 200 depending on the data on your system Now Able to Apply Any IP Filter When Searching for Events Previously when you attempted t...

Page 7: ...nt 2008 2 this directory structure is properly created Events Appear in Event Viewer and Flows in Flow Viewer After June 30 2008 The Event Correlation Engine license expires on 30 June 2008 This licen...

Page 8: ...e configuration file and restart services Step 1 Open the configuration file on the machine that uses the custom SSL key normally the Web Server console Step 1 Add the directory path to your custom SS...

Page 9: ...oller IC device may appear incorrectly as an Enterasys device Workaround Add the Infranet Controller device manually Infranet Controller Device Appears as Secure Access Device An auto discovered Infra...

Page 10: ...nfiguration change the event query service process restarts and may be temporarily unable to process event searches Workaround Wait between 2 and 3 minutes for the Event Viewer to finish restarting Th...

Page 11: ...per Networks Inc in the United States and other countries JUNOS and JUNOSe are trademarks of Juniper Networks Inc All other trademarks service marks registered trademarks or registered service marks a...

Reviews: