Cyber Discussions!

[GulfOfAmerica]

🌟 Welcome! We’re using Discussions as a place to connect with other members of our community.

• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we build together! 💪To get started, comment below with an introduction of yourself and tell us about what you do with this community.--

I'm a cybersecurity student pursuing a bachelor’s degree, with hands-on experience in penetration testing. I’m passionate about building tools to strengthen cybersecurity, inspired by my work with Kali Linux, Python scripting, and bug bounty programs like Visa’s. Recently, I’ve been exploring the CVE ecosystem, and I’m excited to contribute to the MITRE-Cyber-Security-CVE-Database organization.

My Project: HackinSacks CVE ManagementI’m starting an open-source project called "HackinSacks CVE Management" to address gaps in vulnerability management, especially with the recent funding uncertainties around the CVE program (extended by CISA for 11 months as of April 16, 2025). My goal is to:

• Develop a community-driven tool to aggregate and prioritize CVE data from public sources.
• Create an accessible platform for students, small businesses, and pentesters to leverage vulnerability insights.
• Eventually explore becoming a CVE Numbering Authority (CNA) to contribute directly to the ecosystem.I’ve already forked repos like cvelist and cve-reference-ingest and created 11 repositories under my GitHub profile. My initial prototype is a Python script to fetch and filter CVE data—check it out here!

How You Can HelpI’d love your input! Whether you’re a developer, researcher, or security pro, here’s how you can get involved:

• Code Contributions: Help enhance the script or add features like severity scoring.
• Feedback: Share ideas on what the community needs from a CVE tool.
• Testing: Try the prototype and report bugs or suggestions.

Let’s build this together—drop a comment to introduce yourself or share your thoughts!
🚀

---

For the maintainers, here are some tips 🎯 for getting started with Discussions. We’ll leave these in Markdown for now, but feel free to take out the comments for all maintainers to see.

• "Announce to your community" that Discussions is available! Go ahead and send that tweet, post, or link it from the website to drive traffic here.
• If you use issue templates, link any relevant issue templates such as questions and community conversations to Discussions.
• You can convert issues to discussions either individually or by labels. Looking at you, issues labeled "question" or "discussion".