So you want to build a Security Program? Part 1 - Vulnerability Scanning
-
So I've been using OpenVAS for a while now, and the results are enlightening. One question though is how do I make sure my the NVT's are current?
I tried running
openvasmd --update && openvasmd --rebuildfrom a shell and was told thatopenvasmd isn't recognized -
So @IRJ I wasn't sure where else to put this. Do you give root access to your vulnerability scanners? Just a conversation I've been having with some people here.
-
@stacksofplates said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
So @IRJ I wasn't sure where else to put this. Do you give root access to your vulnerability scanners? Just a conversation I've been having with some people here.
Unfortunately they need root to scan according to tenables documentation. You can set a specific login window for that account to correlate with your scan. That way it isn't abused anywhere besides during the scan window. Not really 100% secure, but it's better than leaving it wide open.
-
@irj said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
@stacksofplates said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
So @IRJ I wasn't sure where else to put this. Do you give root access to your vulnerability scanners? Just a conversation I've been having with some people here.
Unfortunately they need root to scan according to tenables documentation. You can set a specific login window for that account to correlate with your scan. That way it isn't abused anywhere besides during the scan window. Not really 100% secure, but it's better than leaving it wide open.
Ya we do SCAP with the RedHat SCAP tool. We don't control the Nessus box so we weren't going to give up root access, and they are essentially just checking patch levels.
What I don't get is why they need root access. If there is a vulnerability, it has to be able to be seen/leveraged from an unprivileged account. Sure you can see vulnerabilities when you log in as root, because you are the vulnerability. I think it's kind of pointless.
-
@stacksofplates said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
@irj said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
@stacksofplates said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
So @IRJ I wasn't sure where else to put this. Do you give root access to your vulnerability scanners? Just a conversation I've been having with some people here.
Unfortunately they need root to scan according to tenables documentation. You can set a specific login window for that account to correlate with your scan. That way it isn't abused anywhere besides during the scan window. Not really 100% secure, but it's better than leaving it wide open.
Ya we do SCAP with the RedHat SCAP tool. We don't control the Nessus box so we weren't going to give up root access, and they are essentially just checking patch levels.
What I don't get is why they need root access. If there is a vulnerability, it has to be able to be seen/leveraged from an unprivileged account. Sure you can see vulnerabilities when you log in as root, because you are the vulnerability. I think it's kind of pointless.
You can do an external uncredentialed scan against a box and only see a few vulnerabilities. It doesn't mean the box only has those vulnerabilities. A skilled hacker could try common exploits against the box and possibly breach it. Another possibility is they are using their own scripts against the box instead of what you'd see with an out of the box scanner.
-
@irj said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
@stacksofplates said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
@irj said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
@stacksofplates said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
So @IRJ I wasn't sure where else to put this. Do you give root access to your vulnerability scanners? Just a conversation I've been having with some people here.
Unfortunately they need root to scan according to tenables documentation. You can set a specific login window for that account to correlate with your scan. That way it isn't abused anywhere besides during the scan window. Not really 100% secure, but it's better than leaving it wide open.
Ya we do SCAP with the RedHat SCAP tool. We don't control the Nessus box so we weren't going to give up root access, and they are essentially just checking patch levels.
What I don't get is why they need root access. If there is a vulnerability, it has to be able to be seen/leveraged from an unprivileged account. Sure you can see vulnerabilities when you log in as root, because you are the vulnerability. I think it's kind of pointless.
You can do an external uncredentialed scan against a box and only see a few vulnerabilities. It doesn't mean the box only has those vulnerabilities. A skilled hacker could try common exploits against the box and possibly breach it. Another possibility is they are using their own scripts against the box instead of what you'd see with an out of the box scanner.
We do credentialed but not privileged. I just don't trust another team to have root access to our stuff. Admins don't even have permission to log into the servers. It's all forced through Tower. Root access is disabled on both console logins and SSH and I get real time notifications for events. To me, I think I'd be going backwards if I gave them root access. If I owned the Nessus box it would be 100% different, but since it's a different team I don't trust it.
-
I don't have permission to change things on their Nessus system. So I think it's more important that they don't have permissions on mine. If we had to do something, I would craft a sudoers file for them vs just give them root/sudo for everything.
-
@stacksofplates said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
I don't have permission to change things on their Nessus system. So I think it's more important that they don't have permissions on mine. If we had to do something, I would craft a sudoers file for them vs just give them root/sudo for everything.
If they're doing real pen testing, they don't need root access to stuff. Hack the box and tell me how you got in!
-
@dafyre said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
@stacksofplates said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
I don't have permission to change things on their Nessus system. So I think it's more important that they don't have permissions on mine. If we had to do something, I would craft a sudoers file for them vs just give them root/sudo for everything.
If they're doing real pen testing, they don't need root access to stuff. Hack the box and tell me how you got in!
Right.
-
@dafyre said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
@stacksofplates said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
I don't have permission to change things on their Nessus system. So I think it's more important that they don't have permissions on mine. If we had to do something, I would craft a sudoers file for them vs just give them root/sudo for everything.
If they're doing real pen testing, they don't need root access to stuff. Hack the box and tell me how you got in!
Vulnerability Scanning and pen testing are not the same. Not all attack surfaces are covered during pen tests and pen testing is much more labor intensive for less information.
-
@irj said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
@dafyre said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
@stacksofplates said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
I don't have permission to change things on their Nessus system. So I think it's more important that they don't have permissions on mine. If we had to do something, I would craft a sudoers file for them vs just give them root/sudo for everything.
If they're doing real pen testing, they don't need root access to stuff. Hack the box and tell me how you got in!
Vulnerability Scanning and pen testing are not the same. Not all attack surfaces are covered during pen tests and pen testing is much more labor intensive for less information.
I guess I don't see why you would do either without it being blind. I guess it's not a far cry to assume that hackers could get root on your box if they find a vulnerable application.
-
@dafyre said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
@irj said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
@dafyre said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
@stacksofplates said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
I don't have permission to change things on their Nessus system. So I think it's more important that they don't have permissions on mine. If we had to do something, I would craft a sudoers file for them vs just give them root/sudo for everything.
If they're doing real pen testing, they don't need root access to stuff. Hack the box and tell me how you got in!
Vulnerability Scanning and pen testing are not the same. Not all attack surfaces are covered during pen tests and pen testing is much more labor intensive for less information.
I guess I don't see why you would do either without it being blind. I guess it's not a far cry to assume that hackers could get root on your box if they find a vulnerable application.
I can see the merit to a credentialed scan because of insider threats. It will show packages are up to date, file perms that should be set, etc. However I don't see the merit to a plain root access scan. I would at the very least craft sudo perms for the Nessus user.
-
@stacksofplates said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
@dafyre said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
@irj said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
@dafyre said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
@stacksofplates said in So you want to build a Security Program? Part 1 - Vulnerability Scanning:
I don't have permission to change things on their Nessus system. So I think it's more important that they don't have permissions on mine. If we had to do something, I would craft a sudoers file for them vs just give them root/sudo for everything.
If they're doing real pen testing, they don't need root access to stuff. Hack the box and tell me how you got in!
Vulnerability Scanning and pen testing are not the same. Not all attack surfaces are covered during pen tests and pen testing is much more labor intensive for less information.
I guess I don't see why you would do either without it being blind. I guess it's not a far cry to assume that hackers could get root on your box if they find a vulnerable application.
I can see the merit to a credentialed scan because of insider threats. It will show packages are up to date, file perms that should be set, etc. However I don't see the merit to a plain root access scan. I would at the very least craft sudo perms for the Nessus user.
Edit, initially wrote can't see the merit. Meant to say can.
