threat generic:5llion.com generic:conti.news

cancel
Showing results for 
Search instead for 
Did you mean: 

threat generic:5llion.com generic:conti.news

L3 Networker

How to block this “unknown“ event to the customer that contains the threat generic:5llion.com (408607164). Because this threat is categorized as DNS Signature, the event had the destination port 53

 

 

2 ACCEPTED SOLUTIONS

Accepted Solutions

L4 Transporter

Hi @NavidAlam thank you for posting question.

 

Do you need to change action specifically for DNS Threat ID: 408607164 to action block? When it comes to DNS signatures the action is set for all signatures under Anti-Spyware Profile > DNS Signatures > Policies & Settings. The option for Exceptions per signature bases is only for excluding signature from enforcement. There is no other configuration option to change action based on signature. Based on screen shot you have provided, the action is already: sinkhole. I think in this case there is no action needed as this has been forged with sinkhole IP address. Have you configured a rule to block: sinkhole.paloaltonetworks.com ?

 

Kind Regards

Pavel 

Pavel Kucera

View solution in original post

L4 Transporter

Hello @NavidAlam 

 

The final action for the DNS query is blocked as the action is a sinkhole. That means when a device will try to resolve the IP address for the known bad site, a sinkhole address ( dead end) is provided. 
That way you can identify if which device is trying to reach a bad site, and the connection is never successful. 

Sinkhole and block are parallel actions, not in sequence. 

 

I hope this helps.

 

Himani

Himani Singh

View solution in original post

3 REPLIES 3

L3 Networker

2021-09-07_11-00-18.png

L4 Transporter

Hi @NavidAlam thank you for posting question.

 

Do you need to change action specifically for DNS Threat ID: 408607164 to action block? When it comes to DNS signatures the action is set for all signatures under Anti-Spyware Profile > DNS Signatures > Policies & Settings. The option for Exceptions per signature bases is only for excluding signature from enforcement. There is no other configuration option to change action based on signature. Based on screen shot you have provided, the action is already: sinkhole. I think in this case there is no action needed as this has been forged with sinkhole IP address. Have you configured a rule to block: sinkhole.paloaltonetworks.com ?

 

Kind Regards

Pavel 

Pavel Kucera

View solution in original post

L4 Transporter

Hello @NavidAlam 

 

The final action for the DNS query is blocked as the action is a sinkhole. That means when a device will try to resolve the IP address for the known bad site, a sinkhole address ( dead end) is provided. 
That way you can identify if which device is trying to reach a bad site, and the connection is never successful. 

Sinkhole and block are parallel actions, not in sequence. 

 

I hope this helps.

 

Himani

Himani Singh

View solution in original post

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!