Internal knowledge vs client-facing articles
Overview
Leaking internal runbooks exposes attack paths—tag clearly in KB CMS.
Tag standard
internal-only vs client-portal with permission matrix.
Review
Client-facing requires marketing scrub for tone + removal of internal hostnames if sensitive.
Automation
Portal publish pipeline distinct from internal Notion/Git wikis where split.
Incident
If mis-published, revoke cache/CDN; incident ticket; lesson for RBAC tightening.
Culture
Technicians rewarded for updating stale external articles quarterly chore wheel.
Related Articles
EDR deployment checklist for new workstations
## Overview Use this runbook when onboarding a new Windows workstation or re-imaging a device that...
Handling Defender for Business false positives
## Overview False positives waste analyst time and train users to ignore alerts. This article stand...
Application allowlisting with Windows Defender ASR rules
## Overview Attack Surface Reduction (ASR) rules reduce exploit surface by constraining Office macr...