Discussion Locked
0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
One of the RAS dial-up users, in our domain, successfully connected using his home PC, rather that his issued laptop, after renaming it. How can we detect this security breach and stop it?
7 replies
by cg it
well, if he has dial up permission via RRAS, there's not much you can do. Especially if he renames his home computer and uses his authorized account and he is required to be able to dial up. You might be able to segregate his account from all othersby placing him in his on OU, then create a group policy [manditory profile] for him which does not allow him to view what his computer name is on his authorized laptop. Then he would not be able to change his home computer to match his laptop. You'll see remote access denied in the event viewer when he tries something.
by archie 0'nut
The question was auto-closed by TechRepublic
by d.walker5
You could implement Certificate Authority (CA). See Microsoft Knowledge Base article 253498. After installing CA use the RAS Access Policy snap-in to configure a policy that only allows access after the authorized laptop presents a Machine Certificate. This procedure entails considerable planning to implement correctly. However, CA can greatly improve overall security.
by archie 0'nut
The question was auto-closed by TechRepublic
Hi,
Ask him if he values his job! Such actions should be clearly in breach of the companies Acceptable User Policy signed by all employees. Then sort out how you will track suck breaches in the future. Next time someone tries such a stunt make sure management sack him \ her on the spot! Sounds harsh I know, but drastic action often works wonders as an example to others.
Regards,
PJ
by archie 0'nut
The question was auto-closed by TechRepublic
by archie 0'nut
This question was auto closed due to inactivity
This discussion is closed to new replies.
Trending Security posts
Sort by Trending
0 helpful
8 replies
0 helpful
2 replies
0 helpful
0 replies
Discussion Locked
LiteLLM SQL Injection Vulnerability (CVE-2026-42208)
0 helpful
0 replies
Discussion Locked
How do you go about MCP Security?
0 helpful
8 replies