Security Test Scanner
Overview
Automate security vulnerability detection covering OWASP Top 10 categories including SQL injection, XSS, CSRF, broken authentication, and sensitive data exposure. Combines static analysis (source code scanning with Semgrep, Bandit, ESLint security plugins) with dynamic testing patterns (input fuzzing, header validation, authentication bypass checks).
Prerequisites
- Static analysis tools installed (Semgrep, ESLint with
eslint-plugin-security, Bandit for Python, or SpotBugs for Java)
- Application running in a test environment (never scan production without explicit authorization)
- Written authorization to perform security testing on the target system
npm audit, pip-audit, or trivy for dependency vulnerability scanning
- OWASP ZAP or Burp Suite for dynamic application security testing (optional)
Instructions
- Run dependency vulnerability scanning to identify known CVEs:
- Execute
npm audit --json or pip-audit --format json or trivy fs ..
- Parse results and flag critical/high severity vulnerabilities.
- Check if vulnerable dependencies have available patches.
- Perform static application security testing (SAST) on source code:
- Run Semgrep with OWASP rulesets:
semgrep --config=p/owasp-top-ten.
- Execute language-specific scanners (Bandit for Python, ESLint security for JS).
- Scan for hardcoded secrets using
gitleaks or trufflehog.
- Analyze code for injection vulnerabilities:
- Search for string concatenation in SQL queries (use Grep for patterns like
"SELECT.*" +).
- Identify unsanitized user input flowing into
innerHTML, eval(), or exec().
- Check for command injection via
child_process.exec() or os.system() with user input.
- Validate authentication and authorization:
- Verify password hashing uses bcrypt, scrypt, or Argon2 (not MD5/SHA1).
- Check JWT token validation includes expiration, issuer, and audience claims.
- Ensure authorization checks exist on every protected endpoint.
- Test for common web vulnerabilities:
- CSRF: Verify anti-CSRF tokens on state-changing endpoints.
- CORS: Check
Access-Control-Allow-Origin is not set to * on authenticated endpoints.
- Security headers: Validate presence of
Content-Security-Policy, X-Frame-Options, Strict-Transport-Security.
- Generate a prioritized findings report with:
- CVSS score for each vulnerability.
- Affected file, line number, and code snippet.
- Specific remediation steps with code examples.
- Create regression tests for each finding to prevent reintroduction.
Output
- Security scan report in Markdown with findings sorted by severity
- Dependency vulnerability list with CVE IDs and available patches
- SAST findings with file paths, line numbers, and code context
- Remediation checklist with specific code fixes for each finding
- Security regression test file to prevent reintroduction of fixed vulnerabilities
Error Handling
| Error |
Cause |
Solution |
| False positive on SQL injection |
ORM parameterized queries flagged as concatenation |
Add Semgrep nosemgrep comments on verified safe patterns; tune rules to recognize the ORM |
| Secret scanner flags test fixtures |
Test files contain example API keys or tokens |
Add test directories to .gitleaksignore; use obviously fake values like test-key-000 |
| Dependency audit returns hundreds of results |
Transitive dependencies with low-severity issues |
Filter to direct dependencies first; focus on critical/high only; use npm audit --omit=dev |
| Scanner cannot reach application |
Application not running or port mismatch |
Start the application before dynamic scans; verify the base URL and port configuration |
| Rate limiting blocks scan |
Too many requests from the scanner |
Configure scan throttling; use authenticated sessions with higher rate limits |
Examples
Semgrep scan for OWASP Top 10:
semgrep --config=p/owasp-top-ten --json --output=security-results.json .
Checking for hardcoded secrets:
gitleaks detect --source=. --report-format=json --report-path=secrets-report.json
Security regression test (Jest):
describe('Security: XSS Prevention', () => {
it('escapes HTML entities in user-generated content', () => {
const input = '<script>alert("xss")</script>';
const rendered = renderUserComment(input);
expect(rendered).not.toContain('<script>');
expect(rendered).toContain('<script>');
});
it('rejects SQL injection in search parameter', async () => {
const response = await request(app)
.get('/api/search?q='; DROP TABLE users; --')
.expect(200); # HTTP 200 OK
expect(response.body.results).toBeDefined();
// Verify users table still exists
const users = await db.query('SELECT count(*) FROM users');
expect(users.rows[0].count).toBeGreaterThan(0);
});
});
Resources
1---2name: performing-security-testing3description: Test automate security vulnerability testing covering OWASP Top 10, SQL injection, XSS, CSRF, and authentication issues. Use when performing security assessments, penetration tests, or vulnerability scans. Trigger with phrases like "scan for vulnerabilities", "test security", or "run penetration test".4license: MIT5---6# Security Test Scanner
7
8## Overview
9
10Automate security vulnerability detection covering OWASP Top 10 categories including SQL injection, XSS, CSRF, broken authentication, and sensitive data exposure. Combines static analysis (source code scanning with Semgrep, Bandit, ESLint security plugins) with dynamic testing patterns (input fuzzing, header validation, authentication bypass checks).
11
12## Prerequisites
13
14- Static analysis tools installed (Semgrep, ESLint with `eslint-plugin-security`, Bandit for Python, or SpotBugs for Java)
15- Application running in a test environment (never scan production without explicit authorization)
16- Written authorization to perform security testing on the target system
17- `npm audit`, `pip-audit`, or `trivy` for dependency vulnerability scanning
18- OWASP ZAP or Burp Suite for dynamic application security testing (optional)
19
20## Instructions
21
221. Run dependency vulnerability scanning to identify known CVEs:
23 - Execute `npm audit --json` or `pip-audit --format json` or `trivy fs .`.
24 - Parse results and flag critical/high severity vulnerabilities.
25 - Check if vulnerable dependencies have available patches.
262. Perform static application security testing (SAST) on source code:
27 - Run Semgrep with OWASP rulesets: `semgrep --config=p/owasp-top-ten`.
28 - Execute language-specific scanners (Bandit for Python, ESLint security for JS).
29 - Scan for hardcoded secrets using `gitleaks` or `trufflehog`.
303. Analyze code for injection vulnerabilities:
31 - Search for string concatenation in SQL queries (use Grep for patterns like `"SELECT.*" +`).
32 - Identify unsanitized user input flowing into `innerHTML`, `eval()`, or `exec()`.
33 - Check for command injection via `child_process.exec()` or `os.system()` with user input.
344. Validate authentication and authorization:
35 - Verify password hashing uses bcrypt, scrypt, or Argon2 (not MD5/SHA1).
36 - Check JWT token validation includes expiration, issuer, and audience claims.
37 - Ensure authorization checks exist on every protected endpoint.
385. Test for common web vulnerabilities:
39 - CSRF: Verify anti-CSRF tokens on state-changing endpoints.
40 - CORS: Check `Access-Control-Allow-Origin` is not set to `*` on authenticated endpoints.
41 - Security headers: Validate presence of `Content-Security-Policy`, `X-Frame-Options`, `Strict-Transport-Security`.
426. Generate a prioritized findings report with:
43 - CVSS score for each vulnerability.
44 - Affected file, line number, and code snippet.
45 - Specific remediation steps with code examples.
467. Create regression tests for each finding to prevent reintroduction.
47
48## Output
49
50- Security scan report in Markdown with findings sorted by severity
51- Dependency vulnerability list with CVE IDs and available patches
52- SAST findings with file paths, line numbers, and code context
53- Remediation checklist with specific code fixes for each finding
54- Security regression test file to prevent reintroduction of fixed vulnerabilities
55
56## Error Handling
57
58| Error | Cause | Solution |
59|-------|-------|---------|
60| False positive on SQL injection | ORM parameterized queries flagged as concatenation | Add Semgrep `nosemgrep` comments on verified safe patterns; tune rules to recognize the ORM |
61| Secret scanner flags test fixtures | Test files contain example API keys or tokens | Add test directories to `.gitleaksignore`; use obviously fake values like `test-key-000` |
62| Dependency audit returns hundreds of results | Transitive dependencies with low-severity issues | Filter to direct dependencies first; focus on critical/high only; use `npm audit --omit=dev` |
63| Scanner cannot reach application | Application not running or port mismatch | Start the application before dynamic scans; verify the base URL and port configuration |
64| Rate limiting blocks scan | Too many requests from the scanner | Configure scan throttling; use authenticated sessions with higher rate limits |
65
66## Examples
67
68**Semgrep scan for OWASP Top 10:**
69
70```bash
71semgrep --config=p/owasp-top-ten --json --output=security-results.json .
72```
73
74**Checking for hardcoded secrets:**
75
76```bash
77gitleaks detect --source=. --report-format=json --report-path=secrets-report.json
78```
79
80**Security regression test (Jest):**
81
82```typescript
83describe('Security: XSS Prevention', () => {
84 it('escapes HTML entities in user-generated content', () => {
85 const input = '<script>alert("xss")</script>';
86 const rendered = renderUserComment(input);
87 expect(rendered).not.toContain('<script>');
88 expect(rendered).toContain('<script>');
89 });
90
91 it('rejects SQL injection in search parameter', async () => {
92 const response = await request(app)
93 .get('/api/search?q='; DROP TABLE users; --')
94 .expect(200); # HTTP 200 OK
95 expect(response.body.results).toBeDefined();
96 // Verify users table still exists
97 const users = await db.query('SELECT count(*) FROM users');
98 expect(users.rows[0].count).toBeGreaterThan(0);
99 });
100});
101```
102
103## Resources
104
105- OWASP Top 10: https://owasp.org/www-project-top-ten/
106- Semgrep rules registry: https://semgrep.dev/explore
107- Bandit (Python SAST): https://bandit.readthedocs.io/
108- Gitleaks secret detection: https://github.com/gitleaks/gitleaks
109- npm audit documentation: https://docs.npmjs.com/cli/commands/npm-audit
110- OWASP ASVS (Application Security Verification Standard): https://owasp.org/www-project-application-security-verification-standard/