<?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: CSA 6.0 Rule Creation in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/csa-6-0-rule-creation/m-p/1158885#M77873</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I will configure that, and update the thread. Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 23 Jan 2009 22:56:42 GMT</pubDate>
    <dc:creator>rz7dzmeds</dc:creator>
    <dc:date>2009-01-23T22:56:42Z</dc:date>
    <item>
      <title>CSA 6.0 Rule Creation</title>
      <link>https://community.cisco.com/t5/network-security/csa-6-0-rule-creation/m-p/1158883#M77869</link>
      <description>&lt;P&gt;I would like to create a File Access Control rule to generate an alert when the /var/adm/csalog is attempted to be modified on *nix systems. An Agent Service Control rule already generates an alert when this file is modified, however we need to isolate this activity down to a File Access Control rule. I have attempted to define the rule from scratch, however it's not working. Any guidance on this would be appreciated.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 11:28:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/csa-6-0-rule-creation/m-p/1158883#M77869</guid>
      <dc:creator>rz7dzmeds</dc:creator>
      <dc:date>2019-03-10T11:28:30Z</dc:date>
    </item>
    <item>
      <title>Re: CSA 6.0 Rule Creation</title>
      <link>https://community.cisco.com/t5/network-security/csa-6-0-rule-creation/m-p/1158884#M77871</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Create a new File Access control rule, make it as specific as possible on src application and filename/directory, and then make it a monitor rule, it will then log it no matter what other rules are in place.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Jan 2009 22:47:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/csa-6-0-rule-creation/m-p/1158884#M77871</guid>
      <dc:creator>jan.nielsen</dc:creator>
      <dc:date>2009-01-23T22:47:56Z</dc:date>
    </item>
    <item>
      <title>Re: CSA 6.0 Rule Creation</title>
      <link>https://community.cisco.com/t5/network-security/csa-6-0-rule-creation/m-p/1158885#M77873</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I will configure that, and update the thread. Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Jan 2009 22:56:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/csa-6-0-rule-creation/m-p/1158885#M77873</guid>
      <dc:creator>rz7dzmeds</dc:creator>
      <dc:date>2009-01-23T22:56:42Z</dc:date>
    </item>
  </channel>
</rss>

