On Fri, Aug 10, 2012 at 8:44 AM, Deerwalker
<
sysa...@system.deerwalk.com> wrote:
> hello All,
>
> Good day,
>
> We have configured active-response for windows machine as suggested in
>
http://www.ossec.net/doc/manual/ar/ar-windows.html
>
> while executing agent_control -b 1.2.3.6 -f win_nullroute600 -u 001 we are
> getting response below and we are also getting the null route added for the
> ip address 1.2.3.6 in target machine
>
> agent_control -b 1.2.3.6 -f win_nullroute600 -u 001
>
> OSSEC HIDS agent_control: Running active response 'win_nullroute600' on: 001
>
> However, when someone trying to make unauthorized access then at that time
> the active response seems not working because we are still getting multiple
> login failure message with following details.
>
> Rule: 18152 fired (level 10) -> "Multiple Windows Logon Failures."
> Portion of the log(s):
>
> WinEvtLog: Security: AUDIT_FAILURE(4625):
> Microsoft-Windows-Security-Auditing: (no user): no domain: ip-0A00FD07: An
> account failed to log on. Subject: Security ID: S-1-5-18 Account Name:
> IP-0A00FD07$ Account Domain: WORKGROUP Logon ID: 0x3e7 Logon Type: 10
> Account For Which Logon Failed: Security ID: S-1-0-0 Account Name:
> administrator Account Domain: IP-0A00FD07 Failure Information: Failure
> Reason: %%2313 Status: 0xc000006d Sub Status: 0xc000006a Process
> Information: Caller Process ID: 0x77c Caller Process Name:
> C:\Windows\System32\winlogon.exe Network Information: Workstation Name:
> IP-0A00FD07 Source Network Address: 115.236.163.106 Source Port: 55909
> Detailed Authentication Information: Logon Process: User32
> Authentication Package: Negotiate 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.
>
> any clue ?
>
> is there other way to know if active response is working or not ?
>
> thanks
>
On non-windows platforms there's an active response log file. Check to
see if one exists for Windows.
Also, double check to make sure that AR is enabled on the agent, and
that your test actually works (check on the agent).