Secure Folder

[GRitchie]

Hello,

We have a folder on our network that we want to secure so that only the IT team can open the folder and view the contents.

It has information in such as serial numbers and license agreements etc. and we don't want your average Joe to just stumble upon it.

 

Even better would be having to type a password to open the folder, but I don't think this is possible within Windows Server default.

 

 

Best ideas for making this folder secure?

Thanks!

[gtg93]

Why not just restrict it with NTFS permissions, and / or set it as a seperate share so it's not within staff/pupil share folders? Edited June 26, 2014 by gtg93

[sonofsanta]

Just use NTFS permissions. Untick inheritance, remove everyone's permissions and add in a security group for you lot with access. Leave Domain Admin with access, and System if it's there.

 

Don't use a Deny permission on an All Staff group if you're also all in that group, because that general Deny will take precedence over a specific Allow. Deny is always more powerful than Allow in NTFS permissions.

[CamelMan]

If you are more worried about it you could always encrypt it with something like TrueCrypt (I know its be discontinued but its the principle more that than the product!). I used it to encrypt our knowledge base area previously as it had serials, license keys and network config information.

[3s-gtech]

An NTFS protected folder with a Truecrypt file within would be pretty strong. The permissions would stop anyone else deleting it in frustration!

 

Despite being discontinued, I think Truecrypt (or ideally a forked project) should still be useable for this stuff - it has never been shown as insecure or cracked (when used in a secure manner, I should say).

Edited June 26, 2014 by 3s-gtech

[Tall_Paul]

I keep all our vital information in a password protected 7-zip folder. AES-256 encryption so it's pretty secure! It's also protected with NTFS permissions as mentioned above. Edited June 26, 2014 by Tall_Paul

[Arthur]

NTFS permissions are all you need. I wouldn't overcomplicate things.

[smithson83]

+1 for NTFS

 

But I'd hide the folder for good measure, or even create a specific share for it outside any other current structure that is only mapped by IT admins.

[cooka]

NTFS + hide (use the almighty $)