November 10, 2009 at 5:36 am
I work for a start-up internet retailer/auction house. In the last two weeks we have had a run of people have opened fraudulant accounts to try manipulate auction prices on the site and I have just been asked to try and sort out the problem :ermm:
So far I have been flagging these users up by their email address extentions as they are using Hungarian and Russian email addresses, I then run an update statement on the users table to disable their account. I wanted to create a trigger that would do this for me when a new record has been created in the users table but there is some sort of ADO.Net component in the web site that does the insert into the table so I can't set up the trigger on proc as I thought.
What I wanted to know is if I can set up a trigger on the table to check when a new row has been added which would then check if the conditions I set are true and disable the account accordingly. I would also appriciate any other fraud prevention advise you guys can offer.
November 16, 2009 at 11:07 pm
Triggers can be added to tables and can handle inserts, updates, and deletes. Triggers cannot be created on sprocs. You might also consider using CAPTCHA to make sure (or more sure) that there is a human signing up instead of a computer..
http://en.wikipedia.org/wiki/CAPTCHA
CEWII
November 29, 2009 at 4:40 pm
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply