From c0c54b1a0c6d66ba94bc1a68a7444b3b3da9b457 Mon Sep 17 00:00:00 2001 From: drjones Date: Wed, 20 May 2026 19:02:38 -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..066923c 100644 --- a/Security.md +++ b/Security.md @@ -0,0 +1,20 @@ +# Security + +## Risk Profile + +- Hardware/firmware changes can affect physical devices; releases need board verification, recovery notes, and checksums. +- 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.