Vulnerability Disclosure
Receive vulnerability reports through a secure channel agreed with Mobile-ID.
Document status and scope
Reference draft for agreeing service conditions. No confirmed approver or effective date is available. The procedure below requires project review and approval before application.
| Property | Value |
|---|---|
| Document ID | LTANS-VULNERABILITY-DISCLOSURE |
| Content revision | 0.2 · DRAFT |
| Topic | Reproducible vulnerability reporting |
| Editorial date | 15/10/2026 |
| Effect | Not confirmed |
Responsibilities and decisions
Security contact confirms intake scope and sensitive-data transfer channel.
Application procedure
Send URL/version, reproduction, impact and minimal data → triage → remediate → coordinate disclosure.
Exceptions and controls
Do not expose others’ data or secrets; impactful testing requires an authorized scope.
Records and release conditions
Intake record, acknowledgement, impact assessment and fix results.
Formal release must record owner, approver, scope and effective date; preserve revisions and approval evidence. Confirm contacts through info@mobile-id.vn. Do not include secrets or sensitive records in discovery email.