Behavioral detection
Analyze traffic patterns to identify suspected automation, including behavior that signature matching alone may miss.
Protectiv / Prism
Analyze traffic behavior on Protectiv’s anycast network. Identify suspected bots and choose when to allow, challenge, or block requests to your applications.
Capabilities
Combine behavioral detection, bot signatures, and challenges to respond to suspected automation. Set policies for each hostname and review the traffic behind each decision.
Analyze traffic patterns to identify suspected automation, including behavior that signature matching alone may miss.
Use proof-of-work or interactive challenges to check suspicious traffic, with an under-attack mode for periods of elevated abuse.
Apply endpoint controls to repeated login and signup attempts associated with credential stuffing and account abuse.
Choose which requests to allow, challenge, or block using conditions scoped to each hostname.
Use maintained bot signatures alongside behavioral detection to identify known automation.
Review bot classifications, traffic sources, and policy actions in searchable logs.
Prism uses security cookies to manage challenge attempts and remember completed checks.
Read the security cookie reference ↗How it works
Connect a hostname, review its traffic, and decide which requests to allow, challenge, or block.
Add a CNAME for the hostname you want covered.
Review traffic patterns and suspected automation for each hostname.
Decide what to allow, challenge, or block.
Challenge or block matching requests at the edge, according to your rules.
One network
Prism focuses on automated traffic. Protectiv WAAP adds web application and API protection on the same anycast network. Use CDN for content delivery.
Explore Protectiv WAAPExplore Protectiv CDN ↗Tell us where automated traffic is causing problems and how you want to respond. We’ll help you review the controls that fit your applications.