No security events in dashboard

[Gianluca de Simone]

Hello team,

i have a strange problem on my wazuh server. I have a rule on "windows logon failure" with level 10 for monitoring server access. When wazuh generates an alert, i receive it on my email but i don't see it in Security Events on dashboard.  

This behavior is a problem when i generate report. 

Do you have any suggestions?

Thanks in advance for your cooperation.

[Marcelo Hamra]

Hi Gianluca,

I assume you've created a custom ruleset for the Windows logon failure from your post. To help you better answer your question, please post the custom decoders, custom rules, and examples of the events received by the wazuh manager.

[Marcelo Hamra]

I'm copying the private message you've sent below:

Hi Marcelo,

Custom rule
<rule id="60204" level="10" frequency="12" timeframe="240" overwrite="yes">
    <if_matched_group>authentication_failed</if_matched_group>
    <same_field>win.eventdata.ipAddress</same_field>
    <field name="win.system.computer" negate="yes">hostname</field>
    <options>no_full_log</options>
    <description>Multiple Windows logon failures.</description>
    <mitre>
      <id>T1110</id>
    </mitre>
    <group>authentication_failures,gdpr_IV_32.2,gdpr_IV_35.7.d,hipaa_164.312.b,nist_800_53_AC.7,nist_800_53_AU.14,nist_800_53_SI.4,pci_dss_10.2.4,pci_dss_10.2.5,pci_dss_11.4,tsc_CC6.1,tsc_CC6.8,tsc_CC7.2,tsc_CC7.3,</group>
  </rule>

event on alert.log  
{"win":{"system":{"providerName":"Microsoft-Windows-Security-Auditing","providerGuid":"{54849625-5478-4994-A5BA-3E3B0328C30D}","eventID":"4625","version":"0","level":"0","task":"12544","opcode":"0","keywords":"0x8010000000000000","systemTime":"2024-05-09T12:31:30.005693100Z","eventRecordID":"185915002","processID":"768","threadID":"4704","channel":"Security","computer":"hostname","severityValue":"AUDIT_FAILURE","message":"\"An account failed to log on.\r\n\r\nSubject:\r\n\tSecurity ID:\t\tS-1-5-18\r\n\tAccount Name:\t\txxx\r\n\tAccount Domain:\t\txxx\r\n\tLogon ID:\t\t0x3E7\r\n\r\nLogon Type:\t\t\t3\r\n\r\nAccount For Which Logon Failed:\r\n\tSecurity ID:\t\tS-1-0-0\r\n\tAccount Name:\t\txxx\r\n\tAccount Domain:\t\txxx\r\n\r\nFailure Information:\r\n\tFailure Reason:\t\tUnknown user name or bad password.\r\n\tStatus:\t\t\t0xC000006D\r\n\tSub Status:\t\t0xC000006A\r\n\r\nProcess Information:\r\n\tCaller Process ID:\t0x300\r\n\tCaller Process Name:\tC:\\Windows\\System32\\lsass.exe\r\n\r\nNetwork Information:\r\n\tWorkstation Name:\txxx\r\n\tSource Network Address:\txxx\r\n\tSource Port:\t\t49210\r\n\r\nDetailed Authentication Information:\r\n\tLogon Process:\t\tAdvapi  \r\n\tAuthentication Package:\tMICROSOFT_AUTHENTICATION_PACKAGE_V1_0\r\n\tTransited Services:\t-\r\n\tPackage Name (NTLM only):\t-\r\n\tKey Length:\t\t0\r\n\r\nThis event is generated when a logon request fails. It is generated on the computer where access was attempted.\r\n\r\nThe 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.\r\n\r\nThe Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).\r\n\r\nThe Process Information fields indicate which account and process on the system requested the logon.\r\n\r\nThe Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.\r\n\r\nThe authentication information fields provide detailed information about this specific logon request.\r\n\t- Transited services indicate which intermediate services have participated in this logon request.\r\n\t- Package name indicates which sub-protocol was used among the NTLM protocols.\r\n\t- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.\""},"eventdata":{"subjectUserSid":"S-1-5-18","subjectUserName":"xxx","subjectDomainName":"xxx","subjectLogonId":"0x3e7","targetUserSid":"S-1-0-0","targetUserName":"xxx","targetDomainName":"xxx","status":"0xc000006d","failureReason":"%%2313","subStatus":"0xc000006a","logonType":"3","logonProcessName":"Advapi","authenticationPackageName":"MICROSOFT_AUTHENTICATION_PACKAGE_V1_0","workstationName":"xxx","keyLength":"0","processId":"0x300","processName":"C:\\\\Windows\\\\System32\\\\lsass.exe","ipAddress":"xxx","ipPort":"49210"}}}


default windows decoder
<decoder name="windows_fields">
  <type>windows</type>
  <parent>windows</parent>
  <regex>Subject\s*:\t*\s*Security ID:\t*\s*(\S\S+)\t*\s*Account Name:\t*\s*(\S\S+)\t*\s*Account Domain:\t*\s*(\S\S+)\t*\s*Logon ID:\t*\s*(\S\S+)</regex>
  <order>subject.security_id, subject.account_name, subject.account_domain, subject.logon_id</order>
</decoder>

<decoder name="windows_fields">
  <type>windows</type>
  <parent>windows</parent>
  <regex offset="after_regex">Security ID:\t*\s*(\S\S+)</regex>
  <order>security_id</order>
</decoder>

<decoder name="windows_fields">
  <type>windows</type>
  <parent>windows</parent>
  <regex offset="after_regex">Account Name:\t*\s*(\S\S+)</regex>
  <order>account_name</order>
</decoder>

<decoder name="windows_fields">
  <type>windows</type>
  <parent>windows</parent>
  <regex offset="after_regex">Account Domain:\t*\s*(\S\S+)\t*\s*</regex>
  <order>account_domain</order>
</decoder>

<decoder name="windows_fields">
  <type>windows</type>
  <parent>windows</parent>
  <regex>Logon Type:\t*\s*(\S+)</regex>
  <order>logon_type</order>
</decoder>

<decoder name="windows_fields">
  <type>windows</type>
  <parent>windows</parent>
  <regex>Caller Computer Name:\t*\s*(\S+)</regex>
  <order>caller_computer</order>
</decoder>

<decoder name="windows_fields">
  <type>windows</type>
  <parent>windows</parent>
  <regex>Accesses:\s+(\.+)\s+Access Mask:|Accesses:\t+(\.+)Access Mask:</regex>
  <order>accesses</order>
</decoder>

<decoder name="windows_fields">
  <type>windows</type>
  <parent>windows</parent>
  <regex>File\s+Object Name:\s+(\w\.+)\s+Handle ID:|File\t+Object Name:\t+(\w\.+)\t+Handle ID:</regex>
  <order>target_file</order>

</decoder> 

[Marcelo Hamra]

Hi Gianluca,

If the manager sends the alerts by mail but the alert is not visible in your dashboard, something may go wrong when Filebeat tries to send the alert to the Wazuh-indexer.

1. Please check if the alerts are in the /var/ossec/logs/alerts/alerts.log or /var/ossec/logs/alerts/alerts.json files.
2. Could you check the errors in the filebeat log? Please post the output of this command: cat /var/log/filebeat/filebeat | grep -i -E "error|warn"
   
3. Could you check the errors in the Wazuh-indexer log? Please post the output of this command: cat /var/log/wazuh-indexer/wazuh-cluster.log | grep -i -E "error|warn"

[Gianluca de Simone]

Hi Marcelo,
thank you for your answer, here is the output of the checks you asked for:

1. Yes, the alerts are present in /var/ossec/logs/alerts/alerts.log;
2. There are no errors in the filebeat logs;
3. Here is the output of the command cat /var/log/wazuh-indexer/wazuh-cluster.log | grep -i -E "error|warn":
[2024-05-10T01:58:16,162][ERROR][o.o.a.a.AlertIndices     ] [node-1] info deleteOldIndices
[2024-05-10T01:58:16,163][ERROR][o.o.a.a.AlertIndices     ] [node-1] info deleteOldIndices
[2024-05-10T01:58:16,234][ERROR][o.o.s.i.DetectorIndexManagementService] [node-1] info deleteOldIndices
[2024-05-10T01:58:16,237][ERROR][o.o.s.i.DetectorIndexManagementService] [node-1] info deleteOldIndices
[2024-05-10T13:58:16,175][ERROR][o.o.a.a.AlertIndices     ] [node-1] info deleteOldIndices
[2024-05-10T13:58:16,184][ERROR][o.o.a.a.AlertIndices     ] [node-1] info deleteOldIndices
[2024-05-10T13:58:16,235][ERROR][o.o.s.i.DetectorIndexManagementService] [node-1] info deleteOldIndices
[2024-05-10T13:58:16,237][ERROR][o.o.s.i.DetectorIndexManagementService] [node-1] info deleteOldIndices

[Marcelo Hamra]

Hi Gianluca,

I assumed you only have problems with the Windows logon event/alert; other events are visible in your wazuh dashboard. Please confirm.

Could you please share an example of the original event? We will try to reproduce the environment to help you. 

You can obtain the event XML text from the Windows Event viewer. Once you find the original event that generates the alert, you'll have to select it. Clicking on the event should open an actions pane on the right. Right-clicking on the event ID should open a popup menu with the option "copy details as text." After that, you'll have to paste and post an XML message.

Thanks

Marcelo

[Gianluca de Simone]

Hi Marcelo,

this is the XML text about Windows logon alert:

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          14/05/2024 14:17:55
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      ***************
Description:

An account failed to log on.

Subject:
Security ID: ***************
Account Name: ***************
Account Domain: ***************
Logon ID: 0x3E7

Logon Type: 3

Account For Which Logon Failed:
Security ID: NULL SID
Account Name: gdesimone
Account Domain: ***************

Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC000006A

Process Information:
Caller Process ID: 0x300
Caller Process Name: C:\Windows\System32\lsass.exe

Network Information:
Workstation Name: ***************
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.

- Transited services indicate which intermediate services have participated in this logon request.

- Package name indicates which sub-protocol was used among the NTLM protocols.

- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
    <EventID>4625</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>12544</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8010000000000000</Keywords>
    <TimeCreated SystemTime="2024-05-14T12:17:55.280510100Z" />
    <EventRecordID>186452083</EventRecordID>
    <Correlation />
    <Execution ProcessID="768" ThreadID="10144" />
    <Channel>Security</Channel>
    <Computer>***************</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="SubjectUserSid">S-1-5-18</Data>
    <Data Name="SubjectUserName">***************</Data>
    <Data Name="SubjectDomainName">***************</Data>
    <Data Name="SubjectLogonId">0x3e7</Data>
    <Data Name="TargetUserSid">S-1-0-0</Data>
    <Data Name="TargetUserName">gdesimone</Data>
    <Data Name="TargetDomainName">***************</Data>
    <Data Name="Status">0xc000006d</Data>
    <Data Name="FailureReason">%%2313</Data>
    <Data Name="SubStatus">0xc000006a</Data>
    <Data Name="LogonType">3</Data>
    <Data Name="LogonProcessName">Advapi  </Data>
    <Data Name="AuthenticationPackageName">MICROSOFT_AUTHENTICATION_PACKAGE_V1_0</Data>
    <Data Name="WorkstationName">***************</Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">-</Data>
    <Data Name="KeyLength">0</Data>
    <Data Name="ProcessId">0x300</Data>
    <Data Name="ProcessName">C:\Windows\System32\lsass.exe</Data>
    <Data Name="IpAddress">***************</Data>
    <Data Name="IpPort">***************</Data>
  </EventData>
</Event>

I confirm that the problem is on windows logon.

Thank you,

 

--
You received this message because you are subscribed to a topic in the Google Groups "Wazuh | Mailing List" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/wazuh/kwz4TkXiNOg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to wazuh+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wazuh/0c24829f-62ee-41f7-b947-ddd0e46cfdecn%40googlegroups.com.

[Raul Del Pozo Moreno]

Hi Gianluca, can you confirm if your problem is resolved or if you need more assistance? I understand that you have found where the failure point is, but just in case, tell me if we can do something else for you or we can conclude the thread, thank you!