<?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: Salesforceのログについて in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Salesforce%E3%81%AE%E3%83%AD%E3%82%B0%E3%81%AB%E3%81%A4%E3%81%84%E3%81%A6/m-p/579333#M201878</link>
    <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/241705"&gt;@satiku&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(I am answering based on the translation provided by&amp;nbsp;&lt;A href="https://translate.google.com/" target="_blank" rel="noopener"&gt;https://translate.google.com/&lt;/A&gt;.)&lt;/P&gt;&lt;P&gt;In the following examples, replace index=sfdc with your Salesforce index. If you are using Splunk Add-on for Salesforce, authentication events have tag=authentication.&lt;/P&gt;&lt;P&gt;Search for users who logged in two weeks ago but have not logged in during the last week:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;index=sfdc tag=authentication user=* action=success earliest=-2w latest=-1w NOT [ search index=sfdc tag=authentication user=* action=success earliest=-1w latest=now | stats latest(_time) as _time by user | table user ]&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I do not know what a locked user looks like in Salesforce logs, but if we assume login failures lead to locked users, we can look for failures for multiple users from the same source:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;index=sfdc tag=authentication user=* action=failure
| eventstats dc(user) as user_count by src
| where user_count&amp;gt;1&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;These examples can be adapted to use the Authentication data model as well, but you would want to filter by the app field or another field specific to Salesforce.&lt;/P&gt;</description>
    <pubDate>Mon, 27 Dec 2021 16:40:38 GMT</pubDate>
    <dc:creator>tscroggins</dc:creator>
    <dc:date>2021-12-27T16:40:38Z</dc:date>
    <item>
      <title>Salesforceのログについて</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Salesforce%E3%81%AE%E3%83%AD%E3%82%B0%E3%81%AB%E3%81%A4%E3%81%84%E3%81%A6/m-p/579169#M201836</link>
      <description>&lt;P&gt;Salesforceのログにて以下の要件でSPLを作成したいと考えております。&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;①1週間以上 、 毎日複数回ログインを失敗しているユーザ&amp;nbsp;&lt;BR /&gt;②同一IP で複数のユーザ ID に対してログインロックされているユーザの検知&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;どのようなSPLをかけばよいでしょうか。&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Dec 2021 09:25:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Salesforce%E3%81%AE%E3%83%AD%E3%82%B0%E3%81%AB%E3%81%A4%E3%81%84%E3%81%A6/m-p/579169#M201836</guid>
      <dc:creator>satiku</dc:creator>
      <dc:date>2021-12-23T09:25:42Z</dc:date>
    </item>
    <item>
      <title>Re: Salesforceのログについて</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Salesforce%E3%81%AE%E3%83%AD%E3%82%B0%E3%81%AB%E3%81%A4%E3%81%84%E3%81%A6/m-p/579333#M201878</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/241705"&gt;@satiku&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(I am answering based on the translation provided by&amp;nbsp;&lt;A href="https://translate.google.com/" target="_blank" rel="noopener"&gt;https://translate.google.com/&lt;/A&gt;.)&lt;/P&gt;&lt;P&gt;In the following examples, replace index=sfdc with your Salesforce index. If you are using Splunk Add-on for Salesforce, authentication events have tag=authentication.&lt;/P&gt;&lt;P&gt;Search for users who logged in two weeks ago but have not logged in during the last week:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;index=sfdc tag=authentication user=* action=success earliest=-2w latest=-1w NOT [ search index=sfdc tag=authentication user=* action=success earliest=-1w latest=now | stats latest(_time) as _time by user | table user ]&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I do not know what a locked user looks like in Salesforce logs, but if we assume login failures lead to locked users, we can look for failures for multiple users from the same source:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;index=sfdc tag=authentication user=* action=failure
| eventstats dc(user) as user_count by src
| where user_count&amp;gt;1&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;These examples can be adapted to use the Authentication data model as well, but you would want to filter by the app field or another field specific to Salesforce.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Dec 2021 16:40:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Salesforce%E3%81%AE%E3%83%AD%E3%82%B0%E3%81%AB%E3%81%A4%E3%81%84%E3%81%A6/m-p/579333#M201878</guid>
      <dc:creator>tscroggins</dc:creator>
      <dc:date>2021-12-27T16:40:38Z</dc:date>
    </item>
  </channel>
</rss>

