Understanding on deploying Palo Alto instance in AWS is necessary for this lab (https://tungle.ca/?p=3979).
On PA, Configure a tunnel.
Add a new static route into PA Virtual Route to allow traffic from the Private subnet to a LAN subnet in FortiGate.
Create IKE Crypto.Create IPSEC Crypto.Create an IKE Gateway.
Create an IPSEC tunnel.
Create PA-LAN and FG-LAN network.Create both Security rules to allow traffic from PA-LAN to FG-LAN and vice versa.Back to AWS – Route tables. Add a new static route on the Private Route.
Add 192.168.10.0/24 into the routes and select “Private Interface” on the target.
Move on to FortiGate.
Configure interfaces.
Configure default routes on FG.
Configure IPSEC VPN on FG.
Create a FG-LAN and PA-LAN address.Set up a new static route to allow traffic from FG-LAN subnet in FG to PA-LAN subnet in AWS.Create Security Polices to allow traffic from FG-LAN to PA-LAN and vice versa.Setup IP address on Kali machine.
Ping from Kali machine to Windows instance (10.0.3.134).
Ping from Windows instance to Kali machine (192.168.10.2).
Check Security Policy status.The FortiGate IPSEC tunnel is UP.
Back to Palo Alto in AWS. We can see the traffic from PA-LAN to FG-LAN and vice versa.
This is a diagram that I have used for the lab. I have used the same topology to deploy VPN site to site between Azure and Palo Alto firewall on-prem (https://tungle.ca/?p=3338). Basically I removed the Palo Alto firewall and put FortiGate in the diagram.
Create a new virtual network is Azure-PA.
Change default network to PrivateSubnet is 10.0.1.0.
A subnet address range is 10.0.1.0/24
Click Create.
Create a new subnet.
A subnetwork address range is 10.0.0.0/24
Go to “Virtual network gateway” to create a new virtual network gateway.
Virtual network: Azure-PA.
Subnet: Gatewaysubnet 10.0.0.0/24
Public IP address name: VPNIP
Click Create.
Wait around from 20 to 30 minutes to see if the Deployment will be done.
Go to “Local network gateway” and create a new local network gateway.
An IP address is a public IP address of the Palo Alto firewall.
Address space is Palo Alto’s LAN subnets.
Clock create.
Go to “Virtual network gateways”, and select the virtual network gateways that we have created in the previous step.
Go to “Connections” – Add.
Enter a shared key (PSK) for VPN site-to-site.
Take note of the IP address of Azure VPN.
On FortiGate on-prem.
Create a static default route.
Configure an IPSEC Tunnel.
Phase 1.
Phase 2.
Create a new network object for FortiGate.
FG-LAN: 172.16.0.0/16
Azure-LAN: 10.0.0.0/16.
Create both access rules to allow traffic from FortiGate LAN subnets to your Azure VPN private subnets. Remember “Disable NAT” on these rules.
Create a static route to allow traffic from FortiGate LAN subnets to your Azure private subnets via the IPSEC VPN site-to-site IKEv2 tunnel.
Ping from Kali machine to Windows 2016 on Azure.
The tunnel is up on FortiGate.
Ping a Kali machine on FortiGate LAN subnet from Azure.
Back to VPN2S, we can see the VPN status connection is “Connected”.
This is a diagram that I have used for this demonstration.
Create your VPC.
Create a private subnet.
Create a new Internet Gateway and attach it to your VPC.
Create a new route to 0.0.0.0/0 to your Internet gateway.
Create a new Customer gateway with the public IP address of FortiGate.
Create a new Virtual Private Gateway and attach it to your VPC.
Create a new VPN site-to-site.
Click Download Configuration to configure on your FortiGate.
Log into FortiGate.
Interfaces.
Copies these commands and pastes them into FortiGate. Notes the set “mtu 1427” and set “mtu-override enable” does not available on FortiGate 6.2
Back to AWS and launch a new Linux VM instance. This machine is used to test VPN site-to-site.
Configure a new static route to allow LAN subnets on AWS to access LAN subnets on FortiGate.
On FortiGate, configure a new static route to AWS LAN subnets.
Configure access rules to allow FortiGate LAN subnets to communicate with AWS LAN subnets.
Pings from Kali machine to the Linux VM instance on AWS.
The IPSEC tunnel in FortiGate is up.
Back to AWS, the VPN tunnel is up.
Launches a new Windows 2016 VM instance to install Splunk.
On Security Group, add a couple of rules to allow ICMP and all traffic on FortiGate LAN subnets to access this instance.
RDP to Windows instance and disable Firewall to send logs from FortiGate.
Download Splunk Enterprise for Windows and install it into this instance.
Install FortiGate App for Splunk and Fortinet FortiGate Add on Splunk.
Click on the Settings tab and configure Splunk to get FortiGate logs. Select new Local UDP.
Enter 514 on the port setting. Be default, FortiGate is using UDP port 514 to send log to Syslog.
Select: fgt_log
App Context: Fortinet FortiGate App for Splunk
Method: IP
Index: Default
Check the UDP 514 port is running in the instance.
Back to FortiGate, configure Fortigate to send logs to Splunk on AWS. Enter the IP address of Splunk on the IP Address setting, and click choose All for “Event Logging” and “Local Logging”. Then, click Apply.
Log out of FortiGate and log back in to generate logs. If we may not see FortiGate logs on Splunk, we need to type the commands below to change the source-ip address to send log from using the “management interface” to using the LAN interface “172.16.1.254”
config log syslogd setting
set status enable
set mode udp
set port 514
set server "10.0.0.48"
set source-ip "172.16.1.254"
end
Also, enable PING Access, HTTP, and HTTPS on tunnel 1 interface of FortiGate.
Splunk is able to ping the FortiGate LAN interface.
Back to the Splunk instance, now we are able to see logs from FortiGate.
This is a diagram that is used to deploy this lab.
In this lab, we will use Elastic Load Balancer to distribute RDP traffic via Windows 2016 VM instances among the FortiGate in different AZs on AWS.
Below are a couple of steps that are used to deploy this lab.
Create your VPC, subnets, and route tables.
Launch FortiGate 1 on AZ 1 and FortiGate 2 on AZ 2.
Create both Windows 2016 VM on AZ 1 and AZ 2.
Configure DNAT to allow RDP traffic from the Internet to Windows Server 2016 instance on each AZ.
Configure Elastic Network Load Balancing on both FortiGates on multiple AZ.
RDP traffic has been distributed to Windows 2016 VM1 and VM2 via Elastic Network Load Balancing
Create a new VPC.
Create both Public subnet 1 and Private subnet 1 on the first Availability Zone.
Create new both Public subnet 2 and Private subnet 2 on the Availability zone 2
Create 4 route tables as in the diagram above.
Link the subnets to corresponding route tables.
Create a new FortiGate on AZ 1.
Security Group.
Create a new Elastic IP address and associate for the first FortiGate.
Launch the new FortiGate instance on AZ 2.
Rename to Fortinet Zone 1 Public subnet and Fortinet Zone 2 Public Subnet.
Create a new Fortinet Zone 1 Private subnet.
Attach this into the first FortiGate.
Create a new Fortinet Zone 2 Private subnet and attach it to FortiGate 2.
Uncheck “Change source/destination check” on all FortiGate interfaces.
Back to Route tables.
Create a new route 0.0.0.0/0 on Public Route table 1 via Fortinet Zone 1 Public subnet interface.
Create a new route 0.0.0.0/0 on Public Route table 2 via Fortinet Zone 2 Public subnet interface.
Create a new route 0.0.0.0/0 on Private Route table 1 via Fortinet Zone 1 Private subnet interface.
Create a new route 0.0.0.0/0 on Private Route table subnet 2 via Fortinet Zone 2 Private subnet interface.
Access FortiGate management interface.
The FortiGate 1.
Change the LAN setting for port 2.
Do the same with FortiGate 2.
Create two new Windows Server 2016 instances on AZ1 and AZ2.
Windows Security Group.
Launch the new one.
Go to FortiGate 1, and DNAT port 3389 to Windows Server 2016 VM 1 instance.
Create a new inbound policy to allow traffic from the Internet to Windows 2016 instance.
On FortiGate 2.
Create a new Firewall Policy.
Edit the Security Group to allow RDP to Windows 2016 VM 2 instance.
Access Windows VM 1.
Create Network Load Balancer on AWS for RDP traffic to Windows Server 2016 instance.
Select “IP address”.
Add IP addresses on the public subnet of both FortiGates on “register targets”.
Click Register targets.
Wait until the health states on both IP addresses are healthy.
Right-click on FortiGate-NLB-RDP and enable “Cross zone load balancing” to allow load balancing on multiple AZ.
Set the same Windows password for both Windows 2016 instances.
Access RDP to the highlighted DNS name on NLB.
An RDP session will access Windows Server VM 1 or VM 2 via Elastic Load Balancing.
We are able to configure both web servers on Windows server 2016 VMs and distribute web traffic via Windows 2016 VM instances among the FortiGate in different AZs on AWS.
This is a diagram to show how to create a VPN site to site connection from PA on-prem and FG on AWS.
In this lab:
Create a VPC, subnets, Internet gateway, route tables.
Create a FortiGate VM and Windows 2016 instance on AWS
Configure Palo Alto
Create VPN site to site between both sites PA and FortiGate
Allow Windows 2016 instance to access the Internet via FortiGate. Also, allow RDP to this machine via the Internet by using FortiGate.
Test ping traffic between both sites.
Allow a machine on the PA LAN subnet to access the Internet and the Windows 2016 instance on AWS.
Create a new SSLVPN portal on AWS and test to access the portal via SSLVPN.
+ Below are a couple of steps to deploy FortiGate on AWS.
Create a new VPC.
Create a public subnet.
Create a private subnet.
Create an Internet gateway.
Attach the gateway to your VPC.
Edit Route table, change default Route table to Private Route.
Create a Public Route Table.
Link the Public Subnet to the Public Route.
Add a new route 0.0.0.0/0 to your Internet gateway.
Create a new key pair.
+ Go to EC2, and deploy Fortinet on AWS.
Select your VPC, the subnet belongs to Lab Public Subnet. Also, changing the Auto-assign Public IP is Enable.
On the Security Group tab, add new two lines at the end of Security Group as a screenshot below. This allows to ping and RDP to the Windows 2016 machine on a private subnet later on.
Go to Network interfaces, change the interface to FG Public Interface.
Create a new FG Private interface. Links to the private subnet and FortiGate Security Group.
Change to FG Private Interface.
Select the FG private interface, choose Action on the top right-hand side and Attach this network interface to Fortinet EC2.
Right-click on both FG Public and Private interfaces, and disable “Change source/dest check” on both interfaces to allow NAT traffic on these interfaces.
Create a new Elastic IP address.
Change to Fortinet EIP.
Associate this Elastic IP address to Fortinet EC2.
Back to Route tables, add a new route 0.0.0.0/0 to FG private interface.
Now, Fortinet has two interfaces. One is Private, and another one is Public.
Copy the Elastic IP address and paste it to your web browser to access the FortiGate management interface.
Access Fortinet via the Internet.
+ Launch a new Windows VM EC2 instance on your VPC.
Network: Your VPC
Subnet: Private subnet
Auto-assign Public IP: Disabled. We will access RDP to the machine via DNAT on FortiGate.
On the Security Group setting, add two lines to allow RDP and ICMP traffic to the machine.
+ Login to Fortinet.
Copy the FG instance and paste it to password login.
Change the password to login to Fortinet.
Edit WAN and LAN interface setting.
Back to Fortinet to configure Firewall Policy to allow RDP traffic from the Internet to the Windows VM machine.
Configure port forwarding to allow traffic from the Internet to Windows 2016 VM instance on AWS.
External IP address: IP address of FG on the public subnet
Map to IPv4 address on the private subnet is IP address of Windows VM computer.
The external service port and map to IPv4 port is 3389.
Allow inbound traffic from WAN to this machine.
Create both static routes to allow a private subnet to access outside.
Creating new static routes for the private subnet from 10.0.0.0/16 to 10.0.1.1 that is the default gateway on the private subnet.
Try to access the machine.
Load private key to decrypt Windows password.
Access RDP to Windows 2016 instance on AWS.
Now we can see the RDP traffic via Fortinet.
Disable Windows Firewall to allow ICMP traffic to that machine on Palo Alto private subnet.
Configure IPSEC site to site wizard. Choose Custom.
Enter IP address of public interface of PA. Disable NAT traversal, enter the pre-shared key and choose the IKE v2.
Phase 1 and Phase 2 settings need to match with the Palo Alto setting.
Local Address: the private subnet of FG: 10.0.1.0/24
Remote Address: PA LAN subnets: 172.16.0.0/16
Click the Advanced tab. Change the setting to match with PA Phase 2 setting
Create Fortinet LAN and PA LAN subnet network addresses.
Create a static route on Fortinet to allow private subnet traffic to the Palo Alto LAN subnet.
Create a Security Policy to allow traffic from the Fortinet LAN subnet to the PA LAN subnet. Remember to uncheck NAT setting on access rules from AWS LAN to PA LAN and vice versa.
PA LAN subnet to AWS LAN subnet.
AWS LAN subnet to PA LAN subnet.
Create a new access rule to allow the FG LAN subnet to access the Internet.
Ping 8.8.8.8 from Windows 2016 VM instance.
+ Configure PA.
Setting the IP address for e1/1 is DHCP, and assign an IP address for e1/2 is 172.16.1.254/24
Create a tunnel interface: tunnel 1.
Create network objects for FortiGate, PA LAN, and AWS LAN.
Create IKEC Crypto.
Create an IPSEC Crypto.
IKE Gateway.
IPSEC tunnel.
On Proxy ID tab.
Local: PA LAN subnets.
Remote: AWS LAN subnet.
Create a Static Route from PA LAN to Fortinet LAN on AWS.
Create both Security Policies to allow traffic from PA LAN subnet to AWS LAN subnet.
Remember to click “Commit” button to apply the new settings on PA.
From Windows 2016 VM instance, pings a machine on PA LAN subnet.
+ Pings from PA LAN subnet to AWS LAN subnet.
On PA, a tunnel is up.
Monitoring to see the traffic on both sites.
On FortiGate.
An IPSEC VPN site-to-site tunnel is up.
diagnose vpn tunnel list
Click on the log and Report to see events that are related to VPN.
+ Back to PA to create another static route to allow the PA LAN subnet to access the Internet.
A next hop is the default gateway of the PA public subnet.
Create a SNAT policy to allow traffic from the PA LAN subnet to the Internet.
On the Destination interface, should choose e1/1. This is because VPN site-to-site traffic does not use NAT.
Ping 8.8.8.8 from PA LAN subnet.
+ Create an SSLVPN portal on FortiGate to allow to access FG private subnet on the SSLVPN zone.
RDP to Windows 2016 instance private subnet on AWS is 10.0.1.42
On SSLVPN setting, enable SSLVPN via 44333 port.
Create a new username and password to access SSLVPN.
Then assign this user to the portal that we have created on previous step.
Edit the Security Group to allow Internet traffic to SSLVPN port is 44333.
From a Windows machine, access SSLVPN portal on FG.
Also, we can use Forticlient to access if we have a license.
This is a topology that is used to deploy this lab.
+ Configure FortiGate on AWS.
Create a new VPC with a CIDR network is 10.0.0.0/16. Then, create both Lab Public subnet and :ab Private subnet on AWS.
Create a new Internet gateway and attach to your VPC.
Create route tables.
Add a new route to the public Route table.
Associate the public subnet to the Public Route table.
Go to EC2 and create a new FortiGate instance.
Create a new private interface for FortiGate.
Attach the interface to FortiGate.
Disable “Source and destination check” on both Public and Private FortiGate interfaces.
Create a new Elastic IP address and assign it to your FortiGate instance.
Assign the Elastic IP address to public FortiGate interface.
Access FortiGate management interface.
Add a new route on a Private Route table to the Private FortiGate interface.
Create a new Windows instance on AWS.
Security Group.
Modify Windows Security Group to allow ICMP traffic.
Configure VPN site to site.
There are two routes that have been automatically created on FortiGate on the static routes setting.
+ Configure FortiGate on-prem.
Configure a default route on FortiGate.
Configure VPN site to site between both FortiGate.
+ Pings a Windows instance on AWS from a machine on FortiGate on-prem. Remember to access RDP to the machine and disable Windows Firewall to allow ICMP traffic from on-prem to that machine.
The IPSEC tunnel is up.
Pings from Windows instance on AWS to a computer on FortiGate LAN subnet on-prem.
