Editors Note: I’ve been writing a lot about application and web security quite a bit lately, and that’s on purpose. There’s never been more attacks on our personal and private information.  These attacks are comging from not only lone hackers but also from state-supported groups and intelligence agencies. This guest post gives a good overview of what’s been going on and a little on the tactics we can take to combat these activities. This isn’t an exhaustive treatise on how to secure your applications. It’s more an intro course on the topic. It’s a springboard for you to dive into this vast and quickly-evolving world.


Application Security — Cutting Edge Or Critical Failure?

How secure are your applications? While you might be confident about apps designed in-house, what about third-party software for desktops or mobile apps made using open-source code? Are current application security methods doing enough to meet the threat of cutting-edge cybercriminals, or are companies facing critical failure?

Continuing Compromise

At the beginning of March, information-sharing site WikiLeaks published what could be the largest release of CIA documents on record, if the 7818 pages and 943 attachments actually belong to the spy agency.

Non-denial denials aside, however — according to spokesman Don Boyd, “We do not comment on the authenticity or content of purported intelligence documents.” The released data contains a number of application attacks that could presumably net access to almost any device around the world. For example, some files contained instructions for compromising computer applications such as Skype, commercial antivirus programs and even PDF files. Applications such as “Wrecking Crew,” meanwhile, could crash targeted computers while others claim the ability to breach both Apple and Android smartphones, in turn bypassing the encryption offered by tools like WhatsApp, Signal or Telegram. It doesn’t stop there, though. A program code-named “Weeping Angel” — which the documents claim was developed in partnership with British intelligence — supposedly used Samsung smart televisions to listen in on conversations even when the device appears to be turned off.

There’s also another level of concern here: An authentic leak means that even CIA servers and storage solutions aren’t of reach for interested hackers. If the vaunted spy agency is at risk, what’s the downstream consequence for the average application or device?

Emerging Threats

While the WikiLeaks story may be top of mind given its high-profile target and potentially dangerous app attacks, it’s not exactly an outlier: Applications across multiple industries and government agencies are now under threat.

Consider the rise of connected-vehicle applications. Recent research suggests that Android-based connected car apps could be easily hacked if attackers gain access to rooted phones or convince users to download malicious files. Once in control of the car app, cybercriminals could leverage the tool to gain physical access without setting off the alarm. Seven of nine car apps tested were vulnerable. Research firm Kaspersky noted that the problem didn’t stem from code flaws but a simple lack of defense. According to security researcher Victor Chebyshev, these apps are “controlling very valuable things for the user, but they’re not thinking about security mechanisms.”

North of the border, meanwhile, the Canada Revenue Agency (CRA) was forced to temporarily shutter its online services and mobile applications after a vulnerability was discovered in Apache Struts 2, an open-source software tool that is widely used by government and private sector agencies alike. While there’s no evidence of lost or stolen data, it’s a sobering reminder that even popular (and presumably well-tested) applications can put companies at risk.

The Speed of Security

As noted by Dark Reading, the recent CIA breaches, vulnerable industry apps and open-source issues make the case for app security as “pre-industrial,” since it lacks the ability to handle attacks at scale, focuses mainly on vertical threats, and includes a “vast landscape of tools and point solutions.” Plus, without effective standardization and specification, these tools are ad hoc at best and may not successfully address the accelerating speed of security threats.

Top Tactics

The first step in shifting app security from critical failure to cutting edge? Identifying key threat vectors. For example, both DoS and DDoS attacks are on the rise, with 53 percent of security pros saying these threats are among their top concerns. In addition, 60 percent of apps are vulnerable to SQL injection, allowing hackers to gain access and take control. More than 50 percent of web applications still allow cross-site scripting (XSS) attacks. Companies aren’t doing themselves any favors when it comes to design and testing, with stock permissions and APIs opening the app door to hackers even as timid testing of apps assumes that internal code offers superior protection.

Bottom line? Apps are vulnerable and software security isn’t keeping pace. Pushing app protection into the present demands a hard look at current targets and a better understanding of top application threats.

For more information on application security threats and how to handle them, review the accompanying slideshow from Column Information Security.

Author bio: Nori De Jesus is Global Director of Marketing at Column Information Security. De Jesus brings more than 20 years of experience as an advent marketer and business strategist working with software manufacturers and launching proprietary software solutions into the market. With expertise in BPM and case management B2B marketing, she focuses on innovation and making a difference by maintaining agility as the technology climate continues to shift. De Jesus is an evangelist in educating buyers through their technology-purchasing journey via content and research.

In this day and age of websites being hacked, personal information being stolen, and companies large and small being targeted by hackers around the world, you would think most developers would go through their systems to make sure they are following best practices when it comes to security.

I understand “security” is big and scary and has many layers. Let’s start with something easy: passwords.

Facepalm for bad password securityLast week, I signed up for a service. I’m not going to put them on blast, but after I signed up, I received an email with my new account information, including my password.

My heart skipped a beat.

That’s very bad.

If you get an email from a website, large or small, and it contains your password, be very wary. In the vast majority of situations, they are not storing that password in a secure way.

When I pressed them, they said it wasn’t a huge deal because they weren’t storing credit card details in there.

The reality is this: it doesn’t matter what you are or aren’t storing in your database or application. If you have weak security in one place, you have weak security everywhere. I would hazard a guess that the password strength and security for the other servers on that network aren’t great either.

So why do companies launch web applications with terrible password security? Some of it may be lack of knowledge, but that excuse is harder and harder to believe in today’s world.

For some companies, that’s the way its always been done. For others, they store passwords in plain text to make life easier for customers who have lost theirs. They think it’s easier to give them their password as opposed to reset it.

Finally, there’s cost. If have to retrofit your web application to store passwords securely, there is time and effort and resources needed to do that. Company executives may not see the return on investment, which is unfortunate.

One of the most popular posts on this blog was on I did in 2008 about passwords. Specifically, you should never store a user’s password in your database as plain text. This means not saving in  your database or text file exactly what the user typed in.

When developers store passwords this way, and an unauthorized person gains access, that attacker needs to do no work to get all user data. This comes from MediaTemple, who was hacked in 2009 and it was discovered they were storing passwords in plain text.

“Clear Text” is a method of storing passwords in a database so that they are human readable. This preference was made to provide customers a convenient way of managing access to their services, e.g. connecting a PHP app to MySQL. The “clear text” method can be less-secure than methods involving “encryption”, where passwords are not human-readable. This is less convenient for customers, but adds a layer of security. Properly secured databases can store passwords using either method, with the information kept private. However, if a database gets compromised, the encryption method is the only way to keep the information secure.

If you want to securely store your passwords, use a decent hashing algorithm, use a salt, or use a strong password library such as Bcrypt. Don’t store them as plain text. It isn’t hard, and it will help secure the information your users have trusted you with.

I think it’s fair for users to think that sites they give their personal information to will keep that information secure.

Yahoo LogoYesterday, Yahoo announced that back in 2013, approximately 1 billion accounts were hacked, and information about those accounts, including names, hashed passwords, dates of birth, and more were taken. This is on top of the 500 million accounts that they announced last September had been hacked.

First off, Yahoo was using MD5 for hashing passwords. MD5 was shown years ago to be crytographically insecure. I know engineers at Yahoo are pretty smart, but this is pretty dumb.

Second, how do you let 1.5 billion accounts get compromised? Why does Yahoo not take security seriously? In an email to affected accounts, Yahoo said this about what happened:

Law enforcement provided Yahoo in November 2016 with data files that a third party claimed was Yahoo user data. We analyzed this data with the assistance of outside forensic experts and found that it appears to be Yahoo user data. Based on further analysis of this data by the forensic experts, we believe an unauthorized third party, in August 2013, stole data associated with a broader set of user accounts, including yours. We have not been able to identify the intrusion associated with this theft. We believe this incident is likely distinct from the incident we disclosed on September 22, 2016.

Here’s what’s worrying about the announcement. They can’t seem to find out how it happened. They posted this on a Tumblr (?!) site:

We have not been able to identify the intrusion associated with this theft.

Wow. Seriously? 10,000 employees and you can’t figure out how your systems got hacked, again?

If you have been affected by this or a previous breach at Yahoo, here is my professional advice:

STOP USING YAHOO!

If you are using Yahoo for your main personal email, stop immediately. Use Gmail. Yahoo has shown it does not take security and the safety of your data seriously, so don’t use them. Even if we don’t take into account that Yahoo was scanning emails for content and giving it to US intelligence agencies, it’s not safe.

Change all your Yahoo passwords immediately. Email, Flickr, Fantasy Football, all of it. Now. Stop reading this.

I have a spare email address there I use for signing up for dubious looking sites and other mailing lists, fantasy football, and some other things and I’m changing my password there just the same.

R.I.P. our data.