When an employee account is compromised, financial data is at immediate risk. This guide walks you through the steps to contain the breach, secure your systems, and prevent future incidents. You’ll learn how to act quickly and methodically to protect sensitive information.
What You’ll Need
- Access to your identity provider (IdP) or Active Directory admin console
- Access to your email and financial system admin panels
- A list of employees with access to financial data
- Incident response plan (if available)
- Communication channels (email, Slack, etc.)
Step-by-Step
- Immediately revoke the compromised account’s access. Log into your IdP or Active Directory and disable the account. This stops the attacker from using it. If you use SSO, disabling the account there will block access to all connected apps.
- Force a password reset and revoke sessions. After disabling, force a password reset for the user. Also revoke all active sessions and tokens. In Azure AD, go to the user’s profile and select “Revoke sessions.” In Google Workspace, use “Force logout.” This ensures any stolen credentials are useless.
- Reset the user’s MFA. Remove and re-enroll the user’s multi-factor authentication. This ensures any attacker-registered devices are removed.
- Review and revoke OAuth permissions. Check what third-party apps have access to the account. Revoke any that are not explicitly approved. Attackers often use malicious OAuth apps to maintain access.
- Check for email forwarding rules. Attackers often set up forwarding rules to exfiltrate data. In Outlook or Gmail, check the compromised user’s settings for any forwarding rules. Remove any unknown rules.
- Audit financial system access. Log into your financial software (e.g., QuickBooks, Xero, SAP). Check for any recent changes to bank accounts, payment methods, or vendor information. Look for new users or changed permissions.
- Scan for malware on the employee’s device. The compromise may have started with malware. Run a full antivirus scan on the employee’s computer. If you have EDR, review alerts for that device.
- Notify your incident response team and relevant stakeholders. If you have an incident response plan, activate it. Inform your IT team, legal, and management. If you have cyber insurance, contact your provider.
- Preserve evidence. Take screenshots of the account settings, login logs, and any suspicious activity. This is crucial for forensic analysis and potential legal action.
- Restore the account after verification. Once you have cleaned the device and confirmed the account is secure, you can re-enable it. Have the user log in from a known-good device, reset their password, and re-enroll MFA.
- Monitor financial transactions closely. For the next 30-60 days, monitor all financial transactions for unusual activity. Set up alerts for large or unusual transfers.
- Conduct a post-incident review. After the incident is contained, review what happened. Update your security policies and training to prevent similar incidents.
Common Mistakes
- Only resetting the password. This is not enough. The attacker may have other access methods like OAuth tokens or session cookies.
- Not checking email forwarding rules. This is a common exfiltration method. Always check.
- Re-enabling the account too quickly. Ensure the device is clean and the account is properly secured before re-enabling.
- Ignoring the financial system. The attacker may have already changed bank details. Always audit financial systems immediately.
- Not preserving evidence. If you clean up without taking screenshots, you lose valuable forensic data.
Tips
- Use a break-glass account. Have a separate, highly protected admin account that is not used for daily work. Use this to perform emergency actions.
- Enable conditional access policies. Require MFA for all users, and block access from risky IPs or devices.
- Implement a zero-trust model. Assume every account is compromised. Require MFA for every access, and use just-in-time access for sensitive data.
- Train employees to recognize phishing. Most account compromises start with phishing. Regular training can prevent many incidents.
- Have a written incident response plan. This saves time and reduces panic during a real incident.
Troubleshooting
If you cannot disable the account via the IdP: Contact your IdP’s support immediately. In the meantime, change the account’s password in the on-premises directory if you have one, and block the user in your firewall or proxy.
If the attacker has already changed financial details: Contact your bank or financial institution immediately to reverse any unauthorized transactions. Work with your finance team to restore correct vendor information.
If you suspect the attacker has access to other accounts: Perform a full audit of all admin accounts. Check for any new accounts created recently. Look for unusual login patterns across your organization.
If the employee’s device is infected and you cannot clean it: Reimage the device from a known-good backup. Do not re-enable the account until the device is clean.
Frequently Asked Questions
How quickly should I disable the account?
Immediately. Every minute the account is active gives the attacker more time to exfiltrate data or cause damage.
Should I tell the employee their account was compromised?
Yes, but after you have secured the account. Explain what happened and what you are doing. The employee may have information about how the compromise occurred.
What if the attacker changed the password before I could act?
You can still disable the account via your IdP or Active Directory. You can also force a password reset as an admin.
How do I check for OAuth permissions?
In Azure AD, go to Enterprise applications and review the user’s app permissions. In Google Workspace, go to the user’s security settings and review third-party access.
Can I prevent this from happening again?
While you cannot prevent all attacks, you can significantly reduce risk with MFA, conditional access, regular security training, and monitoring for suspicious activity.
Do I need to report this to any authority?
Depending on your industry and location, you may have legal obligations to report data breaches. Check with your legal team.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Don’t Steal the Bobo Codes? Meaning & Origin6.00 min/km
- Best Game Server Hosting for Smooth Gameplay
- Emulating Sega Dreamcast on Mac: Full Guide
- Jump Stars Codes: Active Codes & How to Redeem
- Google Backup: What It Backs Up and How It Works
- Arcane Odyssey Codes: Full List & How to Redeem