Protection fit
Start with the concerns affecting your website. Connect them with DDoS protection, WAF, and bot protection to identify questions for further assessment.
Map your protection needs
Concern → capability → requirement
Start with what your website needs. Use these associations to choose a capability to examine and make the requirements behind your concern explicit.
| Your concern | Capability to examine | Requirement to clarify |
|---|---|---|
| Your concernDDoS-related traffic concerns | Capability to examine DDoS protection | Requirement to clarify Which traffic concerns and availability requirements should your DDoS evaluation address? Identify the affected website services and the traffic patterns you need to discuss. |
| Your concernWeb application protection requirements | Capability to examine WAF | Requirement to clarify Which application risks and legitimate request requirements should your WAF evaluation consider? Describe the applications in scope and the user interactions you need to preserve. |
| Your concernBot-related traffic concerns | Capability to examine Bot protection | Requirement to clarify Which automated traffic concerns matter to your website, and which automated activity should remain allowed? Distinguish unwanted activity from automation your website relies on. |
Yes. Consider each category that relates to your website and note the questions it raises. Overlapping concerns are a starting point for an assessment—not a conclusion that a combined deployment is supported or needed.
Describe the website requirements behind each concern: what you want to address, what needs to keep working, and which constraints matter to your team. Keep unresolved questions alongside those requirements so the discussion can focus on what still needs to be assessed.
Website requirements
Open questions
Bring your open protection questions into a combined fit review, or discuss your requirements directly with sales.