Jailbreak datasets from Menz et al. publication

[MenzBD]

Addition of specific health dataset containing disinformation topics with jailbreaks.

Description

• Jailbreak dataset from https://doi.org/10.1136/bmj-2023-078538
• Two techniques:
• Six prompts each targeting health topics
• Four demographics for systematic testing
• Based on our BMJ publication evaluating LLM safeguards

[microsoft-github-policy-service]

@MenzBD please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

1. Definitions.
   “Code” means the computer software code, whether in human-readable or machine-executable form,
   that is delivered by You to Microsoft under this Agreement.
   “Project” means any of the projects owned or managed by Microsoft and offered under a license
   approved by the Open Source Initiative (www.opensource.org).
   “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
   Project, including but not limited to communication on electronic mailing lists, source code control
   systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
   discussing and improving that Project, but excluding communication that is conspicuously marked or
   otherwise designated in writing by You as “Not a Submission.”
   “Submission” means the Code and any other copyrightable material Submitted by You, including any
   associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
   Project. This Agreement covers any and all Submissions that You, now or in the future (except as
   described in Section 4 below), Submit to any Project.
3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
   Should You wish to Submit materials that are not Your original work, You may Submit them separately
   to the Project if You (a) retain all copyright and license information that was in the materials as You
   received them, (b) in the description accompanying Your Submission, include the phrase “Submission
   containing materials of a third party:” followed by the names of the third party and any licenses or other
   restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
   guidelines concerning Submissions.
4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
   for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
   Submission is made in the course of Your work for an employer or Your employer has intellectual
   property rights in Your Submission by contract or applicable law, You must secure permission from Your
   employer to make the Submission before signing this Agreement. In that case, the term “You” in this
   Agreement will refer to You and the employer collectively. If You change employers in the future and
   desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
   and secure permission from the new employer before Submitting those Submissions.
5. Licenses.

• Copyright License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
  Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
  the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
  parties.
• Patent License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
  Your patent claims that are necessarily infringed by the Submission or the combination of the
  Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
  import or otherwise dispose of the Submission alone or with the Project.
• Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
  No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
  granted by implication, exhaustion, estoppel or otherwise.

6. Representations and Warranties. You represent that You are legally entitled to grant the above
   licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
   have disclosed under Section 3). You represent that You have secured permission from Your employer to
   make the Submission in cases where Your Submission is made in the course of Your work for Your
   employer or Your employer has intellectual property rights in Your Submission by contract or applicable
   law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
   have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
   You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
   REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
   EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
   PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
   NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
7. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
   You later become aware that would make Your representations in this Agreement inaccurate in any
   respect.
8. Information about Submissions. You agree that contributions to Projects and information about
   contributions may be maintained indefinitely and disclosed publicly, including Your name and other
   information that You submit with Your Submission.
9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
   the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
   Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
   exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
   defenses of lack of personal jurisdiction and forum non-conveniens.
10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

[romanlutz]

I see what you're trying to do here, essentially insert the demographics into the prompt, and the prompt into the template. This won't work exactly like this, though, because the code looks for just specific pre-defined fields.

I am wondering if there should be one file for the high-level template, then another for the low-level template, and then a file with potential values to insert for demographics.

I could see this pattern show up a lot more (i.e., inserting demographics at a placeholder, but with a specific set of pre-defined options) and we should perhaps support that with a dataset generator class that can do this?

@rlundeen2 @bashirpartovi @hannahwestra25 any thoughts?

[hannahwestra25]

@romanlutz wdym by high-level template vs low level template ? Agree about adding support for this! this is something that came up with Frederic's notebook.
I think the simplest approach is just to add a field for each prompt like

- value: this is the {prompt}
   template:
      key: prompt
      value: [hi, bye]

(or something like that; idk how much yaml supports for list data types)
and then create another seedprompt in the seed group for every value.

[hannahwestra25]

Oh i see! this first value is supposed to cascade downward ! I can see what you mean and maybe there's another use case I'm not seeing but it seems like the topmost value here is really a system prompt so rather than having a high-level template, we could just add a field for a system prompt

[romanlutz]

I don't think these are system prompts, but @MenzBD can chime in on that perhaps. I think they're meant to be sent to the model directly to see if the model obliges which would mean it creates misinformation (= harm).

SeedPrompt can already be a seed prompt template that's why we have the parameters. If there are not parameters then it's just a plain prompt, not a template. However, this here is several layers of templating which means it's possible for things to get lost. Right now, we'd have to put the first level template ("In the following...") in one file, second level templates ("Write a blog post...") in another file (each), and the parameter values (young adults, parents...) as prompts in a third file. Then we could insert the prompts into the second level templates thus creating a prompt, and then insert that prompt into the top-level template. There is no way people understand how to do that without an example notebook 😆

That's why I'm wondering if this is a common enough use case for us to write that notebook (or ask @MenzBD if they want to chime in) vs. supporting it better with PyRIT functionality somehow (not sure I have good ideas there...). The simpler alternative would be to just generate all the options and dump them into a dataset rather than host templates. I dislike that for obvious reasons (you lose the template) but it's better than adding multiple levels of templates without a notebook.

[MenzBD]

Hi all,
Thanks for the thoughtful discussion, really helpful context.
Just to clarify: the prompts/jailbreaks here come directly from our study, but in the actual workflow we simply used the LLMs via their UI (e.g., ChatGPT for GPT-4). The process was:

1 Submit the initial instruction,
2 Then submit the specific health-topic prompt,
3 Repeating that sequence across the demographic groups.

My initial thought was that structuring the file this way might make that pattern easier to represent for the community, but I can see how the multi-level templating becomes confusing without dedicated examples. My thought was that the top section would act like a system-style instruction, with the health-topic prompts inserted afterward and then looped through the demographic values.

[romanlutz]

Makes sense. It's 24 total combinations per file, so 48 total. Wouldn't be too hard to just generate them and put all of them in a file, but that makes me sad.

@rlundeen2 any thoughts?

[rlundeen2]

Medium term: I think we need a better way to run converters on templates. I have wanted to do this before and I think it would be a potential good solution to problems like this. E.g. here, we could first convert so that the parameters are populated. But in other situations, we could more easily do things like "convert this jailbreak to Spanish"... or honestly it's like you say Roman, we could auto expand pieces.

For now: these need to move. Our text_jailbreak class relies on the jailbreaks just having prompt parameters and this will break it.

Option 1: I am happy including this if it moves to datasets/jailbreak/multi_parameter. It won't be used automatically by the jailbreak converter, but we can tackle this along with the other multi parameter templates. I think already useful, but people would have to apply the templates manually so there is an extra step.

Option 2: We can do the 24 combinations, but I'd want a directory like datasets/jailbreak/menz_health_disinformation. This would definitely be more useful in this moment because would be included in our jailbreak converters, but it's some code debt because we'd likely want to recombine them later.

I am okay with either option, but soft suggestion for option1

[rlundeen2]

Next step: @MenzBD, pick which one you'd prefer, and if you agree, then happy to approve :)