DivisionCero

Kudo

Open-source, practical cybersecurity framework and book

The formula is simple:

Coherence+Trust=Cybersecurity\text{Coherence} + \text{Trust} = \text{Cybersecurity}

It applies to governments, investors, companies, customers and many more...

Want to learn more?

Download the Cybersecurity Kit.

🚀 Quick Install

Create your Kudo app in seconds with our interactive CLI:

pnpm create @divisioncero/kudo-app

Next steps after installing:

cd your-project
pnpm install
pnpm dev

Your app will be available at http://localhost:3000


🛡️ Cybersecurity Policy

We believe in a digital world built on freedom, responsibility and integrity.

Cybersecurity isn't just about defense or attack — it's about mutual respect. It's about striving to give our best so that every interaction, every line of code and every user experience reflects a commitment agreed between the parties, based on what is defined in policies and procedures; and so that they don't stand out only for their lengthy, theoretical content.

📋 Sections

🎯 Why use this site?

  • Trust between stakeholders: It applies to investors, governments, companies, customers and users.
  • Define reference policies: Establish a common framework for cybersecurity management.
  • Team training: Support the initial and ongoing training of employees.
  • Simplify audits: Demonstrate a structured approach during internal and external assessments.
  • Scale security practices: Allow best practices to be replicated across different contexts.
  • Optimize Business as Usual (BaU): Improve operational efficiency and risk management.

🏛️ Document Governance

Enterprise Context

This means the documents aren't only applicable to a specific project or team, but are intended to be used across the whole organization.

All documents are created and maintained in a hypothetical enterprise context named DivisionCero.

Organizational Structure

DivisionCero's organizational structure follows a hierarchical model, with clear reporting lines and functional departments that facilitate governance, accountability and specialization.

Hypothetical Enterprise Context

  • A technology company that offers software as a service (SaaS).
  • It has software development, infrastructure, quality and security teams; also applicable in outsourced contexts.
  • It runs its infrastructure across multiple Cloud Service Providers (CSPs).
  • It maintains a 24/7 SOC (Security Operations Center) for continuous threat monitoring.
  • It has a team specialized in infrastructure security for implementing and maintaining controls.
  • It serves customers in several countries.
  • It employs people who work remotely.

Roles and Responsibilities

  • CEO (Chief Executive Officer): Ultimately responsible for the organization's security posture and risk management strategy.
  • CTO (Chief Technology Officer) & Technology Teams: Ensure the secure implementation of systems and infrastructure following the defined policies.
  • COO (Chief Operations Officer): Oversees daily operations, ensuring security procedures are built into business processes.
  • CFO (Chief Financial Officer): Secures appropriate financial resources for security initiatives and evaluates security investments.
  • CISO (Chief Information Security Officer): Main sponsor of the information security policy framework and governance structure.
  • SOC (Security Operations Center) Team: Monitors threats in real time, detects security incidents, coordinates the initial response and keeps continuous watch over the technology environment.
  • Infrastructure Security Team: Implements and maintains technical security controls, manages secure configurations, performs vulnerability assessments and ensures system hardening.
  • GRC (Governance, Risk & Compliance) Team: Curators of the document architecture and responsible for the policy lifecycle.
  • Legal & Privacy Office: Ensures alignment with regulatory requirements and data protection obligations, provides legal guidance on security policies and handles security-related legal matters.
  • Software Development: Implements secure development practices and addresses security requirements in software products.
  • Operations: Maintains secure infrastructure configurations and operational security controls.
  • Procurement: Evaluates vendors' security practices and includes security requirements in contracts.
  • Human Resources: Manages security training, background checks and security aspects of personnel processes.
  • Finance: Manages the financial aspects of the security program and related expenses.
  • Internal Audit: Performs independent assessments of security controls and provides assurance of their effectiveness.
  • All teams: Responsible for understanding and complying with the established policies and procedures.

🔄 Document lifecycle

📂 Document Structure

Baseline | Tools | Courses
Policies | Procedures

💾 Clarifications

On this page