SiteKey to Prevent Phishing 377
Perekrestok writes "An article at CNN talks about a new system called SiteKey which will be rolled out at Bank of America across the U.S. by this fall. The system would require an online user to not only enter a password but also answer three personal questions. More interestingly, the system will have a button which will allow the user to verify that they are indeed at the bank's website and not at some scammer's fake site."
I don't have time for that junk (Score:5, Interesting)
Keep the password.
Keep the button (which seems like a great idea by the way).
Ditch the three questions.
Re:I don't have time for that junk (Score:5, Interesting)
Phishing sites will include a big button as well
clicking it will say:
Of course your on the real bank website
it does no good - i prefer the way my bank currently does it - I told them (in person when setting this up) a pass code, when logging in, they ask me for random sections of it (ie 1st, third and last digits).
The scammers must manage to fool me multiple times to gain complete access to my account details.
Re:I don't have time for that junk (Score:4, Informative)
Re:I don't have time for that junk (Score:5, Insightful)
Re:I don't have time for that junk (Score:3, Interesting)
The thing about that is it's just one more thing to tip a user off that something's not right. You might catch some people with that, maybe even the vast majority, but suppose it only stops 5% of users from continuing. That's a 5% reduction in phished account passwords, and that's not too bad. Sure this scheme isn't going to solve the whole problem, but any little bi
This works even for email from the bank (Score:2)
Combined with some improvements in browsers that are being worked on, this is not bad. Though the answer 3 questions part has problems and isn't in theory any better than a
Re:This works even for email from the bank (Score:2)
Re:I don't have time for that junk (Score:4, Insightful)
There is a way to deal with this problem too, but I can't go into it at present. (Sorry)
Re:I don't have time for that junk (Score:3, Funny)
Re:I don't have time for that junk (Score:3, Funny)
"even by email to alert a user that it's happened" (Score:3, Insightful)
Re:I don't have time for that junk (Score:2)
You have typed in your password, and the phisher already has it . .
Anyway, how difficult is it for the phisher to fetch the picture from the eral site, and show it to you . .
I still reckon the NetCraft toolbar (or similar) is one of the best solutions available. Show the history of the site, for the user to check.
Now, I've heard that it is trivial to fake by framing the untrusted site, but that is an implementation detail, which can be fixed. The concept is still g
Re:I don't have time for that junk (Score:2)
Not necessarily. The system probably works as such:
If someone tried to phish you they'd get your username and password, yes, but you'd then see that the image your bank sent you was not authentic, so you would then not enter your personal answers. You'd have to
Re:I don't have time for that junk (Score:2)
But the phisher probably works as such:
1. You enter your username and password
2. The phisher uses a botnet[1] to fetch the picture from the real bank site
3. You verify the picture
4. You enter the answers to your personal questions
5 The phisher gains access to your account.
Game over. Thanks for playing.
[1] Use of a botnet prevents the bank from spotting lots of requests from a single location.
Re:I don't have time for that junk (Score:2)
Re:I don't have time for that junk (Score:4, Informative)
1) You enter your username/password on the phishing site.
2) The phishing site then uses this username/password to retrieve the image from the bank site
3) You verify image
So when he is talking about botnet, he is talking about logging on to the bank site as you using the username/password you just gave them and then showing you the image returned from the bank site.
One more little hurdle for them to overcome which is good, but certainly not fullproof.
Re:I don't have time for that junk (Score:3, Interesting)
For a phisher to break this he would either need to know the 3 questions or he would have to read your BofA-site-only cookies (don't know if such an exploit is possible) and use your username and cookie to
Re:I don't have time for that junk (Score:2)
So do they show it before you log in? If so, what's to stop me going to the site and asking for your picture?
After? Then it's too late.
And yes, I did RTFA - my favourite quote was Although SiteKey wouldn't have prevented recent high-profile security breaches, it shows how seriously the bank considers security.
So basically it's another hoop to jump through, that won't help. Great work
Re:I don't have time for that junk (Score:2, Funny)
Of course your on the real bank website
The real website however would say:
Of course you're on the real bank website
Re:I don't have time for that junk (Score:2)
You need a second level of authentication. The password verifies you initially to make sure that you're very very likely you, so that they can show you your secret image (if people that aren't you can see your bank verification picture, then the picture ceases to verify the bank), then the
Re:I don't have time for that junk (Score:3)
So the question is what does it provde that SSL does not provide for already..
The most important thing it provides for is yet another human check on if the site is really the website of the bank.
Currently people have to carefully check the url (in the address bar and on the SSL certificate), which we know to not work very w
Useless. (Score:5, Insightful)
What is your credit card number?
What is your credit card's expiration date?
What is your credit card's three-digit CCV number?
Seriously though, I don't care if you require users to use ten pieces of personal information. They'll still choose to use the same information at 90% of the sites they deal with. And there will still be people with access to that information - whether they're administrators and customer service persons or crackers who steal their database full of customer data. The only difference is that instead of having your password and maybe credit card stolen, you'll also have thieves who have three or more pieces of personal information about you.
Thanks, but I'll keep using the ambiguous password. It's easy to find out where a person was born or when or what their maiden name is. It's a lot more difficult to guess that their password is aPh1l@m8.
Besides, I never give those "personal question" fields real information. Then I end up not only having to remember a password for each site, but a fake maiden name, birthplace, favorite team, first pet and so on. Screw that noise.
And if you're dumb enough to think that PayPal really is sending you two dozen queries about the validity of your account per day, you should just give your money away and shoot yourself in the head anyway.
Re:Useless. (Score:5, Funny)
What is your quest?
What is your favorite color?
Re:Useless. (Score:2)
JavaScript:alert("Congratulations, you are a fish!")
Re:Useless. (Score:4, Informative)
- Three questions are one time only and are NOT credit card or account related
- You also choose a tacky photo
- Once the questions are set then it will ask you only one time from the machine you are at to answer one of the three questions
- Once you have answered you are presented with the tacky photo and a request for your password
- You have to reauthenitcate at each machine you are at and let BoA know if you want that machine added to the list of "safe" machines, meaning you don't have to answer the question again and are presented with only the photo and request for password.
whew!
Re:Useless. (Score:2)
UK has had this kinda of tech for ages (Score:5, Insightful)
There are always going to be people who are too careless with their information, and there will always be other people who are very willing to take all of your personal information to clean out your bank accounts..
Re:UK has had this kinda of tech for ages (Score:2)
A friend of mine when he accessed his bank in sweden had a one time password generated on part from the web page and from part generated via a little calculator device they gave out free.
This combination seemed to me much more secure and also since the passkey was a one time only useless to anyone monitoring his computer.
Re:UK has had this kinda of tech for ages (Score:3, Insightful)
Halifax do the same, but cahoots system is flawed in a different way than all multi-question systems are flawed.
Firstly, cahoots flaw, because it's funny.
I've had a cahoot account for a long time, long before they changed to asking for 2 letters from an answer, entered from drop down boxes. The first time I tried to login with this new system, I could not, because the answer to the question they kept a
keyloggers aren't useless (Score:4, Informative)
the latest PW_Glieder trojans will keylog and report back over a period of time: if you access your online banking a few times and are asked for characters X and Y from your password, chances are quite high that after a few logged sessions, the hacker will have enough info to build your complete password.
this is very common indeed: current SOP is for them to move your money to another account at the same bank to which they've already stolen a matching debit card. move cash, then confederate will go into a branch and withdraw the money in cash and vanish...
Re:keyloggers aren't useless (Score:2, Interesting)
Any bank reasonably worried about security should not require either of these (and would recommend that they be switched off)
Barclays don't require Java or Javascript and their online banking isn't that hard to use so there really isn't any excuse.
Tim.
Re:keyloggers aren't useless (Score:3, Insightful)
The important bit being the dropdown box. Sure, some browser plugin might still be able to get in the middle, but a keylogger is useless.
You say you lost money, did NatWest pony up the cash, or were you personaly responisble?
Monkey in the middle (Score:2, Interesting)
Re:Monkey in the middle (Score:2)
How will SiteKey stop phishing? (Score:2, Interesting)
"Customers can also verify they are indeed at Bank of America's Web site by clicking on a SiteKey button. If they fail to see a secret image and phrase they had chosen earlier, they could be at a fake Web site and the target of a "phishing" scam."
So... once the person has given his account id, password, and answers to 3 personal questions, only then can he verify BofA's site identity?
What kind of idiot came up with that idea?
Re:How will SiteKey stop phishing? (Score:4, Insightful)
Still though, it seems like a potential flaw would be that you have to click on something to verify you're on the banks site. Why not just show you your picture by default? It seems like a lot of people just wouldn't bother verifying the site and they would get phished the same as they would be now.
Re:How will SiteKey stop phishing? (Score:3, Insightful)
So, if I were a phisher, I'd work it like this:
User: *enter u/p on phishing site*
Phishing site: *slurp*
Phishing site: *log in to bank site with new u/p and retrieve image*
Phishing site: Look! We're really the bank, see??
User: *phew!* *enters ot
Re:How will SiteKey stop phishing? (Score:2)
Of course I think a smart phis
Re:How will SiteKey stop phishing? (Score:2)
Re:How will SiteKey stop phishing? (Score:2)
Re:How will SiteKey stop phishing? (Score:2)
I think the order should be more like:
not a solutun, by any means (Score:2)
Just use a password over https and hope for the best, until something more usefu
3 PERSONAL Questions (Score:5, Funny)
1. Religion?
2. Who you voted last election?
3. Are you a terrorist?
Re:3 PERSONAL Questions (Score:2, Interesting)
Simpler solution: password cards (Score:5, Informative)
In order to actually do stuff the bank (and all Finnish bank sites I know of) use a challenge/response system: I have a card which has a bunch of randon number passwords on it, around a 100, in number: password -pairs. The site asks for "password number X" (one number per session) and I give it. These passwords are unique to my own account, and the card has no identification, so if my wallet gets stolen it's useless without knowing which bank and account it's for, as well as the username and password for logging in.
If I were fooled by a phishing site they'd get one of the hundred passwords required for a transaction, and the bank would notice pretty quick if they tried logging in and out for hours trying to get the correct challenge assigned to the session.
Simple, yet very effective.
Re:Simpler solution: password cards (Score:2, Interesting)
Re:Simpler solution: password cards (Score:2)
Re:Simpler solution: password cards (Score:4, Interesting)
A few months ago, a well known Dutch bank (Postbank) was targetted, with scammers directing people to a phishing site. This site asked for their username, password, and the next 3 of these codes (many people mark the ones they've used).
Many people were duped, proving that it's not that good for security.
Far better is the card/token type system (see my comment for details [slashdot.org]).
Re:Simpler solution: password cards (Score:2)
And at least some of those pieces of information is already in there with the card: your bank cards describe both your bank name and account. All one has to do is map the password cards back to the corresponding bank card, which is not necessarily all that difficult.
That said, I do like that idea better than this SiteKey one...
Ah, Geez. More coding (Score:3, Funny)
With the HTML they'll have to keep churning out, pretty soon phishing is going to seem like a real job.
and this "prevents" it how? (Score:3, Insightful)
I just don't think changing the login procedure for the actual site has anything to do with stupid people clicking fake links and entering their info into a phishing site... If I'm missing a piece of this, please, do tell.
Re:and this "prevents" it how? (Score:2)
Your thought is great and all and sure, people might setup all this picture and question crap, but my point is... most of these people are lucky if they can remember how to turn their monitor on. It's VERY unlikely they'll care if the site they're logging into doesn't have some picture showing up on it.
Here's the thought process:
"what? how is my information out of date? oh well, i'll just go update it"
*click*
"hmm... i wonder where my little picture is? oh w
Similar but effective (Score:2, Interesting)
When it comes to cash, I'm more concerned with security than spending less time logging in. I think asking for randomized data sets at each login is a good move.
While its not the perfect solution (if the machine is compromised it would only take a matter of time before the phisher got the info) having a rotating login is slightly more comforting.
Bad rip-off (Score:3, Interesting)
The first, using a "personal question" as a means of making easily guessable passwords more secure is dumb. It is true that people often choose easily guessable passwords. But people *even* more often choose easily guessable "personal questions". "Mothers maiden name" for example. That's how Paris Hiltons adress-book got cracked: She'd used the hugely difficult "personal question" about the name of her dog. It takes only 10 seconds of googling to find the answer to that...
The personally selected secret image on the other hand is a good idea: phishers rely on the fact that they can easily create a fake website that looks like the real one.
If the real one has some element that is unique to you, they won't be able to copy that, simply because they don't know what it is.
This *ain't* the system common in Scandinavia (and other countries) by the way. What we have is generally a one-time "tan" to authorise transactions, provided either as a paper-list where you cancel out those you used, or from a small cryptographic device that generates them using the current time, your account-number and a secret embedded key.
It is, however, just a weaker version of the proposed "security skins", which is an excellent idea to prevent or reduce phishing.
My bank, Skandiabanken does this, sort of, already. (though they underpublizise it). There each user has a private security-certificate used to authenticate the user, in addition to the pin.
This helps in two ways:
First, even if you knew my customer-id and my pin, you still could not log in on my account, you wouldn't have the certificate.
Secondly, it enables the bank to identify me even before I log in, thus giving me a personal greeting not easily copied by phishers: on the login page, before I've entered anything the bank says: "Hello Eivind Kjørstad."
Phishers have no easy way of doing that, they generally don't have a clue which user is sitting behind which ip.
Other people have tackled the obvious problems. (Score:2)
The way to secure against pishing is to use media the pishers don't have access to. The best way to do this is with a physical token. The best example is something like RSA's SecureID. There is no way for the pisher to know what that value is so it makes pishing harder. They may be able to get the value once,
Geezz ... (Score:2, Interesting)
More feel good security (Score:3, Insightful)
There are a few questions I'm not going answer online and I'm guessing most of them will suggested questions.
The last issue is why the high security when its not needed? My credit card balance is public knowledge at least to anyone that can do a credit check which limits it to about 10 million people.
A better system is typical lame password security access for read access to balances and transaction lists but an extra layer when I want to do something like move money to a different account and maybe an extra layer if I want to do something like move money to a foreign country.
How? (Score:2)
Obligatory (Score:5, Funny)
Sir Lancelot: My name is Sir Lancelot of Camelot.
BofA: What is your quest?
Sir Lancelot: To seek the Holy Grail.
BofA: What is your favorite color?
Sir Lancelot: Blue.
BofA: Right, off you go.
Not very effective.. (Score:4, Interesting)
You put your bank card in the device, enter your PIN, and then enter a number given on the site. Hit OK and put into the site a number returned by the device. The algorithm requires the pin number and specific card to calculate the number, so dictionary attacks are thwarted.
Having these 3 personal questions is of limited effectiveness - until the scammers simply make a phishing site which asks the same questions.
Why can't US (and Australian) banks just issue these card reader/token devices? It satisfies the requirements of user authentication.
- Something you know (your PIN)
- Something you have (card + device)
I guess they're too cheap to do it and rely on fraud insurance to compensate for lost money.
Re:Not very effective.. (Score:2)
But... these tokens don't stop a man in the middle attack if the user isn't paying attention to the SSL certificate.
In Denmark there are 3 solutions (Score:2)
The 2nd best is a keycard, with 80 one-time 4-character passwords on. To logon you need your SSN, card identity and a 4-digit password from the card. To verify transactrions you need to enter another 4-digi
Re:Not very effective.. (Score:2)
Australian banks have started sending one-time passwords via SMS to your mobile phone. You must type the 8 digit code from the SMS into a text field before the transaction is completed.
Security Morons (Score:2)
Their "solution":
How about a reverse password... (Score:2)
Reverse the logic for it to work (Score:3, Insightful)
Me (arriving at site): zooble my gooble?
Bank Site: flooble
Me (ok I trust you)
Instead of the site asking me for a password, I give the bank a challenge word or phrase, and I expect a certain response.
Re:Reverse the logic for it to work (Score:2)
Bank Site: What is your login ID?
Me (arriving at site): 123456
Bank Site: Here is a picture you gave us.
Me: OK I trust you.
still (Score:2)
How this actually works... (Score:4, Informative)
At any rate - when you sign-up for site key, you have 3 questions you can pick and give the answer to. You also select YOUR "siteKey" image.
From that point forward, when you go to the BOA site, you enter your Login ID, click "Login with siteKey" and it will display your sitekey image. This verifies that it is a BOA website because it displayed you the correct image.
That's all the image is for- verify this is a real BOA website. That is the purpose anyway.
You are then asked to enter your normal password and are directed to your account information.
Now, for the secret questions. Those come into play when you are accessing your account via a PC that was not the original PC you setup siteKey on. If the PC is not recognized (via a cookie I am sure), you are displayed 1 of your 3 questions rather than the sitekey image.
When you answer the question, you are displayed the sitekey for verification and login as normal.
Anyway, that is how it actually works. It isnt asking you 3 questions AND your password every time you login.
Re:How this actually works... (Score:2)
One possible problem. (Score:3, Insightful)
Presumably they only have a limited number of images. The phisher can display one of the possible sitekey images at random. They will only catch at most 1/N victims, but they will have a better chance of catching the 1/N that they do match because that person will have seen the right sitekey.
Swedish banks (Score:2)
The bank identifying its really them is something we dont have in Sweden. It re
Much better system (Score:2)
For a scam site to be able to crack this they need to live interface with the real bank, so they login at the bank site once you enter your code on their site. Grab the codes of the banksite, show them to you etc etc..
Hum sorry (Score:2)
because it doesn't help with trojans (Score:2)
Re:because it doesn't help with trojans (Score:2)
we will soon see a lot of mail like (Score:2)
new Bank of America SiteKey.
SMS authentication is already being used! (Score:5, Interesting)
Whenever you transfer money or pay a bill (ie. anything risky), it sends a unique code via SMS to your phone. You then type that number into the system before it does the transaction.
It's free too.
It's highly unlikely someon has both stolen your mobile phone AND phished your details.
Hello, this is the Visa card center calling. (Score:5, Insightful)
- Yes, that's me. What's the matter?
- We'd like to confirm. Are you trying to make a big purchase in a shop in New York?
- No! I'm in Washington, DC! Oh my god! My wallet is missing! My card has been stolen!
- Would you like to cancel the transaction and block your credit card?
- Yes, please! Right now!
- In order to do so, we need to confirm that you are indeed John Doe, the owner of the card and not that mr Doe's phone has been stolen.
- Please! How do we do it?
- Please give me the number of the credit card in question.
- I don't remember!
- Expiration date?
- Next year, july or june, or maybe august...
- sorry, I can't take that for an answer. Any other info? Maybe the account number associated with the card? Or maybe the PIN number?
- The PIN is 8352
- Thanks, sucker!
Dear Customer: (Score:2)
Sincerely,
Bank of America Security Department
Catch (Score:2)
What the bank should do is ... (Score:3, Interesting)
Does HTTP support signed web pages (as opposed to just encrypted transmission)?
Note that the authenticity verification would not depend on some third-party certificate (where you have to trust some certification agency possibly unknown to you), but on a paper sent to you on paper by the bank itself. Thus you have only to trust your bank (if you don't trust that, you'd better change it anyway), and fraud would need to intercept both the bank web site and the postal delivery. Which I think will be beyond the ability of the typical phisher.
BoA should read this (Score:2)
http://www.unix.org.ua/orelly/networking/firewall / ch10_02.htm [unix.org.ua]
But BoA's new system is just something you know, something else you know, another something you know, and yet another something you know. Unfortunately, teh Intarweb combined with the hardware that home users normally have isn't really suited
The summary is wrong (Score:2)
Personally I hate SiteKey, it causes me to go to an extra screen when I sign in to my online banking site. I wish that there was a way to deactivate it, or at least a way to eliminate the need to type my password in twice. Eh, I guess that it might get better.
Hmmm.... (Score:2)
Token-based security? (Score:2)
I'm already using it (Score:2)
It works like this
And this will help how? (Score:2)
back door taped shut, front door still wide open (Score:3, Insightful)
Comment removed (Score:3, Informative)
Why not 143 passwords and 79 questions? (Score:3, Insightful)
Banks are Dumb. (Score:3, Interesting)
Sitekey is better than article states (Score:3, Informative)
Why not properly use existing solutions? (Score:3, Insightful)
The certificate system underlying SSL is already largely in-place, particularly for trusted/confidential sites, and it provides relatively assured proof of identity. The problem is that there's no way we can expect users to click on the little lock icon, and examine or understand certification paths, issuers, subjectAltNames, etc.
Why don't browsers simply make this more plain and prominent? Why not just interpret this information and present it clearly to the user? Just an integrated toolbar that says in plain english/french/german/japanese/etc. "You and your browser know and trust the certifying authority of Verisign, and according to Verisign, this site [your bank name here] is who they claim to be. Chances are you're safe."
And if something is off, instead of a pop-up box with three relatively cryptic security alerts to which everyone has been trained to say "yes" regardless of understanding, try simply "The identity of this site cannot be confirmed. Click for details, proceed with caution." Different discrepancies can provide commensurate levels of warning to try to avoid cry-wolf syndrome.
This, combined with existing (and also underutilized) techniques to mitigate URL obfuscation won't be perfect, but they will go a long way, and it only requires a little effort from the browser folk.
Re:A button? (Score:2, Informative)
from TFA: "Customers can also verify they are indeed at Bank of America's Web site by clicking on a SiteKey button. If they fail to see a secret image and phrase they had chosen earlier, they could be at a fake Web site and the target of a "phishing" scam."
Re:Can you say... (Score:2)
You're right, but that's not the way most phishing scams play out. Most of them are sent by e-mail. Getting rid of phishing scams like that defeats a large portion of the threats, as well as raising the level of skill required of a person who might want to start a phishing scam (yes yes, it's still not terrifically difficult, but it's not as ea
Re:Doh! (Score:3, Insightful)
The image/phrase shown is supposed to be a secret one that the customer chose beforehand (i.e. when setting up their account).
So, when I go to my bank site and click the button (presumably after logging in so they know who I am), if I don't see the cute little picture of my son and the phrase "you're cool", then I know it's a fraud.
It's not just a standard image/phrase... it's customized and unique.
RTFA, or even TFComments.
MadCow.
Re:Doh! (Score:2)
Re:Doh! (Score:2)
It will at least make it harder for phishers though.
Re:FIRST FISH! (Score:2, Funny)
Maybe
See, I thought so.