I was playing around with some prompt injection guard rails frameworks. I know they don't mitigate attack classes, but they at least do something. I just got a bit miffed about the high false positive rates I saw in my own testing.
This one has a low false positive rate. And I thought that was interesting.
There is a simple way to mitigate prompt injection. Just check metadata only: is this action by the LLM suspicious given trusted metadata, blanking out the data
while i cant speak regarding arbitrary prompt injections, ive been using a simple approach i add to any llm harness i use, that seems to solve turn or role confusion being remotely viable.
i really need to test my toolkit (carterkit) augmented harnesses on some of the more respectavle benchmarks
I was playing around with some prompt injection guard rails frameworks. I know they don't mitigate attack classes, but they at least do something. I just got a bit miffed about the high false positive rates I saw in my own testing.
This one has a low false positive rate. And I thought that was interesting.
There is a simple way to mitigate prompt injection. Just check metadata only: is this action by the LLM suspicious given trusted metadata, blanking out the data
while i cant speak regarding arbitrary prompt injections, ive been using a simple approach i add to any llm harness i use, that seems to solve turn or role confusion being remotely viable.
i really need to test my toolkit (carterkit) augmented harnesses on some of the more respectavle benchmarks
You misspelled 'execute' in the video ;)
And it still did the right thing. Which I think makes the demo slightly more impressive.