Skip to content

feat: add security_logging playbook and simplify category detail rendering#315

Open
l50 wants to merge 1 commit into
dreadnode:mainfrom
l50:upstream/security-logging-panel
Open

feat: add security_logging playbook and simplify category detail rendering#315
l50 wants to merge 1 commit into
dreadnode:mainfrom
l50:upstream/security-logging-panel

Conversation

@l50

@l50 l50 commented Jun 28, 2026

Copy link
Copy Markdown
Contributor

Key Changes:

  • Added security_logging.yml to all playbook profiles (NHA, SCCM, GOAD-Mini, DRACARYS, default)
  • Simplified the fail/warn detail cell logic in the validation panel to only show breakdown when both conditions are present
  • Removed redundant detail rendering since the row icon already conveys single-condition state

Added:

  • Security logging playbook step - Added security_logging.yml to all five playbook profiles in playbooks.yml (NHA, SCCM, GOAD-Mini, DRACARYS, and default)

Changed:

  • Category detail cell rendering - Simplified logic in renderCategoryColumn (cli/internal/validate/panel.go) to only display the combined x{fail} !{warn} breakdown when both fails and warns are present simultaneously, since a row icon like [x] or [!] already makes the single-condition state self-evident from the pass/total count alone

…panel detail rendering

**Added:**

- `security_logging.yml` to all environment playbook lists (NHA, SCCM, GOAD-Mini, DRACARYS, default) in `playbooks.yml`

**Changed:**

- Simplified category detail cell rendering in `panel.go` to only show the combined fail/warn breakdown (e.g. `x3 !2`) when both are present, since the row icon and pass/total count already convey the state when only one condition exists
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant