ISD - How to guard against a brute force attack?
Posted: Mon Jul 20, 2015 3:20 pm
In ISD, when you have a DataStage job set as the operation, how can one guard against a brute force attack?
I would imagine a brute force attack is where a hacker codes a program to cycle through all possible web service input values, by going in order or randomly, until the web service returns some useful data.
I am looking for brainstorming ideas that go beyond requiring authentication. For instance, some web sites only allow 5 sample requests from a given IP address per day (but ISD does not have access to the requestor's IP address). Are there any additional ways to protect an ISD application from such an attack?
I would imagine a brute force attack is where a hacker codes a program to cycle through all possible web service input values, by going in order or randomly, until the web service returns some useful data.
I am looking for brainstorming ideas that go beyond requiring authentication. For instance, some web sites only allow 5 sample requests from a given IP address per day (but ISD does not have access to the requestor's IP address). Are there any additional ways to protect an ISD application from such an attack?