Home
DAST
AppScan on Cloud performs security scans for web-applications for production, staging and development environments. For development environments it is aided by Private Site Scanning technology to scan applications not accessible to the open Internet.
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.
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.

Welcome
Welcome to the documentation for HCL AppScan on Cloud.
Getting started
Security is about protecting your valuable assets. Some of the most important assets your organization owns are in the form of information, such as intellectual property, strategic plans, and customer data. Protecting this information is critical for your organization to continue to operate, be competitive, and meet regulatory requirements.
Navigation
This section describes the items on the main ASoC menu bar, and links to more detailed information.
Administration
Define users, applications, policies, and configure DevOps integrations.
DAST
AppScan on Cloud performs security scans for web-applications for production, staging and development environments. For development environments it is aided by Private Site Scanning technology to scan applications not accessible to the open Internet.
- Dynamic (DAST) scanning
  ASoC can perform dynamic analysis of an application that runs in a browser or a web API. Use the configuration options available in ASoC, or upload an AppScan Standard configuration (template file) or a full scan file.
- 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
  - Upgrade to AppScan Presence V2
    AppScan Presence V1 was deprecated in October 2022. If you have a V1 AppScan Presence installed and you want to upgrade to V2, follow these instructions.
- AppScan Traffic Recorder
  The AppScan Traffic Recorder (DAST proxy) enables you to record traffic to use as Explore data. Traffic Recorder instances can be created on demand to record traffic that will later be used for a DAST scan.
- Private sites
  An AppScan Presence on your server enables you to scan sites not accessible from the Internet.
IAST
Using an agent installed on your application, ASoC identifies security vulnerabilities in your app during runtime, by monitoring all interactions, both legitimate and malicious. The process is "passive", in the sense that IAST does not send its own tests, and can therefore run indefinitely.
Static analysis
Use static analysis (SAST) to scan for security vulnerabilities in web and desktop applications. Static analysis includes Intelligent Finding Analytics (IFA) and Intelligent Code Analytics (ICA).
Results
The Scan History tab of your application displays your scan results (including scan statistics) and rescan options.
Troubleshooting
If you experience problems with this service, you can perform these troubleshooting tasks to determine the corrective action to take.
FAQ & Reference
Frequently asked questions, information about integrating ASoC into the product lifecycle (SDLC), and ASoC API documentation.

Creating the AppScan 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.

About this task

This service is not available with the Free plan.

Private network — Figure 1. Scanning a secure network

For details of how private site scanning works "under the hood", refer to Understanding Private Site Scanning

Procedure

Click Main > AppScan Presence Create Presence .
At the Name your presence screen, enter a unique name for the AppScan Presence and click Next.
At the Download presence screen, select the network's operating system (Linux™ or Windows™), then click Download and save the compressed file.
Click Done.

The new presence is added to the list of presences, with Status: "Inactive", and the Key Expiry Date.
Extract the Presence files, and save them on a computer in the same network as your site. The computer must have access to the site and to the Internet.
If the Presence needs to connect to the app or Internet by proxy, Configuring a Private Site Server proxy for the Presence.
Starting the AppScan Presence.