Welcome
Management
Define users, roles, groups, applications, policies, and configure DevOps integrations.
DevOps
Tools for incorporating ASoC in your software development lifecycle.
REST API
The built-in REST API interface provides you with a way to visualize RESTful web services. The API documentation is built using Swagger, where you can test API operations and instantly view the results to help you scan your applications faster.
Generating API Keys
Use a Key ID and Key Secret to access the AppScan on Cloud REST APIs and to log in from some of the ASoC client tools (for example, from the Jenkins plug-in and from the Static Analyzer Command Line Utility and IDE plug-ins).

Getting started
Welcome to the documentation for HCL AppScan on Cloud, where you can find information about how to install, maintain, and use this service.
Navigation
This section describes navigating AppScan on Cloud, including items on the side main menu and top navigation bars, with links to more detailed information.
Management
Define users, roles, groups, applications, policies, and configure DevOps integrations.
- Working with applications
  An application is a collection of scans related to the same project. It can be a web site, a desktop app, a mobile app, a web service, or any component of an app. Applications enable you to asses risk, identify trends, and make sure that your project is compliant with industry and organization policies.
- DevOps
  Tools for incorporating ASoC in your software development lifecycle.
  - REST API
    The built-in REST API interface provides you with a way to visualize RESTful web services. The API documentation is built using Swagger, where you can test API operations and instantly view the results to help you scan your applications faster.
    - Technical overview of REST API upgrade to v4
      Version 4.0 of the REST API brings a host of enhancements, optimizations, and improvements over the previous version (v2). API v4 maintains compatibility by using the same access token as v2, facilitating a gradual migration of your code to v4 while continuing to use the existing token. Notably, the path prefix for API v4 has changed from "/api/v2" to "/api/v4/". While many functions retain their names and models, ensuring a straightforward transition from "v2" to "v4," some functions have undergone modifications. This topic serves as a technical guide, outlining the primary changes introduced in API v4.
    - Generating API Keys
      Use a Key ID and Key Secret to access the AppScan on Cloud REST APIs and to log in from some of the ASoC client tools (for example, from the Jenkins plug-in and from the Static Analyzer Command Line Utility and IDE plug-ins).
    - OData
      This section provides information and tips for using Open Data Protocol (OData) through the ASoC API.
    - Export scan data
      This section describes how to export scan results as CSV, JSON, or SARIF.
    - Export data to SARIF
      You can export data to SARIF (Static Analysis Results Interchange Format) from the product UI and via the Reports API.
    - DAST scan priority
      Use the API to assign priorities to DAST scans, manage the DAST scan queue order, and control scan scheduling.
  - Webhooks
    Use webhooks to receive notifications about events that occur in AppScan on Cloud.
  - Integrations
- Email notifications
  Use email notifications to be informed about scan progress, results, proactive alerts for new CVEs added and other AppScan events. This topic describes how to configure notification settings, select asset groups, applications and triggers, and manage delivery options.
- Personal scans
  A personal scan is a way of evaluating the relative security of an application in development without affecting overall application scan data (issues, for example), or compliance.
- Scan status
Dynamic analysis
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.
Interactive monitoring
Using an agent installed on your application, ASoC identifies security vulnerabilities in your application 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.
Software Composition Analysis
Use Software Composition Analysis (SCA) to scan for security vulnerabilities in open source and third-party packages used by your code. SCA includes Intelligent Finding Analytics (IFA) and Intelligent Code Analytics (ICA).
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 Scans and Sessions page lists the scans under the categories DAST, SAST, SCA, and IAST, where you can view your scan results, including scan statistics. To view, rescan, or download reports, select a scan.The Scans and Sessions page lists scans under the categories where you can view your scan results, including scan statistics. To view, rescan, or download reports, select a scan.
AppScan on Cloud AI assistant
The AI assistant is an integrated intelligence layer that works within the AppScan on Cloud environment. It provides security insights, automates issue triage, and offers remediation guidance.
AppScan Model Context Protocol (MCP) server
The AppScan MCP server integrates HCL AppScan on Cloud directly with AI-powered development environments and agents. By implementing the Model Context Protocol (MCP), this server allows LLMs (such as Claude or models running in VS Code) to securely access your security data—including SAST, DAST, SCA, and IAST results—to help you triage issues, analyze findings, and automate workflows using natural language.
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.

Generating API Keys

Use a Key ID and Key Secret to access the AppScan on Cloud REST APIs and to log in from some of the ASoC client tools (for example, from the Jenkins plug-in and from the Static Analyzer Command Line Utility and IDE plug-ins).

About this task

A Key ID is unique to each user. If you do not have a Key ID, or if you have lost your Key Secret, you can generate a new combination. To generate a new key, either:

Procedure

Go to the API key page at the AppScan on Cloud service:
- North America datacenter users: https://cloud.appscan.com/main/apikey
- Western Europe datacenter users: https://eu.cloud.appscan.com/main/apikey
Generate the key through the user interface:
1. Click the user menu in the upper-right corner and select API key or Account settings > API key.
2. Click Generate new keys.
3. If you have already generated the keys, a warning appears indicating that creating a new key pair will break any existing integrations that rely on your current credentials. Click Proceed to continue.
4. Optional: Set an expiration date (enabled by default) by selecting a date and clicking Proceed. If you do not want to set an expiration date, clear the checkbox and click Proceed.
5. You are required to re-authenticate before a new key is issued. Complete the login prompt to continue. After successful authentication, the new Key ID and Key Secret are displayed.
  
  Attention:
  The Key Secret is shown only once and is visible for one minute. Copy and store it in a secure secrets manager. The secret cannot be viewed again through the UI. Generating a new key immediately expires the previous one.
  
  Note:
  Users with permission to revoke keys may delete their own key from this page using Revoke API keys
Key management for administrators and managers:

Administrators and Managers (roles that have the manage API keys permission) can view and manage API keys for other users from the User Management page. Administrators and Managers can revoke another user’s API key; however, revoking a key does not prevent that user from generating a new one if their role allows it.