Skip to main content

Content Security Management

Content Security Management

The entry point for content security management is shown below:

Sensitive Word Management​

The sensitive word management feature helps users effectively control platform content, ensuring compliance, healthiness, and alignment with internal corporate policies or community management standards. By defining sensitive words, the system can intelligently identify and intercept them during content creation, display, or storage stages, preventing the spread of sensitive information.

Feature Highlights​

  • Supports batch import and export, facilitating centralized management of large volumes of sensitive words
  • Flexible status control, allowing each sensitive word to be individually enabled or disabled
  • Supports description information, making it easier to record the background and purpose of sensitive word settings
  • Import template validation mechanism, preventing format errors or duplicate entries during import

Adding New Sensitive Words​

Users can manually add one or multiple sensitive words by following these steps:

  1. Navigate to: Content Security Management > Sensitive Words > New
  2. Fill in the following information in the pop-up window:
    • Sensitive Word: e.g., terrorism
    • Enable Status: select Enable or Disable
    • Description (optional): additional notes on the background of adding the sensitive word
  3. Click Save, the sensitive word will take effect immediately or be reserved for later use (depending on the enable status)

Download Import Template​

To facilitate batch management of sensitive words, the system provides a unified import template. The steps are as follows:

  1. Navigate to: Content Security Management > Sensitive Words > Download Template
  2. The system will automatically download an Excel file, named by default: Sensitive_Words_Import_Template.xlsx
  3. Open the template file and fill in the following fields:
    • Sensitive Word (required)
    • Enable (Yes / No)
    • Description (optional)
  4. Save the completed file for import use

Import Sensitive Words​

After preparing the sensitive word template, batch import can be performed as follows:

  1. Navigate to: Content Security Management > Sensitive Words > Import
  2. Click the upload area or drag and drop the template file to upload
  3. The system will automatically validate the content (field completeness, format, duplicates, etc.)
  4. Upon successful import, a "Upload Successful" message will appear, and the new sensitive words will be displayed in the list

⚠️ It is recommended to perform a small batch test first to ensure the format is correct before bulk importing

Export Sensitive Words​

The platform supports exporting all sensitive words as an Excel file. The steps are as follows:

  1. Navigate to: Content Security Management > Sensitive Words > Export
  2. Click Export, and the system will automatically download a .xlsx file, named by default: Sensitive_Words_Report.xlsx
  3. The report includes the sensitive word itself, enable status, and description information, facilitating archiving and sharing

Content Review Model​

Confidence usually refers to the degree of certainty a model or system has about its prediction results.

In the context of content review models, the confidence threshold setting is an important feature that allows users to define the minimum confidence level the model must reach before marking content as a specific category (such as spam, inappropriate content, etc.). This helps reduce false positives or false negatives depending on the threshold setting.

For example, if the confidence threshold is set to 0.8, the model will only mark content as inappropriate if it is at least 80% confident in its prediction. This ensures that only cases the model is very sure about will be acted upon.

⚠️ This section is currently under development. Stay tuned.

PII Detection and Masking​

💡 Note: This feature is only supported in version V4.1 and above

PII (Personally Identifiable Information) detection and masking functionality is used to identify and protect data that may expose personal privacy. The system supports identifying various types of data that can uniquely identify an individual, either alone or combined with other information. Its core purpose is to ensure data security and privacy compliance.

Global Configuration​

Interface Description
In the "Admin Console," navigate to [Content Security Management > PII Detection and Masking > Global Configuration] to set unified PII detection policies across the platform.

Configuration Items Description

  • Automatic PII Detection and Masking:
    • Platform-level switch, enabled by default.
    • When enabled, the system automatically identifies personal privacy information (such as names, phone numbers, emails, ID numbers, etc.) during Agent interactions and data processing, and performs masking.
    • If disabled, all PII detection will be inactive.
  • Agent Whitelist:
    • Specific Agents can be added to the whitelist.
    • Agents on the whitelist will bypass PII detection and masking processes, but all operations will be recorded in audit logs to ensure security and traceability.

Operation Instructions

  • Select Agents to exclude from detection in the "Agent Whitelist" dropdown;
  • Toggle the "Automatic PII Detection and Masking" switch to enable or disable global detection;
  • Click Save, and the configuration takes effect immediately.

Functionality

  • Automatically identify and mask sensitive personal information to prevent privacy leaks;
  • Support flexible configuration to meet privacy policies in different business scenarios;
  • Audit logs trace all configuration changes, ensuring security, compliance, and control.

Masking Rule Configuration​

💡 Note: This feature is only supported in version V4.1 and above

Feature Description

"Masking Rule Configuration" is used to define the system's handling strategies when detecting personal sensitive information (PII). By setting different rules and policies, administrators can flexibly control how the system identifies, prompts, and masks sensitive data, ensuring data compliance and privacy security.

Page Description

The page displays all masking rules configured in the system, including the following information:

  • Rule Type: distinguishes between system built-in (preset) rules and user-defined rules.
  • Rule Name: the type of sensitive information the rule detects, such as ID number, phone number, email, etc.
  • Rule Content: regular expressions or detection logic used to match sensitive information.
  • Enable Status: controls whether the rule is active.
  • Masking Policy: the action the system performs when sensitive information is matched, selectable from "Mask," "Prompt," "Terminate," "Delete," etc.
  • Update Time: the most recent update time of the rule.
  • Actions: supports editing or deleting the rule.

Configuration Steps

  1. Add Custom Rule

    • Click the "Add Custom Rule" button at the top right of the page;
    • In the pop-up window, fill in the following:
      • Rule Name: name the rule, e.g., Bank Card Number Detection;
      • Rule Content: enter the regular expression used to identify this type of information;
      • Enable Status: enable immediately or leave disabled as needed;
      • Masking Policy: select the masking method from the dropdown (e.g., "Mask", "Prompt", "Terminate", "Delete");
    • Click "Save" after completion, and the rule will take effect.

  2. Custom User Prompt

    • When the masking policy is set to "Prompt," click "Custom User Prompt" at the top right to set the prompt message;
    • Example: "Your input contains ID information, do you want to continue?";
    • After saving, when users trigger this rule, the system will pop up a confirmation prompt.

  3. Rule Management

    • Rules can be edited at any time to modify content or policies;
    • Unneeded rules can be deleted by clicking "Delete."

Usage Example

The system presets common sensitive information rules (such as ID numbers, Mainland China mobile numbers, etc.), which administrators can enable directly; custom rules can also be added according to business scenarios, such as detecting emails, bank card numbers, or other specific data formats.