I'm going to give my opinion on the various options
- Static IP/MAC/HW checking
Implementation on this is hard. I would agree for non-dynamic IP users or users who will be on a limited number of IP ranges (just enable the entire range). Keep in mind that IP might change for some reason and this will cause trouble (we had some serious trouble when our IT department changed the main router last week). A good way to communicate and confirm the change would be nice.
- Strong password policy
I don't believe in more enforcement. Many people don't want the trouble of a 'strong' password, even if that trouble does not really exist.
The main problem is using the same credentials on various places.
To discourage brute-forcing it would be nice if a IP address or range can be put to slower logins when failing (not entirely on account level, else there is the possibility of denial of service).
- SecurID authentication option
This is a great option. I use this for work as do many other people. One major problem. Battery will be empty in time. We had this problem several times with people in our IT department who use their token often. And we are not even talking about the people spilling drinks on the item or putting it in the washing machine.
- "NO DELETE" option on characters/items
I think this is good, I would call the option 'fix to account'.
Meaning marked items cannot be deleted, salvaged and cannot be moved from the account to another account.
- Authentication for storage access
I don't see much added value to this. The 'fix to account' option mentiond above should work better.
I know some websites offer a 'pin' to protect specific 'valuable' area's.
It might slow down a hacker, but why is he on the account anyway.
- Randomized point and click input for passwords
Would work against keyloggers. I can see some use for this, but not too much. I think it would be annoying if you d/c about every 15 minutes and have to log in while searching each time
- Compromised account restorations
Ah, rollback. Sounds nice, would not work except when disabling trading
- Other H/W solution
One thing on the 'fingerprint'. We have those at work on some workstations. Funny things. Till one colleague of mine called with the message: I cut my thumb last week and cannot log into the system.... Lucky the help desk for that application has quick response times.
- Other S/W solution
- No additional security required
Let me say this.
I do believe that account safety is very important. However, first priority is keeping unwanted people of the account, which is mainly concerned with the user. A-net can implement some things to help here, but this is not their main problem. It will be if their systems are hacked and credentials are stolen from them though.
There are plenty advices on the internet how to make accounts more safe. One of those advises is not sharing the same username/password combination everywhere.
Another is not downloading from an untrusted source or run security measures (like virus-/mallware scanner).
When an account is compromised nothing more can be done. People can do whatever they want with it. Sure, you can have an option that prevents all bad things. However, the hacker might get annoyed and rant in local chat in a major outpost, causing a perma ban (and while busy also change credentials so that you first have to get the account back only to find out it's perma banned).
My suggestion will be in the 'strong password policy'.
Have A-net do a simple check on strength.
All same characters, same case, dictionary for commong languages, low length = red
Variations in case or addition of numbers, low length = orange
Variations in case combined with addition of numbers, decent length = yellow (ish)
Variations in case with addition of special characters, decent length = green.
Give the result back when it's not green with a warning message depending on color. Red = huge warning, yellow = suggestion to add some special characters. People can choose to accept the unsafe pass or type a new stronger one.
And another suggestion. When the password is to be entered make a
HUGE message on the window to please, please, please not use the same password as on other online resources.
The second option is something that A-net might implement with not that much effort.
However, I don't think we should expect this from them. Individual account safety is
YOUR responsibility, not theirs. When it's about their databases containing those credentials or the servers running guild wars it's A-net's responsibility. But we are not talking about that, are we?