Make sure Telnet and other non-secure remote login commands are not available for remote access |
This query verifies that insecure ways to access the endpoints are not available, such as Telnet, radmin and more. Clear-text protocols (such as HTTP, telnet, etc.) do not encrypt traffic or logon details, making it easy for an eavesdropper to intercept this information.
Sign-up for Action1 Free Edition to streamline compliance efforts for your network of endpoints. Such as you can simplify assessments of 2.3.b Insecure Remote Login Not Available for your internal or external auditors, create instant or regular compliance reports that prove your compliance while reducing the costs. Action1 Endpoint Security Platform is entirely SaaS, with online web interface (no management tools to install) and it has zero cost for basic functionality. Running in the Cloud, Action1 discovers all of your endpoints within seconds and allows you to pass compliance audits and maintain continuous compliance with ease.
Respond to Threatsin Real-Time
Ask questions in plain English such as "list of installed software" or "all running processes".
Get answers instantly from live systems or subscribe to real-time alerts.
Related Alerts and Reports:
2.3.a Strong Encryption for Administrator Access
Verify that a strong encryption method is invoked before the Administrator’s password
Keywords: Make sure Telnet and other non-secure remote login commands are not available for remote access,Action1 2.3.b Insecure Remote Login Not Available.
Find more information on 2.3.b Insecure Remote Login Not Available at Microsoft TechNet.