Uncover Your Areas of Risk

IT audits can confirm effective IT processes and improve continuity of operations.

The benefits of IT auditing extend well beyond regulatory compliance. But even when not required by law, IT audits should become regular checkpoints for almost every information technology environment.

Continuity of operations and disaster recovery planning remain firmly entrenched in the hands of IT, often out of view of government leaders. State and local government leaders need to be educated about the benefits of auditing processes. IT audits uncover areas of risk and help senior officials understand where additional money may need to be budgeted.

Audits confirm effective IT processes to ensure the job security of the technical staff. Ultimately, identifying and minimizing risk increases peace of mind, when government leaders are shown that the systems and information needed to operate the organization are safe and secure.

When developing an IT auditing plan, consider a few key strategies:

  • Meet with senior officials to identify operational goals and discover concerns. What fears do they have? What potential failures do they see? This meeting will be one of joint education, where IT and leadership share what each thinks is important. Based on discovered concerns, develop an audit plan to check and confirm the most important mutual goals.
  • Select an unbiased third party for the audit. An audit performed by a group that wants to sell additional products or services might not produce a trustworthy report. Clearly state the scope of work and limit the potential for future services. This approach encourages focus on the task at hand and engenders trust in the resulting report.
  • Evaluate continuity of operations as part of the audit. Critical systems that have redundant components should be failed (during a maintenance window) to confirm that operations will continue even during a failure. Test different failure modes to ensure continuity despite a variety of potential problems. Try to fail the system when testing -- don't try to pass it. Only when the system can't be made to fail should it be considered acceptable.
  • Auditors should be key contributors to your disaster recovery planning, both in plan development and firedrill testing. Have the auditor recover critical portions of your environment. After each major IT deployment, consider trying a system recovery offsite, as though you had lost your data center in a fire, flood or other natural disaster. 
  • IT auditors should also be well-versed in security protocols and "white hat" hacking. Allow your auditors to attempt to compromise your systems by hijacking services or stealing data (specifically, customer data).
  • Auditors also need to keep a scorecard of observed, regular maintenance. How often were backups performed successfully? Were logs checked regularly? What other daily or weekly tasks should be measured to assure those tasks were actually performed as scheduled? Simple metrics (for example, the success rate for daily backups, measured as a percentage) can be tracked to show improvement (or lack of it) over time.
  • The auditor should produce two documents. The first, a technical report for IT staff on what risk points were found. The second, and most important, should be a one-page nontechnical summary for leadership. Develop a simple scoring system so each audit over time can be given a simple grade. This will help measure improvement and show the value that audits bring.

Every organization depends on its IT systems to keep operations running, though some skip the easy and relatively affordable step of implementing an effective IT audit. Few organizations will find a better way to increase communication, understanding and trust between IT and senior leadership.

Feb 10 2011