For instance, SMS 2.0 allows separate log files of each SMS-implemented feature, such as software distribution and remote control. Another instance would be specific password and account policies that are meant to be applied enterprise-wide across all platforms. In addition to reviewing current security policies, an SMS security policy should be developed that would address the particular issues that SMS introduces, and are specifically identified, in the SMS 2.0 Administrator's Guide, SMS 2.0 Resource Guide, and related publications from Microsoft. One such policy issue is how non-standard or unlicensed software identified in the SMS Software Inventory Feature and Software Metering Feature are to be handled and communicated. Without diving into the security framework of SMS provided by Microsoft, the fact that SMS 2.0 features are enterprise-wide should have prompted some consultation with the company's Human Resource and Legal department over whether corporate policies relating to employee privacy and employer rights need to be clarified or updated.
Companies do have the right to manage and control all company assets to reduce liability.
However, legal and privacy issues can arise in enterprises that allow the use of an employee's own personal computer to remotely access the company network, particularly if SMS required to be installed in order to connect. SMS should be configured to detect such access. Legal and forensic issues can also arise if SMS is not configured with security in mind. In the case of the SMS Remote Diagnostics feature, displayed are the following Remote Control properties options in the Control Panel. This is to help understand the internal controls environment, and to understand the issues that SMS security must address.