Forum Discussion
Importing and exporting the same policy via python leads to differences in the policy
Hello,
I am currently looking to import multiple policies automatically. Therefore, I wrote a script using the python SDK to accomplish this. To make sure the import works fine, I checked for a diff after importing the policy and then manually exporting it. It looks like there are several new signatures inside the imported and exported policy's xml. I guess it's due to new signatures being added and automatically inserted into imported policies? Is that the case?
Thank you very much!
Cheers,
Daniel
If the ASM device you are importing the policies too have a newer attack signature update than the system you pulled the ASM policies from, then it is possible that newer attack signatures have been added to the signature sets that you have applied to those policies and that will account for the difference in attack signatures between the two copies of the same policies.
- Romani_2788Historic F5 Account
If the ASM device you are importing the policies too have a newer attack signature update than the system you pulled the ASM policies from, then it is possible that newer attack signatures have been added to the signature sets that you have applied to those policies and that will account for the difference in attack signatures between the two copies of the same policies.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com