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

Audit logging resource requirements #576

Open
skeggse opened this issue Oct 11, 2023 · 1 comment
Open

Audit logging resource requirements #576

skeggse opened this issue Oct 11, 2023 · 1 comment

Comments

@skeggse
Copy link

skeggse commented Oct 11, 2023

The docs indicate that enabling auditing imposes "severe resource requirements." What are those requirements, and what makes them "severe?" Does ContainerSSH do something more invasive or complex than other SSH auditing tools?

@janosdebugs
Copy link
Contributor

janosdebugs commented Oct 12, 2023

Hey @skeggse audit logging can, depending on the configuration, log every keystroke, the whole SFTP communication, port forwarded data (not sure this is implemented yet, @tsipinakis do you know?) and more. This means that you need to have enough storage space on your ContainerSSH host to temporarily store possibly several GBs of data per session and then enough bandwidth to upload it to an S3 storage if that's what you want to do. Disk IO should not be a concern, you will run out of CPU much sooner due to the relatively expensive encryption SSH uses I believe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants