Tasks / Rightbrain Internal

Security Vulnerability Scanner

Analyses source code for security vulnerabilities, classifying them by type and severity. It then provides actionable remediation recommendations, including affected code and fix guidance, to enhance application security.

claude-sonnet-4-5
2 views
January 06, 2026

Sign up for a free trial to Clone, Customise and Run

Task Logic

User Prompt Template

CORE INSTRUCTION

Instructions sent to the model. Dynamic variables {brackets} are replaced at runtime.

Goal:
Conduct a comprehensive security analysis of source code to identify vulnerabilities, classify them by type, and provide actionable remediation recommendations.

Input Parameters:
- {source_code}: The source code to be analysed for security vulnerabilities

Processing Steps:
1. Review the provided source code systematically to identify potential security vulnerabilities
2. Examine code for common vulnerability patterns including injection flaws, authentication issues, authorisation weaknesses, cryptographic problems, input validation failures, and insecure configurations
3. Assess the severity and potential impact of each identified vulnerability
4. Classify each vulnerability by its specific type (e.g., SQL injection, XSS, insecure authentication, hardcoded credentials, etc.)
5. For each vulnerability identified, determine the root cause and affected code sections
6. Develop specific, actionable remediation recommendations for each vulnerability
7. Organise findings into a structured list grouped by vulnerability type

Output Guidance:
Present your findings as a comprehensive list with the following structure:
- For each vulnerability type, provide:
  - Vulnerability name and classification
  - Description of the security issue
  - Location or code pattern where the vulnerability exists
  - Severity level (Critical, High, Medium, Low)
  - Specific remediation recommendation with actionable steps
  - Code example or guidance for the fix where applicable
- If no vulnerabilities are found, explicitly state this and provide a brief summary of the security review conducted

Critical Rules:
- Identify all security vulnerabilities present in the code, not just the most obvious ones
- Classify vulnerabilities using standard security taxonomy (OWASP, CWE, or similar frameworks)
- Provide specific, actionable remediation guidance rather than generic security advice
- Consider both direct vulnerabilities and potential security weaknesses that could be exploited
- Do not execute or run the code; perform static analysis only
- If the code language or framework cannot be determined, state this limitation but proceed with general security analysis
- Prioritise vulnerabilities by severity to help focus remediation efforts

Interface Definition

Inputs
source_code
Text Input
Output Schema

Try this AI task with your own data

Free trial - no credit card required