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?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

sunhuxAuthor Commented:
We thought of enabling Auditing of these files but these files are being accessed frequently to authenticate users.
Is there any way of auditing/logging it so that we only capture the genuine attempts to copy out these files ?
Dr. KlahnPrincipal Software EngineerCommented:
Q1:  Yes.

Q3:  There's a relatively simple mitigation nobody ever uses.  Have anyone with sensitive access individually background investigated and commercially bonded.  (A blanket position bond might be acceptable as the bar for claim is lower; but imo don't settle for that as it puts the burden on the company.)  Anyone who can't be bonded should not be in that position, or indeed any position in your organization.
sunhuxAuthor Commented:
on the Q3's reply, we're looking more in terms of mitigating from systems perspective & not from process/bonding/policy perspective.

Would placing an audit logging help & how can we configure it such that we don't get false positives?

So, using DoD's B2 (or is it C2) method is the way to go?
Shaun VermaakTechnical SpecialistCommented:
I primarily focus on MS but the principals translate

Should stronger hash (what's the current best practice?)  or encryption be used?
Both. Strong hashes project compromised hashes (except pass-the-hash) and encryption protects the SAM from offline/physical attacks.

The biggest security risk, however, is over-permission. Even in an environment with 100k endpoints, there should not be more than 2 or 3 domain admins. You can use Admin on the device to shadow copy SAM and crack offline.
and a proper delegation model must be implemented
and devices isolated

I do not even need to carry rainbow table with me because I can crack hashes in the cloud

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It;s late, but I'll add my 2c
Q1: Not really. If someone has access to the hashed password file, they already have Admin/root access, at least temporarily. There are better things to worry about - logging and auditing, for example.
Q3: SHA256 + salting is easy to implement and, in my opinion, makes the hashes pretty much immune to cracking or rainbow tables.

Look at the real Risk to the company first - i.e. how likely is (something) to happen, and what would be the impact?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.