Skip to content

Asset Scope Management

Every asset Fencer tracks — repositories, cloud accounts, artifacts, network services, applications, domains, endpoints, and SaaS apps — has an in-scope or out-of-scope flag. Marking an asset out of scope excludes it from scope-based reporting and views without deleting it or stopping it from being scanned, which is useful for GRC/compliance reporting where only a subset of your environment counts toward a given audit or framework.

  • Assets already discovered by a scan or connected integration.
  • The assets:edit ability to change scope (Administrator and Team Member hold it). Anyone who can view assets can see each asset’s scope.

Scope is a simple in-scope / out-of-scope flag on each asset, and on the individual resources that make up that asset (for example, the services under a cloud account). Changing an asset’s scope cascades: it propagates from the asset to its resources, and further down to any child resources and the assets tied to them — so setting a cloud account out of scope also marks its resources out of scope, without needing to update each one individually.

Scope also affects vulnerability visibility: a vulnerability is treated as in scope based on the specific resource it was found on when available, falling back to the parent asset’s scope otherwise. Out-of-scope vulnerabilities are left out of:

  • Vulnerabilities synced to connected GRC integrations.
  • SLA tracking, including the Breached and Approaching counts on Home.
  • The In scope and True positives stages of the noise-reduction funnel on Home.
  • Vulnerability lists filtered with Scope is In scope.

On any asset list under Posture (Infrastructure, SaaS, Code, Artifacts, Domains, Network, Application, or Endpoint), the In Scope column shows the current value. Click it to open the Set Scope picker and switch between In Scope and Out of Scope directly from the list, without opening the asset’s detail page. You can also right-click a row and use its Scope submenu, or click the scope badge in an asset’s detail page header.

For a repository, the same setting appears as Compliance Scope in the repository’s Settings.

  1. Select multiple rows on any of the asset lists above, or on the Inventory tab of Main > Assets.
  2. Use the bulk action bar’s Set In Scope or Set Out of Scope action.
  3. Fencer applies the change to every selected asset (and cascades to their resources) and confirms how many assets were updated.

Excluding a decommissioned cloud account from an audit:

  1. Navigate to Posture > Infrastructure and select the account being decommissioned.
  2. Use the bulk action bar (or the inline In Scope column) to set it Out of Scope.
  3. The account’s resources and any vulnerabilities on them drop out of scope-filtered reporting, while the account remains visible and continues to be tracked.
  • A vulnerability still shows as in scope after marking its asset out of scope — Scope is resolved from the specific resource the vulnerability was detected on when Fencer has one; check that resource’s scope directly rather than only the parent asset’s.
  • Bulk scope change didn’t apply to a related resource — Cascading applies to resources whose root points back to the asset (or resource) you changed. A resource with no such relationship needs its scope set directly.