Account Security (major changes that require customer support actions to be carried out)
in Suggestions
Posted by: Spec Op.5670
Essentially I am making this post to suggest a solution to a potential problem. The first post will identify the issue and the second will propose a solution, as I’ve not been able to post it all under one.
Currently, if you have a major account change you need to go through customer support to have it carried out. For example, changing your e-mail address associated with the account and having it recovered if it was stolen.
To complete these requests generally speaking they request your Serial Product Key to to verify the account as “yours.” You can do this when submitting it to them via the support ticket generator tool that is used to communicate to them.
EX:
Hi my name is X and I need my email changed from Y to Z.
My serial code is 1234-5678-90ab-cdef.
Thanks!,
X
This all seems fine. You have sent an message to customer support proving this is your account (after all you are the only one who has access to that serial number) and they can verify this and carry out this action for you.
Here are the problems I notice though when looking at this system though:
All of this is essentially conducted via an e-mail support system. They communicate to you via e-mail with the ticket history and you communicate back, again, via e-mail.
E-mail unless encrypted is sent via plain text.
This e-mail system is not encrypted.
Plain text means that if someone sees that e-mail they see exactly what is in it. Encrypted means there is some sort of method used to hide the message (there are numerous ones with different degrees of effectiveness.)
That may not seem like much of an issue until you consider the following:
Assuming both the customer service e-mail account(s) and the end user’s account are secure, the e-mail is passed on to multiple servers / locations / computers as it makes its way to its destination. (Think of it like crossing multiple territories/states/countries to get to your travel destination.) The problem exists in the simple fact that during its travel between the two parties that e-mail can easily be intercepted by someone with a little bit of talent and know how. Now you may think, “What issue is that of mine?” Well, its a big issue and here is why.
If someone were to intercept that e-mail, they now have the entire conversation, which just so happens to contain the e-mail addresses of the parties that are communicating, probably the end-user’s name, and the serial key that is required to carry out changes and prove ownership of that account.
All of a sudden, you, the end-user, now share your account with someone else unwillingly. They are able to contact customer support with your serial key and cite your e-mail address and with a little bit of a story perhaps, impersonate you and take over your account.
While this seems grim, keep in mind they do not have access to any payment methods used or your password or anything extremely compromising. While they can get your password reset and e-mail changed and wreak havoc on your virtual characters and their wealth or reputation, you can always submit an e-mail or support ticket and get that account right back. Essentially you and the thief will play keep away as much as possible passing the account back and forth until it gets resolved somehow, which it probably would be very hard to do and faithfully know whose account this is. If you purchased it directly from ArenaNet you at least benefit from the fact that you need some more purchasing information and can potentially find another avenue of contact with them and give them the aforementioned information in its entirety and possibly get a serial key change. If this happens, please don’t use e-mail again as it was how you were exploited.
I hope I’ve been clear enough in explaining the potential issue or exploit that can occur with the current customer support solution.