Unusual server port activity Internal Alerts Potential False Positives

Retired Member — Mon, 23 Nov 2020 17:24:34 GMT

I have the thresholds for Unusual Server Port Internal activity set to the most conservative settings to minimize false positives but it seems like the highest port consistently gets flagged as "unusual". In the example below there are 15 ports labeled as usual and the Kafka port (9092) is being flagged as unusual. Upon further investigation we always find out that this is the intended purpose and traffic volumes support that this is normal activity. For example another similar alert was fired off on MongoDB but going into the investigate tab I can see months and hundreds of Gb of Mongo DB traffic so it should NOT have flagged this traffic coming from a host labeled as MongoDB (not that the naming convention has anything to do with it but I had to figure out if the resource this was connected to was legit a MongoDB server and client).

I may enter a feature request to give "allowed ports" check box based on alerts generated for Unusual server port Internal.

Re: Unusual server port activity Internal Alerts Potential False Positives

AKing9 — Fri, 12 Aug 2022 14:38:00 GMT

Greetings Ramyfrahman,

I hope that this note finds you well! I know that it has been a while since you had posted this question but I wanted to see if you still potentially needed any help. Thank you for your time and I hope that you have a good remainder of your day.

Kind Regards,

J. Avery King

topic Unusual server port activity Internal Alerts Potential False Positives in Prisma Cloud Discussions

Unusual server port activity Internal Alerts Potential False Positives

Re: Unusual server port activity Internal Alerts Potential False Positives