This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Require Token with Safeguard

nf over 7 years ago

Currently using Safeguard and Safenet tokens. Have established policies that require token at login, however after logging into windows users is able to remove token, lock the screen and log back into windows without the need for the token. Is there a way to stop that? kind of defeats the purpose of our MFA solution if the token is not needed anymore.

This thread was automatically locked due to age.

Parents

0 Typhoon87 over 7 years ago

I am actually seeing a similar issue here.

I had to create some new policy's for machines with skylake processors since the tokens no longer work at POA which is a whole separate annoying issue on its own that needs fixed. The issue is when I did that we had to allow username/password at POA but now I am unable to make the safenet software FORCE token login at the windows cont-alt-delete screen users are able to log in without a token. All the Group policy options for the token software are the same just inheriting to a new sub ou. For the life of me I am unable to figure it out.

I have a question then does this option also control windows logon even though the description only says POA?
Cancel
Vote Up 0 Vote Down

Cancel
0 Haridoss Sreenivasan over 7 years ago in reply to Typhoon87

Hi Typhoon87

What is the OS on the machine, where the Token is not working? Please refer to the article SafeGuard Enterprise 8: Supported middleware, tokens and smart cards to confirm that your token is supported.

Haridoss Sreenivasan
Technical Support Engineer | Sophos Technical Support
Knowledge Base | @SophosSupport | Video tutorials
Remember to like a post. If a post (on a question thread) solves your question use the 'This helped me' link.
Cancel
Vote Up 0 Vote Down

Cancel
0 nf over 7 years ago in reply to Haridoss Sreenivasan

Windows 7 Pro
Cancel
Vote Up 0 Vote Down

Cancel
0 Typhoon87 over 7 years ago in reply to Haridoss Sreenivasan

Its Windows 7 Pro SP1. The tokens are supported and work. Again the issue is WIndows is showing the option to log in without it. Only on the new machines. There are no other policy diffrencets that I can find.
Cancel
Vote Up 0 Vote Down

Cancel
0 Haridoss Sreenivasan over 7 years ago in reply to Typhoon87

Hi Typhoon87

Is the token plugged into USB 2.0 or USB 3.0? If it is plugged into USB 3.0 try using USB 2.0. If the token is old they may not work with the USB 3.0. Let me know if this helps resolve the issue.

Haridoss Sreenivasan
Technical Support Engineer | Sophos Technical Support
Knowledge Base | @SophosSupport | Video tutorials
Remember to like a post. If a post (on a question thread) solves your question use the 'This helped me' link.
Cancel
Vote Up 0 Vote Down

Cancel
0 Typhoon87 over 7 years ago in reply to Haridoss Sreenivasan

The tokens are newer and do work in USB 2 and 3 we have tried both.

I really feel this is a policy issue as older machines it works as intended. On the newer machines (skylake) we have issues. I created a duplicate poicy and the only change should have been the POA allowing username/password. But now if offers username password at the windows login as well.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Typhoon87 over 7 years ago in reply to Haridoss Sreenivasan

The tokens are newer and do work in USB 2 and 3 we have tried both.

I really feel this is a policy issue as older machines it works as intended. On the newer machines (skylake) we have issues. I created a duplicate poicy and the only change should have been the POA allowing username/password. But now if offers username password at the windows login as well.
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data