Skip to main content
ricky76
New Member
Sep 7, 2016 7:13 AM UTC
Question

Large traffic by a frauded account email - IPS how to use

Hi, I'm facing the following issue. On our fortigate 110C I'm observing a lot of traffic originated from an email account. This email account was frauded and someone is trying to register it with wrong password on our servers in the locale network generating a lot of traffic.

Unfortunately we can't block this account because is in use every day by our customer. So I tried to use the IPS sensor in default mode but no mails are delivered. How can I configure the IPS sensor in order to block the malicious traffic and permit the right traffic? Could you please give some advice? In this situation we have the firewall CPU at 100%

 

Thanks.

Ricky

    10 replies

    ede_pfau
    SuperUser
    SuperUser
    Sep 7, 2016 11:10 AM UTC

    I don't quite understand the situation from your post:

    - the traffic is from where to where - internal to internal?

    - which kind of traffic - SMTP, IMAP,...?

    - why did you think that an IPS sensor with "default" settings would block this specific traffic? Why IPS in the first place?

     

    Lots of questions. If you could be more specific we can try to help you here.

    Translate
    ricky76
    ricky76Author
    New Member
    Sep 8, 2016 8:33 AM UTC

    Hi ede_pfau,

    the traffic is from wan to internal LAN.

     

    This email-account is in use by our customer and I can't use an email-filter otherwise no more mail are sent or received.

    We already changed a lot of time the email password with no luck. We cancelled the account email on the client PC but traffic does't stop anyway.

     

    So I supposed that maybe IPS sensor can help in this scenario, am I wrong?

    If not how can I limit or stop this traffic?

    Often the firewall's CPU goes at 100% and I forced to klill the netscan process to regain the normal behaviour.

     

    Thanks.

    Ricky

    Translate
    ede_pfau
    SuperUser
    SuperUser
    Sep 8, 2016 1:43 PM UTC

    OK, first reduce all UTM features in use on that policy to guarantee stable operation of your firewall. Not blocking / scanning connection attempts should not bring your FGT down, or else it's way too small.

     

    Second, you can use a 'rate limit' IPS filter to specifically block connections with too many connection attempts per time interval. The 'how-to' depends on the firmware version you're using. From v5.2 on, rate limit IPS sensors can be defined in the WebGUI; on older versions, in the CLI.

    Either there is already a signature for SMTP login, or IMAP login (you didn't answer which kind of traffic you want to block), or you'll write one yourself. The main point is that the sensor checks the server's answer - in case of password mismatch it'll be some text string like 'login error' or such. That depends on the protocol used, but it's well defined and you should be able to google for it.

     

    You can find examples of rate limit IPS signatures in the forums, even by me. Keyword is 'rate limit' or 'custom IPS signature'. Then adapt the values in the sensor to your situation.

     

    When the sensor triggers (for example, after 3 unsuccessful login attempts) the FGT can block any further connection attempts from this source IP address for a period of time (minutes, hours,...). That should bring your traffic load down a lot.

    Translate
    ricky76
    ricky76Author
    New Member
    Sep 8, 2016 2:33 PM UTC

    Hi Ed,

    I think it's a good solution and I'm going to try.

    My firmware version is v5.0,build0252 (GA Patch 5) and the only way is to proceed by CLI command.

    I'm searching in the forum for an example...

    Translate
    Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024