<?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 Mission Control incidents in Security</title>
    <link>https://community.splunk.com/t5/Security/Mission-Control-incidents/m-p/674630#M17552</link>
    <description>&lt;P&gt;We are due to go line on the following Monday and we wanted to erase all of our Test mission control incidents so we have a clean slate, How is this possible?&lt;/P&gt;</description>
    <pubDate>Thu, 18 Jan 2024 10:12:43 GMT</pubDate>
    <dc:creator>faizalk786</dc:creator>
    <dc:date>2024-01-18T10:12:43Z</dc:date>
    <item>
      <title>Mission Control incidents</title>
      <link>https://community.splunk.com/t5/Security/Mission-Control-incidents/m-p/674630#M17552</link>
      <description>&lt;P&gt;We are due to go line on the following Monday and we wanted to erase all of our Test mission control incidents so we have a clean slate, How is this possible?&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 10:12:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Mission-Control-incidents/m-p/674630#M17552</guid>
      <dc:creator>faizalk786</dc:creator>
      <dc:date>2024-01-18T10:12:43Z</dc:date>
    </item>
  </channel>
</rss>

