How to be secure using MOR

From Kolmisoft Wiki
Revision as of 12:42, 19 November 2020 by Viliuss (talk | contribs)
Jump to navigationJump to search
Secure.png


How to be secure using MOR

This guide will give you some hints where you could improve your MOR system security

Passwords

  1. Never give passwords to people you do not trust
  2. Use only secure passwords:
    1. Your passwords must be at least 12 symbols length
    2. Your passwords must contain letters (a-z)
    3. Your passwords must contain numbers (0-9)
    4. Your passwords must contain special characters (!@#$%^&*() and so on..)
  3. You must use different passwords for all types of services, for example MOR GUI, ROOT, phpmyadmin and stats passwords must be different
  4. When using SSH - please consider using SSH keys instead of passwords. More information about SSH can be found here.
  5. Change passwords regularly. Some guides how to do it:
    1. Change root password
    2. Change stats password
    3. MOR GUI password - change it from user details
  6. Change all default MOR passwords after installation.

Devices

  1. Make sure you carefully understand what each device setting means.
  2. Do not enable Insecure port + Invite, unless you understand what these settings mean!

Device passwords

  1. Always create secure (as stated above) passwords for devices if you want to avoid loss.



Multiple accounts registration

In order to prevent multiple accounts registration from the same user - you can implement an SMS based user verification using MOR API and a technique described here.

MOR good practices

  1. It is recommended to disable public new user registrations or to be careful with:
    1. Default user settings - it is common for new users to do these mistakes:
      1. DO NOT put any initial balance - if you do so you will give money for calling for your new customers for free - such service is often abused and one or more users make a lot of of free account registrations to call for free.
      2. DO NOT MAKE USER POSTPAID - if you do so with public registrations enabled and you set any credit for that user (it can also be automatically applied from default user settings) - that user will be allowed to call for free and you risk that the unknown customer will not pay you.
      3. DO NOT GIVE ANY CREDIT in default user settings - if a credit is given and the user is postpaid - he is allowed to call till he reaches this limit. Very dangerous when being used with public user registrations.
  2. Do not connect external PBX systems or at least ensure that they ARE SECURE. Please read more about this here, here and here.
  3. Use Action log feature in MOR to monitor suspicious users actions in MOR system. Keep an eye on Hacking attempt messages here - they indicate that the user is trying to access MOR GUI places/features which are not allowed for him to use. More information about Action log can be found here.



Additional software to increase MOR system security

MOR Monitorings Addon

Monitorings Addon addon will protect your from high money losses. More information about this addon can be found here.

Fail2Ban

Fail2Ban is installed by default in MOR systems and by using following rules protects server against brute force attacks and suspicious activity:

  • ssh-iptables - blocks IP which enters incorrect password 3 times in 10 minutes. Automatically unblocked after 10 minutes.
  • asterisk-iptables - blocks IP which tries SIP registration with wrong password 5 times in 10 minutes. Automatically unblocked after 10 minutes.
  • ast-cli-attck - blocks IP which sends any SIP packet from sipcli, sipvicious, sip-scan, sipsak, sundayddr, friendly-scanner, iWar, CSipSimple, SIVuS, Gulp, sipv, smap, friendly-request, VaxIPUserAgent, VaxSIPUserAgent, siparmyknife or Test Agent tool. Blocked permanently, no automatic unblock.
  • asterisk-manager - blocks IP if it tries to connect Asterisk Manager Interface and is not authorized to do that. Blocked permanently, no automatic unblock.
  • ast-hgc-200 - blocks IP who attempts to send unauthorized call (HGC 200) 20 times in 10 minutes. Blocked permanently, no automatic unblock.
  • mor_api - blocks IP which tries to use MOR API with wrong authentication details. Blocked permanently, no automatic unblock.
  • mor_ddos - block IP which tries incorrect and suspicious URLs 20 times in 10 minutes. Automatically unblocked after 1 hour.

Information how to override default Kolmisoft Fail2Ban configuration can be found here.

More information about Fail2Ban can be found here and here.

Iptables

It is a default Linux firewall and is installed by default in all MOR systems. Although additional configuration is needed in order it would protect you:

  • Configure iptables that it would accept connections only to ports required for MOR system to work. More information about these ports can be found here.
  • Allow connections to SSH (default TCP Port: 22) only from support.kolmisoft.com and systems you trust.
  • If MOR GUI is not required for your business model - you can block access to it too (Default TCP ports: 80/443). Only remember to allow access to it from support.kolmisoft.com and the systems you trust.





Does Fail2ban block calls with hang up cause code 200?

By default Fail2Ban blocks calls (IP address sending those calls) with HGC 200 when there are 20 or more such attempts / minute - it is a safe limit which should never be reached by normal users. This behavious can be easy adjusted. See this guide how to achieve this.

See also:

http://wiki.kolmisoft.com/index.php/Lots_of_calls_made_by_System_Admin_user

Services

  • Apache (httpd) - you must use SSL in order you and your users could surf MOR GUI safely. More information about installing SSL can be found here.
  • Asterisk - do not connect external PBX systems or at least ensure that they ARE SECURE. Please read more about known insecure PBX systems here, here and here.
  • SSH - you can go even further securing the SSH - you can limit the number of allowed SSH connections per minute. For more information please check this guide.
  • MySQL - read here why you don't need to use Fail2Ban in order to block unsuccessful login attempts.



Various security related guides




Very advanced techniques for highly technically skilled people

For these techniques Kolmisoft does not provide any support.

  • Port knocking (can be used for SSH or GUI access if it is not used publicly). More information about this technique can be found here.
  • Intrusion prevention systems: Cisco Suricata



Other information regarding increasing MOR security


Protection against Brute-force attacks

If you try to login to MOR system unsuccesfully 3 times in a row (via GUI or API) you will have to wait 10 seconds to login again.

Note that 10 seconds blocking is set to the IP, so everyone who are trying to access MOR System from the same IP will have to wait for 10 seconds.

Login bad.png



Block Countries

Deny/Allow access only from specified Countries, using Blocked Countries functionality



Alerts

Use Alerts functionality to prevent the hacking attempts.



See also

Retrieved from "https://wiki.kolmisoft.com/index.php?title=How_to_be_secure_using_MOR&oldid=25973"