<?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: Restrict access to LOM in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Restrict-access-to-LOM/m-p/207260#M39167</link>
    <description>&lt;P&gt;Typically it would be connected to a management network or other out-of-band network where access into it is limited.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 27 Feb 2024 11:30:37 GMT</pubDate>
    <dc:creator>Chris_Atkinson</dc:creator>
    <dc:date>2024-02-27T11:30:37Z</dc:date>
    <item>
      <title>Restrict access to LOM</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Restrict-access-to-LOM/m-p/207089#M39140</link>
      <description>&lt;P&gt;Hello to all. I have use this forum a lot to solve some issues with CP products but this is the first time to post here. Yesterday I upgraded our customers 6200 from R81.10 to R81.20 take 41 I also upgrade the lom firmware from 6.10 to 6.20 Then I started to wonder what is the actual idea of the lom security. I read a lot documents but haven't found anything how to restrict the access to the lom. If we just connect it to the internet anyone can access to the login page of lom. But what is the point having lom just connected behind the firewall when it comes useless if the firewall fails for some reason and customer needs remote support.&lt;/P&gt;&lt;P&gt;Or maybe I just have missed something or haven't found anything to restirct the traffic.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 25 Feb 2024 07:10:32 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Restrict-access-to-LOM/m-p/207089#M39140</guid>
      <dc:creator>Simo-Kerberos</dc:creator>
      <dc:date>2024-02-25T07:10:32Z</dc:date>
    </item>
    <item>
      <title>Re: Restrict access to LOM</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Restrict-access-to-LOM/m-p/207250#M39165</link>
      <description>&lt;P&gt;As far as I can find this is not possible. I see it is possible in other LOM cards but not this one.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Feb 2024 10:54:09 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Restrict-access-to-LOM/m-p/207250#M39165</guid>
      <dc:creator>Lesley</dc:creator>
      <dc:date>2024-02-27T10:54:09Z</dc:date>
    </item>
    <item>
      <title>Re: Restrict access to LOM</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Restrict-access-to-LOM/m-p/207260#M39167</link>
      <description>&lt;P&gt;Typically it would be connected to a management network or other out-of-band network where access into it is limited.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Feb 2024 11:30:37 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Restrict-access-to-LOM/m-p/207260#M39167</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2024-02-27T11:30:37Z</dc:date>
    </item>
  </channel>
</rss>

