Using the Secunia SC2012 Plugin 2.0 to Deploy Updates Secunia CSI 7 - SC2012 Plugin 2.0 Rev. 05-Sep-2014

Using the Secunia SC2012 Plugin 2.0 to Deploy Updates Secunia CSI 7 - SC2012 Plugin 2.0 Rev. 05-Sep-2014 Secunia.com

Contents Using the Secunia SC2012 Plugin 2.0 to Deploy Updates... 1 Contents... 2 The Secunia SC2012 Plugin... 3 The Secunia CSI... 3 Prerequisites... 3 Install... 4 Windows 8 with IE 10... 4 Get Started... 4 Login to Your Secunia CSI Account from the Console... 5 Patches... 6 View Installations... 7 Device Overview... 7 Import... 8 Schedule... 9 Configure... 10 The Secunia Daemon... 11 The Secunia Package System (SPS)... 12 SPS Concepts and Terminology... 12 What does a SPS package consists of?... 12 Applicability Rules... 12 Creating a Patch with the Secunia Package System (SPS)... 12 SPS Package... 13 Execution Flow Script... 13 Files... 13 Create an Update Package... 13 Step 1 of 4: Package Configuration... 14 Step 2 of 4: Package Contents... 15 Step 3 of 4: Applicability Criteria - Paths... 16 Step 4 of 4: Applicability Criteria - Rules... 17 Create an Uninstall Package... 18 Create a Custom Package... 18 Package Deployment... 19 Logout... 19 Additional Information... 20 Disclaimer... 20 2 Secunia.com

The Secunia SC2012 Plugin The Secunia Corporate Software Inspector (CSI) Microsoft System Center 2012 Configuration Manager (SC2012) Plugin enables the user to easily create and deploy packages for third-party (non-microsoft) updates using the Secunia Package System (SPS) directly from the System Center 2012 Configuration Manager console. The Secunia SC2012 Plugin consists of two parts: a plugin for the System Center 2012 Configuration Manager console and a standalone service running scheduled jobs, the Secunia Daemon. It requires a System Center 2012 Configuration Manager enabled Secunia CSI account that is purchased separately. Visit www.secunia.com for more details on licensing. The Secunia CSI The Secunia CSI is an authenticated internal vulnerability scanner, capable of assessing the security state of practically all legitimate programs running on Microsoft Windows platforms and supports scanning on Microsoft Windows, Apple Mac OSX, Android and Red Hat Enterprise Linux (RHEL) platforms. The Secunia CSI also integrates with Microsoft WSUS, System Center 2012 Configuration Manager and third-party patch deployment solutions for easy deployment of third-party updates, making patching a simple and straight-forward process for all IT departments. The Secunia CSI runs with administrative privileges on the network and is capable of logging into the systems being scanned. It can read data from files on the hard-drives of the scanned systems and assess whether the installed programs are vulnerable or not, cross-referencing with Secunia Vulnerability Intelligence to provide a comprehensive overview of your environment. In addition the CSI is able to import and process scan data from the Microsoft System Center 2012 Configuration Manager. In this case, the scan data is collected by the Software Inventory agent and in turn processed by the Secunia backend. Based on the scan results, packages are available out-of-the-box which can be viewed and deployed directly in the System Center 2012 Configuration Manager via the Secunia SC2012 Plugin. Prerequisites In order to use the integrated Secunia SC2012 Plugin, a number of prerequisites must be set up: A Secunia Scanning solution consisting of either: A Secunia CSI installation with scanning using CSI agents or System Center 2012 Configuration Manager import, or A System Center 2012 Configuration Manager import using the Secunia SC2012 Plugin or Secunia Daemon A deployment setup using a WSUS or the System Center 2012 Configuration Manager distribution point An installed and configured System Center 2012 Configuration Manager console For more information on requirements for distribution setup, scanning and more, please refer to the Secunia CSI Technical User Guide, available for download from: http://secunia.com/resources/product_sheets/ Secunia.com 3

Install The plugin will be activated by the Secunia Customer Support Center. The Secunia SC2012 Plugin should be installed on the same machine that the System Center 2012 Configuration Manager console is installed. You can use the plugin on the System Center 2012 Configuration Manager Server or on a client machine where the console is installed. The version of the Secunia SC2012 Plugin depends upon the version of the Software Update Point. If the Software Update Point is installed on Windows Server 2008R2 WSUS 3 SP2 then the SC2012 Plugin should be downloaded from: https://secunia.com/sc2012_csi7pluginsetup.exe If your Software Update Point is installed on Windows Server 2012 (WSUS 6.x) then install the x64 bit version of SC2012 plugin from: https://secunia.com/sc2012_csi7pluginsetupx64.exe 1. Download the correct installer from secunia.com. 2. Double-click the installer icon and follow the wizard instructions. 3. Launch the System Center 2012 Configuration Manager console. The plugin can be found under the Software Library > Secunia folder. 4. Login with your Secunia CSI Account credentials (User name/password) The machine should have access to https://*.secunia.com. Windows 8 with IE 10 If you experience problems loading the console when using Internet Explorer 10 with Windows 8 or Windows 2012 Server, a known workaround is to disable TLS 1.0 in your Internet options: From Internet Explorer click Tools on the top toolbar Select Internet options and click the Advanced tab Scroll to the bottom of the Settings list Deselect Use TLS 1.0 Get Started When the host scanning is setup and configured, the process of creating and deploying an update package is a simple process involving the following steps: Open the Patches folder in the System Center 2012 Configuration Manager console and login using your CSI credentials Navigate to the Configure folder and enter the connection information of your WSUS server or System Center 2012 Configuration Manager distribution point Navigate to the Patches folder and select the update you wish to deploy Complete the deployment wizard and click Publish Navigate to the All Software Updates page under the Software Updates folder in the Assets and Compliance workspace to approve the update and deploy the package You can also configure the System Center 2012 Configuration Manager, scan devices and view hosts connected to the upstream System Center 2012 Configuration Manager (from the Scan folder) and define the schedule for importing System Center 2012 Configuration Manager scan data and to add/remove hosts to be scanned (from the Schedule folder). The following sections describe each of these steps in detail. 4 Secunia.com

Login to Your Secunia CSI Account from the Console To use the Secunia SC2012 Plugin, select Run as administrator and launch the System Center 2012 Configuration Manager console. Go to the Secunia folder under Software Library. From the Patches folder, login to your Secunia CSI account. Secunia.com 5

Patches After you login, a list of products for which the Secunia CSI can automatically create an Update/Uninstall package is displayed. This list is based on the data that is received through the Secunia cloud and originates from the Secunia CSI scan data (either through CSI agents or System Center 2012 Configuration Manager import). For more information on scanning hosts, please refer to the Secunia CSI Technical User Guide. 6 Secunia.com

View Installations You can right-click on a patch and select View Installations to display overview and installation details of the product that the patch applies to. Device Overview Right-click a host in the Devices folder in the Assets and Compliance workspace and select Secunia Scan Details to view the scan result for that particular host. Secunia.com 7

Import Use the Import folder to configure the Secunia SC2012 Plugin, scan devices and view hosts connected to the upstream System Center 2012 Configuration Manager. Scan results are obtained from the data collected by the System Center 2012 Configuration Manager software inventory agent, which avoids the need to install the Secunia CSI agent on each client. The System Center 2012 Configuration Manager software inventory agent must be configured and running prior to loading the System Center 2012 Configuration Manager inventory folder. The inventory agent is configured by a set of simple rules that govern which files are queried. To produce the best possible scan result using System Center 2012 Configuration Manager, the Secunia CSI uses a relatively broad pattern, which could lead to large amounts of data being collected. If all file data is collected, a file size of between 5 and 10 MB for a single host is not uncommon, and the SQL server must be dimensioned to handle this. System Center 2012 Configuration Manager integration requires the following prerequisites: 1. Setting up authentication. The user running the CSI console must have access to the database containing the data of the System Center 2012 Configuration Manager. For System Center 2012 Configuration Manager the database is named CM_<site_code>. To add permissions, open SQL Server Management Studio, right-click the appropriate database, navigate to permissions and add Connect and Select rights. 2. Setting up the software inventory agent. Assuming that the System Center 2012 Configuration Manager site has been set up, open the System Center 2012 Configuration Manager console and ensure that the System Center 2012 Configuration Manager client (agent) is installed on the hosts to be scanned. In System Center 2012 Configuration Manager, go to Devices and right-click Install client. Then go to Administration > Client Settings > Properties > Software Inventory. To configure the broadest possible pattern, select File Detail: full and add the patterns *.dll, *.exe, *.ocx. Do not exclude the Windows directory. Less data will be generated by specifying a narrower pattern, however, the quality of the scan result will suffer. 8 Secunia.com

3. In addition, you might want to consider increasing the software inventory file size from the default of 5 MB to 12 MB. To accomplish this, change the following registry key on the System Center Server: HKLM\Software\Microsoft\SMS\Components\SMS_SOFTWARE_INVENTORY_PROCESSOR\Max File Size Click Configure SC2012, enter the Server Name and click Save. If you select Manual, enter the SQL Host, SQL Port and SQL Database connection data and click Save. Click Scan Selected Devices or Scan All Devices. Schedule Use the Schedule folder to define the schedule for importing System Center 2012 Configuration Manager scan data and to add/remove hosts to be scanned. The schedule is executed by the Secunia Daemon with credentials provided during the installation of the Daemon. Click New SC2012 Import Schedule. When you have created the schedule, click Save. A new window opens, where you will be prompted to add the hosts whose data you want to import. To remove the hosts in a Schedule, select the Schedule in the list. The hosts for that Schedule will appear in the bottom table. Select hosts (hold down shift or control to select multiple hosts), then right-click and select Remove. To add hosts to an existing Schedule, select the Schedule in the Schedules list and click Add Hosts. Select Include All Hosts to import the scan results of all Hosts available on the server. If new Hosts are discovered by the System Center 2012 Configuration Manager Server at a later date, they will also be included in the scan result. The New SC2012 Import Schedule and Add Hosts buttons will be disabled if the SC2012 Plugin is not connected to a System Center 2012 Configuration Manager server. To access the connection settings, click Configure SC2012 on the Scan folder. Secunia.com 9

Configure In order to deploy packages, a connection to the WSUS or System Center 2012 Configuration Manager infrastructure must be set up. The wizard is identical to the wizard in the Secunia CSI console. For more information, please refer to the Secunia CSI Technical User Guide. If you have a single WSUS server, which is connected to Microsoft Updates site, running the Configure Upstream Server wizard will be sufficient for setting up the Secunia CSI with WSUS. After clicking Configure Upstream Server, a configuration wizard will be initiated. Follow the wizard steps to successfully integrate the Secunia CSI with your Microsoft WSUS. To configure the WSUS connection in the SC2012 plugin, the SC2012 Configuration Manager console must be started with (right-click) Run as administrator if UAC is enabled. 10 Secunia.com

The Secunia Daemon The Secunia Daemon is a stand-alone executable that executes the import schedules configured in the Secunia CSI or System Center 2012 Configuration Manager console. It runs as a background service with no user interaction. The Secunia Daemon requires you to purchase the SC2012 Plugin to be able to use it. Since the Secunia Daemon is connecting directly to the Secunia servers and the System Center 2012 Configuration Manager database server unattended, you must provide the appropriate connection details during installation. The SQL Host, SQL Port and SQL Database must be set in the SC2012 Plugin, enabling it to perform unattended import from the System Center 2012 Configuration Manager database. Before installing the Secunia Daemon, you should install the Secunia SC2012 Plugin and configure and save the System Center 2012 Configuration Manager SQL Database Settings in the Scan folder. You can then: 1. Double-click the Secunia Daemon installer icon and follow the wizard instructions. 2. Login with your Secunia CSI Account credentials (User name/password). 3. Accept the End User License Agreement. 4. Select the Launch Option to run the daemon service as a local system or a specific user (users must have read access to the System Center 2012 Configuration Manager database on the SQL server). 5. During the Launch Option step, you will be prompted to choose the Windows Account the Daemon service will log on as. The ODBC Connection the Secunia Daemon uses will require the Windows Account to be from a Trusted Domain if the System Center 2012 Configuration Manager Server is located on another machine in the domain. On this step you should select the "Run as Some User" options and enter the credentials for the Windows Account. For Domain Users, the Account name will need to be in the Account@Domain format. For example, if your Account name is Admin and your Domain is ABC.local then you should enter it as Admin@ABC.local instead of ABC.local\Admin. 6. Click Finish to close the Secunia Daemon setup. The Secunia Daemon uses the System Center 2012 Configuration Manager SQL Database Settings that are specified in the Configure dialog in the Scan folder in the SC2012 Plugin. If those settings haven't yet been specified when the Secunia Daemon has been run then it will check for them again in 10 minutes and every 10 minutes afterwards until it gets them. The Secunia Daemon checks with Secunia every 10 minutes to download new schedules or fetch changes to existing schedules as long as it is not in the process of processing scans. The results are displayed in the Secunia CSI Completed Scans window and potentially patchable programs will appear in the Patches folder of the System Center 2012 Configuration Manager console (under the Secunia folder). Secunia.com 11

The Secunia Package System (SPS) The Secunia Package System (SPS) was created to give administrators the ability to create packages that are capable of doing a wide range of actions; everything from updating and uninstalling third-party applications to handling complex execution flows with multiple files. The Secunia Package System (SPS) window displays a list of products for which the Secunia CSI can automatically create an Update/Uninstall package. Right-click any of the listed products to view the available options. Click Configure View to select the criteria that will be used to display the products in this view. SPS Concepts and Terminology The Secunia SC2012 Plugin user should become familiar with the concepts and terminology described in this section. What does a SPS package consists of? The package consists of two parts; applicability rules and SPS package. The applicability rules are used by WSUS to only execute the package on computers that are applicable for the selected package. The SPS package consists of the payload that is then executed on the computer. Applicability Rules The applicability rules are rules used to decide whether or not a package should be offered to a client. These rules are as follows: IsInstallableApplicabilityRule Obtains the rules for determining whether or not this item is installable on a given computer. It generally consists of paths and version information of relevant files. IsInstalledApplicabilityRule Obtains the rules for determining whether or not this item is already installed on a given computer. It generally consists of keys and value information of relevant registry keys. IsSupersededApplicabilityRule Obtains or sets the rules for determining whether or not this item is superseded by another update on a given computer. It generally consists of paths and version information of relevant files. Creating a Patch with the Secunia Package System (SPS) The Secunia Package System (SPS) window displays a list of programs that you can create updates for. Click Configure View to customize the list and limit the types of programs shown, as well as highlight programs for which packages have or have not been created. If highlighted, programs for which SPS packages exist will be shown in green. A program will be displayed in blue if the vendor provides unattended/silent installation parameters for its patches. Any product listed in blue is available to have an update created in a simple three step process. 12 Secunia.com

Some programs are presented in grey because the vendor of the program does not provide silent installation parameters. If you choose to patch one these products, you must provide (import) the.msi/.msp/.exe file together with the parameters for the unattended installation. The Secunia CSI will then repackage and publish the update through the standard workflow. Packages cannot be automatically created by the Secunia CSI for these products. If you wish to create a new custom package that does not necessarily patch an existing product, for example to deploy new software, you can click New Custom Package. In this case you should provide the files/installer that will be executed on the target client together with the execution flow script as described in What does a SPS package consists of? With the Secunia CSI you are able to create three different kinds of packages. Right-click a product and select one of the available options: Create Update package Create Uninstall package Create Custom package For the Update and Uninstall packages a default execution flow script is provided in the package creation wizard (Step 2), which will fulfill most of the common needs. The execution flow script can also be customized for additional functionality. SPS Package An SPS package is a container consisting of a number of files for execution and a script. The execution flow script is either JavaScript or VBScript; by default a JavaScript example is provided in the package creation wizard. The script will be automatically extracted from the SPS package and executed. Based on the execution flow more files can then be extracted and executed from the SPS package, referenced by their index order. Execution Flow Script This execution flow script is always executed. This is the file with index 0, and as such it will always be the first to run. In the execution flow script you can define any other files to be extracted and executed. The default execution flow template that is provided in the Secunia CSI package creation wizard will extract the first file supplied in the package with the specified silent parameters (usually this is the patch file provided by the vendor). Any other files added to the package will NOT be extracted or executed when using the example script. Files The SPS package supports additional files besides the execution flow script. The added files will have array indices from 1 to n where the first file will have index 1, and the additional files are numbered in ascending order. Create an Update Package A program will be displayed in blue if the vendor provides unattended/silent installation parameters for its patches. Any product listed in blue is available to have an update created in a simple 4 step process. Right-click one of these products and select Create Update Package to start the package creation wizard. Secunia.com 13

Step 1 of 4: Package Configuration In Step 1 no action is required if the selected product was in blue. You should only check Edit Package Content (Optional) if the product was in grey or there is a need to customize the update patch by selecting a different file(s) and/or defining a different execution flow script. The Import Package feature allows you to import a SPS template in XML format that will automatically populate all the fields of the package creation wizard. This feature will be especially relevant when creating custom updates or when creating update packages for the products in grey. In Step 4 of the wizard you will also have the option to export the XML template for the package being created. After clicking Next, and if Edit Package Content (Optional) was not selected, you will go directly to Step 3 of 4: Applicability Criteria - Paths. We advise that you use the Secunia CSI Community to exchange SPS XML templates with other Secunia CSI users (https://secunia.com/community/forum/csi/). 14 Secunia.com

Step 2 of 4: Package Contents Step 2 becomes available when Edit Package Content is selected in Step 1. The first section of Step 2 is the Execution Script where you select JScript (Javascript), VBScript or Powershell Script and then review or create a customized execution flow. Secunia.com 15

Step 3 of 4: Applicability Criteria - Paths In Step 3 you should select the paths/locations to which this package should be applied. 16 Secunia.com

Step 4 of 4: Applicability Criteria - Rules In Step 4 you should specify if you want to limit the package to 32-bit or 64-bit systems or computers with specific operating system languages. The patch file to be deployed will be automatically downloaded in the background by the Secunia SC2012 Plugin. Once this is completed the console will repackage and publish the update package into the WSUS/System Center 2012 Configuration Manager. You will receive a notification when the package has been successfully created. Secunia.com 17

Create an Uninstall Package Any Products that are listed as Yes in the Uninstallable column are available to have an uninstall package created in a simple three step process exactly as the update packages in blue. For Products listed as No in the Uninstallable column you must customize the execution flow script to successfully uninstall the product. This can be done by starting the SPS package creation wizard and selecting the Edit Package Content check box in Step 1. Alternatively, and instead of creating your own execution flow script, you can engage with the Secunia CSI Community to exchange SPS XML templates with other community members. If you have an SPS XML template you can import it by clicking Import Package in the first step of the wizard. Once this is completed, all the fields in the wizard will be automatically populated, including the execution flow script. Special attention should be given to the files mentioned in the execution flow script. These files can be files originally provided by the SPS template creator or they can be dynamically downloaded. You should only import SPS packages if you trust the author of the package and the source from where you downloaded/obtained the package. Create a Custom Package The Secunia SC2012 Plugin allows creating custom packages that can be deployed through WSUS/System Center 2012 Configuration Manager. By creating a custom package you can do a wide range of actions; everything from updating and uninstalling third-party applications to handling complex execution flows with multiple files. The creation of a custom package can be done in two different ways. Either: Right-click a product and choose Create Custom Package. By doing this the product applicability rules will be included in the package; this will mean that the Custom Package will only be applicable for computers with the selected product installed. OR Click New Custom Package to start the package creation wizard. In this case no applicability rules will limit the installation base. Independently of the chosen approach, in both cases the package creation wizard will be initiated. 18 Secunia.com

Package Deployment To display and deploy the published update packages, go to the All Software Updates folder under Software Updates. Select the required packages and click Deploy. Logout Go to the Secunia folder, right-click and select Logout to logout of your Secunia CSI account. Right-click and select Toggle Logging to enable/disable the Secunia CSI logging feature, which is useful when troubleshooting any issue that you may experience. In the event of a support request you can send the log file together any other relevant information to CSC@secunia.com. The default path for the log file is: C:\User\<username>\AppData\Local\Temp\secunia_sc2012_plugin.log Secunia.com 19

Additional Information To learn more about the Secunia CSI, Secunia Package System and CSI WSUS Server Configuration, download the Secunia CSI Technical User Guide at: http://secunia.com/resources/product_sheets/ Disclaimer The contents of the Secunia website and all materials, information, links, documents and quotes ( Material ) are provided as is. Secunia does not, unless expressively provided otherwise in an agreement between you and Secunia or except as required by mandatory applicable law, either express or implied for the accuracy, warrant the accuracy, reliability or the contents of the Material. Secunia and any of its licensor or partners are to the extent permitted by applicable law, under no circumstances responsible for any loss of data or income or any special, incidental, consequential or indirect damages howsoever caused. Secunia assumes no responsibility for errors or omissions in the Material or software or other documents which are referenced by or linked to the Secunia website. In no event shall Secunia be liable for any special, incidental, indirect or consequential damages of any kind, or any damages whatsoever. This includes without limitation, those resulting from (i) reliance on the material presented, (ii) cost of replacement goods (iii) loss of use, data or profits, (iv) delays or business interruptions, (v) and any theory of liability, arising out of or in connection with the use or performance of information. This applies irrespectively whether Secunia has been advised of the possibilities of such damages. Secunia reserves the right to change any part of the Material without any notice. 20 Secunia.com

For further information please visit our website: secunia.com Email: info@secunia.com Contact Secunia Copyright 2014 Secunia. All rights reserved. This document may only be redistributed unedited and unaltered. This document may be cited and referenced only if clearly crediting Secunia and this document as the source. Any other reproduction and redistribution in print or electronically is strictly prohibited without explicit permission. Secunia.com Secunia.com 21