Protect/prevent Unix passwd/shadow and Windows SAM from being copied out
There's a discussion internally within our corporate if it's a concern that an internal staff attempts to copy out
SAM & passwd and then run a password cracking tool on it.
Is this a valid concern?
In DoD B2 (or is it C2), the file containing hashed passwd 'vanishes' : is the purpose to prevent someone from
copying out the hashes for cracking? Or what's the purpose of doing this?
What are the measures we can put in place to prevent internal staff from making cracking attempts on SAM
& a Unix file containing the hashed passwords? Should stronger hash (what's the current best practice?) or
encryption be used?
Is there any way of auditing/logging it so that we only capture the genuine attempts to copy out these files ?