Scope for GAing External IPs:

Goal 1: Ensure external IPs can be viewed in the network graph's side panel.

This means in practice 2 things:

 1. When a customer click on the network graph 'External Entities', the side panel provides granular information about the IPs in that bucket. 

2. When a customer clicks on a deployment that communicates with External Entities, it expected that 'Flows' shows both Internal and External flows tabs. Each of the tabs will filter only the flows relevant. And external flows tab will include granular IP information if available. 

Baselines will not show granular IPs even through external IPs is available. 

Goal 2: Fix UI and data bugs reported in 4.7 ROX-28021

• Fix UI and data bugs reported in 4.7 

Goal 3: Provide additional IP context to Unexpected Network Flow violations  ROX-28546

• Customer problem: As a customer, who received unexpected network flow violations, I want to know the exact IP behind. 

Goal 4: Extensive testing and perf-scale testing
**

Out of scope for External IP GAs:

• Anomalous network flows will keep working the same way as in 4.7 = in case a external network flow is part of the baseline, it will only compare the port and protocol.
• Runtime network policy generation will keep working the same way as in 4.7 = Network policies will only be generated for external IPs taking into consideration port and protocol. 
• Visibility on CIDR blocks  ROX-24987