Symantec Control Compliance Suite 11.0 Readme. Maintenance Pack 3 (Product Update )

Transcription

1 Symantec Control Compliance Suite 11.0 Readme Maintenance Pack 3 (Product Update )

2 Symantec Control Compliance Suite 11.0 PU Readme The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version: 11.0 PU Legal Notice Copyright 2013 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo and the Checkmark Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR and subject to restricted rights as defined in FAR Section "Commercial Computer Software - Restricted Rights" and DFARS , et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement. Symantec Corporation 350 Ellis Street Mountain View, CA

3 Technical Support Contacting Technical Support Symantec Technical Support maintains support centers globally. Technical Support s primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantec s support offerings include the following: A range of support options that give you the flexibility to select the right amount of service for any size organization Telephone and/or Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers software upgrades Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis Premium service offerings that include Account Management Services For information about Symantec s support offerings, you can visit our Web site at the following URL: All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy. Customers with a current support agreement may access Technical Support information at the following URL: Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem. When you contact Technical Support, please have the following information available: Product release level

4 Hardware information Available memory, disk space, and NIC information Operating system Version and patch level Network topology Licensing and registration Customer service Router, gateway, and IP address information Problem description: Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: Customer service information is available at the following URL: Customer Service is available to assist with non-technical questions, such as the following types of issues: Questions regarding product licensing or serialization Product registration updates, such as address or name changes General product information (features, language availability, local dealers) Latest information about product updates and upgrades Information about upgrade assurance and support contracts Information about the Symantec Buying Programs Advice about Symantec's technical support options Nontechnical presales questions Issues that are related to CD-ROMs, DVDs, or manuals

5 Support agreement resources If you want to contact Symantec regarding an existing support agreement, please contact the support agreement administration team for your region as follows: Asia-Pacific and Japan Europe, Middle-East, and Africa North America and Latin America

6

7 Contents Technical Support... 3 Chapter 1 What's New... 9 New features and enhancements in PU Before you begin installing PU Chapter 2 Resolved Issues Resolved Issues in PU Chapter 3 Installing PU Installing the update Prerequisites for installing PU Installing PU Chapter 4 Known Issues Known Issues in PU

8 8 Contents

9 Chapter 1 What's New This chapter includes the following topics: New features and enhancements in PU Before you begin installing PU New features and enhancements in PU Product Update (PU) is a cumulative package of product updates released for CCS 11.0, and also contains features, enhancements and fixes released in PU and PU For information on features, enhancements and fixes provided in PU and PU , see the following locations: CCS 11.0 PU CCS 11.0 PU Following is a list of new features and enhancements in PU :

10 10 What's New New features and enhancements in PU Table 1-1 New features and enhancements Policy Central Policy Central is a single portal to access your organizational policies and to manage policy attestations. Some of the following features from CCS Web portal are now available in CCS Policy Central. CCS Policy Central lets you interact with your organizational policies in the following ways: Read and download the published policies that are applicable to your department. Search policies based on your keywords. Accept or decline policies. Filter policies based on their status. Request exceptions or clarifications for your policies. Track all your exception and clarification requests. Mandate based reports Mandate Compliance Report provides a consolidated compliance view for Standards Manager, SCAP, and integrated external data systems. Mandate Compliance Report is the control centric report which includes the following: Pie chart displaying overall mandate compliance. High Level Section Summary table displaying compliance for high level sections of a mandate. Stacked Bar chart displaying rolled up section summary and Section Summary table for its sub-sections. Table containing control statement evaluation summary. Control Statement summary lets you view details on the fields displayed in the report. Mandate Remediation Report gives overview of remediation for failed controls. Mandate Remediation Report is the asset centric report which includes the following: Information on the High Level section summary Failed Control details along with source of the control for the Asset. Control Details table lets you view the following fields displayed in the report: Check, Mandate section, Collection Date, Risk Score, and Evidence. List of Controls With Remediation Information

11 What's New New features and enhancements in PU Table 1-1 New features and enhancements (continued) Assess Windows 2012 agent-based targets You can now collect data from the Windows 2012 platform. To collect data from Windows 2012 using agent-based method, you need to install the following: 1 Latest version of the CCS Agent. The new CCS Agent with Windows 2012 support can be downloaded from the Symantec Security Response Website. 2 Security Content Update , for Windows 2012 content. Use the following link to install Security Content Update : Security Content Update Support for CCS Assessment Manager 11.0 After applying PU , you can integrate CCS 11.0 with CCS Assessment Manager PU contains the following enhancements for CCS Assessment Manager integration: CCS provides an Assessment page in CCS Web Console for CCS AM assessments and also adds hyperlinks to the following portals to connect to CCS AM Server: CCS AM Administrative Console CCS AM End User Console The Assessment Message field from the following predefined reports now provides data for CCS AM to view detailed response on CCS AM assessments. Policy Results by Control Mandate Remediation Updates to Controls Studio Enable and Disable Control Statement options In the Controls Framework view, CCS adds Enable Control Statement option that lets you enable the control statement while Disable Control Statement option lets you disable the control statement. After you disable the Control Statement, it does not participate in any risk or compliance calculation. Disabled Control Statements are not available in Reports and Dashboards. All other CCS views or workspaces show the disabled Control Statements differentiated with an icon, however you can still map them and use such mappings for future use. When you copy a mandate all Control Statement mappings along with Control Statement state (Enable or disable) are retained from source mandate to copied mandate. Controls Studio also provides Filter option that lets you filter the control statements based on their states. Controls Studio view is enhanced with the following updates: Merging of Controls Framework and Control Statement workspaces Support for Hi-Trust framework

12 12 What's New New features and enhancements in PU Table 1-1 New features and enhancements (continued) Updates to Trend Panels CCS provides support for four new data models to create the trend panels for Policies, Mandates, and Standards. The CCS Dashboards page lets you create the trends to measure security assessment posture of your organization over a period of time. You can create custom trend panels based on the new data models. CCS adds pre-shipped trend source panels and trend panels to the Dashboards. Following trend panels, that are marked as deprecated, are still available on the CCS Dashboards page only for viewing old trend data: Compliance Trends by Standard (Deprecated) Monthly Status Trend of Checks (Deprecated) Overall Failure Trend of Checks (Deprecated) Control Status Trends for Policies (Deprecated) Control Status Trends for Mandates (Deprecated) Control Status Trends for HIPAA Mandates (Deprecated) Control Status Trends for ISO Mandates (Deprecated) Control Status Trends for NERC Mandates (Deprecated) Control Status Trends for PCI Mandates (Deprecated) Control Status Trends for SOX Mandates (Deprecated) Business Asset reconciliation updates Introduced conditions based Business Asset association during external data import as the Post Rule. Introduced range based conditions to filter resolved assets in the Update Rule. Introduced range based conditions to filter resolved assets for IPv4 and numeric format. Increased association limit per Business Asset from 1500 to Improved Business Asset association performance in the Post Rule during external data import. Ability to search assets on CCS Dashboard panels CCS provides a new search functionality to find assets in the asset constellation pages and custom panels. You can look for assets by keywords in the AssetDetails predefined panel and other tabular panels.

13 What's New New features and enhancements in PU Table 1-1 New features and enhancements (continued) Dashboard panel constellation pages with additional information The Failed External Data Assessments section, from Asset details constellation page displays a list of failed external data assessments and assessment procedures for the asset along with Provider or schema name. The Failed External Data Assessments section, from Assets evaluated and Asset details, provides the View Evidence link for CCS AM, CCS VM, and other external data systems. The View Evidence link opens a web dialog box, which displays the detailed information on the evidence that was collected. Only for CCS AM, View detailed response link is given to connect to CCS AM server. Risk Dashboard panel with revised drilldown options Top 5 Business Units at Highest Risk panel displays the following revised drilldown options: Top 10 Assets with Highest Risk Score option is the first option now. Overall Risk Business Unit option is removed. Multibrowser support for CCS The following versions of Web browsers are verified for CCS: Internet Explorer version 8.0 or 9.0 Mozilla Firefox version 20.0 (only on Windows) Google Chrome version 26.0 (only on Windows) Safari version 6.0 (only on the Macintosh) For information about configurations required on each browser to access the CCS Web Console or the Policy Central, see the Software Requirements section in the Symantec Control Compliance Suite 11.0 Planning and Deployment Guide. Database maintenance through CCS Console CCS displays an alert on the Product Health and Status area of the CCS Console Homepage, when the database maintenance plan is due. The alert is displayed if the index fragmentation in CCS databases goes above 90% or when the alert notification is due as per the number of days specified in the Health and Status Notifications configuration. Clicking the High index fragmentation alert link on the CCS Console Homepage launches a dialog box from where you can run the database maintenance or view a help topic for creating a database maintenance plan. Production data purge job added to the jobs view The Production data purge job is now added to the jobs view, to allow scheduling and notifications for the job, and view job status messages. The Production data purge job is executed to purge data from the Production database and ADAM.

14 14 What's New Before you begin installing PU Table 1-1 New features and enhancements (continued) Performance improvements in CCS Improved performance of panels and reports. Improved performance of the automatic data synchronization task, which runs as part of the evaluation job. Improved performance of the evaluation job. Improved job search and asset resolution. To optimize CCS performance the Update Statistics maintenance task is now run on the Reporting database every time the Global Metrics and Trend Computation job is run. Miscellaneous enhancements in CCS Using CCS PowerShell cmdlet you can now create dynamic asset groups based on the input parameters. From the Jobs view, you can now export the entire list of messages to a CSV file, which may span multiple pages, by using the Export All link. For better monitoring of jobs, the Status Details column of the jobs table in BrowseJobsView now displays the status "Job completed with <n> error/exception message(s)". Where <n> is the number of error messages. While exporting query results, for formats CSV, Excel and SQL, you can now export the list items in query results into individual rows per list item. On the CCS Console, in the Settings menu, the workspace User Management is now changed to "User Configuration". The policy document, either in PDF or Word document format, can be viewed from CCS Web Portal. You can view the policy document from the Document tab of Review Policies, Approve Policies, or Publish Policies page and add your comments for the selected policy. CCS has started supporting site-based routing for external data connection. Now you can specify the site name for the external data import while creating a new data connection or editing an existing one. The External Data Integration job routes to the site for which CCS Manager with Connector role is configured. Before you begin installing PU Consider the following before you install PU : If you are an existing Symantec Response Assessment Module (RAM) customer, note that PU provides limited backward compatibility with RAM 10.x and does not support rolling up of RAM assessment evidence for Compliance and Risk reporting in CCS Reporting and Analytics. If you are an existing customer using RAM, you must move to Symantec CCS Assessment Manager

15 What's New Before you begin installing PU (CCS AM) 11.0 before installing PU For more information, refer to CCS AM documentation. If you are an existing Vendor Risk Manager (VRM) customer, note that PU is not compatible with VRM 11.0 and must not be installed if VRM 11.0 is currently running with CCS 11.0, PU , or PU You can contact Technical Support for details on availability of a VRM update compatible with PU

16 16 What's New Before you begin installing PU

17 Chapter 2 Resolved Issues This chapter includes the following topics: Resolved Issues in PU Resolved Issues in PU Following issues are fixed in PU : Table 2-1 Resolved Issues Resolved Issues in PU During silent install, CCS Agent on UNIX prompted to verify the manager and agent communication. As a result, the installer did not proceed ahead, and waited for user response, which is not required while installing the agent in silent mode. This issue is resolved. The prompt to verify manager to agent communication does not appear during silent install. In case an Agent computer has multiple NICs, the CCS Agent got automatically registered to any random IP. If the user re-registers the agent, this would create a different asset with the different IP on CCS. Also the CCS Agent would get automatically registered on the backup IP even if the user may want to register the agent on the primary IP. To resolve this issue, the user can now specify a preferred IP address of the computer during agent registration. The CCS Manager uses the IP address specified while connecting to the Asset. The preferred IP address can be specified using the new switch -I, while registering the CCS agent on UNIX.

18 18 Resolved Issues Resolved Issues in PU Table 2-1 Resolved Issues (continued) Resolved Issues in PU CCS agent on SUSE LINUX would get registered using loop back IP address (For example, ). As a result the connection between the manager and an agent would fail and no task could be communicated to the agent. This issue is resolved. CCS now blocks all loop back IP addresses from being used during agent registration. When multiple agents were registered to the CCS Manager at the same time, the GUID generated for the agents were the same. This caused the agent import to replace one agent with another and as a result assets of the previous agent got scoped to the new agent. This resulted in failure of Data Collection for the assets. This issue is resolved. The guid generation logic is now corrected. CCS External data integration job failed with time-out error while fetching data using Web Services connector. The issue was observed when Web service took more than one minute for retrieving the dataset to CCS. To resolve the issue, CCS provides a configurable option to specify time-out and other settings for data connection. When the Windows server license was not installed, CCS displayed the following database warning message for the data collection job on Windows computer: The available licenses for Database data collection, exceed the required licenses limit: Database data collection license issue This issue is resolved. CCS provides a proper warning message specific to the data collection job. Reconciliation rules of Post type did not work when the field value for any asset was blank. This issue is resolved. The reconciliation rule of Post type works, even if the field value of an asset being imported is blank. While creating the custom panel, the filter values for the Results attribute of the Check entity were numeric instead of textual values. This issue is resolved. The list of values accepted by Check result attribute is now made intuitive. While executing Agent Management jobs like ping or Agent settings, the expression based routing rules based on domain name or host name were not getting considered. This issue is resolved. Now Hostname, domain name, or FQDN properties of the agent can be used to configure expression based routing rules.

19 Resolved Issues Resolved Issues in PU Table 2-1 Resolved Issues (continued) Resolved Issues in PU After running the data collection-evaluation-reporting job, the data collection date in the Data Collection Coverage dashboard panel was displayed incorrectly as 01/01/1900. This issue is resolved. The panels are updated to display the correct date. On the CCS Dashboard panel the drilldown page was taking more time to display. To resolve the issue, CCS now provides the following key that needs to be added in the web.config file of the panel in the in appsettings section: <add key="dynamicdashboard:drilldownqueryhint" value="expand VIEWS,maxdop=1"/> Automatic Synchronization activity in the Evaluation job took very long time to complete, after adding or updating the assets in the dynamic asset groups. This issue is resolved. The performance of the Automatic Synchronization activity is now optimized. In external data integration, CCS could not update the custom properties for Integer data type of an asset using the reconciliation rules. This issue is resolved. CCS allows you to update the Integer field through Update rule. CCS failed to delete the temporary files that were created in the Temp folder of the User s profile on performing the following tasks: visiting the Health and Status job, visiting the LiveUpdate workspace in CCS Console, running Automatic Updates Installation, Application Server service start, visiting the home page in CCS Console, visiting the Map View > Edit Setting > View Health and Status result. This issue is resolved. CCS now deletes the temp files when each task is successful. DBConvert did not clean the suppression records even after they had been removed from the ESM manager. As a result the reports continued to show the suppression data. To resolve this issue, a new parameter "dbconvert.cleansuppression" is added for the database conversion tool. If the value for the parameter dbconvert.cleansuppression is set to true, suppression records that do not exist on the ESM manager for a policy, are removed from the database. Certain types of errored out jobs were re-converted every time DBConvert utility was run, although DBConvert utility must convert each job only once. This issue is resolved. The DBConvert utility does not try to re-convert errored out jobs every time the utility is run.

20 20 Resolved Issues Resolved Issues in PU Table 2-1 Resolved Issues (continued) Resolved Issues in PU CCS 11.0 uses the CCS maintenance license to download raw data content. ESM required a separate content license to download message based content. This issue is resolved. As ESM is now part of the CCS Suite 11.0, ESM will also use the CCS maintenance license to download message based content. CCS displayed the following error message when Agent Product Update job failed to upgrade ESM agent: The given key was not present in the dictionary. This issue is resolved. The Agent Product Update job now upgrades the ESM agent. ESM Console consumed a lot of system memory resources and failed to update an ESM manager using LiveUpdate. This issue is resolved. Memory consumption of ESM Console is now optimized. ESM Console threw an error when a user tried to add a large number of assets from one domain to another domain. This issue is resolved. You can now add assets from one domain to another domain. Symantec has released updated binaries for the issues resolved on ESM components. The updated ESM binaries are separately available on the product support Web site from where you download the PU Web package.

21 Chapter 3 Installing PU This chapter includes the following topics: Installing the update Installing the update CCS does not support installing PU on the CCS Application Server or CCS Directory Server, using LiveUpdate. You can only perform a manual installation of PU on the CCS Application Server or CCS Directory Server. However, you can install PU on standalone CCS Managers, through the LiveUpdate workspace. Note: After you apply PU on all the CCS components, ensure that you run the Health and Status Job. The Health and Status Job helps you assess whether the components are updated and functioning perfectly. See the following sections for installing PU See Prerequisites for installing PU on page 21. See Installing PU on page 22. Prerequisites for installing PU The PU contains the latest feature enhancements and fixes for CCS The prerequisites to install the PU are as follows: You can install the PU only on an existing installation of CCS 11.0 or CCS PU or CCS PU For information on installing CCS 11.0, see the Symantec Control Compliance Suite Planning and Deployment Guide.

22 22 Installing PU Installing the update You must take a backup of all the computers where the product databases and the components are installed. You must close all remote consoles before you install the PU. Ensure that the user installing the PU is a member of the CCS Administrator role and has permissions to access the CCS databases. For more information on user privileges, see the Symantec Control Compliance Suite Planning and Deployment Guide. Ensure that no CCS jobs are executing. If your current deployment contains stand-alone CCS components, you must install the PU on each stand-alone component in the following order: CCS Directory Server CCS Application Server CCS Manager Note: Symantec recommends that you install the latest Microsoft security patches. Installing PU The Symantec Web site contains the Web package to be used for installing PU Downloading and extracting the PU Web package 1 Go to the product Web site where the Web packages are uploaded and download the Web package, CCS_11_0_3_2013-2_PU_Win.exe on the local computer. 2 Double-click the CCS_11_0_3_2013-2_PU_Win.exe file. The web package extracts the following files: CCS_11_0_INFRA_2013-2_PU_Win.exe CCS_11_0_CCSM_2013-2_PU_Win.exe update.manifest.xml CCS_11_0_3_PU_2013-2_ReadMe.html Use the CCS_11_0_INFRA_2013-2_PU_Win.exe file to update the following CCS components: CCS Application Server CCS Directory Server

23 Installing PU Installing the update 23 See Installing PU on CCS Application Server or CCS Directory Server Use the CCS_11_0_CCSM_2013-2_PU_Win.exe file to update a standalone CCS Manager. See Installing PU on a standalone CCS Manager Installing PU on CCS Application Server or CCS Directory Server You can only perform a manual installation of PU on CCS Application Server or CCS Directory Server To install PU on CCS Application Server or CCS Directory Server 1 Copy the CCS_11_0_INFRA_2013-2_PU_Win.exe file to the CCS Application Server or CCS Directory Server computer, and double-click the CCS_11_0_INFRA_2013-2_PU_Win.exe file. Setup prepares the CCS installation wizard. 2 In the Welcome panel of the launched Symantec Control Compliance Suite 11.0 installation wizard, read and accept the End-user license agreement, and then click Next. 3 Setup prompts you to verify the upgrade prerequisites. Click Yes to continue. 4 In the Summary panel, review the installation details and click Install.

24 24 Installing PU Installing the update 5 The Installation Progress panel indicates the progress of the installation. After the installation finishes, the Finish panel appears. If the installation is completed with warnings, a Warning panel displays warning messages or a Result panel displays critical errors, perform the remediation steps displayed in the Detail window to complete the installation. You can click the link, Log Files to view the installation log files. The log files are in.csv format. You can use the LogViewer in the <Install_Directory>\Application Server to view the log files. The LogViewer helps you to easily identify warnings and errors using the color codes. Warnings are highlighted in yellow color and errors are highlighted in red color. 6 In the Finish panel, review the installation result and then click Finish. You can click the link, Log Files to view the installation log files. The log files are in.csv format. You can use the LogViewer in the <Install_Directory>\Application Server to view the log files. The LogViewer helps you to easily identify warnings and errors using the color codes. Warnings are highlighted in yellow color and errors are highlighted in red color. You can check options to launch the CCS console or view the readme. Installing PU on a standalone CCS Manager You can install PU on a standalone CCS Manager using any of the following methods: Manual installation, Silent installation, or through the LiveUpdate workspace. To install PU manually on a standalone CCS Manager 1 Copy the CCS_11_0_CCSM_2013-2_PU_Win.exe file extracted in Step 2 in the section Downloading and extracting the PU Web package to the CCS Manager computer, and double-click the CCS_11_0_CCSM_2013-2_PU_Win.exe file. Setup prepares the CCS Manager installation wizard. 2 In the Welcome panel of the launched Symantec Control Compliance Suite 11.0 installation wizard, click Next. 3 Setup prompts you to verify the upgrade prerequisites. Click Yes to continue. 4 In the Summary panel, review the installation details and click Install.

25 Installing PU Installing the update 25 5 The Installation Progress panel indicates the progress of the installation. After the installation finishes, the Finish panel appears. If the installation is completed with warnings, a Warning panel displays warning messages or a Result panel displays critical errors, perform the remediation steps displayed in the Detail window to complete the installation. You can click the link, Log Files to view the CCS Manager installation log files. The log files are in.csv format. You can use the LogViewer in the <Install_Directory>\Application Server to view the log files. The LogViewer helps you to easily identify warnings and errors using the color codes. Warnings are highlighted in yellow color and errors are highlighted in red color. 6 In the Finish panel, review the installation result and then click Finish. You can click the link, Log Files to view the CCS Manager installation log files. The log files are in.csv format. You can use the LogViewer in the <Install_Directory>\Application Server to view the log files. The LogViewer helps you to easily identify warnings and errors using the color codes. Warnings are highlighted in yellow color and errors are highlighted in red color. You can check the option to view the readme. To install PU on a standalone CCS Manager in silent mode In the silent mode of installation, no user interface is displayed. 1 Copy the CCS_11_0_CCSM_2013-2_PU_Win.exe file extracted in Step 2 in the section Downloading and extracting the PU Web package to the CCS Manager computer. 2 On the command prompt, from the location where you have copied the CCS_11_0_CCSM_2013-2_PU_Win.exe file, run the following command to install the CCS Manager in silent mode: CCS_11_0_CCSM_2013-2_PU_Win.Exe /Silent Note: The command /Silent is case sensitive. To install PU on a standalone CCS Manager using the LiveUpdate workspace You can install the PU on CCS Manager using the Automatic Updates Installation job on CCS Console. Before running the Automatic Updates Installation job, perform the following steps:

26 26 Installing PU Installing the update 1 On the Application Server computer, in the CCS staging area at location %allusersprofile%\symantec\ccs\liveupdatestaging\ccs_pu\, move any existing folders for PU or PU to a temporary location, and then create a new folder with the name CCS110.11_0_10300_1148_CCS_PU. Such as %allusersprofile%\symantec\ccs\liveupdatestaging\ccs_pu\ CCS110.11_0_10300_1148_CCS_PU. 2 Copy the following files extracted in Step 2 in the section Downloading and extracting the PU Web package into the CCS110.11_0_10300_1148_CCS_PU folder created in the above step. CCS_11_0_CCSM_2013-2_PU_Win.exe update.manifest.xml CCS_11_0_3_PU_2013-2_ReadMe.html You must also copy the following files into the CCS110.11_0_10300_1148_CCS_PU folder. Web package file CCS_11_0_3_2013-2_PU_Win.exe CCS_11_0_3_PU_2013-2_ReadMe.pdf The CCS_11_0_3_PU_2013-2_ReadMe.pdf file is located on the product Web site from where you downloaded the Web package file CCS_11_0_3_2013-2_PU_Win.exe. 3 On the CCS Console, go to Manage > LiveUpdate, and then click Common Tasks > Check Updates to make the PU files available in the LiveUpdate workspace for deployment. 4 Go to Manage>LiveUpdate, and then click CommonTasks>DeployUpdates to configure and run the Automatic Updates Installation job. For more information on the Automatic Updates Installation job, see Copying and installing the updates section in the Symantec Control Compliance Suite 11.0 User Guide.

27 Chapter 4 Known Issues This chapter includes the following topics: Known Issues in PU Known Issues in PU The issues that are known in CCS are described as follows: Table 4-1 Known Issues Issue Description / Workaround If the same name as that of previously deleted external data system schemas is used for creating a new data schema, some issues are observed. Policy document or attachment, containing special characters or locale characters in the file name, is not getting downloaded properly on Mac Operating System with Safari browser. In Firefox browser on CCS Dashboards page if you try to export a panel, then the file gets exported in the following manner: Without any extension on auto saving at default location OR With.htm extension on specifying a location The exported file cannot be used to import the panel into CCS unless you change the file extension. While creating a data schema do not use the schema name that was used for any of previously deleted schemas in CCS. Right-click on the file and select the option "Download Linked File As" for downloading the policy document or attachment. Rename the exported panel file to.xml extension so that you can use it for import.

28 28 Known Issues Known Issues in PU Table 4-1 Issue Known Issues (continued) Description / Workaround Update API for updating assets fields fails with unhandled exception, if Assets Site attribute is not set. Set Asset Site attribute to default site.