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

Table C-2 Reporting Options Supported by idsadmin (continued)
DescriptionOption
Comma-separated list of alert fields to print in a report, where:
• hostname — The hostname of the agent that generated the alert.
• ipaddr — The host IP address of the agent that generated the
alert.
• template — The template that generated the alert.
• localdate — The local date and time of the event that triggered
the alert.
• utcdate — The UTC date and time of the event that triggered
the alert.
• utcsecs — The UTC time of the event that triggered the alert.
• severity — The alert severity.
• count — Number of times this alert was generated. For aggregated
alerts, this field contains the number of alerts that were aggregated
into a single alert.
• attacker — Program that triggered the attack for file related
alerts. User that triggered the attack for login/logout or su alerts.
For aggregated alerts, the program that triggered the alerts and/or
whose forked programs triggered the alerts.
• target — For file related alerts, the pathname of the targeted file.
For login/logout, or su alerts, the targeted user account. For
aggregated alerts, set to {multiple targets}.
• event — The event that triggered the target. For aggregated alerts,
this field is set to {multiple targets}.
• user — The user (ruid:rgid:euid:egid) that triggered the alert.
• summary — Alert summary.
• details — Alert details.
By default, all fields (except the template field) are displayed.
--alert-fields
Specifies that only alerts with the specified severity levels are reported.
By default, alerts of all severity levels are included in the alert report.
If this option is not specified, alerts of all severity levels are included
in the report.
--alert-severities critical |
severe | moderate | all
Comma separated list of email addresses to which alert reports are
sent.
--email-to EMAIL_ADDRESS1,
EMAIL_ADDRESS2, ...
Used with the --email-to reporting options. Text of an email
message containing a report. Text must be enclosed in double quotes
if it contains white spaces. This option can be specified only from the
command line and not from the interactive menu prompt.
--email-message TEXT
Used with the --email-to reporting options. Subject line of an email
message containing a report. Text must be enclosed in double quotes
if it contains white spaces. This option can be specified only from the
command line and not from the interactive menu prompt.
--email-subject TEXT
Specifies that only alerts generated on or before the specified date are
reported. The date/time is interpreted as local time on the host on
which idsadmin is run, not as the local time on agent host(s). The
default is the current time. If YYYYMMDD is specified but not HHMMSS,
then HHMMSS defaults to 235959 (11:59:59 PM).
--end-date YYYYMMDD[HHMMSS]
Used with the --report-format (with raw option) reporting option.
Specifies the delimiter character when printing alert reports in raw
format. The default is the pipe (|) character.
--report-delimiter CHAR
Specifies the format of the generated report. The default is html.
--report-format html | txt | raw
186 Tuning Schedules and Generating Alert Reports