Hi, I am currently using the following in a patternsdb.xml file and it is working well but I now need to exclude some of those matches.
<pattern>
<id>9</id>
<name>successful-logon</name>
<matchfield>
<name>Message</name>
<type>REGEXP</type>
<value>An account was successfully logged on</value>
</matchfield>
<exec>
exec_async("/bin/sh", "-c", 'echo "Message from ' + $Hostname + ' : ' +
$raw_event + '"|/usr/bin/mutt -s "Alert from ' + $Hostname + '" ' +
'emailaddr...@example.com' );
</exec>
</pattern>
The above pattern produces the email below
----------------------------------------------------------------------------
----------------------------------------------------
Message from SERVER : 2015-02-05 09:52:49 SERVER AUDIT_SUCCESS 4624 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-18
Account Name: SERVER$
Account Domain: AD-DOMAIN
Logon ID: 0xf7299b18
Logon GUID: {DF53F168-D034-4F68-A870-BB749FF4F4B9}
Process Information:
Process ID: 0x0
Process Name: -
Network Information:
Workstation Name:
Source Network Address: 127.0.0.1
Source Port: 0
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.
----------------------------------------------------------------------------
----------------------------------------------------
My question is how would I go about excluding the machine account logon?
Account Name: SERVER$
Thanks,
Paul Fontenot
Enterprise Key Management & Public Key Infrastructure | CS | EIS E&S | EIS |
Corp Risk | Wells Fargo
2600 S. Price Rd. 2nd Floor | Chandler, AZ 85286
MAC S3939-022
Cell (480) 253-2908
ward.p.fonte...@wellsfargo.com
This message may contain confidential and/or privileged information. If you
are not the addressee or authorized to receive this for the addressee, you
must not use, copy, disclose, or take any action based on this message or
any information herein. If you have received this message in error, please
advise the sender immediately by reply e-mail and delete this message. Thank
you for your cooperation.
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ nxlog-ce-users mailing list nxlog-ce-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
