<?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: Feature Request - Highlight the policies we have to install when make some changes in an object in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Feature-Request-Highlight-the-policies-we-have-to-install-when/m-p/230190#M38411</link>
    <description>&lt;P&gt;RFE is your best bet.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
    <pubDate>Fri, 18 Oct 2024 19:49:35 GMT</pubDate>
    <dc:creator>the_rock</dc:creator>
    <dc:date>2024-10-18T19:49:35Z</dc:date>
    <item>
      <title>Feature Request - Highlight the policies we have to install when make some changes in an object</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Feature-Request-Highlight-the-policies-we-have-to-install-when/m-p/230109#M38400</link>
      <description>&lt;P&gt;We have an environment with 4 clusters and 2 small business appliances all connected to the same management server.&lt;/P&gt;&lt;P&gt;Each one of these cluster/small business have a dedicated policy but they are sharing the same set of objects.&lt;/P&gt;&lt;P&gt;When we make changes into the objects to implement something in a specific policy of a specific cluster we are not able to know if these changes could impact also other clusters or not. (Now it's not so easy to verify where all the X modified objects are used when you have Y policies with Z rules; with X, Y and Z as large as desired).&lt;/P&gt;&lt;P&gt;What normally happens is that we make some changes in an object used in the cluster A, but we forgot that the same object is used also into the cluster B and C. Se we install the policy on cluster A until some user phone us to tell that something is not working as expected.&lt;/P&gt;&lt;P&gt;Our request is: in a future release, could you add a feature to highlight all the policies that we have to install to implement all the commits made up to that point?&lt;/P&gt;&lt;P&gt;What do you think?&lt;/P&gt;&lt;P&gt;Thanks...&lt;/P&gt;</description>
      <pubDate>Fri, 18 Oct 2024 08:01:38 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Feature-Request-Highlight-the-policies-we-have-to-install-when/m-p/230109#M38400</guid>
      <dc:creator>gianogli</dc:creator>
      <dc:date>2024-10-18T08:01:38Z</dc:date>
    </item>
    <item>
      <title>Re: Feature Request - Highlight the policies we have to install when make some changes in an object</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Feature-Request-Highlight-the-policies-we-have-to-install-when/m-p/230178#M38408</link>
      <description>&lt;P&gt;You can figure this out easily enough by using "Where Used" on any object you modify.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="image.png" style="width: 346px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/28120i73716242EA12BE5D/image-size/medium?v=v2&amp;amp;px=400" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This will show every policy is used in and where:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="image.png" style="width: 400px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/28121i3E29C35B7471604E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Of course, it won't tell you what policy packages are applicable to which gateways.&lt;BR /&gt;You might want &lt;A href="https://usercenter.checkpoint.com/ucapps/rfe/" target="_self"&gt;submit this as an RFE&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Oct 2024 18:53:26 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Feature-Request-Highlight-the-policies-we-have-to-install-when/m-p/230178#M38408</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2024-10-18T18:53:26Z</dc:date>
    </item>
    <item>
      <title>Re: Feature Request - Highlight the policies we have to install when make some changes in an object</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Feature-Request-Highlight-the-policies-we-have-to-install-when/m-p/230190#M38411</link>
      <description>&lt;P&gt;RFE is your best bet.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Fri, 18 Oct 2024 19:49:35 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Feature-Request-Highlight-the-policies-we-have-to-install-when/m-p/230190#M38411</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-10-18T19:49:35Z</dc:date>
    </item>
    <item>
      <title>Re: Feature Request - Highlight the policies we have to install when make some changes in an object</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Feature-Request-Highlight-the-policies-we-have-to-install-when/m-p/230234#M38419</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/7"&gt;@PhoneBoy&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;yes, I know the "Where Used..." feature but it's not "user friendly" for&amp;nbsp; this purpose at all.&lt;/P&gt;&lt;P&gt;In this way you tell us that after each commit where we modified X objects we've to check X "Where Used..." windows and write in a sheet of paper the list of policy we've to install. This procedure could be useful when you have 2 policies and you change 3 objects in a commit, but if you have 10+ policies and you change 50 objects in a commit it becomes impracticable.&lt;BR /&gt;We will surely open an RFE when we will plan the next EA2GA installation...&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Thanks anyway for your support.&amp;nbsp;8)&lt;/img&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Oct 2024 06:56:38 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Feature-Request-Highlight-the-policies-we-have-to-install-when/m-p/230234#M38419</guid>
      <dc:creator>gianogli</dc:creator>
      <dc:date>2024-10-21T06:56:38Z</dc:date>
    </item>
    <item>
      <title>Re: Feature Request - Highlight the policies we have to install when make some changes in an object</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Feature-Request-Highlight-the-policies-we-have-to-install-when/m-p/230330#M38423</link>
      <description>&lt;P&gt;This is something that could theoretically be accomplished by means of a script calling the API.&lt;BR /&gt;At a high level, you would:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Call &lt;A href="https://sc1.checkpoint.com/documents/latest/APIs/#cli/show-changes~v2%20" target="_self"&gt;show-changes&lt;/A&gt; between revisions, review the operations output for the added/modified objects&lt;/LI&gt;
&lt;LI&gt;For each object identified, run &lt;A href="https://sc1.checkpoint.com/documents/latest/APIs/#cli/where-used~v2%20" target="_blank"&gt;where-used&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Based on that, you would know what policy layers/package are potentially impacted by the changes.&lt;BR /&gt;You could even &lt;A href="https://sc1.checkpoint.com/documents/latest/APIs/#cli/install-policy~v2%20" target="_self"&gt;install-policy&lt;/A&gt; for the affected gateways.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Oct 2024 20:15:39 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Feature-Request-Highlight-the-policies-we-have-to-install-when/m-p/230330#M38423</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2024-10-21T20:15:39Z</dc:date>
    </item>
  </channel>
</rss>

