Security and privacy for software updates in System Center Configuration Manager
Applies to: System Center Configuration Manager (Current Branch)
This topic contains security and privacy information for software updates in System Center Configuration Manager.
Security best practices for software updates
Use the following security best practices when you deploy software updates to clients:
Do not change the default permissions on software update packages.
By default, software update packages are set to allow administrators Full Control and users to have Read access. If you change these permissions, it might allow an attacker to add, remove, or delete software updates.
Control access to the download location for software updates.
The computer accounts for the SMS Provider, the site server, and the administrative user who will actually download the software updates to the download location require Write access to the download location. Restrict access to the download location to reduce the risk of attackers tampering with the software updates source files in the download location.
In addition, if you use a UNC share for the download location, secure the network channel by using IPsec or SMB signing to prevent tampering of the software updates source files when they are transferred over the network.
Use UTC for evaluating deployment times.
If you use local time instead of UTC, users could potentially delay installation of software updates by changing the time zone on their computers
Enable SSL on WSUS and follow the best practices for securing Windows Server Update Services (WSUS).
Identify and follow the security best practices for the version of WSUS that you use with Configuration Manager.
If you configure the software update point to enable SSL communications for the WSUS server, you must configure virtual roots for SSL on the WSUS server.
Enable CRL checking.
By default, Configuration Manager does not check the certificate revocation list (CRL) to verify the signature on software updates before they are deployed to computers. Checking the CRL each time a certificate is used offers more security against using a certificate that has been revoked, but it introduces a connection delay and incurs additional processing on the computer performing the CRL check.
For more information about how to enable CRL checking for software updates, see How to enable CRL checking for software updates in System Center Configuration Manager.
Configure WSUS to use a custom website.
When you install WSUS on the software update point, you have the option to use the existing IIS Default Web site or to create a custom WSUS website. Create a custom website for WSUS so that IIS hosts the WSUS services in a dedicated virtual website instead of sharing the same web site that is used by the other Configuration Manager site systems or other applications.
For more information, see Configure WSUS to use a custom web site.
Privacy information for software updates
Software updates scans your client computers to determine which software updates you require, and then sends that information back to the site database. During the software updates process, Configuration Manager might transmit information between clients and servers that identify the computer and logon accounts.
Configuration Manager maintains state information about the software deployment process. State information is not encrypted during transmission or storage. State information is stored in the Configuration Manager database and it is deleted by the database maintenance tasks. No state information is sent to Microsoft.
The use of Configuration Manager software updates to install software updates on client computers might be subject to software license terms for those updates, which is separate from the Software License Terms for System Center Configuration Manager. Always review and agree to the Software Licensing Terms prior to installing the software updates by using Configuration Manager.
Configuration Manager does not implement software updates by default and requires several configuration steps before information is collected.
Before you configure software updates, consider your privacy requirements.