<?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: Rare Admin Login in Environment in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/rare-admin-login-in-environment/m-p/1224063#M8075</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/336272"&gt;@a2123k1&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;DIV class="p-rich_text_section"&gt;You should be able to accomplish this relatively simply, just using the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE class="c-mrkdwn__code" data-stringify-type="code"&gt;xdr_login_events&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;preset. you can adjust the final&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE class="c-mrkdwn__code" data-stringify-type="code"&gt;login_count&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;filter to whatever number of total events is rare enough for your user.&lt;BR /&gt;Just keep in mind that our OOTB analytics will do all this and more, with no extra work (just need the ITDR license). Any user logging into a host for the first time and doing&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;I data-stringify-type="italic"&gt;anything&lt;/I&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;on that host will generate alerts on that activity, far more effectively than a manual correlation rule&lt;/DIV&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV class="p-rich_text_block--no-overflow"&gt;config timeframe = 30d |preset = xdr_login_events |filter action_user_status = ACTION_LOGIN and outcome = "SUCCESS" and dst_is_machine_account = "false" and action_local_ip not in ("",":1","127.0.0.1") |alter identity = login_data_dst_normalized_user -&amp;gt; identity, domain = login_data_dst_normalized_user -&amp;gt; domain |fields identity, domain, agent_hostname as dest_host, action_local_ip as source_ip , action*, actor*, *dst*, src* |comp count() as login_count by identity, domain , dest_host, source_ip addrawdata = true as rawdata |filter login_count = 1&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="p-rich_text_block--no-overflow"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="p-rich_text_block--no-overflow"&gt;&lt;SPAN&gt;If you feel this has answered your query, please let us know by clicking like and&amp;nbsp; on "mark this as a Solution". Thank you.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 18 Mar 2025 05:21:33 GMT</pubDate>
    <dc:creator>aspatil</dc:creator>
    <dc:date>2025-03-18T05:21:33Z</dc:date>
    <item>
      <title>Rare Admin Login in Environment</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/rare-admin-login-in-environment/m-p/1223910#M8063</link>
      <description>&lt;P&gt;Hi guys, could anyone help me with the query I'm trying to do.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I'm looking to build an alert based on the rarity of a login in the environment. For instance, raise an alert if "admin" logged in to a device, but that action hasn't been seen in the device/IP for 30 days. As an additional action, cut off the connection from that host IP to the domain.&lt;BR /&gt;&lt;BR /&gt;I made a correlation alert based on this, unfortunately, I don't think this is the best way to do this, because:&lt;BR /&gt;&lt;BR /&gt;1. correlation is not real-time and can only raise an alert once it runs the query (every 10 minutes at a minimum).&lt;BR /&gt;2. You can't do a timeframe in correlation. So you can compare the log ins from 30 days ago to now. (config timeframe between "30d" and "now")&lt;BR /&gt;3. What's the use of drill-down if we can do a drill-down inside a query (join etc.)?&lt;BR /&gt;&lt;BR /&gt;Here's an example of the query, I transformed some of the fields for alert mapping.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;dataset = xdr_data&lt;BR /&gt;| filter event_type = EVENT_LOG&lt;BR /&gt;| filter action_evtlog_event_id in (4768, 4776, 4624, 4776) &lt;BR /&gt;| alter username = action_evtlog_data_fields -&amp;gt; TargetUserName, logon_status_desc = action_evtlog_data_fields -&amp;gt; Status, ip_address = trim(action_evtlog_data_fields -&amp;gt; IpAddress,":ffff:")&lt;BR /&gt;| alter logon_status = if(logon_status_desc = "0x0", "Successful")&lt;BR /&gt;| fields username, logon_status, ip_address, action_evtlog_data_fields, action_evtlog_message, action_evtlog_event_id, *&lt;BR /&gt;| filter logon_status = "Successful" // filter all successful login&lt;BR /&gt;| filter ((username contains "admin"&lt;BR /&gt;| filter instance &amp;lt;= 1&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Mar 2025 18:56:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/rare-admin-login-in-environment/m-p/1223910#M8063</guid>
      <dc:creator>a2123k1</dc:creator>
      <dc:date>2025-03-14T18:56:52Z</dc:date>
    </item>
    <item>
      <title>Re: Rare Admin Login in Environment</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/rare-admin-login-in-environment/m-p/1224063#M8075</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/336272"&gt;@a2123k1&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;DIV class="p-rich_text_section"&gt;You should be able to accomplish this relatively simply, just using the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE class="c-mrkdwn__code" data-stringify-type="code"&gt;xdr_login_events&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;preset. you can adjust the final&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE class="c-mrkdwn__code" data-stringify-type="code"&gt;login_count&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;filter to whatever number of total events is rare enough for your user.&lt;BR /&gt;Just keep in mind that our OOTB analytics will do all this and more, with no extra work (just need the ITDR license). Any user logging into a host for the first time and doing&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;I data-stringify-type="italic"&gt;anything&lt;/I&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;on that host will generate alerts on that activity, far more effectively than a manual correlation rule&lt;/DIV&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV class="p-rich_text_block--no-overflow"&gt;config timeframe = 30d |preset = xdr_login_events |filter action_user_status = ACTION_LOGIN and outcome = "SUCCESS" and dst_is_machine_account = "false" and action_local_ip not in ("",":1","127.0.0.1") |alter identity = login_data_dst_normalized_user -&amp;gt; identity, domain = login_data_dst_normalized_user -&amp;gt; domain |fields identity, domain, agent_hostname as dest_host, action_local_ip as source_ip , action*, actor*, *dst*, src* |comp count() as login_count by identity, domain , dest_host, source_ip addrawdata = true as rawdata |filter login_count = 1&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="p-rich_text_block--no-overflow"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="p-rich_text_block--no-overflow"&gt;&lt;SPAN&gt;If you feel this has answered your query, please let us know by clicking like and&amp;nbsp; on "mark this as a Solution". Thank you.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Mar 2025 05:21:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/rare-admin-login-in-environment/m-p/1224063#M8075</guid>
      <dc:creator>aspatil</dc:creator>
      <dc:date>2025-03-18T05:21:33Z</dc:date>
    </item>
    <item>
      <title>Re: Rare Admin Login in Environment</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/rare-admin-login-in-environment/m-p/1224805#M8129</link>
      <description>&lt;P&gt;Thanks! I'll reach out to my AE. Is there a technical documentation I can read in the meantime? I found this:&amp;nbsp;&lt;A href="https://www.paloaltonetworks.com/apps/pan/public/downloadResource?pagePath=/content/pan/en_US/resources/techbriefs/identity-threat-detection-and-response-module" target="_blank"&gt;Cortex Identity Threat Detection and Response Module&lt;/A&gt;, doesn't tell me much. Would this work with other non-xdr logs we brought in to Cortex i.e Azure logs etc.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Mar 2025 14:42:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/rare-admin-login-in-environment/m-p/1224805#M8129</guid>
      <dc:creator>a2123k1</dc:creator>
      <dc:date>2025-03-26T14:42:26Z</dc:date>
    </item>
  </channel>
</rss>

