Ten Stupid Ideas to Harm Iowa
- At March 02, 2009
- By Josh More
- In Business Security
- 1
As I was reading the March 2, 2009 edition of the Des Moines Business Record this morning, I was surprised to read the editorial section “Iowans offer ideas on budget”. The gist of the article is that the Democrats and Republicans are soliciting ideas for ways to save money. The general tone seemed to be that Iowans have some good ideas, and express some doubt as to whether the legislators would actually listen to them.
Now, this isn’t a political blog, it’s about security (as well as nature, technology, business and mythology… but mostly about security). The hardest thing about working in security is that it’s impossible to be perfect. In many cases, one has to look at the problem and pick the least horrible solution. If you’re really really lucky, you can align technology and security with the business goals and work towards a common goal. Mostly though, it’s about looking at tradeoffs.
Reading this list of suggestions is a wonderful exercise in this type of thinking. Let’s take a look at the tradeoffs around what seems to be passing for “prudent thinking” among today’s Iowans.
“Set up toll booths on the interstate highways. One variation: Only charge out-of-state drivers.”
The intent here seems to be to raise revenue for the state by leveraging our interstate system which, if I recall, was largely funded by Federal dollars. Assuming that it is even legal to do this, is it wise to effectively to institute a tax on mobility? For years I’ve heard concerns about the “brain drain” in Iowa. Do you really think that smart kids will stick around in a state that actively hampers their movement?
Also, even if it’s only a tax on out-of-state drivers (which has some implementation difficulties), is it a good idea to make it economically worthwhile for truckers and travelers to re-route through Minnesota or Missouri?
Lastly, how would we pay for all the toll booths?
“Suspend maintenance of bicycle trails for a year and concentrate on the roads and sidewalks instead”
Right. We are living in a state with increasing numbers of people who are out of work. With a growing population who can’t afford to repair failing vehicles. Where pollution is on the rise and gas prices are expected to follow soon. And lastly, where obesity and heart disease are leading health concerns… and the solution is to take away the bike paths?
We’d be saving tens of dollars now and then paying thousands of dollars to repair the ecological damage and deal with the health impact.
“I am a 30-year DOT (Iowa Department of Transportation) employee. … There are far too many do-nothing positions in the DOT that could easily be eliminated, saving millions of dollars.”
I’m all in favor of efficiencies, but I have to wonder how shifting millions of dollars from minimally productive work towards unemployment benefits would be a net gain for the state. Maybe, it might make a bit more sense to turn the “do-nothing positions” into “do-something positions” instead?
“Audit the recent tax returns of the upper 10 percent of Iowa’s taxpayers.”
This logic only holds up if you believe that the upper 10 percent of Iowa’s taxpayers are crooks. In fact, if you’re in the upper 10 percent, you’re likely NOT a crook. The crooks would be the ones who find the loopholes to appear in the lower 90 instead. The really big crooks would be the ones that have managed to not show up on the tax rolls at all.
I suspect that this suggestion would result in a lot of busywork for the auditors and, in the end, would result in MORE crooks getting away, not boosting the state’s coffers.
“Establish a whistle-blowers committee to reward everyone who reports waste of public money.”
Um, reward them how exactly? With public money? With tax credits? Who pays for the committee?
I think I have some waste to report.
More seriously, security is all about checks and balances and there ought to be a good way to report such wastes. Personally, I think that reporting such things to the media and our elected officials is working pretty well.
“The salaries of Iowa’s elective officials are generally the second or third highest (compared with the seven surrounding states), and the judges are consistently the second highest. … The salaries need to be reigned in.”
Suppose I’m the CEO of a large company make $500,000 a year and am engaged in some sort of illegal business practice. Suppose this practice puts you out work and you have to sue me. Now suppose that you have very little money, and your only hope at economic survival is for justice to be served.
Now suppose the judge makes so little that I can spend ten percent of my yearly income ($50,000) to bribe the judge to rule in my favor. Suppose I could spend less than one percent of my yearly income ($5,000) and give “campaign contributions” to our elected officials to change the laws in my favor.
I don’t know about you, but I’d much rather live in a society where our elected officials and judges are as hard to corrupt as possible. If this means paying them more, then by all means, let the dollars flow.
“A 10 percent pay cut for every state employee making a salary of more than $100,000.”
OK, so there’s something magical about the $100,000 figure. I can understand that. I can also understand how people that make substantially less can be upset that many people are making more than that. However, the thing to remember is that people don’t tend to just step into such jobs. Such a high salary is often the result of years of hard work and compromise in other areas of their life. A sudden drop in salary from $100,000 to $90,000 is a really good way to tell employees “you’re not valued here and you should go back to the private sector where you could both be valued and make around $200,000”.
The follow-on question to ask here is whether or not we could afford to replace all of the $100,000 workers at the state, and what that would cost. I bet it’d be a heck of a lot higher than the savings that we would get by cutting their salaries.
“Stop allowing state employees to drive state vehicles to and from work.”
As I understand it, such a perk is one of the reasons that state employees accept lower salaries than the private sector. If we take them away, are we prepared to raise their salary to compensate? Are we prepared to replace them entirely should they leave?
Also, might it not make sense to encourage people to drive the state vehicles as often as possible? The more ethanol consumed the more our farmers make. The more cars that need repair, the more work the dealerships make. The more cars we buy, the more the car factories make.
“I recently read that the state wants to provide ‘diversity’ training to all 21,000 state employees at the cost of $250,000. Surely the state can come up with a better way to spend $250,000.”
The United States of America was founded on immigration (along with other, less pleasant realities). No one person can do everything, and no one culture can be the best at everything. Immigration provides for an inexpensive workforce that is also often skilled in special ways. Immigrants will often make the tradeoff of a lower salary for a better (or different) way of life. Some will work hard at multiple low-wage jobs simply to provide a better life for their children. In short, immigration is a wonderful thing and an often-overlooked driver for our economy.
The states on the coasts benefit from this more than Iowa, because they’re easier to get to. As such, they’ve developed a culture that is perceived as more welcoming of others than the Midwestern states. “Diversity Training”, as dumb as it sounds, is intended to counter this perception.
Like it or not, Iowa has a branding problem. If we want to be the fast-moving, accepting, challenging environment that I’ve been hearing about. You know, the state that won’t drive all the kids away after college, we have to change the perception. If such training lets us attract just five young people earning $50,000 a year (or ten at $25,000), we’re making progress.
“Use more videoconferencing, rather than sending state employees to meetings that require driving and overnight stays.”
I actually like this one. Iowa has a wonderful distance-learning solution with the ICN. That could be leveraged to reduce travel and overnight stays, and save money across the board.
What I like most about it is the phrasing “use more”, as opposed to “require” or “use only”. There are certain areas where face-to-face meetings are often most effective. We should not have to give up effective meetings and trainings to save money. We should simply use the technology where it makes sense to do so.
“Eliminate most mowing along roads and highways.”
Wow. Just wow.
I grew up in the country. I’m used to unmown ditches where the weeds and grasses use our prairie soil to reach truly amazing heights. I love nature. I love the sound of the tall grasses rustling in the breeze. I love animals. I love deer. I do not love hitting them when I’m moving at 70mph. I’m also not a fan of rats, ticks and opossums.
We mow along roads and highways for a reason. Public safety should not be compromised to save a few bucks. Besides the salaries that we would save would, again, be converted directly into unemployment benefits.
Surprisingly, there’s no suggestion for the one logical step towards a budget shortfall. Taxes will have to go up. No one likes paying taxes, but if the alternatives are:
- Driving away interstate commerce
- Having an unhealthy population and environment
- Laying off tons of people
- Producing busywork for tax auditors
- Spending money to track where our money went
- Having corruptible judges and congresspeople
- Driving away the high performers
- Owning a fleet of never-used state vehicles
- Driving away energetic immigrants who could jumpstart our economy
- Increasing interstate deer-related fatalities and intra-city disease
I’ll gladly pay more.
Luckily, I live in a representative democracy that, like security, is based on checks and balances. I trust my representatives to do what is best for the state. And they, in turn, trust me not to vote them out if they decide to make unwise cuts to produce short-term gains that will cause larger long-term losses. After all, it was that sort of thinking that got us into this mess in the first place.
And we’ve all learned our lessons, right?
Tech Review – Telephones
- At February 27, 2009
- By Josh More
- In Business Security
- 0
This blog is about technology, business and security, and even though telephones are older technology, they are still technology.
Earlier this week, I received a phone call. As I was busy, it went to voice mail. Upon checking it, I heard the following:
Hi, this is Travis. Calling about full time and part time work. 555-555-5555.
First of all, I do not know Travis. Secondly, I do not know if Travis was looking for work or looking to hire. Third, I have no idea what company Travis is representing (or if he even is). I returned his call and left a message with my name, company, reason for calling and a contact number.
This morning, my phone rings and the following conversation ensues:
- Phone: Ring Ring
- Me: “This is Josh”
- Note, I deliberately answer the phone this way, because many of the automated systems listen for a “hello” or a “yes”. It’s also a good way to put people off their guard and give me the upper hand in case they’re trying a scam.
- Phone: Pause
- This indicated to me that I was being called by a machine.
- Travis: “Yes, I’m looking for Josh”
- I just told him who I was. This tells me that he’s not listening.
- Me: “This is Josh”
- Note, making me repeat myself is not a good way to start a conversation or a relationship.
- Travis: “I think I received a call from this number looking for part time work”
- OK, first of all, his message was full or part time work, so he’s changed his story. Second, he clearly doesn’t know who he’s calling. Third, I have some doubts as to whether he’s actually listened to my message.
- Me: “May I ask who is calling?”
- Travis: “Travis”
- Uh huh. Either this guy is utterly clueless or there’s some sort of scam going on here.
- Travis: “Are you looking for part time work?”
- Yes, as a matter of fact, I am. In fact, I don’t even care what the work is, where it is, when it is, or how much you pay.
- Me: “Um, what kind of work?”
- Travis: “Well, we’re in the health care industry”
- Right. Are they a hospital? Are they looking for nurses, doctors, janitors, receptionists? Maybe they do health insurance. Maybe they run around breaking people’s kneecaps and then driving them to the ER. So many options, so little time.
- Me: “I work in I.T.”
- Travis: “Umm, err”
- At this point, I decide to let him off the hook, as I’m busy and have real work to do. Even if he is trying to scam me, I don’t have the time or legal authority to set a trap for him.
- Me: “I suspect that you have the wrong number. In the future, it would be useful to know which company you represent and what sort of work you are referring to.”
- Travis: “Thanks for the tip!”
- Phone: Hang Up
The telephone is a form of electronic communication, much like email, blogging, IM and Twitter. As with all forms of communication, there is a minimal standard of etiquette as well as a layer of etiquette that is technology-specific. In this case, were Travis a legitimate caller, he should have given me his company name and a reason for his call in his initial message. That would have given me the information necessary to return his call and leave a message indicating that he had dialed the wrong number. That would have much more efficient for everyone involved.
Also, were Travis a scammer, he should have researched me before calling me (I’m not difficult to find) and constructed a scam that would have appealed to me. Odds are “I need help with my computer” would have sufficed. At that point, we could have had a conversation about the type of work I do, which would have enabled him to better tune the scam at getting either free work or money out of me.
By not following the appropriate form of social etiquette for the communication medium, he tipped me off that there was something hinky going on. Much like misspelled words in email, poor (or perfect) grammar in spam, or letter-abbreviations in instant messages, a variance from established social convention is often the first tip we get that a security violation is taking place. Watching for those is the best way to protect yourself against scams and shady business dealings. It’s also a good way to recognize business errors before they start to take too much of your time.
In case you need one, there are many phone etiquette guides.
Small Business Defense – Remote Logging and Analysis
- At February 26, 2009
- By Josh More
- In Business Security
- 0
The first thing to realize when it comes to protecting your logs from attackers is that if the logs aren’t there, they can’t be attacked. At a minimum, you should consider setting up a remote logging server. This does not have to be a brand new top-of-the-line server. It can be an older server, a workstation or a virtual machine. The big thing to keep in mind is that it will need a lot of disk space. Depending on your network, it may also need a very fast network connection.
A nice free option to use is syslog. It’s not as user friendly as some of the commercial systems, but you can’t beat the price. For this tool, you just install one of the syslog-compatible systems on your remote server and configure each of your other systems to log to it. There are Windows tools and guides so you can capture those logs as well.
Of course, there are some commercial options as well. These often include enhanced tuning and searching. Splunk , Snare and LogLogic are known in the industry.
The second thing to consider when looking at logs is that you actually have to look at them. Remote logging may get the logs away from the attacker, but if it also gets them away from you, they’re not terribly effective. Most of the log management tools fall into three categories:
- those that find problems and alert you
- those that let you search the log
- those that help you visualize the data.
Before looking at any of the many tools out there, ranging from application-specific to purpose-specific to problem analysis, you should first consider what you care the most about. Logging involves a lot of data, and if you start with alerting before you tune anything, you’ll be drowning in it. Similarly, it doesn’t make much sense to put considerable analysis time into an application that isn’t business critical.
Instead, it’s best to start by getting all of your logs in one place, and focusing on doing that well. That’s a large project in of itself. Once that’s done, start looking at the sizes of the log files that you’re creating and work on reducing them. Odds are that at least one of your logs was set to maximum verbosity for testing something and never set back. Once you know that all of your logs have the data they need in them and as little garbage as possible, start with the biggest and look for a free tool that helps you pull out the important information. Then, move on to the next. Yes, it will take a lot of time and many tools. It may not look pretty, but it will work.
And, after all, working is what matters the most.
Then, later, once you have a greater level of inspection than you’ve ever had, you’ll know enough to seriously consider the big log management players. There’s no point in spending lots of money until you know what you’re spending it on.
Small Business Attack – Changing Logs
- At February 25, 2009
- By Josh More
- In Business Security
- 0
In I.T., we love logs. They’re organic, they float, they burn and you can build houses out of them! Of course, we also like the other kind of logs as well.
The kind of logs I want to talk about are the ones that keep track of what’s going on with your systems. They are intended to make it easier to reconstruct strange behavior and trace issues between systems. System administrators will check the logs to see if there are problems involving CPU, memory or disk usage. Network administrators can use them to trace network congestion and connectivity issues. Developers can use them to find out why certain programs aren’t functioning properly. Also, security professionals can use them to help identify attackers and how far they penetrated a system or network.
At least, in theory we can. There’s one problem: attackers can write logs too.
A common technique that attackers use is to erase or modify the logs after they successfully compromise a system. They can cover up vulnerabilities, erase their tracks and make things appear to be running OK even when they’re not. They can also read the logs and use the information in them to identify other targets.
If you have a system that is backed up on a regular basis, an attacker can find those logs and use them to identify the backup server. Once they know that, they can focus their efforts on getting the data that’s over there. They can use logs to identify which users might have elevated permissions on other systems. They can also use them to determine what “normal” activity looks like, so they can hide their activities in places you can’t find them.
Like many things, it’s a double-edged sword.
You need the logs, because they’re useful to you, but they’re also useful to the attackers, so what can you do?
Security lessons from Nature – Immortal Jellyfish
- At February 24, 2009
- By Josh More
- In Natural History
- 0
Today, let’s take a look at the other side of immortality (the down-side of which was explored here). In particular, let’s look at jellyfish.
That’s right, scientists have discovered immortal jellyfish. (Such an interesting world that we live in.)
What’s most interesting about these creatures is how they achieve immortality:
But when starvation, physical damage, or other crises arise, “instead of sure death, [Turritopsis] transforms all of its existing cells into a younger state,” said study author Maria Pia Miglietta, a researcher at Pennsylvania State University.
The jellyfish turns itself into a bloblike cyst, which then develops into a polyp colony, essentially the first stage in jellyfish life.
The jellyfish’s cells are often completely transformed in the process. Muscle cells can become nerve cells or even sperm or eggs.
In other words, it does a “reset”. This allows it to adjust in the face of environmental changes and rebuilt itself in such a way as to maximize success.
How many times have you had your IT people come up to you and say “if only you’d let us re-write/re-build the system, we could make all these problems go away”? How many times have you sighed, shaken your head and patiently explained to them why such a move didn’t make business sense?
Looking at the jellyfish, it might be worth considering. If things aren’t looking too good, maybe it would make sense to take another look at those persistent business problems. If you can solve even ONE of them, it might allow you to rebuild your company. After all, it worked for Flickr.