Log desensitization

Automatically recognize and replace sensitive information in logs, supporting IP addresses, mailboxes, cell phone numbers, ID cards, bank cards, MAC Address. All processing is done locally and data will not be uploaded on the server.

IPv4 Address IPv6 Address Mailbox Cell phone number ID number Bank card number MAC Address

Enter Log

Dissensitization results

Advertising

What's a journal de-sensitization? Why is it so important?

Logs are an important tool in the day-to-day software development and transport process for the sorting of issues. However, the logs often contain a large amount of sensitive information: the true user IP Address, log-in mailbox, cell phone number, even ID and bank card information. Once these log documents are improperly shared or leaked, the privacy and property security of users are directly jeopardized.

Sensitive information types common in logs

IP Address : Accurate exposure of users' geographic location and network behaviour
E-mail : user identification, highly vulnerable to fishing attacks
Cell phone number. : related true identity, usable for harassment or fraud
ID number : highly sensitive personal privacy information, with serious consequences of leakage
Bank card number : financial information, which may lead to loss of direct property
MAC Address : unique device identifier to track user equipment

Practical application of de-sensitization tools

1. Sharing of the barrier log to third parties
User-sensitive information must be removed from the production environment log when you need to share it with external suppliers or communities for help.

2. Log archive and long-term storage
According to regulations such as the GDPR, the Personal Information Protection Act, long-term stored logs must be dissensitized and only necessary information retained.

3. Development of testing environment use
Logs exported from the production environment need to be dissensitized to protect the privacy of the true user before being used for testing.

4. Security audits and compliance
Safety audits in the financial and medical sectors require that the journal should not contain explicit and sensitive information.

All the processing of this tool is done locally in the browser, and the data is not uploaded to any server, so that you can handle the logs containing real and sensitive information.

How to use log de-sensitization tools

Use this tool very simple: Desensitive log content will be required to paste to the left input box, tick the type of information that needs to be desensitive, click on the "desensitive" button, and the right side will display the result of the process. Once processed, you can copy it directly or pass it through a shared link.

De-sensitization rule description

IPv4 : first paragraph retained and the rest replaced ***
IPv6 Replace with ****:****:****:****
Mailbox : Save the first and end characters and replace them with ***
Cell phone number : retain first three and last four places, replace ****
ID card : retain first six and last four places, replace middle with ****
Bank card : retain the first four and the last four and replace the middle with **** ****

Common Question Answers

Q: Can post-sensitization logs also be used to sort out problems?
A: Yes. De-sensitization replaces only user privacy information, and error stacks, time stamp, status code etc. are kept in full.

Q: Will regular expressions be misjudged?
A: We use strict rules of due process, but there may still be very few miscalculations, suggesting simple verification of output results.

Q: How much log files are supported for processing?
A: This tool is a pure front-end processing process, and it is recommended that log content not exceeding 5MB be processed in a single instance, and that super-sized documents be processed in batches.