Organizational Security Policy
Organizational Security Policy
A key element of any organization's security planning is an effective security policy. A security
policy must answer three questions: who can access which resources in what manner?
The organizational security policy is the document that defines the scope of a utility’s
cybersecurity efforts. It serves as the repository for decisions and information generated by other
building blocks and a guide for making future cybersecurity decisions. The organizational
security policy should include information on goals, responsibilities, structure of the security
program, compliance, and the approach to risk management that will be used.
Importance
The organizational security policy serves as a reference for employees and managers tasked with
implementing cybersecurity. What has the board of directors decided regarding funding and
priorities for security? What new security regulations have been instituted by the government,
and how do they affect technical controls and record keeping? Which approach to risk
management will the organization use? How will the organization address situations in which an
employee does not comply with mandated security policies?
The organizational security policy serves as the “go-to” document for many such questions. It
expresses leadership’s commitment to security while also defining what the utility will do to
meet its security goals.
Developing an organizational security policy requires getting buy-in from many different
individuals within the organization. The policy needs an “owner”—someone with enough
authority and clout to get the right people involved from the start of the process and to see it
through to completion. The owner will also be responsible for quality control and completeness
(Kee 2001). Appointing this policy owner is a good first step toward developing the
organizational security policy.
The policy owner will need to identify stakeholders, which will include technical personnel,
decision makers, and those who will be responsible for enforcing the policy. Ideally, the policy
owner will be the leader of a team tasked with developing the policy. Everyone must agree on a
review process and who must sign off on the policy before it can be finalized.
The utility decision makers—board, CEO, executive director, and so on—must determine the
business objectives that the policy is meant to support and allocate resources for the development
and implementation of the policy. Business objectives should drive the security policy—not the
other way around (Harris and Maymi 2016).
The utility will need to develop an inventory of assets, with the most critical called out for
special attention. Threats and vulnerabilities should be analyzed and prioritized. Mitigations for
those threats can also be identified, along with costs and the degree to which the risk will be
reduced.
The policy will identify the roles and responsibilities for everyone involved in the utility’s
security program. The utility leadership will need to assign (or at least approve) these
responsibilities. Objectives for cybersecurity awareness training objectives will need to be
specified, along with consequences for employees who neglect to either participate in the
training or adhere to cybersecurity standards of behavior specified by the organization (see
the cybersecurity awareness training building block for more details).
The policy can be structured as one document or as a hierarchy, with one overarching master
policy and many issue-specific policies (Harris and Maymi 2016). The SANS Institute offers
templates for issue-specific policies free of charge (SANS n.d.); those templates include:
Essential Data
The following information should be collected when the organizational security policy is created
or updated, because these items will help inform the policy.
A list of stakeholders who should contribute to the policy and a list of those who must
sign the final version of the policy
An inventory of assets prioritized by criticality
Historical data on past cyberattacks, including those resulting from employee errors (such
as opening an infected email attachment). This will supply information needed for setting
objectives for the cybersecurity awareness training building block.
Threats and vulnerabilities that may impact the utility.
In addition, the utility should collect the following items and incorporate them into the
organizational security policy: