Security Considerations: Difference between revisions

From Integrics Wiki
Jump to navigation Jump to search
Content deleted Content added
Created page with "* Disallow routes to countries that customers don't need, especially high fraud countries. * Set a daily spending limit for all customers. * Requiring long password lengths fo..."
 
Dovid (talk | contribs)
No edit summary
Line 4: Line 4:
* Educate customers on choosing good passwords.
* Educate customers on choosing good passwords.
* Have contracts to make sure the right person pays if they are hacked and run up a huge bill.
* Have contracts to make sure the right person pays if they are hacked and run up a huge bill.
* Change the SSH port from 22 to something non standard like 9900.
* Use IPTables to lock out countries where you do not have customers.
* Set Asterisk servers to use non default ports for SIP like 5065 instead of 5060.
* Make sure all handsets have a username and password which are not the devices default.
* Monitor servers with a tool like Nagios and or Cacti where there is an alert if there is more than X calls per customer, system etc.


Some systems have easySysAdmin or fail2ban (for example) automatically block brute force SSH or SIP registration attacks.
Some systems have easySysAdmin or fail2ban (for example) automatically block brute force SSH or SIP registration attacks.

Revision as of 17:23, 25 February 2015

  • Disallow routes to countries that customers don't need, especially high fraud countries.
  • Set a daily spending limit for all customers.
  • Requiring long password lengths for phones and people.
  • Educate customers on choosing good passwords.
  • Have contracts to make sure the right person pays if they are hacked and run up a huge bill.
  • Change the SSH port from 22 to something non standard like 9900.
  • Use IPTables to lock out countries where you do not have customers.
  • Set Asterisk servers to use non default ports for SIP like 5065 instead of 5060.
  • Make sure all handsets have a username and password which are not the devices default.
  • Monitor servers with a tool like Nagios and or Cacti where there is an alert if there is more than X calls per customer, system etc.

Some systems have easySysAdmin or fail2ban (for example) automatically block brute force SSH or SIP registration attacks.