Home
AppScan Presence
An AppScan Presence on your server enables you to scan sites not accessible from the Internet, and to incorporate scanning as part of your functional testing.
Legacy AppScan Presence
This section describes the legacy version of the AppScan Presence, V1. This version will be supported only until October 1, 2022.
Starting the legacy Presence

AppScan Presence
An AppScan Presence on your server enables you to scan sites not accessible from the Internet, and to incorporate scanning as part of your functional testing.
- System requirements
- Creating the Presence
  For private web apps, or for including a scan as part of your functional testing procedure, you must create an AppScan Presence, with access to the web app or back-end server, and to the Internet. Proxy connections are supported.
- Starting the Presence
- Configuring Private Site Server proxy
  If your private network requires the Private Site Server to use a proxy to connect with the web app or back-end server (internal proxy), or with the Internet (outgoing proxy), configure it as follows.
- Configuring a PAC file
  If a proxy auto-config (PAC) file is required in order to reach the various domains in your site, configure the AppScan Presence as follows.
- Renewing the Presence key
  When you originally download the presence, it includes a key to activate it. When that key expires, you must replace it with a valid key.
- Log files
- Upgrading to the new AppScan Presence
  If you already have a V1 AppScan Presence installed and you want to upgrade to V2, follow these instructions.
- Legacy AppScan Presence
  This section describes the legacy version of the AppScan Presence, V1. This version will be supported only until October 1, 2022.
  - System requirements for the legacy Presence
  - Creating the legacy Presence
    For private web apps, or for including a scan as part of your functional testing procedure, you must create an AppScan Presence, with access to the web app or back-end server, and to the Internet. Proxy connections are supported.
  - Starting the legacy Presence
  - Activating the Proxy Server
    To use the Proxy Server in the AppScan Presence, you must activate it, and configure the port.
  - Using the Proxy Server
    You can use the AppScan Presence Proxy Server to record traffic, save it as a DAST.CONFIG file, and import it to run an ASoC scan. You can optionally encrypt this file, as described in a sub-section below.
  - Configuring Private Site Server proxy (legacy Presence)
    If your private network requires the Private Site Server to use a proxy to connect with the web app or back-end server (internal proxy), or with the Internet (outgoing proxy), configure it as follows.
  - Configuring a PAC file (legacy Presence)
    If a proxy auto-config (PAC) file is required in order to reach the various domains in your site, configure the AppScan Presence as follows.
  - Renewing the Presence key (legacy Presence)
    When you originally download the presence, it includes a key to activate it. When that key expires, you must replace it with a valid key.

Starting the legacy Presence

About this task

Important: For Linux systems the shell script must have execute permissions. Use chmod +x startPresence.sh, or

chmod +x
startPresenceAsService.sh

Procedure

Locate and run:

Linux™, to start Presence as a process: startPresence.sh
Linux™, to start Presence as a service (sudo password required): startPresenceAsService.sh start The service name is presenceService.
Windows™, to start Presence as a process: startPresence.exe
Windows™, to start Presence as a service: startPresenceAsService.exe start The service name is presenceService You can display the logs by running: "startPresenceAsService.exe displayLogs"

Restriction: You cannot run the Presence as a process and a service on the same machine: after running it as a service you cannot run it as a process until you delete the service.