PlanetScale Security Checklist
Last updated: January 12, 2026
Use this checklist to ensure your PlanetScale application is secure before launch. 5 critical items require immediate attention.
Why This Security Checklist Matters
Security checklists serve as systematic guides for identifying vulnerabilities that might otherwise be overlooked during rapid development cycles. For PlanetScale applications specifically, this checklist addresses the most common security gaps that emerge when using AI-assisted development workflows.
Research from multiple security organizations indicates that approximately 80% of AI-built applications contain at least one exploitable vulnerability at launch. The vulnerabilities are often predictable—they follow patterns that this checklist is designed to catch. By systematically reviewing each item, you significantly reduce the risk of launching an insecure application.
Unlike generic security checklists, this guide focuses specifically on vulnerabilities prevalent in PlanetScale applications. Each item has been prioritized based on real-world attack patterns and the potential impact of exploitation. Critical items should be addressed before any production deployment.
Critical Priority
Critical items can lead to complete application compromise, data breaches, or unauthorized access to all user accounts. These must be addressed before deploying to production. Attackers actively scan for these vulnerabilities.
High Priority
High priority items represent significant security risks that could allow unauthorized access to sensitive data or functionality. While not immediately catastrophic, these vulnerabilities should be fixed as soon as possible.
Medium/Low Priority
Medium and low priority items strengthen your overall security posture. While they may not be immediately exploitable, addressing them prevents attack chains and defense-in-depth gaps.
Manual vs Automated Security Checking
While manual security reviews are thorough, they're time-consuming and prone to human error. Automated scanning catches common vulnerabilities instantly, freeing you to focus on business logic and complex security decisions.
Items VAS Automates
- Exposed API keys and secrets in JavaScript bundles
- HTTP security header configuration
- Supabase RLS policy testing
- Firebase Security Rules validation
- Cookie security attributes
Manual Review Still Required
- Business logic vulnerabilities
- Custom authentication implementations
- Access control logic in API routes
- Data validation requirements
- Third-party integration security
Connection Security
Use PlanetScale connection strings securely
AutoStore connection strings in environment variables, not code
SSL is required by default
PlanetScale enforces SSL - ensure your client supports it
Use separate passwords per environment
Create different credentials for dev, staging, production
Rotate passwords regularly
Periodically rotate database passwords
Branch Security
Use branches for safe schema changes
Test schema changes in branches before deploying to production
Protect production branch
Enable production branch protection to require deploy requests
Review deploy requests carefully
Schema changes should be reviewed for security implications
Clean up unused branches
Delete old branches to reduce attack surface
Application Security
Implement application-level access control
PlanetScale doesn't have RLS - enforce access control in your app
Use parameterized queries
Prevent SQL injection with prepared statements
Validate all user input
MySQL is vulnerable to injection - validate input thoroughly
Use an ORM for safer queries
ORMs like Prisma and Drizzle handle parameterization
Audit & Monitoring
Enable query insights
Monitor query patterns for unusual activity
Review audit logs
Check access logs for unauthorized access attempts
Set up alerts for unusual activity
Configure alerts for spikes in queries or errors
Monitor branch usage
Track which branches are active and who's accessing them
Don't Check Manually
VAS automatically checks 1 of these 16 items. Get instant results with detailed remediation guidance.
Run Automated Security ScanFrequently Asked Questions
What's the difference between critical and high priority items?
Critical items represent immediate security risks that could lead to data breach if not addressed - like missing database access controls or exposed secrets. High priority items are important but typically require an additional vulnerability to exploit.
Can I skip low priority items?
Low priority items provide defense-in-depth but aren't immediate risks. Address all critical and high items before launch. Low items can be added post-launch, but shouldn't be ignored entirely - they protect against edge cases and future vulnerabilities.
How often should I re-run this checklist?
Re-run after major feature additions, authentication changes, or new database tables. Set up automated scanning with VAS to catch regressions. Many teams integrate security scans into their CI/CD pipeline for continuous verification.
What does 'Auto-Scanned' mean on checklist items?
Items marked 'Auto-Scanned' can be automatically verified by VAS. Instead of manually checking each item, run a VAS scan to instantly verify these items against your deployed application. Non-automated items require manual verification.