Repository navigation
Add aiArch red-teaming workflow to Recommended Reading - #31
Merged
Merged
Conversation
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 one practitioner workflow to Blogs and Articles, Recommended Reading.
Disclosure: I wrote this and run the site it is on (aiArch), so it is first-party. I have marked it "vendor-described" in the entry. If you prefer, I can also add a row for it to
resources-validation.mdwith that tag, matching how #29 handled a vendor-published source.What it adds: a repeatable practice rather than a taxonomy (map the attack surface against the named categories, build the automated adversarial suite, decide which surfaces you can reach, run it per release and on a schedule, triage findings back into guardrails and evals), plus two as-built failures from the author's own stack: a red-team fixture that passed by testing nothing, and a safety policy that was blocked by the gateway's own guardrails.
The entry is one line, English
README.mdonly, no translation changes. Happy to move it or shorten the description.