Skip to content

Commit d556ad0

Browse files
author
mrachidi
committed
adding all tools needed for Vulnerability Intelligence MCP Server
1 parent e590d21 commit d556ad0

File tree

1 file changed

+7
-16
lines changed

1 file changed

+7
-16
lines changed

security_tests_scenario.md

Lines changed: 7 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -7,51 +7,42 @@ Here are 7 realistic prompts that tell the story of how a security engineer uses
77

88
### 1️⃣ **CVE Details Lookup** - "What exactly is this vulnerability?"
99
```
10-
"Hey, I just got an alert about CVE-2021-44228 affecting our Java applications. So I can brief my team. Only use CVE Lookup"
11-
12-
Test with: lookup_cve("CVE-2021-44228")
10+
Hey, I just got an alert about CVE-2021-44228 affecting our Java applications. So I can brief my team. Only use CVE Lookup
1311
```
1412

1513
### 2️⃣ **EPSS Score Lookup** - "How likely is this to be exploited?"
1614
```
17-
"Now that I understand what CVE-2021-44228 is, I need to prioritize this among our 500+ other vulnerabilities. What's the EPSS score?. Only use EPSS tool"
18-
19-
Test with: get_epss_score("CVE-2021-44228")
15+
Now that I understand what CVE-2021-44228 is, I need to prioritize this among our 500+ other vulnerabilities. What's the EPSS score?. Only use EPSS tool
2016
```
2117

2218
### 3️⃣ **CVSS Score Calculator** - "How bad could this vulnerability be IF exploited?
2319
```
24-
"I want to double-check the CVSS score for this vulnerabilty."
20+
I want to double-check the CVSS score for this vulnerabilty.
2521
26-
Test with: calculate_cvss_score("CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H")
2722
```
2823

2924
### 4️⃣ **Vulnerability Search** - "Are there other related threats?"
3025
```
31-
"Since we're dealing with a critical Log4j issue, I want to search for other recent Apache vulnerabilities that might affect us. Can you search for Apache-related vulnerabilities from the last year with HIGH or CRITICAL severity? I need to see if we have a pattern of Apache security issues we should address holistically."
26+
Since we're dealing with a critical Log4j issue, I want to search for other recent Apache vulnerabilities that might affect us. Can you search for Apache-related vulnerabilities from the last year with HIGH or CRITICAL severity? I need to see if we have a pattern of Apache security issues we should address holistically.
3227
33-
Test with: search_vulnerabilities(keywords="apache", severity="HIGH", date_range="1y")
3428
```
3529

3630
### 5️⃣ **Exploit Availability** - "Are attackers already using this?"
3731
```
38-
"This CVE-2021-44228 is looking serious. Before I recommend emergency patching to the Chief Security Officer, I need to know: are there public exploits available? Are we seeing active exploitation in the wild? Check all the usual sources - GitHub, ExploitDB, Metasploit modules. This will determine if we go into crisis mode or proceed with controlled patching."
32+
This CVE-2021-44228 is looking serious. Before I recommend emergency patching to the Chief Security Officer, I need to know: are there public exploits available? Are we seeing active exploitation in the wild? Check all the usual sources - GitHub, ExploitDB, Metasploit modules. This will determine if we go into crisis mode or proceed with controlled patching.
3933
40-
Test with: get_exploit_availability("CVE-2021-44228")
4134
```
4235

4336
### 6️⃣ **Vulnerability Timeline** - "When was this disclosed and what's the patch status?"
4437
```
45-
"I need to understand the timeline for CVE-2021-44228. When was it first published? How long has it been public? Are patches available from vendors? This information will help me explain to leadership why we might have been caught off-guard and what our remediation timeline should look like."
38+
I need to understand the timeline for CVE-2021-44228. When was it first published? How long has it been public? Are patches available from vendors? This information will help me explain to leadership why we might have been caught off-guard and what our remediation timeline should look like.
4639
47-
Test with: get_vulnerability_timeline("CVE-2021-44228")
4840
```
4941

5042
### 7️⃣ **VEX Status** - "Is our specific Apache deployment affected?"
5143
```
52-
"Finally, I need to check the VEX status for CVE-2021-44228 specifically for our Apache HTTP Server deployments. We have Apache HTTP Server 2.4.51 running on our web servers. Has Apache provided any VEX statements about whether their HTTP server is affected by this Log4j vulnerability? I need product-specific guidance to determine our actual exposure."
44+
Finally, I need to check the VEX status for CVE-2021-44228 specifically for our Apache HTTP Server deployments. We have Apache HTTP Server 2.4.51 running on our web servers. Has Apache provided any VEX statements about whether their HTTP server is affected by this Log4j vulnerability? I need product-specific guidance to determine our actual exposure.
5345
54-
Test with: get_vex_status("CVE-2021-44228", "Apache HTTP Server")
5546
```
5647

5748
## 🎯 **The Complete Story Arc**

0 commit comments

Comments
 (0)