This has been covered elsewhere (like on serverfault: http://serverfault.com/a/107346/2557 ) But it comes down to: - Take existing server down immediately. I'm assuming it is not on an isolated network -- so this should really be a priority. - Prep a new patched server (with a smaller attack surface and updated security credentials) - Postmortem the old box on an isolated network. Try to understand how the attacker g…
Ask HN: Anonymous person sent proof of SSH access to our production server
21–30 of 246 posts
Re: Ask HN: Anonymous person sent proof of SSH access to our production server
#22>We are a small company and don't have any security experts, etc. Find one.
If unsure about how much a reward should be, keep in mind how expensive it could get without.. often a costly chain-reaction of disasters.
Re: Ask HN: Anonymous person sent proof of SSH access to our production server
#23>We are a small company and don't have any security experts, etc. Find one.
This isn't the most insightful or actionable comment, but it is the correct solution for both the short term problem and many long term problems.
Without a "security expert" there really is nothing they can do.
Re: Ask HN: Anonymous person sent proof of SSH access to our production server
#24Re: Ask HN: Anonymous person sent proof of SSH access to our production server
#25Earlier quoted context omitted.
Or contact the person if you can and ask them how they got in maybe even offer him a financial reward. Since he contact you Anonymously and is not trying to extort you he's just trying to point the issue out so there's no point in over reacting.
How much would you trust that person? Enough to potentially risk your business on them?
Re: Ask HN: Anonymous person sent proof of SSH access to our production server
#26Re-install the server On new re-installed server: 1. Change SSH service port to non-default one. 2. Do not allow root user to remotely connect (change sshd config) 3. Create new user which you will be using for administration to login as root. 4. If possible restrict which IP addresses are allowed to connect via SSH using firewall.
Re: Ask HN: Anonymous person sent proof of SSH access to our production server
#27Earlier quoted context omitted.
How much would you trust that person? Enough to potentially risk your business on them?
You are already trusting that person enough to risk your business on them, if that server is still up and running after finding the security hole.
Re: Ask HN: Anonymous person sent proof of SSH access to our production server
#28Re: Ask HN: Anonymous person sent proof of SSH access to our production server
#29Subsequently, refer to "Essential Security for Linux Servers" [0] and "7 Security Measures to Protect Your Servers" [1].
[0] https://plusbryan.com/my-first-5-minutes-on-a-server-or-esse...
[1] https://www.digitalocean.com/community/tutorials/7-security-...
[2] https://www.digitalocean.com/community/tutorials/how-to-set-...
Re: Ask HN: Anonymous person sent proof of SSH access to our production server
#30This has been covered elsewhere (like on serverfault: http://serverfault.com/a/107346/2557 ) But it comes down to: - Take existing server down immediately. I'm assuming it is not on an isolated network -- so this should really be a priority. - Prep a new patched server (with a smaller attack surface and updated security credentials) - Postmortem the old box on an isolated network. Try to understand how the attacker g…
Also, wipe clean the existing server after the Postmortem. Even if fairly sure that the server can be cleaned it's never safe to re-use a box which was compromised.