liveBook · Manning

Guideline

As explained in Fundamentals of Cybersecurity

A guideline is a recommended practice that directs decisions or behavior without imposing an absolute requirement.

A guideline is a flexible recommendation for a task, technology, or domain. It suggests good practice without imposing an absolute requirement or penalty for noncompliance. section 4.2.5

Guidelines help organizations make consistent, informed security decisions while adapting to differences in systems, resources, risk tolerance, threat exposure, and operational constraints. section 4.2.5 section 4.4

Guidelines can support security governance in several ways:

  • Inform security-related decisions and help develop procedures. section 4.2.5
  • Bridge high-level policies and standards with day-to-day technical implementation. section 4.2.5
  • Promote shared security practices, especially when organizations actively adopt them as part of daily work. section 4.2.5
  • Operate as internal recommendations or external references from recognized organizations. section 4.1 section 4.2.5

Adapting a security recommendation

An organization can use a secure-configuration guideline as a reference, then adapt its recommendations to its systems, risk tolerance, and operational constraints rather than treating every recommendation as mandatory. section 4.2.5

Guideline
Focus
Purpose
NIST SP 800-53
Security Controls
Provides a comprehensive catalog of security and privacy controls, widely used as a reference for building security programs.
ISO/IEC 27002
Security Controls
Offers guidance on selecting and implementing controls aligned with ISO/IEC 27001.
OWASP Top 10
Application Security
Identifies the most critical web application security risks and mitigation approaches.
CIS Benchmarks
Secure Configuration
Provides detailed configuration guidelines for systems and applications to reduce exposure to vulnerabilities.

Compare widely referenced guidelines by focus and purpose, including security controls, application security, and secure configuration. section 4.2.5

How Fundamentals of Cybersecurity covers it

How deep it goes
Defines flexibility, origins, functions, and maturity implications, but stops short of prescribing mandatory steps or penalties.
Examples
Names NIST SP 800-53, ISO/IEC 27002, OWASP Top 10, and CIS Benchmarks as external cybersecurity references.
What you can do after
Apply it via named security references to inform decisions and adapt recommended practices to organizational conditions.
How it connects
Connects policies, standards, procedures, security governance, administrative controls, and security maturity.

Also explained in

Compare how 3 books explain guideline →

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.