What happened?
On December 11, 2023, we were made aware of an issue where a recent inspector update introduced a bug where Microsoft 365 parent data was replicated into child Microsoft 365 inspectors. This happened for child inspectors that haven't switched to using GDAP permissions and haven't been active since we stopped supporting application permissions in May 2023.
Who Is affected?
This issue only affects any partners with active Microsoft 365 child Inspectors that have NOT been configured with Microsoft GDAP.
What is the impact to affected partners?
The potential impact for affected Partners includes the following scenarios between the dates 12/7 and 12/11:
End customers have access to their environment information in Liongard. In this scenario, those customers may have been able to view the mirrored parent inspector data in the child inspector assigned to their environment.
Liongard data was consumed by a partner-authorized third-party system/integration, such as a PSA. If data was sent from Liongard to a third-party system for the M365 inspector during this time, it would still be in the third-party system and should be removed.
Reports containing M365 child inspector data that was exported or shared. Reports generated during this time period may contain inaccurate data.
What did Liongard do to resolve this?
As soon as we became aware of the issue, we immediately prevented inspectors from running without the GDAP auth token, which prevented further mirrored timeline entries for the impacted inspectors.
We also removed all incorrect data from the platform, which includes inspector timelines, Actionable alerts, and change detections.
What action do I need to take?
Data sent to third-party systems should be reviewed, and any erroneous data from this period should be removed.
We greatly appreciate your patience and understanding during this issue. If you have any further questions or concerns, please do not hesitate to contact our support team.