DCGW: Bot Detector

[cloudjumpercat]

Jobs to be done (optional)

Definition of done

• MVP: link on landing page with a short description that would take them to the Labs feature https://developer.konghq.com/dedicated-cloud-gateways/
• Request draft, ideally it contains how to set it up, descriptions of Rules (what are the Konnect created ones and what can users create?), monitoring vs blocking mode, any limitations/gotchas, what data is collected and why

need to request draft

Information

PRD: https://docs.google.com/document/d/1_snYwtpUEB6NBpInKVYyYB19yMycKMaRteB-_aN7lV4/edit?tab=t.0#heading=h.36bvwfgzw1nu
AHA: https://konghq.aha.io/epics/CGW-E-38

Due date (optional)

Size

[cloudjumpercat]

• I don't see the Kong-curated rule set in v0 in the UI, will we have this for release or just custom rules?
• Can I get a link to the API spec?
• Users and AI would greatly benefit from some example rules (beyond the Kong-curated ones) that fit common customer use cases. Solution-focused content like this will increase the stickiness of Bot Detector. Does anyone have a list of examples or should I share the match types/PRD with Claude and have it speculate?
• What's the recommended way to use this? Should customers let it sit in monitoring mode for a while and use the results to determine what to block/create rules for? Based on the monitoring results, how will customers know what they should make a rule for and/or block?