Cloud Guard Network + Azure Installation & Integration Guide

Поделиться
HTML-код
  • Опубликовано: 27 авг 2024
  • In this tutorial, we will go through the full process of setting up a Management Station, Firewall HA Cluster and most importantly connect this to an existing Azure Infrastructure.
    CloudGuard for Azure prevents network attacks and data breaches while enabling secure connectivity to Azure public cloud environments
    CloudGuard also integrates with a wide variety of public cloud and private cloud environments including those built on SDDC technology.

Комментарии • 6

  • @mo_checkpoint6210
    @mo_checkpoint6210 Год назад +1

    Great video, simple & easy to follow and understand! Cloud doesn't need to be scary when you demonstrate it like this :)

  • @taukirsyed1769
    @taukirsyed1769 Год назад

    Simple yet powerful! Thank you so much!

  • @arendkolk1
    @arendkolk1 4 месяца назад

    How would you create the clusterobject in smartConsole based on the private IP addresses of the gateways? Instead of the public ip addresses of the firewalls

  • @TheKamaladmire1
    @TheKamaladmire1 Год назад

    Amazing amazing amazing

  • @wearewhoweare6602
    @wearewhoweare6602 Год назад

    Amazing vid. However I know you want to keep it short. You did not really show the config of both frontend and back end load balancers. How to secure connection from both to the HA cluster

  • @TheKamaladmire1
    @TheKamaladmire1 Год назад

    Quick question..I created the vnets before start the gateway deployment with template (high availability) creat resource group etc and when get on network page I choose the vnet that I have created prior to deployment. However after deployment completed it doesn't create automatic routes and no NSG, this cause the problem after deployment you not able to SSH to gateway via its public IP (already try reboot few times) so I decided to delete all and start new template and create resource group etc and on network page create vnet that way it's do all auto jobs like create frontend backend routes NSG etc and accessable over SSH... Why it behaves like that???