Некорректное срабатывание датчика при п&
Логи Windows в связке с rsyslog собираются на centOS тачку. Парсинг логов настроил, НО при создании триггера
- создание нового пользователя на кд (Win2008) он отправляет событие по ID - 4624
Причем я бы понял взаимосвязь, если бы в описании был тот пользователь, который создал новую учетку, так нет - совершенно никак не связанный с этим. Возможно триггер некорректно настроен? Версия zabbix- server 3.0, zabbix-agent 3.0
Code:
{Logmonitor:log[/var/log/windows/DC3.log].str(4720)}=1
Code:
Value: <29>1 2016-07-26T10:02:20+03:00 XXXXXXX Security-Auditing - - 4624: AUDIT_SUCCESS An account was successfully logged on. Subject: Security ID: S-1-0-0 Account Name: - Account Domain: - Logon ID: 0x0 Logon Type: 3 New Logon: Security ID: S-1-5-21-4063185021-3864391926-1917589314-12892 Account Name:XXXXXXX Account Domain: IDB Logon ID: 0x478321d Logon GUID: {2F122A78-67CE-0405-D9EC-BDC2954FDF67} Process Information: Process ID: 0x0 Process Name: - Network Information: Workstation Name: Source Network Address: xxx.xxx.xxx.xxx Source Port: XXXXX 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 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.
Comment