These docs are for v1.1. Click to read the latest docs for v1.2.

.HAR file

An HTTP Archive File (.HAR file) is a recorded session of user interaction with an application. The .HAR file keeps all the HTTP requests and responses between the web client and web application.

You can use a pre-recorded .HAR file when running a security scan. Using the data contained in the .HAR file, Bright defines the attack surface and ensures complete coverage of the scan scope. To run a scan with a .HAR file, in the Recording Session section, you need either to upload a file from a disk or use a file previously uploaded to the Bright storage.



When using third-party QA automation tools, use HAR format to save session files.



When using a pre-uploaded file, make sure this user has an access to the project and appropriate permissions to operate with it. For more, see Managing Organization Users.

You can create a .HAR file using either specialized tools or common web browsers. See Creating a HAR File to learn how to record an interaction session and review the generated .HAR file.



Authentication coverage - To ensure complete coverage of the scan, you should configure an authentication object so that the Bright engine can reach the authenticated parts of the target application. See Managing Your Authentications for detailed information.

HAR upload limits - A single .HAR file is limited to 500 Mb, but you can upload multiple files for larger targets.

Deeper coverage. You can enable Bright to switch between the microservers during scanning if the relative data is recorded in the HAR file. Bright uses all the recorded data to define the attack surface. Therefore, it can reach every part of your application covered by the HAR file.Less automation. You have to create a HAR file on every new part of the application you want to scan. It may be a problem for large development teams where the engagement process is quite complicated.
Scope control. The scan covers exactly the same scope of the target as recorded in the HAR file (determined by a user). Therefore, Bright can run a scan only for a new part, instead of scanning the whole application on every build.



You can combine full automation with complete coverage by applying both the Crawler and Recorded (HAR) discovery types for a scan.

What’s Next