common miscnfigured windows services and data exposure
Posted on 2011-09-27
As an internal only user often we identify what we call “open shares and directories” on our domain – that often house sensitive data. I believe we access them over the SMB protocol. Aside from open shares, where all the user really needs to do to access is be a member of everyone or domain users group and no how to mount a remote share - are there any other services or common mistakes made on windows server that could also grant internal users inappropriate access to any sensitive data resident with little or no skill required to access it? Or are “Open shares” by far the easiest and most common on windows server? If there are other common misconfigured windows services that can grant access to data on target server – please detail.