Cloud Discovery & Visibility (CDV) v24.1.1 has the following new features:
Cloud Networks summary enhancements
The Cloud Networks summary table has the following enhancements:
You can now sort the Cloud Networks summary table of available networks by Region. In addition, the Region column now displays the region in which each of these networks is hosted.
The Cloud Information column now displays the following platform-specific details:
-
Amazon Web Services (AWS): The AWS account number.
-
Google Cloud Platform (GCP): The Project ID and Email address.
-
Microsoft Azure: The Azure Tenant ID, the Subscription, and the Resource Group.
-
For more details, see Cloud Networks summary.
Podman container support
You can now deploy CDV into a Podman container. Podman is an open source container, pod, and container image management tool.
For more details, see Installing Cloud Discovery & Visibility into a Podman container.
(AWS) BAM Configuration names with the Region before the Account Name
You can now specify that CDV puts the Region before the Account Name when creating
BlueCat Address Manager Configurations (as in <Region
name>/<AWS account name>
) for AWS. To do so, in the
AWS Setup tab in the Configuration Options section, check the
Region Name Before Account Configuration Format checkbox
under BlueCat Configuration Mode.
(AWS) Enhanced filtering of AWS account tags for Organization-level Discovery jobs
When configuring filters for Organization-level Discovery jobs on AWS infrastructures, you can now both include and exclude accounts by Tag Names and Values. If an account has a Tag Name and value that you have specified as to be excluded, Discovery will not run on that account, regardless of whether or not it fits other filters.
For more details, see AWS Account Filter Options.
(AWS) New Discovery Options
When configuring Discovery Options for Amazon Web Services infrastructures, the following options are now available:
Ignore Default VPCs: When checked, the default VPC and its related resources (virtual machines, load balancers, private endpoints, elastic Kubernetes, and private DNS zones) will not be added to the BAM configuration during Discovery or Visibility jobs.
Create Stand-alone PTR Records: If checked, when a host record is created, the corresponding PTR record is also created. These PTR records will be located in external hosts under the internal view. This setting applies to both Discovery and Visibility jobs.
This setting is available only when either AWS EC2 Instances or AWS ELBv2 Load Balancers is checked, and AWS DNS Hostnames - Internal is checked.
(AWS) Ability to filter out VPCs by associated AWS Tag
You can now configure a set of AWS Tags and Tag values to exclude VPCs from discovery and visibility jobs. Any VPC (and its related resources such as virtual machines, load balancers, private endpoints, elastic Kubernetes, and private DNS zones) that has a matching AWS Tag and Tag value will be skipped during discovery and visibility.
To access these options, in the CDV banner, click AWS, then click the Setup tab and scroll down to AWS VPC Filter.
For more details, see AWS VPC Filter Options.
(AWS) Ability to import AWS resource tag details
For more details, see AWS Additional Tags Options.