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
2. Select one of the following options to resynchronize:
• Click the Resync button.
• Choose the Actions > Resync menu item.
• Press Shift+F6.
• Right-click in the Monitored Hosts area and select Resync from the menu.
Any alerts in each agent’s log file that are newer than the last one seen by the System Manager
are transferred to the System Manager’s log files. The numbers are updated on the Monitored
Hosts list and the alerts and errors are displayed on the Network Node screen for each host.
The updates continue as alerts and errors are generated and the System Manager runs.
Activating Schedules on Agent Hosts
To provide intrusion detection, you must activate surveillance schedules on the agent hosts. You
also use this procedure to replace a schedule on one or more hosts.
To activate a surveillance schedule on agent hosts, follow these steps:
1. On the System Manager screen, in the Monitored Hosts list, select the hosts to be activated.
Their Status fields must show Available, Scheduled, or Running.
2. In the Schedules list, select the surveillance schedule you want to activate.
3. Select one of the following options to activate the schedule:
• Click the Activate button.
• Choose the Actions > Activate Schedule menu item.
• Press Shift+F8.
• Right-click (in the Monitored Hosts area) and select Activate Schedule from the menu.
4. If any of the agent hosts is already running a schedule, the Confirm Schedule Activation
dialog box appears. Click Yes to override existing surveillance schedule, and No to cancel.
5. If the activation is successful, the Status column indicates Scheduled or Running, and the
name of the downloaded surveillance schedule is displayed in the Schedule column of the
selected hosts; otherwise, Error or No Agent Available is displayed in the Status
column.
6. If Error is shown for a host, view the error messages on the Network Node Error tab for
the host. For more information see “Network Node Screen” (page 56) and “Errors Tab ”
(page 97) then check the status. For more information, see “Getting the Status of Agent
Hosts” (page 51).
If No Agent Available is shown for a host, see “No Agent Available” (page 221) for
troubleshooting options.
Stopping Schedules on Agent Hosts
When you stop a surveillance schedule on an agent host, the schedule is removed from the agent
and ceases to be scheduled or running. The agent program continues running, ready to accept
future actions.
If you want to replace one schedule with another, just activate the new one. For more information,
see “Activating Schedules on Agent Hosts” (page 53).
To stop a surveillance schedule on agent hosts, follow these steps:
1. On the System Manager screen, in the Monitored Hosts list, select one or more hosts on
which you want to stop the schedules.
Activating Schedules on Agent Hosts 53