Brainforge Knowledge

README

2 min read

LinkedIn Publishing Incidents

Purpose: Track any incidents where sensitive data was published or nearly published Status: Active incident log

Purpose

This directory logs all LinkedIn publishing incidents to:

  • Document what went wrong
  • Track remediation actions
  • Identify patterns to prevent future incidents
  • Maintain accountability

When to Create an Incident Report

Create a report when:

  • Sensitive client data was published
  • Internal information was leaked
  • A post had to be deleted after publishing
  • A near-miss was caught before publishing (optional, but helpful for learning)

Incident Report Template

When creating a new incident report, use this filename format:

YYYY-MM-DD-brief-description.md

Example: 2026-02-12-client-metrics-leak.md

Template Contents:

# Incident Report: [Brief Title]
 
**Date**: YYYY-MM-DD  
**Reporter**: [Name]  
**Severity**: [Critical / High / Medium / Low]  
**Status**: [Resolved / In Progress / Monitoring]
 
---
 
## What Happened
 
[Describe what was published and when]
 
## What Was Sensitive
 
[Describe the sensitive information that was leaked]
 
## Impact
 
- **Client Impacted**: [Client name or "N/A"]
- **Public Exposure**: [How long was it public? How many views?]
- **Client Notification**: [Was client notified? How did they respond?]
 
## Root Cause
 
[What step(s) of the checklist were skipped or failed?]
 
## Remediation Actions Taken
 
1. [Action 1 - e.g., Post deleted at XX:XX]
2. [Action 2 - e.g., Client contacted at XX:XX]
3. [Action 3 - e.g., Team notified via Slack]
 
## Prevention Actions
 
[What changes are being made to prevent this in the future?]
 
## Lessons Learned
 
[Key takeaways for the team]
 
---
 
**Reviewed By**: [GTM Lead]  
**Date Closed**: [Date or "Open"]

Incident Severity Levels

Critical

  • Client data publicly exposed
  • Legal or contractual breach
  • Credentials or API keys leaked
  • Immediate client escalation required

High

  • Internal proprietary information leaked
  • Pricing or financial data exposed
  • Client identifiable from context
  • Professional reputation damage

Medium

  • Minor internal process revealed
  • Near-miss caught before wide distribution
  • Corrected within minutes

Low

  • Typo or minor error caught quickly
  • No sensitive data involved
  • Learning opportunity

Reporting Process

  1. Immediate: Delete post if still live
  2. Within 1 hour: Create incident report using template
  3. Within 2 hours: Notify Robert; if Robert is OOO, notify Lisa (fractional CMO)
  4. Within 24 hours: Complete incident report with root cause
  5. Within 1 week: Review prevention actions

Monthly Review

GTM lead reviews all incidents monthly to:

  • Identify patterns
  • Update checklist if needed
  • Provide team training
  • Report to leadership if necessary

Maintained By: Marketing ops (Lisa + Jadyn coordination)
Created: 2026-02-12
Last Updated: 2026-05-06

Graph View