--- title: "Cloudvisory Release Notes 4.10.2" slug: "cloudvisory-release-notes-4-10-2" updated: 2026-07-23T12:51:51Z published: 2026-07-23T12:51:51Z canonical: "docs.trellix.com/cloudvisory-release-notes-4-10-2" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Cloudvisory Release Notes 4.10.2 ![FireEye logo — stylized black eye/ellipse with vertical stripe pattern](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/cloudvisory-release-notes-4.10.2_page_0001_img_01.png?sv=2026-02-06&spr=https&st=2026-11-22T13%3A56%3A17Z&se=2026-11-22T14%3A56%3A17Z&sr=c&sp=r&sig=fhaOMk1Uzj%2FcasgkWW8rEd%2FaxPWXr3TfbAR%2FB99wX5o%3D) ## Cloudvisory Security Platform # **Release Notes** 4.10.2 Copyright © 2021 Cloudvisory Documentation, Fireeye Inc. 1 # Release Notes ### Highlights ## Software Changes - Added support for AWS GovCloud, and AWS China Cloud - Improved performance rendering on the dashboard. - Improved performance of the Compliance Check Inspector page - Improved performance on the Network Security landing page - Improved the search filters on Inspector Pages: - Clear any open-text search values when submitting a new filter - Show blank page (i.e. no results) when all filters are removed/deleted - Carry forward any dashboard filters to inspector pages only for any clickable links on the dashboard. - Added the capability for compliance service to generate the remediation record for any violation fixes in provider. - Added new discovery for AWS EC2 VPC Flow Log - Added a new Compliance check: AWS-200-109:1.0.0 - ensure AWS VPC Flow Log is configured to publish to specific bucket - Added new AWS Cloud Type for AWS in provider page to support AWS GovCloud and AWS China Cloud. - Changed Tag filters such that if the Tag keys match, they are OR’d and if they do not match, they are ANDed. ## Fixed Issues - Azure flows mapped to wrong server with same IP address - Azure hierarchy processor fixed to ensure that multiple parentIds are not added to non k8s nodes - Fixed LastUsedTime for compliance check AWS-100-068 - Fixed remediation for compliance check AWS-200-031, Azr-200-002 - Fixed empty value and created time, and add new field ‘LastRotatedTime’ for compliance check AWS-001-003 - Tags values are missing on the popup link of assets from Compliance check results - Number of risks do not match between Dashboard and Compliance Inspector - ‘Remediate and Notify’ on compliance check results for failed assets. - The Remediate request row can be clicked and when clicked, it pops up the details in the Compliance Checks Inspector. ## Known Issues - Unsupported recommendations for micro-segmentation network policies for OpenStack. - AWS/EKS or Azure/AKS K8S are exported as provider account while exporting the AWS and Azure provider account. - Tag filters on the NPI page do not have the changed behavior yet. Copyright © 2021 Cloudvisory Documentation, Fireeye Inc.