-
Feature Request
-
Resolution: Done
-
Undefined
-
None
-
None
-
False
-
None
-
False
-
-
-
1. Proposed title of this feature request
Improve network graph to show possible violations
2. What is the nature and description of the request?
The network graph of RHACS shows basic network traffic information, without any additional information if a Deployment is at risk or has any vulnerabilities.
Expectation: It is expected that the network graph already shows and cross-links the actual violations of a namespace or deployment/pod. For example, if the deployment “patient” has a critical violation the network graph should already mark this accordingly. For example, draw the dot, which represents the deployment as red. Moreover, the namespace itself might be coloured accordingly.
In addition to the graphical indications, a cross-link to the list of violations, filtered by the deployment or namespace should be added to the network graph.
3. Why does the customer need this? (List the business requirements here)
Justification: An indication of current violations in the deployments or namespace on the network graph would increase the user experience massively, showing already which vulnerable application is talking to which entity while it has possible security violations. Linking them directly to the list of violations, will help RHACS users to easily filter and identify vulnerabilities based on the network flow.
4. List any affected packages or components.
RHACS network graph in UI
Please note that this Jira is part of a larger group of issues raised by BRZ, and you can find more information in this google document.
- mentioned in
-
Page Loading...