What is a one sentence summary of your feature request?
Support for South Korean RRN (Resident Registration Number) Validation Algorithm
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
I am writing on behalf of DataSecure, an official partner of Netwrix, to submit a critical feature request regarding data classification capabilities for the South Korean market.
Currently, as an official Netwrix partner preparing for commercial distribution in South Korea, DataSecure is conducting internal testing on sensitive data identification and protection features. During this internal testing phase, we have observed a high rate of false positives when using Regex patterns alone to detect South Korean Resident Registration Numbers (RRNs), due to the lack of a built-in RRN validation algorithm (checksum check).
In the South Korean data security market, a built-in RRN checksum validation functionality is an absolute prerequisite. Without this capability, it is extremely difficult to satisfy local enterprise compliance standards and win competitive deals.
In South Korea, an RRN is a standard 13-digit identifier, but it follows a specific mathematical checksum algorithm on the last digit to verify its legitimacy. Without this validation logic, standard Regex patterns often mistakenly flag other non-sensitive 13-digit numbers (such as order numbers, barcodes, or serial numbers) as RRNs.
To enhance detection accuracy and ensure successful market adoption in South Korea, we strongly request the addition of a built-in “Korean RRN Validation Check” algorithm option to your classification module.
How do you currently solve the challenges you have by not having this feature?
While we currently use Regex patterns to detect Korean RRNs, it generates a high rate of false positives.
