Windows Security Center ZTA Score is Not Sent to Okta
Last Updated:
Overview
When having Endpoint Security set up with Windows Security Center, the Windows Security Center startup settings must match with the Okta Verify startup settings. Otherwise, the ZTA score will be missing from the authentication request.
Applies To
- Endpoint Security
- Okta Identity Engine (OIE)
- Authentication policy
Cause
Depending on the Security Center service configuration, the Windows Security Center can start Automatic/Automatic (Delayed Start)/Manual /Disabled. This can cause the service to not be active at the time of the Okta Verify probing, resulting in the ZTA score being null.
Solution
Since the service is Log On as a Local Service account, the admin/user is unable to make changes from the service itself, so in this case, they will need to make the changes in the Registry.
- In the Registry Editor, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc. - To make sure the Windows Security Center starts when login into the Windows device, please make sure the following 2 registers are set as follows:
- Set the Start register Value data to 2 (Automatic(Delayed start)).
- Set the DelayedAutoStart Value data to 0 (without delay).
