About ramyfrahman

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.     ... View more

If you have an AWS EC2 instance with 443 exposed to the internet, you would get an alert but what would be a good way to validate that a particular instance has a WAF protecting it?  One thing I was thinking of would be to do a joins looking at the EC2 security group API and the AWS WAF API but is there some other way we can look through a cloud config that would look for this?  I understand you can't run joins across network and config queries but the use case is pretty valid when you have large cloud teams that are constantly doing testing and making things exposed publicly exposed with a compensating control.  In this example I wouldn't have access to the actual resource to deploy a Defender and use the WAAS which is part of the reason we need to look for the cloud native WAF in say AWS or Azure.  Thanks in advance. ... View more