---
title: "Security Vulnerability Scanner"
description: "Comprehensive security analysis and vulnerability assessment for code and systems"
category: "template-prompt"
tags: ["security", "vulnerability", "penetration-testing", "owasp", "code-security", "threat-analysis"]
tech_stack: ["any"]
---

# Security Vulnerability Scanner

As a cybersecurity expert, you focus on vulnerability assessment and secure coding practices. Let’s dive into your security analysis request and how to tackle it effectively.

## Security Analysis Request
- **Target**: Specify the target, whether it's an application, API, infrastructure, or a code module.
- **Security Level**: Define the security level you need: basic, enterprise, or high-security.
- **Compliance Requirements**: Identify the relevant standards like OWASP, PCI DSS, SOC2, or GDPR.
- **Technology Stack**: List the technology stack you are using.
- **Access Level**: Choose the access level: black box, white box, or code review.
- **Priority Areas**: Highlight the focus areas such as authentication, data protection, or API security.

## Code/System to Analyze
```[INSERT LANGUAGE]
[INSERT CODE OR SYSTEM DESCRIPTION]
```

## Security Assessment Framework

### 1. OWASP Top 10 Analysis
Here's what to look out for:
- **A01 - Broken Access Control**
- **A02 - Cryptographic Failures**
- **A03 - Injection**
- **A04 - Insecure Design**
- **A05 - Security Misconfiguration**
- **A06 - Vulnerable Components**
- **A07 - Authentication Failures**
- **A08 - Software/Data Integrity**
- **A09 - Logging/Monitoring Failures**
- **A10 - Server-Side Request Forgery**

### 2. Custom Security Checks
Make sure to evaluate:
- **Input Validation**
- **Output Encoding**
- **Session Management**
- **Error Handling**
- **Cryptography Implementation**

## Output Format

### Executive Summary
- **Overall Risk Level**: [LOW/MEDIUM/HIGH/CRITICAL]
- **Critical Vulnerabilities**: [COUNT]
- **Major Security Concerns**: [COUNT]
- **Compliance Status**: [COMPLIANT/NON-COMPLIANT]

### Vulnerability Report

#### CRITICAL (Fix Immediately)
1. **[VULNERABILITY NAME]**
   - **OWASP Category**: [CATEGORY]
   - **Description**: [WHAT IS VULNERABLE]
   - **Impact**: [POTENTIAL DAMAGE]
   - **Exploit Scenario**: [HOW IT CAN BE EXPLOITED]
   - **Evidence**: 
   ```[language]
   [VULNERABLE CODE SNIPPET]
   ```
   - **Fix**: 
   ```[language]
   [SECURE CODE REPLACEMENT]
   ```
   - **Priority**: Critical

#### HIGH (Fix Soon)
[Follow the same format for high-priority issues]

#### MEDIUM (Address in Next Sprint)
[Follow the same format for medium-priority issues]

#### LOW (Consider for Future)
[Follow the same format for low-priority issues]

### Security Recommendations

#### Immediate Actions (24-48 hours)
- [List urgent security fixes needed]

#### Short-term (1-2 weeks)
- [Highlight important security improvements]

#### Long-term (1-3 months)
- [Identify architectural security enhancements]

### Secure Code Examples
```[INSERT LANGUAGE]
// VULNERABLE CODE
[INSECURE EXAMPLE]

// SECURE CODE
[SECURE REPLACEMENT WITH EXPLANATION]
```

### Security Testing Plan
- **Automated Tests**: [Add security test cases]
- **Manual Testing**: [Include penetration testing checklist]
- **Code Review**: [List security-focused review points]

### Compliance Checklist
- [ ] [COMPLIANCE REQUIREMENT 1]
- [ ] [COMPLIANCE REQUIREMENT 2]
- [ ] [COMPLIANCE REQUIREMENT 3]

### Security Monitoring
- **Logging Requirements**: Specify what to log.
- **Alerting Rules**: Define when to alert.
- **Monitoring Tools**: Recommend tools for monitoring.

## Success Criteria
- Identify all critical vulnerabilities
- Provide remediation steps
- Address compliance requirements
- Create a security testing plan
- Define a monitoring strategy