Who Controls My Scope Configuration?
By default, the scope configuration for all assets is controlled by our security operations team. Users can choose to manually configure the scope of individual assets by "opting in" to manual configuration.
Version Number: v1.0.0
Published Date: 26 Aug 2025
The function should be considered a BETA function as it has not been generally released and access to this functionality is available via request only.
____________________________________________________________________________
This can be done through the user interface on the scope configuration page for each asset where this feature is available.
Each of your web application assets has a flag indicating who is responsible for the scope configuration of that asset. This flag can be set to Automatic, Manual, or Restricted.
- Automatic
- Our security operation team is fully responsible for configuring the scope of the particular asset.
- Users have read-only access to their scope configuration.
- Manual
- You, or a member of your organization is fully responsible for configuring the scope of the asset.
- You, or a member of your organization has opted in to control the scope configuration of the asset.
- Our security operations team will not make any changes to your scope configuration unless deemed absolutely necessary.
- Users have read and write access to their scope configuration.
- Restricted
- Our security operation team is fully responsible for configuring the scope of the particular asset.
- Restricted assets cannot be manually configured by your organization and must be configured by our operations team at all times.
- You will not be able to opt in to manually configure assets which are set to restricted.
- This is typically reserved for assets which require PCI certification or other strict requirements.
Click here for more information regarding what your organization will be responsible for when opting in to manually configure an asset.