Creating a new scan from a scan file
You can upload your own AppScan Standard scan
(SCAN) file to run an ASoC scan.
Before you begin
- Back up your site before scanning.
- If you have not yet done so, Create an application for your scans.
- Verify to ASoC your permission to scan the domain (see Verifying a domain)
- If your site is not available on the Internet, and an AppScan Presence does not yet exist on the server: Creating the AppScan Presence.
- When configuring a scan in AppScan Standard that requires an OTP, you must use action-based login, not request-based login. See the AppScan Standard documentation for details.
CAPTCHA login is supported only when it is configured in
AppScan Standard and uploaded in a scan
(SCAN) or template (SCANT) file. For configuration
instructions, see CAPTCHA authentication in AppScan Standard.
For applications that use Google reCAPTCHA v2, ask the site owner to configure Google's reCAPTCHA v2 test keys in the UAT or staging environment. Use test keys only in test environments, never for production traffic. IP allowlisting alone might not prevent reCAPTCHA v2 from blocking the scan or leaving the verification widget loading indefinitely.
If the scan file uses advanced encryption, prepare it for the target ASoC environment before uploading it. See Using files with advanced encryption.