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: Share and NTFS permissions

Subject: RE: Share and NTFS permissions
Date: Mon, 5 Feb 2007 10:58:41 -0700
One way you can set custom permissions on new files is to use the file
screens feature in Win2003 R2. You could create a file screen for all new
files, have that screen run a script and that script can set permissions and
can be as elaborate as you want. 

Of course, this does introduce a bit of a race condition but that would only
be for the creator/owner. It may not work for every situation. 

I mentioned this technique recently in my blog:
http://xato.net/bl/2007/02/01/using-filescreens-for-server-lockdowns/



Mark Burnett



-----Original Message-----
From: David LeBlanc [mailto:dleblanc@mindspring.com] 
Sent: Monday, February 05, 2007 10:31 AM
To: 'De Rienzo, James'; 'M. Burnett'; 'Jim Harrison';
Monrad.DC@Forces.gc.ca; focus-ms@securityfocus.com
Subject: RE: Share and NTFS permissions

 

-----Original Message-----
From: De Rienzo, James [mailto:James.DeRienzo@hq.doe.gov] 
Sent: Monday, February 05, 2007 7:34 AM
To: David LeBlanc; M. Burnett; Jim Harrison; 
Monrad.DC@Forces.gc.ca; focus-ms@securityfocus.com
Subject: RE: Share and NTFS permissions

Change the file's Ownership to Administrator, and be done with it. 

Simple yet effective.

And have the likely side-effect of removing access from the original owner.
I'd suggest taking a more thorough approach. This is why I originally wrote:

"it takes ownership of anything showing up there, ****and sets an ACL the
admin finds appropriate****"


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