Sboxr DOM Documentation
  • Introduction
  • Getting Started
    • Prerequisites
    • Download Sboxr
    • Launch Sboxr
    • Register for Trial Access
    • Activate Subscription
    • Analyzing a Site
  • Finding Issues
  • Viewing Issues
    • Code Execution Issues
      • JSON Source
      • Non-JSON Source
      • Open Execution Details
      • Execution Flow Details
      • Verification and Remediation Advice
      • Duplicate Tainted Sources
    • Cryptographic Issues
    • JS Code Issues
      • View Cross-Origin Code
      • View Same-Origin Code
      • View All Code
      • View Code by Origin
    • Communication Issues
      • Cross-window Messaging Broadcasts
      • Cross-site Communications
      • Same-Origin Communications
      • All Communications
    • Data Leakage Issues
      • Sensitive Data Leakage
      • Non-sensitive Data Leakage
      • Non-sensitive Data leaked via Referrer header
      • All Data Leakage
      • All Data Leaked via Referrer header
    • Data Storage Issues
      • Sensitive Data Stored
      • Non-sensitive Data Stored
      • All Data Stored
  • View Live Event Stream
  • Event Location Details
    • Code Details
    • Window Details
  • Save/Reload Session Data
  • Troubleshooting FAQ
Powered by GitBook
On this page

Was this helpful?

  1. Viewing Issues
  2. Data Leakage Issues

Sensitive Data Leakage

Sensitive Data Leakage (refresh page to view from start)

Sboxr uses a set of patterns to classify the monitored data as sensitive. It looks at both the parameter name as well as the parameter value to make this determination.

For example, a parameter named email as well as a parameter with value in the format of an email address will be marked as sensitive by Sboxr.

PreviousData Leakage IssuesNextNon-sensitive Data Leakage

Last updated 5 years ago

Was this helpful?