-
Notifications
You must be signed in to change notification settings - Fork 0
Security
Lucas YourLastName edited this page Jul 17, 2026
·
2 revisions
SFWA-WTL-G1 is a template, not a completed security program. Every downstream project must own its threat model, Firebase rules, IAM, billing controls, dependency updates, monitoring, backups, legal review, and incident response.
- Never commit
.env.local, service-account JSON, private keys, refresh tokens, legacy Firebase tokens, Stripe secret keys, or production exports. - Use local interactive login for developers and OIDC or Application Default Credentials for CI.
- Use least privilege and target local emulators or staging before production.
- Keep optional MCP servers disabled until a bounded task requires them.
- Run
npm run ci:security,npm audit --audit-level=high, and CodeQL. - Review Firestore and Storage rules before every release.
SYSTEMX state is non-secret and ignored. Logs are sanitized JSONL, rotate at 5 MB, redact credential-shaped values, and never dump the environment. Windows uses NTFS ACLs for protected local files; POSIX systems use owner-only mode.
Report vulnerabilities through GitHub private vulnerability reporting rather than a public issue.
SFWA-WTL-G1 · Standard Firebase Web App, Wayne Tech Lab Generation 1 · Provided by Wayne Tech Lab LLC under MIT · Use at your own risk · Subject to daily change · Repository
- Home
- Quick Start
- WTL Standard Setup Guide
- One-Line Install
- Platform Matrix
- Linux Setup
- Windows Setup
- Architecture and Stack
- Project Structure
- SYSTEMX Root and Folder Standard
- Setup Playbook
- Environment Variables
- Security
- Deployment
- Testing and QA
- MCP and Agents
- GitHub Authors and Contribution Notes
- SYSTEMX WEBPORTAL
- White Paper
- Executive Summary
- CISO Note From the Founder
- Wayne Tech Lab Purpose
- Security Overview
- Long-Term Warnings
- .ENV Solutions
- Menu Operations
- Setup and Deployment
- Start and End of Day
- SYSTEMX Sync and Controlled Updates
- Agent 0 and Subagents
- Agent 0 Operating Model
- How Subagents Work
- Starter Prompts and Smart Routing
- Third-Party Responsibility
- User Ingest and Production Setup
- FAQ