Defining a Data Scope

When adding assets to a data scope, the configuration of asset subsets is inherited from the main asset type.

To define a data scope:

1. From the Data Scopes page, click + Add Data Scope.
2. Define which assets are included in the data scope according to the following methods.

There are a number of ways to define what assets are available in a data scope.

• Defining a Data Scope by Assets - You can define a data scope by selecting what asset types are to be included, Define by Assets. Then, for each asset type you can refine and further specify the included assets by creating a query that returns the assets to be included or by selecting specific fields to include or exclude from the data scope.
  • You can also apply a data scope profile to use a saved configuration of included or excluded fields.
• Defining a Data Scope by Adapter - Define which assets and fields appear in the data scope based on adapter connections. Use Define asset access by adapter connection to include or exclude assets fetched by specific adapters. Use Define field access by adapter connection to include or exclude fields retrieved by specific adapters.
• Restrict Data - You can hide adapter connection information and restrict data within a data scope by cloud account:
  • Managing Adapter Connection Information- By default, information about adapter connections is visible to users who can access the data scope. You can restrict the visibility of adapter connections here. Select the adapter connections whose information you want to block within the data scope.
  • Managing Cloud Accounts in the Data Scope- You can select which cloud accounts are visible to the data scope in the Cloud Compliance Center.

You can combine these methods to define a data scope. For example, you can include only Device assets in a data scope that are fetched by specific adapter connections.