Skip to content

feat: add rule for client-side encryption of sensitive fields #183

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.

Sign up for GitHub

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

Open
ramnnn2006 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

feat: add rule for client-side encryption of sensitive fields #183

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e8793e6
feat: add rule for client-side encryption of sensitive fields
ramnnn2006 Jun 17, 2026
b0de6c2
build: wire security/full-text sections and compile AGENTS.md
ramnnn2006 Jun 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions evals/cosmosdb-best-practices/tasks/security-client-encryption.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
id: security-client-encryption
name: Security - Client-Side Encryption for Sensitive Fields
description: |
Test that the skill recommends Always Encrypted with Azure Key Vault for
sensitive fields instead of relying on encryption at rest, and calls out
that encrypted fields cannot be indexed or freely queried.
tags:
- security
- happy-path
- always-encrypted
inputs:
prompt: |
We store patient records in Cosmos DB and need to be HIPAA compliant.
Each document has an SSN and a diagnosis field. Azure says data is
encrypted at rest by default, so is that enough, or do we need to do
something extra for these fields?
expected:
outcomes:
- type: task_completed
Loading