Hi David,
we are using RDMS as data source with integrated security to connect to the data source.
But this is the problem:
I start my computer and log on. When not locking my desktop any user could start RDM, enters his credentials (as he wont know mine) and connects to the data source with MY user as my windows user is still logged on.
So the credential entering does only one thing: Keep non-domain-Users from connecting.
But over 60% of data-loss come from internal users...
And internal users are more likely to get to my unlocked desktop, of course.
Another thing I already mentioned above is with our hotline VMs:
There is a general user logged on in order to wont log out / log in every time one of my colleagues connects or disconnects from a VM.
If we can use RDM with the password-at-startup function and that credentials went to the logs on session start/close/whatever we would have a perfect audit trail with the corresponding users and not the general ones.
The general users have no rights to edit/create/delete sessions so connecting with the general user wont be a problem on this side.
and another time
thanks for the lightspeed response time ,-)
we are using RDMS as data source with integrated security to connect to the data source.
But this is the problem:
I start my computer and log on. When not locking my desktop any user could start RDM, enters his credentials (as he wont know mine) and connects to the data source with MY user as my windows user is still logged on.
So the credential entering does only one thing: Keep non-domain-Users from connecting.
But over 60% of data-loss come from internal users...
And internal users are more likely to get to my unlocked desktop, of course.
Another thing I already mentioned above is with our hotline VMs:
There is a general user logged on in order to wont log out / log in every time one of my colleagues connects or disconnects from a VM.
If we can use RDM with the password-at-startup function and that credentials went to the logs on session start/close/whatever we would have a perfect audit trail with the corresponding users and not the general ones.
The general users have no rights to edit/create/delete sessions so connecting with the general user wont be a problem on this side.
and another time
thanks for the lightspeed response time ,-)