liveBook · Manning

Style guide

As explained in Fundamentals of Cybersecurity

A standard is a formally specified requirement or criterion that translates policy requirements into consistent, measurable implementation practices.

A security standard sets criteria for putting security requirements into practice. It turns a broad expectation into consistent actions or controls that an organization can check. For example, a policy might require customer data to be protected from unauthorized access. A corresponding standard could require AES-256 encryption, storage on approved systems, and multi-factor authentication. section 16.1 section 3.2.3

Standards help teams apply requirements consistently and compare their practices with an established benchmark. Some are created within an organization to specify how its controls must be implemented. Others come from industry or standards-setting bodies; ISO/IEC 27001, for example, sets requirements for an information security management system. section 4.2.2

A standard has a distinct place among governance documents:

  • Laws and regulations impose legal requirements. A standard provides criteria and guidance for meeting security requirements; an external standard may also be required by regulation or contract. section 4.2.2 section 4.3.4
  • A policy states what the organization expects. A standard makes that expectation more specific. A procedure gives the step-by-step instructions for carrying it out; a guideline offers advice. section 4.3.4 section 16.1

An external standard is generally voluntary until an organization adopts it or another obligation requires it. Missing its requirements may not bring a direct legal penalty, but it can affect certification and trust. For example, failing to meet ISO/IEC 27001 requirements may cost an organization its certification, which customers or partners may use as evidence of its security practices. section 4.2.2

Governance Element
Enforceability
Scope
Laws and Regulations
Mandatory
External
Standards
Mandatory once adopted
External or Internal
Policies
Mandatory
Internal
Procedures
Mandatory
Internal
Guidelines
Not mandatory
Internal

The comparison shows which governance elements are external or internal and when they are mandatory. section 4.1

How Fundamentals of Cybersecurity covers it

How deep it goes
Defines standards, distinguishes internal from external standards, and explains adoption and certification consequences without giving a procedure for drafting one.
Examples
Uses ISO/IEC 27001 certification and a customer-data standard specifying AES-256 encryption, approved systems, and multi-factor authentication.
What it assumes
Starts with definitions of governance and security policy rather than assuming prior governance knowledge.
What you can do after
Evaluate/understand whether a requirement belongs in a standard rather than a policy, procedure, regulation, or guideline.
How it connects
Connects standards to security governance, regulations, policies, procedures, guidelines, administrative controls, and system hardening.

Also explained in

Compare how 13 books explain style guide →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Fundamentals of Cybersecurity. The section links point to the parts of the book it draws on.