If you don’t understand Net Neutrality, perhaps this video will enlighten you. It shows what the ISPs want to do to kill the idea, and why. That’s all I’m going to say. Arrive at your own conclusion after viewing this informative (and refreshingly snarky) video.
In its annual report issued in April of 2013, the Electronic Frontier Foundation examined the policies of major Internet companies to assess whether they publicly commit to standing with users when the government seeks access to user data. This, of course, is in response to the revelation that the NSA has literally been spying on every single U.S. citizen. They have been posting updates regularly showing who is doing what. The latest, UPDATE: Encrypt the Web Report: Who’s Doing What shows a good picture of what is happening to your information as it passes through various providers and services.
We’ve asked the companies in our Who Has Your Back Program what they are doing to bolster encryption in light of the NSA’s unlawful surveillance of your communications. We’re pleased to see that four companies—Dropbox, Google, SpiderOak and Sonic.net—are implementing five out of five of our best practices for encryption. In addition, we appreciate that Yahoo! just announced several measures it plans to take to increase encryption, including the very critical encryption of data center links, and that Twitter has confirmed that it has encryption of data center links in progress. See the infographic [Which I have also provided below… Ed].
Regardless of your opinion of what Edward Snowden has done by leaking NSA documents, the result is that ISPs and other public service providers have become security conscious to a high degree. This is a good thing.
Microsoft Security Advisory (2914486) warns of a zero-day vulnerability in a kernel component of Windows XP and Windows Server 2003 that can result in an elevation of privilege: “An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. An attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights.”
It does not affect newer versions of the desktop or server OS beyond XP and Server 2003.
It’s not critical. “An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.”
If you’re worried about it, here’s what to do:
“For environments with non-default, limited user privileges, Microsoft has verified that the following workaround effectively blocks the attacks that have been observed in the wild.”
To implement this workaround, follow these steps:
- From an elevated command prompt, execute the following commands:
sc stop ndproxy
reg add HKLM\System\CurrentControlSet\Services\ndproxy /v ImagePath /t REG_EXPAND_SZ /d system32\drivers\null.sys /f
- Restart the system.
Microsoft warns: “Disabling NDProxy.sys will cause certain services that rely on Windows Telephony Application Programming Interfaces (TAPI) to not function. Services that will no longer work include Remote Access Service (RAS), dial-up networking, and virtual private networking (VPN).” If you have problems after doing this and have to undo the workaround, here’s how:
- From an elevated command prompt, execute the following commands:
sc stop ndproxy
reg add HKLM\System\CurrentControlSet\Services\ndproxy /v ImagePath /t REG_EXPAND_SZ /d system32\drivers\ndproxy.sys /f
- Restart the system.
The recent Adobe hack revealed that people still haven’t been listening, don’t care or are just too lazy to bother coming up with good passwords. Here is some interesting data about that hack from this article at ITProPortal:
Security researcher Jeremi Gosney conducted a study on the massive dataset, assessing which passwords were most frequently used by Adobe users.
According to the research, “123456” came out as the most popular password, with 1.9 million instances, representing 1.26 per cent of all users. This was closely followed by “123456789”, “password” and “adobe123″.
“1234567890”, “1234567”, “1234”, “123123”, and “abc123″ were strong contenders too, all featuring in the top 20 passwords used.
Slightly more surprising are “qwerty” and “azerty” (the first six letters used on keyboards in France and Belgium), as well as the touching “iloveyou”.
I hope you’re not one of those whose password matches any of these. Better yet, I hope you’re not one of the people whose credentials were compromised.
You can check to see if your email is among those who were leaked by entering it here: http://adobe.cynic.al/ at the “Adbobe Leaked Credentials Checker.”
Even if you find you are safe, please change your password if it’s a weak one, especially if it’s one of the ones listed above. And if you have ever used that password — or any password — at more than one site (heaven forbid at your banking site), fix that problem, too.
To my readers who celebrate this American holiday…
May you have a Safe and Happy Thanksgiving.
Adobe’s October 2013 data breach was not only one of the largest breaches ever, it could have been prevented if the company had stored the user passwords correctly. They didn’t and to their great embarrassment, 150,000,000 records were exposed.
…here is our minimum recommendation for safe storage of your users’ passwords:
- Use a strong random number generator to create a salt of 16 bytes or longer.
- Feed the salt and the password into the PBKDF2 algorithm.
- Use HMAC-SHA-256 as the core hash inside PBKDF2.
- Perform 10,000 iterations or more. (November 2013.)
- Take 32 bytes (256 bits) of output from PBKDF2 as the final password hash.
- Store the iteration count, the salt and the final hash in your password database.
- Increase your iteration count regularly to keep up with faster cracking tools.
Whatever you do, don’t try to knit your own password storage algorithm.
It didn’t end well for Adobe, and it is unlikely to end well for you.
This also got me to thinking about password length and complexity again, so stay tuned for my latest cogitations on that matter.
[Editor’s Note (Skoudis): A few years ago, Marcus Sachs mentioned to me an intriguing idea. He said, someday, it is possible that pretty much every system will have some malware on it, just as our bodies are chock full of viruses and bacteria. But, our bodies handle it ok as long as the infection doesn’t get out of hand and cause damage. The notion was that it will be impossible to be 100% clean, but you can in fact still be operational if you have good defenses (like the body’s immune system). I didn’t like hearing what he had to say then, as it sounded defeatist. But, stories like this remind me of that view of the future and make me wonder if we are heading there. ]
I have recently cleaned several PCs that showed evidence of infection by Trojans and spamware, yet they were performing fine and behaving themselves on the network; the items were sitting in Symantec’s quarantine, having been caught by the AV engine at some point. I guess you could consider that these machines were infected, similar to someone who had the flu virus in their system, but was not suffering from the illness. In the former case, the AV engine acted as the PC’s immune system; in the latter case, the body’s biological structures and processes to locate, isolate, and/or destroy pathogens are its immune system. This view seems to validate Mr. Sachs’ idea.
With all of the malware, old and new, that is already traveling around the internet, I believe we’ve already reached a certain level of ubiquitous infection if only of the infrastructure. As malware continues to get more sophisticated, it’s inevitable that some will slip by our defenses and end up on every PC.
We’ll need a better digital immune system to fight it.
Hackers claim to have hacked the site adobe.com on 2013-11-03 and we’ve detected that your email address was included in the data published as part of the leak. The full description of the leak is as follows:Adobe Systems announced on October 3rd of 2013 that hackers broke into Adobe network and stole source code for a range of products, including ColdFusion and Acrobat family of products. The breach also affected what was at that time estimated to be 2.9 million users but later was revised to include at least 38 million users. Adobe said hackers had stolen nearly 3 million encrypted customer credit card records, as well as login data for an undetermined number of Adobe user accounts. The breach happened in early October but the stolen accounts were not published on the web until early November. The published data includes 10s of millions of accounts with IDs, email addresses, encrypted passwords and more.
Please update the password for your adobe.com account immediately. The LastPass Security Challenge, located in the Tools menu of the LastPass addon, will help find any other accounts using the same password as the leaked account.
The LastPass Team
Seems that I had to change some passwords just a short time back when this happened. I sure wish someone would come up with viable, secure replacements for Adobe apps so we could breathe a little easier.
Black Friday (or Thursday, or Monday, or whatever) is approaching and marks the “official” kickoff of the holiday shopping season. According to the National Retail Federation, if the trend holds, this season will be busier than last for online merchants, increasing approx. 4.9% to $602 billion this year. That’s good news for merchants, who make most of their profits for the year during the holiday season.
It’s also good news for cybercrooks.
Criminals will be vying for their share of the revenues by victimizing unwary shoppers seeking to get the most out of their holiday shopping dollar. Offering super low prices on name brand and designer merchandise is their favorite trick. Here are ten tips for secure online shopping that will help you avoid online shopping fraud this season.
- If the price seems too good, it probably is. That cheap Rolex watch is either a fake, stolen or is really a “Rolev.” Beware.
- Crooks duplicate well-known websites to the last detail. Check the domain. If it’s different than the site, leave quickly.
- Poor grammar and obvious mistakes in spelling are a good reason to avoid shopping on the site.
- Never shop on an insecure website. Make sure you see “https://” in the URL.
- Avoid merchants with no customer service phone number. If there is a number, call it to verify it’s real.
- Avoid merchants with email addresses that don’t match the site’s domain name, e.g., gmail or yahoo addresses.
- Don’t use a debit card; you risk your entire bank account. Use a credit card with buyer protection. Pay Pal is a good option.
- Check public reviews of the site to see what others have experienced.
- Keep all receipts and emails related to the transaction until you have received your products.
- The safest option by far is to simply shop at known reputable sites or sites you have prior successful dealings with.
There is no such thing as being 100% secure online, but if you follow these guidelines, you should be OK.
Security is a dynamic process, never a one-time set-it-forget-it thing. As such, I periodically review and attempt to improve the security of my systems. For some years now, I have been a loyal and happy user of LastPass. Every login to every site I use on a regular (and not-so-regular) basis is stored there. One of the services that LastPass provides is their Security Challenge which examines your password vault, gives you an overall security score, and tells you what to do to improve your security. Here’s my most recent result:
I just scored 73% on the LastPass Security Challenge ranking 69029th overall. It securely analyzes the strength of your passwords, alerts you if you have any duplicate or weak passwords, and tells you how to make them more secure.
Give it a try and see if you can beat my score!
Not a bad score — probably much better than the average person — but I’m not happy with it. Out of carelessness, or just plain laziness, I’ve been guilty of the the biggest password no-no of all: using duplicate passwords on different sites. Seems I’ve used 22 different passwords multiple times on 65 different sites. Moreover, I have 24 passwords that are considered weak and (yikes!) three blank passwords.
So, I’ll spend a few hours of my weekend changing passwords and eliminating duplicates and weak ones.