HP-UX Host Intrusion Detection System Version 4.3 administrator guide
Table Of Contents
- HP-UX Host Intrusion Detection System Version 4.3 administrator guide
- Table of Contents
- About This Document
- 1 Introduction
- 2 Configuring HP-UX HIDS
- 3 Getting Started with HP-UX HIDS
- 4 Using the System Manager Screen
- Starting the HP-UX HIDS System Manager
- Stopping the HP-UX HIDS System Manager
- System Manager Components
- Starting HP-UX HIDS Agents
- Getting the Status of Agent Hosts
- Resynchronizing Agent Hosts
- Activating Schedules on Agent Hosts
- Stopping Schedules on Agent Hosts
- Halting HP-UX HIDS Agents
- Accessing Other Screens
- 5 Using the Schedule Manager Screen
- The Schedule Manager
- Configuring Surveillance Schedules
- Configuring Surveillance Groups
- Configuring Detection Templates
- Setting Surveillance Schedule Timetables
- Configuring Alert Aggregation
- Configuring Monitor Failed Attempts
- Configuring Duplicate Alert Suppression
- Viewing Surveillance Schedule Details
- Predefined Surveillance Schedules and Groups
- 6 Using the Host Manager Screen
- 7 Using the Network Node Screen
- 8 Using the Preferences Screen
- A Templates and Alerts
- Alert Summary
- UNIX Regular Expressions
- Limitations
- Template Property Types
- Buffer Overflow Template
- Race Condition Template
- Modification of files/directories Template
- Changes to Log File Template
- Creation and Modification of setuid/setgid File Template
- Creation of World-Writable File Template
- Modification of Another User’s File Template
- Login/Logout Template
- Repeated Failed Logins Template
- Repeated Failed su Commands Template
- Log File Monitoring Template
- B Automated Response for Alerts
- C Tuning Schedules and Generating Alert Reports
- D The Agent Configuration File
- E The Surveillance Schedule Text File
- F Error Messages
- G Troubleshooting
- Troubleshooting
- Agent and System Manager cannot communicate with each other
- Agent complains that idds has not been enabled, yet lsdev shows /dev/idds is present
- Agent does not start on system boot
- Agent halts abnormally, leaving ids_* files and message queues
- Agent host appears to hang and/or you see message disk full
- Agent needs further troubleshooting
- Agent does not start after installation
- Agents appear to be stuck in polling status
- Agent displays error if hostname to IP mapping is not registered in name service
- Aggregated alerts targets or details field are truncated and the same aggregated alert has several entries logged in the IDS_ALERTFILE
- Alert date/time sort seems inconsistent
- Alerts are not being displayed in the alert browser
- Buffer overflow triggers false positives
- Duplicate alerts appear in System Manager
- Getting several aggregated alerts for the same process
- GUI runs out of memory after receiving around 19,000 alerts
- The idsadmin Command needs installed agent certificates
- The idsadmin Command notifies of bad certificate when pinging a remote agent
- IDS_checkInstall fails with a kmtune error
- IDS_genAdminKeys or IDS_genAgentCerts does not complete successfully
- IDS_genAdminKeys or idsgui quits early
- Large files in /var/opt/ids
- Log files are filling up
- No Agent Available
- Normal operation of an application generates heavy volume of alerts
- Reflection X rlogin produces multiple login and logout alerts
- Schedule Manager timetable screen appears to hang
- SSH does not perform a clean exit after idsagent is started
- System Manager appears to hang
- System Manager does not let you save files to specific directories
- System Manager does not start after idsgui is started
- System Manager starts with no borders or title bar in X client programs on Windows
- System Manager times out on agent functions such as Activate and Status Poll
- UNKNOWN program and arguments in certain alert messages
- Using HP-UX HIDS with IPFilter and SecureShell
- Unable to Generate Administrator Keys and Agent Certificates on PA–RISC 1.1 Systems
- Troubleshooting
- H HP Software License
Global Configuration
The Global section is bracketed by the [global]...[END] keywords. Only the parameters in
Table D-1 may be edited.
CAUTION: Do not edit any other variables between [global] and its [END] tag.
Table D-1 Global Configuration Variables
Default ValueName
/var/opt/ids/alert.logIDS_ALERTFILE
/var/opt/ids/error.logIDS_ERRORFILE
""
IDS_LISTEN_IFACE
/opt/ids/rt_responseIDS_RT_RESPONSE_DIR
/opt/ids/responseIDS_RESPONSE_DIR
They are defined as follows:
IDS_ALERTFILE
The full path name to the alert log file for this HP-UX HIDS agent
process. Any alerts resulting from intrusive activity detected by
the agent software will be logged to this file.
IDS_ERRORFILE
The full path name to the error log file for this HP-UX HIDS agent
process. Any errors generated in the operation of the agent
software will be logged to this file.
IDS_LISTEN_IFACE
The IP address or host name associated with the agent system’s
network interface card.
On a system with only one IP address, this parameter does not
need to be specified.
On a multihomed system (a system with more than one network
interface card) this parameter is required. See “Configuring a
Multihomed Agent System” (page 35) for configuration
information.
IDS_RT_RESPONSE_DIR
The full path name to the automated response directory, containing
executable binary or script programs that are executed on the
agent node. These programs are executed when a real-time alert
is generated and when both the Alert Aggregation and the Real
Time Alerts options are enabled. The programs can take any
actions that you deem appropriate. For more information on
writing response scripts, see Appendix B (page 159) for information
on writing response scripts. For more information about how real
time alerts can be generated when alert aggregation is enabled,
see “Configuring Alert Aggregation” (page 72).
IDS_RESPONSE_DIR
The full path name to the automated response directory containing
executable binary or script programs that are executed on the
agent node. These programs are executed either when alert
aggregation is disabled and any alert is generated or when alert
aggregation is enabled and an aggregated alert or an alert that is
not or cannot be aggregated is generated. The programs can take
any actions that you deem appropriate. For information on writing
response scripts, see Appendix B (page 159).
For more information about different types of alerts that can be generated when alert aggregation
is enabled, see “Configuring Alert Aggregation” (page 72).
192 The Agent Configuration File