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
HP-UX HIDS Functionality
HP-UX Host Intrusion Detection System (HIDS) is an intrusion detection system that enhances
local host-level security within a network. It automatically monitors each configured host system
within the network for possible signs of unwanted and potentially damaging intrusions. If an
intrusion is successful, it can lead to the loss of availability of key systems or compromise system
integrity.
HP-UX HIDS continuously examines ongoing activity on a system, and it seeks out patterns that
suggest security breaches or misuses. Security threats or breaches can include attempts to break
into a system, subversive activities, or spreading a virus. Once you activate HP-UX HIDS for a
given host system and it detects an intrusion attempt, the host sends an alert to the administrative
interface where you can immediately investigate the situation, and when necessary, take action
against the intrusion. In addition, you can set up customized local responses to alerts.
HP-UX HIDS can provide notification in the event of suspicious activity that can precede an
attack. By contrast, other intrusion detection systems often allow a potential intruder considerable
time to damage a system before being detected, because they rely on an operator-instigated
analysis of system log files, typically performed at the end of the day.
HP-UX HIDS is useful for enterprise environments where centralized management tools control
networks of heterogeneous systems. These environments can include web servers, transaction
processors, application servers, and database systems.
HP-UX HIDS uses knowledge about how host systems, the network, or the entire enterprise can
be exploited, and applies that expertise to the flow of system events. Many intrusions, while
differing in their scenarios, reuse the same building blocks to exploit a wide variety of system
vulnerabilities. HP-UX HIDS uses known building blocks to protect resources against existing
attack scenarios and unknown scenarios.
HP-UX HIDS provides simplified administration through a secure graphical user interface (GUI),
the HP-UX HIDS System Manager.
HP-UX HIDS provides customizable intrusion response capabilities. Hosts always send alerts
to the administration interface. You can augment these notifications with automated host-based
response programs that you can customize for the host that is being monitored. HP provides a
customized program for OpenView Operations (OVO) integration; you can also create your own.
HP-UX HIDS Limitations
HP-UX HIDS cannot solve all security-related problems. Following are the limitations of HP-UX
HIDS:
• HP-UX HIDS is not a replacement for comprehensive security policies and procedures. You
must define and implement security policies and procedures, and configure HP-UX HIDS
to enforce them. A lack of comprehensive policies, procedures, and configuration can result
in attacks going undetected. HP-UX HIDS can also report false alerts, while your system
remains vulnerable.
• HP-UX HIDS does not prevent the onset of attacks. If your system is vulnerable to attacks,
those vulnerabilities remain even after HP-UX HIDS is installed.
• HP-UX HIDS does not find static security flaws on a system, nor does it prevent the onset
of attacks. It only reports the possibility of an attack or an intrusion. For example, if a
password file contained an illegitimate account before HP-UX HIDS was installed, that
illegitimate account remains vulnerable even after HP-UX HIDS is installed and operational.
Furthermore, HP-UX HIDS cannot authenticate users of a valid account. For example, if
users share passwords, HP-UX HIDS cannot ascertain the identity of the user gaining access
to the system.
HP-UX HIDS Functionality 23