eye-slashRedact sensitive data

Redact Sensitive Data (with Custom HTML Attribute and Regex Patterns)

BetterBugs.io enables you to prevent sensitive information from being captured or shared while creating bug reports with screenshots, screen recordings, or Rewind sessions.

You can configure BetterBugs.io to do this in multiple ways. For this, you have the following options

  • Custom HTML Attribute for Blurring Information — Adding data-betterbugs=”ignore” to your web page HTML element blurs out those elements before taking screenshots or recording screens or when using Rewind.

  • Redact Data with Regex Patterns — Adding default or custom regex patterns first globally identifies the defined key/value pairs in the technical information getting captured (while creating bug reports). Then, the corresponding values get redacted and replaced with “[*** REDACTED BY BETTERBUGS FOR PRIVACY ***]” from your bug reports.

Custom HTML attribute for blurring information

Before creating a report, you need to add the data-betterbugs=”ignore” HTML attribute to your application web page(s) elements to exclude them from getting captured.

You can use this to blur out DOM elements. This means adding the attribute to the DOM elements would prevent them from getting recorded.

Using data-betterbugs=”ignore” HTML attribute in your source code

To use the feature, just add the attribute in your HTML source code for selecting the desired element(s) to be ignored during screenshots, screen recordings, or Rewind sessions.

Here’s what it looks like:

Adding HTML Attribute to Your Web Page(s)

You're good to go.

Redact data with regex patterns

You can easily add regular expressions (REGEX) to BetterBugs.io for it to redact/remove sensitive data or prevent information from getting captured.

shield-checkSteps to Add Custom Regex Patterns

How It Works

Once you add the specific regex, when you create a report, BetterBugs.io stringifies the technical details captured during the screen capturing (screenshot, screen record, or Rewind) session object and processes it with the saved regex patterns before the report uploads.

This prevents the pre-defined sensitive information, such as authentication headers, access tokens, emails, passwords, card numbers, CVV, and API keys, from being accidentally shared along with the bug reports.

circle-info

The system avoids overwriting critical fields like titles, descriptions, or metadata unless specified by the regex patterns. Besides this, BetterBugs.io shows a preview of the data after redaction, allowing you to verify and adjust regex patterns as needed.

For instance, if a network request (being captured) in your bug report contains a sensitive user email ID, with the pre-applied regex pattern, BetterBugs.io redacts it automatically while getting shared.

This means instead of the actual email ID for the key/pair value in the request/response/payload object, BetterBugs.io replaces it with “[*** REDACTED BY BETTERBUGS FOR PRIVACY ***]” as the value in the result object.

EXAMPLE

Original JSON Object before capturing:

Redacted JSON result with the pre-applied REGEX after capturing:

Use cases: Redact data with regex

Here’s how it’s commonly used:

  • Data Privacy Management — You can define multiple regex patterns in the settings to redact sensitive data before uploading. BetterBugs.io comes with predefined regex patterns for common sensitive data types like authentication headers, access tokens, emails, passwords, card numbers, CVV, and API keys. You can view unredacted data before uploading and verify redaction after uploading sensitive data.

  • Customizable Redaction — You can modify the regex patterns to fit your application's specific requirements. Redaction is applied only to sensitive data, and other intentionally added data remains unaltered.

Last updated