Difference between revisions of "Vuln ssh noadmin"
m (→Next Steps) |
m (→Next Steps) |
||
| (One intermediate revision by one user not shown) | |||
| Line 9: | Line 9: | ||
= Next Steps = | = Next Steps = | ||
| − | If this risk is unacceptable for your system, then you will want to | + | If this risk is unacceptable for your system, then you will want to configure administrative users for your system. Please follow the steps below: |
Step 1: Log into the ASL GUI, click on Configuration and select the ASL configuration menu option. This will open the ASL configuration screen. | Step 1: Log into the ASL GUI, click on Configuration and select the ASL configuration menu option. This will open the ASL configuration screen. | ||
| Line 17: | Line 17: | ||
https://www.atomicorp.com/wiki/index.php?title=ASL_Configuration#ADMIN_USERS | https://www.atomicorp.com/wiki/index.php?title=ASL_Configuration#ADMIN_USERS | ||
| − | + | If you need assistance setting up SSH keys for these users, please see the [[SSH keys]] article. | |
| − | Step | + | Step 3: Click the "update" button. |
This will resolve this vulnerability. | This will resolve this vulnerability. | ||
Latest revision as of 11:19, 31 May 2015
Vulnerability
No Administrative users are defined
Explanation
Administrative users are the users that maintain this system, that should su or sudo to root. This test verifies that administrative users are defined. It is not recommended to manage the system by directly logging in as root.
[edit] Next Steps
If this risk is unacceptable for your system, then you will want to configure administrative users for your system. Please follow the steps below:
Step 1: Log into the ASL GUI, click on Configuration and select the ASL configuration menu option. This will open the ASL configuration screen.
Step 2: Scroll down to ADMIN_USERS and set this to the users on your system that you have configured SSH keys for.
https://www.atomicorp.com/wiki/index.php?title=ASL_Configuration#ADMIN_USERS
If you need assistance setting up SSH keys for these users, please see the SSH keys article.
Step 3: Click the "update" button.
This will resolve this vulnerability.
