Think of your organization’s information systems as a beehive, thriving and full of information (analogous to honey). The processes you have in place to guard and protect information are the honeycombs, which store the valuable information, and the worker bees are the information systems hierarchy charged with protecting the honey (assets and associated information). The worker bees are programmed to repel invaders or have backup plans in place to protect their queen (the board and the stakeholders).
The worker bees employ different tactics to repel specific intruders. A worker bee or a swarm of worker bees know the inherent threats to a particular beehive as they react to different situations in different ways. In much the same way information systems professionals need to know what threats can affect the beehive of the organization, they should also know to react appropriately.
It is with this frame of mind that my recent Journal article will be the most beneficial. In this article, I have tried to warn information systems professionals of possible errors that can happen by using examples from my experience. Even experienced professionals have experienced these kinds of issues, but the article outlines how an avoidance or remediation mechanism can be put into place. Much like the tactics used by worker bees against intruders and threats, processes need to be in place to tackle software incidents head-on.
There are certain scenarios for which information security professionals can prepare for, and my article outlines what these situations are and how to mitigate them.
Read Frederick G. Mackaden’s recent Journal article:
“Seven Software-related Incidents and How to Avoid or Remediate Them,” ISACA Journal, volume 1, 2016.