Knowledge systems
Structured guides, reference works, release-governed learning resources, and practitioner material designed to remain useful beyond a single post or event.
- Cyber Master Series
- Certification Study Series
- Conference resources
Projects · Research · Open Source
Build in public. Make it useful.
I turn cybersecurity knowledge into inspectable work: learning systems, research, utilities, release tooling, conference resources, and community infrastructure that practitioners can use, question, and improve.
400+Public GitHub repositories
6Selected public projects
3Cyber Master Series pillars
OpenIssues, corrections & collaboration
The public-work model
Code is one output. Capability is the goal.
The portfolio connects technical artifacts with learning, assurance, professional practice, and community benefit.
Research & technical artifacts
Security research, proof-of-concept work, technical notes, write-ups, utilities, and small tools that make a security concept inspectable or repeatable.
- CVE research
- Security utilities
- Technical write-ups
Practitioner tooling
Tools that improve the quality of operational work: release assurance, repository hygiene, diagnostics, prioritization, evidence, and repeatable decision support.
- Release Sentry
- Quality gates
- Decision-support utilities
Community infrastructure
Public repositories and reusable assets that support chapters, learners, practitioners, events, and collaborative security knowledge.
- OWASP Algiers
- Open corrections
- Community materials
Public now
Selected projects with a real release trail.
A curated view of shipped or publicly accessible work. Every card links directly to its repository or maintained public home.
01
Knowledge systemActive ecosystem
Cyber Master Series — Certification Guides
Free, version-aware certification study resources built from official objectives, authoritative references, practical context, community corrections, and controlled releases.
Interactive editions, downloadable PDFs, public corrections, and transparent release governance.- CCSP 2026.2
- ISC2 CC
- Learning
- Documentation
FeaturedOpen repository ↗
02
Developer security toolv1.0.0 released
Release Sentry
A release-readiness and repository-hygiene tool designed to detect packaging mistakes, exposed internal files, version drift, and avoidable defects before a public release ships.
A practical quality gate for safer, cleaner, and more intentional releases.- Release assurance
- Repository hygiene
- Automation
- Open source
FeaturedExplore Release Sentry ↗
03
Speaking resourcesPublic archive
Conferences
Selected slides, workshops, demonstrations, and supporting materials from public cybersecurity talks and technical learning sessions.
Extends the value of a live session into reusable professional and community material.- Slides
- Workshops
- Cybersecurity
- Knowledge sharing
04
Vulnerability researchPublished research
CVE-2018-10583
Security research and proof-of-concept work concerning information disclosure through automatically initiated SMB connections in affected document-processing software.
Documents the weakness, affected behavior, and reproducible research context for defenders and researchers.- CVE
- PoC
- Information disclosure
- Python
05
Security utilityPublic utility
Strong Password Generator
A lightweight Python utility for generating strong passwords, preserved as a simple and accessible example of practical defensive scripting.
A focused utility that demonstrates small, understandable security automation.- Python
- Password security
- Utility
- Beginner friendly
06
Open communityCommunity infrastructure
OWASP Algiers Chapter Repository
Public chapter infrastructure supporting OWASP Algiers, community communication, local activities, and accessible application-security knowledge sharing.
Connects open-source practice with local community leadership and sustained public contribution.- OWASP
- Community
- Application security
- Algiers
Publishing principles
Open work should earn professional trust.
Security resources become credible when their purpose, limits, sources, status, and maintenance expectations are visible.
- 01
Useful before promotional
A public project should solve a real problem, clarify a difficult subject, or save practitioners meaningful effort.
- 02
Transparent about status
Released, active, archived, experimental, and planned work are identified clearly. A roadmap is not presented as a finished product.
- 03
Defensible by design
Sources, assumptions, limitations, versions, and intended use should be understandable to the people who rely on the work.
- 04
Open to correction
Issues, feedback, and responsible contributions are part of improving public security knowledge—not a threat to authority.
Active roadmap
What is being developed—clearly labelled.
These are active directions, not finished products. Public links appear only when a usable release is ready.
Cyber Master Series
Additional certification guides, professional books, and practitioner toolkits—released only when each asset reaches its own quality gate.
Roadmap — not yet a released deliverable
Security decision tools
Privacy-aware diagnostics and prioritization utilities across vulnerability management, resilience, GRC, SecOps, and incident readiness.
Roadmap — not yet a released deliverable
Applied field resources
Reusable templates, checklists, mappings, workshop artifacts, and implementation aids grounded in real practitioner workflows.
Roadmap — not yet a released deliverable
Contribute · Collaborate · Build
Found something to improve—or something worth building together?
Open an issue for project-specific feedback, explore the repositories, or start a conversation about cybersecurity research, practitioner tools, learning resources, and useful community work.