SIMULATION -
You need to ensure that connections through an Azure Application Gateway named Homepage-AGW are inspected for malicious requests.
To complete this task, sign in to the Azure portal.
You do not need to wait for the task to complete.
See the explanation below.
You need to enable the Web Application Firewall on the Application Gateway.
1. In the Azure portal, type Application gateways in the search box, select Application gateways from the search results then select the gateway named
Homepage-AGW. Alternatively, browse to Application Gateways in the left navigation pane.
2. In the properties of the application gateway, click on Web application firewall.
3. For the Tier setting, select WAF V2.
4. In the Firewall status section, click the slider to switch to Enabled.
5. In the Firewall mode section, click the slider to switch to Prevention.
6. Click Save to save the changes.
As an AI language model, I do not have access to the Azure portal and cannot perform simulations. However, I can provide you with the general steps you can take to configure Azure Application Gateway to inspect for malicious requests:
Log in to the Azure portal and navigate to the Homepage-AGW Application Gateway.
Click on the "Listeners" tab and then click on the existing listener that you want to modify.
Under the "Security" section, enable the Web Application Firewall (WAF) feature by toggling the switch to "On".
Select the appropriate WAF policy from the dropdown menu or create a new WAF policy that suits your requirements. The WAF policy contains rules that determine how the gateway inspects requests for malicious content.
After selecting the WAF policy, click on the "Save" button to apply the changes.
Test the configuration by sending requests to the application through the Application Gateway. The WAF should inspect the requests and block any that match the rules defined in the WAF policy.
Note that configuring the WAF may incur additional costs, depending on the size and complexity of the WAF policy.