Looks like they have allowed users to create their own for quite a while:
We have allowed customers to write their own security questions for over two and a half years now.
http://www.site5.com/blog/s5/security-and-social-engineering...
However there's nothing intrinsically wrong with the
maiden name question.
Asking users to enter their mother's maiden name, when you actually think they certainly shouldn't do that, then blaming your customers for having used their maiden name, seems like an odd way of doing it.If mother's maiden name isn't a good enough security question, stop asking it! And we all know it isn't a good enough security question.
It's a pain, but I don't trust this "Mother's Maiden name" invention.
Problem is remembering this (and some offline systems have it as well, oh well)
So if you think I'm going to put the actual name there you're wrong. Maybe not +@sfghh#54$=24 but something different.
Sound advice, but... but... but.....
This is his own website using this as a security question!
2) Knowing the answers to those questions shouldn't allow an attacker direct access to the account. It should initiate a password reset via email.
To be rather blunt you should have better security questions. You should always put in a custom answer, for example I might use the question mother's maiden name and then the answer is "L@J-289098=a9jaosdjf" which I keep in an encrypted text doc or ecrypted note in 1Password.
Not a bad point.