From b288835b47258b5b2f079099016a165990502fc6 Mon Sep 17 00:00:00 2001 From: Ishaan Jaff Date: Tue, 2 Jul 2024 18:10:41 -0700 Subject: [PATCH] doc secret detection --- docs/my-website/docs/proxy/enterprise.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/docs/my-website/docs/proxy/enterprise.md b/docs/my-website/docs/proxy/enterprise.md index 419827dceb6..9088af20361 100644 --- a/docs/my-website/docs/proxy/enterprise.md +++ b/docs/my-website/docs/proxy/enterprise.md @@ -506,10 +506,7 @@ curl --request POST \ 🎉 Expect this endpoint to work without an `Authorization / Bearer Token` - - -## Content Moderation -### Content Moderation - Secret Detection +## Guardrails - Secret Detection/Redaction ❓ Use this to REDACT API Keys, Secrets sent in requests to an LLM. Example if you want to redact the value of `OPENAI_API_KEY` in the following request @@ -606,7 +603,7 @@ https://api.groq.com/openai/v1/ \ **Step 1** Create Key with `hide_secrets` Off -👉 Set `"permissions": {"secret_detection": false}` with either `/key/generate` or `/key/update` +👉 Set `"permissions": {"hide_secrets": false}` with either `/key/generate` or `/key/update` This means the `hide_secrets` guardrail is off for all requests from this API Key @@ -670,7 +667,7 @@ The `hide_secrets` guardrail check did not run on this request because api key=s ::: - +## Content Moderation ### Content Moderation with LLM Guard Set the LLM Guard API Base in your environment