This 6-page PDF, Ten Myths for Safe Web Browsing sophos-myths-for-safe-web-browsing-wpna.pdf cites data from 2008 about how malware can hitch rides on web page content and browser plug-ins into your computer (or mobile device). I have a few maybe grasping at straws hopes:
1. Browsers have been updated a zillion times since 2008 so might have gotten smarter against malware.
2. Ditto for plugs-ins and extensions such as ActiveX, Flash, Acrobat.
3. With HTML5, maybe plug-ins will be a thing of the past.
4. The software of your browsing platform should have gotten smarter too.
5. Ditto for 'local' security software, cleaning apps and operating systems.
What's this got to do with marketing?
Evil-doers such as malware writers are market drivers. They are getting smarter too so their products create demand for new browsers, operating systems, plug-ins, and (surprise, surprise) demand for new security applications. Software standards like HTML5 help to vitiate vulnerability from plug-ins. No doubt cloud-based security products are enjoying strong growth.
Neglecting the allure of maliciousness for its own sake and the two other motivators of malware (see footnote)*, I believe the commercial disseminators of malware are motivated by advertising and industrial espionage. There is real business value in infecting users' platforms. Malware can commit fraud by re-directing users to click-throughs. Pay Per Click advertisers pay for 'fake' clicks generated by malware. Is it too paranoid to suspect manufacturers of platforms and system software of using malware to build-in obsolescence or to covertly co-market with publishers of security or performance acceleration software?
At the end of this white paper is an ad for Sophos' 'end point security solution.' The fact that the authors point out these ten vulnerabilities ought to signal that their product protects against those malware entry points, but marketing pieces may not always comply with 'the truth, the whole truth...'
---------------
*Malware allow evil players to use your computer to do their deeds without your knowledge. Another high-value motivation for malware infection is theft of credentials and/or data.
Showing posts with label security. Show all posts
Showing posts with label security. Show all posts
Jul 6, 2011
Aug 6, 2009
Managing online credentials
Managing one's web credentials is a very important topic that is especially relevant to privacy, especially for social media sites. Do web users have too many different credentials and find it troublesome to manage them?
There are primarily three ways to 'remember' your credentials:
For low level credentials such as your subscription to a newspaper, it doesn't really matter that much if someone accesses your account. I make my username and password the same, such as "mariatseng" as username, and the same string, "mariatseng" as the password.
It is critical that you remember the rules (protocols) you made up to create usernames and passwords, such as 'same username and password for magazine subscriptions' but for important applications, use 'email ID as username and patriotic song for password.' It's ok to write your rules down because whoever is spying still must discern the specifics.
There's lots more to say about this topic, and there are lots of experts, entire fields in computer science for security and encryption.
There are primarily three ways to 'remember' your credentials:
- Use storage and retrieval methods that are at your end:
- biometric authentication e.g., your fingerprint recognized by your computer. Biometric authentication only controls access to your local, individual computer. What happens when there's a software error, for example, with your biometric software, or when you move from versions of operating systems, change computers, or are a victim of malware? Or when your computer is damaged? As of now, more intelligent authentication methods such as face-recognition are not yet commercialized.
- Cookies or Browser-based which means your username and passoword are stored on your computer.
- A pass-worded document on a hard-drive or a piece of text saved on another device such as a mobile hand-held
- (God forbid) a hard copy such as a Post-it note stuck to the bottom of your PC
- In your head or in your wife's head
- Storage methods that are 'remembered' by the websites that you must log into such as your bank account, social networking sites like FaceBook, and/or other subscriptions. Some sites are more secure than others. Most just use cookies; others encrypt and validate through sophisticated methods. Most subscription log-in pages should have a way for you to ask them to email to you a new password, but you must get your username right or answer their security questions so that they can send the new password to the correct email address. The better ones will send you a new temporary password that you must change immediately.
Many web sites that provide primarily content (such as newspapers or blogs) now post 'share' links to popular social networks like Facebook, del.icio.us... but they are relying on those networks to check your credentials.
- Store your credentials in a central place on the web, either at a provider like Google or Verisign, or elsewhere.
One such initiative is OpenID where groups of web sites agree to 'recognize' the log-in credentials of other web sites. You will see sites that say you can log in using, for example, your Facebook or Twitter credentials. Google has integrated their applications with a single sign-in. Once you log into Google, you can use many (if not all) Google applications such as the calendar, documents, Wave, Feedburner, etc.
- introduce point solutions
- then offer a 'swarm' of incompatible solutions that don't work together,
- followed by ones that interoperate meaning they're not 'native' but do work together
- and, finally, after technologies, standards, licensing deals, APIs or open source code have been worked out, and the market is mature enough to support profitable pricing models, we will have 'end to end' or 'universal' solutions.
- Use the same credentials everywhere. This is ok provided those credentials are 'strong.' "Strongness" means username and password that are hard to guess. There are programs that test for credentials so they're not just guessing.
- Use variants on the same credentials. This is better than 'the same' but the complexity might make it just as hard to manage as altogether different credentials. You can create 'protocols' for yourself like in the paragraph below after 'strong passwords.'
- Using your browser's 'remember me' is not very secure.
- Many sites now use your email address as a unique username. That is easy to find out or guess. Many people use their ISP's email address so when they change ISPs, it can become a problem (although ISPs have gotten smart and keep those users active instead of deleting those addresses). So, many web sites now rely 'solely' on your password for authentication.
- 8 characters or longer, use one or more capital letter(s), one or more number(s), one or more special characters (some authentication software have limitations such as you cannot use a dot, or underscore)
- A good way to make strong passwords is to use the first letters of words of song lyrics, such as "Oh Say Can You See! 1776" to create the password: "Oscys!1776"
For low level credentials such as your subscription to a newspaper, it doesn't really matter that much if someone accesses your account. I make my username and password the same, such as "mariatseng" as username, and the same string, "mariatseng" as the password.
It is critical that you remember the rules (protocols) you made up to create usernames and passwords, such as 'same username and password for magazine subscriptions' but for important applications, use 'email ID as username and patriotic song for password.' It's ok to write your rules down because whoever is spying still must discern the specifics.
There's lots more to say about this topic, and there are lots of experts, entire fields in computer science for security and encryption.
Labels:
authentication,
credentials,
login,
password,
security
Subscribe to:
Posts (Atom)