splunk / splunk/security_content
Duplicate *http* Pattern in Windows Ngrok Reverse Proxy Usage Detection
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 494
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 25
Description
Hi,
This is a relatively small problem and I understand that it doesn’t really affect the Windows Ngrok Reverse Proxy Usage Detection process at all. It still works perfectly fine the way it is.
But upon going through the detection process, I found that the http is being repeated twice in the Processes.process IN clause:
Processes.process IN ("*start*", "*--config*", "*http*", "*authtoken*", "*http*", "*tcp*")
It seems that the second occurrence of http is a repeat and can therefore be deleted to improve the search.
Processes.process IN ("*start*", "*--config*", "*http*", "*authtoken*", "*tcp*")
Of course, this is just a tiny problem and it doesn’t impact the way the detection works and the results it produces in any significant way.
The reason I bring up these inconsistencies is just that I like participating in the Security Content project in whatever small way I can participate. It’s always useful for keeping search results more optimal, consistent, and neat, and I would rather report a tiny problem than ignore it when I see one.
It’s a fantastic project, and I hope my contributions can add to its already high value.
Thank you for your time and consideration.
Best regards
App Version:
ESCU: [6.6.0]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Windows Ngrok Reverse Proxy Usage Detection entry and inspect its Processes.process IN clause. Remove the repeated "http" value, then verify that the resulting detection definition remains valid and contains the intended patterns.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100