From 979915530542781bf57704cf713afc10afc561f3 Mon Sep 17 00:00:00 2001 From: RootGuard Date: Tue, 20 Oct 2026 19:32:16 +0100 Subject: [PATCH 1/4] docs: remove internal governance and project roadmap from public GitBook navigation --- SUMMARY.md | 27 +++++---------------------- 1 file changed, 5 insertions(+), 22 deletions(-) diff --git a/SUMMARY.md b/SUMMARY.md index 0c1a138..eff2044 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -2,35 +2,18 @@ ## Welcome -* [RootGuard 3.0 Quality and Maturity Roadmap](contributing/rootguard-3-quality-roadmap.md) -* [Enterprise Security Architecture Assessment](security-architecture/enterprise-security-assessment.md) -* [Incident Response Handoff Checklist](defensive-security/dfir/end-to-end-playbooks/response-handoff-checklist.md) - -* [Documentation Design System](design-system/README.md) - * [Diagram Patterns](design-system/diagram-patterns.md) - -* [Start Here](start-here/README.md) -* [Guided Learning Paths](learning-paths/README.md) -* [Security Architecture & Engineering](security-architecture/README.md) -* [Documentation Standards](contributing/README.md) - * [Technical Content Review Register](contributing/content-review-register.md) - * [Detection Guide Template](contributing/templates/detection-guide.md) - * [Incident Playbook Template](contributing/templates/incident-playbook.md) - * [Architecture Decision Template](contributing/templates/architecture-decision.md) - - * [RootGuard](README.md) + * [Start Here](start-here/README.md) * [About the Author](welcome/who-am-i/README.md) * [Professional Profile](welcome/who-am-i/professional-profile.md) - -## Runbook Technical Assurance - -* [Runbook Safety and Validation Standard](defensive-security/dfir/runbooks/runbook-technical-safety-standard.md) -* [Runbook Execution and Validation Matrix](defensive-security/dfir/runbooks/runbook-execution-validation-matrix.md) +* [Guided Learning Paths](learning-paths/README.md) +* [Security Architecture & Engineering](security-architecture/README.md) + * [Enterprise Security Architecture Assessment](security-architecture/enterprise-security-assessment.md) ## End-to-End Incident Playbooks * [Incident Investigation Playbooks](defensive-security/dfir/end-to-end-playbooks/README.md) + * [Incident Response Handoff Checklist](defensive-security/dfir/end-to-end-playbooks/response-handoff-checklist.md) * [Phishing Compromise](defensive-security/dfir/end-to-end-playbooks/phishing-compromise.md) * [Ransomware](defensive-security/dfir/end-to-end-playbooks/ransomware.md) * [Credential Theft](defensive-security/dfir/end-to-end-playbooks/credential-theft.md) From 9d2c5f56e883599e5fbb32e21c72b021b4642c1f Mon Sep 17 00:00:00 2001 From: RootGuard Date: Tue, 20 Oct 2026 19:32:32 +0100 Subject: [PATCH 2/4] docs: remove internal roadmap and editorial guidance from public entry points --- contributing/README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/contributing/README.md b/contributing/README.md index a279b9c..7b87bfe 100644 --- a/contributing/README.md +++ b/contributing/README.md @@ -1,7 +1,5 @@ # RootGuard Documentation Standards -See the [RootGuard 3.0 Technical Quality Roadmap](rootguard-3-quality-roadmap.md) for the current quality baseline, outstanding reviews and acceptance criteria. - Follow the [RootGuard Documentation Design System](../design-system/README.md) for visual hierarchy, metadata, and diagram conventions. Use the [Operational Article Template](templates/operational-article.md) for new practitioner workflows. [Technical Content Review Register](content-review-register.md) tracks prioritised legacy corrections and validation status. From b89084b6da13d25b41f68c46a6c29169780c580b Mon Sep 17 00:00:00 2001 From: RootGuard Date: Tue, 20 Oct 2026 19:32:35 +0100 Subject: [PATCH 3/4] docs: remove internal roadmap and editorial guidance from public entry points --- README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/README.md b/README.md index bdade41..e29f1be 100644 --- a/README.md +++ b/README.md @@ -53,8 +53,6 @@ RootGuard is an independent technical reference for security practitioners inves ## How to use this reference -For consistent article layouts and diagrams, see the [RootGuard documentation design system](design-system/README.md). - **1. Check the prerequisites.** Identify the product and query execution environment, the required audit settings, retention and permissions. **2. Investigate, then corroborate.** A matching event is an observation, not a finding of compromise. Correlate multiple sources and document limitations. From dcfe94dde4868eeacbb5de01a4f30abadb3358f8 Mon Sep 17 00:00:00 2001 From: RootGuard Date: Tue, 20 Oct 2026 19:32:38 +0100 Subject: [PATCH 4/4] docs: unpublish internal development roadmap from GitBook source --- contributing/rootguard-3-quality-roadmap.md | 36 --------------------- 1 file changed, 36 deletions(-) delete mode 100644 contributing/rootguard-3-quality-roadmap.md diff --git a/contributing/rootguard-3-quality-roadmap.md b/contributing/rootguard-3-quality-roadmap.md deleted file mode 100644 index 1fec13a..0000000 --- a/contributing/rootguard-3-quality-roadmap.md +++ /dev/null @@ -1,36 +0,0 @@ -# RootGuard 3.0: Technical Quality and Operational Maturity - -**Baseline:** 20 October 2026. **Repository inventory:** 306 Markdown documents (including navigation and templates). This is a file-count inventory, **not** a claim that 306 pages were technically reviewed. - -## Milestone 1: Technical assurance - -| Workstream | Deliverable | Acceptance evidence | -| --- | --- | --- | -| Repository hygiene | Automated syntax/content integrity checks | GitHub Actions passes and reports scope | -| Priority safety | Reviewed high-impact runbooks with known risks addressed or restricted | Technical review register and documented exception | -| Query assurance | Per-query reviewer worksheet | Correct execution portal, schema, permissions, positive/negative checks and result | -| Technical accuracy | Review queue prioritised by reader impact | Per-article owner, evidence and status | - -## Milestone 2: Operational maturity - -Four operational incident playbooks contain triage, scoping, KQL investigation pivots, response decisions and recovery criteria. The [response handoff checklist](../defensive-security/dfir/end-to-end-playbooks/response-handoff-checklist.md) standardises analyst handover and escalation. Production testing remains pending. - -## Milestone 3: Documentation consistency - -Use the [design system](../design-system/README.md) and [operational article template](templates/operational-article.md) for all substantial updates. Preserve URLs, explicit review dates, authorisation requirements and links. A passing Markdown/link check is **not** technical validation. - -## Milestone 4: Technical depth - -Introduce a substantive [security architecture assessment workflow](../security-architecture/enterprise-security-assessment.md) connecting identity, control placement, telemetry, response, business requirements and measurable verification. - -## Remaining backlog - -- **Critical:** Execute and attest each of the remaining legacy KQL and PowerShell examples in the correct product/module context. -- **High:** Complete article-by-article technical audits of the older DFIR, detection and offensive-security references. -- **High:** Review all state-changing snippets and require case-specific approvals. -- **Medium:** Compare remaining duplicated reference pages and consolidate without breaking published URLs. -- **Medium:** Verify rendered GitBook site appearance and responsive layouts after administrator customisation. - -## Release discipline - -A document may be marked **Static reviewed** only for the specific checks performed. Do not mark any item lab-validated without executable test cases and redacted outcomes. Track deficiencies rather than assuming they do not exist.