![]() Otherwise, but that's specific to Linux, you can run the process in an isolated network namespace and use wireshark to monitor the traffic. To monitor an existing process with a known PID: strace -p $PID -f -e trace=network -s 10000 To start and monitor an new process: strace -f -e trace=network -s 10000 PROCESS ARGUMENTS These may provide indications as to the source of the program or the nature of the tasks it is performing.I found this answer on askubuntu, but it's valid for Unix: ![]() Examine the process arguments, title and working directory. If it has a consistent cadence (for example if it runs monthly or quarterly), it might be part of a monthly or quarterly business or maintenance process. If this process only manifested recently, it might be part of a new software package. Is this network activity part of an expected workflow for the user who ran the program? Consider the user as identified by the username field. If the destination IP address is remote or external, does it associate with an expected domain, organization or geography? Note: avoid interacting directly with suspected malicious IP addresses. ![]() Are these used by normal but infrequent network workflows? Are they expected or unexpected? Here are some possible avenues of investigation: # Investigating Unusual Network Activityĭetection alerts from this rule indicate the presence of network activity from a Linux process for which network activity is rare and unusual.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |