I have a handful of questions regarding how DirectAdmin handles its security. To be clear, I am referring to additional security options that I can put in place without breaking DirectAdmin functionality. Now that I've got a couple DirectAdmin servers running, I need to begin locking things down.
- Can I change the "admin" user to something else? Will the system ever expect a default "admin" login like it may expect a default SSH port?
- Can I change the DirectAdmin port from 2222? I imagine as DA grows in popularity, scanners will pick up on that port. I'd rather not deal with the noise in my logs.
- Should the primary "admin" account own a domain name or site? Is it more proper to have your primary DA user void of any sites or emails, and then have another account control the primary domain?
- Can I configure to put DirectAdmin users in a jail/chroot for HTTP/FTP and SSH? I know CloudLinux has many options, but what about for the default Apache/PHP7 install? Do I just edit some conf paths to tell DA to create a certain way, and set up my jail accordingly?
- Having easy access to server-status page for quick HTTP monitoring is really important for Apache users with default setup. Is there any chance an addon or something official to easily enable and secure this access? Like an icon "View Apache Live" or something, proper deny/allow settings, etc. I am tempted to create one myself, but I wanted to ask first.
- There was once an old script called Easy Linux Security (ELS) made by developer(s) here, and while it's no longer being maintained, I need something I can rapidly deploy to different DirectAdmin setups (not just cloning a "good" image of one setup). Do you think anything like this will exist again with the influx of new DirectAdmin migration from cPanel and Plesk users? Is there any official documentation on securing DirectAdmin?
Thanks,
- Can I change the "admin" user to something else? Will the system ever expect a default "admin" login like it may expect a default SSH port?
- Can I change the DirectAdmin port from 2222? I imagine as DA grows in popularity, scanners will pick up on that port. I'd rather not deal with the noise in my logs.
- Should the primary "admin" account own a domain name or site? Is it more proper to have your primary DA user void of any sites or emails, and then have another account control the primary domain?
- Can I configure to put DirectAdmin users in a jail/chroot for HTTP/FTP and SSH? I know CloudLinux has many options, but what about for the default Apache/PHP7 install? Do I just edit some conf paths to tell DA to create a certain way, and set up my jail accordingly?
- Having easy access to server-status page for quick HTTP monitoring is really important for Apache users with default setup. Is there any chance an addon or something official to easily enable and secure this access? Like an icon "View Apache Live" or something, proper deny/allow settings, etc. I am tempted to create one myself, but I wanted to ask first.
- There was once an old script called Easy Linux Security (ELS) made by developer(s) here, and while it's no longer being maintained, I need something I can rapidly deploy to different DirectAdmin setups (not just cloning a "good" image of one setup). Do you think anything like this will exist again with the influx of new DirectAdmin migration from cPanel and Plesk users? Is there any official documentation on securing DirectAdmin?
Thanks,