What if you can't tighten your base path? Is there an elegant way to battle the port scanners within the service or VSM?
In my case the I have a list of transactions similar to :
GET /api/v1/employees
GET /api/v1/employee/{EmployeeId}/
POST /api/v1/create
GET /info
As I understand my options, the /info transaction limits my ability to put in a restrictive base path in this particular case.
If I deploy this service, after 4th port scans the service goes off line. They don't even have to be consecutive.
One way I replicate this is to hit the service with a telnet command. Example:
telnet {{VSEip}} {{VSEport}}
Cntrl-x <Enter>
I've thought about creating a generic operation responses for / in the VSI, but the error comes pre-VSI during the http listener which reports the "incoming request is not HTTP"