TotalCloud Release 2.19

October 15, 2025

TotalCloud 2.19 brings updates to supported integrations, insights, inventory, dashboard, and controls.

TotalCloud Dashboard: New and Enhanced Connector Widgets

Applicable for:  aws azure gcp oci

With this release, we are introducing a new Dashboard template, new Widget templates and enhancements to provide deeper visibility and actionable insights into your connector ecosystem. You can either choose the new dashboard template with all the new widgets included, or manually configure the existing and new widgets as per your requirements.

new_conn_dashboard

In addition to the original nine default widget templates, the TotalCloud Dashboard now includes seven newly added widget templates, bringing the total to 16. The New Connector widgets templates and enhancements are:

  • Remaining CSPM Connectors (New Template created )
    This widget allows you to track your remaining CSPM connectors and stay informed about license utilization to avoid coverage gaps.
    Supported data representation format: Stacked bar Chart

    remaining_cspm_connectors
  • Connector Count: Critical Misconfiguration (New Template created )
    This Connector widget allows you to track your accounts with critical misconfiguration.
    Supported data representation format: Tabular

    critical_misconfiguations
  • Connector with Critical Vulnerabilities 
    Applicable for: 
    aws azure
    This Connector widget enhancement lets you track accounts with critical vulnerabilities. To enable this feature, you can edit an existing widget or create a new one, using the query "vulnerability.severity in (4,5)."
    Supported data representation format: All formats 

    conn_critical_vuln
  • Connectors with Attack Path enabled resources
    Applicable for:  aws azure

    This Connector widget enhancement lets you track your connectors with attack path-enabled resources. To enable this feature, you can edit an existing widget or create a new one, using the query "isAttackPathEnabled:true."
    Supported data representation format: All formats

    conn_attackpath
  • Connectors with Assets (Created → Terminated)
    This widget enhancement lets you track instances/VMs that were created and subsequently terminated within the last 24 hours, giving you real-time visibility into short-lived assets. To enable this feature, you can edit an existing widget or create a new one using the following query:
    • AWS: instance.state:terminated and Created:[now-24h..now-1s]
    • Azure: virtualmachine.status:Deleted and Created:[now-24h..now-1s]
    • GCP: instance.status : TERMINATED and Created:[now-24h..now-1s]
    • OCI: instance.lifecycleState in (Terminated,TERMINATED) and Created:[now-24h..now-1s]
    Supported data representation format: All formats

    conn_created_terminated
  • Connectors with Public Assets (scanned/unscanned by Cloud Perimeter Scan)
    Applicable for: 
    aws azure
    This widget enhancement allows you to view connectors with public assets scanned via Cloud Perimeter Scan. To enable this feature, you can edit an existing widget or create a new one, using the following query:
    • AWS: not instance.networkInterface.publicIp is null and instance.scanType:Cloud Perimeter Scan and instance.lastScanDate:[now-24h..now-1s]
    • Azure: not virtualmachine.networkInterface.publicIp is null and virtualmachine.scanType:Cloud Perimeter Scan and virtualmachine.lastScanDate:[now-24h..now-1s]
    Supported data representation format: All formats

    conn_public_assets
  • Total Connectors
    This enhancement includes two new connector widget templates:
    1. Connectors with/without Organization Connector: This widget provides visibility into organizational linkage for each connector.
      Supported data representation format: All formats

      conn_org_connector
    2. Total Connectors in ERROR / SUCCESS (New Template created): This widget enhancement allows you to quickly assess the operational status of all your connectors, whether they are successful, in error, or in progress state.
      Supported data representation format: Stacked Bar Chart

      conn_status
  • Connectors with Capability Stats (New Template created ) 
    Applicable for:  aws azure gcp
    This widget enhancement allows you to get the number of connectors with scan types (CSPM, API-Based Scanning, Snapshot-Based Scanning, Cloud Perimeter Scanning) enabled/disabled for each cloud provider.
     
    Supported Scan Types:
    • AWS: API Based Scan, Cloud Agent Scan, Cloud Perimeter Scan, Snapshot Based Scan, VM Scan, and Other Scan
    • Azure: Cloud Agent Scan, Cloud Perimeter Scan, Snapshot Based Scan, VM Scan, and Other Scan.
    • GCP: Cloud Agent Scan, Cloud Perimeter Scan, and Other Scan

    Supported data representation format:
     Tabular

    Scan Type Disabled

    scan_disabled

    Scan Type Enabled

    scan_enabled
  • Merge/Unmerge Connector Widget (New Template created)
    Applicable for:  aws azure gcp
    This widget lets you see the count of connectors that are merged versus unmerged with any organization connector.
    Supported data representation format: Tabular

    conn_mergestate
  • Connectors with Scan Types (New Template created)
    Applicable for:  aws azure gcp
    This widget enhancement enables you to view the number of connectors that have assets scanned using any scan method, including CSPM, API-Based Scanning, Snapshot-Based Scanning, or Cloud Perimeter Scanning. To enable this feature, you can edit an existing widget or create a new one, using the following query, followed by any supported scan Type:
    • AWS: instance.scanType: {Scan Type}
    • Azure: virtualmachine.scanType: {Scan Type}
    • GCP: instance.scanType: {Scan Type}
    Supported data representation format: All formats

    conn_aws

Snapshot-Based Scans Logs

Applicable for:  aws 

With this release, TotalCloud introduces Snapshot-Based Scan Logs, providing full visibility into the history and details of snapshot-based scans. You can now access a centralized log view that tracks all assets scanned using snapshot-based methods.

Scan Types Supported:

  • OS Scan
  • SwCA (Software Composition Analysis)
  • Secret Scan

Prerequisite: CloudFormation Service Template (CFT-S) version 10 or above

To view this feature, navigate to Configure > Snapshot Scan Logs.

To support this feature, we have introduced new search tokens to help you filter the logs.

snapshot_logs

Enhanced Cloud Posture: QFlow UDC Evaluation Visibility

Applicable for:  aws 

With this enhancement, you can now build and evaluate resources at the account level using user-defined controls (UDCs), providing a centralized and streamlined overview of evaluation results, and making it easier to access and interpret QFlow-based UDC assessments across your cloud accounts.

This feature applies only to selected QFlow user-defined controls. To enable it in TotalCloud, select the checkbox (shown below) under Advanced Options in the TotalCloud node of QFlow.

tc_node

Enhancements include:

  • Account-Level Evaluation Results: Evaluation results are now displayed at the account level, replacing the previous resource-level view. This provides a broader perspective on posture status across your environment. 

    eva_account_level
  • Region-Wise Resource Evaluation in Evidence Menu: The Evidence menu for each account now presents region-wise evaluation results for all associated resources, enabling easier navigation and analysis.  
    evidence_region
  • Improved Visibility of Failed Resources: A dedicated Code Block tab in the Evidence window now lists all failed resources, organized by region, to help quickly identify non-compliant assets.
    evidence_code_block

Benefits:

  • Aggregated posture data at the account level offers a more cohesive and efficient evaluation experience.
  • Allows you to assess posture across all regions from a single interface, eliminating the need to inspect individual resources.
  • Regional grouping of failed resources helps pinpoint issues quickly and take corrective action with greater speed and accuracy.

Enhanced Connector Configuration in User Onboarding 

Applicable for:  aws azure gcp 

In our commitment to continuous improvement, this release enhances the onboarding experience by refining the connector setup process, enabling more flexible configurations within the TotalCloud application.

Previously, onboarding only allowed configuration of member connectors. With this release, you can now also configure organization/Tenant connectors as part of the onboarding process, delivering a more complete experience from the beginning.

Key Benefits of the New Onboarding Workflow

  • Organization/Tenant Connector Support: Configure both organization/tenant and member connectors during onboarding.
  • Simplified Setup Flow: Simplified user interface for setting up all connector types in one walk through.
  • Less post-setup adjustments: Completely sets up your TotalCloud environment during the onboarding process, minimizing the necessity for modifications after the setup is completed.

To access this new onboarding flow, go to the TotalCloud's Home page and click Configure More Connectors > Choose your Cloud Provider > Select the needed connector type (Account/Organization) from the new configuration screen.

For more detailed onboarding steps, check out the onboarding sections for your cloud provider in our TotalCloud online help: AWS | Azure | GCP.

New configuration screen for AWS.

onboarding_aws

New configuration screen for Azure.

onboarding_azure

New configuration screen for GCP.

onboarding_gcp

Enhanced Evidence Details for Control Evaluation

Applicable for:  aws azure gcp oci

With this release, we have enhanced the evidence details screen to provide more insight into the control evaluation reporting for each resource.

The following are the new enhancements for each detail section:

  • Evaluation Summary: New fields added to show the previous and current state of evaluation.

    cloud_run_services

    If no previous state data is found, then "Nothing Found" information will be shown. Previous state data gets updated on the next connector run or state change.

  • Actual Results: This section presents the evaluation results of the resource in accordance with the defined control rules. The information displayed varies based on the specific evaluation criteria applied to the resource.
    actual_results
  • Code Block Tab: The Code Block tab shows the results of the evaluation in a json structure.
    code_block
  • Remediation Activity: This displays the remediation details for the resource if remediation action was selected.

    Select Remediate Now
    remediate_now

    Click on Remediation Activity tab to view the remediation details
    remediation_activity
  • View in AWS Console: This shows the option to view the resource in the AWS console.
    Applicable for:  aws 
    cloud_run_services
  • Exception details: This section provides exception details for a resource, such as the status, start date, and end date of the exception.
    actual_results

New search tokens are also introduced to support this feature. Read about the new tokens here.

Enhanced CSV Reports: New Column for Resources deleted from Cloud

Applicable for:  aws 

To improve visibility into real-time changes in your cloud environment, a new "Deleted from Cloud" column has been added to CSV reports generated via both the UI and APIThis column reflects whether a resource has been deleted from the cloud provider. If a resource is no longer present in the cloud environment, the column will display "True", helping you track asset lifecycle changes more effectively.

This enhancement builds on real-time inventory metadata updates captured through cloud events, offering better context for asset status.

deleted_from_cloud

  • This column is visible only when Event Bridge is enabled for your subscription.
  • If the report is generated using a connector without Event Bridge enabled, the column will still appear, but its values will remain empty.

Extended Inventory Support to AWS AI Services

Applicable for:  aws

TotalCloud is now adding a new resource to its AWS inventory base. The AWS AI Services provide a detailed view of the AI services running in your AWS environment. 

The inventory can identify and report the following kind of AWS AI Services:

  • Bedrock Foundation Model
  • Bedrock Custom Model
  • Bedrock Knowledge Bases
  • Sagemaker Models

We have introduced a new API parameter and a new token to help with accessibility of these resource findings.

Read about the token here.

Read about the API parameter here.

Enhanced Google Cloud Run Services Inventory Support

Applicable for:  gcp 

As part of Google Cloud's transition of Cloud Functions to Cloud Run functions, we have updated our platform to align with this change and improve the accuracy of our cloud resource inventory.

What's New:

  • Enhanced Cloud Run Services Inventory

    We have enhanced the Cloud Run Services inventory type by offering more detailed resource-level insights and better tracking features.
  • Updated Control - CID: 52186

    The control "Ensure No Cloud Run Service is Publicly Accessible" has been updated to support and evaluate Cloud Run Services in accordance with the new inventory structure.

cloud_run_services

In the future release, the existing Cloud Functions inventory type will be deprecated. All related resources will be migrated to the Cloud Run Services inventory to ensure simplified inventory management and governance.

Cloud Detection and Response (CDR)

The following sections describe the enhancements made to the CDR environment in the upcoming CDR release. 

These CDR enhancements will be available by the end of October.

Integrated Container Security Runtime IP Reputation Events

Applicable for:  aws azure gcp 

With this release, we have integrated the Container Runtime Security (CRS) IP reputation events with the CDR Investigate menu. This feature allows the creation of CDR threat alerts based on CRS Network Events received from the CRS sensor when suspicious communications are detected between a container and a malicious IP address.

The service determines the reputation of the public IP using threat intelligence verdicts. Based on the verdict:

  • If the public IP is identified as malicious, a corresponding alert is generated in CDR, which includes the complete raw data of the event when selected.
  • If the public IP is deemed non-malicious, the event is recorded and ignored.

Benefits

  • Enhances threat detection by identifying connections to malicious public IPs and ensuring that critical event data is both alerted on and securely stored, improving visibility and response efficiency.
  • Allows for continuous monitoring, detection, and response to threats in real-time, assisting in prioritizing high-risk containers and reducing attack surfaces in dynamic cloud-native environments.

CRS IP Reputation

New TruRisk™ Score for CDR Findings

Applicable for:  aws azure gcp 

This release, we are introducing a TruRisk™ Score column to the Detections page under the Investigate tab. The TruRisk™ score provides deeper insight into the risk level of each finding, which enables quick assessment of the real-world risk associated with each vulnerability.

Benefits

  • Helps focus on the most exploitable and impactful vulnerabilities.
  • Helps understand risk in business terms to enable smarter, faster decision-making.

cdr_trurisk

Enhanced Filter Option for Dashboard Widgets

Applicable for:  aws azure gcp 

With this release, we have added three new search query options under the "Group By" filter to dashboard widgets for CDR findings to dashboard widgets for CDR findings:

  • tc.findings.remote.ipAddress
  • tc.findings.remote.country
  • tc.findings.category

cdr_widget_token

You can now group and filter findings by IP address, country, and category, making it easier to perform targeted analysis and gain better visibility into remote connections.

tc.findings.category

Added Support for Azure VNet Flow Logs

Applicable for:  azure 

This release, we have added support for Azure VNET Flow Logs in CDR Investigate, alongside the existing NSG Flow Logs. This update ensures continued visibility as Azure NSG Flow Logs are being retired. With VNET Flow Logs, you gain deeper insights into network activity, improved detection of vulnerabilities, and more comprehensive threat analysis across your Azure environment.

For more details, see.

Enhanced Findings View in CDR Investigate

Applicable for:  aws azure gcp 

In this release, we have enhanced the Findings view in Cloud Detection and Response (CDR) to make it easier and faster to investigate grouped findings.

Earlier, when using the “Group By” option in the Investigate tab, you could only see the count of findings per resource. To view detailed information, such as detection time, severity, and account number, QQL queries had to be manually constructed for each resource.

With this release, you can now click directly on the findings count in the grouped view to instantly access detailed findings for that specific resource without manually constructing any QQL queriesThis enhancement streamlines your investigation workflow, reduces manual effort, and helps you quickly assess and respond to critical findings across your cloud environment.

Group by View with enriched findings Count

groupby_detections

When selected, the enriched findings count shows the details for the selected resource with the QQL query constructed.

groupby_redetails

Enhancement: IPv6 Address Redirect Support in Investigate Tab

Applicable for:  aws azure 

In Release 2.17, we introduced support for IPv6 addresses for AWS and Azure. This release builds on that enhancement by adding the ability to redirect IPv6 addresses in the Investigate tab findings to their respective resource details pages. You can now seamlessly navigate to detailed views of AWS and Azure resources using IPv6 addresses, improving traceability and investigation workflows.

Enriched Resource Raw Data in CDR Investigate

Applicable for:  aws azure gcp 

With this release, we have enriched the resource data in the CDR Investigate to provide deeper insights and improve investigation efficiency. With this update, you can now:

  • View TrueRisk™ scores for both IPv4 and IPv6 host addresses.
  • Access detailed container and host port mapping information.
  • Get node-level information to understand the infrastructure context.

These enhancements offer a more comprehensive view of each resource, helping you make faster, more informed decisions during investigations.

cdr_enriched_alerts

New Buildtime and Runtime Controls

New buildtime and runtime controls introduced to the cloud posture analysis.

New Controls in Amazon Web Services 

New Controls for AWS IAC policy.

CID Title Service Resource
562 Ensure that Network Load Balancer(s) Listeners Use SSL Certificates Provided by AWS Certificate Manager EC2 LOAD_BALANCER

New Controls for AWS Best Practice policy.

CID Title Service Resource
563 Ensure that AWS CloudFront distribution origins do not use insecure SSL protocols Cloud Front Cloudfront Distribution
564 Ensure the traffic between the AWS CloudFront distributions and their origins is encrypted Cloud Front Cloudfront Distribution
565 Ensure your AWS Cloudfront distributions are using an origin access control for their origin S3 buckets Cloud Front Cloudfront Distribution

New Controls in Microsoft Azure

New Controls for CIS Microsoft Azure Compute Benchmark Policy

CID Title Service Resource
50492 Ensure API app is using the latest version of TLS encryption version App Service API App
50493 Ensure Standard Logic App uses latest TLS encryption version Logic App Logic App
50494 Ensure that Standard Logic App have Incoming Client Certificates on Logic App Logic App
50495 Ensure that Register with Entra ID is enabled on API App App Service API App
50496 Ensure that Register with Entra ID is enabled on Standard Logic app Logic App Logic App
50497 Ensure that Register with Entra ID is enabled on Consumption Logic app Logic App Logic App
50498 Ensure Java version is the latest, if used to run the Linux Function App App Service Function App
50499 Ensure Java version is the latest, if used to run the Linux API App App Service API App
50502 Ensure that Logic Apps redirects all HTTP traffic to HTTPS in Azure App services Logic App Logic App
50503 Ensure App Service Authentication is set on Logic Apps Logic App Logic App
50504 Ensure App Service Authentication is set on API Apps App Service API App
50505 Ensure that Logic Apps enforce FtpsOnly access to FTP traffic Logic App Logic App
50506 Ensure HTTP 2.0 is enabled on API App App Service API App
50507 Ensure HTTP 2.0 is enabled on Logic App Logic App Logic App
50509 Ensure PHP version is latest, if used to run Linux API App App Service API App
50510 Ensure that Python version is latest, if used to run Linux API App App Service API App
50511 Ensure that Python version is latest, if used to run Linux Function App App Service Function App


New Controls for CIS Azure Foundation Benchmark Policy

CID Title Service Resource
50534 Ensure that 'Default to Microsoft Entra authorization in the Azure portal' is set to 'Enabled' Storage Account Storage Account
50535 Ensure that Azure Databricks is deployed in a customer-managed virtual network (VNet) Azure Databricks Azure Databricks


New Controls for Azure Without Policy Attachment

CID Title Service Resource
50514 Ensure that Managed Identity is used in Logic Apps Logic App Logic App
50500 Ensure that CORS does not allow every resource to access the API Apps App Service API App
50501 Ensure that CORS does not allow every resource to access the Standard Logic Apps Logic App Logic App
50512 Ensure that routing of outbound non-RFC 1918 traffic to Azure Virtual Network is enabled in API App App Service API App
50513 Ensure that routing of outbound non-RFC 1918 traffic to Azure Virtual Network is enabled in Logic App Logic App Logic App
50515 Ensure web sockets disabled for Function App App Service Function App
50516 Ensure web sockets disabled for API App App Service API App
50517 Ensure web sockets disabled for Logic App Logic App Logic App
50518 Ensure that IP restriction rules are configured for Function App App Service Function App
50519 Ensure that IP restriction rules are configured for API App App Service API App
50520 Ensure that IP restriction rules are configured for Standard Logic App Logic App Logic App
50521 Ensure that API Apps use Azure Files App Service API App
50522 Ensure that Function Apps use Azure Files App Service Function App
50523 Ensure that Standard Logic Apps uses Azure Files Logic App Logic App
50524 Ensure that all your Azure Function App Services applications are using the Backup and Restore feature App Service Function App
50525 Ensure there is a sufficient backup retention period configured for Azure Function App Services applications App Service Function App
50526 Ensure that Api Apps have always-on feature enabled App Service API App
50527 Ensure that Function apps have always-on feature enabled App Service Function App
50528 Ensure that Logic apps have always-on feature enabled Logic App Logic App
50529 Ensure that Request Tracing enabled in Windows Web Apps App Service Web App
50530 Ensure that Web Server Logging enabled in Windows Web Apps App Service Web App
50531 Ensure that Detailed Error Logging enabled in Windows Web Apps App Service Web App
50532 Ensure that Remote debugging is Off for Standard Logic App Logic App Logic App
50533 Ensure that Remote debugging is Off for API App App Service API App

Control Migration

Azure Controls Policy-To-Policy Migration

CID Title Old Policy New Policy
50089 Ensure that HTTP Version used for Function app is latest CIS Microsoft Azure Foundations Benchmark CIS Microsoft Azure Compute Services
50146 Ensure that Function apps enforce FTPS-only access to FTP traffic CIS Microsoft Azure Foundations Benchmark CIS Microsoft Azure Compute Services
50202 Ensure API App enforces FtpsOnly access to FTP traffic CIS Microsoft Azure Foundations Benchmark CIS Microsoft Azure Compute Services
50204 Ensure API App redirects all HTTP traffic to HTTPS in Azure App Services Azure Best Practices Policy CIS Microsoft Azure Compute Services
50205 Ensure that API Apps have Incoming Client Certificates is set to On Azure Best Practices Policy CIS Microsoft Azure Compute Services
50256 Ensure that Network Interfaces don't use public IPs CIS Microsoft Azure Foundations Benchmark Azure Best Practices Policy


Existing Azure Controls Added to CIS Microsoft Azure Compute Services Benchmark Policy

CID Title New Policy
50084 Ensure App Service Authentication is set on Function Apps CIS Microsoft Azure Compute Services
50085 Ensure 'HTTPS Only' is set to On for Function Apps CIS Microsoft Azure Compute Services
50086 Ensure Function app has Client Certificates (Incoming client certificates) set to On CIS Microsoft Azure Compute Services
50087 Ensure that Register with Azure Active Directory is enabled on Function apps CIS Microsoft Azure Compute Services
50088 Ensure Function app is using the latest version of TLS encryption version CIS Microsoft Azure Compute Services


Existing Azure Controls Removed from CIS Microsoft Azure Foundations Benchmark Policy

CID Title Removed from Policy
50047 Ensure App Service Authentication is set on web apps CIS Microsoft Azure Foundations Benchmark
50048 Ensure Web app redirects all HTTP traffic to HTTPS CIS Microsoft Azure Foundations Benchmark
50050 Ensure that Register with Entra ID is enabled on Web App CIS Microsoft Azure Foundations Benchmark
50051 Ensure Web app is using the latest version of TLS encryption version CIS Microsoft Azure Foundations Benchmark
50061 Ensure that HTTP Version used for web app is latest CIS Microsoft Azure Foundations Benchmark
50136 Ensure Web App enforces FtpsOnly access to FTP traffic CIS Microsoft Azure Foundations Benchmark
50233 Ensure PHP version is the latest, if used to run the Linux Web App CIS Microsoft Azure Foundations Benchmark
50234 Ensure Python version is the latest, if used to run the Linux Web App CIS Microsoft Azure Foundations Benchmark
50235 Ensure Java version is the latest, if used to run the Linux Web App CIS Microsoft Azure Foundations Benchmark
50240 Ensure Infrastructure double encryption for PostgreSQL Database Server is Enabled CIS Microsoft Azure Foundations Benchmark

Control Title Changes

Control Title Changes for Azure

CID Old Title New Title
50005 Ensure that Microsoft Defender Recommendation for Apply system updates status is Completed Ensure that Microsoft Defender for Cloud is configured to check VM operating systems for updates
50050 Ensure that Register with Entra ID is enabled on App Service Ensure that Register with Entra ID is enabled on Web App
50058 Ensure that Detailed Error Logging is enabled in API Apps Ensure that Detailed Error Logging is enabled for windows API Apps
50061 Ensure that HTTP Version used for web app is latest Ensure HTTP 2.0 is enabled on Web App
50085 Ensure Function app redirects all HTTP traffic to HTTPS Ensure Function App redirects all HTTP traffic to HTTPS in Azure App Services
50089 Ensure that HTTP Version used for Function app is latest Ensure HTTP 2.0 is enabled on Function App
50097 Ensure that Request Tracing is enabled in API Apps Ensure Request Tracing is enabled on Windows API Apps
50136 Ensure FTP deployments are disabled for web apps Ensure Web App enforces FtpsOnly access to FTP traffic
50202 Ensure that FTPS is enforced in API Apps Ensure API App enforces FtpsOnly access to FTP traffic
50204 Ensure that API Apps are only accessible over HTTPS Ensure API App redirects all HTTP traffic to HTTPS in Azure App Services
50206 Ensure that HTTP Logging is enabled in API Apps Ensure Web Server Logging is enabled on Windows API Apps
50233 Ensure that PHP version is the latest, if used to run the web app Ensure PHP version is the latest, if used to run the Linux Web App
50234 Ensure that Python version is the latest, if used to run the web app Ensure Python version is the latest, if used to run the Linux Web App
50235 Ensure that Java version is the latest, if used to run the web app Ensure Java version is the latest, if used to run the Linux Web App
50240 Ensure Infrastructure double encryption for PostgreSQL Database Server is Enabled [Legacy] Ensure Infrastructure double encryption for PostgreSQL Database Server is Enabled
50341 Ensure web sockets are disabled for Azure App Service Ensure Web Sockets are disabled on Web App
50344 Ensure that IP restriction rules are configured for Azure App Service Ensure IP Restriction Rules are configured on Web App

Controls Deprecated

Cloud Provider CID Service Resource Title Policy
Azure 50145 App Service Web App Ensure that Diagnostic logs is enabled in Web apps Azure Best Practices Policy
Azure Infrastructure as Code Security Best Practices Policy
Azure 50168 Cosmos DB Cosmos DB Ensure that Advanced Threat Protection is enabled for all Microsoft Azure Cosmos DB accounts Azure Best Practice policy
Azure Infrastructure as Code Security Best Practices Policy
Azure 50479 App Service Web App Ensure that Remote debugging is set to Off for Web App CIS Microsoft Azure Foundations Benchmark
Azure 50480 App Service Function App Ensure that Remote debugging is set to Off for Function App CIS Microsoft Azure Foundations Benchmark
AWS 419 Cloud Front Cloudfront Distribution Ensure that AWS CloudFront distribution origins do not use insecure SSL protocols AWS Best Practice Policy
AWS IaC Practice Policy
AWS 430 Cloud Front Cloudfront Distribution Ensure the traffic between the AWS CloudFront distributions and their origins is encrypted AWS Best Practice Policy
AWS IaC Practice Policy
AWS 431 Cloud Front Cloudfront Distribution Ensure your AWS Cloudfront distributions are using an origin access identities for their origin S3 buckets AWS Best Practice Policy
AWS IaC Practice Policy

New Tokens

The following section describes the new tokens introduced as part of TotalCloud 2.19.0

TotalCloud Posture tokens

Name Description Example
cloud.resource.prevResult.
value
Use this to filter resources according to their prior control evaluation results. cloud.resource.
prevResult.value: FAIL
cloud.resource.currentResult.
startDate
Use this to find the most recent time when the resource evaluation status was updated to its current state. cloud.resource.
currentResult.startDate:
[now-24h..now]
cloud.resource.firstPassedDate Use this to filter resources based on the time frame of their first passed evaluation. cloud.resource.
firstPassedDate:
[now-24h..now]
cloud.resource.lastPassedDate Use this to filter resources based on the time frame of their last passed evaluation. cloud.resource.lastPassedDate: 
[now-24h..now]
cloud.resource.firstFailedDate Use this to filter resources based on the time frame of their first failed evaluation. cloud.resource.firstFailedDate: 
[now-24h..now]
cloud.resource.lastFailedDate Use this to filter resources based on the time frame of their last failed evaluation. cloud.resource.lastFailedDate:
[now-24h..now]
cloud.resource.prevResult.
startDate
Use this to find resources for which the evaluation status changed from pass to fail, or from fail to pass within the specified time frame. cloud.resource.prevResult.
startDate:[now-30h..now]

TotalCloud Configure tokens

Name Description Example
cloud.accountId Use this to search logs for a specific AWS account ID. scloud.accountId:
123456789012
cloud.region Use this to filter and view scan logs based on the region associated with the AWS account. cloud.region:
us-east-1
cloud.resource.name Use this to filter and view scan logs for a specific resource. cloud.resource.name:
linux system
cloud.resource.type Use this to filter and view scan logs for a specific resource type. cloud.resource.type:
Image
scan.status Use this to filter and view scan logs based on the status of the scan. Example: skipped, pending, completed, failed. scan.status:
completed

AWS AI Services Tokens

These new tokens are introduced as part AWS AI service resources with TotalCloud 2.19.0.

Resource Name Description Example
Bedrock Foundation
Model
foundationModel.arn Use this to filter resources based on their Amazon Resource Name (ARN). foundationModel.arn:
arn:aws:bedrock:eu-west-2::foundation-model/amazon.sampleARN
Bedrock Foundation
Model
foundationModel.
customizationsSupported
Use this to filter resources based on the supported customization type.
Available options are:
(CONTINUED_PRE_TRAINING, DISTILLATION, FINE_TUNING)
foundationModel.customizationsSupported: CONTINUED_PRE_TRAINING
Bedrock Foundation
Model
foundationModel.
inferenceTypesSupported
Use this to filter resources based on the supported inference type.
Available options are:
(INFERENCE_PROFILE, ON_DEMAND, PROVISIONED)
foundationModel.
inferenceTypesSupported:
INFERENCE_PROFILE
Bedrock Foundation
Model
foundationModel.inputModalities Use this to filter resources based on the input modalities.
Available options are:
(IMAGE, SPEECH, TEXT, VIDEO)
foundationModel.inputModalities: IMAGE
Bedrock Foundation
Model
foundationModel.outputModalities Use this to filter resources based on the output modalities.
Available options are:
(EMBEDDING, IMAGE, SPEECH, TEXT, VIDEO)
foundationModel.outputModalities: EMBEDDING
Bedrock Custom
Model
customModel.arn Use this to filter resources based on their Amazon Resource Name (ARN). customModel.arn:
arn:aws:bedrock:eu-west-2::custom-model/amazon.sampleARN
Bedrock Custom
Model
customModel.customizationType Use this to filter resources based on the supported customization type.
Available options are:
(CONTINUED_PRE_TRAINING, DISTILLATION, FINE_TUNING)
customModel.customizationType: CONTINUED_PRE_TRAINING
Bedrock knowledge
Base
KnowledeBases.arn: Use this to filter resources based on their Amazon Resource Name (ARN). KnowledeBases.arn: 
arn:aws:bedrock:eu-west-2::KnowledeBases-model/amazon.sampleARN
Bedrock Knowledge
Base
KnowledeBases.
knowledgeBaseConfigurationType
Use this to filter resources based on the supported customization type.
Available options are:
(KENDRA, SQL, VECTOR)
KnowledeBases.
knowledgeBaseConfigurationType: KENDRA
Sagemaker
Model
sagemakerModel.arn Use this to filter resources based on their Amazon Resource Name (ARN). sagemakerModel.arn::
arn:aws:bedrock:eu-west-2::sagemakerModel-model/amazon.sampleARN

CDR Investigate Tokens

Name Description Example
container.host.name Use this to filter findings by the name of the host running the container container.host.name: 
my-host-name
container.host.ipAddress Use this to filter findings using the IPv4 address of the host. container.host.ipAddress:
XX.XX.XX.XXX
container.host.ipV6Address Use this to filter findings using the IPv6 address of the host. container.host.ipV6Address:
XXXX:X:X:X:XXXX:XXXX:XXXX:XXXX
container.portMapping.
hostIp
Use this to filter findings based on the IP address of the host machine used in container port mapping. container.portMapping.
hostIp:XXX.XXX.XXX.XXX
container.portMapping.
hostPort
Use this to filter findings based on the host computer's port that is mapped to the container's internal port. container.portMapping.
hostPort:XXXXX
container.portMapping.port Use this to filter findings by the internal port exposed by the container. container.portMapping.
port:XXXXX
container.portMapping.
protocol
Use this to filter findings based on the network protocol (e.g., TCP, UDP) used in the port mapping. container.portMapping.
protocol:UDP
asset.truRisk Use this to filter findings based on the TruRisk™ score. asset.truRisk:
60

Issues Addressed

The following issues reported by customers, as well as other notable problems, have been resolved in this release.

Category/Component Issue
CV - Monitor We have fixed the issue where the firstEvaluatedOn token is not working when running a scan to fetch a list of controls, and inconsistent evaluations were observed for AWS controls.
CV - Azure Connector We have fixed the issue where azure connectors were receiving 429 error due to throttling issue.
CV - Reports We have fixed the broken CSV report issue and the problem where downloading the Inventory Report was failing for GCP.
CV - Resources, CV - UI We have fixed the issue where searching with a date range to find when a resource was first evaluated did not work as expected.
CV - Reports, TotalCloud - Portal We have fixed the issue where SCF-related Control Objectives were incorrectly included in reports. Controls under these objectives are now displayed directly under their respective parent requirements as a separate field, across all mandates.
CV - False Positive We have fixed the issue where evaluations were failing for the following control: 50011, 50142, 50075, 50313
CV-False Negative For CID-40092, We have resolved the issue by skipping the Identity Users causing Status Code 429 and such Identity Users will not evaluate.
CV - GCP Connector We have fixed the issue where GCP Zero Touch perimeter scans ran successfully, but the scan titles in the Qweb UI did not reflect the prefix set in the connector settings.
AV - AWS, CV - EC2 Connector We have updated the role creation section for AWS in the connector online help document to provide steps for the creation of a role for cross-account access and External ID.
CV - EC2 Connector We have fixed the issue where the last synced date format was updated as ‘ONMONTH’ without space for all the connector types, and the issue where the TotalCloud AWS connectors gave the error “There was an error during connector execution”.
CV-Resources, CV-UI We have fixed the issue wherein the Inventory failed column showed no data whereas the posture showed failed Inventory types/services.
TotalCloud - UI We have fixed the issues where exceptions were not being populated for resources with tags for the CID 50073.The issues where incorrect references were listed for the CID-50256 and incorrect resources were reported for CID 52122 are also fixed
TotalCloud - UI We have fixed the issues where exceptions were not being populated for resources with tags for the CID 50073.The issues where incorrect references were listed for the CID-50256 and incorrect resources were reported for CID 52122 are also fixed
CV - Control behavior We updated the detection logic of the following controls : 330, 50071, 52122.
CV-Remediation and evidence Clarification We have updated the remediation steps for the following controls 204, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 172, 50047, 50050 50059,50063,50068,50069,50070,50071,50126,50135,50142.
CV-ControlEnhancement We have fixed the issues where Azure controls of APP services needed enhancement: 50084, 50085, 50086, 50087, 50088, 50205, 50049, 50204, 50048, 50051, 50050, 50136, 50235,50234, 50233,50202, 50089,50061, 50147, 50148, 50203, 50058, 50097, 50206, 50344, 50047.
CV-ControlEnhancement We have Enhanced CID-106 and CID-107 to accommodate the pagination and retry mechanism while making an API call through the SDK. Updated the control logic to handle a few edge cases.
CV - UI, Documentation We have fixed the issue where the "AI Powered" tag was shown on all insights.
CV-Policy reference changes We have corrected CIS policy mapping for CID-50256 and CID-50240. The controls was incorrectly mapped to CIS Azure foundation benchmark policy. CID-50256 has now been migrated to Azure Best Practices Policy, and Incorrect CIS reference has been removed from both control.