Hi Rengar,
There are two reasons for the high CPU usage caused by security policy modification, addition, and deletion.
1. The session update process is triggered. The current concurrent sessions go through the new process, which causes high CPU usage in a short period of time.
2. When a security policy is added, it is traversed to match the security policy in a short period of time, instead of index mapping. The process of traversing non-accelerated search policies consumes CPU resources. The more concurrent sessions, the more likely the CPU usage increases.
Check the number of policies on the device. If the number of policies exceeds 100, you are advised to enable policy backup acceleration.
policy accelerate standby enable
I hope it helps!