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.
Q1:
Is this a valid concern?
Q2:
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?
Q3:
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?
Our community of experts have been thoroughly vetted for their expertise and industry experience.
This award recognizes a member of Experts Exchange who has made outstanding contributions to the community within their first year as an expert. The Rookie of the Year is awarded to a new expert who has the highest number of quality contributions.
The Distinguished Expert awards are presented to the top veteran and rookie experts to earn the most points in the top 50 topics.