Intelijen Ancaman & Manajemen Kerentanan
Pelajari cara melacak kerentanan, memprioritaskannya dengan CVSS dan intelijen ancaman, serta menjalankan siklus remediasi berkelanjutan dalam pipeline DevSecOps.
Intelijen Ancaman & Manajemen Kerentanan adalah pelajaran Secure Coding & OWASP Top 10 for Backend gratis di CoddyKit. Ini adalah pelajaran 4 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Secure Coding & OWASP Top 10 for Backend, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Secure Coding & OWASP Top 10 for Backend mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
Why Vulnerability Management?
New vulnerabilities appear daily. Vulnerability management is the ongoing process of discovering, prioritizing, and remediating weaknesses before attackers exploit them. It is a continuous loop, not a one-time scan.
The Management Lifecycle
The lifecycle has clear stages:
- Discover: find vulnerabilities via scans and feeds
- Prioritize: rank by risk
- Remediate: patch, mitigate, or accept
- Verify: confirm the fix
- Report: track metrics over time
CVE and CVSS
A CVE is a unique identifier for a known vulnerability. CVSS is a 0-10 score describing severity based on factors like attack vector and impact. CVSS gives a baseline, but it is not the whole story.
Reading a CVSS Score
CVSS bands roughly map to urgency. Use them to triage, but always combine with context.
def severity(score):
if score >= 9.0:
return 'Critical'
if score >= 7.0:
return 'High'
if score >= 4.0:
return 'Medium'
if score > 0.0:
return 'Low'
return 'None'
for s in [9.8, 7.5, 4.3, 2.1]:
print(s, severity(s))Threat Intelligence
Threat intelligence adds real-world context: Is this CVE being actively exploited? Is there public exploit code? Feeds like CISA KEV and EPSS help you focus on what attackers are actually using right now.
Risk-Based Prioritization
Severity alone is misleading. A medium-CVSS bug under active exploitation on an internet-facing system may outrank a critical bug on an isolated internal tool. Combine severity, exploitability, and asset exposure.
def priority(cvss, exploited, internet_facing):
score = cvss
if exploited:
score += 3
if internet_facing:
score += 2
return round(min(score, 15), 1)
print(priority(5.0, True, True)) # medium CVE but urgent
print(priority(9.0, False, False)) # critical but isolatedSoftware Bill of Materials
An SBOM lists every component and version in your software. When a new CVE drops, an SBOM lets you instantly answer: are we affected, and where?
Integrating into CI/CD
In DevSecOps, vulnerability scanning runs automatically on every build: dependency scanning, container image scanning, and IaC scanning. Builds can fail when a new critical issue is found, shifting detection left.
Remediation Options
Remediation is not always a patch. Your options are:
- Patch or upgrade the component
- Mitigate with a workaround or compensating control
- Accept the risk formally if impact is low
Track each decision with an owner and a deadline.
SLAs and Metrics
Define remediation SLAs by severity (for example, critical within days, high within weeks). Track metrics like mean time to remediate so the program improves measurably over time.
Feeding Incident Response
Vulnerability data and threat intel inform incident response: knowing which CVEs are exploited helps responders recognize attacks faster and patch the right systems first during an incident.
Quick Check
Test your understanding of vulnerability management.
Recap
You learned the vulnerability management lifecycle, how to read CVSS, and how threat intelligence and SBOMs enable risk-based prioritization. Integrating scanning into CI/CD, setting remediation SLAs, and feeding incident response close the loop in a mature DevSecOps program.
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Intelijen Ancaman & Manajemen Kerentanan” gratis?
Ya — teks lengkap “Intelijen Ancaman & Manajemen Kerentanan” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Secure Coding & OWASP Top 10 for Backend, upgrade ke CoddyKit PRO. Kursus Secure Coding & OWASP Top 10 for Backend mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Intelijen Ancaman & Manajemen Kerentanan”?
Pelajari cara melacak kerentanan, memprioritaskannya dengan CVSS dan intelijen ancaman, serta menjalankan siklus remediasi berkelanjutan dalam pipeline DevSecOps. Kamu berlatih Secure Coding & OWASP Top 10 for Backend dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai Secure Coding & OWASP Top 10 for Backend?
Tidak diperlukan pengalaman sebelumnya. Secure Coding & OWASP Top 10 for Backend di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 4 dari 4.
Berapa lama pelajaran “Intelijen Ancaman & Manajemen Kerentanan” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran Secure Coding & OWASP Top 10 for Backend ini?
Ya. Setiap pelajaran Secure Coding & OWASP Top 10 for Backend menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Mengintegrasikan Keamanan ke dalam CI/CD (DevSecOps)
- Pengujian Keamanan (SAST, DAST, IAST)
- Respons Insiden dan Pemulihan Bencana
- Intelijen Ancaman & Manajemen Kerentanan