<?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: AppSec - Self Paced Hands On Lab in WAF</title>
    <link>https://community.checkpoint.com/t5/WAF/AppSec-Self-Paced-Hands-On-Lab/m-p/131150#M51</link>
    <description>&lt;P&gt;Hello Shay!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I went through the AppSec demo and found a few odd things:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) &amp;nbsp;With the power meter API asset in "Prevent" mode, and after enforcing the policy, I run the demo .EXE app on the VM desktop. &amp;nbsp;Yes, it did show "Forbidden (403)" in the response (as expected). &amp;nbsp;The lab document said that the usage graph would continue normally, and not reset to Zero. &amp;nbsp;However, in the web browser showing the power usage graph, the graph did not continue auto-updating. &amp;nbsp; Instead, the status showed "No communication" and the other values were not updating; they all stayed static. &amp;nbsp;I set the EXE app back to Normal Mode, and the graph resumed normally. &amp;nbsp;The AppSec services were working correctly, and blocking the API attack, however.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2) When doing the k8s lab demo, the process failed when running "helm install ..." on the juice chart app:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;root@waap-k8s:~# helm install juice juice-chart.tar.gz --set nanoToken="cp-bf0bfc7e-269c-401e-a6d2-fcc237ce880c2a6f7bec-2a24-4d0b-92f7-4727ccf7afb8"&lt;BR /&gt;Error: failed to download "juice-chart.tar.gz" (hint: running `helm repo update` may help)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looks like there is a missing repository, and it cannot be installed via 'helm'.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let me know if there is something else that needs to be done.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Wed, 06 Oct 2021 14:39:39 GMT</pubDate>
    <dc:creator>Duane_Toler</dc:creator>
    <dc:date>2021-10-06T14:39:39Z</dc:date>
    <item>
      <title>AppSec - Self Paced Hands On Lab</title>
      <link>https://community.checkpoint.com/t5/WAF/AppSec-Self-Paced-Hands-On-Lab/m-p/129197#M39</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="4"&gt;&lt;SPAN&gt;In this LAB you will attack a vulnerable web application and then you would learn how to use CloudGuard AppSec to protect it.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="4"&gt;&lt;SPAN&gt;To access the lab click&amp;nbsp;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;FONT size="4"&gt;&lt;A href="https://community.checkpoint.com/t5/CloudGuard-AppSec/ct-p/cloudguard-appsec-demo" target="_self"&gt;here&lt;/A&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 12 Sep 2021 12:03:36 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/WAF/AppSec-Self-Paced-Hands-On-Lab/m-p/129197#M39</guid>
      <dc:creator>Shay_Levin</dc:creator>
      <dc:date>2021-09-12T12:03:36Z</dc:date>
    </item>
    <item>
      <title>Re: AppSec - Self Paced Hands On Lab</title>
      <link>https://community.checkpoint.com/t5/WAF/AppSec-Self-Paced-Hands-On-Lab/m-p/131150#M51</link>
      <description>&lt;P&gt;Hello Shay!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I went through the AppSec demo and found a few odd things:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) &amp;nbsp;With the power meter API asset in "Prevent" mode, and after enforcing the policy, I run the demo .EXE app on the VM desktop. &amp;nbsp;Yes, it did show "Forbidden (403)" in the response (as expected). &amp;nbsp;The lab document said that the usage graph would continue normally, and not reset to Zero. &amp;nbsp;However, in the web browser showing the power usage graph, the graph did not continue auto-updating. &amp;nbsp; Instead, the status showed "No communication" and the other values were not updating; they all stayed static. &amp;nbsp;I set the EXE app back to Normal Mode, and the graph resumed normally. &amp;nbsp;The AppSec services were working correctly, and blocking the API attack, however.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2) When doing the k8s lab demo, the process failed when running "helm install ..." on the juice chart app:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;root@waap-k8s:~# helm install juice juice-chart.tar.gz --set nanoToken="cp-bf0bfc7e-269c-401e-a6d2-fcc237ce880c2a6f7bec-2a24-4d0b-92f7-4727ccf7afb8"&lt;BR /&gt;Error: failed to download "juice-chart.tar.gz" (hint: running `helm repo update` may help)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looks like there is a missing repository, and it cannot be installed via 'helm'.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let me know if there is something else that needs to be done.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 06 Oct 2021 14:39:39 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/WAF/AppSec-Self-Paced-Hands-On-Lab/m-p/131150#M51</guid>
      <dc:creator>Duane_Toler</dc:creator>
      <dc:date>2021-10-06T14:39:39Z</dc:date>
    </item>
  </channel>
</rss>

