Detailed wiki content repair: Security
19
Security.md
19
Security.md
@@ -0,0 +1,19 @@
|
||||
# Security
|
||||
|
||||
## Risk Profile
|
||||
|
||||
- Security-sensitive repository; documentation is scoped to authorized lab, defensive, or research use.
|
||||
|
||||
## Handling Rules
|
||||
|
||||
- Do not commit credentials, tokens, cookies, keys, private logs, captures, card data, or personal data.
|
||||
- Keep generated dependency trees, copied SDKs, and build output out of Git unless explicitly documented as source.
|
||||
- For security-sensitive projects, keep docs scoped to authorized lab, research, or defensive maintenance.
|
||||
- Treat unknown-origin binaries as blocked until provenance is recorded.
|
||||
|
||||
## Review Checklist
|
||||
|
||||
- [ ] Search the repository for secrets and private data.
|
||||
- [ ] Confirm dependency sources and upstream license status.
|
||||
- [ ] Confirm generated artifacts are ignored or moved to releases.
|
||||
- [ ] Confirm project-specific safe-use boundaries are written in README and release notes.
|
||||
|
||||
Reference in New Issue
Block a user