# Scan and mask PII in graylog

**URL:** https://community.graylog.org/t/scan-and-mask-pii-in-graylog/29566
**Category:** Graylog Central (peer support)
**Tags:** access-specific-log-
**Created:** [July 18, 2023, 7:08am UTC](https://community.graylog.org/t/scan-and-mask-pii-in-graylog/29566 "2023-07-18T07:08:22Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![ihe](https://avatars.discourse-cdn.com/v4/letter/i/a88e57/32.png) [@ihe](https://community.graylog.org/u/ihe)
#### Post date: [July 19, 2023, 9:35am UTC](https://community.graylog.org/t/scan-and-mask-pii-in-graylog/29566/4 "2023-07-19T09:35:52Z")

</div>

HI @sunnyjaisinghani  
I would suggest to make yourself familar with Grok patterns. They combine multiple regex, which can capture multiple values into different fields.  
After you build your Grok-Patterns you create a pipeline and run the grok there. I explained that on another case here: [Regex Matching in Pipeline or Extractor - #16 by ihe](https://community.graylog.org/t/regex-matching-in-pipeline-or-extractor/27207/16)  
In a stage after your parsing you can replace the message field with some content without PII, again with a pipeline.

---

_[View the full topic](https://community.graylog.org/t/scan-and-mask-pii-in-graylog/29566)._