spec 1 linked patterns checked
OWASP MASTG: Checking for Sensitive Data Disclosure Through the User Interface
Supports testing whether application UI components disclose sensitive information, including values that should be protected from unnecessary display or leakage.
Read with a purpose
What this source can teach
Use this source to check a technical or accessibility requirement against its exact wording and scope.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Sensitive-data reveal | Choose sensitive-data reveal when a normally masked or redacted value needs a deliberate temporary reveal, hide, peek, copy, partial reveal, reauthentication, or audited access path. | The value is masked by default unless the user is actively entering it and the platform-specific control intentionally permits display. | Supports checking whether sensitive information is disclosed through application UI components. |
Comparisons supported by this source
- Sensitive-data reveal vs password input vs input mask vs typed confirmation vs permission request
Supports testing for sensitive information disclosure through UI components.
Evidence Role
This source is treated as spec evidence. Its value comes from the specific claims and setting described above.
Publisher: OWASP Foundation. Last checked: .