Rencana respons insiden untuk Weblate

Cakupan dan tujuan

This IRP covers incidents impacting the confidentiality, integrity, or availability of Weblate-operated deployments.

Catatan

This plan is specifically designed for deployments operated by Weblate s.r.o. Other deployments need to adapt provider-specific and organizational steps to their own environment.

Handling an incident

One team member handles the incident and names an available teammate as a backup. They coordinate investigation, containment, recovery, reporting, and user communication, asking other teammates or outside specialists for help when needed. The backup takes over when the handler is unavailable.

Use Incident reporting for reporting decisions, deadlines, and a private incident note. No separate management approval is needed to begin responding.

Logistik komunikasi

• Komunikasi Internal:

  • Saluran utama adalah Signal untuk koordinasi antarmanusia.

  • Peringatan teknis tetap berada di luar Signal untuk menghindari kebisingan.

• Komunikasi Eksternal

  • Surel digunakan untuk menjangkau pelanggan.

  • Daftar kontak pelanggan dipelihara di beberapa lokasi untuk memastikan akses selama penghentian layanan.

• Pengungkapan Publik:

  • If an incident includes a Weblate product vulnerability, follow the product vulnerability reporting process and Kebijakan pengungkapan kerentanan in Kerentanan dan penanganan insiden.

Kategori dan keparahan insiden

Incident activation

• Declare an incident when an event is confirmed or strongly suspected to affect the confidentiality, integrity, or availability of the service beyond routine operational noise.

• Whoever identifies the incident alerts teammates through Signal. An available teammate takes responsibility, records the initial severity, and names a backup.

• Reclassify the incident if the scope or impact changes during investigation.

Kategori insiden

• Kategori 1 – Akses Tidak Sah

• Kategori 2 – Pelanggaran Integritas Data

• Kategori 3 – Gangguan atau Penurunan Layanan

• Kategori 4 – Kesalahan Konfigurasi atau Galat Penyebaran

Tingkat keparahan dan SLA

These are operational response targets, not a statement of continuous staffing. Assess product-security reporting separately using Incident reporting; these targets do not extend reporting deadlines.

Keparahan	Definisi	Pengakuan Target	Tindakan Awal Target
Kritis	Total outage; Admin compromise; Active data breach; requires immediate containment.	< 30 Menit	< 4 Hours
Tinggi	Kegagalan fitur inti; Kebocoran PII pengguna tunggal.	< 2 Jam	12 Jam
Sedang	Penurunan kinerja; Isu keamanan kecil.	1 Hari Bisnis	3 Hari Bisnis
Rendah	Kesalahan UI; Isu pertahapan; Galat non-keamanan.	Upaya Terbaik	Upaya Terbaik

Siklus hidup respons insiden

Persiapan

• Pastikan pencadangan harian rutin basis data PostgreSQL dan direktori data menggunakan pencadangan bawaan Weblate dengan rotasi, lihat Mencadangkan dan memindahkan Weblate.

• Pastikan Weblate menggunakan proksi terbalik yang dikonfigurasikan dengan benar (misalnya, NGINX) dengan HTTPS (TLS 1.2+).

• Aktifkan 2FA untuk semua akun tingkat admin.

• Jaga agar instansi Weblate dan dependensinya (Python, Django, Celery, basis data, dll.) tetap terkini.

• Integrasikan dengan sistem SIEM menggunakan protokol GELF untuk audit dan penerusan catatan aplikasi.

• Complete the preparation checklist in Incident reporting and keep private contact and access details current.

Identifikasi

• Pantau catatan sistem dan aplikasi (journalctl, catatan proksi terbalik, catatan aplikasi Weblate dan catatan audit).

• Menganalisis peristiwa masuk, eksekusi kait web, dan kegagalan dorong/tarik.

• Konfigurasikan peringatan (melalui Prometheus, Zabbix, atau SIEM) untuk beberapa kegagalan masuk, pemulaian ulang yang tidak terduga, atau tindakan VCS yang tidak teratur.

• Record awareness times and assess authority and user notifications using Incident reporting, without waiting for a complete investigation.

• Assess whether a security incident caused accidental or unlawful destruction, loss, or alteration of personal data, or unauthorized disclosure or access, and follow Personal-data breach notifications. This includes availability or integrity breaches without disclosure, such as accidental deletion or ransomware destruction. Seek privacy advice where needed while continuing investigation and reporting preparation.

Personal-data breach notifications

The incident handler determines whether Weblate acts as controller or processor for the affected processing and records the assessment in the private incident note. Under GDPR Article 33:

• As controller, notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of the personal-data breach, unless the breach is unlikely to result in a risk to individuals' rights and freedoms. Record the reason for a decision not to notify.

• If notification takes longer than 72 hours, include the reasons for the delay. Where information cannot be supplied together, provide it in stages without undue further delay.

• As processor, notify the controller without undue delay after becoming aware of a personal-data breach; do not wait for the controller's 72-hour deadline.

The controller's supervisory-authority notification must include the following information under Article 33(3):

• The nature of the breach, including, where possible, the categories and approximate numbers of affected individuals and personal-data records.

• The name and contact details of the person who can provide further information, such as the incident handler or a data protection officer if one is appointed.

• The likely consequences of the breach.

• Measures taken or proposed to address the breach, including measures to reduce its adverse effects where appropriate.

Identify information that is not yet available and provide it in follow-up notifications without undue further delay. Do not wait for exact counts before notifying the authority.

As controller, separately assess communication to affected individuals under GDPR Article 34. If the breach is likely to create a high risk to their rights and freedoms, inform them without undue delay unless an Article 34(3) exception applies. This applies even without active exploitation or a severe product-security incident. Notification to the supervisory authority does not replace this communication.

Explain the breach in clear language, giving a contact for further information, likely consequences, measures taken or proposed, and actions individuals can take. Record the assessment and any exception relied on: effective protection of the affected data, such as encryption making it unreadable to unauthorized people, or subsequent measures ensuring the high risk is no longer likely. If individual communication would involve disproportionate effort, use public communication or a similar measure that informs individuals equally effectively. See the EDPB data-breach guidance.

Record breach-awareness timestamps, recipients, and deadlines separately from CRA reporting. A CRA submission does not replace a GDPR notification, and the two reporting clocks may start at different times.

Penahanan

• Maintain the private incident note from Incident reporting, including timeline updates, reporting deadlines, and submission receipts.

• Coordinate human response in Signal and keep technical alerting in the existing monitoring systems.

• For Category 1 or 2 incidents, create a manual Hetzner Cloud Snapshot before taking disruptive action when it is safe to do so.

  • Format nama: IRP-[CaseID]-[YYYYMMDD]-Evidence.

  • Cadangan ini terpisah dari cadangan berputar standar dan harus disimpan untuk dianalisis.

• Isolate the affected host or service as needed (for example by firewall rules or service isolation).

• Nonaktifkan integrasi eksternal (Git/webhook) jika merupakan bagian dari vektor serangan.

• Segera tangguhkan akun pengguna yang terpengaruh.

• Revoke or rotate affected administrative, API, VCS, and webhook credentials as applicable.

• Preserve relevant evidence, including system logs, reverse proxy logs, Weblate application and audit logs, affected configuration state, and the list of impacted credentials or integrations.

Pemberantasan

• Hapus kode atau data yang tidak sah.

• Perbaiki kerentanan yang diketahui dengan meningkatkan komponen Weblate atau server.

• Validasi integritas biner dan repositori menggunakan checksum SHA-256 atau log Git.

Pemulihan

• Pulihkan layanan atau data yang terpengaruh dari cadangan Weblate terbaru yang diketahui masih bagus.

• Perkenalkan kembali layanan secara bertahap.

• Confirm the root cause has been removed or a compensating control is in place before restoring normal traffic.

• Rotate affected credentials and verify integrity of the restored system, repositories, and configuration.

• The handler records the decision to return to normal operations, checking recovery with the backup or another teammate where practical.

• Pantau catatan dan perilaku sistem secara terus-menerus setidaknya selama 72 jam pasca-pemulihan.

Tinjauan pasca-insiden

• Timeline: Hold a short team review within 5 business days of incident closure.

• Susun garis waktu insiden lengkap dan tindakan yang diambil.

• Lakukan Root Cause Analysis (RCA) dan dokumentasikan dalam 10 hari bisnis.

• Perbarui kebijakan keamanan dan dokumentasi IRP berdasarkan temuan.

• Tinjau efektivitas mekanisme deteksi dan penahanan.

• Verify whether escalation, alerting, and external communication followed Kerentanan dan penanganan insiden as expected.

• Check for outstanding reports, promised updates, and delayed disclosures before closing the incident note.