Showing posts with label Security. Show all posts
Showing posts with label Security. Show all posts

Wednesday, December 14, 2022

Security and NFC/RFID

An interesting post today from Bruce Schneier points to an article about hacking the MBTA CharlieCard (Boston's public transit system). I couldn't help but think back to Cory Doctorow's book Little Brother that came out in 2008. I reviewed it back in early 2009.

One of the major plot points includes the protagonists rebelling against an overreaching government by messing around with transit cards by reading and reprogramming them by simply bumping the reader against them in people's pockets. Apparently something more or less the same has been occurring since then up in Boston, made easier and easier with commercially available scanning equipment.

In the book, they were reprogramming cards to make it harder for the government to use people's travel pattern data against them. In real life, people are just getting free rides.

Tuesday, October 31, 2017

Genisys

This type of thing happens all too often. You're talking about something random, let's say your favorite pieces from a bag of Chex Mix. You don't type anything into a search engine about it. You're not using your desktop computer or mobile phone at the time. You haven't purchased any from the store or Amazon or looked up any Chex Mix recipes recently. You just briefly talk about it for a minute and then the conversation changes.

The next day, you open up Facebook, and the following ad appears:


That is an actual screenshot I took when this happened to me. The strangest thing about this is that I don't have the Facebook app on my phone. I access it through my web browser, which means Facebook can't be constantly listening in to me. My wife and daughter do have the Facebook app. So if it was listening on one of their phones, it made the connection to show the ad to me.

Genisys in the title above is a reference to Terminator Genisys, which I just watched so is fresh on my mind. It is interesting how the time travelers are blown away by everyone's obsession with their mobile devices. And [spoiler alert] the artificial intelligence network which was a missile defense system in the initial movies ended up being a social media cloud system in this movie reboot. It was honestly more of a MacGuffin than an important plot point, other maybe when the security guard was looking at his phone instead of the surveillance cameras. Of course 2 or 3 decades ago people were concerned with Soviet missiles, while now social media is the big thing.

Is it a big leap from your phone showing you ads for Chex Mix to robots controlled by social media and destroying mankind? Maybe. But next time you're out in public, look around at who's being controlled by their phones.

Wednesday, May 7, 2014

War on General-Purpose Computing

We hear a lot about security. We hear much about copyright. Not often do we think or hear about the connections between the two. Copyright- and internet-reform activist and science fiction author Cory Doctorow discusses just how these two come together in what he calls the War on General-Purpose Computing. The idea is that general purpose computers, such as your laptop or the servers locked away in the company data center, are designed to do exactly what we tell them. Because they can do anything, it's important that their owners/users know what is running on them. Rogue processes need to be found and removed to keep legitimate programs and data secure.

Being able to control everything on the computer means if it's displaying copyrighted content, you can (technologically, if not legally) make and distribute copies of that content. Content publishers claim this causes them to lose money, so they push for laws and technology that don't allow users to control everything on their previously general-purpose computer. Since owners/users can't even tell everything that is running, let alone actually control everything their computer is doing, security gives way as someone else is controlling their computer. Someone else is controlling your computer.

Friday, May 31, 2013

Password Security and the Minimum Password Age

Everyone has their favorite (or least favorite) password rule.  Just google password rules, and you'll find all kinds of things we inflict on our users.  Some sites require the use of special characters, while others prohibit them.  Upper, lower, numbers, symbols, length, change every 30/60/90 days, can't use the previous 3/5/10 passwords, no dictionary words, and so on.

There are a couple webcomics on xckd that address the issues of password strength and password reuse.  Go read them; they're great.  And then read a couple dozen randomly selected comics on the site, and if you remember to come back, the rest of the post with my point will be here waiting.

One of the most interesting to me is that of minimum password age.  We're all familiar with the maximum age - it's been 90 days, time to change it or you'll be locked out.  Whether it's effective to change a good password at all is debatable, but not the conversation for today.  The thing about not reusing a previous password is fairly common.  But why would you want to set a minimum password age?  That is, a certain amount of time needs to pass before you're allowed to change it again.

Let's go to an example.  There's a system I use that requires me to change passwords every 6 months.  Fair enough.  You can't reuse any of your last three passwords.  Okay.  The idea, then, is that you use one password for 6 months, a second for 6 months, a third for six months, and a fourth for six months, so two years later (or 18 months, depending on how you do math) you can switch back to your original password.  If someone had stolen that original password, they'd have to wait a long time to use it, assuming you ever switched back to it.  If it's been a couple years, maybe you're 'over' that password.

But what if it's been six months, and you're not over your first password?  So you change it, because you're forced to.  Only you change it three or four times to random whatever passwords that you don't even keep in your short term memory longer than to immediately change it.  You cycle through your throwaway passwords until the queue of previously used passwords is cleared, at which time you can set it back to your original password.

Stop and think about that for a second.  Without a minimum password age, which requires you to wait an hour, a day, two weeks, a month, or whatever you set it to, you can quickly cycle through 3, 5, or even 10 passwords to clear your preferred password from the queue in a matter of minutes.

Requiring a minimum password age of 1 month, with 5 previous passwords saved, means the quickest you could get back to your old standby would be 5 months.  If you've gone 5 months, chances are by then  you're over the old password.  Someone would have to have a pretty sustained interest in getting their old password back quickly to wait that long.

So if you're in the camp that a good password is a good password and need not be changed unless something has happened, and there's no minimum password age, you can rotate quickly through enough passwords to clear the list and go back to your original one.  On the other hand, if you're managing the system and setting password policies, if you decide you want users to have to change their password (and that's a big IF for another day), only let them change it once every so often with a minimum password age.

Wednesday, August 24, 2011

Bubble Guppy Analytics

I haven't watched much Nickelodeon since the days of Double Dare and You Can't Do That On Television. I'm slightly intrigued by a cartoon that is in its first season on the well know kids' channel. I actually don't know anything about the show, but Google somehow thinks, or at least one day thought, that my blog is somehow related to Bubble Guppies.

I was just looking around in my analytics and found that a couple weeks ago, someone from Ontario visited my site after googling Bubble Guppies. They were sent to my main blog page, not to a specific post. I have no idea what could have been the draw, other than perhaps a recent post that mentioned swimming in a couple triathlons. I wouldn't think that the mere mention of swimming would be enough to pull in a search for information about preschool-aged cartoon mer-people.

By writing about it now, I am, of course, taking the risk of forever linking my blog to the cartoon like I did with the website Surf the Channel in a post a few years ago that still gets me hundreds of hits every month for no good reason. So to the potentially hundreds of you that may visit in the future, if you actually read all three paragraphs of this post, leave me a comment and let me know what you were looking for when you found this and perhaps an interesting fact about yourself. Don't be afraid that you'll be revealing too much, as I already know quite a bit about you just by your visiting (for example, my unknown visitor from Ontario was using Google Chrome on a 22 inch widescreen monitor over Rogers Cable). And yes, every other website on the internet knows at least that much, if not more, about you when you visit them, especially if they integrate Facebook plugins to their site.

Sunday, June 20, 2010

Energy Independency

We are an unstoppable oil dependency breaking machine. Unfortunately the machine runs on oil.



Thank you Jon Stewart.

Wednesday, September 30, 2009

Free Software

I followed an interesting discussion this past week. It started as a discussion of some security vulnerabilities that were released by a security researcher. "Abe" got all worked up, saying that this researcher should be prosecuted for releasing the details of the security hole so anyone would be able to take advantage of it.

The importance of openness in security was brought up, specifically how big software companies will generally try to hide vulnerabilities to protect the illusion of security, as opposed to the way open source projects just acknowledge and fix the security holes.

The conversation somehow turned into Abe accusing someone else of participating in an underground economy and personally benefiting from using free software at the expense of taxpayers, who are paying his salary (which is so false it doesn't even merit a reply). He continued on pointing out that free software isn't actually free, since there are all kinds of costs associated with it.

Of course there are costs associated with any software. The "free" doesn't mean that there are no acquisition costs but that once you have acquired it, you are free to do with it what you want. Proprietary software generally costs up front to purchase it, and then you are at the mercy of the software developers to make changes to the software if that is desired or needed. If you need a new feature and they don't want to implement it, you'll never get it. With free software, you may or may not pay up front to purchase it, but you are of course likely to invest in training, hardware, and other costs to actually implement it. The nice thing is that once you've implemented it, if you need a new feature, you can just add it or pay someone else to add it. If the original developer won't do it for you, it doesn't matter. You're free to change it if you want as long as you're willing to share your changes with others.

It was pretty obvious to everyone else that Abe didn't know what he was talking about, since he kept referring to money instead of freedom, so someone finally called him a troll. It didn't end there as he made a joke about trolls that showed he didn't know what a troll was. Someone else referred him to Wikipedia's article on trolls, after which Abe backed off and claimed he was just acting as devil's advocate and pointed out that the debate could just go back and forth all day so wasn't worth continuing.

I'm pretty sure he didn't understand all the arguments against his position or else he was the dumbest devil's advocate ever. Either way, he realized he was outmanned. The biggest piece that he was missing was not whether there are costs associated with implementing free software but that there are very real costs associated with not being permitted to maintain proprietary software yourself after implementing it. Can you really afford the lack of control over whatever platform you deploy if you use something other than free software?

Thursday, March 5, 2009

Little Brother

Introduction

Cory Doctorow is a science fiction author and activist. His book Little Brother stands in both the science fiction and activism camps. He builds an argument for everyone to learn more about the technology that is pervasive in our lives, with a story of daring teenagers taking on the government. The book's byline, "Big Brother is watching you. Who's watching back?", hints at this showdown between technophiles and bureaucrats. San Francisco is turned into a police state after the Bay Bridge is blown up by terrorists. A group of teenagers fight back against abusive behavior by agents of the government, using their tech-smarts to expose injustices and force the government to reign in an overzealous Department of Homeland Security. Although at first glance the storyline appears over the top, neither the injustices being done nor the technologies used to expose them are very far off from what is happening today. Political ideologies aside, what saves the lives of these kids and many others is education and openness.

Background

The most obvious work that this book may be compared to is George Orwell's 1984. In that book, Big Brother is the iconic face of The Party (or government), and Winston Smith is the protagonist who rebels and is eventually brought into submission by The Party. At the beginning of Little Brother, the protagonist Marcus goes by the handle w1n5t0n, pronounced Winston. The term Little Brother is used by the media in the book to describe the members of the Abuses of Authority movement, "who watch back against the Department of Homeland Security's anti-terrorism measures, documenting the failures and excesses." There are several similarities in the storylines, with characters devising methods to avoid surveillance, dealing with issues of who to trust, and government-sponsored torture. The most notable deviation from the 1984 script, other than Marcus being a nonconforming teenager rather than an experienced government employee like Winston, is that Little Brother has a relatively positive ending. Although the strings are not tied up as neatly as a Perry Mason episode, it's not at all a stretch to say that Marcus and friends "win" in the end.

Another book that provides a more scholarly approach to a similar topic is Larry Lessig's Code: Version 2.0. Both books point out that technology may be manipulated to whatever end we desire. The only way to ensure biases or bugs are eliminated is through transparency, since trust is often lacking. An important concept in Lessig’s book is that of latent ambiguities, which come about since technology moves faster than the law. A current example of this is the complaint from the Author’s Guild that Amazon’s e-book reader Kindle would be able to read books aloud without…gasp…purchasing audio rights. [Doctorow's response to the Kindle controversy]

Little Brother is aimed at young adults. It seeks to lure in these digital natives with fast-paced action, distrust of adults, cool technology, and a sprinkling of sexuality. It is important that this next generation make the leap from being consumers of technology to producers, so there will be new creators of technology to take the place of the baby boomers as they begin to retire.

In the foreword of the book, Doctorow states the following: "This book is meant to be something you do, not just something you read. The technology in this book is either real or nearly real. You can build a lot of it. You can share it and remix it. You can use the ideas to spark important discussions with your friends and family. You can use those ideas to defeat censorship and get onto the free Internet, even if your government, employer or school doesn't want you to."

In the afterword, Bruce Schneier, a well known security technologist, and Andrew Huang, a researcher known for hacking the Xbox, point out the amount of dysfunction in the world today. Security through obscurity seems to be the pervasive method in the world for keeping us safe; however, openness and courage to stand up for our freedoms is what will make us safer. Schneier admonishes us to pay attention to the world and try to figure out how it works, and by doing so we will begin to worry about the things that will actually make us safer and stop relying on technologies that can be defeated with a little bit of knowledge and a ballpoint pen.

Summary

The book follows the exploits of a seventeen year old high school student, Marcus Yallow, who uses technology to his advantage work his way around the technical measures instituted by his school district to keep the students in line. The school is truly a place that Paolo Freire would speak out against, as students are monitored and disciplined for speaking their minds; they are oppressed, rather than being allowed to participate in the learning process.

In rebelling against the oppression, these students learn about and utilize technology to encrypt chat sessions, block RFID tracking, and confuse gait-recognition cameras in the halls. As they are out skipping school, a terrorist attack occurs, and Marcus and his friends are picked up by the Department of Homeland Security (DHS) as possible suspects in the attack. After being held and questioned for several days and then released, they return to a city which has been locked down by the DHS. Innocent people are being stopped and questioned by police to ask why they visited certain parts of the city, since they are tracked by their RFID cards that are used for payment on bridges, toll roads, and mass transportation.

Marcus organizes an underground movement utilizing a special Linux distribution called ParanoidLinux that could run on Xboxes that had been handed out for free by Microsoft the previous year. They teach other youth around the city to reprogram RFID cards to throw off the DHS's data mining techniques. The movement gains momentum, but eventually it becomes obvious that the DHS has infiltrated the so-called Xnet. A small group of Xnet members use encryption technology to create a trusted group within the Xnet. The more this trusted group organizes and tries to rebel, the more they realize that the DHS is closer to figuring out who they are. Their only choice is to go public with the abuses being handed out by the DHS, as they bring in more agents and apply more pressure to finding these supposed terrorists.

In a conversation with his father, who did not know Marcus was the leader of this group rebelling against the DHS's tactics, his dad points out that, "The Bill of Rights was written before data-mining. The right to freedom of association is fine, but why shouldn't the cops be allowed to mine your social network to figure out if you're hanging out with gangbangers and terrorists?" Marcus' response was, "Taking away our privacy isn't catching terrorists: it's just inconveniencing normal people." His father seems willing to accept the inconveniences of being stopped without cause while looking for the bad guys, while Marcus is actively fighting for rights guaranteed us in the Constitution. In the process they address some of the latent ambiguities that Lessig discusses in Code: Version 2.0.

The publisher provides a free Teacher's Guide which contains writing activities for students with thought-provoking questions to help students enhance their analysis of the book. This is a nice addition for classroom use, covering issues such as understanding truth and reality, history, research techniques, code transparency, privacy and surveillance, righteous rebellion, torture, legal and civil rights, marketing techniques, protests, trust, and problem solving. There is really something in this book for everyone. With the book’s Creative Commons license, a teacher can download and distribute the book for free to students. If the sex or some of the language is a little too risqué, it can be legally modified.

Evaluation

Very little can hold the short attention span of the upcoming generation, but this novel has what it takes to keep them motivated to turn the page while learning a little bit about technology. The action and exciting technology are enough to keep the reader hooked, even as Doctorow explains the basics of cryptography, networking, IP tunneling, and RFID. It is enjoyable to learn more about the technologies, even though most people would not admit to being interested in such things. He directly ties technology into the story and how these teens are using the technology to fight back. Schneier states, "Cory invited me into the last few pages of his book because he wanted me to tell you that security is fun. It's incredibly fun. It's cat and mouse, who can outsmart whom, hunter versus hunted fun. I think it's the most fun job you can possibly have. If you thought it was fun to read about Marcus outsmarting the gait-recognition cameras with rocks in his shoes, think of how much more fun it would be if you were the first person in the world to think of that." Doctorow did a good job of showing how fun and interesting a more advanced understanding of technology can and should be. With the afterwords by Schneier and Huang, he ties back to his statements at the beginning of the book to explicitly remind the readers why he wrote it.

Unlike movies like Independence Day, Jurassic Park, and The Net, where technology is incorrectly utilized in unrealistic ways, the technologies in Little Brother either already exist or would be relatively easy to implement. The ParanoidLinux distribution mentioned in the book did not exist at the time the book was written, but interested Open Source programmers have begun putting together an operating system that mirrors the capabilities mentioned in the book. Much of the software used already exists, but the ParanoidLinux distribution is simply bringing them all together in one package. The use of real technology is very important, as it removes some of the need for suspension of disbelief, making it easier to get lost in the story.

A more in depth look at the characters in the story, however, reveals a superficial, one-dimensional nature to most of the players. There was just a lack of complexity that was somewhat distracting. The evil characters are pure evil. His friends and family are either 100% supportive of him or want absolutely nothing to do with his plans. We do get inside Marcus' head as the majority of the book is written in first person, from his point of view. We see Marcus' inner struggle and growth as the reluctant leader in the rebellion he spawned on a whim, but see little character development in those around him. Marcus does have fights with one of his friends and his girlfriend, but they seem to be more devices in furthering Marcus' growth rather than their own. I kept waiting for the twist, like his girlfriend being a spy or his dad working to help the DHS improve its data mining techniques as they close in on Marcus. That twist never came. Even the supposedly surprise DHS informant was not out of line with previous interactions with that character.

Conclusion

As technology departments at universities around the country struggle to attract females into their programs, Little Brother can be used as a recruiting tool. There are just as many tech-savvy, important females in the story as there are males. Computer Science suffers from a lack of understanding among both males and females as to what you can do with a degree in that field besides sitting in a dark basement writing line after line of code. Being able to program is an important part of the story, but so is understanding and using technology that has been created by others in unique ways.

I hesitate using the term "must-read", but Little Brother is high up on my recommendation list. It is not often that a book with a decidedly technology-rich storyline can reach out to both readers that are tech-savvy and less knowledgeable in a way that makes them want to learn more. Doctorow makes it easy for his readers by telling them what he wants them to do when they finish the book, presenting a compelling story, concluding with another call to action, and providing a list of more sources to turn to with their new-found interest in security, technology, and counterculture books and electronic resources.

Friday, December 19, 2008

SteadyState

Many people I've talked to lately have either had some kind of spyware infestation, the notoriously scamacious Antivirus 2009 (or 2008), or just something that the kids did weird that messed up their computer.

In looking around for something to help keep computers under control, I found Windows SteadyState, which is a free program put out by Microsoft for locking down Microsoft Windows. As much as I dislike some of Microsoft's business practices and their frequent security problems (stop laughing Mac fans - the Mac OS has been bitten by malware as much as Windows has lately), this is a program that appears to have what it takes to really lock down a computer. It won't help in cleaning one up after the fact but in keeping it from getting messed up in the first place.

I used it to create an account for the kids. The account is locked down so no programs can run except Internet Explorer. Then IE is locked down so it is more limited than normal. You can set it up with a whitelist or only specific sites that can be visited, but I didn't turn that feature on.

If something strange does get installed even with the limited version of IE that is running, when you log out of the account, all changes made to the computer are automatically removed. Pretty cool. You can unlock the account so you can make changes and then just lock it back up.

I'm still playing with it, so I don't have a full review for it yet, but I recommend trying it out.

If you don't want to totally lock down your computer to just a small list of websites but still want good protection, I recommend K9 Web Protection from Blue Coat Systems. It's free for personal use. It lets you pick from a huge list of categories of sites that you can block and logs all sites that are visited.

And if you do happen to get the Antivirus 2009 trojan installed on your computer, I've found System Restore, which is automatically enabled in both Windows XP and Vista, to be the easiest option to remove it.

Friday, October 3, 2008

Possible research project

In looking around for possible research topics for journal articles and presentations or for my dissertation, computer security has kind of caught my eye recently. On a weekly campus vulnerability scan recently, the list of problem computers included about 25 unpatched Macs and a few other random boxes with vulnerable versions of software running or easy to guess passwords. Subsequent network scans have found several hundred more vulnerable Macs. It's nice to see them harassed by the security team occasionally so they don't get sloppy.

One interesting machine that showed up in the to-be-killed list was the server where they post information on the computers that get locked out of the network for security problems. Ironic.

One other machine caught my eye was a student's personal computer that had blank passwords for the Admin and Owner users; critical Windows updates not installed; vulnerable versions of Quicktime, RealPlayer, Flash, iTunes, and Mcafee; and the hard drive publicly shared to be readable and writeable. Ouch. That's almost as bad as the MIS professor who set up a new server just before the Christmas break a few years ago, and came back the next semester to find it had been taken over to serve up pr0n and warez.

Since information on who a computer is registered to is easily available, I got curious and looked up the student's CIL test scores. The student has not taken the Computer Systems CIL test yet, which is the one that talks about the need to keep your OS and applications patched so your computer is protected. I wonder how many students that are contacted by the campus security team have taken that test or prepared for it in any way.

In a completely nonscientific, ad hoc, non-IRB-approved, 5 minute study, I grabbed the IDs of 3 or 4 other students threatened with being disconnected from the network, and none of them had passed the Computer Systems test either. It makes me wonder.

Wednesday, March 19, 2008

New Way to Cheat

We had another person this week open up a website in full view of our test proctors to look up the answer to a question on the web-based test they were taking. Really? You're taking a test. Of all the ingenious ways one could think of to cheat, that's what you come up with? Of course, the really novel ways to cheat on our tests probably take more energy and time to pull off than just taking the tests, so it's not worth it.

An interesting company, Microvision, looks to have some cool laser-based projection technology that may make it easier to cheat in certain situations. Of course, there are many appropriate applications of their technology, but as with anything, there will be inappropriate uses as well.

A pair of glasses that can show video to the wearer could be used for many things, per their website, such as giving a speech, reading email, watching movies, viewing schematics while performing repairs, and more. Hook it up with a GPS and you can see a friend or acquaintance coming from several blocks away or follow directions to a restaurant. Or cheat during a test.

Of course, the cool products they have displayed on their website are much more interesting to me than facilitating bad behavior. The PDA-sized projector is pretty cool. The Heads Up Display (HUD) for cars will surely be common soon, so you can follow directions reflected off your windshield instead of having to look down to the nav screen mounted in the dash.

Hopefully professors and other teachers will embrace new technology and encourage students to use it for good purposes rather than be scared of it and ban it or (even worse) ignore it. Those who teach will have to adapt and choose different assessment methods that are not quite so prone to cheating as multiple choice tests. On second thought, that would require change - we'd better start thinking of something else.

Tuesday, March 18, 2008

Awareness

I don't Stumble that much, but I found this video recently doing so.

It's an amazing awareness test, as part of an ad campaign sponsored by the mayor of London. You can watch it without sound, but it's a little better with sound.

How many did you see? 12, 13, 14? You simply have to watch the video again after you've seen it once.

There's so many possible applications of this video. Of course, their message at the end is a great one, but you could apply it to other situations as well.

I met recently with my employees and we talked about some of the distractions that they face while working, such as computer games, texting, and IM. I hesitate fully banning any kind of diversion for days or times when it is slow, but when there are piles of things to do and people to help, I don't understand at all that they don't see all this stuff they should be doing. How do I make them be aware if they don't want to be?

Wednesday, February 27, 2008

I Am Supernode

I've been using Skype a little bit lately. The main reason is that a programmer who works for me just moved to Venezuela, so we use it to video conference him into our weekly meetings, as well as for text chatting and occasional voice calls. Overall it works pretty well.

I have been using the campus Jabber server to chat with the consultants in our testing lab but hadn't really been using anything to chat with the programmers. Since we all installed Skype, we've been chatting through that, so I actually talk to them more than I had been, even though it only takes about 7 seconds to walk out my door into their office.

So I got an email from one of the campus security team saying that my computer was serving as a supernode for about 400,000 Skype clients. Basically, Skype uses a peer to peer network for handling traffic, and since I had a fast enough computer with a high speed internet connection that was always on and logged into Skype, I got volunteered to route calls through my machine for people. Yikes.

One site that talked about how to keep from getting wrestled into being a Skype supernode was much less technologically advanced than I hoped it would be. Their suggestion? Block Skype with your firewall and only run the program when you are planning to make or receive a call. That's not ideal, but I suppose it will work, except I now have to pick a different communication method to determine when we need to load up Skype so we can communicate. Google Talk may work, since you can make voice calls through it; it doesn't do video, but none of us are really that exciting to look at anyway.

So, the lesson for today is be careful with Skype.

Tuesday, January 1, 2008

Investing in Security

A recent article discussed several myths and realities related to investments in information security. IS investments are very complicated, since companies must provide the "confidentiality, integrity, and availability of information, while also assuring authenticity and non repudiation…." That is to say, data needs to be protected against unknown change and kept away from non-authorized persons, while at the same time assuring that those who have legitimate business with that data are allowed full access.

Because of the complicated nature of many businesses, CxOs rightfully demand some monetary justification for pumping money into security rather than other projects that also need funding. According to the authors of this article, the traditional accounting measure, ROI, does not completely capture the benefits and risks associated with Information Security, so other measures must be used to find a project's Return on Security Investments (ROSI).

The first myth dispelled in the article is that "the accounting concept of 'return on investment' is an appropriate concept for evaluating information security investments." The problem with ROI is that it is an historical accounting measure. The IRR, an economic measure of future asset values and discounted cash flows, is a truer measure.

The second myth is that "Maximizing the IRR on information security investments is an appropriate objective." That is, the highest IRR is not necessarily the best choice. The amount of investment that yields the greatest net benefit is the one that should be used. The IRR measures a percentage return, not an actual return, so the IRR is used to a point, but to determine the actual amount to invest, the proportion with the largest actual return should be used. I'm not so sure that I agree with this point, but of course none of my articles have been published in Strategic Finance yet. What it looks like to me is that if another project has a higher marginal IRR, it will have a higher present value than the IS project, so the alternative project should receive the additional funding. This may be implied, but the article seems to focus on comparing a project's IRR only to itself, not to alternative projects.

The third myth is that "IRR and NPV are ex post metrics for evaluating the actual performance of information security investments." IRR is used to anticipate the returns of a project. Going back to measure the actual return on a project once it has been completed is called "post-auditing." Because of the nature of security investments, the more successful a project turns out to be, the fewer security problems will be seen, and the harder it will be to measure how successful it was. So the most successful project will result in no one even thinking about the security plan.

The fourth myth is that "it's appropriate to invest in security activities up to the level where the investments equal the expected loss from security breaches." The probability of an event taking place must be factored in when determining the present value of those investments. So, with this final point, the authors tell us that optimal level of security investments must be found, not just the project's rate of return.

In their research, they have found that on average, a maximum of about one-third of the expected potential loss should be invested in preventing that loss. By investing more than this, the amount spent preventing a loss approaches the amount of the loss. By investing less than this, a firm leaves its systems completely open.


Gordon, L.A. & Loeb, M.P. (2002). Return on information security investments: Myths vs realities. Strategic Finance, 84(5).

Cryptography

President Clinton passed the E-Sign Law in July of 2000 allowing a digital signature to complete a valid enforceable contract, but there is still little done by consumers using digital signatures. A few years ago, someone in my office came to me asking for my help in creating a digital signature. I did some research, found the costs and what technologies might be appropriate, and presented the options to my coworker. It turned out that all my coworker needed was for me to scan a signature from a piece of paper to insert into a Word document. I didn't explain that it wasn't really a digital signature I'd be creating; I just created it. Five-plus years later, I don't think that general consumer knowledge has risen much from where it was back then.

TCP/IP and the Internet in general was not designed to be secure. It was designed to not fail. In order to become secure, layers must be added at higher levels to protect data when it is being handed around the Internet. PGP (Pretty Good Privacy) and GPG (GNU Privacy Guard) are programs that use PKI for encrypting and signing data.

Public Key Infrastructure (PKI) is an application of cryptography. Technology is used to implement cryptography, but cryptography itself is inherently mathematic. Symmetric cryptography involves using one key to both lock and unlock or encode and decode a set of data. The sender and receiver must both have a copy of the same key. Asymmetric cryptography involves a public key and a private key. The public key is passed out to anyone, but the private key must be kept secret. With asymmetric cryptography, one key is used to encrypt or mark a set of data and the other key is used to decrypt or verify that the data sent has not changed. An asymmetric pair of keys can be used for either encryption or a digital signature or both. A symmetric key can only be used for encryption.

A regular, paper-based signature is used to prove to a third party that a transaction has taken place. Likewise, a digital signature is a mathematical operation to a set of data that proves that a message or transaction was enacted by the person who signed it and that it has not been changed.

A message goes through the following when it is encrypted: the message is written, a mathematical hashing operation is used to process the message, it is encrypted using a public key, the message is received and another hash is performed, and the message is decrypted using the receiver's private key.

A digital certificate, often used on websites and other transactions, contains the public key of a certain user or organization and identifying information such as email address, website, phone number, name, expiration date, etc. The digital certificate is signed by the organization or person who issued the certificate. Their certificate is in turn signed by the organization or person who issued their certificate, until a root is reached. Ultimately, it is that root that must be trusted. Each issuer must take the proper steps to verify the identity of an applicant before the digital certificate is issued.

Friday, December 14, 2007

Reset Vista

I have a new computer that's been sitting on my desk, waiting for me to have time to move everything over off my old computer. I only use it only occasionally, but have logged into it several times. So yesterday, as I was trying to transfer some music files over that I didn't want to store on the file server where I'd been putting everything from my old computer, I couldn't get my old computer to connect to the new one. I end up rebooting it, and when it comes back up, the password doesn't work. I don't know if I changed it or if a security update did something weird, but I was locked out. No other account to login with.

I found a nice Linux CD that boots you up to a registry editor that allows you to reset the passwords on accounts and enable or un-lockout accounts. The website itself was confusing to navigate, but once I found what I needed, it went pretty quick. I reset the password to something else a couple times. Nothing. I tried enabling the Administrator account and setting a password on that (since the Administrator account is disabled by default in Vista). No go.

So as I start looking through his FAQs, I find that setting the password is a bit flaky but just blanking the password should be pretty consistent. So I tried that and was in, and then within Windows I set the password to what it should have been all along. It won't let me change anything on the Administrator account, so I'll have to go disable that again, I guess.

When I was setting the password, I got this little hint from Vista: "If your password contains capital letters, they must be typed the same way every time you log on." Yes, thank you, but the question I have to ask is that if my password does not contain capital letters, does it not have to be typed the same way every time? If it's all lower case letters and numbers, do I not have to type my password the same way? I'm not sure I want to actually find out.