reggiep Posted August 1, 2009 Posted August 1, 2009 Forgive me if I sound ignorant here but I have just moved from CC3 to a vanilla Windows 2008 environment. One thing that a friendly work experience guy has pointed out is that if he creates a batch file with command.com inside it he can run it and then have the command prompt. Is file screening the way to go with this or is there a better solution? I have read that with file screening the users could just rename the extension and then use it whenever!
CyberNerd Posted August 1, 2009 Posted August 1, 2009 deny users access to command.com by setting the ntfs permissions 1
maniac Posted August 1, 2009 Posted August 1, 2009 Software restriction policies is the way forward here, you can deny access to specific programs by using a hash of them (so even if they renamed it it still wouldn't run) as well as stopping batch files being run from their home areas by denying executables on anything except the C:\ There is also a GPO 'deny access to command prompt' which if set should stop it being run as well. Mike. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now