Question 530
For Aspen Digital, the security review of client advisory systems and shared files highlights this gap: An architecture assigns Azure Firewall to inspect application-layer OWASP payloads without deploying an appropriate WAF capability. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?
Explanation
Correct Answer
The WAF records the malicious web payload while the network firewall enforces its separate connectivity policies. This is the relevant proof because it tests whether the selected corrective action (Select a web application firewall for HTTP application threats and retain network-layer controls for routing and access) addressed the initiating problem (An architecture assigns Azure Firewall to inspect application-layer OWASP payloads without deploying an appropriate WAF capability) in Aspen Digital's client advisory systems and shared files environment, not merely whether a task was marked complete.
Incorrect Answers
The published endpoint reaches only the intended private service and an unrelated inbound port remains blocked. This is useful evidence for a different situation (An internal service must be reached through a published endpoint but staff mistakenly assume an outbound allow rule automatically enables inbound address translation) and action (Configure the appropriate Azure Firewall destination NAT and network access controls for approved inbound traffic). For the reported issue at Aspen Digital, it does not establish the required outcome: The WAF records the malicious web payload while the network firewall enforces its separate connectivity policies.
A controlled assessment documents network-layer attack mitigation coverage and monitoring for the public workload. This is useful evidence for a different situation (A public Azure web service is overwhelmed by volumetric network attacks but administrators expect a web application firewall alone to absorb the flood) and action (Evaluate Azure DDoS Protection for the protected virtual network and application exposure requirements). For the reported issue at Aspen Digital, it does not establish the required outcome: The WAF records the malicious web payload while the network firewall enforces its separate connectivity policies.
Malicious HTTP payloads matching the configured protection rule are blocked while ordinary requests continue. This is useful evidence for a different situation (An internet-facing application experiences SQL injection attempts but the organization places only layer-three network rules in front of HTTP requests) and action (Deploy Azure Web Application Firewall with an appropriate policy for application-layer threats). For the reported issue at Aspen Digital, it does not establish the required outcome: The WAF records the malicious web payload while the network firewall enforces its separate connectivity policies.