: Configure an IP Tag Cloud Connection
Focus
Focus

Configure an IP Tag Cloud Connection

Table of Contents

Configure an IP Tag Cloud Connection

Learn how to configure the Cloud Identity Engine to collect IP-Tags for policy enforcement.
An IP-Tag Cloud Connection allows the Cloud Identity Engine to collect IP address-to-tag information from cloud service providers. To enforce a tag-based security policy that adapts to IP address changes, configure Dynamic Address Groups using the IP address-to-tag information.
To configure the Cloud Identity Engine to collect IP address-to-tag (also known as IP-tag) information for policy enforcement, configure a connection to your cloud service provider to synchronize the mappings. The identity management system provides the IP-tag information to the Cloud Identity Engine for processing, which then provides the information to the firewalls for policy enforcement.
To collect IP-tag information from your cloud service provider, you must grant the Cloud Identity Engine the required permissions.
  • Azure — Grant the read permissions as described in the Azure Monitoring section in the VM Series documentation to the service account.
  • Amazon Web Services (AWS) — Grant the service account the Amazon Role Name (ARN) roles as described in the IAM Roles and Permissions for Panorama section as shown in the JSON example in the VM Series documentation. For more information on the ARN, refer to the AWS documentation.
  • Google Cloud Platform (GCP) — Grant the IAM roles as described in the VM Series documentation to the service account.
If you use Strata Cloud Manager, you can view your IP-tag information using the unified interface and use it to create your tag-based security policy.
For each region, you can synchronize up to 60,000 IP-tag mappings from a cloud service in a monitoring configuration at one time. The Cloud Identity Engine sync only the new or modified mappings each time. You can view up to 32,000 IP-tag mappings per page.
You can also view all IP-tag information in the Cloud Identity Engine (User ContextMappings and tags).
  1. If you have not already done so, activate User Context and use the default segment or configure a new segment to receive the mapping information.
  2. Select User ContextIP-Tag Collection.
  3. Select the Credential Configuration tab (if it does not already display).
  4. To Set Up a New Credential Configuration, select the cloud service provider you want to use.
    • AWS—Connect to an Amazon Web Services (AWS) instance.
    • Azure—Connect to a Microsoft Azure Active Directory instance.
    • Google Cloud Platform—Connect to a Google Cloud Platform (GCP) instance.
  5. Enter a unique and descriptive Name for the configuration.
  6. (AWS only) Configure your AWS connection.
    To open your AWS administrator portal in a new window so you can create or edit any necessary ARNs, select the type of Cloud Formation Template (CFT) you want to configure and log in with your AWS credentials.
    • Open CFT (Application Account Prerequisites)—Configure the Application Account prerequisites.
    • Open CFT (Security Account Prerequisites)—Configure the Application Account prerequisites.
    To enable monitoring using the current account, you only need to configure the application account prerequisites. If you want to use a different account, such as a service account or a cross-account role, to collect the data, you must configure the application account prerequisites, the security account prerequisites, and a role ARN for the account. For more information, refer to the Amazon documentation.
    1. Enter your Access Key ID.
      To learn how to obtain your access key ID and secret access key, refer to the AWS documentation.
    2. Enter your Secret Access Key.
    3. Reenter your secret access key to Confirm Secret Access Key.
    4. (Optional) Enter a Role ARN Name and Role ARN Value.
      To configure additional Role ARNs, click Add Role ARN for each Role ARN you want to include.
  7. (Azure only) Configure your Azure connection.
    1. Enter your Client ID.
      To learn how to obtain the client ID and client secret, refer to the Azure documentation.
    2. Enter your Client Secret.
    3. Enter your Tenant ID.
      To learn how to obtain the tenant ID and subscription ID, refer to the Azure documentation.
    4. Enter your Subscription ID.
  8. (Google Cloud Platform only) Configure your GCP connection.
    1. Create credentials for a service account in your Google Cloud console, then download and save the JSON file in a safe location.
    2. Click Browse files and click Open to navigate to the JSON file or drag and drop the GCP credential JSON file.
    3. (Optional) Select the Region for the instance.
      You can optionally Search for a region. If you don't select a region, the Cloud Identity Engine uses the us-west-2 region. You can select one region per instance.
  9. Verify the connection by clicking the Test Connection button.
    (AWS only) You can optionally select the Region before testing the connection. By default, the Cloud Identity Engine selects the US West region; if this region does not allow API requests, select a region that can allow API requests.
    Even if the connection test isn't successful, you can still submit your configuration; until you resolve the connectivity issues, the configuration status is Not connected. You must resolve the connection issues for the configuration to successfully retrieve the IP address-to-tag mappings.
  10. Submit the configuration.
    To collect and view your IP-Tag mappings, you must configure a IP-Tag monitor configuration.
  11. (Strata Cloud Manager only) If you're using Strata Cloud Manager, view the tags that the Cloud Identity Engine shares with Strata Cloud Manager by selecting an address group then select the Tags from CIE tab when you add match criteria.
  12. To configure a connection to your cloud service provider for monitoring purposes (such as audits) or to share the IP address-to-tag mapping information using a segment, select the Monitor & Status tab.
    There are four states for the connection to the cloud service provider:
    • Connected—The Cloud Identity Engine has successfully established a connection with the cloud service provider and can collect IP-tag mapping information.
    • Partially connected—The Cloud Identity Engine could successfully establish a connection to some aspects of the configuration, such as the region for AWS, but not all of them. The Cloud Identity Engine receives IP-tag mappings from connected sources; it does not receive them from unconnected sources.
    • Connection pending—The Cloud Identity Engine has successfully established a connection but has not completed the sync for the IP tag mappings from one or more regions.
      For more information on the connection status, select Click to see details.
    • Not connected—The Cloud Identity Engine couldn’t successfully establish a connection with cloud service provider using the current configuration.
    1. Set Up a New Monitor Configuration and select the monitor configuration for the cloud service provider that you configured for credential configuration in step 4.
    2. Enter a unique and descriptive Name for the configuration.
    3. Select the Credential Configuration that you configured in step 4.
    4. (AWS only) Optionally select the Role ARN you want to use.
    5. Select if you want to configure the connection for All Regions , All VPCs (AWS only) or All Project IDs (GCP only).
      To select a specific region or virtual private cloud (VPC), deselect the All Regions or All VPCs check box and allow the list of regions or VPCs to populate, then select the region or VPC you want to include. To select a specific VPC, you must first select one or more regions or select all regions.
    6. (Azure only) Select whether you want to Fetch Service Tags.
      Azure Service tags simplify security for Azure virtual machines and Azure virtual networks because you can restrict network access to just the Azure services you want to use. A service tag represents a group of IP address prefixes for a particular Azure service. For example, a tag can represent all storage IP addresses.
    7. Define the Polling Interval (in seconds) to specify how frequently the Cloud Identity Engine checks for new data.
      The default is 60 seconds and the range is 60–1800 seconds.
    8. If you want to share the mappings, select the segment you configured in step 1. Otherwise, if you want to create this configuration only for monitoring without sending mappings to any firewalls, select None.
      If you need to change the segment after you submit the configuration, you must create a new configuration and select the segment you want to use.
    9. Submit the configuration.
  13. Search and monitor your configurations in the Cloud Identity Engine.
    1. Select the Monitor & Status tab.
    2. Use the filters to highlight the information you want to find.
      • Name—Enter the name of a configuration to filter results to this configuration.
        The search query does not need to be an exact match for the name.
      • Vendor—Select the vendor type of the cloud service provider to filter the results to this vendor type.
      • Status— Select the status type (such as Connected or Partially Connected) to filter the results to this status type.
      • Segment— Select the Segment name to view the monitor segments that send mappings to the segment you select.
      • Associated Credential— Select the name of the Associated Credential configuration to view monitor segments that use the credential configuration type you select.
    3. (Optional) To remove the filter, click Reset.
  14. Manage your IP-Tag Collection configuration.
    1. (Optional) To sync all new IP-tag mappings and use them in the security policy immediately or to resolve any discrepancies in the IP-tag mappings, click Full Sync.
      The Sync Status displays the time and date of the last sync.
    2. (Optional) To change the IP-Tag Collection configuration, click Edit.
    3. (Optional) To remove the IP-Tag Collection configuration, click Delete and confirm the deletion.
      When you confirm the deletion, the Cloud Identity Engine removes all IP-tag mappings from the cloud service provider and from any firewalls that collect the IP-tag mappings to enforce security policy.
  15. View more details for a specific configuration.
    1. Select the name of the configuration that you want to view from the IP-Tag Collection page.
    2. On the Monitor & Status page, review the Connection Details to view information such as the connection status.
  16. View the IP address-to-tag mapping information.
    Options vary depending on your configuration type.
    1. (AWS only) On the VPC tab, Search by VPC ID to view information for a specific VPC or select the number in the IPs column to view the IP addresses associated with the VPC ID in that row.
    2. Select the Tag To IP tab and Search by Tag to view all IP addresses that contain the tag you specify.
      You can view the results for an exact or partial match for your query. You can optionally limit the search to a specific region or select All Regions.
    3. Select the number in the IPs column to view the IP addresses that the Cloud Identity Engine has collected for the selected Tag.
    4. Search by IP Address then close the window or click Cancel after reviewing the IP addresses.
    5. Select the IP To Tag tab to Search by IP Address.
      For an AWS-based configuration, you can also search by VPC ID.
    6. Click the number in the Tags column to view the tags associated with the IP Address of that row.
    7. Search by Tag then close the window or click Cancel after reviewing the tags.