There are a few ways you can do this. I have previously written a script to upload file to a web server which would check for permitted file extensions and locations. You may also be able to control what files you can deploy from a content management system if you're using one. if you are giving you software department FTP access to the web root you should probably rethink how you load web content.

Some security software (e.g. anti-malware applications) have functionality to limit file system writes, probably acting at the kernel level by hooking system calls. McAfee Entercept can for example stop root writing to a given file, a mechanism which is used to prevent privileged users from tampering with it.

Rather than looking for a software solution consider creating a policy and enforcing it by checking the contents of your web root every so often. A scripted solution could check daily for example and report any non-whitelisted file extenstions.

Regards,
Jim

Hi
I have worked with it .But my problem is that if i do make the script then all i can do is look for restricted files and then delete them.While what i reuire is the safety at very first end.Mean to say that if i do have to restrict tar files from being created in htdocs then i should have a solution that if any software personnel tries to create tar of something in htdocs it should not be allowed at very that instant.My htdocs has write permissions for the software department and i do have the situation that i cannot change the permissions.I do have to restrict them somehow.Kindly help me regardin the same once again.
Hoping a quick and positive response from ur side.