Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add VBR-Decoy to T-Pot #1749

Closed
n00rm opened this issue Jan 24, 2025 · 1 comment
Closed

Add VBR-Decoy to T-Pot #1749

n00rm opened this issue Jan 24, 2025 · 1 comment
Labels
no basic support info Please follow the guidelines so we can help

Comments

@n00rm
Copy link

n00rm commented Jan 24, 2025

Is your feature request related to a problem? Please describe.
I stumbled across VBR-Decoy and would like to see it integrated to T-Pot
VBR-Decoy is a simple server to act as a Veeam "honeypot" providing alerting for network scans for Veeam services.
With this project, T-Pot could be extended to alert on Veeam Backup scanning/attacking.

Describe the solution you'd like
A native integration of this project would be awesome. It seems that it doesn't use Docker/Container and the deployment is currently only as OVA (VM) available.

Describe alternatives you've considered
none

Additional context
Project: https://github.com/VeeamHub/veeam-decoy
Documentation: https://dl.24xsiempre.com/Decoy_Manual_EN.pdf

@github-actions github-actions bot added the no basic support info Please follow the guidelines so we can help label Jan 24, 2025
@t3chn0m4g3
Copy link
Member

Thanks for spotting this!

I just reviewed the codebase for feasibility and the number of port collisions we'd have with other honeypots is extremely high, logging is currently implemented with Syslog (we require JSON) and the hardware requirements (even when assuming 1GB of RAM will be working fine) are quite high for a single purpose honeypot.

Even if we integrated the solution into T-Pot, it would mostly have to run isolated anyway (for the reasons mentioned above) which would render an integration mostly redundant.

Based on the purpose the project is aiming for, a distributed installation of Veeam-Decoy for environments invested in Veeam, will probably make the best sense.

Thanks again for taking the time to open the issue and all the best!

@t3chn0m4g3 t3chn0m4g3 closed this as not planned Won't fix, can't repro, duplicate, stale Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no basic support info Please follow the guidelines so we can help
Projects
None yet
Development

No branches or pull requests

2 participants