From 5282643b445ca8d2b9c9c7d39ad3d6f86a513e2d Mon Sep 17 00:00:00 2001 From: drjones Date: Wed, 20 May 2026 19:04:29 -0700 Subject: [PATCH] Detailed wiki content repair: Security --- Security.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/Security.md b/Security.md index e69de29..09ec423 100644 --- a/Security.md +++ b/Security.md @@ -0,0 +1,20 @@ +# Security + +## Risk Profile + +- Automation projects can carry account/session risk; never commit tokens, cookies, private data, or scraped content. +- 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.