Mainstay
Well-Known Member
- Reaction score
- 747
I was asked by a [lawyer] client who is in the process of purchasing a competitors law firm to come in and evaluate the equipment of the firm she is buying.
The site is managed / supported by my direct competitor.
I was 5 minutes in the door and getting a verbal overview of their operations (router, switches, computers, etc.).
I asked, "how are the systems running, in general?".
They pointed me to the 'server' and said that they can't use this system as they are constantly logged out... always returning to the login screen. They can use it if to access client files on the network, but if they sit at the station and try to use the computer it always logs them out.
Hmmm.... bad profile?
I ask if I can take a quick look at it... they say yes... I log in and pull up eventvwr and the very first entry is a disconnected user from RDP.
OK, when I logged in, I bumped off the remote user from console. Oops.
I turn to them and say, "sorry, didn't realize you had a remote worker logged into this computer."
They say, "we don't have anyone else working in the firm, and no-one has remote access."
YIKES!
I look up their IP address and it returns as originating in THE RUSSIAN FEDERATION.
Double YIKES!
The logs are FULL of RDP sessions spanning the last 4 years.
I ask if I can close this down, NOW... and the only concern they have is that I bill this portion of the evaluation to the current owner.
WTF?!
You have a law firm with client files (yes, admittedly from a small town from the back yard of beyond, but STILL) being accessed from outside the firm, the province, and the country and you don't bat a blinking eye?!
And these are lawyers! You'd think if there was someone who would catch the liability issue it would be them.
And yes, the router was fully configured to pass on 3389 to the server and there were no limitations on origin IP etc. The password to the system was laughable.
I started to try and incite some fire in them but let it go... I've been down this path too many times. Battling customer apathy is wasted effort.
The site is managed / supported by my direct competitor.
I was 5 minutes in the door and getting a verbal overview of their operations (router, switches, computers, etc.).
I asked, "how are the systems running, in general?".
They pointed me to the 'server' and said that they can't use this system as they are constantly logged out... always returning to the login screen. They can use it if to access client files on the network, but if they sit at the station and try to use the computer it always logs them out.
Hmmm.... bad profile?
I ask if I can take a quick look at it... they say yes... I log in and pull up eventvwr and the very first entry is a disconnected user from RDP.
OK, when I logged in, I bumped off the remote user from console. Oops.
I turn to them and say, "sorry, didn't realize you had a remote worker logged into this computer."
They say, "we don't have anyone else working in the firm, and no-one has remote access."
YIKES!
I look up their IP address and it returns as originating in THE RUSSIAN FEDERATION.
Double YIKES!
The logs are FULL of RDP sessions spanning the last 4 years.
I ask if I can close this down, NOW... and the only concern they have is that I bill this portion of the evaluation to the current owner.
WTF?!
You have a law firm with client files (yes, admittedly from a small town from the back yard of beyond, but STILL) being accessed from outside the firm, the province, and the country and you don't bat a blinking eye?!
And these are lawyers! You'd think if there was someone who would catch the liability issue it would be them.
And yes, the router was fully configured to pass on 3389 to the server and there were no limitations on origin IP etc. The password to the system was laughable.
I started to try and incite some fire in them but let it go... I've been down this path too many times. Battling customer apathy is wasted effort.