<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to filter Windows Security Event Logs Output? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-Windows-Security-Event-Logs-Output/m-p/249013#M99172</link>
    <description>&lt;P&gt;if its Standard Windows Eventlogs, please use &lt;A href="https://splunkbase.splunk.com/app/742/#/overview"&gt;Windows Addon (TA)&lt;/A&gt;&lt;BR /&gt;
This will extract all the fields and is  Common Information Model (CIM) compatible for future proof&lt;/P&gt;</description>
    <pubDate>Wed, 16 Mar 2016 15:58:57 GMT</pubDate>
    <dc:creator>koshyk</dc:creator>
    <dc:date>2016-03-16T15:58:57Z</dc:date>
    <item>
      <title>How to filter Windows Security Event Logs Output?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-Windows-Security-Event-Logs-Output/m-p/249011#M99170</link>
      <description>&lt;P&gt;Hello, I understand this question had been ask before in varies variations, but I am a newbie and I’m trying to filter out the following information below. I would like to keep everything after Logon Type 3 and before Detail Authentication and if possible filter everything else out. I am using Windows 7 and I don’t have an AD (Active Directory) and Windows Infrastructure won’t work since I don’t have an AD. I’m just using Splunk with add-ons. From the research I’ve done and been unsuccessful with, there is the regex expression or just entering in a better query. If it’s not possible to filter the areas I want out, I would settle for just getting rid of the paragraph at the button starting with: “This event is generated when a logon request fails”&lt;BR /&gt;
Thank you&lt;/P&gt;

&lt;P&gt;03/13/2016 10:57:20 AM&lt;BR /&gt;
LogName=Security&lt;BR /&gt;
SourceName=Microsoft Windows security auditing.&lt;BR /&gt;
EventCode=4625&lt;BR /&gt;
EventType=0&lt;BR /&gt;
Type=Information&lt;BR /&gt;
ComputerName=pedrt2012-PC&lt;BR /&gt;
TaskCategory=Logon&lt;BR /&gt;
OpCode=Info&lt;BR /&gt;
RecordNumber=43158&lt;BR /&gt;
Keywords=Audit Failure&lt;BR /&gt;
Message=An account failed to log on&lt;/P&gt;

&lt;P&gt;Subject:&lt;BR /&gt;
    Security ID:        S-1-0-0&lt;BR /&gt;
    Account Name:       -&lt;BR /&gt;
    Account Domain:     -&lt;BR /&gt;
    Logon ID:       0x0&lt;/P&gt;

&lt;P&gt;Logon Type:         3&lt;/P&gt;

&lt;P&gt;Account For Which Logon Failed:&lt;BR /&gt;
    Security ID:        S-1-0-0&lt;BR /&gt;
    Account Name:       pedro 2012&lt;BR /&gt;
    Account Domain:     &lt;/P&gt;

&lt;P&gt;Failure Information:&lt;BR /&gt;
    Failure Reason:     Unknown user name or bad password.&lt;BR /&gt;
    Status:         0xc000006d&lt;BR /&gt;
    Sub Status:     0xc000006a&lt;/P&gt;

&lt;P&gt;Process Information:&lt;BR /&gt;
    Caller Process ID:  0x0&lt;BR /&gt;
    Caller Process Name:    -&lt;/P&gt;

&lt;P&gt;Network Information:&lt;BR /&gt;
    Workstation Name:   192.167.1.192&lt;BR /&gt;
    Source Network Address: -&lt;BR /&gt;
    Source Port:        -&lt;/P&gt;

&lt;P&gt;Detailed Authentication Information:&lt;BR /&gt;
    Logon Process:      NtLmSsp &lt;BR /&gt;
    Authentication Package: NTLM&lt;BR /&gt;
    Transited Services: -&lt;BR /&gt;
    Package Name (NTLM only):   -&lt;BR /&gt;
    Key Length:     0&lt;/P&gt;

&lt;P&gt;This event is generated when a logon request fails. It is generated on the computer where access was attempted.&lt;/P&gt;

&lt;P&gt;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.&lt;/P&gt;

&lt;P&gt;The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).&lt;/P&gt;

&lt;P&gt;The Process Information fields indicate which account and process on the system requested the logon.&lt;/P&gt;

&lt;P&gt;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.&lt;/P&gt;

&lt;P&gt;The authentication information fields provide detailed information about this specific logon request.&lt;BR /&gt;
    - Transited services indicate which intermediate services have participated in this logon request.&lt;BR /&gt;
    - Package name indicates which sub-protocol was used among the NTLM protocols.&lt;BR /&gt;
    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.&lt;BR /&gt;
Collapse&lt;BR /&gt;
host = pedro2012-PC source = WinEventLog:Security sourcetype = WinEventLog:Security&lt;/P&gt;</description>
      <pubDate>Tue, 15 Mar 2016 21:09:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-Windows-Security-Event-Logs-Output/m-p/249011#M99170</guid>
      <dc:creator>L06141</dc:creator>
      <dc:date>2016-03-15T21:09:11Z</dc:date>
    </item>
    <item>
      <title>Re: How to filter Windows Security Event Logs Output?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-Windows-Security-Event-Logs-Output/m-p/249012#M99171</link>
      <description>&lt;P&gt;Hi there mate,&lt;/P&gt;

&lt;P&gt;Take a look at this, and you will probably understand how to strip the event as you wish. &lt;/P&gt;

&lt;P&gt;This example will remove event description. Add this to your props.conf and restart Splunk.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[yoursourctype]
SEDCMD-del_desc = s/(?mis)This event is generated.*$//g
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Or like this, to remove distinct types of event descriptions in the same regex.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[yoursourctype]
SEDCMD-del_desc = s/(?mis)(This event is generated|other_type_of desc_1|other_type_of_desc_2).*$//g
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Oh, and remember, events already indexed wont change after this but the new ones does.&lt;/P&gt;

&lt;P&gt;Hope it helps and let me know if it works.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Mar 2016 14:47:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-Windows-Security-Event-Logs-Output/m-p/249012#M99171</guid>
      <dc:creator>alemarzu</dc:creator>
      <dc:date>2016-03-16T14:47:15Z</dc:date>
    </item>
    <item>
      <title>Re: How to filter Windows Security Event Logs Output?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-Windows-Security-Event-Logs-Output/m-p/249013#M99172</link>
      <description>&lt;P&gt;if its Standard Windows Eventlogs, please use &lt;A href="https://splunkbase.splunk.com/app/742/#/overview"&gt;Windows Addon (TA)&lt;/A&gt;&lt;BR /&gt;
This will extract all the fields and is  Common Information Model (CIM) compatible for future proof&lt;/P&gt;</description>
      <pubDate>Wed, 16 Mar 2016 15:58:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-Windows-Security-Event-Logs-Output/m-p/249013#M99172</guid>
      <dc:creator>koshyk</dc:creator>
      <dc:date>2016-03-16T15:58:57Z</dc:date>
    </item>
  </channel>
</rss>

