<?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: Policy/Object Automation Approach in API / CLI Discussion</title>
    <link>https://community.checkpoint.com/t5/API-CLI-Discussion/Policy-Object-Automation-Approach/m-p/183503#M7781</link>
    <description>&lt;P&gt;You can feed a CSV file to mgmt_cli, but it has to be formatted correctly.&lt;BR /&gt;But, like you said, that's not full automation.&lt;/P&gt;
&lt;P&gt;We do provide Postman collections for the various versions of the Management API:&amp;nbsp;&lt;A href="https://community.checkpoint.com/t5/API-CLI-Discussion/Postman-Collections-links-to-all-available-and-the-basics/m-p/40923#M2785" target="_blank"&gt;https://community.checkpoint.com/t5/API-CLI-Discussion/Postman-Collections-links-to-all-available-and-the-basics/m-p/40923#M2785&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm also curious about how companies are approaching this topic as well as anything we (Check Point) can do to better support these efforts.&lt;/P&gt;</description>
    <pubDate>Wed, 07 Jun 2023 15:33:55 GMT</pubDate>
    <dc:creator>PhoneBoy</dc:creator>
    <dc:date>2023-06-07T15:33:55Z</dc:date>
    <item>
      <title>Policy/Object Automation Approach</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/Policy-Object-Automation-Approach/m-p/183408#M7780</link>
      <description>&lt;P&gt;Morning all,&lt;/P&gt;
&lt;P&gt;I am looking at various ways of automating policy changes using the Management API. We currently receive scoping requests via an excel spreadsheet, which details what objects are to be created/rules added, etc.&lt;/P&gt;
&lt;P&gt;I've modified the excel file so that it will generate the mgmt_cli output, which saves time, but isn't full automation.&lt;/P&gt;
&lt;P&gt;I'd like to utilise tools like PowerAutomate, Postman, etc. I'm interested in hearing how the community approach their policy automation.&lt;/P&gt;
&lt;P&gt;Any ideas/suggestions welcomed &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jun 2023 06:48:44 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/Policy-Object-Automation-Approach/m-p/183408#M7780</guid>
      <dc:creator>AaronCP</dc:creator>
      <dc:date>2023-06-07T06:48:44Z</dc:date>
    </item>
    <item>
      <title>Re: Policy/Object Automation Approach</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/Policy-Object-Automation-Approach/m-p/183503#M7781</link>
      <description>&lt;P&gt;You can feed a CSV file to mgmt_cli, but it has to be formatted correctly.&lt;BR /&gt;But, like you said, that's not full automation.&lt;/P&gt;
&lt;P&gt;We do provide Postman collections for the various versions of the Management API:&amp;nbsp;&lt;A href="https://community.checkpoint.com/t5/API-CLI-Discussion/Postman-Collections-links-to-all-available-and-the-basics/m-p/40923#M2785" target="_blank"&gt;https://community.checkpoint.com/t5/API-CLI-Discussion/Postman-Collections-links-to-all-available-and-the-basics/m-p/40923#M2785&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm also curious about how companies are approaching this topic as well as anything we (Check Point) can do to better support these efforts.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jun 2023 15:33:55 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/Policy-Object-Automation-Approach/m-p/183503#M7781</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2023-06-07T15:33:55Z</dc:date>
    </item>
    <item>
      <title>Re: Policy/Object Automation Approach</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/Policy-Object-Automation-Approach/m-p/183510#M7782</link>
      <description>&lt;P&gt;Great question mate! Let us know what you find, as I also had client ask me this question before.&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jun 2023 15:55:03 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/Policy-Object-Automation-Approach/m-p/183510#M7782</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2023-06-07T15:55:03Z</dc:date>
    </item>
    <item>
      <title>Re: Policy/Object Automation Approach</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/Policy-Object-Automation-Approach/m-p/185706#M7826</link>
      <description>&lt;P&gt;What you're talking about is called "glue code". It hooks up a ticket system to a firewall management server, for example. This code tends to be very environment-specific, because there aren't a lot of companies using the same set of tools. For example, my current company has gone through at least five ticket tracking systems in the last ten years. The code also tends to be fairly proprietary, and not very high-quality. Not sure you'll find any which already exists to hook into your existing workflow, and if you did, I'm not sure I would trust it.&lt;/P&gt;
&lt;P&gt;A few companies like Tufin and HashiCorp make a sort of "API broker" tools which talk to many tools on the back-end. They then present a subset of those tools' capabilities via a consistent API, thereby reducing the amount of glue code you have to write to deal with multiple back-end platforms. I don't know of anything similar which talks to many ticket systems and gives you one reactive programming platform to deal with events in any of them.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jul 2023 20:05:40 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/Policy-Object-Automation-Approach/m-p/185706#M7826</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2023-07-05T20:05:40Z</dc:date>
    </item>
  </channel>
</rss>

