This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About ktague
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About ktague
04-05-2023
24Posts
0Likes
0Solutions
Apr 05, 2023Last Visited
User
Activity
User
Profile
Latest posts by ktague
| Subject | Views | Posted |
|---|---|---|
| 2953 | 04-11-2018 02:37 PM |
User Badges
Community Statistics
| Member Since | 02-18-2016 08:49 AM |
| Date Last Visited | 04-05-2023 02:04 PM |
| Posts | 24 |
04-11-2018
02:37 PM
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!
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
04-05-2023
02:04 PM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks