• About Me
    • Bios
  • Professional
    • Resumes
      • Data Security Resume
      • Full Consulting Resume
      • Skills List
    • Certifications
      • Certified Information Systems Security Professional (CISSP)
      • GIAC Certified Incident Handler (GCIH)
      • GIAC Security Leadership (GSLC-Gold)
      • Novell Certified Linux Professional (NCLP)
      • Red Hat Certified Engineer (RHCE)
    • Communities
      • A Ticket, A Task Kit
      • Infragard
      • Central Iowa Area Linux Users Group
      • SANS Community
    • HOWTOs
      • How To Configure Firefox – 2005 Version
      • How To Configure FreeBSD
      • How To Configure Mediawiki
      • How To Configure NetBSD – 2004
      • How To Configure Palm Treos
      • How To Migrate Red Hat 6.1 server to VMWare
  • Fun Stuff
    • Allergies
    • Book Reviews
    • Coyote Signs – The Inspiration
    • How to make s’mores
    • How to ship a tiger to Canada
    • Photography
    • Strained Geometries
  • Categories
    • Business Security
    • Coyote Signs
    • Mythology
    • Natural History
    • Psychology
    • Sprint
  • Contact
Menu

Real Life Lessons: Legal System

  • At February 07, 2008
  • By Josh More
  • In Business Security
  • 1

[flickr]photo:497353227(small)[/flickr]The fifth lesson was of the legal system. As you recall, I chose to not involve the police. If I had, I likely could have filed charges against the boy. (Not sure if it would have been breaking and entering, since he didn’t seem to break anything.) I chose to not do this. There were several reasons:

  • No harm, no foul.
  • It would have taken a lot of time to deal with the paperwork… and I had a full schedule.
  • I do not know how the law would have handled it, but to my own mind, I was just as negligent as he was.

In effect, I made a business decision that to involve the law would likely cost more (in time) than it was worth. Many people are faced with decisions like this, and most people have a different invisible line that must be crossed. I have known businesses that would call the police at the drop of a hat. I have also known business that would ignore successful network intrusions, considering them a “cost of business“.

In the event of a breach, most businesses consider it as follows:

  • dollar amount stolen + dollar amount of lost time in repair
  • dollar amount of successful prosecution times likelihood of successful prosecution – cost of successful prosecution – loss of trust in the market

It is often easier for a business to simply accept the loss than to risk greater losses by involving the legal system… but sometimes there is no choice. An increasing number of states have disclosure laws. If the breach involved any personal information (names, addresses, credit card numbers, social security numbers, etc), you may well be required to disclose the incident and accept any negative consequences that arise.

So, what is a business to do? First of all, you should have a lawyer that can help guide you through such a decision. Secondly, you should have a lawyer before a problem occurs – so that they are already familiar with your business. Third, you should know your data and know what possible ramifications might exist from storing it. Fourth, and optionally, you should have a security office or consultant who can look at your system and offer ways to limit risk and/or detect potential breaches. See, you’ll want to be the one telling your clients about the guy that broke in… not the newspapers.

Once you have these, your primary question should always be “Do I need to keep this data?“. If you are keeping information on users “just because“, and if that information would cost you if it got out… DELETE IT! It’s OK, if your users want you to have it, they’ll give it to you again.

My questions to you:

  1. What data do you store on your employees, customers, clients, and partners?
  2. If that information were stolen, how much could it damage you? (fines, lost clients, stolen clients, blackmail)
  3. How many years would it take you to recover?

Real Life Lessons: Social Engineering

  • At February 05, 2008
  • By Josh More
  • In Business Security
  • 0

[flickr]photo:36572011(small)[/flickr]The fourth lesson to learn from my incident is that of social engineering. Simply put, social engineering is using predictable social response to create a situation that benefits you. From a security perspective, this technique is often described as a tool used by the bad guys, but it can also be used by the good ones. In my case, once I became aware of the situation, I did the following things:

  1. I finished getting dressed. This puts me at a higher level than a person who is waking up disheveled. Though it was likely not consciously noticed, the distinction might have played in my favor. This helped to create the predictable response of a subordinate to a superior.
  2. I positioned myself between the light and his head. This way, when he awoke, he would be at a visual disadvantage. I would be able to see him clearly and, to him, I would appear in silhouette. The response I was trying to get here was to maximize his confusion while also maximizing the amount of information I could get when he awoke.
  3. I held a weapon on him, and I chose one which I could easily control and would likely create a feeling of fear but not create a feeling of terror. This way, I could anticipate a logical response (no terror), but a manipulated response (because he was scared).
  4. I awoke him with very specific instructions and questions. The socially acceptable response to these questions when one is in an inferior position is to simply answer the questions.

By arranging the environment and taking control of the situation, I was able to very quickly get the information that I needed to determine whether or not he was a threat (he was not) and make a decision (to let him go and not involve the police). Since I was in control, I was also able to get him out of the house as rapidly as possible, while minimizing the harm to either of us or anything that I had in the house.

From a business perspective, you face social engineering all the time. Most business relationships (whether between boss/employee or company/vendor) are hierarchical. Where hierarchies exist, there are ample opportunities for social engineering. This can be something as simple as a coworker asking you for something and stating that your boss had asked them. It could also be as complex as an attacker calling in and pretending to be an irate customer — leading you to believe that if you do not do as they ask, your company will lose the account and you will be at fault.

There are only a few ways to combat social engineering. The first is through constant and thorough training. This is time consuming and costly. It is, however, the best way to secure your business. That said, if you go this route, you must take care that the training plan is based on reasons and reasoning. All too often training programmes focus on the threats instead of on analysis and consideration. This makes your business utterly secure against yesterday’s attacks . . . and completely open to tomorrow’s.

The second way to protect against social engineering attacks is to eliminate the time pressure. You can do this by empowering your employees to solve problems in non-standard ways. If the “irate client/boss” refuses to accept rational non-standard solutions, there might be an attack going on. In such a situation, escalating the issue to someone with more experience just makes sense. You can also eliminate the time pressure by investing in highly redundant and flexible systems. This works well if you are devising a new solution… less well if you are supporting legacy technology. If you are handling legacy systems, the risks of inflexibility should be considered the next time you build a business case for overhaul and replacement.

The third way to protect against social engineering is to implement an identification system. If your front-line people can know, with certainty, that the person with whom they are talking is really who they claim to be, most concerns can be eliminated. There is, however, an element of client training to such a system. Any challenge-response system is accepted more easily when all parties are expecting it.

So, my questions to you are:

  1. What would you give an angry client or boss in order to make them happy?
  2. What if it wasn’t really them?

Real Life Lessons: Access Control

  • At January 31, 2008
  • By Josh More
  • In Business Security
  • 0

[flickr]photo:321434733(small)[/flickr]The third lesson to learn from my incident is the importance of access control. This model is often described in policy and procedure terms. We’ll use as an example, the different levels of people who I allow into my house.

From a policy perspective, I lay out the rules and roles of different people who are permitted to access my house:

  1. I always allow myself access to my house. In I.T. terms, I am my house’s administrator (or “root”) and have permission to go everywhere.
  2. I also allow my cats access to much of my house. However, as I have a higher level of clearance, there are certain rooms into which I may go (laundry room, exercise room), from which my cats are banned.
  3. At a lower level of clearance are my friends and family. While they can come over, I generally prefer that this occur only when I am present. While they are some rooms in which they are permitted without supervision (bathroom), others I need to be present (bedroom and office).
  4. Lastly, some people fall under the “service personnel” category (plumbers, electricians, etc). Their access is limited to a “need to know” basis, and I tend to be present at all times.
  5. All other people are not permitted in my house.

Once a policy is defined, the next step is to implement it. There are many many ways to do this. In my case, I use an access control list (ACL) which defines who has access to do what, and rely on a combination of mandatory and discretionary access controls. Allow me to explain:

  • To implement (1) in the policy, I give myself a set of keys to everything in the house. This gives me complete access to everything that exists. The ACL entry would read: “Me: ALL“. The control would be mandatory, as I require a key to access what I need.
  • To implement (2) in the policy, I give my cats free range to all the rooms in which they are permitted. For the rooms from which they are banned, I simply close the door. The ACL entry would read: “Cats: ALL except ‘laundry room, exercise room, office’“. The control would be mandatory, as I am relying on the fact that my cats lack opposible thumbs and cannot operate the doorknobs. (They are also not allowed on the kitchen table or counters, but this is a descrectionary control, as can evidenced by the fact that I often hear a thump when I walk into the kitchen, followed by a small furry face looking up at me with a perfect picture of innocence.)
  • To implement (3) in the policy, I had to be somewhat more complicated. Generally, my friends are allowed in my house, but only when I am present. However, in certain circumstances (when I am traveling), certain friends are allowed to come over and feed my cats. The ACL here is somewhat more complex:
    • “Friends: ALL when ‘Me in room’“
    • “Friends: ‘bathroom, kitchen, living room’ when ‘Me in house’“
    • “Friends.trusted: ‘bathroom, kitchen, living room’“

The control here is a combination of mandatory and discretionary. In order to access my house, my friends must either request access (ring the doorbell) and have it granted (I open the door and let them in) or be in the Friends.trusted group (I give them a key). This allows them access to the house. Once they are in, I rely on the discretionary access control of social mores (the customs, not the eels) to keep them from digging around my private areas.

  • To implement (4) in the policy, I use a similar method as with friends but with a tighter ACL rule: “ServicePersonnel: ALL when ‘Me in room’ AND ‘have reason’“. As with my friends, the service personnel must request access and have it granted. Then, I stay with them at all times keep them where they only have a reason to be.
  • To implement (5) in the policy, I simply keep the doors locked and the security system armed.

Though I failed operationally to implement (5) at the time of my incident, I have corrected this problem. My questions for you:

  1. What different roles/groups of people do you have in your business?
  2. How do you make sure that you limit access to these roles?

Real Life Lessons: Monitoring

  • At January 29, 2008
  • By Josh More
  • In Business Security
  • 0

[flickr]photo:2194849199(small)[/flickr]The second lesson to learn from my incident is the importance of monitoring. The concept behind monitoring is where you have a service that periodically checks the status of your resource and if there is a problem, it lets you know. These are commonly seen in physical security (where you have a device that knows when doors/windows open or if there is movement where there should not be) and in I.T. (where you periodically look at a web or email server and make sure that things are running properly).

In my case, I had three monitoring systems. My security system is aware of when doors or windows open, and if that occurs, it sounds an alarm and notifies the security company. This is highly (99%) reliable, when it is active. The fatal flaw in the system is that it does this whether a criminal comes in the house or if I leave the house. Thus, it is easy to leave it off when I am home. The second monitoring system is that of my watch cats. In theory, if someone enters the house, the watch cats will start hissing and clawing and otherwise alert me to the individual’s presence. In practice, the proper operation of watch cats is directly proportional to how tired they are… and how likely the intruder is to give them yummy food.

They’re not 100% reliable.

The third monitoring system was me. On some level I was aware that something wasn’t right, and the smell of cigarette smoke did wake me. However, while the monitoring was effective (I woke up), the monitor was not (I ignored the problem and went back to sleep).

Thus, all three of my monitoring systems failed, largely due to operational problems. I have corrected this by making sure that my security system is on, even when I am home. Like many operational challenges, the problem is taking the same action often enough to make it become a habit. Once you reach that point the operational costs are effectively zero.

My questions to you:

  1. What are your primary resources that need protection?
  2. How do you ensure that you know when they are affected?

Real Life Lessons: Defense in Depth

  • At January 24, 2008
  • By Josh More
  • In Business Security
  • 0

[flickr]photo:121282608(small)[/flickr] The first lesson to draw from my experience is that is almost perfectly illustrates the idea of Defense in Depth (DiD). Simply put, the concept is that it is best to layer your defenses. That way, if one layer fails, there is a good chance that a second layer will block the attack.

In my case, I had locks (two different ones). I had a security system. I also had two watch cats and a defensive weapon. When the incident occurred, my first two controls had failed. The locks weren’t engaged and the security system was off. However, my watch cats reacted to the changed circumstances (which I ignored). Once I became aware of the situation, I was able to arm myself and defuse it.

To generalize this, if you’ll oblige me while I lapse into a bit of math (a small amount, I promise).

Suppose that you are comparing two technologies. One is 99% effective, the other is 90% effective. If money were not a factor, most people would go to the 99% effective option. . . but let’s look a tad deeper. Let’s say that the 99% effective solution costs $100,000 but the 90% effective solution only costs $10,000. Now you’re caught in a classic security vs economy choice. However, suppose that there is a second product that is also 90% effective and costs $10,000. If you layer them, you get the following comparison:

99% – Cost = $100,000 – 1 out of every 100 attacks gets through.
90% + 90% – Cost = $20,000 – 10 out of every 100 attacks gets through the first layer… 1 out of every 10 attacks get through the second.

So, you are looking at the same average effectiveness – 1 out of every 100 attacks are successful, which leaves you free to compare the $100,000 and $20,000 price tags. The choice gets a lot easier, doesn’t it?

However, that’s only half of the story. Let’s extend this a bit with two more layers.

99% – Cost = $100,000 – 1 out of every 100 attacks gets through.
90% * 90% * 90% * 90% – Cost = $40,000 – 1 out of every 10000 attacks gets through!

So, for $100,000 you can get a single solution that is 99% effective. And for $40,000 you can get four solutions that combine to be 99.99% effective!

In my case:

  1. Locks ($200) – This is a binary defense. It is either ON or OFF. While you can still break the defense when they are ON, they are effectively absent when they are OFF.
  2. Security System ($200 + $20/mo) – This is also a binary defense. Given that it is inside the house, it is more difficult to break this defense, but still quite possible. Like the locks, it is 100% ineffective when it is OFF.
  3. Watch Cats (~$100/mo) – This is a complex defense. They have a high false positive rate. However, the false negatives are fairly low. The problem is that the high false postive rate creates the “cry wolf” problem that can render this defense ineffective. This is what occured in my instance.
  4. Me + Sword ($200) – This is also a complex defense. It is highly expensive, as it depends on the primary resource that needs to be protected (me) to be effective. If it fails, the resource (me, again) could be compromised (i.e. injured or killed). On the plus side, I have a fairly low false positive rate (I almost never stab legitamate visitors) as well as a low false negative rate (I almost never let strangers wander around my house without confronting them).

Thus, in an instance where I had four fairly inexpensive security controls, three of which failed. However, because I had a layered defense, the primary resource (me) and the secondary resources (my stuff) were kept safe from harm. My questions to you:

  1. What is your business’s primary defense?
  2. What happens when it fails?

Real Life Lessons: The Story

  • At January 22, 2008
  • By Josh More
  • In Business Security
  • 4

[flickr]photo:218204744(small)[/flickr] I will sometimes have friends over. This blog series with an event that occurred after a small gathering and then veers into a security analysis. It is my hope that it is as educational for you as it was for me.

We ended the night much later than planned, and since I had a busy morning, I neglected my normal nightly routine. Thus, that night, I neglected to arm the security system. I also assumed that my friends had locked the door as they left. As I am sure you can tell, this does not bode well…

Later that night, I awoke to the smell of smoke. While unpleasant and unusual, my neighbor is a smoker and when the wind is just wrong, I sometimes get a whiff of it in my bedroom. Since it was definitely cigarette smoke that I smelled, I went back to sleep. Then, a bit later, I woke up to my cats acting oddly. Not terribly unusual, but strange enough that I probably should have checked it out. Being half asleep, I didn’t. Instead, I just closed my bedroom door to keep my cat from bugging me. This is the part that I’m kicking myself over.

Why?

Well, once I finally wake up, I go about my normal morning routine. During this process, I see a pair of shoes on my living room floor that had not previously been there. Looking up, I see a young man sleeping on my couch, who had also not previously been there.

This is a situation for which I did not have a ready response.

Since it was dark, I considered the possibility that one of my friends couldn’t start his car or had gotten kicked out of his house (unlikely, but not outside the realms of possibility, especially given how late we broke up the party) and came back to my place for the lack of anywhere better to go. Another possibility was that a stranger had broken in (unlikely) and taken a nap on my couch (considerably more unlikely). Obviously, the way to determine which of these two possibilities were occurring was to turn on a light somewhere.

First, however, I decided to put on some pants. *shrug* it just seemed like a good idea.

Given that I was going into an unfamiliar situation, I decided that preparation would be wise. I grabbed my sword from my bedroom (I don’t own a gun, but that’s a completely different post), and entered 9-1-1 (but did not hit “send”) on my cell phone prior to waking the individual. I then turned on the light in the kitchen, so that I would have enough to see by, and positioned myself between the man (boy? Not really sure. He seemed to be in his (very) young twenties.) and the light (maximizing my visual advantage), and started prodding him.

He is probably not the only person in Des Moines to wake up that night in a strange place, utterly confused and hung over. He is, however, likely the only one to wake up with a sword at his throat.

He was quite apologetic.

In response to my questions, I learned that he had been drinking last night (he said “a lot”) and that the last thing he remembered was thinking that it was too cold and he had to go inside. He then gathered his shoes and windbreaker(!) and left, asking only what part of the city he was in. I locked the door behind him.

I elected not to call the cops as I suspect that he had just learned a lot in those sixty seconds, and I have no desire to ruin someones life over a single stupid mistake.

So, what did I learn from this experience?

  1. When suddenly finding myself in a potentially dangerous situation, I am calm and logical. I have suspected this for a while, but it’s nice to have the (very) occasional confirmation.
  2. I was in complete control of the situation from the moment I became aware of it. While I am not a control freak, it is nice to know that I have that in me when it is needed.
  3. At no point was I afraid. Concerned, yes. Afraid, no. I like that.
  4. Even though I hardly ever use the front door (garage is in the back), I need to check that door nightly and not assume it is locked. I do always check the back door.
  5. I need to be better at arming the security system at night than I have been. I used to be an extremely light sleeper, but I can apparently no longer rely in my ability to wake up at the slightest noise. (I guess living in a city has changed me).
  6. It was stupid of me to ignore the subtle indicators that did wake me up. I need to be better at checking those out.

So, in conclusion, I did some very negligent things that resulted in a situation that should never have occurred. This is bad. However, once in that situation, I think that my reaction was acceptable. There is, however, ample room for improvement. We shall explore the lessons learned in greater detail in future posts

Other Sites: Business, Photos/Conservation
Search

Get the feed (RSS):



Josh More - Entropologist
Expert in removing chaos from
I.T. and business systems.

Recent Posts

  • Thinking about enterprises
  • New Book: Breaking In to Information Security
  • Security Metaphors
  • Book Review: All Yesterdays
  • Book Review – Blackhatonomics
  • Three Stories about Growing Up
  • Internet Theft and the Holidays
  • Sophos: Pushing the Boundaries
  • Controlling the Security Story
  • Video – OWASP – July 16th, 2012

Archives

Categories

  • Business Security
  • Coyote Signs
  • Mythology
  • Natural History
  • Psychology
  • Sprint
  • Uncategorized
Copyright © 2013 by Josh More