Hi lra,
Thank you for your reply, there is no new strategy application recently.
After investigation, I found that the HTTP request parameters of several URLs are too long. I guess that the HTTP request parameters may be too long to match the "Recommended signatures Policy for Web Applications" or "Web Correlation Policy", which has timed out, resulting in high CPU usage.
------------------------------
Shoulin Yan
Hope
beijing CAM
------------------------------
Original Message:
Sent: 08-06-2020 01:08
From: Ira Miga
Subject: regexp match error match time limit
Hi Shoulin,
Also you can check if recently new policies have been applied that could have caused this.
The CPU can be high since the processed traffic has extremely large parameters.
You can create an exception to the policy to ignore extremely large parameters to see if it solves the issue.
But then you should find the problem and delete the exception.
Best,
------------------------------
Ira Miga
Imperva
Knowledge Engineer
Original Message:
Sent: 08-05-2020 13:42
From: Christopher Detzel
Subject: regexp match error match time limit
@Shoulin Yan, That's a difficult question to answer without divulging information that someone can leverage to bypass inspection. I recommend they open a support ticket. You can login here.
------------------------------
Christopher Detzel
Community Manager
Imperva
Original Message:
Sent: 08-05-2020 11:27
From: Shoulin Yan
Subject: regexp match error match time limit
Hello,
I encountered a problem: /var/log/messages has a lot of "regexp match error match time limit" error messages, and the gateway' CPU usage is very high, but the processed traffic is very small. How should I do ?
#On-PremisesWAF(formerlySecuresphere)
------------------------------
Shoulin Yan
Hope
beijing CAM
------------------------------