What's New
What's New
FortiCWP 21.3.0 Release Highlights
FortiCWP Container Protection:
-
Docker Hub Integration is added to the list of available container management platforms.
- New Kubernetes Agent version 21.3.0-2.1 is now available with log collection.
-
Automatic Container Image Scan - Registry/Repository Scan and Cluster Compliance Scan Intervals can be configured in Admin > Settings.
-
Registry/Repository Scan can be initiated manually in Configure > Registry.
-
Container Visibility - Pod Layer gained additional details: replica, container name, and label info.
-
Suspicious IP Group, supported by FortiGuard, is added to Container Visibility to identify botnet and malicious IP addresses.
-
IP connected to Jenkins through CI/CD Integration can be viewed in CONFIGURE > Kubernetes Cluster.
-
CIS Benchmark Compliance rate in Cluster Detail page is updated to graphical chart representation.
-
Container Registry Name now uses local registry name during registry creation in place of Kubernetes cluster url.
-
Ability to edit cluster name is added to CONFIGURE > Kubernetes Cluster.
-
Cluster names are given the flexibility to choose between using the original cluster name (only for EKS, GKE, AKS) or a user defined name.
-
Traffic Group can now be created and configured for both Container Protection and Workload Protection.
What's New
What's New
FortiCWP 21.3.0 Release Highlights
FortiCWP Container Protection:
-
Docker Hub Integration is added to the list of available container management platforms.
- New Kubernetes Agent version 21.3.0-2.1 is now available with log collection.
-
Automatic Container Image Scan - Registry/Repository Scan and Cluster Compliance Scan Intervals can be configured in Admin > Settings.
-
Registry/Repository Scan can be initiated manually in Configure > Registry.
-
Container Visibility - Pod Layer gained additional details: replica, container name, and label info.
-
Suspicious IP Group, supported by FortiGuard, is added to Container Visibility to identify botnet and malicious IP addresses.
-
IP connected to Jenkins through CI/CD Integration can be viewed in CONFIGURE > Kubernetes Cluster.
-
CIS Benchmark Compliance rate in Cluster Detail page is updated to graphical chart representation.
-
Container Registry Name now uses local registry name during registry creation in place of Kubernetes cluster url.
-
Ability to edit cluster name is added to CONFIGURE > Kubernetes Cluster.
-
Cluster names are given the flexibility to choose between using the original cluster name (only for EKS, GKE, AKS) or a user defined name.
-
Traffic Group can now be created and configured for both Container Protection and Workload Protection.