TypeScript Security
Priority: P0 (CRITICAL)
Security standards for TypeScript applications based on OWASP guidelines.
Implementation Guidelines
- Validation: Use
Zod,Joi, orclass-validatorat the API boundary. Alwaysparseand validateuser-controlled inputbefore using. UsesafeParsefor error handling without throwing. Return400 with structured errorson failure. - Sanitization: Use
DOMPurifyfor HTML sanitization to prevent Cross-Site Scripting (XSS). - Secrets: Store secrets in
.env(e.g.,JWT_SECRET) or Secret Managers. NEVER commit them to Git. - Vulnerabilities: Prevent SQL Injection using Parameterized Queries (e.g.,
pool.query('... WHERE id = $1', [id])) or Type-safe ORMs (Prisma/TypeORM). UsePrisma.sqlfor raw queries. - Authentication: Use
Argon2idfor password hashing. ImplementJWT(viajsonwebtokenorjose) withHttpOnlyandSecurecookies. UseRS256for public/private key pairs and implementRefresh Token rotation. - CORS: Configure
CORSwith Strict Origin Whitelisting. Avoidorigin: '*'. - Encryption: Use
crypto(Node.js) orWeb Crypto APIfor sensitive data. Avoid legacy algorithms like MD5/SHA1. - Input Filtering: Sanitize
user-controlled inputbefore using it in file paths or OS commands (Command Injection).
Verification
After typing validation schemas (Zod/joi) or auth guards, call getDiagnostics (typescript-lsp) to confirm type narrowing is correct before finalizing.
Anti-Patterns
- No
eval(): Avoid dynamic execution. - No Plaintext: Never commit secrets.
- No Trust: Validate everything server-side.
References
See references/REFERENCE.md for Zod validation, secure cookie setup, JWT auth, security headers, and RBAC patterns.