7.3. About network baselining in the network graph


In RHACS, you can minimize your risks by using network baselining. It is a proactive approach to keep your infrastructure secure. RHACS first discovers existing network flows and creates a baseline, and then it treats network flows outside of this baseline as anomalous.

When you install RHACS, there is no default network baseline. As RHACS discovers network flows, it creates a baseline and then it adds all discovered network flows to it, following these guidelines:

  • When RHACS discovers new network activity, it adds that network flow to the network baseline.
  • Network flows do not show up as anomalous flows and do not trigger any violations.

After the discovery phase, the following actions occur:

  • RHACS stops adding network flows to the network baselines.
  • New network flows that are not in the network baseline show up as anomalous flows but they do not trigger any violations.

7.3.1. Viewing network baselines from the network graph

You can view network baselines from the network graph view.

Procedure

  1. Click the Namespaces list and use the search field to locate a namespace, or select individual namespaces.
  2. Click the Deployments list and use the search field to locate a deployment, or select individual deployments to display in the network graph.
  3. In the network graph, click on a deployment to view the information panel.
  4. Select the Baseline tab. Use the filter by entity name field to further restrict the flows that are displayed.
  5. Optional: You can mark baseline flows as anomalous by performing one of the following actions:

    • Select an individual entity. Click the overflow menu, kebab , and then select Mark as anomalous.
    • Select multiple entities, and then click Bulk actions and select Mark as anomalous.
  6. Optional: Check the box to exclude ports and protocols.
  7. Optional: To save the baseline as a network policy YAML file, click Download baseline as network policy.

7.3.2. Downloading network baselines from the network graph

You can download network baselines as YAML files from the network graph view.

Procedure

  1. In the RHACS portal, go to Network Graph.
  2. Click the Namespaces list and use the search field to locate a namespace, or select individual namespaces.
  3. Click the Deployments list and use the search field to locate a deployment, or select individual deployments to display in the network graph.
  4. In the network graph, click on a deployment to view the information panel.
  5. The Baseline tab lists the baseline flows. Use the filter by entity name field to further restrict the list of flows.
  6. Optional: Check the box to exclude ports and protocols.
  7. Click Download baseline as network policy.

7.3.3. Configuring the network baseline observation time frame

You can configure the duration of the observation period that RHACS uses when creating the network baseline.

Procedure

  • Set the ROX_NETWORK_BASELINE_OBSERVATION_PERIOD environment variable by running the following command:

    $ oc -n stackrox set env deploy/central \
      ROX_NETWORK_BASELINE_OBSERVATION_PERIOD=<value>
    • oc: If you use Kubernetes, enter kubectl.
    • <value>: Use time units, for example: 300ms, -1.5h, or 2h45m. Valid time units are:

      • ns
      • us or µs
      • ms
      • s
      • m
      • h

7.3.4. Enabling alerts on baseline violations in the network graph

You can configure RHACS to detect anomalous network flows and trigger violations for traffic that is not in the baseline. This can help you determine if the network contains unwanted traffic before you block traffic with a network policy.

Procedure

  1. Click the Namespaces list and use the search field to locate a namespace, or select individual namespaces.
  2. Click the Deployments list and use the search field to locate a deployment, or select individual deployments to display in the network graph.
  3. In the network graph, click on a deployment to view the information panel.
  4. In the Baseline tab, you can view baseline flows. Use the filter by entity name field to further restrict the flows that are displayed.
  5. Toggle the Alert on baseline violations option.

    • After you toggle the Alert on baseline violations option, anomalous network flows trigger violations.
    • You can toggle the Alert on baseline violations option again to stop receiving violations for anomalous network flows.
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

Red Hat ドキュメントについて

Legal Notice

Theme

© 2026 Red Hat
トップに戻る