From 960ea0dbc8716885f0f9ad177d74d137328cbe8e Mon Sep 17 00:00:00 2001 From: Lukas Rist Date: Mon, 23 Dec 2024 22:32:39 +0100 Subject: [PATCH 1/2] initial gsoc 2025 pages --- content/gsoc/_index.md | 4 +- content/gsoc/faq.md | 4 +- content/gsoc/gsoc-2025/_index.md | 69 +++++++++++++++++++ content/gsoc/gsoc-2025/application.md | 32 +++++++++ content/gsoc/gsoc-2025/ideas.md | 34 +++++++++ content/gsoc/gsoc-2025/ideas/artemis.md | 19 +++++ .../gsoc/gsoc-2025/ideas/drakvuf-sandbox.md | 20 ++++++ content/gsoc/gsoc-2025/ideas/drakvuf.md | 14 ++++ content/gsoc/gsoc-2025/ideas/honeyscanner.md | 14 ++++ content/gsoc/gsoc-2025/ideas/intelowl2.md | 17 +++++ content/gsoc/gsoc-2025/ideas/intelowl3.md | 18 +++++ content/gsoc/gsoc-2025/ideas/intelowl4.md | 18 +++++ .../gsoc/gsoc-2025/ideas/intelowlproject.md | 18 +++++ content/gsoc/gsoc-2025/ideas/mitmproxy.md | 14 ++++ content/gsoc/gsoc-2025/ideas/riotpot.md | 12 ++++ content/gsoc/gsoc-2025/ideas/tanner.md | 17 +++++ hugo.toml | 5 ++ 17 files changed, 325 insertions(+), 4 deletions(-) create mode 100644 content/gsoc/gsoc-2025/_index.md create mode 100644 content/gsoc/gsoc-2025/application.md create mode 100644 content/gsoc/gsoc-2025/ideas.md create mode 100644 content/gsoc/gsoc-2025/ideas/artemis.md create mode 100644 content/gsoc/gsoc-2025/ideas/drakvuf-sandbox.md create mode 100644 content/gsoc/gsoc-2025/ideas/drakvuf.md create mode 100644 content/gsoc/gsoc-2025/ideas/honeyscanner.md create mode 100644 content/gsoc/gsoc-2025/ideas/intelowl2.md create mode 100644 content/gsoc/gsoc-2025/ideas/intelowl3.md create mode 100644 content/gsoc/gsoc-2025/ideas/intelowl4.md create mode 100644 content/gsoc/gsoc-2025/ideas/intelowlproject.md create mode 100644 content/gsoc/gsoc-2025/ideas/mitmproxy.md create mode 100644 content/gsoc/gsoc-2025/ideas/riotpot.md create mode 100644 content/gsoc/gsoc-2025/ideas/tanner.md diff --git a/content/gsoc/_index.md b/content/gsoc/_index.md index b842bf8..cabac56 100644 --- a/content/gsoc/_index.md +++ b/content/gsoc/_index.md @@ -2,7 +2,7 @@ title: "Google Summer of Code" --- -The Honeynet Project has participated 15 times in the Google Summer of Code. Throughout the years, it has been an important and successful event for the organization. Many former GSoC students have become successful contributors, GSoC mentors and admins themselves. Every year Google Summer of Code provides a breeze of fresh air into the Honeynet Project, motivating students, mentors and organization members alike. +The Honeynet Project has participated 16 times in the Google Summer of Code. Throughout the years, it has been an important and successful event for the organization. Many former GSoC students have become successful contributors, GSoC mentors and admins themselves. Every year Google Summer of Code provides a breeze of fresh air into the Honeynet Project, motivating students, mentors and organization members alike. Every year we are trying to gather as many successful students as possible at our in-person workshop to provide an opportunity for the students to present their work, meet their mentors and many members of the organization. @@ -16,4 +16,4 @@ We have compiled a list of [frequently asked question]({{< ref "gsoc/faq.md" >}} ### Contacting Us -If you have any questions, please drop by in our [Discord](https://discord.gg/68B8Ru5fSU) and say "hi" (note that our members do have to sleep and come from timezones all over the world, so please be patient and wait a few hours if you have a specific question). \ No newline at end of file +If you have any questions, please drop by in our [Discord](https://discord.gg/68B8Ru5fSU) and say "hi" (note that our members do have to sleep and come from timezones all over the world, so please be patient and wait a few hours if you have a specific question). diff --git a/content/gsoc/faq.md b/content/gsoc/faq.md index 92a23b3..ba4f8d8 100644 --- a/content/gsoc/faq.md +++ b/content/gsoc/faq.md @@ -3,10 +3,10 @@ title: "Frequently Asked Questions" --- - **Where can I find the list of project ideas for this year?** -Our project ideas can be found [here](https://www.honeynet.org/gsoc/gsoc-2024/google-summer-of-code-2024-project-ideas/) +Our project ideas can be found [here](https://www.honeynet.org/gsoc/gsoc-2025/google-summer-of-code-2025-project-ideas/) - **How do I get started?** -Read through the list of [ideas](https://www.honeynet.org/gsoc/gsoc-2024/google-summer-of-code-2024-project-ideas/) and identify the project ideas you find interesting. Play around with our tools! Install the project, use it. Have a look at the issue tracker. +Read through the list of [ideas](https://www.honeynet.org/gsoc/gsoc-2025/google-summer-of-code-2025-project-ideas/) and identify the project ideas you find interesting. Play around with our tools! Install the project, use it. Have a look at the issue tracker. - **How do I start contributing to a project?** Often projects have issues tagged which are considered good starting points. Updating documentation is often a low barrier start and gets you familiar with the process of contributing to an open source project. diff --git a/content/gsoc/gsoc-2025/_index.md b/content/gsoc/gsoc-2025/_index.md new file mode 100644 index 0000000..8c1a608 --- /dev/null +++ b/content/gsoc/gsoc-2025/_index.md @@ -0,0 +1,69 @@ +--- +title: "GSoC 2025" +date: "2024-12-23" +--- + + +* * * + +### We are applying again as a mentor organization for GSoC in 2025 + +This will be the 16th time that Honeynet is participating in the Google Summer of Code program to accelerate the creation of information- and cyber security related tools that are free and open source software. Thank you to all mentors who submitted their project ideas and will volunteer as mentors throughout the summer. + +On this page you will learn more about GSoC 2025 and our efforts on developing and improving our projects. + +### Project Ideas + +- [GSoC 2025 Project Ideas](google-summer-of-code-2025-project-ideas) + +Often students ask us what kind of projects we are likely to be offering in a coming year. If you want to get an idea of the kind of projects ideas we proposed and the accepted projects we ran during GSoC 2009-2024, you can view these here: + +- [GSoC 2024 Project Ideas](/gsoc/gsoc-2024/google-summer-of-code-2024-project-ideas/) +- [GSoC 2023 Project Ideas](/gsoc/gsoc-2023/google-summer-of-code-2023-project-ideas/) +- [GSoC 2022 Project Ideas](/gsoc/gsoc-2022/google-summer-of-code-2022-project-ideas/) +- [GSoC 2021 Project Ideas](/gsoc/gsoc-2021/google-summer-of-code-2021-project-ideas/) +- [GSoC 2020 Project Ideas](/gsoc/gsoc-2020/google-summer-of-code-2020-project-ideas/) +- [GSoC 2018 Project Ideas](/gsoc/gsoc-2018/google-summer-of-code-2018-project-ideas/) +- [GSoC 2017 Project Ideas](/gsoc/gsoc-2017/google-summer-of-code-2017-project-ideas/) +- [GSoC 2016 Project Ideas](/gsoc/gsoc-2016/google-summer-of-code-2016-project-ideas/) +- [GSoC 2015 Project Ideas](/gsoc/gsoc-2015/google-summer-of-code-2015-project-ideas/) +- [GSoC 2014 Project Ideas](/gsoc/gsoc-2014/google-summer-of-code-2014-project-ideas/) +- [GSoC 2013 Project Ideas](/gsoc/gsoc-2013/google-summer-of-code-2013-project-ideas/) +- [GSoC 2012 Project Ideas](/gsoc/gsoc-2012/google-summer-of-code-2012-project-ideas/) +- [GSoC 2011 Project Ideas](/gsoc/gsoc-2011/google-summer-of-code-2011-project-ideas/) +- [GSoC 2010 Project Ideas](/gsoc/gsoc-2010/google-summer-of-code-2010-project-ideas/) +- [GSoC 2009 Project Ideas](/gsoc/gsoc-2009/google-summer-of-code-2009-project-ideas/) + +### Contacting Us + +If you have any questions, please drop by in our [Discord](https://discord.gg/68B8Ru5fSU) and say "hi" (note that our members do have to sleep and come from timezones all over the world, so please be patient and wait a few hours if you have a specific question). + +### Organizational Administrators + +Our GSoC 2025 organizational administrators this year are: + +- Lukas Rist (lead) +- Maximilian Hils +- Emmanouil Vasilomano + +### Why get involved with the Honeynet Project? + +1. We are an enthusiastic and passionate group of volunteers dedicated to the ideals of open source and sharing our security research and development knowledge with the community +2. For over ten years, we have pioneered research in the field of honeypots, releasing many freely available [tools](/projects), [challenges](/challenges) and [Know Your Enemy whitepapers](/papers) that are often considered groundbreaking when first published +3. We wrote the book on the topic, and regularly present on our R&D activities at conferences all over the world +4. We have active volunteer member chapters in many countries and from many different backgrounds, with a wide variety of skills and experience they are happy to share +5. We have always been committed to the concepts of open source software and freely share everything we do, including each chapter publishing regular status reports on their recent activity +6. We maintain active public and private communities of developers and researchers who use and contribute to our tools each day +7. We provide our members and the community with the public and private infrastructure necessary to support distributed collaborative remote working, such as IRC channels, mailing lists, subversion repositories, Trac instances for ticket management and wikis, content management systems, blogs, live deployments with real end users for testing and regular feedback, etc. +8. We are hands on, supportive and keen to involve more talented people in projects we are really passionate about +9. We have a strong track history of mentoring new members and successfully delivering open source projects, tools and research that demonstrably benefit the community +10. The vast majority of our GSoC projects were delivered successfully and our students were happy, with a number of the tools created going on to become widely used within the security community +11. Students from GSoC have gone on to become active members of the honeynet community, including proposing project ideas for future GSoCs or offering to be project mentors and organization administrators (so we can't be too unpleasant a bunch to get involved with!) +12. We have ex-GSoC students actively serving on our Board of Directors and in Executive Officer positions, so GSoC has definitely proven to be a great career path for students wanting to get more involved in open source and information security R&D. +13. Honeypots and honeynet technology, research and tools have filtered down benefits to many areas of IT, web development, operational service management, Internet education and computer security research + +### Other ways to get involved + +[GSoC](//summerofcode.withgoogle.com/) is not the only way you can become involved in the with honeynet technologies and open source software - check out our current series of [forensic challenges](/challenges). Or learn more about the practical, real world application of honeynet technology in our popular series of ["Know Your Enemy"](/papers) whitepapers. + +Feel free to contact us at on [Discord](https://discord.gg/68B8Ru5fSU) or at [project@honeynet.org](mailto:project@honeynet.org) at any time. diff --git a/content/gsoc/gsoc-2025/application.md b/content/gsoc/gsoc-2025/application.md new file mode 100644 index 0000000..cd4f142 --- /dev/null +++ b/content/gsoc/gsoc-2025/application.md @@ -0,0 +1,32 @@ +--- +title: "GSoC 2025 application template" +date: "2024-12-23" +--- + +These are the questions we require potential [Google Summer of Code](https://summerofcode.withgoogle.com/) participants to complete. **Please use [Google's official interface](https://summerofcode.withgoogle.com/) to submit both drafts for feedback and your final proposal.** You can always update your submission up until the deadline. Submission received by email, Discord, or through direct contact with a mentor will not count. + +Your Name: +Discord Username: +Email Address: +Nationality: +Primary Spoken Language: + +1. Top project choice (can be one of our project ideas or your own) +2. Are you willing and able to work on other projects instead? +3. Please describe you preferred coding languages and experience. +4. Please describe any Windows, Unix or Mac OS X development experience relevant to your chosen project. If your project does not require OS-specific expertise, feel free to leave it empty. +5. Please describe any previous usage with Honeynet Project tools or honeypots in general. +6. Please describe any previous Honeynet Project or honeypot related development experience, including details of any patches, code or ideas you may have previously submitted. +7. Please describe any previous open source development experience, including projects you have worked on. +8. What school do you attend and what is your specialty/major at the school? +9. How many years have you attended there? +10. What city/country will you be spending this summer in? +11. How much time do you expect to have for this project? +12. Please list all jobs, summer classes, vacations and/or other commitments that you'll need to work around. +13. Have you participated in any previous Summer of Code projects? If so please describe your projects and experience, including what you liked or didn't like about the experience +14. Have you applied for (or intend to apply for) any other Google Summer of Code 2022 projects? If so, which ones? +15. If you have a URL for your resume/CV, please list it here. +16. If you wish to list any personal/blog URLs, do so here. +17. Please describe your proposed project in detail, including deliverables and expected timeline with milestones (this is the long answer, so spend most time here!). +18. Why are you well suited to perform this project and why are you interested in it? +19. Have any of our members met you face to face, such as at one of our recent public events? If so, please list who/where. diff --git a/content/gsoc/gsoc-2025/ideas.md b/content/gsoc/gsoc-2025/ideas.md new file mode 100644 index 0000000..641592b --- /dev/null +++ b/content/gsoc/gsoc-2025/ideas.md @@ -0,0 +1,34 @@ +--- +title: "Google Summer of Code 2025 Project Ideas" +date: "2024-12-23" +url: "/gsoc/gsoc-2025/google-summer-of-code-2025-project-ideas" +type: "ideas" +--- +### Getting Started + +This page contains a list of potential project ideas that we are keen to develop during GSoC 2025. If you would like to apply as a GSoC student, please follow these two steps to get started: + +1. Read through this page and identify the project ideas you find interesting. Play around with our tools! +2. Join us on Discord and talk to your potential mentors on [Discord](https://discord.gg/68B8Ru5fSU) + +If there are any questions, please don’t hesitate and get in touch! 🙂 + +### GSoC and The Honeynet Project + +During the previous years of GSoC, the Honeynet Project's students have created a wide range of very successful open source security projects, many of which have gone on to become the industry standard open source tools in their respective fields. + +We are also always interested in hearing any ideas for additional relevant computer security and honeynet-related R&D projects (although remember that to qualify for receiving GSoC funding from Google your project deliverables need to fit in to [GSoC's project timescales](//developers.google.com/open-source/gsoc/faq)!). If you have a suitable and interesting project, we will always try and find the right resources to mentor it and support you. + +Please note - even if you aren't an [eligible GSoC participant](//developers.google.com/open-source/gsoc/faq), we are also always looking for general volunteers who are enthusiastic and interested in getting involved in honeynet R&D. + +Each sponsored GSoC 2025 project will have one or more mentors available to provide a guaranteed contact point to students, plus one or more technical advisors to help applicants with the technical direction and delivery of the project (often the original author of a tool or its current maintainer, and usually someone recognized as an international expert in their particular field). Our Google Summer of Code organizational administrators will also be available to all sponsored GSoC students for general advice and logistical support. We'll also provide hosting for project infrastructure, if required. + +For all questions about the Honeynet Project, the GSoC program or our projects, please contact us on [Discord](https://discord.gg/68B8Ru5fSU) (preferred)** or email us at [project@honeynet.org](mailto:project@honeynet.org). + +**Application template** + +If you are considering applying to participate with us in GSoC 2025 please find our [application template here]({{< ref "application.md" >}}). Use it when you are preparing your application on the official GSoC site and don't hesitate to ask your mentors for feedback before submitting! + +* * * + +# GSoC 2025 Project Ideas Overview diff --git a/content/gsoc/gsoc-2025/ideas/artemis.md b/content/gsoc/gsoc-2025/ideas/artemis.md new file mode 100644 index 0000000..4274eea --- /dev/null +++ b/content/gsoc/gsoc-2025/ideas/artemis.md @@ -0,0 +1,19 @@ +--- +title: "Extending the Artemis scanner" +date: "2024-12-23" +project_url: "https://github.com/CERT-Polska/Artemis" +hours: "175 or 350 hours" +mentor: "Krzysztof Zając" +project_type: "Improving an existing tool" +--- + +Artemis is a modular vulnerability scanner that checks various aspects of website security and builds easy-to-read messages to send to organizations to get the vulnerabilities fixed. +Multiple national-level CSIRTs use it to improve the security of their constituencies. + +The goal of this project is to: + +* research what existing tools to add to the Artemis scanning pipeline, +* extend Artemis with modules detecting different types of vulnerabilities, +* improve Artemis in other aspects: performance, UI, etc. + +The primary required skill is Python programming and a familiarity with the Linux environment. Skill with web security topics is also desired. diff --git a/content/gsoc/gsoc-2025/ideas/drakvuf-sandbox.md b/content/gsoc/gsoc-2025/ideas/drakvuf-sandbox.md new file mode 100644 index 0000000..29a9bd3 --- /dev/null +++ b/content/gsoc/gsoc-2025/ideas/drakvuf-sandbox.md @@ -0,0 +1,20 @@ +--- +title: "Extending the DRAKVUF Sandbox analytic pipeline" +date: "2024-12-23" +project_url: "https://github.com/CERT-Polska/drakvuf-sandbox/" +hours: "175 or 350 hours" +mentor: "Jarosław Jedynak" +project_type: "Improving an existing tool" +--- + +DRAKVUF Sandbox is an open source automated black-box malware analysis system using virtual machine introspection (VMI) with DRAKVUF (https://drakvuf.com) engine under the hood. + +As DRAKVUF Sandbox monitors behavior of malware samples it collects a lot of detailed data, like API calls, syscalls, network traffic, etc., however despite this vast amount of information, most of it is not exposed directly to the first-line operators and analysts using the sandbox. + +The goal of this project is to: + +* extend DRAKVUF Sandbox with useful heuristics for detecting the most common malware types and behaviours +* detect typical malicious patterns like code injection, and create a behaviour graph that can be easily grokked by the analysts (currently a subset of this feature is provided by a thirdparty project proc2dot) +* improve the integration of DRAKVUF Sandbox with the rest of the analytic pipeline. This will make it possible to display the analysis results more directly in other tools + +Primary required skill is Python programming and a familiarity with Linux environment. Knowledge of how OS works under the hood and other low-level topics is also very desired. Skill with malware analysis or IT security topics is nice to have, but absolutely not necessary - we will help with any malware-specific design issues. diff --git a/content/gsoc/gsoc-2025/ideas/drakvuf.md b/content/gsoc/gsoc-2025/ideas/drakvuf.md new file mode 100644 index 0000000..57b99fc --- /dev/null +++ b/content/gsoc/gsoc-2025/ideas/drakvuf.md @@ -0,0 +1,14 @@ +--- +title: "DRAKVUF Rust & Python bindings" +date: "2024-12-23" +project_url: "https://github.com/tklengyel/drakvuf" +hours: "90, 175 or 350 hours" +mentor: "Tamas Lengyel" +project_type: "Improving an existing tool" +--- + +DRAKVUF is a hypervisor-based malware analysis system written in mostly C & C++. It is designed to be high performant and stealthy, so malware won't be able to detect the analysis tools. + +This project will focus on creating automatic Rust & Python binding generators for the core DRAKVUF libraries (libdrakvuf & libinjector). The goal is to automate the binding generation process, so future changes to the core library APIs will get automatically adjusted in the respective language bindings. Test-cases will need to be created and added to the CI to ensure the bindings remain operational. + +The ideal candidate for this project should be at least on an intermediate level in either C, C++, Python or Rust, and will be willing to learn the others on the go. diff --git a/content/gsoc/gsoc-2025/ideas/honeyscanner.md b/content/gsoc/gsoc-2025/ideas/honeyscanner.md new file mode 100644 index 0000000..bde7f7c --- /dev/null +++ b/content/gsoc/gsoc-2025/ideas/honeyscanner.md @@ -0,0 +1,14 @@ +--- +title: "Improving the functionality of Honeyscanner: a honeypot vulnerability analyzer" +date: "2024-12-23" +project_url: "https://github.com/honeynet/honeyscanner" +hours: "90, 175 or 350 hours" +mentor: "Emmanouil Vasilomanolakis, Ricardo Yaben and Shreyas Srinivasa" +project_type: "Improving an existing tool" +--- + +Honeyscanner is a vulnerability analyzer for honeypots designed to automatically attack a given honeypot, in order to determine if the honeypot is vulnerable to specific types of cyber attacks. + +Honeyscanner uses a variety of attacks, ranging from exploiting vulnerable software libraries to DoS, and fuzzing attacks. The analyzer then provides an evaluation report to the honeypot administrator, offering advice on how to enhance the security of the honeypot. Targeted toward security enthusiasts, open-source communities, and companies, Honeyscanner provides a much needed safety check for various honeypots. + +This project aims at improving the code base, add new attacks to the Honeyscanner arsenal, as well as add support for more honeypots. diff --git a/content/gsoc/gsoc-2025/ideas/intelowl2.md b/content/gsoc/gsoc-2025/ideas/intelowl2.md new file mode 100644 index 0000000..fcf6f17 --- /dev/null +++ b/content/gsoc/gsoc-2025/ideas/intelowl2.md @@ -0,0 +1,17 @@ +--- +title: "New Documentation Site for IntelOwl and friends" +date: "2024-12-23" +project_url: "https://github.com/intelowlproject" +hours: "175" +mentor: "Matteo Lodi, Daniele Rosetti" +project_type: "Improving an existing tool" +--- + +Right now we are not satisfied of how we manage our documentation and how we make it available. + +The project aims to create a new repository dedicated to the documentation, move all the documentation of all our projects there and build a new documentation site by leveraging Github Pages and MkDocs. + +More information in this [Github Issue](https://github.com/intelowlproject/IntelOwl/issues/2043) + +The candidate would have the chance to try some popular tools and to solve a big common problem that a lot of other Open Source projects have. +The ideal candidate is proactive in reading documentation of new tools and excited in trying them to solve our problem. diff --git a/content/gsoc/gsoc-2025/ideas/intelowl3.md b/content/gsoc/gsoc-2025/ideas/intelowl3.md new file mode 100644 index 0000000..910907d --- /dev/null +++ b/content/gsoc/gsoc-2025/ideas/intelowl3.md @@ -0,0 +1,18 @@ +--- +title: "Scanners: a new plugin type for IntelOwl" +date: "2024-12-23" +project_url: "https://github.com/intelowlproject" +hours: "175" +mentor: "Matteo Lodi, Daniele Rosetti, Simone Berni" +project_type: "Improving an existing tool" +--- + +Right now there are many possible types of [plugins](https://intelowl.readthedocs.io/en/latest/Usage.html#plugins) in IntelOwl. + +This project aims to add a new plugin type to the already existing ones in IntelOwl: +* The **"Scanner"** type would be a subtype of the “[Analyzers](https://intelowl.readthedocs.io/en/latest/Usage.html#analyzers)” ones with special configuration. In that way, IntelOwl could be used not only for classic data enrichment with external services but as either a vulnerability scanner or a scraper too. Refer to the [Github Issue for more details](https://github.com/intelowlproject/IntelOwl/issues/1393) + +Like we have similarly done with other GSoC projects in the past that added new plugin types, we expect the contributor to add the most important new scanners (like [this](https://github.com/intelowlproject/IntelOwl/issues/1021)) to IntelOwl once he finishes building the framework to provide a base of tools which can be used by the users. + +The candidate would have the chance to work through all the application stack (backend and frontend). +The ideal candidate for this project is someone who is familiar with how IntelOwl works and its core concepts. diff --git a/content/gsoc/gsoc-2025/ideas/intelowl4.md b/content/gsoc/gsoc-2025/ideas/intelowl4.md new file mode 100644 index 0000000..96008fa --- /dev/null +++ b/content/gsoc/gsoc-2025/ideas/intelowl4.md @@ -0,0 +1,18 @@ +--- +title: "New Analyzers for IntelOwl" +date: "2024-12-23" +project_url: "https://github.com/intelowlproject" +hours: "175" +mentor: "Matteo Lodi, Daniele Rosetti, Simone Berni" +project_type: "Improving an existing tool" +--- + +Right now we have a lot of [Analyzers](https://intelowl.readthedocs.io/en/latest/Usage.html#analyzers) implemented in IntelOwl. + +But they are not enough! They are the core part of the application so we want to add even more of them!!!! :) + +This project aims to increment the number of available Analyzers. We have about [50 different Analyzers that has been requested by the community members in Github](https://github.com/intelowlproject/IntelOwl/issues?q=is%3Aissue+is%3Aopen+label%3Anew_analyzer+) and are still not implemented. We obviously do not ask to implement all of them but a reasonable amount of them based on the available time and the efforts required for each of them. + +Adding a new Analyzer to the framework is one of the easiest things that can be done in this project. Once you get used to it, adding more of them is even easier! + +The ideal candidate for this project is someone who understand how IntelOwl's framework works and already tried to implement an Analyzer. diff --git a/content/gsoc/gsoc-2025/ideas/intelowlproject.md b/content/gsoc/gsoc-2025/ideas/intelowlproject.md new file mode 100644 index 0000000..f240e4d --- /dev/null +++ b/content/gsoc/gsoc-2025/ideas/intelowlproject.md @@ -0,0 +1,18 @@ +--- +title: "IntelChat: Enhancing Threat Analysis with an LLM-Based Chatbot in IntelOwl" +date: "2024-12-23" +project_url: "https://github.com/intelowlproject" +hours: "350" +mentor: "Hugo Gascón, Matteo Lodi" +project_type: "Improving an existing tool" +--- + +1. The proposed Google Summer of Code project aims to integrate a cutting-edge, self-deployed LLM-based chatbot into IntelOwl, enhancing user interaction with collected threat intelligence. + +2. Leveraging Python libraries like LangChain and ChainLit, the project envisions building an intuitive interface that empowers analysts to pose natural language queries about threat data, fostering a more user-friendly and efficient investigative process (e.g. "In what campaigns have you seen this IOC?”) + +3. The chatbot's capabilities will extend beyond basic queries, seamlessly interfacing with IntelOwl's enrichment modules when deeper investigation is required, providing a comprehensive and interactive experience for analysts. + +4. By harnessing the power of LLM technology, the chatbot will not only streamline communication between analysts and the IntelOwl platform but also adapt to evolving user needs, contributing to a more dynamic and responsive threat intelligence environment. + +5. This project aligns with the overarching goal of making threat analysis more accessible and efficient, offering analysts a powerful tool that combines the strengths of natural language understanding, self-deployment, and seamless integration with IntelOwl's existing modules. diff --git a/content/gsoc/gsoc-2025/ideas/mitmproxy.md b/content/gsoc/gsoc-2025/ideas/mitmproxy.md new file mode 100644 index 0000000..a4f8a4a --- /dev/null +++ b/content/gsoc/gsoc-2025/ideas/mitmproxy.md @@ -0,0 +1,14 @@ +--- +title: "Hack on Mitmproxy!" +date: "2024-12-23" +project_url: "https://mitmproxy.org" +hours: "90, 175 or 350 hours" +mentor: "Maximilian Hils" +project_type: "Improving an existing tool" +--- + +mitmproxy is your swiss-army knife for debugging, testing, privacy measurements, and penetration testing. It can be used to intercept, inspect, modify and replay web traffic such as HTTP/1, HTTP/2, HTTP/3, WebSockets, DNS, UDP, or any other SSL/TLS-protected protocols. You can prettify and decode a variety of message types ranging from HTML to Protobuf, intercept specific messages on-the-fly, modify them before they reach their destination, and replay them to a client or server later on. + +mitmproxy is a large project with a huge number of interesting areas to explore, down from low-level protocol work up to UX improvements. If you are motivated and know what you’re interested in, why not get in touch with us and map out a custom GSoC project? Below are some ideas – an enterprising student should be able to complete one large or 3 or more small tasks in a large size GSoC project. + +Potential Tasks: https://github.com/mitmproxy/mitmproxy/issues/6589 diff --git a/content/gsoc/gsoc-2025/ideas/riotpot.md b/content/gsoc/gsoc-2025/ideas/riotpot.md new file mode 100644 index 0000000..fda2c60 --- /dev/null +++ b/content/gsoc/gsoc-2025/ideas/riotpot.md @@ -0,0 +1,12 @@ +--- +title: "Improving the RioTPot hybrid interaction honeypot" +date: "2024-12-23" +project_url: "https://github.com/honeynet/riotpot" +hours: "90, 175 or 350 hours" +mentor: "Emmanouil Vasilomanolakis, Ricardo Yaben and Shreyas Srinivasa" +project_type: "Improving an existing tool" +--- + +RIoTPot is a hybrid interaction honeypot, primarily focused on the emulation IoT and OT protocols, although, it is also capable of emulating other services. In essence, RIoTPot acts as a proxy service for other honeypots included in the system. Therefore, you can run any honeypot and other services alongside RIoTPot. In addition, there is an UI web-application that you can use to manage your routing. Moreover, RIoTPot comes with multiple low-interaction services ready to use. Since these services are written as plugins, they are only supported on Linux; however, you can start RIoTPot without them. The following table contains the list of services included in RIoTPot by default, their internal port, and proxy port. + +The project aims at providing RioTPot with the ability to run in a light mode that requires minimum user interaction and minimize existing external library utilization. Furthermore, we will improve the support for existing profiles and protocols. diff --git a/content/gsoc/gsoc-2025/ideas/tanner.md b/content/gsoc/gsoc-2025/ideas/tanner.md new file mode 100644 index 0000000..7b64619 --- /dev/null +++ b/content/gsoc/gsoc-2025/ideas/tanner.md @@ -0,0 +1,17 @@ +--- +title: "ML-based Web-attack Classification for TANNER" +date: "2024-12-23" +project_url: "https://github.com/mushorg/tanner" +hours: "175 or 350 hours" +mentor: "Evgeniia Tokarchuk" +project_type: "Improving an existing tool" +--- + +The project aims to enhance the efficiency and accuracy of web attack detection in TANNER by replacing detection based on regular expressions with machine learning methods. The project will be divided into two main parts: + +1. Research of existing solutions and/or data collection +2. Integration of the ML classifier into TANNER + +Over the past few years, we have collected data from various SNARE sensors. This data is annotated using regular expressions and can be used for building a data-driven classification model of web-based attacks. However, since this data is noisy and imbalanced, it requires careful pre-processing and filtering. Moreover, curating the test set is essential to build a robust, high-quality model. External datasets can be used along with historical data from TANNER to enlarge the dataset and mitigate the noise. The resulting ML model must have accuracy above the regexp baseline and low latency to enable real-time analysis of the TANNER events. + +Requirements: python3, machine learning diff --git a/hugo.toml b/hugo.toml index 43d13ad..4553232 100644 --- a/hugo.toml +++ b/hugo.toml @@ -80,6 +80,11 @@ baseName = "../feed/index" parent = 'GSoC' pageRef = '/gsoc' weight = 10 +[[menu.main]] + parent = 'GSoC' + name = 'GSoC 2025' + pageRef = '/gsoc/gsoc-2025' + weight = 18 [[menu.main]] parent = 'GSoC' name = 'GSoC 2024' From eb6df80acf2ad79836b85aeea20cfa632fc989e1 Mon Sep 17 00:00:00 2001 From: Muhammad Bilal Arif Date: Sat, 11 Jan 2025 16:26:57 -0800 Subject: [PATCH 2/2] Glutton GSoC 2025 Project (#80) --- content/gsoc/gsoc-2025/ideas/Glutton.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 content/gsoc/gsoc-2025/ideas/Glutton.md diff --git a/content/gsoc/gsoc-2025/ideas/Glutton.md b/content/gsoc/gsoc-2025/ideas/Glutton.md new file mode 100644 index 0000000..b4bdf5f --- /dev/null +++ b/content/gsoc/gsoc-2025/ideas/Glutton.md @@ -0,0 +1,20 @@ +--- +title: "Implementing Protocol Parsers for Glutton Using Spicy" +date: "2025-01-07" +project_url: "https://github.com/mushorg/glutton" +hours: "175 or 350 hours" +mentor: "Muhammad Bilal Arif" +project_type: "Improving an existing tool" +--- + + +Glutton is a powerful **Generic Low Interaction Honeypot** designed to emulate various network services and capture malicious activity for security analysis. Its strength lies in its generic nature, supporting a wide range of network protocols. + +The goal of this project is to: + +* Develop a Go wrapper to integrate [Spicy](https://github.com/zeek/spicy) with Glutton. +* Implement protocol parsers for HTTP and DNS as initial examples. +* Provide documentation to explain the implementation. + +The primary required skill is proficiency in Go programming and familiarity with Linux networking. +An understanding of network monitoring tools like Spicy or similar is a nice-to-have skill.