Hypothetical scenario — illustrative, not a customer story
How it could unfold
- A support staff password is guessed.
- It works because no MFA is registered on that account.
- The attacker reads client email and creates a forwarding rule.
- Matter details leave the firm.
Warning signs visible from outside
- MFA registration is not complete across all accounts.
- Legacy authentication blocked (flagged when it is not).
What PixelPrivate would have shown you
Legacy authentication blocked (flagged when it is not)
Shown by the Microsoft 365 connector.
MFA registration coverage
Lists accounts that have not registered MFA.
External forwarding rule (indicator for review)
Rules for review. We cannot tell who made them.
What you would do
- Register MFA for every account.
- Block legacy authentication.
- Review forwarding rules.
Honest limits
PixelPrivate can show the exposures listed above. It cannot guarantee that an incident would not happen, and it cannot see anything outside its checks. PixelPrivate does not detect intrusions or fraud. This scenario describes no real company, person, quote or statistic.
