Skip to content
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

[Security GenAI] Assistant Anonymization feature anonymizes fields with the same values regardless of how they're configured #183571

Open
peluja1012 opened this issue May 15, 2024 · 1 comment
Labels
bug Fixes for quality problems that affect the customer experience Team:Security Generative AI Security Generative AI Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed

Comments

@peluja1012
Copy link
Contributor

Describe the bug:
When configuring anonymization and one field is set to anonymized and another field to non-anonymized, the non-anonymized setting is ignored when the value of the two fields is the same. For example, if the value for both user.name and event.user.name is foo, and user.name is set to anonymized and event.user.name is set to non-anonymized, then both values will be anonymized by the assistant, thus ignoring the setting of event.user.name.

Kibana/Elasticsearch Stack version:
v 8.14.0 BC3

Steps to reproduce:

  1. Open the AI Assistant from the Alert Detail page.
  2. Add the alert as context to the conversation.
  3. Edit the anonymization settings for that alert.
  4. Find two fields that have the same value. Set one field to anonymized Yes and the other to anonymized No. Save the settings.
  5. Refresh the page.
  6. Open the same alert, then open the AI Assistant, then add the alert as context, then send a message.
  7. Look at the context of the message sent and click on the Show Anonymized toggle at the top.
  8. Notice that both field values are anonymized, even though you set one of the fields to No.
image image
@peluja1012 peluja1012 added bug Fixes for quality problems that affect the customer experience triage_needed Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Security Generative AI Security Generative AI labels May 15, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:Security Generative AI Security Generative AI Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed
Projects
None yet
Development

No branches or pull requests

2 participants