Agentic Agentless Detection performs security checks on servers without installing an agent, and you can enable or disable the feature as needed.
What is Agentic Agentless Detection
The Agentless Detection feature allows you to assess the security risks of cloud servers without installing the Security Center agent. The feature scans the images of your servers, uses AI sandbox-based dynamic analysis, and performs multi-dimensional security checks in an isolated environment, including checks for vulnerabilities, malware, configuration baselines, and sensitive files. The feature also supports AI-powered vulnerability fixing.
How it works
Create a full-server image (host scan tasks only): Based on the task configurations, the system creates a full-server image for the disks of the target Elastic Compute Service (ECS) instance.
Share and mount: The system shares the created snapshot or image with the dedicated analysis cluster of Security Center.
Isolated scanning: In an isolated dedicated environment, the analysis engine mounts the file system of the snapshot or image and performs a security scan. The AI sandbox detonates suspicious files or images and analyzes their runtime behaviors to improve the accuracy of threat analysis. This process consumes no computing resources of the target server.
Report generation and cleanup: After the scan is complete, the system generates a risk report and automatically deletes the temporary image based on the configured policies to save storage costs.
Common use cases
"Zero-interference" risk assessment: Perform non-intrusive security risk assessment that consumes no resources on core production systems that cannot run an agent or cannot tolerate performance impact, to ensure business continuity.
Unified cross-platform asset security detection: Cover all asset types, including legacy and proprietary systems, and quickly assess the overall security posture of a cross-platform environment from a unified view.
Visualized multi-dimensional risk detection: A single scan detects multi-dimensional risks such as vulnerabilities, malicious files, configuration baselines, and sensitive information, and visualizes the overall security posture.
Asset compliance and security review: Before you create instances or launch services, review the security of custom images and host snapshots to ensure that the delivered production environment meets security and compliance standards.
AI-powered automatic fixing loop: Based on the AI sandbox analysis results, the feature provides one-click or automated fixing suggestions and execution for risks that can be fixed, such as specific application vulnerabilities, baseline alerts, and malicious file alerts, to create a closed loop from risk detection to remediation.
Enable Agentic Agentless Detection
Enable the service
Log on to Security Center console.Select the region where the asset to be protected is located: Chinese Mainland or Outside Chinese Mainland.
On the Overview page, turn on the Agentic Agentless Detection switch in the Enable Pay-as-You-Go Service section.
On the enablement page, confirm the billing information (Agentless detection and analysis are billed by scanned data volume; vulnerability fixing is billed by the number of successfully fixed vulnerabilities. Both are billed daily and can be unsubscribed at any time). By default, Enable Policy (Recommended) is selected. Click Enable Now and Authorize.
ImportantAgentless detection uses the pay-as-you-go billing method.
You can also go to the page and click Activate Now and select the relevant agreement.
Complete service authorization (first time)
When you use the feature for the first time, the system prompts you to authorize a service role. Follow the on-screen instructions and click Authorize Now.
NoteAfter the authorization is successful, Security Center automatically creates the service-linked roles AliyunServiceRoleForSas and AliyunServiceRoleForSasAgentless. For more information about these service-linked roles, see Service-linked roles for Security Center.
Authorize Agentless Detection for encrypted ECS disks (first time)
When you use the feature for the first time, if your ECS instances use encrypted disks (encrypted system disks or encrypted data disks) and you need to perform agentless detection on them, complete the authorization by following the instructions in Authorize for ECS encrypted disks.
Disable Agentic Agentless Detection
Disable entry:
On the Overview page of the Security Center console, turn off the Agentic Agentless Detection switch in the Enable Pay-as-You-Go Service section.
On the Agentless Detection page of the Security Center console, click Suspended in the Risk Detection section.
Data cleanup:
The results of detection tasks are retained for only 30 days and are automatically cleared after expiration.
Scan task configurations are retained and not cleared.
Billing
The following describes the billing for the Agentless Detection feature:
Scan and fixing fees (Agentless Detection)
Billing method: Pay-as-you-go.
Billing cycle: Natural day.
Unit price:
Agentic agentless detection and analysis: USD 0.13/GB.
Agentic vulnerability fixing: USD 1.33/vulnerability.
Billing rules:
Agentic Agentless Detection and Analysis: Calculated based on the actual data volume of the scanned images, not the total disk capacity.
Agentic Vulnerability Fixing: Charged by the number of successfully fixed vulnerabilities, not by the number of tasks or attempts.
If a fixing task involves three vulnerabilities and all are fixed, it counts as three successfully fixed vulnerabilities.
Agentic Baseline Check Fixing and Malicious File Fixing: Charged by the number of successfully fixed alerts, not by the number of tasks or attempts.
ECS resource usage fees
ImportantWe recommend that you select Retain Only At-risk Image when you configure a host scan task. The system automatically deletes risk-free images after the scan is complete to save storage costs. For more information, see Retention Period Configuration.
Image fees: Detection tasks create images for servers, which are charged based on the image usage capacity and duration. These fees are charged by ECS. For more information, see Image billing.
Encrypted disk scan resource fees: To scan ECS encrypted disks, the system creates the following resources under your account each time a scan is performed. Some resources incur minimal fees and are released immediately after the scan.
ECS instance: When you select Service Key encryption for the ECS encrypted disk to be scanned, we create a preemptive ECS instance for encrypted disk scanning. These fees are charged by ECS. For more information, see Instance type billing.
VPC instance: A VPC instance named alibaba-cloud-security-scan-vpc. No fees are incurred for creating this instance.
VSwitch instance: A VSwitch instance named alibaba-cloud-security-scan-subnet. No fees are incurred for creating this instance.
FAQ
What is the difference between Agentless Detection and Virus Blocking?
Comparison item
Agentless Detection
Virus Blocking
Working mode
Scans offline snapshots and uses AI sandbox-based dynamic analysis
Real-time online monitoring and scanning, dynamic and static analysis
Server status
Can detect servers that are started or stopped
Can detect only servers that are started and have the agent online
Detection scope
Vulnerabilities, baselines, malicious samples, and sensitive files
Viruses, webshells, intrusions, vulnerabilities, and more
Handling capability
Supports detection, alerting, and whitelisting, and provides AI automatic fixing or one-click fixing for some risks
Provides one-click isolation, blocking, and fixing
Performance impact
None
Minimal (the agent consumes a small amount of system resources)
Billing mode
Pay-as-you-go (by scanned GB)
Subscription (Anti-virus edition or higher) or pay-as-you-go
Scan mode
Supports full-disk scan
Supports quick scan and custom directory scan
Can Agentless Detection automatically fix all risks?
No, it cannot automatically fix all risks. It supports AI automatic fixing for only some application vulnerabilities. For the list of supported vulnerabilities, see Vulnerability fix support list.
NoteFixing is completed by creating a new custom security image. The original image is not modified, ensuring business continuity and rollback capability.
For risks that do not support automatic fixing, follow the handling suggestions in the risk details page to manually complete the fixing.
How do I use the advanced detection feature for non-Alibaba Cloud servers?
Currently, Agentless Detection supports access to Alibaba Cloud ECS, AWS EC2, and Azure servers.
ImportantAzure is supported for access and detection only in Outside Chinese Mainland. For more information, see Detect and fix risks.
For servers from other cloud providers or on-premises data centers, we recommend that you install the Security Center agent and enable the Anti-virus edition or a higher edition to obtain comprehensive security protection capabilities. For more information, see Purchase Security Center and Install the agent.
Why is the asset IP not displayed for some Agentless Detection alerts?
When you use Agentless Detection, if the asset IP is empty, the possible causes are as follows:
The instance is released
After the asset instance corresponding to the alert is released, Security Center cannot obtain the IP address of the instance because the instance no longer exists in the system and its IP address cannot be tracked or displayed.
Data cleanup mechanism
Security Center may clean up the records of released instances, causing the related information to fail to load.
Does Agentless Detection support on-premises IDCs?
No. Agentless Detection relies on the cloud image mechanism for offline analysis. The system automatically creates images for specified servers to perform risk detection. On-premises servers cannot create cloud images. To perform security detection on on-premises servers, install the Security Center agent and use agent-based detection features such as Virus Blocking and Vulnerability Scan.
Supported regions
Agentic agentless detection is supported in the following regions and features:
Alibaba Cloud
regionId | Region name | Standard/encrypted disk scan | Parallel sandbox | Vulnerability fixing |
cn-hangzhou | China (Hangzhou) | |||
cn-qingdao | China (Qingdao) | |||
ap-northeast-1 | Japan (Tokyo) | |||
ap-northeast-2 | South Korea (Seoul) | |||
ap-southeast-1 | Singapore | |||
ap-southeast-3 | Malaysia (Kuala Lumpur) | |||
ap-southeast-5 | Indonesia (Jakarta) | |||
ap-southeast-6 | Philippines (Manila) | |||
ap-southeast-7 | Thailand (Bangkok) | |||
ap-southeast-8 | Malaysia (Johor) | |||
cn-beijing | China (Beijing) | |||
cn-chengdu | China (Chengdu) | |||
cn-guangzhou | China (Guangzhou) | |||
cn-heyuan | China (Heyuan) | |||
cn-hongkong | China (Hong Kong) | |||
cn-huhehaote | China (Hohhot) | |||
cn-shanghai | China (Shanghai) | |||
cn-shenzhen | China (Shenzhen) | |||
cn-wuhan-lr | China (Wuhan) (Local Region) | |||
cn-wulanchabu | China (Ulanqab) | |||
cn-zhangjiakou | China (Zhangjiakou) | |||
cn-zhongwei | China (Zhongwei) | |||
eu-central-1 | Germany (Frankfurt) | |||
eu-west-1 | UK (London) | |||
eu-west-2 | France (Paris) | |||
eu-west-3 | Netherlands (Amsterdam) | |||
me-central-1 | Saudi Arabia (Riyadh) | |||
me-east-1 | UAE (Dubai) | |||
na-south-1 | Mexico | |||
sa-east-1 | Brazil (Sao Paulo) | |||
us-east-1 | US (Virginia) | |||
us-west-1 | US (Silicon Valley) |
AWS
China site
regionId | Region name | Standard/encrypted disk scan | Parallel sandbox | Vulnerability fixing |
cn-north-1 | China (Beijing) | |||
cn-northwest-1 | China (Ningxia) |
International site
regionId | Region name | Standard/encrypted disk scan | Parallel sandbox | Vulnerability fixing |
af-south-1 | Africa (Cape Town) | |||
ap-east-1 | Asia Pacific (Hong Kong) | |||
ap-east-2 | Asia Pacific (Taipei) | |||
ap-northeast-1 | Asia Pacific (Tokyo) | |||
ap-northeast-2 | Asia Pacific (Seoul) | |||
ap-northeast-3 | Asia Pacific (Osaka) | |||
ap-south-1 | Asia Pacific (Mumbai) | |||
ap-south-2 | Asia Pacific (Hyderabad) | |||
ap-southeast-1 | Asia Pacific (Singapore) | |||
ap-southeast-2 | Asia Pacific (Sydney) | |||
ap-southeast-3 | Asia Pacific (Jakarta) | |||
ap-southeast-4 | Asia Pacific (Melbourne) | |||
ap-southeast-5 | Asia Pacific (Malaysia) | |||
ap-southeast-6 | Asia Pacific (New Zealand) | |||
ap-southeast-7 | Asia Pacific (Thailand) | |||
ca-central-1 | Canada (Central) | |||
ca-west-1 | Canada West (Calgary) | |||
eu-central-1 | Europe (Frankfurt) | |||
eu-central-2 | Europe (Zurich) | |||
eu-north-1 | Europe (Stockholm) | |||
eu-south-1 | Europe (Milan) | |||
eu-south-2 | Europe (Spain) | |||
eu-west-1 | Europe (Ireland) | |||
eu-west-2 | Europe (London) | |||
eu-west-3 | Europe (Paris) | |||
il-central-1 | Israel (Tel Aviv) | |||
me-central-1 | Middle East (UAE) | |||
me-south-1 | Middle East (Bahrain) | |||
mx-central-1 | Mexico (Central) | |||
sa-east-1 | South America (Sao Paulo) | |||
us-east-1 | US East (N. Virginia) | |||
us-east-2 | US East (Ohio) | |||
us-west-1 | US West (N. California) | |||
us-west-2 | US West (Oregon) |
Azure
China site
regionId | Region name | Standard/encrypted disk scan | Parallel sandbox | Vulnerability fixing |
chinanorth3 | China North 3 |
International site
regionId | Region name | Standard/encrypted disk scan | Parallel sandbox | Vulnerability fixing |
australiacentral | Australia Central | |||
australiaeast | Australia East | |||
australiasoutheast | Australia Southeast | |||
austriaeast | Austria East | |||
belgiumcentral | Belgium Central | |||
brazilsouth | Brazil South | |||
canadacentral | Canada Central | |||
canadaeast | Canada East | |||
centralindia | Central India | |||
centralus | Central US | |||
chilecentral | Chile Central | |||
eastasia | East Asia (Hong Kong) | |||
eastus | East US | |||
eastus2 | East US 2 | |||
francecentral | France Central | |||
germanywestcentral | Germany West Central | |||
indonesiacentral | Indonesia Central | |||
israelcentral | Israel Central | |||
italynorth | Italy North | |||
japaneast | Japan East | |||
japanwest | Japan West | |||
koreacentral | Korea Central | |||
koreasouth | Korea South | |||
malaysiawest | Malaysia West | |||
mexicocentral | Mexico Central | |||
newzealandnorth | New Zealand North | |||
northcentralus | North Central US | |||
northeurope | North Europe (Ireland) | |||
norwayeast | Norway East | |||
polandcentral | Poland Central | |||
qatarcentral | Qatar Central | |||
southafricanorth | South Africa North | |||
southcentralus | South Central US | |||
southeastasia | Southeast Asia (Singapore) | |||
southindia | South India | |||
spaincentral | Spain Central | |||
swedencentral | Sweden Central | |||
switzerlandnorth | Switzerland North | |||
uaenorth | UAE North | |||
uksouth | UK South | |||
ukwest | UK West | |||
westcentralus | West Central US | |||
westeurope | West Europe (Netherlands) | |||
westindia | West India | |||
westus | West US | |||
westus2 | West US 2 | |||
westus3 | West US 3 |
Tencent Cloud
regionId | Region name | Standard/encrypted disk scan | Parallel sandbox | Vulnerability fixing |
ap-guangzhou | China (Guangzhou) |