The first step working with automation and PowerShell is completing an authentication process against a remote server and providing the right credentials. In the previous article our aim was to raise the awareness of how SecureString can be used in a very unsafe way, now we simply would like to show you what to avoid and how to store your credentials.
Powershell is frequently described as secure by default or design, but I’ve found that end-users could be frequently tempted to take risks or bypass the security or not aware of what the implications are.
Nothing really new to most developers or sysadmins, but not many of them have gone through the process of decoding a SecureString, even if is quite a trivial exercise. Continue reading “Passwords and SecureString, How To Decode It with Powershell”
Nagios is a very powerful open source tool for monitoring networks and infrastructures. The number of plugins available on Nagios Exchange and extensions make this tool essential to not just to be reactive but to create workflows and escalations if needed in a matter of minutes.
The installation and configuration of this tool under a major linux distributions is not difficult.
The default tool for monitoring a Windows network are SCCM/SCOM and OMS, but if your environment is a mixed environment I think personally that Nagios can be considered a safe bet!
NSClient++ is the agent needed for performing some interesting checks on windows and you can leverage your powershell scripting ability to perform custom checks on the environment. Continue reading “PowerShell, Nagios and NSClient++”