Vulnerability Scan Service
- Operation Guide
Privacy Policy
Last updated: 2022-02-28 14:43:57
1. INTRODUCTION
This Module applies if you use Vulnerability Scan Service (“Feature”). This Module is incorporated into the privacy policy located at Privacy Policy. Terms used but not defined in this Module shall have the meaning given to them in the Privacy Policy. In the event of any conflict between the Privacy Policy and this Module, this Module shall apply to the extent of the inconsistency.
2. CONTROLLERSHIP
The controller of the personal information described in this Module is as specified in the Privacy Policy.
3. AVAILABILITY
This Feature is available to users globally but primarily intended for users located in the same country/region as the selected service region for optimal performance.
4. HOW WE USE PERSONAL INFORMATION
We will use the information in the following ways and in accordance with the following legal basis:
Personal Information | Use | Legal Basis |
Vulnerability Scanning Engine Operating Data: engine operation time, engine operation count, engine operation status, engine task log data | We use this information to ensure the engine functions as required, to provide this Feature to you. Please note that this data is stored in our TencentDB for Redis (Redis), TencentDB for MySQL (MySQL) and TencentDB for MongoDB (MongoDB) features for this purpose. | We process this information as it is necessary for us to perform our contract with you to provide the Feature. |
Asset Mapping Engine Operating Data: map of engine operation | We use this information to provide this Feature to you, including to generate security scan, risk and related reports, provide risk warnings and vulnerability detection notifications, and provide repair suggestions. Please note that this data is stored in our Redis, MySQL and MongoDB features for this purpose. | We process this information as it is necessary for us to perform our contract with you to provide the Feature. |
User Quota Data: expiry date and time, number of domain names, number of IPs, number of APIs | We use this information to calculate your user quota and charge, for billing purposes. Please note that this data is stored in our Redis, MySQL and MongoDB features for this purpose. | We process this information as it is necessary for us to perform our contract with you to provide the Feature. |
Task Log Data: task name, monitoring type, scanned asset scanning plan, scanning speed, scanning duration, scanning result | We use this information to provide this Feature to you, and for troubleshooting. Please note that this data is stored in our TencentDB for Redis, TencentDB for MySQL and TencentDB for MongoDB features for this purpose. | We process this information as it is necessary for us to perform our contract with you to provide the Feature. |
Vulnerability Matching Data: Vulnerability name, threat level, affected assets, vulnerability type, time when last found | We use this information to provide this Feature to you, and for troubleshooting. Please note that this data is stored in our TencentDB for Redis, TencentDB for MySQL and TencentDB for MongoDB features for this purpose. | We process this information as it is necessary for us to perform our contract with you to provide the Feature. |
Port Matching Data: port, vulnerability response suggestions, protocol, port service | We use this information to provide this Feature to you, and for troubleshooting. Please note that this data is stored in our TencentDB for Redis, TencentDB for MySQL and TencentDB for MongoDB features for this purpose. | We process this information as it is necessary for us to perform our contract with you to provide the Feature. |
5. HOW WE SHARE AND STORE PERSONAL INFORMATION
As specified in the Privacy Policy.
6. DATA RETENTION
We will retain personal information in accordance with the following:
Personal Information | Retention Policy |
Vulnerability Scanning Engine Operating Data | Stored for 7 days. |
Asset Mapping Engine Operating Data | Stored for 7 days. |
User Quota Data | We retain such data for as long as you use the Feature. When your use of the Feature is terminated, we will delete this data after 7 days. |
Task Log Data | We retain such data for as long as you use the Feature. When your use of the Feature is terminated, we will delete this data after 7 days. |
Vulnerability Matching Data | We retain such data for as long as you use the Feature. When your use of the Feature is terminated, we will delete this data after 7 days. |
Port Matching Data | We retain such data for as long as you use the Feature. When your use of the Feature is terminated, we will delete this data after 7 days. |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No