Skip to main content
diardnic
New Member
February 4, 2020
Solved

Please help me identify that flows

  • February 4, 2020
  • 1 reply
  • 16760 views

I spent some times on fortianalyzer NOC view. Then i noticed some internal users have a lot of blocked udp outgoing connections. So far nothing looks suspicious on workstations. Whatsoever, i'd really like to understand what is going on.

So if you have any ideas.

ty

 

Sample

    Best answer by andrewbailey
    Hi diardnic, What are the clients may I ask? I traced a similar issue a year or two back to Windows 10 machines. There is a setting that allows windows 10 to pull updates via other Windows 10 machines (even outside your network). Originally the behaviour was to allow peering to any other Windows 10 machine and the results look a bit like what you are seeing. Lots of connections to random consumer IP addresses. I think The behaviour has now been changed and by default it now only uses machines on the local subnet. But it is still a setting that can be changed. Even by end users if not locked down. Let me know if that sounds plausible and I’ll try and find a screenshot or link for you. Kind Regards, Andy.

    1 reply

    diardnic
    diardnicAuthor
    New Member
    February 5, 2020

    I'm more and more concerned it could be something malicious :

    - thousands UDP connections to ISP subscribers IP ranges

    - it has started as soon as user locked is windows session, and ended when he came back

    - some botnets seems to show that kind of behaviour for c&c communication

     

    Alivo__FTNT
    Staff
    Staff
    February 5, 2020

    Hello,

    I would perhaps suggest to use some sort of tool that can track which program/process makes these connections.

    Never tried this one but it might be helpful > google fo LiveTcpUdpWatch

     

    Best Regards, Alivo

    ede_pfau
    SuperUser
    SuperUser
    February 5, 2020

    @OP,

     

    how come you can detect these policy violations in the first place? Do you restrict outbound traffic to 'known' services?

    Usually, outbound traffic is allowed by a 'services: all' policy but I think your design is way smarter.