How Windows Server strengthens the security of your cloud server

1. Change the default port number

Terminal Services by default using the well-known port number 3389, It is clear that everyone knows what this port is doing , So change the port number can avoid a lot of machine scanning. You can modify the default port number from the Terminal Services native , and If there is a firewall to do NAT, It is simpler , the port number after NAT is not used 3389 Just .

2. Set up complex password

now theGpuThe processing power is horrible .,so it's not safe to have fewer digits.,combination of uppercase and lowercase letters and numbers Abit password is still basic enough. Remote Desktop unexpectedly does not supportCACertificate Authentication Login,This is lessSSHup. SSHSet as2048bitRSACertificate Login,Disable Password login,prohibitedRootLogin,it's pretty safe.

3. Limit the number of login attempts

Modify Group Policy,”Computer Configuration->windowsSet -Security Settings -Account Policies -Account Lockout Policy","Account lockout threshold value"set toTen,alsoTenInvalid login and then block each otherIP,prevents it from continuing to try to log on for a period of time. "Account lockout time"is how long after the invalid login can continue to try to log on. "Reset account lockout counter"set how long it takes to reset"Account lockout threshold value",must be less than or equal to"Account lockout time".

4, Prohibit Administrator user Remote Desktop login

Administrator is too glaring , You can disable its Remote Desktop login , and set up an administrator account to perform remote login tasks , So the combination of user name and password is more complex , the difficulty of blasting greatly increased.

Double-click the Local policy, security settings , Computer Configuration ->windows settings User Rights Assignment , allow logon through Terminal Services , Administrators account is deleted and added to another administrator account.

5. Encrypt Remote Desktop Connection

By default , the Remote Desktop Data link is not encrypted , very dangerous wood has , easy to be monitored with wood. 2003 later versions of Windows can be Encrypting Remote Desktop Connection using SSL, of course, encryption is not only a type of SSL ,SSL works in the transport layer, the same can be done at the IP layer IPSec implements secure Remote Desktop and provides authentication and data integrity verification.

This article is from the "12179013" blog, please be sure to keep this source http://12189013.blog.51cto.com/12179013/1874625

How Windows Server strengthens the security of your cloud server