Security
When it comes to security, you need to consider DSC as well. Not only do your configurations contain all your sensitive operational data, passwords, connection strings, and infrastructure; Desired State Configuration is also an excellent attack vector to quickly and reliably spread malware and create general mayhem.
Securing your pull server and controlling who may push configurations to your systems is one thing you can do to secure your configurations. This can be done by employing JEA, authentication policies and silos, group policies, and in other ways. The following screenshot shows why security is very important. Notice the two plaintext credentials here for a highly privileged account.
In addition to securing your pull or build server, you need to encrypt your configurations. The only way this can be accomplished is by using certificates. The pull server needs to know all of the public keys of its nodes, and each node needs its own document encryption certificate to receive...
