нормализует через cli и из исходников, и из графа

компилируется и через cli, и через ptkb

и используется ли полный набор формул нормализации при компиляции через sdk, или собирается граф из единственной формулы

полный набор

версии sdk на ptkb и через cli совпадают?

да, ипользую те, что с дистрибутивом шли

чистая установка или обновлялись?

чистая

а как выглядит ненормализованное событие, если его из ластика дернуть?

# <13>Jan 22 22:39:45 host AgentDevice=WindowsLog\tAgentLogFile=Security\tPluginVersion=7.2.8.145\tSource=Microsoft-Windows-Security-Auditing\tComputer=host\tOriginatingComputer=ip\tUser=\tDomain=\tEventID=4624\tEventIDCode=4624\tEventType=8\tEventCategory=12544\tRecordNumber=153259678\tTimeGenerated=1548185958\tTimeWritten=1548185958\tLevel=Log Always\tKeywords=Audit Success\tTask=SE_ADT_LOGON_LOGON\tOpcode=Info\tMessage=An account was successfully logged on.  Subject:  Security ID:  NULL SID  Account Name:  -  Account Domain:  -  Logon ID:  0x0  Logon Type:   3  Impersonation Level:  Impersonation  New Logon:  Security ID:  user  Account Name:  user  Account Domain:  domain  Logon ID:  0x99E6818F0  Logon GUID:  {00000000-0000-0000-0000-000000000000}  Process Information:  Process ID:  0x0  Process Name:  -  Network Information:  Workstation Name: host2  Source Network Address: ip2  Source Port:  57929  Detailed Authentication Information:  Logon Process:  NtLmSsp   Authentication Package: NTLM  Transited Services: -  Package Name (NTLM only): NTLM V2  Key Length:  128  This event is generated when a logon session is created. It is generated on the computer that was accessed.  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 occurred. The most common types are 2 (interactive) and 3 (network).  The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.  The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.  The impersonation level field indicates the extent to which a process in the logon session can impersonate.  The authentication information fields provide detailed information about this specific logon request.  - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.  - 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.

только предупреждаю, что ip я заменил на ip и ip2

ещё раз, ненормализованное событие, вместе с конвертом, после попадания через siem в elastic

{"corrections": {"time_delta": 0, "time_zone": 10800}, "uuid": "00000005-c4db-02f9-f000-02cde96f687b", "tag": "syslog", "recv_ipv4": "10.100.200.54", "type": "raw", "job_id": "7b686fe9-e577-4c4c-914c-3159074cb1b5", "body": "<13>Jan 27 16:32:45 dc2.domain.ru AgentDevice=WindowsLog\tAgentLogFile=Security\tPluginVersion=7.2.8.145\tSource=Microsoft-Windows-Security-Auditing\tComputer=dc2.domain.ru\tOriginatingComputer=192.168.5.51\tUser=\tDomain=\tEventID=4624\tEventIDCode=4624\tEventType=8\tEventCategory=12544\tRecordNumber=102376199\tTimeGenerated=1548595957\tTimeWritten=1548595957\tLevel=Log Always\tKeywords=Audit Success\tTask=SE_ADT_LOGON_LOGON\tOpcode=Info\tMessage=An account was successfully logged on.  Subject:  Security ID:  NULL SID  Account Name:  -  Account Domain:  -  Logon ID:  0x0  Logon Type:   3  Impersonation Level:  Delegation  New Logon:  Security ID:  DOMAIN\\USER$  Account Name:  USER$  Account Domain:  DOMAIN  Logon ID:  0x37A3E275  Logon GUID:  {31E3F3A4-170A-CF01-59DF-CB74285B7BD1}  Process Information:  Process ID:  0x0  Process Name:  -  Network Information:  Workstation Name: -  Source Network Address: 192.168.7.7  Source Port:  59266  Detailed Authentication Information:  Logon Process:  Kerberos  Authentication Package: Kerberos  Transited Services: -  Package Name (NTLM only): -  Key Length:  0  This event is generated when a logon session is created. It is generated on the computer that was accessed.  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 occurred. The most common types are 2 (interactive) and 3 (network).  The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.  The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.  The impersonation level field indicates the extent to which a process in the logon session can impersonate.  The authentication information fields provide detailed information about this specific logon request.  - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.  - 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.", "agent_id": "f6e886e7-d072-42a0-96cc-ef7972c05da5", "historical": false, "tenant_id": "00000000-0000-0000-0000-000000000004", "recv_time": "2019-01-27T13:32:41Z", "normalized": false, "scope_id": "00000000-0000-0000-0000-000000000005", "site_id": "00000000-0000-0000-0000-000000000000", "mime": "text/plain", "task_id": "10a9ffda-0cc0-0001-0000-000000000002", "input_id": "9f040f3d-d57c-4a38-947c-9eb85202b414"}

ваша формула не нормализует данное событие

по всей видимости, вы некорректно извлекли событие из конверта

очень простенький питонный скрипт, на вход рвым параметром имя файла с событием из базы, на выходе в stdout - текст исходного события, как его видит siem

stdout рекомендуется сразу форвардить в файл

питон 3й версии

спасибо, разбираюсь