-
Notifications
You must be signed in to change notification settings - Fork 11
Contributing
Christian Taillon edited this page Oct 22, 2025
·
1 revision
We welcome contributions from the community! This project thrives on collaborative efforts to improve and expand its content. Here's how you can contribute:
- Navigate to the CISOinaBox repository on GitHub
- Click the "Fork" button in the top right corner
- Select your GitHub account as the destination for the fork
- Wait for GitHub to create your copy of the repository
git clone https://github.com/CroodSolutions/CISOinaBox.git
cd CISOinaBoxAdd the upstream repository to keep your fork synchronized:
git remote add upstream https://github.com/CroodSolutions/CISOinaBox.gitBefore making changes, create a new branch for your work:
git checkout -b feature/your-feature-nameUse descriptive branch names that relate to the changes you're making.
- Follow the existing formatting and style conventions
- Ensure your content is clear, accurate, and well-organized
- If adding new sections, follow the established structure
- Update the table of contents if necessary
- Test any code examples you include
Write clear, concise commit messages:
git add .
git commit -m "Brief summary of changes (50 chars or less)
More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. The blank line separating the summary from the
body is critical."Before submitting your pull request, sync your fork with the upstream repository:
git fetch upstream
git checkout main
git merge upstream/main
git checkout feature/your-feature-name
git rebase mainPush your changes to your fork:
git push origin feature/your-feature-name- Navigate to your fork on GitHub
- Click the "Compare & pull request" button
- Provide a detailed description of your changes:
- Reference any related issues
- Explain the problem you're solving
- Describe your solution
- Mention any testing you've performed
- Click "Create pull request"
- Project maintainers will review your pull request
- They may suggest changes or improvements
- Make any requested changes in your branch and push them
- Once approved, your changes will be merged into the main branch
- After merging, you can safely delete your feature branch
- Be respectful and inclusive in all interactions
- Ensure content is accurate and well-researched
- Follow the existing structure and formatting
- Write in clear, accessible language
- Attribute any external sources or references
- Focus on practical, actionable guidance
- Consider the needs of both technical and non-technical readers
By participating in this project, you agree to abide by our Code of Conduct:
- Be welcoming and inclusive
- Be respectful of differing viewpoints
- Focus on what is best for the community
- Show empathy towards other community members
- Be collaborative and constructive in feedback
- Home
- Contributing
- 01 - Getting Started
- 02 - Understanding Business Risk
- 03 - Understanding the Adversary
- 04 - Mapping Attack Surface
- 05 - CIS18 and Basic Security Controls
- 06 - Security Architecture and Engineering
- 07 - Product and Software Security
- 08 - Secure Business Process Design
- 09 - Identity and Access Management
- 10 - Security Management
- 11 - Security Leadership
- 12 - Governance Risk and Compliance
- 13 - Security Awareness
- 14 - Security Operations - SOC
- 15 - Response - IR
- 16 - Business Continuity Planning - BCP
- 17 - Disaster Recovery - DR
- 18 - Vulnerability Management and Risk
- 19 - Frameworks and Standards
- 20 - Careers - The Road to CISO
- 21 - Cyber Insurance
- 22 - Resources