-
Notifications
You must be signed in to change notification settings - Fork 397
Add AI Guard component and settings #5144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Application key is required for direct communication to AI Guard API.
We want to allow the user to disable AI Guard without having to remove AI Guard SDK method calls.
This exception should be only raised when AI Guard was disabled, but evaluation request was performed manually, or when AI Guard component did not initialize properly.
Typing analysisNote: Ignored files are excluded from the next sections.
|
We need to use the same name, since front-end is expecting it.
manuel-alvarez-alvarez
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, the only think I'm missing is an update to CODEOWNERS to set ASM as owners of the new folders.
What does this PR do?
This PR adds SDK for AI Guard. This feature is currently in preview.
Motivation:
We want to have a native Ruby SDK for AI Guard.
Change log entry
Yes. AI Guard: Add SDK for evaluating safety of user messages and assistant commands for LLM session.
Additional Notes:
APPSEC-60063
How to test the change?
Manual testing and CI.