Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Praktik terbaik untuk menggunakan Submission API
Dokumen ini menjelaskan penerapan yang direkomendasikan untuk Submission API.
Meningkatkan deteksi dengan ThreatInfo dan ThreatDiscovery
Sebaiknya gunakan kolom ThreatInfo dan ThreatDiscovery untuk memberikan informasi tambahan tentang kiriman, yang berpotensi meningkatkan deteksi dan meningkatkan kemungkinan kiriman diblokir.
Gunakan kolom ThreatInfo untuk memberikan informasi selengkapnya tentang alasan URI dikirim.
Gunakan kolom ThreatDiscovery untuk memberikan informasi selengkapnya tentang cara ancaman ditemukan.
Contoh
Penyerang meluncurkan situs phishing kredensial yang menargetkan klien bank yang berbasis di Italia. Klien yang ditargetkan mulai menerima pesan teks yang menipu dari penyerang tersebut dengan link ke halaman login palsu. Bank menerima laporan dari klien yang menerima pesan teks, meluncurkan penyelidikan, dan mengonfirmasi bahwa situs tersebut melakukan phishing untuk mendapatkan kredensial. Untuk melindungi kliennya, bank mengirimkan situs phishing ke Web Risk dengan isi permintaan berikut:
{"submission":{"uri":"http://example.com/login.html"},"threatDiscovery":{"platform":"ANDROID","regionCodes":"IT"},"threatInfo":{"abuseType":"SOCIAL_ENGINEERING","threatJustification":{"labels":["USER_REPORT","MANUAL_VERIFICATION"],"comments":"Site is impersonating a bank and phishing for login credentials"},"threatConfidence":{"level":"HIGH"}}}
Saat bank memeriksa status pengiriman dengan nama operasi yang ditampilkan oleh Submission API, statusnya adalah SUCCEEDED, yang menunjukkan bahwa URL yang dikirim telah ditambahkan ke daftar URL yang tidak diizinkan Safe Browsing.
Langkah selanjutnya
Melihat referensi API untuk ThreatInfo dan ThreatDiscovery (RPC, Rest)
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[],[],null,["# Best practices for using the Submission API\n===========================================\n\nThis document describes the recommended implementation for the Submission API.\n\nImprove detection with `ThreatInfo` and `ThreatDiscovery`\n---------------------------------------------------------\n\nWe recommend using [`ThreatInfo`](/web-risk/docs/reference/rest/v1/projects.uris/submit#threatinfo) and [`ThreatDiscovery`](/web-risk/docs/reference/rest/v1/projects.uris/submit#threatdiscovery) fields to provide additional information about submissions, which has the potential to improve detection and increase the chances of a submission being blocked.\n\n- Use `ThreatInfo` fields to provide more information about why the URI is being submitted.\n- Use `ThreatDiscovery` fields to provide more information about how the threat was found.\n\n### Example\n\nAn attacker launches a credential phishing site targeting clients of a bank based in Italy. Targeted clients begin receiving deceptive text messages from that attacker with a link to a fake login page. The bank receives reports from clients that received the texts, launches an investigation, and confirms that the site is phishing for credentials. To protect their clients, the bank submits the phishing site to Web Risk with the following request body: \n\n {\n \"submission\": {\n \"uri\": \"http://example.com/login.html\"\n },\n \"threatDiscovery\": {\n \"platform\": \"ANDROID\",\n \"regionCodes\": \"IT\"\n },\n \"threatInfo\": {\n \"abuseType\": \"SOCIAL_ENGINEERING\",\n \"threatJustification\": {\n \"labels\": [\"USER_REPORT\", \"MANUAL_VERIFICATION\"],\n \"comments\": \"Site is impersonating a bank and phishing for login credentials\"\n },\n \"threatConfidence\": {\n \"level\": \"HIGH\"\n }\n }\n }\n\nWhen the bank checks the status of the submission with the operation name returned by the Submission API, the status is `SUCCEEDED`, indicating that the submitted URL was added to the Safe Browsing blocklist.\n\nWhat's next\n-----------\n\n- View the API reference for `ThreatInfo` and `ThreatDiscovery` ([RPC](/web-risk/docs/reference/rpc/google.cloud.webrisk.v1#submiturirequest), [Rest](/web-risk/docs/reference/rest/v1/projects.uris/submit))"]]
