Security monitoring.
Using activity logs to detect suspicious behavior and protect the app
Activity logs are your first tool against security threats. Monitor authentication events, detect suspicious patterns, and respond to potential attacks.
Why security monitoring matters
Your installation contains sensitive business data and customer information. Activity logs help you:
- Detect brute-force attacks: Multiple failed login attempts
- Identify compromised accounts: Unusual activity patterns
- Track unauthorized access attempts: Failed logins from unknown locations
- Monitor suspicious behavior: Unusual deletion or modification patterns
- Meet compliance requirements: Maintain security audit trails
Monitoring failed login attempts
Failed logins are often the first sign of a security threat.
Viewing failed login statistics
- Navigate to Analytics in the admin sidebar
- Scroll to the Authentication Statistics section
- Review the Failed Logins count
What to look for:
- Sudden spikes: Sharp increases in failed attempts
- Consistently high numbers: Ongoing attack attempts
- Patterns: Regular failed attempts at specific times
Investigating failed logins
When you notice suspicious failed login activity:
- Navigate to Activity logs in the admin sidebar
- Set Event filter to "Login Failed"
- Review the results table
For each failed login, check:
- Date/Time: When did it happen?
- User: Which account was targeted?
- IP Address: Where did the attempt come from?
Identifying attack patterns
Click on individual failed login records to see details:
Brute-Force Attack Signs:
- Multiple failed attempts from the same IP address
- Attempts targeting the same user account
- Rapid succession of attempts (minutes apart)
- Attempts from unusual geographic locations
Credential Stuffing Signs:
- Failed attempts across multiple user accounts
- Attempts from the same IP address
- Different usernames but similar patterns
Taking action
If you identify a security threat:
- Block the IP address at your server/firewall level
- Contact affected users if their accounts were targeted
- Require password resets for compromised accounts
- Add a second factor in front of admin accounts through your own SSO, VPN, or reverse-proxy auth
- Monitor ongoing to ensure the threat has stopped
Monitoring successful logins
Track successful authentications to spot compromised accounts.
Unusual login patterns
- Navigate to Activity logs in the admin sidebar
- Set Event filter to "Login"
- Review recent successful logins
Red flags:
- Logins from unexpected locations (check IP address)
- Logins at unusual times (middle of the night)
- Multiple logins in rapid succession
- Logins from different locations within minutes
Investigating suspicious logins
Click on a login record to view:
- IP Address: Does it match the user's normal location?
- User Agent: Is the device/browser familiar?
- Time: Is this a normal time for this user?
If a login looks suspicious:
- Contact the user to verify it was them
- If unauthorized, reset their password right away
- Review their recent activity for unauthorized changes
Monitoring deletion activity
Unusual deletion patterns can indicate malicious behavior or compromised accounts.
Tracking deletions
- Navigate to Activity logs in the admin sidebar
- Set Event filter to "Deleted"
- Review what's being deleted
Warning signs:
- Mass deletions: Many records deleted in a short time
- Critical data: Important cards, rewards, or members deleted
- Unusual users: Deletions by accounts that don't normally delete
- After-hours activity: Deletions at odd times
Setting up regular security checks
Create a routine security monitoring schedule:
Daily checks (5 minutes)
- Open Analytics in the admin sidebar
- Review Authentication Statistics
- Check for spikes in failed logins
- Review Recent Activity for anything unusual
Weekly checks (15 minutes)
- Review Failed Logins for the past 7 days
- Check Most Active Users for unexpected accounts
- Filter deletions and review critical records
- Export logs for compliance records
Monthly checks (30 minutes)
- Analyze Activity Timeline for unusual patterns
- Review User Types Breakdown for anomalies
- Check all failed logins from the past month
- Generate security report for stakeholders
Best practices
| Practice | Description |
|---|---|
| Review IP addresses | Every log entry records the request IP; review them to trace attack sources |
| Monitor Admin Accounts | Admin accounts have the most power; keep a close watch on them |
| Restrict admin access by IP | Allowlist known IPs for /admin at the web server or firewall level |
| Set up external alerts | Point your own monitoring at the logs for threshold-based alerts; the app sends no alerts itself |
| Regular Exports | Export logs each month for long-term analysis |
| Educate Users | Train on strong passwords and phishing recognition |
| Add a second factor externally | Enforce it in front of the app (SSO, VPN, or reverse-proxy auth); there is no per-account 2FA switch |
Related topics
- Activity logs overview: Introduction to activity logging
- Activity analytics: Visual insights and metrics
- Viewing logs: Search and filter details