Skip to content

fix: hide the Splunk Cloud stack name at untrusted output boundaries - #83

Open
JacobPEvans-personal wants to merge 2 commits into
mainfrom
feat/cloud-target-redaction
Open

fix: hide the Splunk Cloud stack name at untrusted output boundaries#83
JacobPEvans-personal wants to merge 2 commits into
mainfrom
feat/cloud-target-redaction

Conversation

@JacobPEvans-personal

Copy link
Copy Markdown
Contributor

Summary

Test plan

  • ruff check ., ruff format --check ., pyright, pytest (1055 passed) all green locally
  • pre-commit run --all-files green
  • New tests/unit/test_public_target.py covers the opt-in redaction, port preservation, ACS path redaction, and idempotency
  • test_acs.py::test_inspect_reports_deduced_cloud updated for stack_configured

Opt-in via VCT_SPLUNK_REDACT_TARGET=1: hides the Cloud stack label in
prompts, JSON metadata, and transport error text, without touching the
audit log (which still records the real host). `splunk inspect` reports
`stack_configured: bool` instead of echoing the stack name. The Splunk
Cloud Read Canary workflow sets the variable and scans its own pytest
output for a leaked target or credential before publishing anything.
Copilot AI lite review requested due to automatic review settings August 18, 2026 11:18

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

Delete .github/scripts/scan-cloud-ci-leaks.py and its invocation from
run-cloud-suite.sh, and drop the corresponding mentions in cloud-read.yml
and CHANGELOG.md.
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.

2 participants