What capabilities must the automated front-end security solution have for public-facing web apps?

• A. Be in front of public-facing web applications, actively running, up to date, generating audit logs, and configured to block or alert
• B. Log data only, never block
• C. Be installed on a developer machine only
• D. Only run during business hours

Answer: (A)

The capability being tested is a front-end security solution that sits in front of public-facing web apps and actively protects them. It must be deployed in-line so it can inspect traffic as it flows to the application, blocking malicious requests or generating real-time alerts. Keeping the tool up to date ensures it can recognize and defend against the latest threats and attack patterns. Generating audit logs is essential for proving controls are in place and for forensics and monitoring. Configuring it to either block or alert gives you immediate protection and visibility, rather than just collecting data. Logging alone doesn’t stop attacks, and being installed only on a developer machine or only running during business hours would leave production apps unprotected at times, which is not acceptable for public-facing web applications.