You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Blogs/gsoc_25_new_analyzers_and_integrations.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: Akshit Maheshwary
6
6
---
7
7
8
8
### Introduction
9
-
It has always been on my mind for a while, to contribute to a great open-source project, like IntelOwl, in a significant manner and though I knew about GSoC earlier, I never paid much attention to it. But here I am, finally documenting everything that I have done this summer as part of Google Summer of Code 2025.
9
+
It has always been on my mind, to contribute to a great open-source project, like IntelOwl, in a significant manner and though I knew about GSoC earlier, I never paid much attention to it. But here I am, finally documenting everything that I have done this summer as part of Google Summer of Code 2025.
10
10
### Pre-GSoC Commits/Discussions.
11
11
12
12
@@ -19,17 +19,16 @@ which had improved my understanding around some of the core parts of the archite
19
19
20
20
# GSoC Scope of Work and Deliverables
21
21
22
-
GSoC idea that I've been selected for, involved **designing and development of new analyzers** for IntelOwl to enhance the threat intelligence
23
-
capabilites of IntelOwl, further.
22
+
GSoC idea that I've been selected for, involved **designing and development of new analyzers** for IntelOwl, to further enhance it's threat intelligence capabilites.
24
23
25
-
Apart from that, I had the opportunity to work on optimising the performance of IntelOwl's sister project [Honeyscanner - A vulnerability analyzer for honeypots](https://github.com/honeynet/honeyscanner)
24
+
Apart from that, I had the opportunity to work on optimising the performance of another Honeynet org's project [Honeyscanner - A vulnerability analyzer for honeypots](https://github.com/honeynet/honeyscanner)
26
25
which was not in scope of the proposal, but since HoneyScanner analyzer had to be added, as per the initial proposal, so it was worked on as well.
27
26
28
27
Now I'll proceed with elucidating the work that I've done.
29
28
30
29
## Addition of New Analyzers
31
30
32
-
- Added [HuntingAbuseAPI Analyzer](https://github.com/intelowlproject/IntelOwl/pull/2885) which provides an updated list of false positives from all it's services. This API can be queried to verify. if the provided observable is valid or false positive.
31
+
- Added [HuntingAbuseAPI Analyzer](https://github.com/intelowlproject/IntelOwl/pull/2885) which provides an updated list of false positives from all it's services. This API can be queried to verify if the provided observable is valid or false positive.
33
32
- Updated [GreedyBear Analyzer](https://github.com/intelowlproject/IntelOwl/pull/2902) to fetch the command sequences executed in a honeypot using CommandSequenceAPI from GreedyBear.
34
33
- Integrated [GuardDog](https://github.com/intelowlproject/IntelOwl/pull/2930) to IntelOwl, as part of which 2 analyzers, **GuardDogFile** and **GuardDogGeneric**, have been added in order to scan for malicious pypi, npm and go packages.
35
34
-[ExpandURL Analyzer](https://github.com/intelowlproject/IntelOwl/pull/2920) has been added to IntelOwl, which basically follows the redirection chain for a provided malicious shortened URL and expands it to it's original form for further analysis.
0 commit comments