Security Testing

<default_to_action> When testing security or conducting audits:

1. TEST OWASP Top 10 vulnerabilities systematically
2. VALIDATE authentication and authorization on every endpoint
3. SCAN dependencies for known vulnerabilities (npm audit)
4. CHECK for injection attacks (SQL, XSS, command)
5. VERIFY secrets aren't exposed in code/logs

Quick Security Checks:

• Access control → Test horizontal/vertical privilege escalation
• Crypto → Verify password hashing, HTTPS, no sensitive data exposed
• Injection → Test SQL injection, XSS, command injection
• Auth → Test weak passwords, session fixation, MFA enforcement
• Config → Check error messages don't leak info

Critical Success Factors:

• Think like an attacker, build like a defender
• Security is built in, not added at the end
• Test continuously in CI/CD, not just before release </default_to_action>

Quick Reference Card

When to Use

• Security audits and penetration testing
• Testing authentication/authorization
• Validating input sanitization
• Reviewing security configuration

OWASP Top 10 (2021)

#	Vulnerability	Key Test
1	Broken Access Control	User A accessing User B's data
2	Cryptographic Failures	Plaintext passwords, HTTP
3	Injection	SQL/XSS/command injection
4	Insecure Design	Rate limiting, session timeout
5	Security Misconfiguration	Verbose errors, exposed /admin
6	Vulnerable Components	npm audit, outdated packages
7	Auth Failures	Weak passwords, no MFA
8	Integrity Failures	Unsigned updates, malware
9	Logging Failures	No audit trail for breaches
10	SSRF	Server fetching internal URLs

Tools

Type	Tool	Purpose
SAST	SonarQube, Semgrep	Static code analysis
DAST	OWASP ZAP, Burp	Dynamic scanning
Deps	npm audit, Snyk	Dependency vulnerabilities
Secrets	git-secrets, TruffleHog	Secret scanning