OSSEC / HIDS Rule 59227

OSSEC / HIDS rule catalog

• Rule family: OSSEC / HIDS
• Rule ID: 59227
• Definition status: Present in current source
• Alert message / subject: Logon Failure - User not granted logon type
• Rule level: 5
• Definition checked: 2026-10-21

Interpretation and response

This event is recorded as “Logon Failure - User not granted logon type”. 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.

Description

Windows has detected that a system has attempted to log an account where they have not been granted the logon type. The logon otherwise succeeded (the username, password and/or other credentials are valid). The account is simply not allowed to logon in as this type of logon.

Associated Windows Event IDs

• 529
• 530
• 531
• 532
• 533
• 534
• 535
• 536
• 537
• 539
• 4625

Logon types

1 – Interactive Console Logons

2– Network - This logon happens when you’re accessing file shares using SMB for example.

3– Batch - This is used for scheduled tasks.

4– Service - This is used for services and service accounts that log on to start a service.

5– Unlock - This is used whenever a user unlocks their machine.

6– Network Cleartext - This is used when logging on over the network - when the password is sent in clear text (should happen to you!)

7– New Credentials - This is used when you run an application using the RunAs command.

8– Remote Interactive - This is used for the RDP applications like Terminal Services or Remote Assistance.

9– Cached Interactive - This is logged when users log on using cached credentials.

Examples

For example, the account INTERN cannot run as a batch process (logon type 2) because the user is just an intern and should not be attempt to login as a batch process.

What you should do

If this is authorized behavior, update the users account configuration to allow this logon type. If this is not expected or authorized behavior, this may indicate an attack, and the source should be investigated. Check the GUI for other events from the sources IP.

The platform will track this logon, and if multiple events occur will issue a higher level alert that a brute force attack may be occurring.

Troubleshooting

False Positives

A legitimate event may still trigger this rule. Review the surrounding activity before deciding whether it is malicious.

Tuning Guidance

There is no guidance for tuning this rule, this is a generic Windows error and the rule should not be disabled.

Additional Information

Support

If you are unsure about how to respond to this alert, please contact Atomicorp support. We’re here to help you!

Similar Rules

HIDS_59222 Windows: Remote Logon Failure - Unknown user or bad password

HIDS_59223 Logon Failure - Account logon time restriction violation

HIDS_59224 Logon Failure - Account currently disabled

HIDS_59225 Logon Failure - Specified account expired

HIDS_59226 Logon Failure - User not allowed to login at this computer

HIDS_59228 Logon Failure - Account’s password expired

HIDS_59229 Logon Failure - Internal error

HIDS_59230 Logon Failure - Account locked out

Source and revision

Migrated from HIDS_59227, wiki page 743, revision 6105 (20201020). 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 .