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

ip_filters Contains a list of triplets {ip_address, mask,severity}.Filters
login alerts and determines the alert’s severity based on which
remote host or network the login was made from. If a login’s
remote host IP address matches one of the triplet’s IP addresses
qualified by the triplet’s network mask, then the alert severity is
set to the corresponding triplet’s severity. A severity level of 0
indicates that an alert for a login event with a matching remote IP
address is filtered except for root and ids users. If a login event’s
remote host IP address does not match any triplet, then a severe
alert (severity=2) is generated for users in priv_user_listand
a moderate alert (severity=3) is generated for all other users. If the
ip_address is a host IPv4 address, the value of the mask must be
set to 255.255.255.255. If the ip_address is a host IPv6 address, the
value of the mask should be set to /128. Host address filtering is
only applied to those login events that are not filtered out by the
users_to_ignore and users_to_monitor template
properties.
priv_user_list
A high severity alert is generated when a user with a user ID or
user name in this list logs in or logs out.
Alerts generated by this template
See “Login/Logout” (page 149) and “Successful su Detected” (page 150) for more information
about the alerts generated by the Login/Logout template.
Login/Logout
Table A-23 lists the alert properties the Login/Logout template generates and forwards to a
response program when a successful login or logout occurs.
Table A-23 Login/Logout Alert Properties
DescriptionAlert Value/FormatAlert Field TypeAlert FieldResponse
Program
Argument
Unique code assigned to
template
7IntegerTemplate
code
argv[1]
Template version<version>IntegerVersionargv[2]
Alert severity2 for users listed in the
priv_user_list property, and 1 if
specified by an ip filter property.
IntegerSeverityargv[3]
UTC time in number of
seconds since the epoch
when a successful login,
logout, or su event
occured.
<secs>
IntegerUTC Timeargv[4]
Name or IP address of the
host from which the user
attempted to log in.
<fully qualified host name>
<IP address>
StringAttackerargv[5]
Login name that the user
attempted to log in as.
<username>
StringTargetargv[6]
Alert summaryStart of a successful login session or
end of a login session
StringSummaryargv[7]
Login/Logout Template 149