Restrict access to CMD.EXE

  • Thread starter Thread starter Jim Dell
  • Start date Start date
J

Jim Dell

If I restrict access to the CMD.EXE command what side affects might my users
experience? Besides not being able to get to the CMD prompt what else won't
work.

Thanks,

Jim
 
Hi Jim,

Vera's right - any batch files you use at login, or as wrappers to start
your applications would be all that's affected, but it does depend on how
you are blocking the file?

If you do wish to block cmd.exe and still allow specific batch files to be
run, you could look at Application Manager from www.appsense.com, which
allows you to specify individual batch files to allow to run even while
cmd.exe is blocked. You can do the same with various other script types such
as VBScript. You can optionally apply Digital Signature and Trusted File
Ownership checks to make sure that the batch / script hasn't been modified
in any way.

As you don't specifically say whether batch file access would be an issue
for you, I can't be sure this would be the right solution for you. Just
thought I'd point out that it *is* possible if you want to do it!

You can download fully featured evaluations of all our products from our
website at <http://www.appsense.com/newsgroup>. As a special offer, if you
evaluate and later provide feedback on your evaluation, you can claim a free
server copy (with a year's free support) of any one of our products. The
feedback page is <http://www.appsense.com/feedback>.

Regards,

Jon.

--

Jon Harvey
Software Developer
AppSense Technologies

http://www.appsense.com
mailto:jon.harvey[NO^SPAM]@appsense.com
 
I don't know exactly which (side) effects that registry setting
can have. Test it on a non-production server, especially if you
have 16-bit applications.
 
Back
Top