Security and Privacy for Collections in Configuration Manager
Updated: May 14, 2015
Applies To: System Center 2012 Configuration Manager, System Center 2012 Configuration Manager SP1, System Center 2012 Configuration Manager SP2, System Center 2012 R2 Configuration Manager, System Center 2012 R2 Configuration Manager SP1
Note
This topic appears in the Assets and Compliance in System Center 2012 Configuration Manager guide and in the Security and Privacy for System Center 2012 Configuration Manager guide.
This topic contains security best practices and privacy information for collections in System Center 2012 Configuration Manager.
There is no privacy information specifically for collections in Configuration Manager. Collections are containers for resources, such as users and devices. Collection membership often depends on the information that Configuration Manager collects during standard operation. For example, by using resource information that has been collected from discovery or inventory, a collection can be configured to contain the devices that meet specified criteria. Collections might also be based on the current status information for client management operations, such as deploying software and checking for compliance. In addition to these query-based collections, administrative users can also add resources to collections.
For more information about collections, see Introduction to Collections in Configuration Manager. For more information about any security best practices and privacy information for Configuration Manager operations that can be used to configure collection membership, see Security Best Practices and Privacy Information for Configuration Manager.
Security Best Practices for Collections
Use the following security best practice for collections.
Security best practice |
More information |
|---|---|
When you export or import a collection by using a Managed Object Format (MOF) file that is saved to a network location, secure the location, and secure the network channel. |
Restricts who can access the network folder. Use Server Message Block (SMB) signing or Internet Protocol security (IPsec) between the network location and the site server to prevent an attacker from tampering with the exported collection data. Use IPsec to encrypt the data on the network to prevent information disclosure. |
Security Issues for Collections
Collections have the following security issues:
If you use collection variables, local administrators can read potentially sensitive information.
Collection variables can be used when you deploy an operating system.