Mandatory single use of MFA on RDM users

Mandatory single use of MFA on RDM users

0 vote

avatar

Hi,
Right now you can from the RDM application where it is installed, setup a MFA solution - but any new RDM installation that connects with the same user credentials does not have MFA. What I am concerned about is that if our system somehow is compromised and someone get's access to a users AD credentials (and that user have permission to view password i RDM database), then they can just bypass the MFA by setting up a new RDM connection to the database server and get access.
What I would like to see is that an admin somehow could force users to use MFA and deny them access without MFA. Or even better have the MFA configuration (google or other MFA solution), to be stored in the database so everytime that users connects RDM to the RDM database, it will automatically prompt the users to signin with the MFA that the users has setup to use.

Thanks :-)

Thomas

All Comments (3)

avatar

Hello Thomas,

MFA links with AD accounts (in the database) need an authentication server. For this Devolutions Password Server or SQL Azure are required as the database.

That said, if you use another type of advanced data source you can always ask an MFA under Administration -- System Settings -- Security. That said, this MFA is configured locally so the user will just need to configure a local Google Auth and will be able to connect to the database (I'm not sure this is what you are looking for).

I think the best bet for you is SQL Azure or Devolutions Password Server. However, may I ask you what type of data source are you using?

Regards,

David Grandolfo

avatar

Hi David,
Thanks your your reply.
It is a local SQL 2016 server. So what you are saying is that a MFA feature integrated into the database of a local SQL is not possible, so the best choices is to either use the Devolutions Password Server in combination with RDM (i guess that DPS functions as the RDM database online right?).
Or look at Azure SQL migration where Azure SQL only forces a onetime connection MFA approval when connection to the database is made. After that, you will need to setup another MFA authentication on the local RDM client (and here, from what I understand, can't reuse MS Authenticator in RDM as RDM does not support this MFA yet. Correct?)

Thomas

avatar

Hi Thomas,

MFA with SQL is possible, what I'm telling is that the MFA will be on the application not on the authentication. (Force 2FA option)

Adding DPS to your setup (because, you still need a database behind) will add a middleware server to manage the AD integration (or AAD). DPS is an on-prem IIS application. Many other features will be added too (MFA, AD integration, RBAC with AD groups, PAM features, password rotation, approval process, recording servers and more (https://server.devolutions.net/).

For SQL Azure, we support Azure MFA on the authentication, so each time a user will connect to the database (SQL Azure) he will be prompted for his MFA.

Regards,

David Grandolfo