Azure IoT connection string

  • Článek

#This SIT is also included in the All credentials bundled SIT.

Format

The string HostName followed by the characters and strings outlined in the pattern below, including the strings azure-devices.net and SharedAccessKey.

Tip

If you're not an E5 customer, use the 90-day Microsoft Purview solutions trial to explore how additional Purview capabilities can help your organization manage data security and compliance needs. Start now at the Microsoft Purview compliance portal trials hub. Learn details about signing up and trial terms.

Pattern

  • the string HostName
  • zero to two whitespace characters
  • an equal sign (=)
  • zero to two whitespace characters
  • any combination of between 1-200 lower- or uppercase letters, digits, symbols, special characters, or spaces
  • the string "azure-devices.net"
  • any combination of between 1-200 lower- or uppercase letters, digits, symbols, special characters, or spaces
  • the string SharedAccessKey
  • zero to two whitespace characters
  • an equal sign (=)
  • zero to two whitespace characters
  • any combination of 43 lower- or uppercase letters, digits, forward slash (/), or plus sign (+)
  • an equal sign (=)

Credential example

HostName=account.azure-devices.net;SharedAccessKeyName=key;SharedAccessKey=abcdefghijklmnopqrstuvwxyz0123456789/+ABCDE=

Checksum

No

SITs that have checksums use a unique calculation to check if the information is valid. This means when the Checksum value is Yes, the service can make a positive detection based on the sensitive data alone. When the Checksum value is No additional (secondary) elements must also be detected for the service to make a positive detection.

Keyword Highlighting

Supported

When keyword highlighting is supported in the contextual summary for a sensitive information type or a trainable classifier, in the Contextual Summary view of activity explorer, the keywords in a document that were matched to a policy are highlighted.

Definition

A DLP policy has high confidence that it's detected this type of sensitive information if, within a proximity of 300 characters:

  • The regular expression CEP_Regex_AzureIoTConnectionString finds content that matches the pattern.
  • The regular expression CEP_CommonExampleKeywords doesn't find content that matches the pattern.
<!--Azure IoT Connection String-->
<Entity id="0b34bec3-d5d6-4974-b7b0-dcdb5c90c29d" patternsProximity="300" recommendedConfidence="85">
  <Pattern confidenceLevel="85">
        <IdMatch idRef="CEP_Regex_AzureIoTConnectionString" />
        <Any minMatches="0" maxMatches="0">
            <Match idRef="CEP_CommonExampleKeywords" />
        </Any>
  </Pattern>
</Entity>

Keywords

CEP_common_example_keywords

This sensitive information type identifies these keywords by using a regular expression, not a keyword list.

  • contoso
  • fabrikam
  • northwind
  • sandbox
  • onebox
  • localhost
  • 127.0.0.1
  • testacs.com
  • s-int.net