Skip to main content
Skip table of contents

Data Patterns

Overview

image-20240714-055258.png

Administrator > Discovery > Discovery Management > Data Patterns

  • The Data Patterns section provides a list of patterns used for scanning. Predefined patterns are available for convenience, and custom patterns can be created by entering desired regular expressions.

  • Built-in (predefined) patterns cannot be viewed, modified, or deleted.

  • There are two types of patterns based on their purpose:

    • for data: This pattern is used for scanning data. It searches the content of specific columns. If you want to accurately identify sensitive information, you should use this type of pattern.

    • for keyword: This pattern is used for scanning metadata. It is useful when you want to quickly scan path names. For example, if the administrator already knows which columns might contain sensitive data, using a keyword pattern to search only the column names can help reduce scanning time and load.

  • AI Identifier: A trained AI model that can detect sensitive data.

    • Address - Korea: Korean address.

    • Country code - ISO 3166-1 alpha-2 and ISO 3166-1 alpha-3: Country codes consisting of 2 to 3 alphabetic characters.

    • Disease name - Korean: Disease names written in Korean.

    • Job Title - Korean: Job titles written in Korean.

    • License / Certificate - Korean: License or certificate names written in Korean.

    • Name - Korean: Personal names written in Korean.

    • Romanized name - Korean: Romanized Korean names

Creating a Custom Data Pattern

  • To add a custom pattern, click the + Data Pattern button at the top of the pattern list.

  • Regular Expression Purpose: Specify the purpose of the pattern as either for data or for keyword.

    • Both for data and for keyword have different regular expression input formats.

  • Registering Regular Expressions

    image-20240730-212418.png

    for data / for keyword

    For data, since it performs exploration on data, a regular expression capable of detecting actual data is required.
    For keyword, since it only explores metadata such as path names, you simply input text and specify detection conditions for the designated text.

    • Regular expression: Enter the regular expression needed for detection. For keyword, you can either directly input the regular expression or use the method of inputting text and specifying conditions.

    • Text to Test: Enter a string to check if the regular expression works properly.

    • Matched Text: If the string entered in Text to Test is detected by the regular expression, it will be highlighted.

  • Sensitive Item: Select the type of sensitive information detected by the regular expression. This is a mandatory field, so you must select at least one sensitive information type that matches the regular expression.

    image-20241031-120707.png

    Specify Matched Sensitive Item

  • Types of Sensitive Items: Specify the type of sensitive information associated with the selected item. This is optional and does not need to be entered.

    Related Compliance: Specify any compliance regulations related to the sensitive information. This is optional and does not need to be entered.

    Data Pattern Name: Specify a recognizable name for the pattern to aid in identification.

    Description: Provide a description of the pattern. It is recommended to enter detailed information to make it easier to review when adding it to the Detection Profile.

Editing and Deleting Custom Patterns

  • Editing Custom Patterns: In the data pattern list, you can click on a specific custom pattern row to view and modify its settings. Built-in patterns cannot be viewed or edited.

    Deleting Custom Patterns: You can select a specific custom pattern and click the Delete button to remove it. Built-in patterns cannot be deleted.

    image-20241031-121800.png

    Delete Custom Pattern

If a custom pattern is linked to a Detection Profile, it cannot be deleted. To delete it, first remove the custom pattern from any associated profiles.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.