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

Agents
The HP-UX HIDS agent software must be running continually on the systems you are monitoring
for it to detect and report intrusions as they occur. When an agent is running a schedule, it records
intrusion alerts and agent program errors in local log files.
When the System Manager is running on the administration system, and is monitoring the agent,
alerts and errors are transferred to log files on the administration host.
In addition, agents pass alerts to user-defined programs on the agent host for analysis and action
if such programs are configured. For more information, see “Automated Response for Alerts”
(page 159).
The agent runs as a background daemon on the agent host. It communicates with the
administration host via an encrypted Secure Socket Layer (SSL) communications link, which
provides integrity, confidentiality, and authentication for network transmission.
System Manager
The HP-UX HIDS System Manager runs on the administrative system and monitors the alerts
generated by agents on the agent hosts. Use it to create surveillance schedules and download
them to agents on agent hosts.
Starting HP-UX HIDS for the First Time
This procedure describes the steps required to start the HP-UX HIDS System Manager and agents
for the first time. As you do this, your systems benefits immediately the protection of intrusion
detection while you learn the specifics of the software and tune your configuration to fit your
requirements.
Procedure 3-2 To Set up hosts and run schedules, follow these steps:
1. Install the agent software on the agent hosts and the System Manager software on the
administration host. For more information, see the HP-UX HIDS 4.3 release notes.
2. Create SSL certificates for the administration and agent hosts and propagate them to the
host systems. For more information, see “Setting Up HP-UX HIDS Secure Communications”
(page 29).
3. Log in to each agent host as root and start the idsagent program as the ids user. For
more information, see “Starting HP-UX HIDS Agents” (page 51).
NOTE: The ids password field is set to * on installation on both agent and administration
systems, which means you cannot log in directly to ids. For security reasons, do not assign
a password to ids.
a. Login as ids.
# su ids
b. Start the agent program.
$/opt/ids/bin/idsagent
44 Getting Started with HP-UX HIDS