Archive for the ‘ Information Security ’ Category

Usable Security

There has been a big push over the last few years to develop what has been coined as “usable security”. Things like drawing patterns on Android devices instead of typing in a 4 digit pin or identifying particular things in an image instead of typing a password have been developed. The biggest problem with these usable security mechanisms is that they often take longer to use than the alternatives.

Imagine if you had to take your mouse and click at 10 particular spots in an image every time you wanted to unlock your screen at work. Doing this would take several more seconds at every sign on and would add up quickly. Often for systems that are used often keying in a password is still the fastest method.

Well Microsoft has developed a new solution. Instead of having password requirements that are visible to the user, like minimum length, they want to let users use anything as a password. Even simple passwords like “love” would be accepted. However there is a catch, only a small number of users will be allowed to use a particular password.

Complex password requirements were introduced to combat spraying and braying attacks. A spray and bray attack is when an attacker tries to use one particular password on a large number of accounts. This way bypassing lock out procedures. This solution by Microsoft will fix this by only allowing a small number of accounts to be compromised and thus reduce the benefits of the spray and pray attack while keeping passwords simple and easy to remember.

Examining Security Of Open Source and Closed Source

I recently just completed a research paper, with two of my colleagues: Clint Caywood and Matt Strayhall, on the security of Open Source Software. The paper went very in depth and I feel helped fill a void of the lack of credible information in this hotly debated topic. Here is the abstract:

In this paper, we examine the security of open source software versus that of closed source software. Facets examined include a brief history of the growing need for security in software, a comparison of the different philosophies driving the development of security in open and closed source software, arguments for obscurity in closed source versus the “many eyeballs” theory in open source, and the pros and cons involved with both development processes. We also look at the two approaches in practice, focusing on competing software like Linux and Windows, OpenOffice.org and Microsoft Office, and Apache and Windows IIS Server. Finally, we examine the impacts on society from software security, as well as who is responsible for maintaining secure software.

You can find more, including download links, if you visit my Research section of this website.

Risks of Modern Life

According to Confused using social websites such as Twitter or Facebook can increase your risk of being robbed. It is even being said that using Facebook or Twitter may soon increase your home owners insurance. At first glance this seems pretty scary and is something that most people likely never considered.

Robbers want to rob a house when they will have the greatest chance of not getting caught. That means they do not want anyone to be home. These articles point out that when you post your ware abouts online, you are informing robbers. They could use the information that you are not home to go to your house and rob it. The first assumption is that your address is freely available. After doing a quick check of my computer illiterate friends on Facebook, I didn’t find any with that information available. However, the robber could use your name and a phone book to look you up.

The other problem is robbers already have tons of ways to find people that are not home. Simply picking up a phone book and calling numbers in order and going to the houses that do not pick up. In fact the robber could get lucky and they home owner would have put a message on their voice mail saying they will be out of town. Robbers also know that nearly everyone works during the day. So they can simply go up to a house during the day and knock to see if someone answers the door.

If we look at someone who can guarantee is not home during a certain time, such as a news anchor who is live on air at a certain time each day. We do not see an increase in the likelihood of robber for news anchors versus the average person.

I’m not saying its perfectly fine to post your ware abouts online. I just want to point out that it is very doubtful it increases your likelihood of being robbed. I hope the smart people at the insurance companies actually look at some data and not just jump on the chance to charge more money.

Consider both sides

I was recently watching some research project proposals at my university. One of the proposals caught my eye, it was a way to stop common cheating techniques for page rank. At first glance the proposal has some good merit, the system would stop the current techniques used. However the problem was that they did not take into account what new problems they would introduce.  The actual proposal is still private so I can not talk to much about the details.

It is very common to come up with solutions that fix very common bugs. What is equally as common is creating new bugs that are as bad as ones that were corrected. When fixing security vulnerabilities the fixer must consider both what is fixed and what bugs the fix will introduce.

A Lapse in Policy

We have all be on the phone talking to someone that we may not know all to well, when at the end of the conversation they say “sounds good, go ahead and shoot me an email about this.”. If you are like me you think, “why we just talked about it”. However that email actually is used for quite a few things: The most obvious one is that it will be used as a reminder, people often use there inbox as a to-do list. The next thing that email will be used for is a record of your request, most companies have very strict policies on change management where all changes must have a request associated with it. The final thing that email will be used for is authentication, with the raise of knowledge about social engineering over the phone email as authentication has come into play.

The lapse in policy comes from the last two things the email serves. It comes from the assumption that only the person who controls the email account can send an email from that email address.  Unfortunately email, like most Internet protocols was invented before security was taken into account. Its actually considered quite trivial to send an email appearing to come form any name and email address that you please.

Fortunately there is a simple fix to this problem: Simply reply to all request emails with a confirmation request. So if person A requests person B to preform some task on the companies file server. Before preforming the task, person B should send a confirmation email to A asking for A to confirm the task.  Then the request and the confirmation should be stored for record keeping and we can be sure to the point of the security of the email account that the request was authentic.

Paying the Ultimate Cost

In America and most of the western world when we hear the phrase “paying the ultimate cost” we think of dying for a cause. Basically it means we value ones life as the highest cost we can sacrifice. In security the only way to protect something is to make the cost so high that attacking it is simply not worth it to the attacker. So in the west and especially America we use the threat of taking away someone’s life as the cost for committing very serious crimes. Some would debate how well this works, but I am of the personal belief that it works pretty well.

People often argue that defending against a suicide attacker is impossible for the reason that the attacker doesn’t value their own life. The problem with this argument is in the assumption that to the attacker the ultimate cost is the attackers life. I would argue that there most be something that is to valuable to the attacker that will make them feel the attack is not worth it. An example suggestion would be the attackers family. If the 911 hijackers thought America would hunt down their family and killed them I would suspect they wouldn’t have done it.

Now this sounds horrific, that’s because it is. We in America and other Christian based moral codes would never hold the fault of a family member against the entire family. I would also never suggest that as a solution or support it. The point to the argument is that in trying to mitigate a risk you most consider the potential cost to the attacker. The higher you can make it the better. Unfortunately when you deal with people that have a different moral framework, like terrorist,  costs are measured differently. When attempting to develop mitigating controls to defeat terrorism we have to be creative in finding costs to the attacker that are ok in our own moral framework but are still costly enough to make the attacker not attack.

Insights in Risk Assessments

Bruce Schneier has a great insight on risk. In a recent post to his blog he wrote:

People have a natural intuition about risk, and in many ways it’s very good. It fails at times due to a variety of cognitive biases, but for normal risks that people regularly encounter, it works surprisingly well: often better than we give it credit for.

This struck me as I listened to yet another conference presenter complaining about security awareness training. He was talking about the difficulty of getting employees at his company to actually follow his security policies: encrypting data on memory sticks, not sharing passwords, not logging in from untrusted wireless networks. “We have to make people understand the risks,” he said.

It seems to me that his co-workers understand the risks better than he does. They know what the real risks are at work, and that they all revolve around not getting the job done. Those risks are real and tangible, and employees feel them all the time. The risks of not following security procedures are much less real. Maybe the employee will get caught, but probably not. And even if he does get caught, the penalties aren’t serious.

Bruce hits risk assessments right on the head in this post. The risk inherent in what is considered risky Internet  behaviour is not as bad as many make it out to be. People often surf the web in untrustworthy wireless networks and store data on none encrypted memory sticks and nothing bad ever seems to happen because of it. At least on the personal level. We may read news articles once a week that describe how some sensitive data was lost on a stolen laptop or some other similar story. The thing to take from them is that they are in the news, if it happened to everyone it wouldn’t be news worthy. Bruce goes on to say:

“Fire someone who breaks security procedure, quickly and publicly,” I suggested to the presenter. “That’ll increase security awareness faster than any of your posters or lectures or newsletters.” If the risks are real, people will get it.

This is exactly correct. People need a real risk to be aware of the riskiness of their behaviour. However the network administrators need to take into account the actual risk, likelihood, and cost of each policy. You can’t stop business in the name of security.