On this page

OSSEC / HIDS Rule 1006

OSSEC / HIDS rule catalog

  • Rule family: OSSEC / HIDS
  • Rule ID: 1006
  • Definition status: Present in current source
  • Alert message / subject: Syslogd restarted.
  • Rule level: 5
  • Definition checked: 2026-10-21

Interpretation and response

This event is recorded as “Syslogd restarted.” Review the originating log and the affected host or service to determine whether the activity was expected.

An OSSEC/HIDS event records or correlates activity. Blocking depends on the originating application and any separately configured Active Response policy; an alert alone does not prove that an attack was blocked.

Documentation

The following guidance was migrated from the historical wiki and reviewed against the rule definition. Legacy ASL product names and interface instructions refer to the versions documented then. Use the current metadata above and your installed configuration when interpreting thresholds, notification settings and response behavior.

Example log message:

server syslogd 1.4.1: restart.

Explanation:

This means the syslogd system has been restarted. The system servers as the main logging system for the OS. It may be periodically restarted when logs or rotated, or if its software is updated. It may also be restarted via unauthorized activity, such as if the logging system was deactivated to hide actions and then restarted later.

Logs should be audited to see if the syslog system was disabled at any point. The HIDS 1004 (historical reference) and HIDS 1104 (historical reference) events will log if the syslogd system is specifically shut down (as opposed to restarted).

Source and revision

Migrated from HIDS_1006, wiki page 236, revision 2015 (20111218). Documentation review: 2026-10-21. An archived wiki status of Active is not a current deployment status.

For assistance, provide the rule ID, installed product and rule version, and a sanitized event to Atomicorp support .