Configure the Cisco Secure Dynamic Attributes Connector

Install the dynamic attributes connector and configure connectors, dynamic attributes filters, and adapters to provide management center with dynamic network data that can be used in access control rules.

The dynamic attributes connector enables you to configure connectors to provide the management center with dynamic network data that can be used in access control rules.

See the following topics for more information:

Create a Connector

A connector is an interface with a cloud service. The connector retrieves network information from the cloud service so the network information can be used in access control policies on the management center.

We support the following:

Table 1. List of supported connectors by Cisco Secure Dynamic Attributes Connector version and platform

CSDAC version/platform

A.W.S.

Git- Hub

Google Cloud

Azure

Azure Service Tags

Microsoft Office 365

VMware vCenter

Version 1.1 (on-premises)

Yes

No

No

Yes

Yes

Yes

Yes

Version 2.0 (on-premises)

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Cloud-delivered (Cisco Defense Orchestrator)

Yes

Yes

Yes

Yes

Yes

Yes

No

See one of the following sections for more information.

Amazon Web Services Connector—About User Permissions and Imported Data

The Cisco Secure Dynamic Attributes Connector imports dynamic attributes from AWS to the management center for use in access control policies.

Dynamic attributes imported

We import the following dynamic attributes from AWS:

  • Tags, user-defined key-value pairs you can use to organize your AWS EC2 resources.

    For more information, see Tag your EC2 Resources in the AWS documentaiton

  • IP addresses of virtual machines in AWS.

Minimum permissions required

The Cisco Secure Dynamic Attributes Connector requires a user at minimum with a policy that permits ec2:DescribeTags and ec2:DescribeInstances to be able to import dynamic attributes.

Create an AWS User with Minimal Permissions for the Cisco Secure Dynamic Attributes Connector

This task discusses how to set up a service account with minimum permissions to send dynamic attributes to the management center. For a list of these attributes, see Amazon Web Services Connector—About User Permissions and Imported Data.

Before you begin

You must already have set up your Amazon Web Services (AWS) account. For more information about doing that, see this article in the AWS documentation.

Procedure
Step 1

Log in to the AWS console as a user with the admin role.
Step 2

From the Dashboard, click Security, Identity & Compliance > IAM.

Step 3

Click Access Management > Users.

Step 4

Click Add Users.

Step 5

In the User Name field, enter a name to identify the user.

Step 6

Click Access Key - Programmatic Access.

Step 7

At the Set permissions page, click Next without granting the user access to anything; you'll do this later.

Step 8

Add tags to the user if desired.
Step 9

Click Create User.

Step 10

Click Download .csv to download the user's key to your computer.

Note 

This is the only opportunity you have to retrieve the user's key.
Step 11

Click Close.

Step 12

At the Identity and Access Management (IAM) page in the left column, click Access Management > Policies.

Step 13

Click Create Policy.

Step 14

On the Create Policy page, click JSON.

Create a JSON policy
Step 15

Enter the following policy in the field:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "ec2:DescribeTags",
                "ec2:DescribeInstances"
            ],
            "Resource": "*"
        }
    ]
}
Step 16

Click Next.

Step 17

Click Review.

Step 18

On the Review Policy page, enter the requested information and click Create Policy.

Step 19

On the Policies page, enter all or part of the policy name in the search field and press Enter.
Step 20

Click the policy you just created.
Step 21

Click Actions > Attach.

Step 22

If necessary, enter all or part of the user name in the search field and press Enter.
Step 23

Click Attach Policy.

What to do next

Create an AWS Connector.

Create an AWS Connector

This task discusses how to configure a connector that sends data from AWS to the management center for use in access control policies.

Before you begin
Create a user with at least the privileges discussed in Create an AWS User with Minimal Permissions for the Cisco Secure Dynamic Attributes Connector.
Procedure
Step 1

Log in to the dynamic attributes connector.

Step 2

Click Connectors.

Step 3

Do any of the following:

  • Add a new connector: click Add (add icon), then click the name of the connector.

  • Edit or delete a connector: Click More (more icon), then click Edit or Delete at the end of the row.

Step 4

Enter the following information.

Value

Description

Name

(Required.) Enter a name to uniquely identify this connector.

Description

Optional description.

Pull Interval

(Default 30 seconds.) Interval at which IP mappings are retrieved from AWS.

Region

(Required.) Enter your AWS region code.

Access Key

(Required.) Enter your access key.

Secret Key

(Required.) Enter your secret key.
Step 5

Click Test and make sure the test succeeds before you save the connector.

Step 6

Click Save.

Step 7

Make sure Ok is displayed in the Status column.

What to do next

Create an Adapter

Azure Connector—About User Permissions and Imported Data

The Cisco Secure Dynamic Attributes Connector imports dynamic attributes from Azure to the management center for use in access control policies.

Dynamic attributes imported

We import the following dynamic attributes from Azure:

  • Tags, key-value pairs associated with resources, resource groups, and subscriptions.

    For more information, see this page in the Microsoft documentation.

  • IP addresses of virtual machines in Azure.

Minimum permissions required

The Cisco Secure Dynamic Attributes Connector requires a user at minimum with the Reader permission to be able to import dynamic attributes.

Create an Azure User with Minimal Permissions for the Cisco Secure Dynamic Attributes Connector

This task discusses how to set up a service account with minimum permissions to send dynamic attributes to the management center. For a list of these attributes, see Azure Connector—About User Permissions and Imported Data.

Before you begin

You must already have a Microsoft Azure account. To set one up, see this page on the Azure documentation site.

Procedure
Step 1

Log in to the Azure Portal as the owner of the subscription.

Step 2

Click Azure Active Directory.

Step 3

Find the instance of Azure Active Directory for the application you want to set up.
Step 4

Click Add > App registration.

Step 5

In the Name field, enter a name to identify this application.

Step 6

Enter other information on this page as required by your organization.
Step 7

Click Register.

Step 8

On the next page, make note of the Client ID (also referred to as application ID) and the tenant ID (also referred to as the directory ID).

A sample follows.

Make note of the application and tenant ID
Step 9

Click Add a certificate or secret.

Step 10

Click New Client Secret.

Step 11

Enter the requested information and click Add.

Step 12

Copy the client secret ID to the clipboard because you'll need it to set up the Azure connector.

Copy the client ID secret to the clipboard now because you will not see it again
Step 13

Go back to the main Azure Portal page and click Subscriptions.

Step 14

Copy the subscription ID to the clipboard.
Step 15

On the subscriptions page, click the name of the subscription.
Step 16

Click Access Control (IAM).

Step 17

Click Add > Add role assignment.

Step 18

Click Reader and click Next.

Step 19

Click Select Members.

Step 20

On the right side of the page, click the name of the app you registered and click Select.

Associate the role with your app
Step 21

Click Review + Assign and follow the prompts to complete the action.

What to do next

See Create an Azure Connector.

Create an Azure Connector

This task discusses how to create a connector to send data from Azure to management center for use in access control policies.

Before you begin
Create an Azure user with at least the privileges discussed in Create an Azure User with Minimal Permissions for the Cisco Secure Dynamic Attributes Connector.
Procedure
Step 1

Log in to the dynamic attributes connector.

Step 2

Click Connectors.

Step 3

Do any of the following:

  • Add a new connector: click Add (add icon), then click the name of the connector.

  • Edit or delete a connector: Click More (more icon), then click Edit or Delete at the end of the row.

Step 4

Enter the following information.

Value

Description

Name

(Required.) Enter a name to uniquely identify this connector.

Description

Optional description.

Pull Interval

(Default 30 seconds.) Interval at which IP mappings are retrieved from Azure.

Subscription Id

(Required.) Enter your Azure subscription ID.

Tenant Id

(Required.) Enter your tenant ID.

Client Id

(Required.) Enter your client ID.

Client Secret

(Required.) Enter your client secret.
Step 5

Click Test and make sure Test connection succeeded is displayed before you save the connector.

Step 6

Click Save.

Step 7

Make sure Ok is displayed in the Status column.

What to do next

Create an Adapter

Create an Azure Service Tags Connector

This topic discusses how to create a connector for Azure service tags to the management centerfor use in access control policies. The IP addresses association with these tags are updated every week by Microsoft.

For more information, see Virtual network service tags on Microsoft TechNet.

Procedure

Step 1

Log in to the dynamic attributes connector.

Step 2

Click Connectors.

Step 3

Do any of the following:

  • Add a new connector: click Add (add icon), then click the name of the connector.

  • Edit or delete a connector: Click More (more icon), then click Edit or Delete at the end of the row.

Step 4

Enter the following information.

Value

Description

Name

(Required.) Enter a name to uniquely identify this connector.

Description

Optional description.

Pull Interval

(Default 30 seconds.) Interval at which IP mappings are retrieved from Azure.

Subscription Id

(Required.) Enter your Azure subscription ID.

Tenant Id

(Required.) Enter your tenant ID.

Client Id

(Required.) Enter your client ID.

Client Secret

(Required.) Enter your client secret.
Step 5

Click Test and make sure Test connection succeeded is displayed before you save the connector.

Step 6

Click Save.

Step 7

Make sure Ok is displayed in the Status column.

What to do next

Create an Adapter

Create a GitHub Connector

This section discusses how to create a GitHub connector that sends data to the management centerfor use in access control policies. The IP addresses associated with these tags are maintained by GitHub. You do not have to create a dynamic attributes filters.

For more information, see About GitHub's IP addresses.


Note

Do not change the URL because doing so will fail to retrieve any IP addresses.

Procedure

Step 1

Log in to the dynamic attributes connector.

Step 2

Click Connectors.

Step 3

Do any of the following:

  • Add a new connector: click Add (add icon), then click the name of the connector.

  • Edit or delete a connector: Click More (more icon), then click Edit or Delete at the end of the row.

Step 4

Enter a Name and an optional description.

Step 5

(Optional.) In the Pull Interval field, change the frequency, in seconds, at which the dynamic attributes connector retrieves IP addresses from GitHub. The default is 21,600 seconds (6 hours).

Step 6

Click Test and make sure the test succeeds before you save the connector.

Step 7

Click Save.

Step 8

Make sure Ok is displayed in the Status column.

What to do next

Create an Adapter

Google Cloud Connector—About User Permissions and Imported Data

The Cisco Secure Dynamic Attributes Connector imports dynamic attributes from Google Cloud to the management center for use in access control policies.

Dynamic attributes imported

We import the following dynamic attributes from Google Cloud:

  • Labels, key-value pairs you can use to organize your Google Cloud resources.

    For more information, see Creating and Managing Labels in the Google Cloud documentation.

  • Network tags, key-value pairs associated with an organization, folder, or project.

    For more information, see Creating and Managing Tags in the Google Cloud documentation.

  • IP addresses of virtual machines in Google Cloud.

Minimum permissions required

The Cisco Secure Dynamic Attributes Connector requires a user at minimum with the Basic > Viewer permission to be able to import dynamic attributes.

Create a Google Cloud User with Minimal Permissions for the Cisco Secure Dynamic Attributes Connector

This task discusses how to set up a service account with minimum permissions to send dynamic attributes to the management center. For a list of these attributes, see Google Cloud Connector—About User Permissions and Imported Data.

Before you begin

You must already have set up your Google Cloud account. For more information about doing that, see Setting Up Your Environment in the Google Cloud documentation.

Procedure
Step 1

Log in to your Google Cloud account as a user with the owner role.

Step 2

Click IAM & Admin > Service Accounts > Create Service Account.

Step 3

Enter the following information:

  • Service account name: A name to identify this account; for example, CSDAC.

  • Service account ID: Should be populated with a unique value after you enter the service account name.

  • Service account description: Enter an optional description.

For more information about service accounts, see Understanding Service Accounts in the Google Cloud documentation.

Step 4

Click Create and Continue.

Step 5

Follow the prompts on your screen until the Grant users access to this service account section is displayed.
Step 6

Grant the user the Basic > Viewer role.

Step 7

Click Done.

A list of service accounts is displayed.
Step 8

Click More (more icon) at the end of the row of the service account you created.

Step 9

Click Manage Keys.

Step 10

Click Add Key > Create New Key.

Create a new key for your user
Step 11

Click JSON.

Step 12

Click Create.

The JSON key is downloaded to your computer.
Step 13

Keep the key handy when you configure the GCP connector.
What to do next

See Create a Google Cloud Connector.

Create a Google Cloud Connector

Before you begin

Have your Google Cloud JSON-formatted service account data ready; it's required to set up the connector.

Procedure
Step 1

Log in to the dynamic attributes connector.

Step 2

Click Connectors.

Step 3

Do any of the following:

  • Add a new connector: click Add (add icon), then click the name of the connector.

  • Edit or delete a connector: Click More (more icon), then click Edit or Delete at the end of the row.

Step 4

Enter the following information.

Value

Description

Name

(Required.) Enter a name to uniquely identify this connector.

Description

Optional description.

Pull Interval

(Default 30 seconds.) Interval at which IP mappings are retrieved from AWS.

GCP region

(Required.) Enter the GCP region in which your Google Cloud is located. For more information, see Regions and Zones in the Google Cloud documentation.

Service account

Paste the JSON code for your Google Cloud service account.
Step 5

Click Test and make sure the test succeeds before you save the connector.

Step 6

Click Save.

Step 7

Make sure Ok is displayed in the Status column.

What to do next

Create an Adapter

Create an Office 365 Connector

This task discusses how to create a connector for Office 365 tags to send data to the management center for use in access control policies. The IP addresses associated with these tags are updated every week by Microsoft. You do not have to create a dynamic attributes filter to use the data.

For more information, see Office 365 URLs and IP address ranges on docs.microsoft.com.

Procedure

Step 1

Log in to the dynamic attributes connector.

Step 2

Click Connectors.

Step 3

Do any of the following:

  • Add a new connector: click Add (add icon), then click the name of the connector.

  • Edit or delete a connector: Click More (more icon), then click Edit or Delete at the end of the row.

Step 4

Enter the following information.

Value

Description

Name

(Required.) Enter a name to uniquely identify this connector.

Description

Optional description.

Pull Interval

(Default 30 seconds.) Interval at which IP mappings are retrieved from Azure.

Base API URL

(Required.) Enter the URL from which to retrieve Office 365 information, if it's different from the default. For more information, see Office 365 IP Address and URL web service on the Microsoft documentation site.

Instance name

(Required.) From the list, click an instance name. For more information, see Office 365 IP Address and URL web service on the Microsoft documentation site.

Disable optional IPs

(Required.) Enter true or false .

Step 5

Click Save.

Step 6

Make sure Ok is displayed in the Status column.

What to do next

Create an Adapter

vCenter Connector—About User Permissions and Imported Data

The Cisco Secure Dynamic Attributes Connector imports dynamic attributes from vCenter to the management center for use in access control policies.

Dynamic attributes imported

We import the following dynamic attributes from vCenter:

  • Operating system

  • MAC address

  • IP addresses

  • NSX tags

Minimum permissions required

The Cisco Secure Dynamic Attributes Connector requires a user at minimum with the Read Only permission to be able to import dynamic attributes.

Fetch a Certificate Authority (CA) Chain for a vCenter Connector

This topic discusses how to automatically fetch the certificate authority change for a connector or an adapter. The certificate authority chain is the root certificate and all subordinate certificates; it is required to connect securely with vCenter or the management center.

The dynamic attributes connector enables you to automatically fetch the certificate authority chain but if this procedure does not work for some reason, see Manually Get a Certificate Authority (CA) Chain.

Procedure
Step 1

Log in to the dynamic attributes connector.

Step 2

Do any of the following:

  1. To fetch a vCenter CA chain, click Connectors.

  2. To fetch the management center adapter CA chain, click Adapters.

  3. Click Add (add icon).

Step 3

In the Name field, enter a name to identify the connector or adapter.

Step 4

In the Host field, enter the connector or adapter's host name or IP address without the scheme (such as https:// ).

For example, myvcenter.example.com or 192.0.2.100:9090

The host name or IP you enter must exactly match the Common Name of the CA certificate used to securely connect to it.

No other information is required to fetch the certificate CA chain.
Step 5

Click Fetch.

Step 6

(Optional.) Expand the certificates in the certificate CA chain to verify them.
Example
Following is an example of a successful certificate CA fetch for a vCenter connector.

The certificates in the CA chain are displayed at the top of the dialog box

Expanding the certificate CA chain at the top of the dialog box displays the certificates similar to the following.

Expand each certificate to see more details

Create a vCenter Connector

This task discusses how to create a connector for VMware vCenter to send data to the management center for use in access control policies.

Before you begin

If you use non-trusted certificates to communicate with vCenter, see Manually Get a Certificate Authority (CA) Chain.

Procedure
Step 1

Log in to the dynamic attributes connector.

Step 2

Click Connectors.

Step 3

Do any of the following:

  • Add a new connector: click Add (add icon), then click the name of the connector.

  • Edit or delete a connector: Click More (more icon), then click Edit or Delete at the end of the row.

Step 4

Enter the following information.

Value

Description

Name

(Required.) Enter a name to uniquely identify this connector.

Description

Enter an optional description.

Pull Interval

(Default 30 seconds.) Interval at which IP mappings are retrieved from vCenter.

Host

(Required.) Enter any of the following:

  • vCenter's fully qualified host name

  • vCenter's IP address

  • (Optional.) A port

Do not enter a scheme (such as https://) or trailing slash.

For example, myvcenter.example.com or 192.0.2.100:9090

User

(Required.) Enter the user name of a user with the Read-only role at minimum. User names are case-sensitive.

Password

(Required.) Enter the user's password.

NSX IP

If you use vCenter Network Security Visualization (NSX), enter its IP address.

NSX User

Enter the user name of an NSX user with the Auditor role at minimum.

NSX Type

Enter NSX-T.

NSX Password

Enter the NSX user's password.

vCenter Certificate
Step 5

Click Test and make sure Test connection succeeded is displayed before you save the connector.

Step 6

Click Save.

What to do next

Create an Adapter

Create an Adapter

An adapter is a secure connection to management center to which you push network information from cloud objects for use in access control policies.

First you can optionally fetch the certificate authority chain, which is required to securely connect to the management center.

Fetching the certificate authority chain requires only the management center host name; creating the adapter requires a user name, password, and other information.

Create a Secure Firewall Management Center User for the Dynamic Attributes Connector

We recommend you create a dedicated management center user for the dynamic attributes connector adapter. Creating a dedicated management center user avoids issues like unexpected logouts from the management center because the dynamic attributes connector periodically logs in using a REST API to update the management center with new and updated dynamic objects.

The management center user must have Access Admin privileges at least.

Procedure

Step 1

Log in to the management center if you haven't already done so.

Step 2

Click Integration > Users.

Step 3

Click Create User.

Step 4

Enter the information required to create the user.

Step 5

Under User Role Configuration, check any of the following default roles or a custom role with the same privilege level:

  • Administrator

  • Access Admin

  • Network Admin

The following figure shows an example.

Choose a role for the FMC adapter

You can also choose a custom role with sufficient privileges to allow REST actions or a different default role with sufficient privileges. For more information about default roles, see the User Roles section in the chapter on user accounts.

What to do next

Create an Adapter

Fetch a Certificate Authority (CA) Chain for an On-Prem Firewall Management Center Adapter

This topic discusses how to automatically fetch the certificate authority change for a connector or an adapter. The certificate authority chain is the root certificate and all subordinate certificates; it is required to connect securely with vCenter or the management center.

The dynamic attributes connector enables you to automatically fetch the certificate authority chain but if this procedure does not work for some reason, see Manually Get a Certificate Authority (CA) Chain.

Procedure

Step 1

Log in to the dynamic attributes connector.

Step 2

Do any of the following:

  1. To fetch a vCenter CA chain, click Connectors.

  2. To fetch the management center adapter CA chain, click Adapters.

  3. Click Add (add icon).

Step 3

In the Name field, enter a name to identify the connector or adapter.

Step 4

In the Host field, enter the connector or adapter's host name or IP address without the scheme (such as https:// ).

For example, myvcenter.example.com or 192.0.2.100:9090

The host name or IP you enter must exactly match the Common Name of the CA certificate used to securely connect to it.

No other information is required to fetch the certificate CA chain.
Step 5

Click Fetch.

Step 6

(Optional.) Expand the certificates in the certificate CA chain to verify them.

Example

Following is an example of a successful certificate CA fetch for a vCenter connector.

Sample of fetching a CA certificate for a vCenter connector

Expanding the certificate CA chain at the top of the dialog box displays the certificates similar to the following.

You can see the certificates in the chain if you expand the certificates

How to Create an On-Prem Firewall Management Center Adapter

This topic discusses how to create an adapter to push dynamic objects from the dynamic attributes connector to the management center.

Before you begin

See Create a Secure Firewall Management Center User for the Dynamic Attributes Connector.

Procedure

Step 1

Log in to the dynamic attributes connector.

Step 2

Click Adapters.

Step 3

Do any of the following:

  • Add a new adapter: click Add (add icon), then click On-Prem Firewall Management Center.

  • Edit or delete an adapter: Click More (more icon), then click Edit or Delete at the end of the row.

Step 4

Enter the following information.

Value

Description

Name

(Required.) Enter a unique name to identify this adapter.

Description

Optional description of the adapter.

Domain

Enter the Secure Firewall Management Center Virtual domain in which to create dynamic objects. Leave the field blank to create dynamic objects in the Global domain.

For example, Global/MySubdomain

IP

(Required.) Enter your Secure Firewall Management Center Virtual's host name or IP address.

The host name or IP you enter must exactly match the Common Name of the CA certificate used to securely connect to it.

Port

(Required.) Enter the TLS port used by your Secure Firewall Management Center Virtual.

User

(Required.) Enter the name of an Secure Firewall Management Center Virtual user with the Network Admin role at minimum.

Password

(Required.) Enter the user's password.

Secondary IP

(High availability only.) Enter the secondary Secure Firewall Management Center Virtuals host name or IP address.

The host name or IP you enter must exactly match the Common Name of the CA certificate used to securely connect to it.

Secondary Port

(High availability only.) Enter the TLS port used by your secondary Secure Firewall Management Center Virtual.

Secondary User

(High availability only.) Enter the name of a secondary Secure Firewall Management Center Virtual user with the Network Admin role at minimum.

Secondary Password

(High availability only.) Enter the user's password.

Server Certificate

Click Fetch to automatically fetch the certifcate or, if that is not possible, get the certificate manually as discussed in Manually Get a Certificate Authority (CA) Chain.

Step 5

Click Test and make sure the test succeeds before you save the adapter.

Step 6

Click Save.

Create a Cloud-Delivered Firewall Management Center Adapter

This topic discusses how to create an adapter to push dynamic objects from the dynamic attributes connector to a managed management center on the Cisco Defense Orchestrator.

Before you can create a Cloud-Delivered Firewall Management Center, get the following information first: Get Your Base URL and API Token.

Get Your Base URL and API Token

This task dicusses how to get the URL and API token from CDO that are required to create a Cloud-Delivered Firewall Management Center adapter.

Before you begin
You must be a CDO Super Admin to complete the tasks discussed in this section.
Procedure
Step 1

Log in to CDO as a user with the Super Admin role.

Step 2

In the upper right corner of the page, click Settings.

Step 3

Click General Settings.

Step 4

Next to API Token, click Refresh.

Step 5

Copy the API token to a text file for later use.
Step 6

Click Tools & Services > Firewall Management Center.

Step 7

Click the name of the management center to which to send dynamic attributes connector data.

Step 8

The value of Hostname, preceded by https://, is the base URL.

An example follows:

Your base URL for a management center managed by CDO is under Tools & Services > Firewall Management Center. Look for the value of Hostname.
What to do next

How to Create a Cloud-Delivered Firewall Management Center Adapter.

How to Create a Cloud-Delivered Firewall Management Center Adapter

This task discusses how to create a Cloud-Delivered Firewall Management Center adpater that sends data from the dynamic attributes connector to a device managed by CDO.

Before you begin

You must get the management center base URL and API token from CDO before you can complete this task. For more information, see Get Your Base URL and API Token.

Procedure
Step 1

Log in to the dynamic attributes connector.

Step 2

Click Adapters.

Step 3

Do any of the following:

  • Add a new adapter: click Add (add icon), then click Cloud-Delivered Firewall Management Center.

  • Edit or delete an adapter: Click More (more icon), then click Edit or Delete at the end of the row.

Step 4

Enter the following information.

Value

Description

Name

(Required.) Enter a unique name to identify this adapter.

Description

Optional description of the adapter.

Base Url

 (Required.) Use the Base URL you found in Get Your Base URL and API Token.

API Token

(Required.) Use the API token you found in Get Your Base URL and API Token.

Step 5

Click Test and make sure the test succeeds before you save the adapter.

Step 6

Click Save.

What to do next

Create Dynamic Attributes Filters.

Create Dynamic Attributes Filters

Dynamic attributes filters that you define using the Cisco Secure Dynamic Attributes Connector are exposed in the management center as dynamic objects that can be used in access control policies. For example, you could restrict access to an AWS server for the Finance Department to only members of the Finance group defined in Microsoft Active Directory.


Note

You cannot create dynamic attributes filters for GitHub, Office 365, or Azure Service Tags. These types of cloud objects provide their own IP addresses.

For more information about access control rules, see Create Access Control Rules Using Dynamic Attributes Filters.

Before you begin

Complete all of the following tasks:

Procedure

Step 1

Log in to the dynamic attributes connector.

Step 2

Click Dynamic Attributes Filters.

Step 3

Do any of the following:

  • Add a new filter: click Add (add icon).

  • Edit or delete a filter: Click More (more icon), then click Edit or Delete at the end of the row.

Step 4

Enter the following information.

Item

Description

Name

Unique name to identify the dynamic filter (as a dynamic object) in access control policy and in the management center Object Manager (External Attributes > Dynamic Object).

Connector

From the list, click the name of a connector to use.

Query

  • Add a new filter: click Add (add icon).

  • Edit or delete a filter: Click More (more icon), then click Edit or Delete at the end of the row.

Step 5

To add or edit a query, enter the following information.

Item Description

Key

 Click a key from the list. Keys are fetched from the connector.

Operation

 Click one of the following:

  • Equals to exactly match the key to the value.

  • Contains to match the key to the value if any part of the value matches.

Values

 Click either Any or All and click one or more values from the list. Click Add another value to add values to your query.
Step 6

Click Show Preview to display a list of networks or IP addresses returned by your query.

Step 7

When you're finished, click Save.

Step 8

(Optional.) Verify the dynamic object in the management center.

  1. Log in to the management center as a user with the Network Admin role at minimum.

  2. Click Objects > Object Manager.

  3. In the left pane, click External Attributes > Dynamic Object.

    The dynamic attribute query you created should be displayed as a dynamic object.

Dynamic Attribute Filter Examples

This topic provides some examples of setting up dynamic attribute filters.

Examples: vCenter

The following example shows one criterion: a VLAN.

This sample shows a simple vCenter dynamic attributes filter that finds a VLAN

The following example shows three criteria that are joined with OR: the query matches any of three hosts.

Another sample vCenter dynamic attributes filter that finds any of three hosts; the query is joined by OR

Example: Azure

The following example shows one criterion: a server tagged as a Finance app.

Sample Azure dynamic attributes filter that finds the Finance app tag

Example: AWS

The following example shows one criterion: a FinanceApp with a value of 1.

Sample Amazon Web Services dynamic attributes filter that finds a tag FinanceApp with a value of 1