If you are using ESM to collect asset data, you can upgrade to CCS to benefit from the new and improved data processing and reporting features offered by CCS 11.0. ESM data is now called message based data. CCS 11.0 introduces the CCS Manager, which is a replacement for the ESM Manager, and CCS Agent, which is a replacement for the ESM Agent. The CCS Agent interprets the data against the standards or policies and presents the data to CCS in the form of messages.
CCS Manager can collect raw-data using both agent-less and agent-based methods, and message based data using the agent-based method.
Raw-data based collection lets you collect asset data from your enterprise network. The collected data is then evaluated against a standard in CCS. You can collect raw-data using the agent-less method or the agent-based method.
Message based collection lets you collect and interpret asset data from your enterprise network before sending the data to CCS. The CCS Agent installed on each computer in the enterprise network performs the actual task of data collection and interpretation. The CCS Agent interprets the data against the standards or policies and presents the data to CCS in the form of messages.
The CCS Agent supports message based data collection from the following platforms.
Microsoft SQL Server
While migrating from an existing ESM deployment to CCS, you can either:
Perform a full migration by upgrading all ESM Managers to CCS Managers, and ESM Agents to CCS Agents.
Perform a phased migration by upgrading some ESM Managers to CCS Managers and corresponding ESM Agents to CCS Agents. You can continue to use some ESM Managers to collect data from corresponding ESM Agents.
You can choose to perform a phased migration if your existing deployment size is large. You can migrate to using CCS Managers and CCS Agents in place of ESM Managers and ESM Agents, only with a few computers at a time. In case of a phased migration, CCS 11.0 will continue to collect data from the ESM Managers until you upgrade that ESM Manager deployment to a CCS Manager deployment.
If you are performing a partial upgrade, and you do not want to upgrade the ESM Manager, you can upgrade the CCS Console and continue to use the ESM deployment and data collection as before. In this case, you must map the ESM policies to CCS standards using the ESM Policy to CCS Standard Migration Utility. For information on using the migration utility, see the Symantec™ Control Compliance Suite 11.0 User Guide.
If you are performing a partial upgrade, and you do not want to upgrade some ESM Agents, you can still import those agents into CCS using the Import assets and agents job. In this case, from the ESM Console, using LiveUpdate, you must push the LU_4201 package for Asset Information on to the ESM Agents, enable the Asset Information policy, and then run the Import assets and agents job to import those agents into CCS. The Asset Information policy allows CCS to import ESM Agents as Single Assets.
In your existing deployment, ESM Agents and assets that are already imported into CCS are marked as esm.agents. When you upgrade these ESM Agents to CCS Agents or when you push the LU_4201 package to these ESM Agents to import the agents into CCS 11.0, the next time when you run the Import assets and agents job, these agents get imported into CCS as single assets. In this case, CCS contains two separate records of an Asset. One record, which already exists into CCS as esm.agent and the second record of a single asset that gets created when you import the agents after upgrade. For such Assets, you can initiate policy runs on the esm.agent record or standards on the single asset record.