# Deleting only specific fields carrying PCI information from ELastic search indices

**URL:** <https://discuss.elastic.co/t/deleting-only-specific-fields-carrying-pci-information-from-elastic-search-indices/143199>\
**Category:** Elasticsearch\
**Created:** [August 6, 2018, 5:44pm UTC](https://discuss.elastic.co/t/deleting-only-specific-fields-carrying-pci-information-from-elastic-search-indices/143199 "2018-08-06T17:44:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ravish9370](https://avatars.discourse-cdn.com/v4/letter/r/85f322/32.png) [@ravish9370](https://discuss.elastic.co/u/ravish9370)\
**Post date:** [August 6, 2018, 5:44pm UTC](https://discuss.elastic.co/t/deleting-only-specific-fields-carrying-pci-information-from-elastic-search-indices/143199/1 "2018-08-06T17:44:08Z")

</div>

HI All,

I have an issue that starting 8 weeks ago , because of some code changes , PCI information start getting printed in WCS logs. Now that information is parsed into elastic search and can be seen in kibana. Our security team want to remove that information. Can you suggest from below, what should we do -

1. Mask the those specific fields with XXXXXXXX ?
2. Can we delete those fields only from ES indices.
3. Or we have to delete complete indices for 8 weeks which will be a huge loss for our ops team as they will not be able to debug the issue?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 3, 2018, 5:44pm UTC](https://discuss.elastic.co/t/deleting-only-specific-fields-carrying-pci-information-from-elastic-search-indices/143199/2 "2018-09-03T17:44:08Z")

</div>

Closed on September 3, 2018, 5:44pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.