Asset Scope Management
Overview
Section titled “Overview”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.
Prerequisites
Section titled “Prerequisites”- Assets already discovered by a scan or connected integration.
- Edit access to the relevant asset list (role-dependent, same as other asset management actions).
How it works
Section titled “How it works”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 and findings 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. Vulnerabilities on out-of-scope assets are excluded from scope-filtered vulnerability views.
Usage / Configuration
Section titled “Usage / Configuration”Editing scope inline
Section titled “Editing scope inline”On any asset list (Artifacts, Cloud, Code, Network, Application, Domains, Endpoints, or SaaS), the Scope column shows the current value. Click it to open a picker and switch between In Scope and Out of Scope directly from the list, without opening the asset’s detail page.
Bulk scope actions
Section titled “Bulk scope actions”- Select multiple rows on any of the asset lists above (or the artifacts/containers list specifically).
- Use the bulk action bar’s Set In Scope or Set Out of Scope action.
- Fencer applies the change to every selected asset (and cascades to their resources) and confirms how many assets were updated.
Examples
Section titled “Examples”Excluding a decommissioned cloud account from an audit:
- Navigate to the Cloud page and select the account being decommissioned.
- Use the bulk action bar (or the inline Scope column) to set it Out of Scope.
- 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.
Troubleshooting
Section titled “Troubleshooting”- 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.