Custom Signature to Detect Weak Cipher Negotiation in Phase 1 ISAKMP Negotiation

Reply
Highlighted
L2 Linker

Custom Signature to Detect Weak Cipher Negotiation in Phase 1 ISAKMP Negotiation

Good Afternoon,

    Is it possible to create a custom threat signature or APP-ID to match various strings of data inside of the ISAKMP initial payload during the IPSec phase 1 negotiation. The first packets are sent in plaintext during the negotiation. This would be done in order to determine if a weak cipher is being used during tunnel initiation. 

Example:

ISAKMP Packet:

Payload: Proposal -> Payload: Transform -> 

IKE Attribute -> :Hash-Algorithm: SHA 
IKE Attribute -> :Group-Description 

Pattern Match on Hash-Algorith and Group-Description specification.

.*(Group-Description:).*((group 1)|.*(1024-bit))
.*(Hash-Algorithm:).*((SHA)|.*(3DES))

The first expression looks for 'Group-Description:' followed by the word 'group 1' or '1024-bit' for example. The second expression looks for 'Hash-Algorithm:' followed by the word 'SHA' or '3DES'.

Screenshot example attached. Any guidance would be appreciated, Thanks!

Highlighted
L0 Member

thank you so much

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 Live Community as a whole!

The Live Community thanks you for your participation!