Hi,

This ticket is both for fixing an existing numbering bug but mostly for adding important content that was missing at the time we released 4.6

Part A. Numbering

The section numbering is inconsistent. It looks like section 1.3 should  be demoted, it is just one of the new features under section 1.2

Part B. Top level additions

1. Add a new top section titled:

 NEW! Platform Components

• ACS now differentiates issues related to the underlying platform from those related to user workloads. (hyperlink to 1.2.5)

2. Under "Policy" please add the following bullets (hyperlinks)

• Policy Violation Views (hyperlink to 1.2.6)
• Upgraded UI filters (1.2.7)
• Policy Editor UI (1.2.8)
• Exposure analysis in Network Policy tooling (1.2.9)

Part C. hyperlinks

Under New Features add the following. (Pushing down the current 1.2.5 section, but the numbering might change depending how you organize it)

1.2.5 Platform Components

Users need to address security issues differently when issues are in the underlying platform (e.g. OpenShift) or in user workloads.  In ACS 4.6, we introduce an internal definition of what constitutes the underlying platform and enhance ACS views to allow users to focus on either.  Initially, in ACS 4.6 : 

1. Policy Violations UI and API support this differentiation. The UI is realized using the new Policy Violations Views (hyperlink).
2. In ACS 4.6 the Platform definition is built-in (not yet customizable). You can see the impact of the definition in your environment using the global search. Set the new filter `"Platform Component" : true` and then list namespaces. Make sure you have the selector `"Show Orchestrator Components"` set to the ON position.

1.2.6 Policy Violation Views

1. This version introduces a new drop-down selector in the ACS Violations menu, allowing users to focus on violations related to User (Application) workloads, Platform workloads, or both
2. In addition, the UI now lists violations across three panels to easily distinguish between active, resolved, or attempted violations.  

1.2.7 Upgraded UI filters

The Violations UI now exhibits comprehensive filtering capabilities, similar to those introduced earlier in Vulnerability Management:

• By Cluster/NS/Deployment
• By Violation: Date, Time, Entity Type
• By Policy: Name, Category, Severity, and more

1.2.8 Policy Editor UI

1. Sections in the policy editor have been reordered to better reflect the logical policy structure, splitting the policy definition part (rules and metadata) from the behavior part (scope and actions)
2.   The editor is now aware of "Policy as Code" capabilities and will show a warning when editing an "Externally Managed" policy

1.2.9 Exposure analysis in Network Policy tooling

When you produce a connectivity map using the Build time network policy tools (link to docs), an option is now available to depict open connections. This configuration increase the exposure risk and such connections are a good candidate for tightening down.  For example,  a network policy may permit ingress to a particular pod from any namespace instead of specifying individual consumers.

To include exposure information,  add the `--exposure` flag :

roxctl netpol connectivity map --exposure