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
REMOTEHOST
to
REMOTEHOST 192.0.2.4
or
REMOTEHOST 2001:db8::100
NOTE: The REMOTEHOST parameter is overridden when you import the certificate bundle
with IDS_importAgentKeys.
13. Save the file with your modifications.
14. If the agent is running, force it to reread its configuration file, as described in “Forcing Active
Agent to Reread Configuration File” (page 191).
Changing the IP Address of an Administration System
If the IP addresses of the administration systems need to be changed, you must complete the
following steps to ensure that HIDS continues to run smoothly:
• Check the REMOTEHOST entry in the ids.cf file located on the agent systems. If the
REMOTEHOST entry refers to the hostname, no modifications are required. However, if the
REMOTEHOST entry refers to the IP address, then you must update the entry to reflect the
new IP address.
TIP: If your administration system is not multihomed, and if you do not plan to make it
multihomed, use a hostname for the REMOTEHOST entry. You need not modify the ids.cf
file even if the IP address changes in future, as long as the hostname of the administration
system does not change.
• Make this change in all the ids.cf files located on all the agent systems.
If the ids.cf files are identical, you can choose to push a master copy of the file to all the
agents.
Configuring a Loopback System
On a non-networked system (a system with no IP address) or for testing purposes, you can set
up an administration system in a loopback arrangement. This enables only a locally running
agent to communicate with the System Manager on the same system; no other agent systems
can be monitored.
To configure a loopback system, follow these steps:
NOTE: For an IPv6 system, replace all occurances of 127.0.0.1 below with ::1, the IPv6
notation for a loopback address.
1. On the administration system, log in as ids, as follows:
$ su - ids
2. Edit the agent configuration file. For example:
$ vi /etc/opt/ids/ids.cf
3. Set the value of IDS_LISTEN_IFACE to the following:
IDS_LISTEN_IFACE 127.0.0.1
4. Set the value of REMOTEHOST in ids.cf to the following:
REMOTEHOST 127.0.0.1
Configuring a Loopback System 39