Welcome
AI-powered security
AppScan on Cloud recognizes the increasing role of artificial intelligence in development protocols. Just as AI can speed and strengthen the application development process, so can AI be used to ensure those applications are secure and ready for market.
AI security in AppScan on Cloud
In AppScan on Cloud traditional scans can cover conventional vulnerabilities within AI architecture.
Model Context Protocol (MCP) scanning with DAST

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.
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.
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).
AI-powered security
AppScan on Cloud recognizes the increasing role of artificial intelligence in development protocols. Just as AI can speed and strengthen the application development process, so can AI be used to ensure those applications are secure and ready for market.
- AI innovations in AppScan on Cloud
- AI security in AppScan on Cloud
  In AppScan on Cloud traditional scans can cover conventional vulnerabilities within AI architecture.
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.
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.

Model Context Protocol (MCP) scanning with DAST

Use manual explore workflows to test applications that use the Model Context Protocol (MCP) and analyze MCP tool calls during the scan.

AppScan now supports security testing for applications that use the Model Context Protocol (MCP). This capability is available through manual explore workflows and allows AppScan to capture traffic, analyze MCP tool calls, and perform a comprehensive security analysis for your integrations.

Workflow and configuration

MCP scanning is supported through manual exploration workflows using tools such as Postman. For Postman-based workflows, use Postman version 11.42.3 or later.
To use this capability, create a scan in AppScan Standard with the MCP template to ensure appropriate coverage for MCP-based traffic. Then, push it to HCL AppScan on Cloud through AppScan Connect.
For AppScan Connect, first load the MCP template, then open Postman to perform manual crawling. You can then run the scan through AppScan Connect as usual.

Current limitations

Direct import of Postman collections for MCP scanning is currently not supported because Postman cannot export collections that include MCP requests.
The current implementation relies on a manual process and is intended as a specialized workflow for this release. Automatic scanning is planned for a future release.