What data gets sent to the Signal Sciences backend?
Not all traffic is sent to the Signal Sciences backend, but the agent does pre-filtering locally to determine if the request contains an attack. When the agent identifies an attack or anomaly in the request, it only sends parameters with identified attacks to the platform backend. The entire request is never sent to the Signal Sciences backend and certain portions of the request are explicitly never sent to the backend, such as session tokens or tracking cookies. Additional information regarding data redaction can be found here.
What if I have other fields that are sensitive to my application?
We provide a configuration mechanism in the console to add additional fields which will always be filtered. For example, if your password field is named “foobar” instead of “password,” we will redact that field in the agent before it’s sent to our backend. Instructions for specifying additional fields to be redacted can be found here.
How long does Signal Sciences retain the data it collects?
For searching purposes, data is retained for 30 days. Data can only be extracted within 24 hours.
How does Signal Sciences use the data it collects?
We use the data to provide visibility and make decisions about blocking attacks to your application.
Can the data be attributed back to me or any of my users?
No. We’ll never attribute any data back to your organization or end users.
What happens if I want to scrub something after the fact?
See something in the raw data that you’d rather delete? We can delete the data for entire days from our database. Submit a support request with the date range you want to delete and we’ll scrub our database of your requested data.
What response data does the Signal Sciences backend see?
Signal Sciences only collects the response’s metadata, i.e. response codes, sizes, and times.