Security Policy Development
Organizations, regardless of the type of business, are required to meet many regulations and laws . This can be expensive and strenuous on an organization’s resources. There are physical, technical and policy type controls that must be met in complying with regulations and laws. Having a solid security program with properly written policy can meet most requirements.
Unless a policy is in a major document, such as the security plan, it should be a document that is between one and two pages long, is concise and enforceable.
A policy should include:
Title of Policy
Control ID – A unique number following the organization’s numbering standards
Effective Date – Date policy takes place
Revision Date – Date of last review and or revision
Revision Number – Sequential numbering of revision made to policy
Approval – Who approved the policy for release? Must be someone with approval powers
Policy Overview
Policy Purpose
Compliance – The regulations or laws this policy complies with
Recourse for Non-Compliance – What is the recourse for not complying with the policy
Scope – What areas does this policy cover
Policy Description – Details of the policy
Your organization may require additional sections, but these should be the minimum sections covered. If you use prewritten policies such as those provided by SANS or those purchased, make sure they are revised to meet your organization’s business requirements and standards.
Thoughts or comments?
Subscribe to comments via RSS 2.0
You can leave a response, or trackback from your own site.

