<?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 Bulk update ESCU detections in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Bulk-update-ESCU-detections/m-p/760867#M12924</link>
    <description>&lt;P&gt;Is there a way to bulk update enabled ESCU detections when a new version with a lot of metadata changes like the MITRE changes in 5.27 are released? (This is with version detection enabled, ES version&amp;nbsp;8.3.0)&lt;/P&gt;</description>
    <pubDate>Mon, 11 May 2026 19:05:23 GMT</pubDate>
    <dc:creator>cseiler-gmp</dc:creator>
    <dc:date>2026-05-11T19:05:23Z</dc:date>
    <item>
      <title>Bulk update ESCU detections</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Bulk-update-ESCU-detections/m-p/760867#M12924</link>
      <description>&lt;P&gt;Is there a way to bulk update enabled ESCU detections when a new version with a lot of metadata changes like the MITRE changes in 5.27 are released? (This is with version detection enabled, ES version&amp;nbsp;8.3.0)&lt;/P&gt;</description>
      <pubDate>Mon, 11 May 2026 19:05:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Bulk-update-ESCU-detections/m-p/760867#M12924</guid>
      <dc:creator>cseiler-gmp</dc:creator>
      <dc:date>2026-05-11T19:05:23Z</dc:date>
    </item>
    <item>
      <title>Re: Bulk update ESCU detections</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Bulk-update-ESCU-detections/m-p/760869#M12925</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/317047"&gt;@cseiler-gmp&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How are you currently managing your ESCU rules? Do you just enable the ones that come with ESCU or are you cloning them and then enabling them?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":glowing_star:"&gt;🌟&lt;/span&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Did this answer help you?&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;If so, please consider:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Adding karma to show it was useful&lt;/LI&gt;&lt;LI&gt;Marking it as the solution if it resolved your issue&lt;/LI&gt;&lt;LI&gt;Commenting if you need any clarification&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Your feedback encourages the volunteers in this community to continue contributing&lt;/P&gt;</description>
      <pubDate>Mon, 11 May 2026 19:19:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Bulk-update-ESCU-detections/m-p/760869#M12925</guid>
      <dc:creator>livehybrid</dc:creator>
      <dc:date>2026-05-11T19:19:51Z</dc:date>
    </item>
    <item>
      <title>Re: Bulk update ESCU detections</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Bulk-update-ESCU-detections/m-p/760871#M12926</link>
      <description>&lt;P&gt;Currently just enabling them via Enterprise Security Content Management UI, not cloning them out unless we have a very specific logic change that would need to be made for our environment. The searches are still knowledge objects owned by ESCU.&lt;/P&gt;</description>
      <pubDate>Mon, 11 May 2026 19:21:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Bulk-update-ESCU-detections/m-p/760871#M12926</guid>
      <dc:creator>cseiler-gmp</dc:creator>
      <dc:date>2026-05-11T19:21:53Z</dc:date>
    </item>
  </channel>
</rss>

