Security Analytics - Need Help with rules for Administrator-level logins

[HoLarry]

Greeting,

Would like some advise on how to create a rule in Alerts > Configure > Rules.

I am using SA 10.4. I would like to create a rule that will trigger an alert, which will send an email to a designated address, when users with administrator-level login to a particular system. So far has not been successful. Below is the scenario:

1. Whether  the attempt is either successful or failed.  (Figure 2) AND

2. A user attempts to login using an administrative level username (Figure 3) AND

3. Also, this alert is based on a specified logon type (Figure 4), which is :

     a       physical/software-based login on a keyboard

     b.      via network

     c.       via RDP

A screen capture as below of the rule that i created.

.

The first condition as below

The 2nd condition

The 3rd condition

[AbhishekAgrawa1]

Can u provide some test logs sothat I can help u to create the rule.

[HoLarry]

Hi Abhisek,

An example is the below. Hope it helps.

I am using ESA rules.

Apr 6 06:40:55 10.0.0.1 MSWinEventLog,1,Security,71656,Wed Apr 06 06:40:54 2016,4625,Microsoft-Windows-Security-Auditing,company\admin,N/A,Failure Audit,company.com.sg,Logon,,An account failed to log on. Subject: Security ID: S-1-5-18 Account Name: companyName Account Domain: company Logon ID: 0x3E7 Logon Type: 2 Account For Which Logon Failed: Security ID: S-1-0-0 Account Name: admin Account Domain: company Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xC000006D Sub Status: 0xC000006A Process Information: Caller Process ID: 0x5e0 Caller Process Name: C:\Program Files\Microsoft Monitoring Agent\Agent\HealthService.exe Network Information: Workstation Name: companyStation Source Network Address: - Source Port: - Detailed Authentication Information: Logon Process: Advapi 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. 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. - Transited services indicate which intermediate services have participated in this logon request. - Package name indicates which sub-protocol was used among the NTLM protocols.

[huanzhou1]

question, is the logs parsing correctly which the required meta exists?

[HoLarry]

yes. The necessary metas are showing information:

1. event.cat.name

2. logon.type

3. user.dst

[Anonymous]

Have you thought of just doing it via the reporting engine?  The rule is really simple so ESA might over complicate things for you. 

Event.cat.name = 'user.activity.successful logins','user.activity.failed logins' && user.dst = $[/listname] && logon.type = '2','3','10'

Shove that in a rule then alert anytime it happens. 

[KEVINDIENST]

If you could look in ESA and use the "Show Syntax" button, please paste raw EPL or take screenshot and paste it in here. If parsing is working there is probably something simple in ESA syntax that is just jacked up.

[DavidWaugh1]

Also remember that the ESA rules are case sensitive, so looking for Event.cat.name = 'user.activity.successful logins' is different to Event.cat.name = 'User.Activity.Successful Logins'. In 10.6 there is now the option to Ignore Case.