I’d like to know what the best practice is when an attack is detected against a ServiceStack service.
I know this is not ServiceStack specific per se but any input would be appreciated.
I have seen another post using a filter and returning 403 (Best practice for implementing a blacklist IP / url check)
I’m using OrmLite exclusively with the typed API so from another post [here]
(Preventing SQL Injection Attacks) I gathered that SQL injection is not possible.
But for argument’s sake let’s say a mechanism is in place to detect attacks and if an attack is detected what should be returned? 403?
Is there a way to completely “drop” the request and let it timeout from the perspective of the attacker (caller of the API) and wouldn’t this be better?
I’ve been reading hacking tutorials and this would seem to be the most annoying for a potential hacker.