
dse7i (dse7i) asked a question.
We would like to turn on enforcement for Threat Insights, but want to exclude our office egress IPs from getting blocked.
Is there a way for us to continue to have Threat Insights in audit/logging mode for our offices using excluded networks while it runs in blocked/enforced mode for other IPs?

Yes. Create a network zone (Security -> Networks) that contains the public IPs for your office, then add that zone to the Exempt Zones list in the Threat Insight configuration.
I thought doing that would also have them ignored from logging/audit mode.
All connections are logged, so excluding your office IPs from Threat Insight doesn't mean your office connections won't get logged. They'll just bypass the Threat Insight processing. We've had blocking enabled for at least a year now, and it works great.
Ah thats the subtle difference. I would still want Threat Insights processing/alerting for our offices. It'd be good to know if we had a compromised box in our network that was trying to brute force our okta tenant.
That's not really how Threat Insight works. Think of it as a large, constantly updating database of IP addresses that have a history of bad behavior. Whenever a client attempts to connect to your org, Okta compares the incoming connection's IP address against the IP addresses in the database, and if it finds a match (and you have blocking turned on), it blocks that incoming connection at the router level, before the client can even get to your org's login page.
For threats from internal users, take a closer look at rate limit monitoring. A brute force attack from inside is more likely to be detected - and stopped - by the rate limits on the Okta API endpoints.