It’s Audit Time so Panic and Freak OutOK, you know it’s coming. You’ve known it’s been coming for a while now. You’ve donelittle preparation though. You’ve been too busy keeping the lights on and sneaking in theoccasional new feature. It’s audit time!It’s a strange feeling, the collective shiver that goes through the IT department at audittime. For the execs and managers fear and stress permeate. Did we resolve everythingfrom last time? What else could have popped up? What KPIs do I have to hit for mybonus?For staff it’s more likely annoyance and resignation. Great, another 4 weeks of trawlingthrough configs, piecing together CSV files, making up reports and working on their ninjaexits when a prowling auditor enters.
It doesn’t have to be like this though, especially when it comes to your systemconfigurations. If you capture your audit requirements in the form of executable teststhen audit time becomes a breeze. We’re already doing this, you say? That’s cool,maybe you’re scripting them up. Let me ask you this though:Are the audit requirements captured in a format that everyone can read?Can you execute them remotely and get compliance status back in real time for allyour servers?Can you execute them on a schedule to prevent drift from a compliance state yearround?Do they spit out reports you can hand to auditors before they’ve even asked forthem?If your answer to any of these questions is “No” then you should consider implementinga truly automated system configuration testing solution like ScriptRock.Happy audits,Alan.