AI Security Masters E7:
How CPR Broke ChatGPT's Isolation and What It Means for You
Blueprint Architecture for Securing
The AI Factory & AI Data Center
Call For Papers
Your Expertise. Our Stage
Good, Better, Best:
Prioritizing Defenses Against Credential Abuse
Ink Dragon: A Major Nation-State Campaign
Watch HereCheckMates Go:
CheckMates Fest
Dear Folks,
After migrating the rulebase from R81.10 to a new Smart-1 appliance with R81.20, all rules were "Created by: System" and shows the date of the migration, instead of the day, when the rule originally was created.
Please see attached screenshot.
Is there a way to get the old, original information's back?
Best regards,
Christian
Dear Folks,
After migrating the rulebase from R81.10 to a new Smart-1 appliance with R81.20, all rules were "Created by: System" and shows the date of the migration, instead of the day, when the rule originally was created.
Please see attached screenshot.
Is there a way to get the old, original information's back?
Best regards,
Christian
Dear Folks,
After migrating the rulebase from R81.10 to a new Smart-1 appliance with R81.20, all rules were "Created by: System" and shows the date of the migration, instead of the day, when the rule originally was created.
Please see attached screenshot.
Is there a way to get the old, original information's back?
Best regards,
Christian
Dear Folks,
After migrating the rulebase from R81.10 to a new Smart-1 appliance with R81.20, all rules were "Created by: System" and shows the date of the migration, instead of the day, when the rule originally was created.
Please see attached screenshot.
Is there a way to get the old, original information's back?
Best regards,
Christian
Never had that happen before...you see this on every single rule?
Andy
Never had that happen before...you see this on every single rule?
Andy
Never had that happen before...you see this on every single rule?
Andy
Me too!! never heard this kind of scenario.
Me too!! never heard this kind of scenario.
Me too!! never heard this kind of scenario.
Yes, it is on every single rule. The "Date created" is also the same on every rule - only the time differs a little bit.
What is more strange, only one CMA is affected. All other CMA's are fine, they have the correct Date/Time and CreatedBy...
Yes, it is on every single rule. The "Date created" is also the same on every rule - only the time differs a little bit.
What is more strange, only one CMA is affected. All other CMA's are fine, they have the correct Date/Time and CreatedBy...
Yes, it is on every single rule. The "Date created" is also the same on every rule - only the time differs a little bit.
What is more strange, only one CMA is affected. All other CMA's are fine, they have the correct Date/Time and CreatedBy...
JozkoMrkvicka
JozkoMrkvicka
JozkoMrkvicka
I also noticed that all objects and rules were changed by "System" at the time of upgrade of MDS. It is also present while upgrading to R81.10.
At least I know that the object/rule was not modified after the upgrade 😄
What kind of upgrade you used ?
I also noticed that all objects and rules were changed by "System" at the time of upgrade of MDS. It is also present while upgrading to R81.10.
At least I know that the object/rule was not modified after the upgrade 😄
What kind of upgrade you used ?
I also noticed that all objects and rules were changed by "System" at the time of upgrade of MDS. It is also present while upgrading to R81.10.
At least I know that the object/rule was not modified after the upgrade 😄
What kind of upgrade you used ?
I used "migrate_server export" and ".... import" from R81.10 with an actual Jumbo to R81.20.
Only one domain is effected. In my case it is the main domain with my VS0 system...
Maybe it depends on where VS0 is....
I used "migrate_server export" and ".... import" from R81.10 with an actual Jumbo to R81.20.
Only one domain is effected. In my case it is the main domain with my VS0 system...
Maybe it depends on where VS0 is....
I used "migrate_server export" and ".... import" from R81.10 with an actual Jumbo to R81.20.
Only one domain is effected. In my case it is the main domain with my VS0 system...
Maybe it depends on where VS0 is....
