We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Implement https://containerssh.io/guides/honeypot/
Extracted from https://containerssh.io/guides/honeypot/ This section just includes major steps. Refer to the project board for detailed tasks. Set up the following components:
disk_type
Q: Should we use one subnet for both VM or split them? A: Maybe split for security: https://community.cisco.com/t5/switching/ip-subnetting-best-practice/td-p/2191100
Q: How much disk space is sufficient for each VM?
Because "we need to have have sufficient disk space to hold audit logs and containers for both VMs."
Check out #42
Q: Which S3-compatible storage do we use? A: MinIO is good enough. > It should be fairly simple to convert into a docker-compose file or similar.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Goal
Implement https://containerssh.io/guides/honeypot/
Major steps
Might need to modify
disk_type
for Packer.Open Questions
Q: Should we use one subnet for both VM or split them?
A: Maybe split for security: https://community.cisco.com/t5/switching/ip-subnetting-best-practice/td-p/2191100
Q: How much disk space is sufficient for each VM?
Check out #42
Q: Which S3-compatible storage do we use?
A: MinIO is good enough. > It should be fairly simple to convert into a docker-compose file or similar.
The text was updated successfully, but these errors were encountered: