Visibility tab - BlueCat Integrity - 26.1.0

Address Manager Administration Guide

ft:locale
en-US
Product name
BlueCat Integrity
Version
26.1.0

The Visibility page displays all existing Visibility Managers in a table, with all known details about Visibility jobs within those managers and the resource items found and imported into Address Manager.

A Visibility Manager is a collection of visibility jobs. Visibility jobs are created when you set up a Discovery job, then ask Cloud Discovery & Visibility (CDV) to maintain real-time updates of discovered resources on the network with the imported objects in BlueCat Address Manager. Within CDV, these jobs are organized into Visibility Managers: An abstracted layer to simplify your management of visibility jobs.

Note: A Visibility Manager does not represent a specific resource or object that might appear in a network. It is simply a convenient way to organize Visibility jobs when Discovery is performed on multiple resource groups or subscriptions.

When you perform actions on a Visibility Manager (Start, Stop, and so on), CDV performs those actions on all jobs within that Visibility Manager.

Tip: You can quickly perform many activities on a visibility manager in the list by clicking the action button (3 dots) in the far right column and choosing the desired action.

What jobs does a Visibility Manager contain?

Often, a Visibility Manager often contains only one job. A Visibility Manager contains multiple jobs only when CDV needs to maintain certain jobs separately that are otherwise part of the same task. Typically, this occurs when running Organization-level discovery and visibility: discovery operations from the top level of an organization.

The specific organization of jobs into Visibility managers depends on the infrastructure platform.

  • Amazon Web Platform (AWS): The jobs that a AWS Schedule Manager contains depend on whether or not you ran Discovery from the Organization level (that is, whether Discovery for Organization is selected in the AWS job settings: Credentials options).

    • If you run an Organization-level discovery job, a single visibility job is created that covers multiple organizational units—each of which can contain multiple accounts, and each account can contain multiple regions.

    • If you do not use Organization-level discovery, a single visibility job is created for a single account, which can contain multiple regions.

    If a Visibility Manager contains an account, subscription, or project that is later deleted from the network infrastructure, jobs associated with those resources will be deactivated and flagged as Deactivated on the Visibility page. You can Terminate (delete) deactivated jobs from the table there. Or, you can reactivate those jobs if those resources are later restored.

  • Google Cloud Platform (GCP): The jobs that a GCP Visibility Manager contains depend on whether or not you ran Discovery from the Organization level (that is, whether Discovery for Organization is selected in the GCP Service Account options).

    • If you run an Organization-level discovery job, the Visibility Manager that CDV creates will contain a separate job for each Project.

    • If you do not use Organization-level discovery, the Visibility Manager that CDV creates will contain only one job.

  • Microsoft Azure: The jobs that a Visibility Manager contains depend on the subscription and/or resource groups that you specify in the Azure Credentials settings:

    • Discovery of a specific subscription with a specific resource group: CDV will create a single Visibility Manager that contains a single Visibility job.

    • Discovery of a specific subscription with all resource groups: CDV will create a single Visibility Manager that contains multiple Visibility jobs — a single Visibility job for each resource group.

    • Discovery of all subscriptions with all resource groups: CDV will create a single Visibility Manager that contains multiple Visibility jobs — a single Visibility job for each resource group within each subscription.