Cisco Secure Access Documentation Changes

PDF

Cisco Secure Access Documentation Changes

Cisco Secure Access Documentation Changes 2026-10-26

Updated: November 2, 2026

Want to summarize with AI?

Log in

Lists changes to Cisco Secure Access documentation published on October 26, 2026.

Summary

Changed Pages

About this content

https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp.html

  • Removed: Network Connectivity Log

  • Removed: Provides an overview of Network Connectivity Log in Cisco Secure Access, including Network Connectivity Log.

  • Removed: It outlines the concepts, configuration tasks, and operational guidance presented in this chapter.

  • Added: Network Connectivity Monitoring

  • Added: Provides an overview of network connectivity monitoring in Cisco Secure Access, including how to use network tunnel logs and resource connector logs to track infrastructure health, monitor state changes, and troubleshoot connectivity issues.

Security Insights Dashboard

https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/dashboards-overview-intro/security-insights-dashboard.html

  • Added: Failed Private Resource Access Attempts — Detect when an end user makes an unusually high number of failed attempts to access private resources through client-based ZTNA.

Manage Behaviour Analytics Configuration

https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/advanced-user-config-intro/manage_behaviour_analytics_configuration.html

  • Added: Note Changes to UEBA configurations appear in the Admin Audit Log.

  • Added: Entries identify UEBA as the feature and the anomaly type as the component.

  • Added: Update entries show the changed property and its previous and new values.

  • Added: For more information, see Admin Audit Log Report.

  • Removed: User activity from a city or source IP address that was not observed for that user during the previous 30 days.

  • Added: User activity from a city or source IP address that is not in that user’s rolling 60-day location history.

  • Added: Note The system starts to generate alerts only after seven days of configuration.

  • Added: Failed Private Resource Access Attempts

  • Added: An unusually high number of failed attempts to access private resources.

  • Added: An AI-based user baseline and a configured minimum number of failed attempts per hour.

  • Added: The following table lists the traffic types that each UEBA component analyzes.

  • Added: Traffic type

  • Added: UEBA components

  • Added: Secure Web Gateway (SWG) web traffic

  • Added: File Operations; High-Risk Country File Activities; Impossible Travel; Anomalous MCP Activity; Unseen Location Activity; Traffic Spike and Destination Monitoring

  • Added: DLP events

  • Added: DLP Violation Spike

  • Added: Client-based ZTNA traffic

  • Added: Failed Private Resource Access Attempts

  • Added: AD user; web traffic, ZTNA (client-based)

  • Removed: Select the required file activities from the following optons:

  • Added: Select the required file activities from the following options:

  • Removed: UEBA supports only Secure Internet Access traffic paths and does not support Secure Private Access.

  • Removed: AD user; web traffic only

  • Added: Configure Analytics for Failed Private Resource Access Attempts

  • Added: Failed Private Resource Access Attempts identifies an unusually high number of failed attempts to access private resources.

  • Added: It analyzes client-based Zero Trust Network Access (ZTNA) traffic only.

  • Added: Your organization must use client-based ZTNA to use this analytics.

  • Added: Secure Access generates alerts for authentication failures and access-policy rule denials.

  • Added: It does not generate alerts for DNS resolution, profile configuration, device posture, or protocol mismatch failures.

  • Added: The analytics uses an AI-based user baseline.

  • Added: Secure Access generates an alert when activity is anomalous for the user and meets the configured minimum threshold.

  • Added: To configure Failed Private Resource Access Attempts, perform these steps:

  • Added: Before you begin

  • Added: Procedure

  • Added: Navigate to Connect> Users, Groups, and Endpoint Devices> Configuration management> Behaviour analytics.

  • Added: On the Failed Private Resource Access Attempts tile, click Edit.

  • Added: Click the Status toggle to enable it.

  • Added: Enter a value in Alert threshold.

  • Added: Note The alert threshold acts as a minimum activity level for generating an alert.

  • Added: If activity is anomalous but stays below the threshold, no alert is generated.

  • Added: Note The alert threshold value is optional and can be any number between 0 and 10,000.

  • Added: Click Save.

  • Added: Note Secure Access can take up to seven days after you enable this analytics to generate the first alert.

  • Added: It suppresses repeated alerts for the same user for 60 minutes.

  • Added: What to do next

  • Added: To receive notifications, create a behavior analytics alert rule for Failed Private Resource Access Attempts.

  • Added: To know more, see Add and Edit Alert Rules for Behavior Analytics

Manage the Access Policy

https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/access-policies-intro/manage-access-policy.html

  • Removed: For users implementing Kerberos authentication with AD, we recommend reviewing the appropriate Microsoft documentation about configuring the correct ports and private resources to plan for for AD communication. to understand how to optimize the location of a domain controller, see this documentation.

  • Added: For users implementing Kerberos authentication with AD, we recommend reviewing the appropriate Microsoft documentation about configuring the correct ports and private resources to plan for for AD communication.

  • Added: To understand how to optimize the location of a domain controller, see this documentation.

Rule Defaults: Default Settings for Access Rules

https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/access-policies-intro/rule_defaults_default_settings_for_access_rules.html

  • Added: Configure Access Rule Editing Sessions

  • Added: Use the editing-session settings to control how long an administrator can lock and edit an access rule, and to determine whether they can extend the active session.

  • Added: Before you begin

  • Added: You must have the Full Admin user role to configure rule defaults and global settings.

  • Added: For more information, see Manage Accounts.

  • Added: Procedure

  • Added: In the global settings panel, locate the Editing sessions.

  • Added: In the Session duration section, enter the number of minutes that an access rule remains locked for an editing session before it expires.

  • Added: To allow administrators to extend a session, enable the Extend session toggle button, and then enter the number of minutes to add under minutes added per extension.

  • Added: Note You can extend an editing session only once.

  • Added: The maximum extension duration is 40 minutes.

  • Added: Click Save.

  • Added: While editing a rule, the Internet Access Rule and Private Access Rule page both shows the remaining time at the top and bottom.

  • Added: Click Extend session before the time expires to extend the session.

  • Added: If another admin opens the rule during an active session, Secure Access displays a dashboard notification and opens the rule in preview mode.

  • Added: To take over editing, click Take Over Editing, and then click Yes, take over.

  • Added: This action ends the current administrator's session and discards any unsaved changes.

Add an Internet Access Rule

https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/internet-access-rules-intro/add_an_internet_access_rule.html

  • Removed: Navigate to a rule, and then click on the horizontal elipsis (...) to expand the rule menu.

  • Added: Navigate to a rule, and then click on the horizontal ellipsis (...) to expand the rule menu.

Manage Destination Lists

https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/internet-saas-resource-intro/manage_destination_lists.html

  • Removed: Added a URL to an allow list.

  • Removed: URLs in allow lists are not currently supported.

  • Removed: Consider adding the domain only instead.

  • Removed: Remove the URL and replace it with the domain for that URL.

Traffic Steering for Zero Trust Access Client-Based Connections

https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/zero-trust-access-intro/traffic_steering_for_zero_trust_access_client-based_connections.html

  • Removed: dentity workflows that depend on Kerberos service discovery while working remotely through ZTA after sign-in.

  • Added: Identity workflows that depend on Kerberos service discovery while working remotely through ZTA after sign-in.

  • Removed: You can configure a ZTA profile to either permenantly or temporarily pause ZTA enforcement and still utlize the traffic steering configured for a specific profile with the Enable Cisco Secure Client end user pause function.

  • Added: You can configure a ZTA profile to either permanently or temporarily pause ZTA enforcement and still utilize the traffic steering configured for a specific profile with the Enable Cisco Secure Client end user pause function.

  • Removed: Note You can enable the pause functionality for both Secure Private Access and Secure Internet Access indepently of each other; both of these configruable settings are available in their repsective steps when editing or creating a profile.

  • Added: Note You can enable the pause functionality for both Secure Private Access and Secure Internet Access independently of each other; both of these configurable settings are available in their respective steps when editing or creating a profile.

  • Removed: Check the About icon inside your Cisco Secure Client module to view the Secure Client UI verison.

  • Added: Check the About icon inside your Cisco Secure Client module to view the Secure Client UI version.

  • Removed: Microsoft documents specific SRV DNS records for you, see 6.3.2.3 SRV Records sepcifically for more information.

  • Added: Microsoft documents specific SRV DNS records for you, see 6.3.2.3 SRV Records specifically for more information.

  • Removed: For users implementing Kerberos authentication with AD, we recommend reviewing the appropriate Microsoft documentation about configuring the correct ports and private resources to plan for for AD communication. to understand how to optimize the location of a domain controller, see this documentation.

  • Added: For users implementing Kerberos authentication with AD, we recommend reviewing the appropriate Microsoft documentation about configuring the correct ports and private resources to plan for for AD communication.

  • Added: To understand how to optimize the location of a domain controller, see this documentation.

Get Started with Virtual Appliances

https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/virtual-appliances-intro/get_started_with_virtual_appliances.html

  • Removed: Encryption is established with a probe sent on port 53 (UDP/TCP) to 208.67.220.220 and 208.67.222.222 and if you have a firewall or IPS/IDS doing deep packet inspection and expecting to see only DNS traffic, the probe may fail.

  • Added: Encryption is established with a probe sent on port 53 (UDP/TCP) to the following addresses:

  • Added: IPv4: 18.252.251.72 and 18.254.118.193

  • Added: IPv6: 2600:1f15:ef3:1800::aaaa and 2600:1f15:ef3:1801::bbbb

  • Added: If you have a firewall or IPS/IDS doing deep packet inspection and expecting to see only DNS traffic, the probe may fail.

  • Removed: The VA, when deployed, will forward all externally-bound DNS requests to the Secure Access DNS resolvers, 208.67.222.222 and 208.67.220.220.

  • Added: The VA, when deployed, will forward all externally-bound DNS requests to the Secure Access DNS resolvers, 18.252.251.72 and 18.254.118.193 or 2600:1f15:ef3:1800::aaaa and 2600:1f15:ef3:1801::bbbb.

Configure Virtual Appliances

https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/virtual-appliances-intro/configure_virtual_appliances.html

  • Removed: Your password must be at least eight characters long, include at least one lowercase character, one uppercase character, one digit, and one special character.

  • Added: Your password must be at least 15 characters long, include at least one lowercase character, one uppercase character, one digit, and one special character.

  • Removed: For example, if your Org ID is 2406960, the default password for the VA would be Umbrella2406960.

  • Added: For example, if your Org ID is 2406960, the default password for the VA would be Umbrella2406960!.

  • Removed: Configuring an IPv6 address is optional and will not overwrite the IPv4 address configuration.

  • Added: Configuring an IPv6 address is optional and does not replace the IPv4 configuration.

  • Added: In addition to static IPv6 configuration, the VA supports dynamic IPv6 addressing through DHCPv6 or Stateless Address Autoconfiguration (SLAAC) when the network provides the required service or router advertisements.

  • Added: Configure NAT64 Prefixes

  • Added: You can configure NAT64 prefixes on the VA.

  • Added: The prefix must be a valid IPv6 CIDR prefix with host bits set to zero.

  • Added: config va nat64prefixes add 64:ff9b::/96

  • Added: config va nat64prefixes remove 64:ff9b::/96

  • Added: config va nat64prefixes show

  • Added: The VA supports up to eight configured NAT64 prefixes

  • Added: You can configure NTP servers by using IPv4 or IPv6 addresses.

  • Added: Use either IPv4 or IPv6, not both.

  • Added: config ntp add 2001:db8::123

  • Added: config ntp remove 2001:db8::123

  • Added: config ntp show

  • Added: NTP over TLS also supports IPv6 server addresses:

  • Added: config ntp tls add 2001:db8::123

  • Added: config ntp tls remove 2001:db8::123

  • Added: config ntp tls enable config ntp tls disable

  • Added: config ntp tls ca <certificate>

  • Added: You can configure NTP servers by using IPv4 or IPv6 addresses.

  • Added: Use either IPv4 or IPv6, not both.

  • Added: When you configure an IPv6 log export destination, enclose the IPv6 address in square brackets before specifying the port.

  • Added: config logexport destination [2001:db8::50]:514 udp

  • Added: config logexport destination [2001:db8::50]:514 tcp

  • Added: config logexport destination [2001:db8::50]:6514 tls

  • Added: For DMZ deployment, configure two interfaces on the VA before you enable DMZ mode.

  • Added: To enable DMZ mode, enter

  • Added: config va dmz

  • Added: enable

  • Added: .

  • Added: To disable DMZ mode, enter

  • Added: config va dmz

  • Added: disable

  • Added: .

  • Added: To check the current DMZ mode, enter

  • Added: config va

  • Added: show

  • Added: .

Local DNS Forwarding

https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/virtual-appliances-intro/local_dns_forwarding.html

  • Added: Example:

  • Added: config localdns add 2001:db8:300::53 corp.example.com

  • Added: You can configure IPv4 or IPv6 local DNS servers.

  • Added: The VA must have an IPv6 address configured before you add an IPv6 local DNS target.

Add a SaaS API Rule to the Data Loss Prevention Policy

https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/data-loss-prevention-intro/add-a-saas-api-rule.html

  • Removed: Note: When you select Confluence or Jira, each of the tenants you have established for that platform will appear; you must choose one.

  • Added: When you select Confluence or Jira, each of the tenants you have established for that platform will appear; you must choose one.

  • Removed: The Resource Labels area appears only if you have selected AWS or Azure for Platform.

  • Added: The Resource Labels area appears only if you have selected AWS, or Azure for Platform.

Monitor Secure Access with Alert Rules

https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/monitor-alert-rules-intro/monitor_secure_access_with_alert_rules.html

  • Added: Add and Edit Alert Rules for Resource Connectors

  • Added: Manage Alert Rules for Destination Lists

  • Added: Failed Private Resource Access Attempts

  • Removed: However, for Behavior analytics alert rules, Secure Access generates alerts only for the first alert rule created for each alert type.

  • Added: However, for Behavior analytics alert rules, Secure Access generates only 25 alerts in an hour for the first alert rule created for each alert type.

  • Added: Failed Private Resource Access Attempts — Alert when an end user makes an unusually high number of failed attempts to access private resources through client-based ZTNA.

  • Added: Add and Edit Alert Rules for Resource Connectors

  • Added: Secure Access checks the status of resource connectors and resource connector groups at regular intervals.

  • Added: When a resource connector is disconnected or an issue meets alert conditions, Secure Access delays raising the alert for 10 minutes.

  • Added: If alert conditions are still met after 10 minutes, Secure Access raises the alert.

  • Added: This delay avoids unnecessary alerts caused by transient network disruptions and connector flapping.

  • Added: Note When you edit an alert rule, Secure Access dismisses any active alerts for that rule.

  • Added: After you add an alert rule, Secure Access begins to monitor the conditions defined for the alert.

  • Added: You can view the alerts generated by Secure Access for the Behavior analytics alert rules in the organization.

  • Added: In Secure Access, navigate to the toolbar at the top of your browser window.

  • Added: Click the bell icon to open the Alerts drop-down menu.

  • Added: Secure Access displays the alerts generated for the configured alert rules.

  • Added: For information about viewing alerts in Secure Access, see Monitor Alerts From Secure Access.

  • Added: Before you begin

  • Added: Before creating or editing alert rules for Resource Connectors, ensure you meet the following requirements:

  • Added: You must have Full Administrator role in Cisco Secure Access.

  • Added: For more information, see Manage Accounts.

  • Added: At least one resource connector group and active resource connector must be deployed in your organization.

  • Added: Valid email addresses or distribution lists must be identified for alert notifications.

  • Added: Procedure

  • Added: In the Cisco Secure Access navigation menu, navigate to Monitor> Alert Rules.

  • Added: Choose one of the following actions to open the alert rule wizard:

  • Added: To create a new alert rule, click Add Rule.

  • Added: To update an existing alert rule, locate the rule in the table, click More Options (...), and select Edit.

  • Added: In the General Settings tab, specify the rule identity and severity:

  • Added: In the Alert rule name field, enter a unique, descriptive name for the alert rule.

  • Added: From the Category drop-down list, select Resource Connector.

  • Added: From the Alert type drop-down list, select the condition you want to monitor.

  • Added: Table 1.

  • Added: Resource Connector Alert Types

  • Added: Alert Type

  • Added: Trigger Condition

  • Added: Resource connector software updates

  • Added: Resource connector update started

  • Added: Alert on an over-the-air (OTA) software update beginning on a resource connector during its scheduled maintenance window.

  • Added: Resource connector update succeeded

  • Added: Alert on a software update completing successfully and the resource connector restarting with the updated software image.

  • Added: Resource connector update failed

  • Added: Alert on a resource connector software update failure, requiring verification of outbound firewall access to Cisco update repositories.

  • Added: Resource connector certificate & security

  • Added: Resource connector certificate renewal failed

  • Added: Alert on the failure of automatic TLS client certificate renewal between the resource connector and Cisco cloud services.

  • Added: Resource connector certificate expiring soon

  • Added: Alert on a resource connector TLS client certificate approaching expiration within 10 days.

  • Added: Resource connector certificate expired

  • Added: Alert on a resource connector TLS client certificate expiring, resulting in tunnel authentication termination.

  • Added: Resource connector software vulnerability detected

  • Added: Alert on a security vulnerability detected in the running resource connector software package.

  • Added: Resource connector host OS vulnerability detected

  • Added: Alert on a security vulnerability detected in the underlying host operating system of the resource connector.

  • Added: Resource connector connectivity & sync

  • Added: Resource connector tunnel disconnected

  • Added: Alert on a resource connector tunnel remaining disconnected for 10 or more consecutive minutes.

  • Added: Resource connector tunnel reconnected

  • Added: Alert on a previously disconnected resource connector tunnel successfully restoring connection to Cisco Secure Access.

  • Added: Resource connector configuration out of sync

  • Added: Alert on the local configuration metadata on a resource connector failing to match cloud tenant records.

  • Added: Resource connector end-of-support

  • Added: Resource connector software image end of support

  • Added: Alert on a running resource connector software image reaching End-of-Support (EoS).

  • Added: Resource connector host OS end of support

  • Added: Alert on the underlying host operating system of a resource connector reaching End-of-Support (EoS).

  • Added: Resource connector group connectivity

  • Added: Resource connector group disconnected

  • Added: Alert on all resource connectors within a connector group disconnecting simultaneously, interrupting ZTNA access to associated private resources.

  • Added: Resource connector group partially reconnected

  • Added: Alert on at least one resource connector reconnecting in a previously offline group, indicating degraded operational capacity.

  • Added: Resource connector group performance

  • Added: Resource connector group overloaded

  • Added: Alert on active connection load or bandwidth throughput exceeding capacity thresholds for a resource connector group.

  • Added: Configure rule severity and description:

  • Added: From the Severity level drop-down list, select the severity level: High, Medium, Low, or Info.

  • Added: (Optional) In the Description field, enter or edit the remediation description (maximum 150 characters).

  • Added: Click Next.

  • Added: In the Alert Conditions tab, specify the trigger scope for the alert rule:

  • Added: Choose one of the following trigger options:

  • Added: Trigger notifications for all regions and connector groups: To trigger alerts for every region and connector group.

  • Added: Trigger only for selected regions and connector groups: To limit the alert rule to targeted regions and/or connector groups.

  • Added: Select the Regions affected check box, and then from the Select regions drop-down list, choose one or more cloud regions.

  • Added: Select the Connector groups affected check box, and then from the Select connector groups drop-down list, choose one or more resource connector groups.

  • Added: Click Next.

  • Added: In the Notifications tab, enable the notifications for the alert rule.

  • Added: You can enable Webhook notifications and Email notifications

  • Added: Secure Access always enables in-product notifications.

  • Added: For more information about in-product notifications, see Monitor Alerts from Secure Access.

  • Added: Choose Web notifications to configure push notifications to a third-party product or service.

  • Added: You can choose from a list of configured webhooks or add a new webhook.

  • Added: Click on the Select a webhook drop-down menu and then choose a webhook from the list of configured webhooks.

  • Added: Click + Configure a new webhook.

  • Added: After you complete the configuration of the new webhook, click Save.

  • Added: Complete the configuration of the webhook and add the webhook in the organization.

  • Added: You can add at most 10 webhooks.

  • Added: For information about webhooks, see Manage Webhooks for Third-Party Integrations.

  • Added: Click Email notifications to configure notifications to a list of email recipients.

  • Added: You can configure and send a test notification to the list of email recipients.

  • Added: Add a comma-separated list of email addresses.

  • Added: Note

  • Added: You are limited to 50 email addresses.

  • Added: (Optional) Enter an email address, and then click Send.

  • Added: Secure Access sends a test alert to evaluate that the email address receives the alert.

  • Added: In the Summary tab, review the configured general settings, alert conditions, and notifications, then click Save.

  • Added: The alert rule is saved and listed in the Alert Rules table.

  • Added: Cisco Secure Access continuously evaluates connector status against the configured conditions and delivers notifications when matching events occur.

  • Added: What to do next

  • Added: After configuring alert rules, you can:

  • Added: Filter active and dismissed alerts in the notification drawer.

  • Added: For more information, see Monitor Alerts From Secure Access.

  • Added: Click Dismiss on an alert card to clear acknowledged notifications.

  • Added: For more information, see Monitor Alerts From Secure Access.

  • Added: Toggle the rule status to Disable in the Alert Rules table to suspend notifications without deleting the rule configuration.

  • Added: For more information, see Manage Alert Rules.

Report Scheduling

https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/monitor-with-reports-intro/schedule-reports.html

  • Removed: Network Connectivity Log —Lists events for each tunnel within your Network Tunnel Groups.

  • Removed: This log provides key details to help you troubleshoot connectivity issues, monitor tunnel activity, and confirm that traffic is securely transmitted between devices and Secure Access.

  • Added: Network Connectivity Monitoring —Lists events for network tunnel groups and resource connectors to help you monitor connectivity, track state changes, and troubleshoot issues to ensure that traffic is securely transmitted between your environment and Secure Access.

Activity Search Report

https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/activity-reports-intro/activity-search-report.html

  • Added: When a DNS event is evaluated and resolved by underlying platform security settings rather than a user-defined policy rule, Secure Access displays one of the following system-generated descriptions:

  • Added: Block due to security setting (0): Access was blocked by a DNS security policy rather than an explicit access rule.

  • Added: Allow with domain on global allow list (9223372036854775807): Access was allowed because the requested domain is explicitly permitted on your Global Allow List.

  • Added: No action with default rule not defined (9223372036854775806): No action occurs because the traffic does not match any user-defined rule and a default catch-all rule does not exist.

  • Added: Error due to invalid policy (9223372036854775805): An error occurred during evaluation due to an invalid policy configuration.

  • Added: Note System-generated policy names appear as plain text in the report and do not contain a clickable link to the Access Policy page.

  • Added: Note: System-generated DNS rules (such as Block due to security setting (0)) are triggered by global security settings rather than user-defined rules.

  • Added: These specific activity records do not contain a link to the Access Policy page.

Admin Audit Log Report

https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/admin-audit-log-intro/admin_audit_log_report.html

  • Removed: Policies, Identities, or Block Pages that were Changed

  • Added: Policies, Identities, Block Pages, or User and Entity Behavior Analytics (UEBA) Configurations that were Updated

Network Connectivity Monitoring

https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/network-connectivity-log-intro.html

  • Removed: Network Connectivity Log

  • Removed: Provides an overview of Network Connectivity Log in Cisco Secure Access, including Network Connectivity Log.

  • Removed: It outlines the concepts, configuration tasks, and operational guidance presented in this chapter.

  • Removed: Network Connectivity Log

  • Removed: Use this procedure to view, search, and export Network Connectivity Log entries for detailed visibility into network tunnel activity and connectivity issues.

  • Added: Network Connectivity Monitoring

  • Added: Provides an overview of network connectivity monitoring in Cisco Secure Access, including how to use network tunnel logs and resource connector logs to track infrastructure health, monitor state changes, and troubleshoot connectivity issues.

  • Added: Network Connectivity Monitoring

  • Added: This topic provides an overview of network connectivity monitoring, including how to use network tunnel logs and resource connector logs to ensure secure traffic transmission.

Added Pages

Removed Pages