<?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: TTY auditing in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/TTY-auditing/m-p/93064#M18467</link>
    <description>&lt;P&gt;Don’t know enough about how pam_tty_audit.so works to comment.&lt;BR /&gt;That said, an RFE would be needed.&lt;BR /&gt;You may also want to engage your local Check Point office with your precise requirements.&lt;/P&gt;</description>
    <pubDate>Sat, 01 Aug 2020 17:08:14 GMT</pubDate>
    <dc:creator>PhoneBoy</dc:creator>
    <dc:date>2020-08-01T17:08:14Z</dc:date>
    <item>
      <title>TTY auditing</title>
      <link>https://community.checkpoint.com/t5/General-Topics/TTY-auditing/m-p/92978#M18453</link>
      <description>&lt;P&gt;Hello, everyone!&lt;/P&gt;&lt;P&gt;Does anybody successfully configured audit-daemon at CP with module `pam_tty_audit.so`? The module`pam_tty_audit.so` doesn't exist in a standard package of CP but it exists in standard CentOS and RHEL editions.&lt;BR /&gt;I want to log and audit all characters passed into the console\tty from expert and clish shells. Existed audit methods in clish are not satisfied with me. Maybe someone knows the best decision for this task?&lt;/P&gt;</description>
      <pubDate>Fri, 31 Jul 2020 07:20:49 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/TTY-auditing/m-p/92978#M18453</guid>
      <dc:creator>AlexeyD</dc:creator>
      <dc:date>2020-07-31T07:20:49Z</dc:date>
    </item>
    <item>
      <title>Re: TTY auditing</title>
      <link>https://community.checkpoint.com/t5/General-Topics/TTY-auditing/m-p/93058#M18465</link>
      <description>&lt;P&gt;If you want support for pam_tty_audit.so, an RFE will likely be required.&lt;BR /&gt;Specific commands entered via clish and expert shell can be logged, but not “all characters passed.”&lt;/P&gt;</description>
      <pubDate>Sat, 01 Aug 2020 04:41:20 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/TTY-auditing/m-p/93058#M18465</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2020-08-01T04:41:20Z</dc:date>
    </item>
    <item>
      <title>Re: TTY auditing</title>
      <link>https://community.checkpoint.com/t5/General-Topics/TTY-auditing/m-p/93059#M18466</link>
      <description>&lt;P&gt;Existing audit methods (clish and expert-mode) don't log all passed commands. There are many flows that can give you unlogged command execution. The same fault may be caused if you try to log commands with profile's *.rc files. I think that the only proper solution is audit with the pam-module, isn't it?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 01 Aug 2020 08:06:14 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/TTY-auditing/m-p/93059#M18466</guid>
      <dc:creator>AlexeyD</dc:creator>
      <dc:date>2020-08-01T08:06:14Z</dc:date>
    </item>
    <item>
      <title>Re: TTY auditing</title>
      <link>https://community.checkpoint.com/t5/General-Topics/TTY-auditing/m-p/93064#M18467</link>
      <description>&lt;P&gt;Don’t know enough about how pam_tty_audit.so works to comment.&lt;BR /&gt;That said, an RFE would be needed.&lt;BR /&gt;You may also want to engage your local Check Point office with your precise requirements.&lt;/P&gt;</description>
      <pubDate>Sat, 01 Aug 2020 17:08:14 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/TTY-auditing/m-p/93064#M18467</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2020-08-01T17:08:14Z</dc:date>
    </item>
  </channel>
</rss>

