Sensitive Files Exposure Assertion

Applies to ReadyAPI 3.30, last modified on March 24, 2022

The Sensitive Files Exposure assertion checks whether ReadyAPI can access sensitive files by checking the HTTP status code it has got from the server. The list of sensitive files is provided in the configuration of the Sensitive Files Exposure security scan.

The security scan works by replacing parts of the resource path with the file paths specified in the scan configuration. Results depend on the list of status codes specified in the assertion configuration as a list of comma-separated values.

Sensitive Files Exposure Assertion: Scan results

Click the image to enlarge it.

Availability

The assertion is available only in security tests. Use this assertion with the Sensitive Files Exposure security scan.

Create an assertion

Follow these steps:

Security tests: The Assertions panel

Click the image to enlarge it.

  1. Open a security test.

  2. Click Response Assertion next to the Sensitive Files Exposure scan.

  3. Click in the Assertions panel

In the New Assertions dialog, search for the Sensitive Files Exposure assertion or select it manually in the Security category.

Configuration

Sensitive Files Exposure Assertion: Configure the assertion

Click the image to enlarge it.

  • The assertion fails if the server returns one of the status codes specified in the Error codes field (default value: 200).

  • The assertion will return a warning if the server returns one of the status codes specified in the Warning codes field (default value: 401,403).

See Also

Security Assertions
Weak Password Assertion
Sensitive Information Exposure Assertion
Cross Site Scripting Assertion
Basic Authorization Assertion

Highlight search results