Morning, we had, what we suspect, is a denial of service attack which resulted in the DW database expanding uncontollably.
The entry point was a url request on the DW standard SearchV1 module like this:
/xx-xx/searchresults?q=coffiero einbetonieren inshape body curl corner box passen Low Impact Fitness... (up to 300 chars long)
and then a very long Sql SELECT statement I think designed to stall the database. These requests were varied and made many times per second.
I would like to intercept requests like this using a Notification Subscriber to sanitize before the requests hit the database, can anyone recommend which Notification Subscriber would be best to use, or a better standard option if available or to write our own module if SearchV1 is now unusable/deprecated
Rgds
Kevin
