diff mbox series

[3/3] Suricata: detect DNS events on port 853, too

Message ID 35331b2c-281e-f72f-fdd9-de8bfa592717@ipfire.org
State Accepted
Commit ad99f959e2b83dd9f1275c1d385140271c8926ae
Headers
Series [1/3] Suricata: detect TLS traffic on IMAPS/POP3S/SSMTP portsas, well |

Commit Message

Peter Müller Feb. 8, 2019, 4:47 a.m. UTC 
  As DNS over TLS popularity is increasing, port 853 becomes
more interesting for an attacker as a bypass method. Enabling
this port for DNS monitoring makes sense in order to avoid
unusual activity (non-DNS traffic) as well as "normal" DNS
attacks.

Partially fixes #11808

Signed-off-by: Peter Müller <peter.mueller@ipfire.org>
Cc: Stefan Schantl <stefan.schantl@ipfire.org>
---
 config/suricata/suricata.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Comments

Stefan Schantl Feb. 8, 2019, 7:34 a.m. UTC | #1 
Merged.

Best regards,

-Stefan
> As DNS over TLS popularity is increasing, port 853 becomes
> more interesting for an attacker as a bypass method. Enabling
> this port for DNS monitoring makes sense in order to avoid
> unusual activity (non-DNS traffic) as well as "normal" DNS
> attacks.
> 
> Partially fixes #11808
> 
> Signed-off-by: Peter Müller <peter.mueller@ipfire.org>
> Cc: Stefan Schantl <stefan.schantl@ipfire.org>
> ---
>  config/suricata/suricata.yaml | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/config/suricata/suricata.yaml
> b/config/suricata/suricata.yaml
> index d7302788c..67b9e8a7d 100644
> --- a/config/suricata/suricata.yaml
> +++ b/config/suricata/suricata.yaml
> @@ -208,11 +208,11 @@ app-layer:
>        tcp:
>          enabled: yes
>          detection-ports:
> -          dp: 53
> +          dp: "[53,853]"
>        udp:
>          enabled: yes
>          detection-ports:
> -          dp: 53
> +          dp: "[53,853]"
>      http:
>        enabled: yes
>        # memcap: 64mb
Michael Tremer Feb. 8, 2019, 11:51 p.m. UTC | #2 
Do we expect any plain DNS traffic on this port?

I am not sure if any rules would match the TLS traffic here.

> On 7 Feb 2019, at 20:34, Stefan Schantl <stefan.schantl@ipfire.org> wrote:
> 
> Merged.
> 
> Best regards,
> 
> -Stefan
>> As DNS over TLS popularity is increasing, port 853 becomes
>> more interesting for an attacker as a bypass method. Enabling
>> this port for DNS monitoring makes sense in order to avoid
>> unusual activity (non-DNS traffic) as well as "normal" DNS
>> attacks.
>> 
>> Partially fixes #11808
>> 
>> Signed-off-by: Peter Müller <peter.mueller@ipfire.org>
>> Cc: Stefan Schantl <stefan.schantl@ipfire.org>
>> ---
>> config/suricata/suricata.yaml | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>> 
>> diff --git a/config/suricata/suricata.yaml
>> b/config/suricata/suricata.yaml
>> index d7302788c..67b9e8a7d 100644
>> --- a/config/suricata/suricata.yaml
>> +++ b/config/suricata/suricata.yaml
>> @@ -208,11 +208,11 @@ app-layer:
>>       tcp:
>>         enabled: yes
>>         detection-ports:
>> -          dp: 53
>> +          dp: "[53,853]"
>>       udp:
>>         enabled: yes
>>         detection-ports:
>> -          dp: 53
>> +          dp: "[53,853]"
>>     http:
>>       enabled: yes
>>       # memcap: 64mb
diff mbox series

Patch

diff --git a/config/suricata/suricata.yaml b/config/suricata/suricata.yaml
index d7302788c..67b9e8a7d 100644
--- a/config/suricata/suricata.yaml
+++ b/config/suricata/suricata.yaml
@@ -208,11 +208,11 @@  app-layer:
       tcp:
         enabled: yes
         detection-ports:
-          dp: 53
+          dp: "[53,853]"
       udp:
         enabled: yes
         detection-ports:
-          dp: 53
+          dp: "[53,853]"
     http:
       enabled: yes
       # memcap: 64mb