From ca0bab2171f1a276070fe9e4e0bd345270f66e9e Mon Sep 17 00:00:00 2001
From: Parth Malhotra <28601533+parthmalhotra@users.noreply.github.com>
Date: Tue, 25 Jun 2024 12:05:54 +0530
Subject: [PATCH] Update kev.yml

---
 profiles/kev.yml | 21 +++++++++++++++------
 1 file changed, 15 insertions(+), 6 deletions(-)

diff --git a/profiles/kev.yml b/profiles/kev.yml
index 8c3d6f8ff9..6b43543cfd 100644
--- a/profiles/kev.yml
+++ b/profiles/kev.yml
@@ -1,9 +1,18 @@
-# This is a configuration file for the CISA KEV template profile.
-# Additional configuration profiles can be created for different types of nuclei scans.
-# They should be placed under the 'config' directory at:
-# https://github.com/projectdiscovery/nuclei-templates
-# Here is an example of how to use a config profile:
-# nuclei -config config/osint.yml -list target_list_to_scan.txt
+# Nuclei Configuration Profile for CISA KEV Detection
+#
+# This configuration file is specifically tailored for detecting Known Exploited Vulnerabilities (KEV) using Nuclei.
+#
+# Purpose:
+# This profile is focused on identifying vulnerabilities that are listed in the Cybersecurity and Infrastructure Security Agency (CISA) Known Exploited Vulnerabilities (KEV) catalog.
+# Detecting KEVs is crucial for mitigating risks associated with known and actively exploited vulnerabilities.
+#
+# Included Templates:
+# This configuration references specific templates designed to detect KEVs:
+# - tags/kev/: This directory contains templates tagged with 'kev' that are specifically focused on detecting known exploited vulnerabilities.
+#
+# Running this profile
+# You can run this profile using the following command:
+# nuclei -profile kev -u https://example.com
 
 tags:
   - kev