- You’ve shifted the balance of power – The scripter or developer no longer has control over the password’s use; IT does.
- You’ve obfuscated the password’s value – By using a programmatic call for the password (assuming some level of security based on IP address, etc.), the password remains completely hidden and only available to the proper machines.
- You can better secure the password – Besides putting the password under management and hiding it, you now can change it as often as policy deems appropriate, keeping that account far more secure than when it remained static and sitting in the open.
Nick Cavalancia, Founder/Chief, Techvangelism
Nick Cavalancia has over 20 years of enterprise IT experience, 10 years as a tech marketing executive and is an accomplished technology writer, consultant, trainer, speaker, and columnist.
Nick has attained industry certifications including MCNE, MCNI, MCSE and MCT and was once accused at TechEd of "not having enough digits" in his MCP number (which only has 5). He has authored, co-authored and contributed to over a dozen books on Windows, Active Directory, Exchange and other Microsoft technologies and has spoken at many technical conferences on a wide variety of topics.
Previously, Nick has held executive marketing positions at ScriptLogic (acquired by Quest, now DELL Software), SpectorSoft and Netwrix where he was responsible for the global messaging, branding, lead generation and demand generation strategies to market technology solutions to an IT-centric customer base.