Lock a folder in windows Pc#
, but i just wondered why its not possible to do this on a server when it ac be done so easily on a PC or Mac. And yes you can say that the IT company could copy stuff any time but that would be when they are here in my server room and at the very least it would help to know that any data that was copied would be useless to them. Its not that theres anything dodgy in there, but who knows whose doing what and with GDPR coming down the tracks like a freight train, i need to show that i have as a data manager made every effort to secure the Data in my possession, i cannot afford a data breach. My worry was that (and no offence to anyone) whats to stop my IT support guys (based off site and too be fair i dont know who works there or comes and goes) who need access to my company server from accessing these folders. I have three people in accounts and they have a folder on the network that they use and its shared. Earlier in the topic lots of people were asking Why do you need to do this? I am new to the group but can appreciate the topic here as I had a similar question.
Lock a folder in windows software#
We don't entrust the privacy of our data - especially data which we have flagged as being particularly sensitive as in this case - to a random bit of software seemingly developed by a single person that's intercepting the file-system calls on our server. If information needs to be shared, we have reliable, stable, well-tested, widely used, audit-able platforms for doing so. I don't think I have a single client who hasn't gone through some sort of certification process that requires unique and private user accounts - even a simple PCI-DSS SAQ will specify this. In the real world that I live in, people know that sharing login credentials is something that you Do Not Do. If they still insist on doing things a different way, then I suggest that there's little point in their paying my fees. I know that I'm perfectly capable of listening to a client's requirements, and explaining how the solution meets those requirements. I suspect I'm somewhat spoiled in that I've been able to divest myself of any clients who behave in this way very quickly. It's what happens when people try to specify how tools should work, rather than what they should achieve. It may seem silly to us, but it's how things in the real world happen.
Lock a folder in windows password#
I know people that do things like this, letting their secretary have their password so they can login to check things, for instance. If they made use of the system they already have, it would meet their needs perfectly. "We're not using the existing security tools correctly, so are adding another layer. The only reason I can see this request as feasible would be if people are using shared accounts which is the issue rather than a PW protected folder and the solution would be to not use shared accounts. Also as a FYI AD is already dependent on a password entry for access as you first need to authenticate to the domain controller before you are granted rights to the folder structure (assuming the shares are setup properly). Sounds like this is stemmed more so from an issue with business/HR type of issue rather than an IT/Security issue. If you want to stop someone from copying then you set permissions to block permissions for move. IE if you are trying to stop someone from accessing the folder you set explicate rights to the folder so only the people that need access can view or edit. My question as many others would be, Why? What is the reason for this request? I can see absolutely no reason that you would need to password protect a folder that wouldn't also be accomplished by restricting access using Active Directory.