--- title: "Create an attack definition for packet grep protocol match" slug: "create-an-attack-definition-for-packet-grep-protocol-match" tags: ["Product Usage", "IPS 10.1.10"] updated: 2026-09-06T12:33:03Z published: 2026-10-05T15:41:20Z canonical: "docs.trellix.com/create-an-attack-definition-for-packet-grep-protocol-match" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Create an attack definition for packet grep protocol match This scenario is about creating a Custom Attack Definition that uses packet grep protocol match to detect if the DNP3 protocol contains a specific character sequence. In order to write a proper Native Trellix IPS Format Custom Attack for this example, you must identify several key elements: - Application protocol: dnp3 - Packets to parse: Request Packets Only - Text to match: \x00\x00\x00\x3a\x20\x45\x56\x00\x0a To create the attack definition for this example: ## Task 1. In the Custom Attack Editor, click ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-F3F18CF8-B95D-4C8C-8DB8-996CDB6087FB-low.png?sv=2026-02-06&spr=https&st=2026-11-22T17%3A05%3A01Z&se=2026-11-22T18%3A05%3A01Z&sr=c&sp=r&sig=WkW%2FFQpUHqPHQkoqo5oQ6SCO5beC7z59NFyV8YFT6Ko%3D). The **New Custom Attack** interface opens. ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-3EB7CCB4-A36F-41F8-BB0D-1EC2405A7B00-low.png?sv=2026-02-06&spr=https&st=2026-11-22T17%3A05%3A01Z&se=2026-11-22T18%3A05%3A01Z&sr=c&sp=r&sig=WkW%2FFQpUHqPHQkoqo5oQ6SCO5beC7z59NFyV8YFT6Ko%3D) 2. Select one of the options from the **State** drop-down menu. 3. You can specify a name such as "Custom Exploit: Packet Grep Protocol Match" as the **Name**. The letters "UDS" (user-defined signature) are appended to the front of the name upon completion; thus, this attack appears as "UDS-Custom Exploit: Packet Grep Protocol Match" in the Custom Attack Editor, as well as the attack database when you save in the Manager server. 4. Type a description for your attack. This area can be used for your notes or other specific information pertinent to your new attack. 5. You can select **Medium (5)** as the **Severity** because this example scenario does not necessarily involve malicious activity. 6. Select **Advanced Protection Options/Web Application Server** as the **Protection Category**. 7. Select **Custom Exploit (Signature Based)** from the **Detection Type** drop-down menu for the attack. 8. Click **Next**. ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-0B2936AA-6016-4E2A-AF52-5FB77B970543-low.png?sv=2026-02-06&spr=https&st=2026-11-22T17%3A05%3A01Z&se=2026-11-22T18%3A05%3A01Z&sr=c&sp=r&sig=WkW%2FFQpUHqPHQkoqo5oQ6SCO5beC7z59NFyV8YFT6Ko%3D) 9. Select **Client or Server** as **Attack Target**. 10. Select **Attack Packet Only** as **Blocking (As Applicable)**. 11. In the **Matching Criteria** section, select **Protocol** as the **Criterion** and select **pktsearch** as the protocol. ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-D886D376-714A-4375-B5D3-FE895A8C90EA-low.png?sv=2026-02-06&spr=https&st=2026-11-22T17%3A05%3A01Z&se=2026-11-22T18%3A05%3A01Z&sr=c&sp=r&sig=WkW%2FFQpUHqPHQkoqo5oQ6SCO5beC7z59NFyV8YFT6Ko%3D) 12. Attack details configuration is complete. Continue to create signature.