08-21-2019 12:19 PM - last edited on 09-02-2020 10:19 AM by kwadsack
I’m looking at some rules that detect traffic on ports and it seems to flag a lot of traffic to AWS resource like the NAT gateway that we do not control.
Is it possible to exclude these based on the resource type?
For example:
Remove Network - Internet traffic over insecure port (22)
Exclude Network - Internet traffic (21,23,80,443,8444,8443,22)
How do I compose the RQL?
08-21-2019 12:21 PM
The RQL needs constraints to exclude NAT Gateway and ELB.
Please try:
network where src.ip=0.0.0.0 AND protocol=‘TCP’ AND dest.port not IN (21,23,80,443,8444,8443,22) AND source.publicnetwork IN ( ‘Internet IPs’ , ‘Suspicious IPs’ ) AND dest.resource IN ( resource where role not in ( ‘AWS NAT Gateway’ , ‘AWS ELB’ )
network where src.ip=0.0.0.0 AND protocol=‘TCP’ AND dest.port IN (21,22,23,80) AND source.publicnetwork IN ( ‘Internet IPs’ , ‘Suspicious IPs’ ) AND dest.resource IN ( resource where role not in ( ‘AWS NAT Gateway’ , ‘AWS ELB’ ) )
08-21-2019 12:21 PM
The RQL needs constraints to exclude NAT Gateway and ELB.
Please try:
network where src.ip=0.0.0.0 AND protocol=‘TCP’ AND dest.port not IN (21,23,80,443,8444,8443,22) AND source.publicnetwork IN ( ‘Internet IPs’ , ‘Suspicious IPs’ ) AND dest.resource IN ( resource where role not in ( ‘AWS NAT Gateway’ , ‘AWS ELB’ )
network where src.ip=0.0.0.0 AND protocol=‘TCP’ AND dest.port IN (21,22,23,80) AND source.publicnetwork IN ( ‘Internet IPs’ , ‘Suspicious IPs’ ) AND dest.resource IN ( resource where role not in ( ‘AWS NAT Gateway’ , ‘AWS ELB’ ) )
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
