devnulli
commented
1 month ago while you can basically add new rules very easily, the least thing you would need is an actual IP address in it, so you know what/who to ban. there seems to be one in the first line, so you can actually create a rule to autoban this very easily.
do you need help doing that?
We're getting hammered by brute force attempts to our RDWeb. Looking for a solution that will auto ban IP's that don't log the source IP in the 4625 event log entry but do log it in IIS logs, like this:
IIS Log: 2024-07-22 19:40:24 XX.XX.XX.XX POST /RDWeb/Pages/en-US/login.aspx - 443 - 106.58.209.67 node-fetch/1.0+(+https://github.com/bitinn/node-fetch) - 200 0 0 431
Event Log: Log Name: Security Source: Microsoft-Windows-Security-Auditing Date: 7/22/2024 12:40:23 PM Event ID: 4625 Task Category: Logon Level: Information Keywords: Audit Failure User: N/A Computer: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Description: An account failed to log on.
Subject: Security ID: IIS APPPOOL\RDWebAccess Account Name: RDWebAccess Account Domain: IIS APPPOOL Logon ID: 0x38C6E
Logon Type: 3
Account For Which Logon Failed: Security ID: NULL SID Account Name: deanna Account Domain:
Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xC000006D Sub Status: 0xC0000064
Process Information: Caller Process ID: 0x9d0 Caller Process Name: C:\Windows\System32\inetsrv\w3wp.exe
Network Information: Workstation Name: XXXXXXXXXXXX Source Network Address: - Source Port: -
Detailed Authentication Information: Logon Process: Advapi
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 Transited Services: - Package Name (NTLM only): - Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
I installed EvlWatcher but it's not seeing these entries. Is it designed to?