I rarely use this account anymore, but due to the potential #Okta breach here are some SIEM rules which could potentially be useful running back over the past 90 days of data if you can.
Here are some detections / preventions in response to the DarkSide findings.
INITIAL COMPROMISE
Password attacks on perimeter. 2FA everything. Set lockout thresholds on logins. Ingest logs to SIEM and monitor for brute force attempts and impossible travel.
1/14
TeamViewer / Anydesk. Create a SIEM rule and / or run threat hunt for ports in below thread. Try to pick one remote access for your organisation, block the rest.
Dashboards. Yes, your security team has dashboards, but have you thought of creating ones to be used by Networking, Desktop Support and other teams? Ask them what dashboards could be useful, and provide them access to the SIEM which only allows access to these dashboards.
2/6
Threat Hunting. There are bountiful threat hunting resources online - Perform these threat hunts on your SIEM logs! This could find things your alerts or analysts have missed; and can lead to future detection opportunities.
3/6
25494 of the URLs end with Mozi.m, relating to the Mozi Botnet - securityintelligence.com/posts/botnet-a…. To detect this, we can look for the regex pattern .*Mozi\.m$
A further 4636 of the URLs end with Mozi.a, related to the above. We can detect this using regex pattern .*Mozi\.a$
Finally, there are 10 URLs which contain Mozi within them in different patterns to above. It is therefore worthwhile searching for any case of Mozi within a URL (This will be greedier than the above, but still worthwhile checking)