Build to Break: Your Guide to Cybersecurity at Hacktoberfest HackDay x OWASP JIS Univerity

OWASP × Hacktoberfest Cybersecurity Track Build. Break. Secure. Build a project that solves a real cybersecurity problem. Your project can focus on application security, cloud security, AI security, authentication, supply-chain security, detection and response, DevSecOps, or another security challenge. You don't need to build a complete enterprise security platform. Pick one meaningful problem, build a focused solution, and demonstrate that it works. What Can You Build? Here are some areas to explore: Web & API Security - API authorization tester - IDOR/BOLA detector - Web vulnerability scanner - Secure API gateway - Authentication security tool Cloud Security - IAM privilege-escalation analyzer - Cloud misconfiguration scanner - Cloud attack-path visualizer - Exposed credential detector - Cloud security monitoring tool AI Security - Prompt-injection detector - LLM security testing tool - AI data-leakage detector - Secure AI-agent permission layer - AI-generated code security analyzer DevSecOps & Supply Chain - CI/CD security gate - Secret detection and remediation tool - Dependency/SBOM risk analyzer - Container security scanner - Infrastructure-as-Code security analyzer Detection & Response - Security-log correlation tool - Attack-chain reconstruction - Threat-intelligence enrichment tool - Security alert triage system - Automated incident-response assistant These are starting points, not restrictions. If you have a different cybersecurity idea, build it. How to Approach Your Project A simple way to structure a cybersecurity project is: ┌──────────────┐ │ Problem │ └──────┬───────┘ ↓ ┌──────────────┐ │ Attack │ └──────┬───────┘ ↓ ┌──────────────┐ │Security │ │Control │ └──────┬───────┘ ↓ ┌──────────────┐ │ Demonstrate │ │ & Test │ └──────────────┘ 1. Define the Problem Ask: What are you trying to protect, and what are you protecting it from? For example: Problem: Exposed API credentials can be used to access sensitive resources. Attacker: Someone who obtains a leaked credential. Impact: Unauthorized access to data or services. 2. Understand the Attack Before building the solution, understand how the attack actually happens. Think about: Attacker → Attack Vector → Vulnerability/Weakness → Impact For example: Attacker │ ▼ Stolen API Key │ ▼ Unauthorized API Access │ ▼ Sensitive Data Exposure Your project should intervene somewhere in this attack path. 3. Build the Security Control Your project should do something about the security problem. For example: Source Code │ ▼ Secret Scanner │ ▼ Credential Detected │ ▼ Alert / Block Commit Or: IAM Policy │ ▼ Permission Analysis │ ▼ Privilege Escalation Path │ ▼ Finding + Remediation Or: Security Logs │ ▼ Detection Engine │ ▼ Suspicious Activity │ ▼ Alert / Investigation The goal isn't to have the most features. A focused security control that works is more valuable than a large collection of unfinished features. Using AI in Your Security Project If you're using Gemma or another open-source/open-weight model, give the model a meaningful role in your system. For example: Security Detection │ ▼ Gemma │ ▼ Explanation / Correlation │ ▼ Remediation Recommendation Good uses for AI include: - Explaining security findings - Correlating security events - Summarizing incidents - Classifying security data - Extracting threat intelligence - Suggesting remediation - Providing a natural-language interface to security tooling Be careful with AI-generated actions Treat model output as untrusted input, especially if it generates: - SQL - Shell commands - IAM policies - Kubernetes configurations - Code - API requests Prefer: AI Output │ ▼ Validation │ ▼ Controlled Action rather than: AI Output │ ▼ Production Test Your Project Like an Attacker Don't only demonstrate the happy path. Try to break your own system. At minimum, test: - Normal input - Malicious input - Invalid input - Unexpected input - Edge cases For example: Prompt-injection defense Normal Prompt ↓ Works Malicious Prompt ↓ Injection Detected ↓ Blocked IAM Security Tool Vulnerable Policy ↓ Privilege Escalation ↓ Detected ↓ Remediation Suggested Secret Detection Leaked Credential ↓ Detected ↓ Commit Blocked ↓ Developer Alerted Prove That It Works A cybersecurity project should be demonstrated with an actual security scenario. A simple structure is: Attack → Detection/Prevention → Result Don't just show a dashboard and say: "Our system detects attacks." Show the attack. Show what your system detects or prevents. Show the result. Keep Your Claims Realistic Avoid making claims that you cannot demonstrate. Instead of: "Our system completely prevents phishing." Explain what your system actually does: "Our system detects suspicious websites using URL, DOM and visual features." Instead of: "Our AI guarantees secure code." Say: "Our AI identifies potential security issues and suggests remediation." If you report metrics such as accuracy, explain how you measured them. For example: - What dataset did you use? - How many test cases? - How many attacks were detected? - How many false positives? - How many false negatives? Useful Resources OWASP OWASP Top 10:2025 A starting point for understanding common application-security risks and finding project ideas. OWASP Top 10 for LLM Applications Useful for projects involving LLMs, GenAI, AI agents, or open-source models. OWASP Cheat Sheet Series Practical implementation guidance for common security topics. OWASP API Security Top 10 Useful if your project involves APIs, authentication, authorization, or access control. OWASP Web Security Testing Guide Use this to test your web application before submission. Need More Project Ideas? OWASP GSoC Project Ideas Explore real OWASP open-source projects and technical problem areas for additional inspiration. OWASP Project Directory Browse existing OWASP projects across application security, AI security, cloud security, tooling, and more. These are provided for inspiration and further exploration. You do not need to contribute to an existing OWASP project for the Hackday. Final Checklist Before submitting, ask yourself: - [ ] What security problem am I solving? - [ ] Who is the attacker? - [ ] How does the attack work? - [ ] What does my project detect, prevent, or mitigate? - [ ] Can I demonstrate the attack? - [ ] Can I demonstrate my security control working? - [ ] Have I tested malicious and unexpected inputs? - [ ] Are my security/AI claims supported by evidence? - [ ] If I use AI, is it actually contributing something meaningful? - [ ] Can another person understand and reproduce my project? The Basic Formula Problem → Attack → Security Control → Test → Result You don't need to build the next enterprise security platform. Pick one real security problem. Understand it. Build a focused solution. Try to break it. Then demonstrate that your solution works. Top comments (0)