Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Focus-Microsoft
[Top] [All Lists]

RE: Restrict Windows login to certain IPs/hosts for certain domain accou

Subject: RE: Restrict Windows login to certain IPs/hosts for certain domain accounts?
Date: Fri, 27 Apr 2007 16:16:40 -0500
Sure you can create an account and put it in the local Admins group in
AD and then in  the Properties of that account list the servers you want
it to login to

-----Original Message-----
From: listbounce@securityfocus.com [mailto:listbounce@securityfocus.com]
On Behalf Of christopher@mallow.name
Sent: Friday, April 27, 2007 3:41 PM
To: focus-ms@securityfocus.com
Subject: Restrict Windows login to certain IPs/hosts for certain domain
accounts?

Hello to all,


I'm working with a particular client who would like to use a certain

domain account with local admin rights for config and other monitoring

via BMC, but would like to restrict that account so that it can only

log on to other systems from a single IP or a small range of IPs

(i.e., the monitoring servers), so that its local admin rights are not

used/abused by others. The client has Windows 2000 and 2003 servers,

and mostly 2000 and XP workstations. The client is using Cisco

Security Agent on the servers, so if that can factor in, that would be

fine, too. Essentially, we need an account with local admin that can

do anything on those systems for the monitoring but can't mess with AD

and can't be used from other locations by other users who might know

the password (or attackers who have guessed the password).


Is this possible? Would simply restricting local logon/TS logon via

user rights be enough? Anyone have ideas that might be helpful? I'm

wide open to suggestions; the Windows guys here are pretty good, but

even they aren't sure how to approach this. Thanks for any assistance.


Sincerely,

Chris Mallow

-----------------------------------------
***********************
Confidentiality Notice:
This message and any attachment(s) transmitted with it are the
property of Cole Taylor Bank and/or its affiliates and solely for
the use of the individual or entity to which this message is
addressed and contains information that is confidential. If the
reader of this message is not the intended recipient, you are
hereby notified that any review, retransmission, disclosure,
copying, distribution or the taking of any action in reliance on
the contents of this communication by persons or entities other
than the intended recipient is strictly prohibited. If you have
received this email in error, please contact the sender and delete
the material from any computer.
***********************


<Prev in Thread] Current Thread [Next in Thread>