Repository navigation
Record AWS exclusion source lineage and clarify two routes - #505
Merged
carlospolop merged 1 commit intoOct 23, 2026
Merged
Conversation
carlospolop
deleted the
codex/aws-exclusion-lineage-remaining-20261023
branch
October 23, 2026 04:24
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds historical source bindings for 15 reviewed, still-excluded AWS privilege escalation candidates. Clarifies the bounded Timestream scheduled-query effect and the missing AgentCore harness execution witness. No excluded route is activated.\n\nValidation:
python3 scripts/validate_privesc_paths.py --book-root . --peaso-root /tmp/peasso-aws-lineage-remaining-20261023(296 files, 685 techniques, 3777 exclusions).