Uploaded image for project: 'Zero Trust Workload Identity Manager'
  1. Zero Trust Workload Identity Manager
  2. SPIRE-237 Premarge Testing
  3. SPIRE-250

Premarge testing => Restrict SCC for spire-agent

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • OAPE Sprint 279
    • 1

      https://github.com/openshift/zero-trust-workload-identity-manager/pull/50

       

       

      ✅ Pre-Merge Testing Summary for PR #50
      Test Status: PASSED - APPROVED FOR MERGE 🎉
      📊 What Was Tested
      PR #50 Change    Test Status    Evidence
      1. Add privileged: true    ✅ VERIFIED    Confirmed in DaemonSet spec
      2. SCC: MustRunAsRange    ✅ VERIFIED    Pods run as UID 1000730000 (not 0)
      3. SCC: MustRunAs (SELinux)    ✅ VERIFIED    SELinux context enforced
      4. Security + Functionality    ✅ VERIFIED    All pods healthy, security maintained
      🎯 Test Coverage
      Positive Tests: ✅ 8/8 PASSED
      Privileged mode enabled
      SCC policies correct
      Pod UID not root
      Namespace UID range enforced
      Correct SCC applied
      All pods running
      Security context complete
      Negative Tests: ✅ 5/5 PASSED
      Cannot run as UID 0 (override working)
      SCC selection working
      Operator reconciliation verified
      Security restrictions enforced
      Customer-Facing Tests: ✅ 2/2 PASSED
      SPIRE infrastructure ready
      Agent resilience verified
      🔒 Security Validation
      ✅ All PR #50 security mechanisms verified:
      Privileged mode: Enables SPIRE functionality ✅
      MustRunAsRange: Prevents root access (UID 0) ✅
      MustRunAs: Enforces SELinux policies ✅
      Defense in depth: Multiple security layers working ✅
      Result: "Privileged with Guardrails" approach is working perfectly!

              rh-ee-sayadas SAYAK DAS
              rh-ee-sayadas SAYAK DAS
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: