- CONTINUING ED
- PUBLIC PROGRAMS
- COMMUNITY ENGAGEMENT
Is it a Policy, a Standard / Procedure or a Guideline?
What's in a name? We frequently hear people use the names "policy", "standard", “procedure”, and "guideline" to refer to documents that fall within the policy infrastructure. So that those who participate in this consensus process can communicate effectively, we'll use the following definitions.
Policy: A policy is typically a document that outlines specific requirements or rules that must be met. In the information/network realm, policies are usually point-specific, covering a single area. For example, an "Acceptable Use" policy would cover the rules and regulations for appropriate use of the computing facilities.
Standard Procedure: A standard procedure is typically collections of system-specific or procedural-specific requirements that must be met by everyone. For example, you might have a standard that describes how to harden a Windows XP workstation for placement on an external (DMZ) network. People must follow this standard exactly if they wish to install a Windows XP workstation on an external network segment.
Guideline: A guideline is typically a collection of system specific or procedural specific "suggestions" for best practice. They are not requirements to be met, but are strongly recommended. Effective security policies make frequent references to standards and guidelines that exist within an organization.