Protected assets, access relationships and threat scenarios establish priorities. Preventive controls, visibility and incident response are designed to reinforce each other. Technology choices account for team capacity, integration needs and organisational risk tolerance.
Bring access, visibility and response into the same scope
Security work starts with the applications and data the organisation needs to protect. Review identity, remote access, network boundaries and monitoring together. The SASE drawing below illustrates a connectivity approach; the separate AI Defense drawing addresses AI security. These references do not define one mandatory package for every organisation. Existing controls, workloads and risk priorities determine the necessary layers. Acceptance must cover denied flows and escalation to the responsible team as well as permitted access.
CISCO · Figure 7
Cisco Secure Access: active/standby redundancy
Select nodes to read their roles; zoom or enter full screen to follow the connections.
Drag to pan or use the buttons to zoom. Node descriptions appear on hover.
Primary tunnel
Secondary tunnel
Saha bağlantısı / Site connection
Apps
Applications at the customer site.
Core
Source core element connecting applications to the CPE pair.
Primary CPE
Primary customer device carrying traffic in normal operation.
Secondary CPE
Secondary customer device intended for takeover. Actual takeover depends on routing policy.
Primary DC
Primary data center in the Secure Access region, with a tunnel from the primary CPE.
Secondary DC
Secondary data center in the Secure Access region, with a tunnel from the secondary CPE.
CISCO · Figure 1
Cisco AI Defense: hybrid deployment
Select nodes to read their roles; zoom or enter full screen to follow the connections.
Drag to pan or use the buttons to zoom. Node descriptions appear on hover.
AI Defense SaaSControl Plane SaaSConfigurations and EventsAI PODAI WorkloadsAI Defense Connector (Data Plane)DashboardManagement view inside the SaaS control plane.Control Plane ComponentsSource representation of SaaS control-plane components.EventsEvents entry within the source configurations-and-events group.PoliciesPolicies within the source configurations-and-events group.Test ReportSource test-report element for model validation.GenAI AppsGenerative AI applications shown inside the AI POD.AI ModelsAI models shown inside the AI POD.ValidationPreproduction model/application evaluation role inside the AI Defense connector.RuntimeRuntime inspection role inside the AI Defense connector.Data CenterData-center element with an API relationship to the connector in the source.Customer DataCustomer data inside the AI POD boundary. No direct data cable to SaaS is drawn in the source.Outbound connectionport 443APIsAPIs
Data plane → SaaS · TCP 443
API ilişkisi / API relationship
Dashboard
Management view inside the SaaS control plane.
Control Plane Components
Source representation of SaaS control-plane components.
Events
Events entry within the source configurations-and-events group.
Policies
Policies within the source configurations-and-events group.
Test Report
Source test-report element for model validation.
GenAI Apps
Generative AI applications shown inside the AI POD.
AI Models
AI models shown inside the AI POD.
Validation
Preproduction model/application evaluation role inside the AI Defense connector.
Runtime
Runtime inspection role inside the AI Defense connector.
Data Center
Data-center element with an API relationship to the connector in the source.
Customer Data
Customer data inside the AI POD boundary. No direct data cable to SaaS is drawn in the source.
Controlled transition
Inventory and application dependencies establish the baseline. Architecture, capacity expectations and security rules are clarified with the relevant teams. Pilot scope, acceptance criteria and rollback steps are documented before implementation. Migration waves follow business impact; each wave compares essential access, critical application flows and monitoring evidence.
Handover and operations
Topology, configuration ownership and maintenance procedures belong in the handover. Monitoring and escalation follow the organisation’s operating model. Product and service scope is clarified through discovery; support levels are agreed contractually. Share your requirements with Trustnet to assess practical options for your existing infrastructure.
Combine firewall, identity, secure access, endpoint, email, workload and OT controls with clear responsibilities, and design investigation and response with XDR.