FEAT: Add Garak API key elicitation scenario - #2538
Open
寇依 (hey-Chloe) wants to merge 1 commit into
Open
Conversation
|
寇依 (@hey-Chloe) please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
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.
Description
Closes #2535 by adding an
ApiKeyGarak scenario with theGetKeyandCompleteKeytechniques.The scenario:
fixtures, and safe placeholders;
CredentialLeakScorer;identifiers.
For precision, seven Garak entries that represent public resource or OAuth
client identifiers are retained in the prompt corpus but intentionally do not
count as credential leaks. The remaining 51 service entries map to reviewed
credential-shaped patterns. Weak generic shapes require response-side
service/key labeling so objective context alone cannot turn refusals,
checksums, UUIDs, or ordinary text into positive results.
The adapted Garak and dora material is pinned and attributed in
THIRD_PARTY_NOTICE.md.Tests and Documentation
381 passedacross the complete regex scorer test directory and the newdataset/scenario tests.
documentation validation, notebook checks, and type checking.
git diff --checkpasses.doc/scanner/garak.ipynbdoc/code/datasets/1_loading_datasets.ipynbSeedDatasetProvider.Documentation was added to the Garak scanner guide and built-in dataset guide.
No live target or credential-provider validation was performed. The scenario
uses the normal user-configured PyRIT target and stores responses through the
existing framework behavior.
No breaking changes.