<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'><br><hr id="zwchr"><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><span style="font-family: Arial,Helvetica,sans-serif; font-size: 10pt;">When we designed our systems on asterisk we designed it to me multi-tenant. Se we use customer prefixes on all extensions. This allows us to have multiple customers using the same extension pools. It also reduces the hack foot print as hackers must know the prefix for a customer to try and brute force things. All passwords use 8+ characters with alfa/numeric and special characters. <br>
<br>
As I see it Asterisk does very good keeping out the hackers if you use a solid design in your peer and dialplans. At the least put an alpha character post or pre other wise you are just asking for it. Use your head you can be smarter then they are.<br>
<br>
We are looking into ipban as well. If any one has an example of ipban I would love to see how best to implement it. In a 4 year period we have not had a breach but we do get about 10 to 15 hack attempts a week. We have blocking scripts that block ip's at the primary firewall but I would like to trigger the ipban at each switch level. Could I also use the ipban method to trigger the audo updates to our primary firewalls? Any advice is appreciated. <br>
<br>
<div id="divSignature"></div>
Bryant<br>
<br>
<span style="font-family: tahoma,arial,sans-serif; font-size: 10pt;"><hr align="center" size="2" width="100%"></span></span><br></blockquote><span>You could also use OSSEC http://www.ossec.net and a custom decoder and rule:<br><br><decoder name="local-asterisk-denied"><br> <prematch>NOTICE[\d+] \S+: Registration from </prematch><br> <regex offset="after_prematch">^\S+ failed for '(\d+.\d+.\d+.\d+)'</regex><br> <order>srcip</order><br></decoder><br><br><rule id="110005" level="5"><br> <decoded_as>local-asterisk-denied</decoded_as><br> <description>Asterisk Potentially Under Attack</description><br></rule><br><br><rule id="110006" level="10" frequency="5" timeframe="10"><br> <if_matched_sid>110005</if_matched_sid><br> <same_source_ip /><br> <description>Asterisk Under Brute Force Attack</description><br></rule><br>-- <br><span name="x"></span>Thanks, Phil<span name="x"></span><br></span></div></body></html>