The Sensitive Information Exposure assertion checks whether the last message received exposes sensitive information about the target system. For example, if the response gives away the database version in the error message, a hacker can use this information to exploit known database security issues.
This assertion is applicable to REST, GraphQL, SOAP, and HTTP test steps.
Availability
This assertion is available in multiple ReadyAPI applications. Depending on the application, it validates the following data:
| In... | Checks... | To learn more... |
|---|---|---|
| Functional tests | The response. | See Working With Assertions in Functional Tests. |
| Security tests | The response. | See Security Assertions. |
Create an assertion
Follow these steps:
Click the image to enlarge it.
-
Open a test step.
-
Click Add assertion.
In the New Assertions dialog, search for the Sensitive Information Exposure assertion or select it manually in the Security category.
Follow these steps:
Click the image to enlarge it.
-
Open a security test.
-
Click Response Assertion next to any scan.
-
Click
in the Assertions panel
In the New Assertions dialog, search for the Sensitive Information Exposure assertion or select it manually in the Security category.
Setting up properties
-
To create sensitive information token, click
. Specify the token name and description in subsequent dialogs.
Click the image to enlarge it.
To remove the token from the list, click
. -
To let the assertion get the project-level sensitive information, select the Include project specific sensitive information configuration check box.
Note: The list of default tokens is available on the Global Sensitive Information Tokens page of Preferences.
Other Security Assertions
Add more assertions to ensure the security of the tested service:
See Also
Security Assertions
Weak Password Assertion
Sensitive Files Exposure Assertion
Cross Site Scripting Assertion
Basic Authorization Assertion