Explain the potential effects of common attacks on web applications

• • Understand and describe how the ASM can affect clients and applications directly while in either transparent or blocking mode
• • Summarize the OWASP Top Ten

Explain how specific security policies mitigate various web application attacks

• • Understand/interpret an iRule or LTM policy to map application traffic to an ASM policy
• • Explain the trade-offs between security, manageability, false positives, and performance

Determine the appropriate policy features and granularity for a given set of requirements

• • Understand application (security) requirements and convert requirements to technical tasks

Determine which deployment method is most appropriate for a given set of requirements

• • Determine which deployment method is most appropriate given the circumstances (web services, vulnerability scanner, templates, rapid deployment model)

Explain the automatic policy builder lifecycle

• • Create any profiles required to support the policy deployment (xml, JSON, logging profiles)
• • Implement anomaly detection appropriate to the web app (D/DoS protection, brute force attack, web scraping, proactive bot defense)

Review and evaluate policy settings based on information gathered from ASM (attack signatures, DataGuard, entities)

• • Configure initial policy building settings (automatic policy builder settings)

Define appropriate policy structure for policy elements

• • Define appropriate policy structure for policy elements (URLs, parameters, file types, headers, sessions and

Explain options and potential results within the deployment wizard

• • Describe options within the deployment wizard (deployment method, attack signatures, virtual server, learning method
• • Select the appropriate ASM deployment model given the business requirements

Explain available logging options

• • Explain the specifications of the remote logger (ports, types of logs, formats, address)

Describe the management of the attack signature lifecycle and select the appropriate attack signatures or signature sets

• • Understand management of attack signature lifecycle (staging, enforcement readiness period) and select appropriate attack signatures or signature sets.

Evaluate the implications of changes in the policy to the security and functionality of the application

• • Evaluate whether the rules are being implemented effectively and appropriately to meet security and/or compliance requirements and make changes as appropriate

Explain the process to integrate natively supported third party vulnerability scan output and generic formats with ASM

• • Refine appropriate policy structure for policy elements (URLs, parameters, file types, headers, sessions and logins, content profiles, CSRF protection, anomaly protection)
• • Explain how to manage policies using import, export, merge, and revert

Evaluate whether rules are being implemented effectively and appropriately to mitigate violations

• • Evaluate the implications of changes in the policy to the security and vulnerabilities of the application

Determine how a policy should be adjusted based upon available data

• • Tune an ASM policy for better performance, including use of wildcards to improve efficiency

Define the ASM policy management functions

• • Identify the status of the policy
• • Define the violation types that exist in ASM
• • Describe how to merge and differentiate between policies

Interpret log entries and identify opportunities to refine the policy

• • Examine traffic violations, determine if any attack traffic was permitted through the ASM and modify the policy to remove false positives
• • Locate and interpret reported security violations by end users and application developers

Given an ASM report, identify trends in support of security objectives

• • Understand and describe each major violation category and how ASM detects common exploits
• • Generate reporting for the ASM system and review the contents of the reports (anomaly statistics, charts, requests, PCI compliance status)

Determine the appropriate mitigation for a given attack or vulnerability

• • Take appropriate action on reported security violations by end users and application developers
• • Modify ASM policy to adapt to attacks

Decide the appropriate method for determining the success of attack mitigation

• • Choose an appropriate user defined attack signature to respond to particular traffic

Evaluate ASM policy performance issues and determine appropriate mitigation strategies

• • Analyze performance graphs and statistics along with ASM configurations to determine the root cause of performance issues and appropriate remediation to the configuration based on Guaranteed Logging

Understand the impact of learning, alarm, and blocking settings on traffic enforcement

• • Ensure that the security policy is inspecting web application traffic (application is functional and the policies are parsing the traffic)

Examine policy objects to determine why traffic is or is not generating violations

• • Examine Security Event Logs and ASM configurations to determine expected violations based on the logging profile assigned to the virtual server

Identify and interpret ASM performance metrics

• • Understand the impact of ASM iRules on performance.
• • Understand the impact of traffic spikes on ASM performance and available mitigation strategies

Evaluate ASM system performance issues and determine appropriate mitigation strategies

• • Correlate performance issues with ASM policy changes based on security policy history information and system performance graphs

Recognize ASM specific user roles and their permissions

• • Recognize differences between user roles/permissions
• • Recognize ASM specific user roles