Sarbanes-Oxley - How is it Affecting You?
Grant Barrett asks: "All I hear from IT directors is Sarbanes-Oxley, Sarbanes-Oxley, Sarbanes-Oxley. SOX, as they're calling it, is taxing manpower, swallowing time, and adding huge administrative headaches--not to mention incurring fees and salaries paid out to staff or third-party firms hired to ensure compliance--and that's just the IT department. How are you dealing? Did you make your compliance deadline even after the extension? Are you joining the the backlash?"
OK, so the collapse of mega-corporations like Enron and Worldcom in accounting scandals cost the people of the country, particular investors, billions of dollars. Enron also defrauded California of billions of dollars.
MORE billions, in fact, than what the attacks on the World Trade Center cost us.
And now, they are saying that the burden of complying with a law that will help to prevent future abuses is too high? Boo Hoo.
I don't think it's too much to ask companies to prove they aren't ripping us off.
Fascism trolls keeping me up every night. When I starts a preachin', he HITS ME WITH HIS REICH!
Oh well, since he can't be arsed, here's a quote from the second link:
There have been few laws passed in the last 3 decades which are designed to help people (investors are often mutual funds and pension funds) at the expense of executive management. Executives for far too long have been able to lie and then claim they didn't know they were lying. Because the SEC doesn't go after white collar crime they way they go after some 16 year old who rips off a 7/11 these guys never go to jail. By creating a paper trail hopefully more executives who commit fraud will go to jail and there will be some decrease in the amount of fraud in US business.
If that's costs money I'm all for seeing the money spent.
They made a bunch of security changes here, some of which they blamed on SOX. The worst one was 90-day password expiration. Is that really part of SOX, or just the local interpretation?
They also closed off access to most ports besides 80, but I think that was just a local decision.
I'm posting this anonymously as I wouldn't want it traced back to me, but I can tell you not only is it costly and burdensome, but it doesn't work. We are now in "compliance", but the changes we had to make to our systems not only didn't have any affect on my ability to alter financial data, but they made them less secure in the process, because external auditors know nothing about our systems, they only have a checklist of features that have to be enabled. It's nothing more than a costly joke that wastes my time and keeps me from doing work that would actually improve our systems. I've started avoiding small, quick projects that would benefit the users, because I would spend 5 minutes making the changes and then 2 hours spread over several days documenting them and getting the required approvals to implement them.
My wife is a an auditor for a big-4 firm doing SOX work. Cha-ching!
Sarbanes-Oxley is a law that only applies to SEC firms (firms that are publicly traded in the US and must report financial statements to the SEC.)
..."). This is important because, if the CEO signs a statement that states that he knows financial statements are reported fairly and without any material misstatements, he cannot say in court that "I had no idea that this was happening."
Prevents Accounting firms from doing non-Audit functions for SEC firm that they also perform SEC Audits for (except tax-work, and only if approved by the SEC, and for work that produces minimal income to the Audit firm. These must be disclosed in the Financial Statements of the firm audited.) This is important becase an audit firm in the past could be doing as much or more work for a company in consulting as they were for in audit. The leads to an impression that the auditor might not be independant of the firm.
Increases the required independence of the Audit Committee of SEC Firms (Members of the Board of Directors who hire and oversee Independant Auditors). This is important because the Audit committee should not be biased towards the company if they are hiring the independant auditors and overseeing their work.
Makes Management of companies more responsible for the assertions they have in their Financial Statements (and assertion may be along the lines of "Currents Assets: $1.3 Billion" or "In the following year we expect to open three more locations in
Requires Management to asses the controls associated with preventing fraud, defalcation and errors that could lead to materially misstating their Financial Statements, and requires an independant Audit of this assesment. (This would be the part that affects the IT community the most.)
It also created a required record retention for audits, more thourough peer reviews of audits and rotations of the Audit Partners associated with the audit. (Thank you, Arthur Andersen)
How this affected me:
Many more jobs in the Audit field, mine being one. Which allows me to be a techy on the side, which is a lot more fun that it being work.
In Soviet Russia, asses suck this joke.
I work as a geek/developer at a well known fortune 500 oil company. I can say that although I personally thought SOX was a positive step in the right direction, the knee-jerk reaction of individual companies is stifling any benefit that may have been brought about as a result of SOX.
/., how is this going to prevent the CEO of a company from having the books cooked? How is what I'm doing a benefit to the company? (We already use CVS, so you can't say the hard copy has any purpose other than to satisfy some bean counters wicket)
Now, having seen the changes around the company and the assinine requirements that NON-financial related projects have to meet, I'd say it's worthless and will only cause the US economy to further stagnate.
Just a quick example:
I develop/maintain a menu of sorts used by about 800-1000 people on a daily basis to complete their daily sales paperwork. It's just an interface to the underlying software, and does not interact with financial data in any way. Since we've started SOX compliance, I've been required to document every line of code that changes and maintain a hard copy of said change for 3 years. It doesn't even do anything with financial data, it's just a user tool so they don't have to remember the commands of an archaic accounting package. Yet, because of what the company views as SOX compliance, about 50% of the time I used to put towards developing this tool and providing support/documentation to the end user, now get's spent doing diff's and printing reports.
So I ask you,
The most obnoxious changes have come from the IT side of things. Changing passwords every month, and having crazy requirements on them (must have two case changes, mix of numbers and letters, can not just merely end in numbers, and we can not repeat any passwords from the past year).
Funny, when some box gets rooted for having a dictionary password, there's plenty of blame to go around (for users and IT), but when rules are implemented to prevent such things, it's "obnoxious changes" from IT.
When I was an admin, I would run a script once a month trying to hack everyone's passwords...a list of users that got cracked would be sent companywide as the proverbial "walk of shame." If people showed up on that list a couple times, then the President of the company would stop them in the hall and chat about security...much more effective than a harshly worded email from the kid in the server room.
Thanks Sarbanes-Oxley!
The SOX demand on audit compliance covers the entire spectrum of business. Under the general computing section, there are strict guidelines for server logging, authentication audits, remote access, database access, incident response, change management, data integrity, data retention, monitoring, etc. This goes far beyond ethical standards involved with doing business as seen from an executive position. Executives will never understand everything involved with meeting the requirements this law has established.
Choose you future. Choose to sysadmin.
I'm just a programmer/analyst working on developing and supporting one of our products -- I don't deal with the finance end of things. :-)
Is it having an impact on IT resources that I can see? No, not really. I'd never heard of it until this story, in fact.
Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
The Theorem Theorem: If If, Then Then.
Oh - and I prefer to call it SarBox - makes it sound more like the disease it really is.
The consultants that these businesses hire are responsible for the problem as much as the businesses themselves. The accountants and independent auditors are in the business of selling hours just like any other consultant.
The new laws were crafted to solve a real problem, but only end up costing the businesses more money. Why should the same consultants that caused the problem be rewarded by a law that requires more paperwork and more billable hours for those who caused the problem in the first place?
Congress should have passed a law that rewards companies for having simplified accounting systems. Simpler accounting rules would be much easier for shareholders to understand. Similarly, those companies would be much easier and cheaper to audit. That type of law would reward well behaved companies and punish the accounting consulting firms by making their services less profitable.
SOX doesn't effect IT nearly as much as it does accounting. It really only dictated to us how our backups should be run, retention policies. A few of the other minor things involved how secure the servers containing financial information were (physical access), and tracking who should/shouldn't have access to financial software/files.
In all of the above cases, we were already more than compliant. The only major change was the inclusion of a "special" character in passwords to make them more difficult to crack. Our workflows did make some minor tweaks to things, but for the most part I'm not even noticing it.
I recently left a company where they were working on Sarbanes-Oxly (SOX). At that company, at least, it was a huge waste of time and by the time I left a black hole that sucked up out IT budget and most of our time.
Don't get me wrong, the idea behind the law is a good one, but the problem as I saw it is that its too vague in definition of what is a controlled system. Basically as I understood it any system that touched the financial records needed to be audited and controlled. For a smaller company with an IT staff of only 12 that can be a crushing overhead.
We had consultants brought in to help us figure out how to get complaint and as with normal consultant they were completely useless. When ever they didn't know an answer they said that the auditors would explain the correct procedure, that we were not expected to pass the audit the first time around. It didn't help that our manager saw this as an opportunity to force new rules on other departments that would give IT more power in "process improvements" for the company.
I left the company for a smaller private run company that doesn't have to bother with SOX audits. That was 5 months ago and my former company is still wrestling with getting compliant. The audit has been pushed back several times and apparently the consulting company that was brought in is going to be the one to audit us...
Take a moment to think about and see if that doesn't make you go cross-eyed....
The world isn't run by weapons anymore, or energy, or money. It's run by little ones and zeroes, little bits of data.
All picayne password requirements do is force the users to write their passwords on little pieces of paper stuck to the bottom of their keyboards.
Have to change your password every month? Simply append a monthly-incrementing number at the end of your normal password. Congratulations, you just lost the benefit of rotating passwords! Have to use symbols and numbers? Write in 133t5p3&k and all you do is prevent the 1&m35t of dictionary crackers. Prevent that and the users will WRITE their passwords down!
One password on a system at my work had a dictionary that was cracked in less than 72 hours. Corporate IT chewed my ass off and spit it out in little pieces over that one. But the sad part was that the system was a lab system that two hundred people needed access to. The result of IT's analism was that we had to write the password on the lab chalkboard so people could use the system.
My point isn't that passwords are stupid it's that rules for the mere sake of having rules is stupid.
Don't blame me, I didn't vote for either of them!
I too am an InfoSec guy and I have seen exactly the opposite.
I work with fortune 500 clients and they are scared s-less - the threat of jail time makes the security concerns appear more real.
All of the services and products we have been pushing - identity management, e-mail archiving, log analysis, data correlation are all growing by leaps and bounds.
my sponsors are loving it as well. The projects they have been trying to jump-start for months if not years now are getting the go ahead due to SOX audit reports.
it is amazing that all of the concerns i have had for years are now important
Where oh where has my Underdog gone?
As a staffer of a 4th party company which sells products to 3rd parties to impliment and ensure compliance, I am figuratively rolling in the legislatively guaranteed income.
Just a few things I've noticed here..
Our blank check stock must be kept under lock and key. Great.. Well the key is just in a draw in the AP department.
Control issue with AR not being able to recieve checks so in the event a check comes into our office instead of the lockbox it goes to AP. Well AP can't deposit the check without a customer # or Inv #. So they take the check to AR to get the info which generally means dropping it off and coming back later to get a stack of checks.
Database security has been changed so that people have the correct access privs. Before when a person who transfer departments they were not strict at changing them. Well turns out are genius sys admin for the DB has an SQL server running that will allow any user to write/read to any DB file despite user privs in actual database application itself. But since SOX doesn't know about any SQL server it's not an issue.
Basically everything you need to comply with is there for a good reason but in practice I find it to be for show and nothing more.
At the 2004 O'Reilly Open Source convention, r0ml Lefkowitz spoke about the impact of Sarbanes-Oxley on corporations and Open Source Software. This is the gist of what he said. Any corporate software products on the books are considered assets and are assessed at an arbitrary value for purposes of acquisition, etc. The accountants depreciate software system assets over a set number of years, often 3. So by the time the corporation has software of no more book value as an asset, that is when programmers think to ask management to open-source it. But the programmers time (usually salaried exempt) is an expense. Sarbanes-Oxley requires certain reporting of assets and expenses, such that a corporation will not be able to pay a programmer to roll up the source tree or zip it or hardly do anything. Expenses not spent in developing positive value assets are a red flag for auditors.
Posting anonymous because it has been so long that I've forgotten my password. But then, my karma was never a positive value asset for long.
I don't think it's too much to ask companies to prove they aren't ripping us off.
I'm pretty sure that it was already against the law for executives to loot a company and steal from the shareholders, even before Sarbox was passed.
I am center-left on political, social and economic issues, and even I fail to see how another law will prevent future corporate scandals, when there are plenty of laws on the books that already regulate corporate behaviour.
The problems at Worldcom and Enron (et.al.) happened because existing laws were not enforced, and nobody complained as long as the stock prices were increasing. It was only at the very end when the house-of-cards collapsed that everyone cried foul.
Unfortunately, there would be no glory in enforcing the existing laws. Can you imagine the howls of outrage if the legal system took down Enron or Worldcom at the height of the bubble? The neo-cons would have had a field day complaining about undue government interference in the economy...
I'm not sure whether Sarbox would deter a dishonest CEO from stealing the company blind if he/she thought that they stood a reasonable chance of getting away with it. Even if you get caught, the consequences don't seem to bad. It's not like Bernie Ebbers or Ken Lay are living in cardboard boxes underneath the freeway...
*** Where are we going? And what's with this handbasket?
I'm not sure what SOX does, exactly, not into that magnitude of stuff.. but.. my retail company has been making all sorts of uncharacteristic declarations, stating "we need to do this now, because of sarbanes oxley" with no other explanation. *shrug* things have been improving drastically around here, i think.
"Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
What does ANY of this have to do with disclosure of corporate finances and executive compensation?
In every scenario I've seen so far, none of our customers know precisely what they need when they ask us whether our software is "Sarbanes-Oxley" compliant. When pressed for details, they all plead ignorance.
In terms of concrete specifics, I think there's a great deal of confusion out there as to whether a software company is even *capable* of being compliant.
So, you Americans have my sympathy! Perhaps someday your congresscritters will have some measurable grasp on something other than their own two buttcheeks.
I am in an environment where I have to change my password every 90 days...and every time I change it, the complexity requirements get more and more bizzare.
I was originally assigned an 8-character, all-lower-case + 2 letters alphanumeric password. It was computer generated. I kept this password until the first expirey, then changed to another password of the same length, lowercase + digits.
Then the third expirey came around. Suddenly my previous passwords were off limits -- and I needed to use more distinct letters and numbers.
The fourth expirey came around, and I had to now use capital letters as well as lower case letters, in addition to numbers.
My password on this system has ballooned from a phrase that I could easily type in a second, and was still difficult to guess, to variations on the pattern "QWERTY" or similar on my keyboard. Anyone who watches me type my password, knows what it is without any effort at all.
The anal security policy means my password will be virtually bulletproof from the outside -- and paper-thin to someone standing over my shoulder.
It lets me make all sorts of unreasonable requests of my co-workers, and then tell them it's required for Sarbanes-Oxley compliance.
pooptruck
I remember once having to create a passphrase. I chose a short obscure quotation, misquoted it, and translated it into Quenya. Unacceptable! The passphrase needed upper case, lower case, numbers and symbols! Huh?!?!
I guarantee you that EVERYONE, including the shitwit who came up with the rules, has their passphrase written down.
Don't blame me, I didn't vote for either of them!
I got a thesis topic out of it. I'm convinced that the reglation wouldn't have come into play without WorldCom happening. I'm also going into the accounting / audit field = more work for us... it's funny how this was supposed to "punish" the audit / accounting industry and the industry will end up making far more money as a result of this.
Profane,
Here's a quick article over on mises.org that addresses the continuing problems with this latest massive interference with "the market":
http://blog.mises.org/blog/archives/003418.asp
I would appreciate any comments you have on it.
Bob-
The Ludwig von Mises Institute. The reasoning individuals economics