Skip to content

KC-1468,1473,1474: Protect SailPoint config record from Service Mode and fix ${VARNAME} expansion bypass - #2392

Merged
craiglurey merged 1 commit into
releasefrom
fix/sailpoint-hardening-and-var-expansion
Sep 24, 2026
Merged

craiglurey merged 1 commit into
releasefrom
fix/sailpoint-hardening-and-var-expansion

Conversation

@amangalampalli-ks

@amangalampalli-ks amangalampalli-ks commented Sep 23, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Protects SailPoint's config record and folder from Service Mode API access, and closes a bug allowing Service Mode's file/record restrictions to be bypassed via ${VARNAME} expansion.

Changes

  • SailPoint's config record and its folder are now unreachable through any Service Mode command, matching every other integration
  • SailPoint's own gate (marker/capability checks, entitlement queuing) keeps working exactly as before
  • ${VARNAME} environment-variable syntax is now rejected outright in Service Mode commands, closing a bypass where it could expand into a restricted file path or protected record reference after the security check already passed
  • Fixed an issue where SCIM-managed users could be modified by enterprise user ID instead of email
  • Added debug logging so a silently-skipped SailPoint gate (missing marker field) is now diagnosable per-request, not just at container startup

…and fix ${VARNAME} expansion bypass (#2389)

* Protect SailPoint config record from Service Mode and fix ${VARNAME} expansion bypass

* Fix entitlements not working

* Fix copilot review comments

* Fix claude's review comments

* Use Map instead of dict

* Fix review comment
@amangalampalli-ks amangalampalli-ks self-assigned this Sep 23, 2026
@amangalampalli-ks
amangalampalli-ks marked this pull request as ready for review September 23, 2026 13:10
@craiglurey
craiglurey merged commit bdcf52a into release Sep 24, 2026
4 checks passed
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