Skip to content

πŸ•΅οΈ SECURITY_ARCHITECTURE.md: Add Threat Detection, Vulnerability Management, Automated Ops, and Resilience SectionsΒ #384

@pethers

Description

@pethers

πŸ“‹ Issue Type

Documentation / Security Compliance

🎯 Objective

Add dedicated Threat Detection & Investigation, Vulnerability Management, Automated Security Operations, and Resilience & Operational Readiness sections to SECURITY_ARCHITECTURE.md. These are standalone mandatory sections in both CIA and Black Trigram reference implementations but are either missing or only partially covered as subsections in riksdagsmonitor.

πŸ“Š Current State

The riksdagsmonitor SECURITY_ARCHITECTURE.md covers some topics superficially within Β§2.6 (Monitoring & Logging) and Β§4 (Security Controls Summary) but lacks the depth and structure of reference implementations:

Mandatory Section CIA BT Riksdagsmonitor
πŸ•΅οΈ Threat Detection & Investigation βœ… (GuardDuty, Detective, deep analysis) βœ… (Current status, security implications) ❌ Missing
πŸ”Ž Vulnerability Management βœ… (Inspector, remediation process, key benefits) βœ… (Current status, security considerations) ⚠️ Brief mention in Β§4.2
πŸ€– Automated Security Operations βœ… (SSM, automation components) βœ… (Current status, operational benefits) ❌ Missing
⚑ Resilience & Operational Readiness βœ… (Resilience Hub, testing strategy, BC features) βœ… (Current status, resilience benefits) ❌ Missing
πŸ“‹ Configuration & Compliance Management βœ… (AWS Config, compliance framework integration) βœ… (Current status, configuration approach) ❌ Missing
πŸ“Š Monitoring & Analytics βœ… (Security Lake, analytics capabilities) βœ… (Current status, monitoring limitations) ⚠️ Basic in Β§2.6

πŸš€ Desired State

Add 6 dedicated sections with riksdagsmonitor-specific content:

1. ## πŸ•΅οΈ Threat Detection & Investigation

  • GitHub security alert monitoring (Dependabot, CodeQL, Secret scanning)
  • AWS CloudTrail anomaly detection
  • CloudFront access log analysis for suspicious patterns
  • Detection capabilities matrix (what can vs. cannot be detected)
  • Investigation procedures for static site threats

2. ## πŸ”Ž Vulnerability Management

  • Dependabot automated scanning (GitHub Actions, npm dependencies)
  • Chart.js/D3.js/Papa Parse version monitoring
  • Vulnerability remediation SLAs (Critical: 24h, High: 7d, Medium: 30d, Low: 90d)
  • Vulnerability tracking and reporting
  • Key benefits of current approach

3. ## πŸ€– Automated Security Operations

  • GitHub Actions automated security workflows
  • Dependabot auto-merge for minor/patch updates
  • Automated HTML validation (HTMLHint) and link checking (linkinator)
  • SLSA attestation generation automation
  • CIA data validation automation

4. ## ⚑ Resilience & Operational Readiness

  • Dual deployment resilience (AWS CloudFront + GitHub Pages DR)
  • Cross-region S3 replication (<15 min RPO)
  • Route 53 health checks and automatic failover
  • Recovery Time Objective (RTO) and Recovery Point Objective (RPO)
  • Business continuity features

5. ## πŸ“‹ Configuration & Compliance Management

  • Infrastructure as Code (GitHub Actions workflows)
  • Configuration drift detection (GitHub + AWS)
  • Compliance framework integration (ISO 27001, NIST CSF, CIS Controls)
  • Automated compliance checking

6. ## πŸ“Š Monitoring & Analytics

  • GitHub Actions workflow monitoring
  • AWS CloudWatch metrics collection
  • CloudFront access log analytics
  • Security metrics dashboard (if applicable)
  • Key monitoring gaps and remediation plans

πŸ”§ Implementation Approach

  1. Extract relevant content from existing Β§2.6 and Β§4 into new dedicated sections
  2. Add riksdagsmonitor-specific details for each section
  3. Include Mermaid diagrams where appropriate
  4. Add ISO 27001/NIST CSF/CIS Controls mapping to each section
  5. Match the subsection pattern used in CIA/BT (### Key Components, ### Security Benefits, etc.)
  6. Maintain consistency with existing document style

πŸ€– Recommended Agent

security-architect β€” Deep security operations expertise required

βœ… Acceptance Criteria

  • 6 dedicated sections added (Threat Detection, Vulnerability Mgmt, Automated Ops, Resilience, Config/Compliance, Monitoring)
  • Each section has Control Mapping to ISO 27001/NIST CSF/CIS Controls
  • Vulnerability remediation SLAs documented
  • Resilience section includes RTO/RPO targets
  • All content is riksdagsmonitor-specific
  • At least 2 new Mermaid diagrams
  • Existing content preserved (no duplication)

πŸ“š References

🏷️ Labels

type:documentation, priority:high, component:security, agent:security-architect

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions