I'm trying to wrap my head around Firewall as a Service (FWaaS). I currently manage firewalls for a managed service provider and now we're considering eliminating our office space, meaning that we'll have to move our internet and firewall setup to a data center or look into FWaaS options. It's crucial for us to retain our static IP since it's already configured in our customer firewalls for access. With FWaaS, I'm unsure about the setup—where do I connect my network cable? Is there a specific device, like a router, that I need to communicate with the cloud? I'm a bit lost on the implementation side and want to be prepared for vendor demos next week.
5 Answers
If you're moving away from an office setup, try to move away from whitelisting IPs for firewall access. Consider using a cloud VPN and ZTNA instead, since they scale much better for remote work.
For connecting to Firewall as a Service, you'd typically use a site-to-site VPN or a client VPN. This allows your network to communicate securely with the FWaaS in the cloud.
You might also want to explore services like Azure, AWS, or GCP. With FWaaS, your firewall will protect users and resources in the cloud, so check with your firewall vendor about virtual firewall offerings for this transition.
I’d recommend looking into Palo Alto’s Prisma Access. It allows your users to connect from anywhere and you can set up a VPN tunnel to maintain your existing public IP. This helps route your traffic effectively.
One option is to set up a static IP in Azure or AWS and configure a VPN to connect to your resources. This way, you maintain stability in your network while migrating.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures