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 Secure Firewall Management Center.
We support the following:
|
CSDAC version/platform |
AWS |
AWS security groups |
AWS service tags |
Azure |
Azure Service Tags |
Cisco Cyber Vision |
Cisco Multicloud Defense |
Generic text |
GitHub |
Google Cloud |
Microsoft Office 365 |
vCenter |
Webex |
Zoom |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Version 1.1 (on-premises) |
Yes |
No |
No |
Yes |
Yes |
No |
No |
No |
No |
No |
Yes |
Yes |
No |
No |
|
Version 2.0 (on-premises) |
Yes |
No |
No |
Yes |
Yes |
No |
No |
No |
No |
Yes |
Yes |
Yes |
No |
No |
|
Version 2.2 (on-premises) |
Yes |
No |
No |
Yes |
Yes |
No |
No |
No |
Yes |
Yes |
Yes |
Yes |
No |
No |
|
Version 2.3 (on-premises) |
Yes |
No |
No |
Yes |
Yes |
No |
No |
No |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Version 3.0 (on-premises) |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
CSDAC version/platform |
AWS |
AWS security groups |
AWS service tags |
Azure |
Azure Service Tags |
Cisco APIC |
Cisco Cyber Vision |
Generic Text |
GitHub |
Google Cloud |
Microsoft Office 365 |
vCenter |
Webex |
Zoom |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Version 1.1 (on-premises) |
Yes |
No |
No |
Yes |
Yes |
No |
No |
No |
No |
No |
Yes |
Yes |
No |
No |
|
Version 2.0 (on-premises) |
Yes |
No |
No |
Yes |
Yes |
No |
No |
No |
No |
Yes |
Yes |
Yes |
No |
No |
|
Version 2.2 (on-premises) |
Yes |
No |
No |
Yes |
Yes |
No |
No |
No |
Yes |
Yes |
Yes |
Yes |
No |
No |
|
Version 2.3 (on-premises) |
Yes |
No |
No |
Yes |
Yes |
No |
No |
No |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Version 3.0 (on-premises) |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
See one of the following sections for more information.
-
Amazon Web Services (AWS)
For more information, see a resource like Tagging AWS resources on the Amazon documentation site.
See Amazon Web Services Connector—About User Permissions and Imported Data.
-
Amazon Web Services security groups.
For more information, see a resource like Work with security groups.
See Amazon Web Services Security Groups Connector—About User Permissions and Imported Data.
-
Amazon Web Services service tags.
For more information, see a resource like What are tags?.
-
Microsoft Azure
For more information, see this page on the Azure documentation site.
See Azure Connector—About User Permissions and Imported Data.
-
Microsoft Azure service tags
For more information, see a resource like Virtual network service tags on Microsoft TechNet.
-
Cisco Cyber Vision
-
Generic text list of IP addresses you specify
For more information, see Create a Generic Text Connector.
-
GitHub
For more information, see Create a GitHub Connector.
-
Google Cloud
For more information, see Setting Up Your Environment in the Google Cloud documentation.
See Google Cloud Connector—About User Permissions and Imported Data.
-
Office 365 IP addresses
For more information, see Office 365 URLs and IP address ranges on docs.microsoft.com.
-
VMware categories and tags managed by vCenter and NSX-T
For more information, see a resource like vSphere Tags and Attributes in the VMware documentation site.
-
Webex IP addresses
For more information, see Create a Webex Connector.
-
Zoom IP addresses
For more information, see Create a Zoom Connector.
Amazon Web Services Connector—About User Permissions and Imported Data
The Cisco Secure Dynamic Attributes Connector imports dynamic attributes from AWS to Secure Firewall 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 documentation
-
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, ec2:DescribeVpcs, 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 Secure Firewall 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 . |
||
|
Step 3 |
Click . |
||
|
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.
|
||
|
Step 11 |
Click Close. |
||
|
Step 12 |
At the Identity and Access Management (IAM) page in the left column, click . |
||
|
Step 13 |
Click Create Policy. |
||
|
Step 14 |
On the Create Policy page, click JSON.
|
||
|
Step 15 |
Enter the following policy in the field:
|
||
|
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 . |
||
|
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
This task discusses how to configure a connector that sends data from AWS to the Secure Firewall Management Center for use in access control policies.
Before you begin
Procedure
|
Step 1 |
Log in to the dynamic attributes connector. |
||||||||||||||
|
Step 2 |
Click Connectors. |
||||||||||||||
|
Step 3 |
Do any of the following:
|
||||||||||||||
|
Step 4 |
Enter the following information.
|
||||||||||||||
|
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. |
Amazon Web Services Security Groups Connector—About User Permissions and Imported Data
The Cisco Secure Dynamic Attributes Connector imports dynamic attributes from AWS to Secure Firewall Management Center for use in access control policies.
Minimum permissions required
The Cisco Secure
Dynamic Attributes Connector requires a user at minimum with a policy that permits ec2:DescribeTags, ec2:DescribeVpcs, 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 Secure Firewall 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 . |
||
|
Step 3 |
Click . |
||
|
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.
|
||
|
Step 11 |
Click Close. |
||
|
Step 12 |
At the Identity and Access Management (IAM) page in the left column, click . |
||
|
Step 13 |
Click Create Policy. |
||
|
Step 14 |
On the Create Policy page, click JSON.
|
||
|
Step 15 |
Enter the following policy in the field:
|
||
|
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 . |
||
|
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 Security Groups Connector
This task discusses how to configure a connector that sends AWS security groups data to the Secure Firewall Management Center for use in access control policies.
Before you begin
-
Create AWS security groups as discussed in Work with security groups on the AWS documentation site.
-
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:
|
||||||||||||||
|
Step 4 |
Enter the following information.
|
||||||||||||||
|
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. |
Create an AWS Service Tags Connector
This topic discusses how to create a connector for Amazon Web Services (AWS) service tags to the Secure Firewall Management Center for use in access control policies.
For more information, see resources like the following on the AWS documentation site:
Procedure
|
Step 1 |
Log in to the dynamic attributes connector. |
||||||||
|
Step 2 |
Click Connectors. |
||||||||
|
Step 3 |
Do any of the following:
|
||||||||
|
Step 4 |
Enter the following information.
|
||||||||
|
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. |
Azure Connector—About User Permissions and Imported Data
The Cisco Secure Dynamic Attributes Connector imports dynamic attributes from Azure to Secure Firewall 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 Secure Firewall 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 . |
|
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.
|
|
Step 9 |
Next to Client Credentials, 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 value of the Value field to the clipboard. This value, and not the Secret ID, is the client secret.
|
|
Step 13 |
Go back to the main Azure Portal page and click Subscriptions. |
|
Step 14 |
Click the name of your subscription. |
|
Step 15 |
Copy the subscription ID to the clipboard.
|
|
Step 16 |
Click Access Control (IAM). |
|
Step 17 |
Click . |
|
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.
|
|
Step 21 |
Click Review + Assign and follow the prompts to complete the action. |
What to do next
Create an Azure Connector
This task discusses how to create a connector to send data from Azure to Secure Firewall Management Center for use in access control policies.
Before you begin
Procedure
|
Step 1 |
Log in to the dynamic attributes connector. |
||||||||||||||||
|
Step 2 |
Click Connectors. |
||||||||||||||||
|
Step 3 |
Do any of the following:
|
||||||||||||||||
|
Step 4 |
Enter the following information.
|
||||||||||||||||
|
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. |
Create an Azure Service Tags Connector
This topic discusses how to create a connector for Azure service tags to the Secure Firewall Management Center for use in access control policies. The IP addresses associated 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:
|
||||||||||||||||
|
Step 4 |
Enter the following information.
|
||||||||||||||||
|
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. |
Create a Cisco Cyber Vision Connector
This task discusses how to send data from Cisco Cyber Vision to the Secure Firewall Management Center .
Before you begin
Cisco Cyber Vision must be reachable from the machine on which the dynamic attributes connector is running. You must know its IP address, port, and API key.
To find the API key in the Cyber Vision management console, click , then click Show to display the token and
to copy the token to the clipboard.
Procedure
|
Step 1 |
Log in to the dynamic attributes connector. |
||||||||||||||||
|
Step 2 |
Click Connectors. |
||||||||||||||||
|
Step 3 |
Do any of the following:
|
||||||||||||||||
|
Step 4 |
Enter the following information.
|
||||||||||||||||
|
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. |
Create a Generic Text Connector
This task discusses how to create an ad hoc list of IP addresses you maintain manually and retrieve at an interval you select (30 seconds by default). You can update the list of addresses anytime you want.
Before you begin
Create text files with IP addresses and put it on a web server that is accessible from the Secure Firewall Management Center . IP addresses can include CIDR notation. The text file must have only one IP address per line.
For example, you might have a list of IP addresses for an "allow list" in access control rules and another list of IP addresses for a "block list" in access control rules.
You can specify up to 10,000 IP addresses per text file.
![]() Note |
Do not include a scheme (http:// or https://) in your IP addresses. |
Procedure
|
Step 1 |
Log in to the dynamic attributes connector. |
|
Step 2 |
Click Connectors. |
|
Step 3 |
Do any of the following:
|
|
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 the text file. The default is 30 seconds. The minimum value for Pull Interval is 1 second. You can set the maximum to any value you want. We recommend against setting the minimum to a low value because it can generate a lot of traffic, and, when applicable, can result in your being billed for the traffic. |
|
Step 6 |
In the URLs field, enter each URL from which to retrieve IP addresses, one URL per line. |
|
Step 7 |
(Optional.) Click Add another URL to add an additional URL to monitor. |
|
Step 8 |
(Optional.) If a certificate chain is required for a secure connection to the web server, you have the following options:
|
|
Step 9 |
Click Test and make sure the test succeeds before you save the connector. |
|
Step 10 |
Click Save. |
|
Step 11 |
Make sure Ok is displayed in the Status column. |
Create a GitHub Connector
This section discusses how to create a GitHub connector that sends data to the Secure Firewall Management Center for 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:
|
|
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. |
Google Cloud Connector—About User Permissions and Imported Data
The Cisco Secure Dynamic Attributes Connector imports dynamic attributes from Google Cloud to Secure Firewall 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 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 Secure Firewall 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 . |
|
Step 3 |
Enter the following information:
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 role. |
|
Step 7 |
Click Done. A list of service accounts is displayed. |
|
Step 8 |
Click More ( |
|
Step 9 |
Click Manage Keys. |
|
Step 10 |
Click .
|
|
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
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:
|
||||||||||||
|
Step 4 |
Enter the following information.
|
||||||||||||
|
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. |
Create an Office 365 Connector
This task discusses how to create a connector for Office 365 tags to send data to the Secure Firewall 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:
|
||||||||||||||
|
Step 4 |
Enter the following information.
|
||||||||||||||
|
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. |
vCenter Connector—About User Permissions and Imported Data
The Cisco Secure Dynamic Attributes Connector imports dynamic attributes from vCenter to Secure Firewall 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.
Create a vCenter 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 Secure Firewall Management Center . For a list of these attributes, see vCenter Connector—About User Permissions and Imported Data.
Before you begin
You must already have set up your vCenter Server account. For more information about doing that, see About vCenter Server Installation and Setup in the vCenter documentation.
Procedure
|
Step 1 |
Log into vCenter as an administrator. |
|
Step 2 |
Click . |
|
Step 3 |
In the left pane, click . |
|
Step 4 |
From the Domain list, click the name of a domain to add the user. |
|
Step 5 |
Click Add User. |
|
Step 6 |
Enter the requested information and click Add. |
|
Step 7 |
In the left pane, click . |
|
Step 8 |
Click Add( |
|
Step 9 |
From the User field, click the name of the vCenter domain in which you created the user. |
|
Step 10 |
In the search field, enter part of the user's name. |
|
Step 11 |
From the Role list, click Read-only. |
|
Step 12 |
Select the Propagate to children check box.
|
|
Step 13 |
Click OK. |
What to do next
Create a vCenter Connector
This task discusses how to create a connector for VMware vCenter to send data to the Secure Firewall 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:
|
||||||||||||||||||||||||
|
Step 4 |
Enter the following information.
Expanding the certificate CA chain at the top of the dialog box displays the certificates similar to the following.
If it's not possible to fetch the certificate this way, you can get the certificate chain manually as discussed in Manually Get a Certificate Authority (CA) Chain. |
||||||||||||||||||||||||
|
Step 5 |
Click Test and make sure Test connection succeeded is displayed before you save the connector. |
||||||||||||||||||||||||
|
Step 6 |
Click Save. |
Create a Webex Connector
This section discusses how to create a Webex connector that sends data to the Secure Firewall Management Center for use in access control policies. The IP addresses associated with these tags are maintained by Webex. You do not have to create a dynamic attributes filters.
For more information, see Port Reference for Webex Calling.
Procedure
|
Step 1 |
Log in to the dynamic attributes connector. |
||||||||||
|
Step 2 |
Click Connectors. |
||||||||||
|
Step 3 |
Do any of the following:
|
||||||||||
|
Step 4 |
Enter the following information.
|
||||||||||
|
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. |
Create a Zoom Connector
This section discusses how to create a Zoom connector that sends data to the Secure Firewall Management Center for use in access control policies. The IP addresses associated with these tags are maintained by Zoom. You do not have to create a dynamic attributes filters.
For more information, see Zoom network firewall or proxy server settings.
Procedure
|
Step 1 |
Log in to the dynamic attributes connector. |
||||||||||
|
Step 2 |
Click Connectors. |
||||||||||
|
Step 3 |
Do any of the following:
|
||||||||||
|
Step 4 |
Enter the following information.
|
||||||||||
|
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. |

)





).













Feedback