Hello @AlexS.13183 (Customer)​ Thank you for posting on our Community page!

Yes, Okta does temporarily store (cache) the device signals and tags received via the Chrome Device Trust Connector (DTC).

Because Okta treats the Chrome DTC as an Endpoint Security/EDR integration, it handles the device context signals using its standard EDR caching mechanism.

Here is how long those tags are stored:

• Duration: The signals are cached in Okta for up to 8 hours or until the user's session times out, whichever occurs first.

Why you don't see it for every login: Because these signals are cached, Okta does not need to re-fetch and evaluate the Chrome_DTC tags on every single authentication attempt. If a user logs into another application within that 8-hour window and their Okta session is still active, Okta will simply use the cached trust signals. The cache is updated—and a new

Chrome_DTC

entry will appear in your System Log—whenever the cache expires, the session times out, or a specific app sign-in policy forces a fresh signal evaluation.

You can find the official documentation for this behavior in the Endpoint Security Integrations guide under the "How endpoint security integrations work" section.

Here is the direct link to the documentation:

Endpoint security integrations | Okta Identity Engine

Thank you for reaching out to our Community and have a great day!

--

Help others in the community by liking or hitting Select as Best if this response helped you.