registry.redhat.io/advanced-cluster-security/rhacs-main-rhel8:4.3.0
Red Hat Advanced Cluster Security for Kubernetes (RHACS) is an enterprise-ready, Kubernetes-native container security solution that protects your vital applications across the build, deploy, and runtime stages of the application lifecycle. Red Hat Advanced Cluster Security for Kubernetes deploys into your infrastructure and integrates with your DevOps tools and workflows. This integration provides better security and compliance, enabling DevOps and InfoSec teams to operationalize security.
RHACS version | Released on |
---|---|
|
15 November 2023 |
This release adds improvements related to the following components and concepts.
RHACS support has been increased for the following hardware and software:
Red Hat OpenShift on IBM Cloud: You can now protect Red Hat OpenShift on IBM Cloud by using RHACS. With this release, you can run secured clusters on Red Hat OpenShift on IBM Cloud.
IBM Power and IBM Z: RHACS Central Services are now supported on IBM Power and IBM Z.
Red Hat OpenShift Service on AWS: RHACS is supported on ROSA hosted control plane (HCP) enabled clusters.
Red Hat OpenShift: This release is supported with OpenShift Container Platform 4.14.
For more information, see Supported platforms and installation methods.
With this release, the Vulnerability Reporting option under the Vulnerability Management (2.0) menu is generally available. Several enhancements have been made to vulnerability reporting, including the ability to customize email templates that are used when reports are sent. For more information, see Vulnerability Reporting.
Reports created in the Vulnerability Management 1.0 → Reporting page are automatically migrated. For more information, see Migration of vulnerability reports when upgrading to RHACS version 4.3 and later. |
The ability to mark an image as watched has been migrated from the Vulnerability Management (1.0) menu item to Vulnerability Management 2.0. Watched images are still scanned for vulnerabilities even when not in use by an active deployment.
For more information, see Scanning inactive images.
With this release, RHACS introduces an administration events dashboard that allows you to efficiently manage and troubleshoot events within your RHACS instance and significantly improves the reliability and security of your RHACS instance.
For more information, see Using the administration events dashboard.
You can now scan images stored in image registries, including cluster local registries such as the OpenShift Container Platform integrated image registry, by using the roxctl
CLI.
For more information, see Image scanning by using the roxctl
CLI.
You can now invite users and define their roles to ensure accurate access control and improve the security of your RHACS instance.
For more information, see Inviting users to your RHACS instance.
When audit logging is enabled, audit log messages now include the source IP address of the audit log request. For more information, see Enabling audit logging.
The default policy "Iptables Executed in Privileged Container" has been renamed to "Iptables or nftables Executed in Privileged Container" and now also detects the nft
process that is used by nftables
.
Risk reprocessing has been changed from potentially being computed every 15 seconds to 10 minutes. This improves system performance by debouncing expensive risk calculations. To use the earlier value for risk reprocessing, set the environment variable ROX_RISK_REPROCESSING_INTERVAL to 15s
.
In the past several RHACS releases, we have optimized and enhanced RHACS features and functionality available in the Vulnerability Management (1.0) menu item and migrated them to the Vulnerability Management (2.0) menu item.
The existing page for Risk Acceptance in the Vulnerability Management (1.0) menu item will be migrated to the Vulnerability Management (2.0) menu item in an upcoming release. It will be renamed Vulnerability Exception Management.
We invite you to review the existing features in the Vulnerability Management (2.0) menu item and give us feedback by clicking the red Feedback button in the RHACS web portal.
Some features available in earlier releases have been deprecated or removed.
Deprecated functionality is still included in RHACS and continues to be supported; however, it will be removed in a future release of this product and is not recommended for new deployments. For the most recent list of major functionality deprecated and removed, see the following table. Additional information about some removed or deprecated functionality is available after the table.
In the table, features are marked with the following statuses:
GA: General Availability
TP: Technology Preview
DEP: Deprecated
REM: Removed
NA: Not applicable
Feature | RHACS 4.1 | RHACS 4.2 | RHACS 4.3 |
---|---|---|---|
CIS Docker v1.2.0 Compliance Standard |
NA |
DEP |
DEP |
Custom Security Context Constraints (SCCs): |
DEP |
DEP |
REM |
Examining images for Application-level dependencies for vulnerability reporting: |
DEP |
DEP |
REM |
|
DEP |
DEP |
REM |
|
NA |
DEP |
DEP |
|
NA |
DEP |
DEP |
|
NA |
NA |
DEP |
|
NA |
NA |
DEP |
|
NA |
NA |
DEP |
|
NA |
NA |
DEP |
|
NA |
NA |
DEP |
|
DEP |
DEP |
REM |
|
DEP |
DEP |
REM |
Vulnerability Management (1.0) menu item |
GA |
GA |
DEP |
Vulnerability Management (1.0): Image CVEs, Image Components, Images, Deployments, and Namespaces |
DEP |
DEP |
REM |
Vulnerability Management (1.0) → Vulnerability Reporting page |
DEP |
DEP |
REM |
|
DEP |
DEP |
REM |
|
GA |
DEP |
DEP |
|
DEP |
DEP |
REM |
The following section provides additional information about deprecated features listed in the preceding table.
The Vulnerability Management (1.0) menu item in the RHACS web portal has been deprecated and future removal is planned. It is replaced by Vulnerability Management (2.0).
The /v1/cve/requests
APIs have been deprecated and will be replaced by /v2/vulnerability-exceptions/
APIs in the future.
Vulnerability deferral management for host (/node
) and platform (/cluster
) vulnerabilities has been deprecated and will be removed in the future. After deferral management is removed, deferrals cannot be created for host and platform vulnerabilities and the existing exceptions enforced on host and platform vulnerabilities will be reverted. The affected APIs are /v1/nodecves/suppress
, /v1/nodecves/unsuppress
, /v1/clustercves/suppress
, and /v1/clustercves/unsuppress
.
Release date: 15 November 2023
Fixed the diagnostic bundle generation returning an incomplete .zip file when the connection to a secured cluster is lost.
Fixed an issue with the Sensor upgrade tool failing to upgrade from earlier versions on OpenShift Container Platform clusters.
In some cases, Common Vulnerabilities and Exposures (CVEs) that were deferred and approved were not added to the list of snoozed CVEs. This behavior was caused by an issue with the /v1/suppress
and /v1/unsuppress
APIs and has been fixed.
Fixed file search in the ca-setup.sh
file that is used to configure additional Certificate Authorities (CAs). Previously, the script could not find any files in the directory, even with the correct .crt and .pem extensions.
RHACS version 4.2 introduced additional logic that considers the socket connection state to decide whether Collector reports a connection or not. The expected behavior is that the connection is not reported until it is successfully established. A known issue on the ppc64le
architecture can cause a blocked or failing connection to be reported instead of being silenced. No workaround exists for this issue.
RHACS Central components do not deploy correctly on a default ROSA cluster. The workaround is to scale the worker nodes to allow the RHACS components to be scheduled. See RHACS Central pods do not schedule on a default ROSA cluster for more information.
Image | Description | Current version |
---|---|---|
Main |
Includes Central, Sensor, Admission controller, and Compliance. Also includes |
|
Scanner |
Scans images and nodes. |
|
Scanner DB |
Stores image scan results and vulnerability definitions. |
|
Collector |
Collects runtime activity in Kubernetes or OpenShift Container Platform clusters. |
|
Central DB |
PostgreSQL instance that provides the database storage for Central. |
|