There are upcoming maintenance events which may impact our services. Learn more

Further Security Steps For Windows Server Operating Systems. Print

  • RootLayer.net, RootLayer, network, Hardware, Windows, Operating System, Server, Users, Security Steps, Windows Server, Password Change, Server Password, Server hack, Acceptable Usage Policy, Strong Password, Windows Firewall, unauthorized Access, Open Ports, Block Ports, Block Port Range, Open Port Range, Windows updates, Microsoft, Disable SMB, Ransomware Attack, Knowledgebase, Security Software, Security Firewall, Eset Antivirus, bitdefender Antivirus, Anti Malware malwarebytes, Windows Server 2003 R2, Windows Server 2008 R2, Windows Server 2012 R2, SM1 Disable, Windows Server 2016 Standard, Windows 7, Windows 8, Windows 10, File Server, Eset Server Security, Environment
  • 6

Just to let you know that we (Rootlayer Web Services LTD.) are responsible for Hardware & Network only. We are writing this topic to help our users who are using "Windows Operating Systems". Specially, for Server based operating system users.

1.
Change your server password to make sure we (Rootlayer Web Services LTD.) is unaware of your server password. Although, Our given password was too strong to get your server hacked through Login checking tools running by the online hackers. Changing your server password will ensure that we (Rootlayer) are unaware of it (Until we run a password reset or something which will be performed only after your request). As long as you are paying for your subscribed products from us, You have full rights on them, and we do not interfere. (As long as this is according to our AUP). More Here - https://rootlayer.net/acceptable-usage-policy/

Make sure you are generating a hard password, Not just something your friends or others can easily guess. Generate hard ones using this link - https://my.norton.com/extspa/idsafe?path=pwd-gen


2.
Make sure your Windows Firewall is opened/turned on. If you turned off Windows default firewall, it means you are inviting almost any unauthorized access to your server. Please, keep Windows Firewall Turned On.

Learn here on how to Open/Block Ports through Windows Firewall - https://rootlayer.net/billing/index.php/knowledgebase/3/How-to-Open-or-Block-Ports-from-Windows-Firewall.html


3.
Make sure you Install latest Windows Updates released by Microsoft. Also, Make sure your Self Windows updates & Auto Re-start is Disabled. This option to check to make sure you don't face any self Server reboot performed automatically by Windows Server after an Update is applied.

Be Noted that when global Windows updates is done, You will have to reboot the server for applying these properly. Otherwise, It will not work.


4.
Disable SMB1 to block possibly ransomware attacks. Follow this knowledgebase topic - https://rootlayer.net/billing/index.php/knowledgebase/1/How-to-Disable-SMB1-to-avoid-possibly-Ransomware-Attack.html

Check This topic as well for blocking some Ports to help Disabling SMB matter - https://rootlayer.net/billing/index.php/announcements/5/Cyber-Security-Awareness-Port-445orSMB-over-TCP.html


5.

Make sure you have Paid security software or firewall installed to ensure you have enabled the maximum of security inside the server. We prefer you go with Eset or Bitdefender. If you are using Server based Operating Systems like, Windows Server 2003 R2, 2008 R2, 2012 R2 or 2016, Eset has "File Server" protection as well. We count this as the best protection for a Server available.
> https://www.eset.com/us/
> https://www.bitdefender.com/

Antivirus and AntiMalware is different from each other so make sure you use an Antimalware as well. An Antimalware can do something an Antivirus can't do so You should use both together. We recommend you using Malwarebytes.
> https://www.malwarebytes.com/

Please note that what Security application to use is up to you only. If your purchased security tool is not working properly or failed to deliver the performance you deserve, Please contact your security vendor.

These are the Top 5 steps to do to make sure you are taking care of your Windows Server Environment properly and you care your Server environment a lot.


Was this answer helpful?

« Back