Closed bruce-wh-li closed 1 year ago
Test case:
curl 98.137.11.164
Note: This is the IP for yahoo.com. You may use another address. This one has the advantage that it is not often used, so less noise in the firewall logs.
Still in the terminal screen, find the ip for the instance (use ifconfing command, in this test the value was 10.12.18.42
Now, log into the Perimeter account for Forge
Open a AWS console for the perimeter account for the zone (Forge)
Open the EC2 console
There are several instances, check the Checkpoint Smart Config Windows 2022 instance
Click the Connect button
Select the RDP tab
Click on Connect using Fleet Manager
Click on Key pair
Click on Paste key pair content
Paste the Private key value
Once the value has been pasted click the Connect button
The desktop for the VM hosting Checkpoint will appear.
Search for SmartConsole (Note: this VM is a windows machine, so usually the seach feature is in the bottom left of the screen)
A pop up window will request login/pwd credentials to log into SmartConsole
Enter the credentials and click Login button. Click on the Read Only checkbox to prevent any mistake
In the new interface, click on the fw.log tab
In the new tab, in the search area, type dst:98.137.11.164
Check the result has 10.12.18.42 as source
Test case successful. The egress traffic from EC2 instance is routed through the firewall
Describe the Issue As a security analyst, we want to verify that all egress traffic is routed through the firewall
Additional Context
Acceptance Criteria