Microsoft Defender for Azure Cosmos DB

Hi!

Microsoft Defender for Azure Cosmos DB is now generally available (GA) and supports SQL (core) API account types.

This new release to GA is a part of the Microsoft Defender for Cloud database protection suite, which includes different types of SQL databases, and MariaDB. Microsoft Defender for Azure Cosmos DB is an Azure native layer of security that detects attempts to exploit databases in your Azure Cosmos DB accounts.

Alerts:

Alert (alert type)DescriptionMITRE tactics
(Learn more)
Severity
Access from a Tor exit node
(CosmosDB_TorAnomaly)
This Azure Cosmos DB account was successfully accessed from an IP address known to be an active exit node of Tor, an anonymizing proxy. Authenticated access from a Tor exit node is a likely indication that a threat actor is trying to hide their identity.Initial AccessHigh/Medium
Access from a suspicious IP
(CosmosDB_SuspiciousIp)
This Azure Cosmos DB account was successfully accessed from an IP address that was identified as a threat by Microsoft Threat Intelligence.Initial AccessMedium
Access from an unusual location
(CosmosDB_GeoAnomaly)
This Azure Cosmos DB account was accessed from a location considered unfamiliar, based on the usual access pattern.

Either a threat actor has gained access to the account, or a legitimate user has connected from a new or unusual geographic location
Initial AccessLow
Unusual volume of data extracted
(CosmosDB_DataExfiltrationAnomaly)
An unusually large volume of data has been extracted from this Azure Cosmos DB account. This might indicate that a threat actor exfiltrated data.ExfiltrationMedium
Extraction of Azure Cosmos DB accounts keys via a potentially malicious script
(CosmosDB_SuspiciousListKeys.MaliciousScript)
A PowerShell script was run in your subscription and performed a suspicious pattern of key-listing operations to get the keys of Azure Cosmos DB accounts in your subscription. Threat actors use automated scripts, like Microburst, to list keys and find Azure Cosmos DB accounts they can access.

This operation might indicate that an identity in your organization was breached, and that the threat actor is trying to compromise Azure Cosmos DB accounts in your environment for malicious intentions.

Alternatively, a malicious insider could be trying to access sensitive data and perform lateral movement.
CollectionHigh
Suspicious extraction of Azure Cosmos DB account keys (AzureCosmosDB_SuspiciousListKeys.SuspiciousPrincipal)A suspicious source extracted Azure Cosmos DB account access keys from your subscription. If this source is not a legitimate source, this may be a high impact issue. The access key that was extracted provides full control over the associated databases and the data stored within. See the details of each specific alert to understand why the source was flagged as suspicious.Credential Accesshigh
SQL injection: potential data exfiltration
(CosmosDB_SqlInjection.DataExfiltration)
A suspicious SQL statement was used to query a container in this Azure Cosmos DB account.

The injected statement might have succeeded in exfiltrating data that the threat actor isn’t authorized to access.

Due to the structure and capabilities of Azure Cosmos DB queries, many known SQL injection attacks on Azure Cosmos DB accounts cannot work. However, the variation used in this attack may work and threat actors can exfiltrate data.
ExfiltrationMedium
SQL injection: fuzzing attempt
(CosmosDB_SqlInjection.FailedFuzzingAttempt)
A suspicious SQL statement was used to query a container in this Azure Cosmos DB account.

Like other well-known SQL injection attacks, this attack won’t succeed in compromising the Azure Cosmos DB account.

Nevertheless, it’s an indication that a threat actor is trying to attack the resources in this account, and your application may be compromised.

Some SQL injection attacks can succeed and be used to exfiltrate data. This means that if the attacker continues performing SQL injection attempts, they may be able to compromise your Azure Cosmos DB account and exfiltrate data.

You can prevent this threat by using parameterized queries.
Pre-attackLow
Maxime.

Démarrez une conversation

Votre adresse e-mail ne sera pas publiée. Les champs obligatoires sont indiqués avec *