--- title: "Add the condition for string pattern match" slug: "add-the-condition-for-string-pattern-match-2" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:30:59Z published: 2026-11-19T12:30:59Z canonical: "docs.trellix.com/add-the-condition-for-string-pattern-match-2" --- > ## 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. # Add the condition for string pattern match Steps to add the condition to the example signature: 1. **Condition 1** is added automatically according the URL you provided. 2. Click **Condition 1** so that it is highlighted. 3. Click **AND** in the Comparisons section. The **Add AND Comparision** dialog opens. **String Pattern Match**![String Pattern Match](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-0704b9cb-6ff9-e965-b8f4-1ae9a2953229(7).png?sv=2026-02-06&spr=https&st=2026-11-20T16%3A35%3A01Z&se=2026-11-20T17%3A35%3A01Z&sr=c&sp=r&sig=1kiyegiA0l22B7ZVtk6HSJ6BjJqJmSicmM0mzmHxLMs%3D) 4. For this example, select **String Pattern Match** in the **Comparison Type** drop-down menu. 5. Select **http** from the **Protocol** drop-down menu. Because you selected HTTP, the Custom Attack Editor displays the HTTP-specific protocol fields on the following screen. 6. Configure the fields for the comparison you have chosen. For this example, specify **req-uri** for the **Protocol Field**. This specifies that the Sensor should search in the URI of the request packet. 7. Select **get** as the http request method. 8. From the drop-down list in the Regular Expression **Operator** section, select the matching criteria as **Equals** which means that the comparison criteria must be equal to the regular expression entered. 9. Type the pattern to match in the **Text to Match** text box. For this example, the pattern to match is "LpEhZWWuLc0AwAAeHB3DAAAABA". 10. Click ![GUID-1C393536-5E83-4665-9BCD-59D156B85B94-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-1ba38dbb-5442-169b-aa15-602a95a24aac(8).png?sv=2026-02-06&spr=https&st=2026-11-20T16%3A35%3A01Z&se=2026-11-20T17%3A35%3A01Z&sr=c&sp=r&sig=1kiyegiA0l22B7ZVtk6HSJ6BjJqJmSicmM0mzmHxLMs%3D) to verify that your expression is a valid string, and all required options are represented. Click **OK** to close the validation message window. 11. (Optional) Deselect **Ignore Case** and **Ignore String Position** check boxes. 12. Click **Save**. Your comparison appears under **Condition 1**. 13. Click **Add** in the **New Custom Attack** window. 14. Verify that the attack definition is listed on the **Native Trellix IPS Format** tab. ![GUID-5BD5AE4C-6A0F-46F5-B6C1-A9A7A1B768CA-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-acf4200c-c831-a9c0-787d-86c57b25caef(7).png?sv=2026-02-06&spr=https&st=2026-11-20T16%3A35%3A01Z&se=2026-11-20T17%3A35%3A01Z&sr=c&sp=r&sig=1kiyegiA0l22B7ZVtk6HSJ6BjJqJmSicmM0mzmHxLMs%3D) 15. Click **Save** to save the Trellix IPS Custom Attack in the Manager server database. 16. Make sure the Trellix IPS Custom Attack is saved in the database and also published in the policies.