No one wants to write security policies, but every company needs one. Right?

Here is an example of what to avoid:

The general process is that the person assigned will copy a policy from another company, change the names, and submit it for acceptance. The result is that no requirements were identified, no issues were properly addressed, and a solution that was specifically developed for another company has been used as a best hope of solving the current company’s requirements.

A robust IT security policy is key to any enterprise IT security program. If there are flaws and loopholes in the security policy, then these problems are likely to get compunded later.

Food for thought…

RiOn