Assign users to roles.

The role determines what you can see and perform in the CCS Console. In addition to the role, you must have permission on the required folders and objects to successfully perform a task.

See Adding users and groups to a role.

Create asset folders in the Manage > Asset System view.

The user-defined folders store business objects in a hierarchical manner that reflects your organizational structure. The user-defined folders let you effectively assign permissions.

When you install CCS, a default hierarchy structure is created to store objects. Users should organize the tree to follow the flow of control in the organization.

See Creating the asset folders.

Assign permissions to trustees.

You must manually assign permissions to the user-defined folders. When a role is assigned to a user, permissions are automatically granted to the objects in the predefined folders.

See Assigning permissions from the Permission Management view.

Create sites to match the structure in the deployment plan.

You create sites to manage logical groups of assets. Grouping of assets facilitate data collection and other CCS operations.

See Creating a site.

Register installed Data Processing Service instances.

Before the Application Server can use a newly installed Data Processing Service (DPS), you must register the DPS with the Application Server. When you register the DPS, you also assign the DPS to a site and specify the DPS roles. Where appropriate, specify data types to collect.

See Registering the Data Processing Service.

Create asset import reconciliation rules as specified in the deployment plan.

The reconciliation rules let you filter the potential assets before they enter the asset system. The reconciliation rules also help to update the field values of the existing assets.

See Creating reconciliation rules using the manual review.

See Creating reconciliation rules without manual review.

Create asset import jobs.

You must import assets from the network before you can collect data from the assets and evaluate the assets against specific standards and checks.

You can import the assets in one of the following ways:

See Importing the assets for the first time.

See Importing asset-specific fields from the default data collector.

See Importing asset-specific and common fields using the default data collector.

See Importing asset-specific and common fields using the CSV data collector.

See Importing the specific and common fields for custom asset using the CSV data collector.

See Working with asset import scenarios.

Set up data collection jobs.

After you have imported the assets you create jobs to collect data from the imported assets.

See Setting up a data collection job.

Create evaluation jobs.

After you have collected the data from the imported assets you create jobs to evaluate the assets.

See Running an evaluation job.

Mark and configure entitlement control points.

You mark an asset as a control point to monitor the entitlements of the asset through the approval workflow.

See Marking an asset as a control point.

You configure a control point to assign a data owner, an approver, the tags, and the review cycle to the control point

See Configuring control points.

Create report jobs.

The report job generates a report with the data from the reporting database.

You must synchronize the reporting database to view the latest data before you run a report job.

The Scheduled Reporting Database Synchronization job is an existing job in the Monitor > Jobs view.

See Running a job now.

See Scheduling a report .

Create dashboard jobs.

The dashboard job generates the dashboard with the data from the reporting database.

You must synchronize the reporting database to view the latest data before you run a dashboard job.

The Scheduled Reporting Database Synchronization job is an existing job in the Monitor > Jobs view.

See Running a job now.

See Scheduling a dashboard .

Create policies.

Policies are rules established by an organization. Policies are designed to guide their employees. You can create a policy from scratch or import a Microsoft Word document as a policy.

See Creating a new policy.

See Importing a Word policy.

Publish policies.

After a policy is created and approved, the policy is published to the selected audience members in the organization. The audience members can access the policy from the CCS Web Portal.

See Publishing a policy.

Optionally publish Response Assessment module questionnaires.

See Symantec Response Assessment module User Guide for information on publishing questionnaires.

See About Response Assessment module (RAM).