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?"
I use it as a means of literally scaring up new business. I'm in IT security. Frankly, I couldn't care less about it and I haven't seen anyone that takes it seriously.
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!
Slashdot is about to be declared an enemy combatant in cyber-warfare. DDoSing .gov sites...
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!
I work at a large financial firm, and also hear the C word (compliance) all the time, but in reality it really has not produced much work for us. I attribute this to a few things.
First off is that in our journey to institute better well defined processes and to move up the CMM process scale, we have implemented tools that fulfill the reporting and papertrail requirements of SOX quite well.
The second reason I feel that I havent been affected too much is that the law is apparently very ambiguous. From what I hear the only guidance the SEC will give us is "do the right thing." But what is the right thing? how much of an audit trail is enough? When are you in compliance? I think alot of companies are kind of sitting on the sidelines shitting their pants waiting for some lawsuits to define more clearly what is good enough.
We have had to add some features to our system that logs more records and paper trail type stuff to a database, but all in all these have been minor changes.
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). Really they are defeating their purpose of more security as I either use a "cleverly" hidden post it note or just call the helpdesk every time I reboot, but thats a different story. We also no longer have physical access to servers and such which is a real PITA as everytime VNC or hangs on a machine you have to grab someone at the VP level or the sysadmin who may be at various locations throughout the city to swipe you into the server room.
So far, the changes have been inconveniences. We were always fairly unique in that our managers fought very hard for us to keep a small-shop laxness while being a part of a large organization. Kind of like someone moving from a rural area, we are just adjusting to having to do the equivalent of lock the door when we leave the house.
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,
My reading of the SOX's effect on IS is similar to ISO9000. I.e., do you have a process? good. Is it written down? good. Do you follow it? good. Reminds me of an ISO9000 audit a company I worked for. When asked if they make software, they replied "No, that wing of the building is marketing. You don't need to go over there." They got the approval and proudly display the ISO9000 sign to this day.
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.
It might have something to do with a law passed in Italy which requires all companies doing business there to change passwords every 90 days (at a minimum), but it has nothing to do with US law.
Financial Institutions. I work for a mid-sized bank in the southern US. Many companies have IT departments that would not be nearly as affected by SOX as a financial company. More than half of the hardware/software that our IT supports relates to or interfaces with some sort of financial information. Therefore SOX impacts almost every function that our technology performs.
But... you know... if we were, maybe we'd have to get some IT security up in this piece. Our network and database security is a joke. At some point our business may need to join an association that requires SOX compliance, and that's got people all nervous. For good reason.
It would cost us a fortune to replace me with someone who actually knows how to code for a living.
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.
It's interesting that a number of people replied how it affected them personally as opposed to institutionally. Institutionally, I suspect it will be a good thing, but time will tell. But, as a counter to all of the "it's a colossal waste of time" posts....
My wife's company did it, and yes, it ate up 30-40% of her time. But, while everyone else was bitching about it, she decided to master it, and document everything, so the next batch of clueless auditors would have something to look at. It was tedious, but only slightly more so than enduring the audits themselves. She ended up getting promoted 3+ years early, forming the nucleus of a new department, and managing compliance for a couple hundred IT personnel.
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.
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?
http://xbrl.edgar-online.com/x/resources/sfarticle .asp
"Looking at Business Reports Through XBRL-Tinted Glasses
By Liv A. Watson; Brian L. McGuire, CMA, CPA; and Eric E. Cohen, CPA
XBRL is the bridge for communicating financial information easily, quickly, and efficiently. "
Something to keep in mind. What good is all the "disclosed" information, if you have to type it all back in?
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.
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 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.
I work in an accounting firm, and have my CPA and CISA. Of course, on /. that doesn't matter much......
Here's the thing most people don't realize about SOX: It only matter to SOX if it means that there is a greater than remote chance that a reasonable person would decide that a deficient control would lead to a material misstatement. Thus, controls that relate to financial reporting are the only important ones
What does this mean? Basically, a control that would be flagged as being bad in an operational IT audit might not be flagged for SOX. For example, you need strong passwords. However, if there are compensating manual controls that exist outside of the system, such as a review of every journal entry being made, and a review at the end of the month and at the end of the year of all entries and review of all balance sheet and income statement accounts, then weaker controls (like weak passwords) don't matter as much. This only really applies to small companies, as a large company could have thousands of journal entries.
Basically, a deficiency needs to have a greater than remote chance of causing a material misstatement. Accountants see possibilities on 3 levels: Remote (chance of future event is slight), reasonably possible (chance is more than remote but less than likely), and probable (future event is likely to occur). What's the definition of material? Well there are quantitative judgements but basically if a problem would make someone go oh crap! that's material.
So, what does this all mean? If there are compensating manaul controls then the IT controls matter less and less. For smaller companies, IT controls are not as important as the management would have greater control with reviews. For larger companies, you need stronger IT controls (passwords, change controls, operations and security controls etc) because an outside manual review becomes impossible.
Pretty much the only IT control you MUST have is strong backups, with sufficient retention, archives, offsite management, and testing of the backups. Interestingly enough, DRP and BCP plans don't count for SOX, as future controls aren't considered.
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