Classified Protection Evaluation Guide
This document is intended for enterprise users with compliance requirements under the Classified Protection Scheme (MLPS), introducing how to use CloudBase resources to pass the classified protection evaluation.
Overview
What is Classified Protection (MLPS)?
The Classified Protection Scheme (referred to as "Classified Protection" or "MLPS") is a fundamental national policy and system in the field of cyber security in China. According to the Cybersecurity Law of the People's Republic of China, network operators shall perform security protection obligations in accordance with the requirements of the classified protection system.
The scheme classifies the security protection levels of information systems into five levels:
| Level | Name | Applicable Scenarios |
|---|---|---|
| Level 1 | User Autonomous Protection | General information systems |
| Level 2 | System Audit Protection | General enterprise information systems |
| Level 3 | Security Marking Protection | Systems involving critical information or a large volume of user data |
| Level 4 | Structured Protection | Critical national information systems |
| Level 5 | Access Verification Protection | National critical information infrastructure |
Most enterprise applications are required to satisfy either Level 2 or Level 3 classified protection requirements.
CloudBase Compliance and Certifications
As a Tencent Cloud public cloud product, CloudBase inherits the security evaluation and audit results of Tencent Cloud public cloud:
- Classified Protection (MLPS): Tencent Cloud public cloud (IaaS, PaaS, SaaS) has completed Level 3 filing and evaluation, and CloudBase is within its scope.
- Trusted Cloud Certification: Certified by the China Academy of Information and Communications Technology (CAICT).
- ISO 27001 / SOC Audit: Tencent Cloud public cloud holds the information security management system certification and SOC audits. Copies of the qualification documents can be requested on demand.
Passing the cloud platform evaluation does not mean that applications built on top of CloudBase automatically meet the classified protection requirements. You still need to configure and use CloudBase security capabilities reasonably based on your own business characteristics to satisfy the classified protection evaluation.
Mapping Classified Protection Requirements to CloudBase Capabilities
Level 2 Classified Protection Requirements Mapping
The following table details the comparison between MLPS 2.0 Level 2 requirements and CloudBase security capabilities:
| Security Requirement Category | Evaluation Requirement | Corresponding CloudBase Capability | Configuration Recommendation |
|---|---|---|---|
| Identification & Authentication | Users log in must be identified and authenticated | Authentication Service | Enable login methods such as username/password, SMS verification code, etc. |
| Identification & Authentication | Identities must be unique | Unique user UID | Automatically guaranteed by the system |
| Access Control | Resource access should be controlled based on security policies | Database Safety Rules, Permission Management | Configure fine-grained data access permissions |
| Access Control | Administrative users should be granted the minimum required permissions | Cloud Access Management (CAM) | Use the principle of least privilege to configure sub-accounts |
| Security Audit | Security audit functionality should be enabled | Log Service | Enable operational log recording |
| Data Integrity | Verification techniques should be adopted to ensure the integrity of important data | Application-level checksums + database transactions | Store checksums for critical data and verify before and after writes |
| Data Backup & Recovery | Data backup and recovery functions should be provided | Database Backup | Configure automatic backup policies |
Level 3 Classified Protection Requirements Mapping
Level 3 classified protection introduces stricter requirements on top of Level 2:
| Security Requirement Category | Evaluation Requirement | Corresponding CloudBase Capability | Configuration Recommendation |
|---|---|---|---|
| Identification & Authentication | Use a combination of two or more authentication factors (e.g., password, cryptography, biometrics), one of which must be cryptographic | Multiple login methods | Password + SMS/email verification code (the second factor is orchestrated by your own code) |
| Identification & Authentication | Login failure handling functionality should be provided | Login Protection Mechanism | Configure login failure lockout policies |
| Access Control | Set security markings for critical subjects and objects | User Roles, Permission Tags | Implement Role-Based Access Control (RBAC) |
| Security Audit | Audit records should include event types, times, users, results, etc. | Detailed Log Recording | Configure complete audit logs |
| Security Audit | Audit records should be protected | Cloud Log Service (CLS) | Deliver logs to an independent, secure log service |
| Intrusion Prevention | Be capable of discovering potential known vulnerabilities | Vulnerability scanning, DDoS protection | Scan application code and dependencies regularly; the platform provides baseline protection |
| Data Confidentiality | Use cryptographic technologies to ensure confidentiality of important data during transmission | HTTPS/TLS Encryption | Set the domain protocol policy to HTTP_TO_HTTPS |
| Data Confidentiality | Use cryptographic technologies to ensure confidentiality of important data in storage | Encrypted Storage | Encrypt sensitive data before storing it |
| Data Backup & Recovery | Off-site data backup functionality should be provided | Data export | Export data and transfer it to Cloud Object Storage in another region |
In-Depth Analysis of CloudBase Security Capabilities
1. Authentication
CloudBase provides comprehensive authentication services, supporting multiple login methods:
| Login Method | Security Level | Applicable Scenarios | MLPS Support |
|---|---|---|---|
| Username/Password | Basic | General scenarios | Level 2 / Level 3 |
| SMS Verification Code | High | Scenarios requiring mobile phone verification | Level 2 / Level 3 |
| Email Verification Code | High | Enterprise applications | Level 2 / Level 3 |
| WeChat Login | High | Mini Program, Official Account | Level 2 / Level 3 |
| Custom Login | Flexible | Integration with enterprise's existing account systems | Level 2 / Level 3 |
SMS code sign-in is available in the Shanghai region (
ap-shanghai) only, and requires your own SMS provider. The CloudBase SMS package went offline on November 13, 2026, so verification messages sent with the default Tencent Cloud signature are no longer available. Apply for a signature and template in the Tencent Cloud SMS console and complete the configuration first.
SMS Verification Code Login Example:
import cloudbase from '@cloudbase/js-sdk';
const app = cloudbase.init({
env: 'your-env-id',
region: 'ap-shanghai' // SMS sign-in is available in Shanghai only
});
const auth = app.auth();
const phoneNumber = '+86 13800000000'; // Must include the country code
// Step 1: Send the SMS code and keep the returned verificationInfo
const verificationInfo = await auth.getVerification({
phone_number: phoneNumber
});
// Step 2: Wait for the user to enter the received code
const verificationCode = userInputCode;
// Step 3: Verify the code and sign in
await auth.signInWithSms({
verificationInfo,
verificationCode,
phoneNum: phoneNumber
});
The SDK does not provide a built-in flow for "sign in with a password, then verify a second factor". If Level 3 classified protection requires two factors (password plus code), your backend must verify the code after the password sign-in and only then allow sensitive operations.
For more authentication configurations, please refer to the Authentication Documentation.
2. Access Control
Database Safety Rules
CloudBase supports JSON-based safety rule configuration to implement fine-grained data access control:
{
"read": "auth.uid == doc.userId",
"create": "auth.uid != null && request.data.userId == auth.uid",
"update": "auth.uid == doc.userId",
"delete": "auth.uid == doc.userId && doc.status == 'draft'"
}
Once create, update, and delete are configured, write only acts as a fallback and does not need to be set again. With WeChat sign-in the user identifier is auth.openid; with other sign-in methods it is auth.uid.
Safety Rule Capabilities:
| Capability | Description | MLPS Requirement |
|---|---|---|
| Identity Authentication | auth.uid identifies the current user | Access Control |
| Data Validation | Validates the legitimacy of request data | Data Integrity |
| Field-Level Control | Controls fields that are readable or writable | Least Privilege |
| Conditional Judgment | State-based access control of data | Security Marking |
For more safety rule configurations, please refer to the Safety Rules Documentation.
Cloud Access Management (CAM)
Use Tencent Cloud CAM to implement fine-grained administrator control:
- Root Account: Has full control over all resources.
- Sub-Account: Allocated permissions for specific resources as needed.
- Role: Defines a set of permission policies that can be assumed by multiple accounts.
Least Privilege Configuration Recommendations:
| Role | Recommended Permissions | Description |
|---|---|---|
| Developer | Cloud Function Read/Write, Database Read | Daily development and debugging |
| Operations | Log View, Monitoring & Alarm | System operations |
| Auditor | Log Read-Only | Security audit |
| Admin | Full Permissions | Restricted to essential personnel only |
3. Data Security
Encryption in Transit
CloudBase supports encrypted transmission via HTTPS/TLS:
- API Interface: SDK and HTTP API calls go over HTTPS.
- Static Hosting / HTTP Gateway: HTTP and HTTPS are both enabled by default. Set the protocol policy of a custom domain to
HTTP_TO_HTTPSto redirect all traffic to HTTPS. - Cloud Function Invocation: Called through HTTPS endpoints.
- Direct Database Connection (PG mode): SSL connections are supported and can be enabled in the connection string.
Storage Security
| Security Measure | Description | Configuration Method |
|---|---|---|
| Sensitive Data Encryption | Encrypt fields such as ID card numbers and phone numbers before writing | Implemented via business code |
| File Access Control | Cloud Storage access control | Configure storage safety rules |
Sensitive Data Encryption Storage Example:
const crypto = require('crypto');
// Key is 32 bytes and read from an environment variable
const encryptionKey = Buffer.from(process.env.ENCRYPT_KEY, 'base64');
// AES-256-GCM: random IV plus auth tag; store the IV and tag together with the ciphertext
function encrypt(text, key) {
const iv = crypto.randomBytes(12);
const cipher = crypto.createCipheriv('aes-256-gcm', key, iv);
const encrypted = Buffer.concat([cipher.update(text, 'utf8'), cipher.final()]);
return Buffer.concat([iv, cipher.getAuthTag(), encrypted]).toString('base64');
}
// Store encrypted sensitive data (app is the instance returned by cloudbase.init())
const db = app.database();
await db.collection('users').add({
username: 'user@example.com',
idCard: encrypt('110101199001011234', encryptionKey), // Encrypted ID card
phone: encrypt('13800138000', encryptionKey) // Encrypted phone number
});
4. Log Auditing
CloudBase provides complete log recording capabilities:
| Log Type | Content | Use Case |
|---|---|---|
| Access Log | HTTP request records | Access audit |
| Cloud Function Log | Function execution records | Business audit |
| Database Log | Data operation records | Data audit |
| Error Log | Exception error records | Troubleshooting |
Log Delivery Configuration:
It is recommended to deliver logs to Tencent Cloud Log Service (CLS) to achieve:
- Long-term log preservation (satisfying the MLPS requirement for audit log preservation).
- Log search and analysis.
- Alarm and notifications.
- Log exporting and backup.
For more log and monitoring configurations, see the Logs and Monitoring Documentation.
5. Network Security
CloudBase features built-in multi-layered network security:
| Protection Capability | Description | MLPS Requirement |
|---|---|---|
| DDoS Protection | Tencent Cloud basic DDoS protection | Intrusion Prevention |
| Anti-Crawler | Gateway anti-crawler policies | Intrusion Prevention |
| Rate Limiting | QPS limits for Cloud Functions and CloudBase Run by resource or client | Intrusion Prevention |
| IP Black/White List | Access source control for Static Hosting and the gateway | Access Control |
6. Data Backup and Recovery
Backup capabilities depend on the database mode:
| Backup Method | Cycle | Retention Period | Description |
|---|---|---|---|
| Automatic backup (classic mode) | Daily, 02:00 - 06:00 | 7 days | Runs automatically and serves as the source for rollback |
| Instance backup (PG mode) | Defined by the instance policy | See the console | Automatic and manual backups plus point-in-time recovery |
| Data export | On-demand | You manage it | Export to JSON/CSV and transfer to Cloud Object Storage in another region |
Level 3 classified protection requires off-site backup. Automatic and instance backups stay in the region where the environment resides. For off-site backup, export the data and transfer it to Cloud Object Storage or another store in a different region, and maintain the transfer job yourself.
For details, see Database Rollback and PostgreSQL Backup and Recovery.
Best Practices for MLPS Compliance
Level 2 Compliance Checklist
Configuring according to the following checklist can meet the basic Level 2 requirements:
-
Identification & Authentication
- Enable at least one login method.
- Configure password complexity requirements.
- Enable login failure restriction.
-
Access Control
- Configure database safety rules.
- Use CAM to manage administrator permissions.
- Enforce the principle of least privilege.
-
Security Audit
- Enable access log recording.
- Configure log preservation policies.
-
Data Security
- Configure public domains for HTTPS only, or redirect HTTP to HTTPS.
- Configure automatic database backup.
Level 3 Compliance Checklist
Add the following configurations on top of Level 2:
-
Enhanced Identification & Authentication
- Require a second factor (password + SMS/email verification code) for sensitive operations.
- Configure session timeout policies.
- Enable anomalous login detection.
-
Enhanced Access Control
- Implement Role-Based Access Control (RBAC).
- Configure approvals for sensitive operations.
- Enable two-step operational confirmations.
-
Enhanced Security Audit
- Deliver logs to an independent CLS.
- Retain audit logs for at least 6 months (180 days).
- Set security alarm rules.
-
Enhanced Data Security
- Encrypt sensitive data in storage.
- Export data to another region to achieve off-site backup.
- Conduct regular data recovery drills.
-
Enhanced Network Security
- Configure IP white lists (for management APIs).
- Configure rate limits for Cloud Functions and CloudBase Run.
- Put WAF in front of public web services as needed.
Guidelines for Different Business Deployment Scenarios
Compliance strategies vary depending on your deployment. Below are detailed guidelines for two typical scenarios.
Scenario 1: All Services Deployed on CloudBase
If all your businesses run on CloudBase (including Cloud Functions, CloudBase Run, Database, Storage, etc.), MLPS compliance is relatively simple.
Architecture Example
┌─────────────────────────────────────────────────────────────┐
│ User / Client │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ CloudBase Environment │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ Static │ │ CloudBase │ │ Cloud │ │
│ │ Hosting │ │ Run │ │ Functions │ │
│ │ (Front) │ │ (Back APIs) │ │ (Biz Logic) │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
│ │ │ │ │
│ └────────────────┼────────────────┘ │
│ ▼ │
│ ┌─────────────────────────────────────────────────────┐ │
│ │ Database / Cloud Storage │ │
│ └─────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────┘
MLPS Compliance Advantages
| Advantage | Description |
|---|---|
| ✅ Infrastructure Security Managed by Platform | No need to worry about underlying security like OS, network devices, etc. |
| ✅ No Extra Security Products Required | No need for bastion hosts, host security agents, firewalls, etc. |
| ✅ Unified Security Management Portal | All security configurations are completed in the CloudBase Console. |
| ✅ Simplified Categorization & Filing | Clear boundaries, simple asset inventory. |
Checklist (Pure CloudBase Architecture)
Security Physical Environment — Handled by Tencent Cloud data centers; users do not need to concern themselves.
Security Communication Network
- Confirm HTTPS is enabled for public domains (enable forced redirect as needed).
- Configure domains and routes for HTTP Gateways.
- Enable HTTP gateway authentication for publicly exposed paths as needed.
Security Area Boundary
- Configure IP black/white lists (if needed).
- Configure rate limits for Cloud Functions and CloudBase Run.
- Configure inter-service access controls (internal links).
Security Computing Environment
- Configure database safety rules.
- Configure storage safety rules.
- Enable Authentication Service.
- Require a second factor for sensitive operations (for Level 3).
Security Management Center
- Deliver logs to CLS (retained for at least 6 months).
- Set monitoring alarm rules.
- Configure CAM permissions (principle of least privilege).
Data Security
- Confirm automatic or instance backups run as expected.
- Export data to another region for off-site backup (for Level 3).
- Encrypt sensitive data in storage.
How to Address Evaluators
Address the evaluation team with:
"Our business system is completely deployed on the Tencent CloudBase platform. CloudBase is a Serverless PaaS platform running on Tencent Cloud public cloud, which has completed Level 3 classified protection filing and evaluation; copies of the qualification documents can be requested from Tencent Cloud. We do not directly manage any physical servers or virtual machines; infrastructure security is handled by Tencent Cloud. We are primarily responsible for application-layer security configurations, including authentication, access controls, database safety rules, etc."
Scenario 2: Hybrid Architecture (CloudBase + Other Cloud Resources)
If your business uses CloudBase in combination with other cloud resources (such as CVM, PostgreSQL, or existing MySQL instances), you need to satisfy the MLPS requirements for all different resource types.
Common Hybrid Architecture
┌─────────────────────────────────────────────────────────────┐
│ User / Client │
└─────────────────────────────────────────────────────────────┘
│
┌───────────────────┼───────────────────┐
▼ ▼ ▼
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ CloudBase │ │ Cloud Servers │ │ Cloud Database │
│ ┌───────────┐ │ │ (CVM) │ │ (PG) │
│ │ Run / │ │ │ │ │ │
│ │ Functions │ │ │ Traditional Back│ │ Core Biz Data │
│ │ Static │ │ │ Services │ │ │
│ └───────────┘ │ └─────────────────┘ └─────────────────┘
│ │ │ │ │
│ ▼ │ │ │
│ ┌───────────┐ │ │ │
│ │ Document │◄─┼───────────┴───────────────────┘
│ │ Database │ │
│ └───────────┘ │
└─────────────────┘
Shared Responsibility Model
In a hybrid architecture, different resources carry distinct security responsibilities:
| Resource Type | Infrastructure Security | Host Security | Application Security | Required Security Products |
|---|---|---|---|---|
| CloudBase Run / Functions | Tencent Cloud | Managed by Platform | User | No extra purchase required |
| Cloud Servers (CVM) | Tencent Cloud | User | User | Bastion host, Host security |
| Cloud Database (PostgreSQL/MySQL) | Tencent Cloud | Tencent Cloud | User | Database audit (as needed) |
| Cloud Storage (COS) | Tencent Cloud | N/A | User | No extra purchase required |
Checklist (Hybrid Architecture)
CloudBase Part — Configure according to Scenario 1's checklist.
Cloud Server (CVM) Part
- Purchase and configure a bastion host.
- Install host security agents (e.g., Cloud Workload Protection).
- Configure security group rules.
- Conduct regular vulnerability scanning and remediations.
- Configure OS security baselines.
- Enable login auditing.
Cloud Database Part
- Configure database access white lists.
- Enable SSL-encrypted connections.
- Configure automatic backup policies.
- Enable database audit as needed.
- Configure account permissions (least privilege).
Interconnection Security
- Configure VPC network isolation.
- Use private networks (VPC) for connections between CloudBase, CVM, and databases.
- Configure a unified API gateway (if needed).
Key Considerations
-
Misconception: Using CloudBase means a bastion host is not needed.
- Correct: Only pure CloudBase architectures do not need it. If CVM is involved, a bastion host is still required for CVMs.
-
Misconception: The cloud platform's Level 3 evaluation covers the entire system.
- Correct: The evaluation of Tencent Cloud public cloud only covers the cloud platform itself; applications on CloudBase and your own resources must independently meet their respective requirements.
-
Misconception: Data is secure as long as it resides in the same VPC.
- Correct: Fine-grained access control rules must still be configured.
Recommended Security Products
For a hybrid architecture, it is recommended to configure the following security products:
| Security Need | Recommended Product | Applicability | Mandatory (Level 3 MLPS)? |
|---|---|---|---|
| O&M Audit | Bastion Host | CVM / Lighthouse | ✅ Mandatory |
| Host Security | Cloud Workload Protection | CVM / Lighthouse | ✅ Mandatory |
| Vulnerability Scan | Vulnerability Scan Service | CVM / Lighthouse | ✅ Mandatory |
| Database Audit | Database Audit | Cloud Database | As needed (recommended) |
| Web Protection | WAF | External Web Services | As needed (recommended) |
| DDoS Protection | Anti-DDoS | External Services | Point of entry |
| Log Audit | Log Service (CLS) | All Resources | ✅ Mandatory |
How to Address Evaluators
Address the evaluation team with:
"Our system adopts a hybrid architecture. Some services run on CloudBase (Serverless PaaS), while other parts run on cloud servers. For the CloudBase part, infrastructure security is handled by the platform, and we primarily configure application-layer security. For the cloud server part, we have configured a bastion host for O&M audit and host security agents for host protection, and conduct regular vulnerability scans. The two parts communicate via a private network with corresponding access control policies."
Scenario Comparison & Recommendations
| Decision Factor | Pure CloudBase Architecture | Hybrid Architecture |
|---|---|---|
| Compliance Complexity | ⭐ Low | ⭐⭐⭐ High |
| Required Security Products | Basically none | Bastion host, Host security, etc. |
| O&M Complexity | ⭐ Low | ⭐⭐⭐ High |
| Assessment Prep Workload | ⭐ Small | ⭐⭐⭐ Large |
| Ideal Scenarios | New projects, small/medium systems | Legacy migration, highly complex setups |
Recommendations:
- For new projects, prioritize a pure CloudBase architecture to significantly lower MLPS compliance costs and complexity.
- For legacy migration, migrate workloads to CloudBase progressively to reduce the number of CVMs that you need to maintain manually.
- If specific requirements dictate the use of CVMs (e.g., custom software, GPU computing), plan according to the hybrid architecture.
Preparation Recommendations for Classified Protection Evaluation
Pre-Assessment Preparation
-
Inventory System Assets
- List all used CloudBase services.
- Identify where sensitive data is stored.
- Draw system architecture and data flow diagrams.
-
Complete Security Configurations
- Complete configurations according to the checklist.
- Retain configuration screenshots as evidence.
-
Prepare Documentations
- Security management policy documents.
- Incident response plans.
- Data backup and recovery strategies.
Coordination Points During Assessment
| Stage | Coordination Point | CloudBase Support |
|---|---|---|
| Technical Assessment | Show security configurations | Console screenshots, config exports |
| Log Audit | Provide audit logs | CLS exports |
| Vulnerability Scan | Cooperate with scanning | Provide test environments |
| Penetration Testing | Cooperate with security tests | Provide test accounts |
Related Resources
- Tencent Cloud Classified Protection Compliance
- Tencent Cloud Compliance Documents Center
- Tencent Cloud DDoS Protection
- Authentication Service
- Safety Rules Configuration
- Log Service
- Database Backup
FAQ
Do I still need a bastion host after using CloudBase Run?
In most cases, no. CloudBase Run adopts a Serverless container architecture, which is fundamentally different from traditional CVMs:
| Feature | Traditional CVM | CloudBase Run |
|---|---|---|
| Server Management | Self-managed by user | Managed by platform |
| SSH Login | Required | Not provided |
| O&M Approach | Bastion host / jump host | WebShell + Log Service |
| MLPS Requirement | O&M audit required | No server accounts; different audit scope |
Why a bastion host is generally not needed:
- Serverless Architecture: CloudBase Run is a Serverless container service. You hold no server accounts, so there is no traditional SSH login scenario.
- WebShell Alternative: CloudBase Run provides a WebShell feature to enter containers from the console for debugging. Commands executed inside the container cannot be observed or recorded by CloudBase Run; if command-level auditing is required, add an audit tool to your image.
- Console Operation Auditing: CloudAudit records who opened WebShell and when, and which service configurations were changed.
- Access Isolation: Use CAM to control who can access WebShell.
Key points for MLPS evaluation:
During the assessment, if the evaluator asks about O&M auditing, you can state:
- CloudBase Run is Serverless and does not provide SSH access; you hold no server accounts.
- O&M uses Console WebShell. Console operations are recorded by CloudAudit; command-level auditing inside containers is added in the image when required.
- Access permissions are managed centrally by Tencent Cloud CAM, supporting fine-grained controls.
If your system uses CVMs/Lighthouses alongside CloudBase Run, those traditional servers still require bastion hosts for O&M auditing. Bastion host requirements apply only to traditional servers requiring SSH logins.
Do I still need host security products when using CloudBase?
No. Host security products (such as Cloud Workload Protection) are primarily used to protect the OS layer of traditional servers (CVMs). CloudBase's Serverless architecture is fundamentally different:
| Security Focus | Traditional Servers | CloudBase |
|---|---|---|
| OS Security | User's responsibility | Managed by platform |
| System Patching | Self-managed | Runtime maintained by platform |
| Intrusion Detection | Host security agent required | Handled by the platform |
| Antivirus Protection | Antivirus software required | Container isolation, no agent needed |
CloudBase Safety Mechanisms:
- Container Isolation: Each service runs in an isolated container.
- Secure Base Images: Platform-provided base images are security-hardened.
- Automatic Updates: Underlying runtime is maintained by the platform, automatically patching vulnerabilities.
- Network Isolation: Inter-service network isolation by default.
Do I still need to configure firewalls/security groups for CloudBase?
In most cases, no. CloudBase's network security model is different from traditional IaaS:
| Feature | Traditional CVM | CloudBase |
|---|---|---|
| Inbound Traffic Control | Security group rules | HTTP Gateway + Authentication |
| Outbound Traffic Control | Security group rules | Allowed to public by default |
| Inter-Service Communication | VPC + Security Groups | Internal Links (auto-configured) |
| Port Management | Manual port exposure | Unified HTTP/HTTPS ports |
CloudBase Network Security Capabilities:
- HTTP Gateway: Unified entrance supporting custom domains and path routing.
- Authentication: Enabled per path; API requests without valid credentials return
MISSING_CREDENTIALS. - IP Black/White List: Limit access sources at the gateway.
- Rate Limiting: Built-in API rate limiting to prevent malicious requests.
How does CloudBase satisfy "vulnerability scanning" requirements?
MLPS requires regular vulnerability scanning. CloudBase handles this at different layers:
Platform Layer (Responsibility of Tencent Cloud):
- Underlying infrastructure vulnerability scanning.
- Container runtime security updates.
- Platform component hardening.
Application Layer (Your Responsibility):
- Code security auditing.
- Dependency package vulnerability checks.
- API security testing.
Recommended Compliance Operations:
- Code Level: Use code analysis tools (such as SonarQube) to check code.
- Dependency Level: Regularly update dependencies and use tools like
npm audit. - API Level: Perform API security testing focusing on authentication and input validation.
- Configuration Level: Review database safety rules and storage access configurations.
Explain to the evaluator that CloudBase is a Serverless PaaS platform where underlying infrastructure security is managed by Tencent Cloud. Users focus on application-layer security and can provide code audit, dependency scan, and API test reports as supporting evidence.
How do I implement "network partitioning" in CloudBase?
Traditional MLPS requires physical or logical partitioning of network areas (such as DMZ, core zone, etc.). CloudBase achieves this via logical isolation:
| Isolation Dimension | Implementation | Description |
|---|---|---|
| Environment | Multi-environment | Development, testing, and production environments are completely isolated. |
| Service | Container Isolation | Each service runs in an independent container, isolated by default. |
| Data | Database Permissions | Control data access via JSON safety rules. |
| Access | Gateway Authentication | Enabled per path; requests without credentials return 401. |
Recommended Environment Planning:
┌─────────────────────────────────────────────────────┐
│ CloudBase Environments │
├─────────────────────────────────────────────────────┤
│ Production Environment (env-prod) │
│ ├── Front-End Services (Public Access) │
│ ├── API Services (Authentication) │
│ ├── Internal Services (Internal Access) │
│ └── Databases (Safety Rule Controls) │
├─────────────────────────────────────────────────────┤
│ Testing Environment (env-test) ← Completely Isolated│
├─────────────────────────────────────────────────────┤
│ Development Environment (env-dev) ← Completely Isolated│
└─────────────────────────────────────────────────────┘
How long are Cloud Functions/CloudBase Run logs kept? Can they meet MLPS requirements?
The Cybersecurity Law requires network logs to be retained for at least six months, and MLPS 2.0 Level 3 requires audit records to be kept for at least six months (about 180 days). For CloudBase's default log retention periods and extension options, see Log Retention.
Configuration to Satisfy MLPS Requirements:
- Enable Log Delivery: Deliver logs to Tencent Cloud Log Service (CLS)
- Configure Retention: Set log retention to 180+ days in CLS
- Log Backup: Export CLS logs to COS for long-term secure archiving
Does CloudBase support MFA? How do I satisfy Level 3 MLPS MFA requirements?
Authentication supports multiple factors, but there is no built-in flow that verifies a second factor after a password sign-in. Combining two factors is orchestrated by your own business code.
| Authentication Factor | Type | CloudBase Support |
|---|---|---|
| Password | Knowledge Factor | Username & password login |
| SMS Verification Code | Possession Factor | SMS code login |
| Email Verification Code | Possession Factor | Email code login |
| WeChat Authorization | Possession Factor | WeChat scan / Mini Program auth |
| Custom Authentication | Extensible | Integration with enterprise systems |
How to combine two factors:
- Scenario A: After a password sign-in, your backend verifies an SMS code and only then allows sensitive operations.
- Scenario B: After a password sign-in, your backend verifies an email code, implemented the same way as Scenario A.
- Scenario C: After a WeChat authorization sign-in, sensitive operations require an extra SMS code.
SMS code sign-in is available in the Shanghai region (ap-shanghai) only and requires your own SMS provider. The CloudBase SMS package went offline on November 13, 2026, so verification messages sent with the default Tencent Cloud signature are no longer available. Confirm the region and the SMS channel before using SMS codes as a second factor. See SMS Verification Code Login.
CloudBase has passed Level 3 evaluation, is my app automatically compliant?
No. Tencent Cloud public cloud, where CloudBase runs, has completed Level 3 classified protection filing and evaluation, which means the platform-side baseline security capabilities meet Level 3 requirements. Your application's compliance depends on how you configure and use these features. You must configure authentication, access rules, log audits, and data backups reasonably according to your needs.
How do I choose between Level 2 and Level 3 Classified Protection?
- Level 2: Suitable for general enterprise applications not involving large quantities of sensitive personal data.
- Level 3: Mandatory for systems involving massive user data, financial transactions, health/medical records, and other highly sensitive information.
It is recommended to consult a professional MLPS evaluation agency based on your business nature and regulator requirements.