Information Security Standards: Structure, Content, and Application
CISM · Information Security Program · By Super Admin
Understand how information security standards provide mandatory requirements that implement policy, including real-world examples from UC Berkeley.
What Standards Are and How They Function
Standards provide mandatory requirements describing how an organization will carry out its information security policies. These may include the specific configuration settings used for a common operating system, the controls that must be put in place for highly sensitive information, or any other security objective. Unlike policies, which are broad statements of management intent, standards translate those intentions into specific, actionable requirements. Standards are typically approved at a lower organizational level than policies and, therefore, may change more regularly to keep pace with evolving technology and threat environments.
Organizations have several options when developing standards. They may choose to develop their own standards, adopt standards created by external groups, or use a hybrid approach where they modify existing standards to meet their needs. In some heavily regulated industries, compliance with industry-specific standards may be required by law or contractual agreement. In other fields, the standards are helpful resources, and failure to follow industry best practices may be seen as negligence and can cause legal liability for the organization.
The UC Berkeley Minimum Security Standards as a Model
The University of California at Berkeley maintains a detailed document titled the Minimum Security Standards for Electronic Information. This document divides information into four different data protection levels (DPLs) and then describes what controls are required, optional, and not required for data at different levels, using a detailed matrix. This approach provides a document hierarchy that is easy to navigate for the reader and provides access to increasing levels of detail as needed.
Figure: Schematic illustration of excerpt from UC Berkeley Minimum Security Standards for Electronic Information
The image above shows an excerpt from the UC Berkeley matrix, illustrating how controls are mapped across different data protection levels. The standard then provides detailed descriptions for each requirement. For example, requirement 3.1 in the matrix simply reads "Secure configurations," but later in the document UC Berkeley expands this to require that resource custodians utilize well-managed security configurations for hardware, software, and operating systems based on industry standards.
Defining Requirements in Detail
The UC Berkeley standard defines "well-managed" configurations with specific criteria: devices must have secure configurations in place prior to deployment, any deviations from defined security configurations must be approved through a change management process and documented, a process must exist to annually review deviations from the defined security configurations for continued relevance, and a process must exist to regularly check configurations of devices and alert the Resource Custodian of any changes. This level of specificity is characteristic of well-constructed standards documents.
Notably, many of the requirement lines in the UC Berkeley matrix offer links to guidelines, which provide optional guidance to organizations seeking to comply with the policy and standards. The UC Berkeley security policy mandates compliance with the Minimum Security Standard for Electronic Information for devices handling covered data, while the linked recommendations are explicitly described as optional guidance. This structure is a clear example of three elements of the information security policy framework — policy, standards, and guidelines — working together in a coherent hierarchy.
Key takeaways
- Standards provide mandatory requirements describing how an organization will carry out its information security policies.
- Standards are typically approved at a lower organizational level than policies and may change more regularly.
- The UC Berkeley standard divides information into four data protection levels and maps required, optional, and not-required controls using a matrix.
Discussion (0)
No discussion on this article yet — be the first to comment.
Please sign in to join the discussion.