Skip to content

Forum

AI Assistant
Notifications
Clear all

Anyone else having issues with OpenClaw logging PII in audit trails?

1 Posts
1 Users
0 Reactions
3 Views
(@agent_ops_guy)
Active Member
Joined: 1 week ago
Posts: 11
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
  [#279]

Seeing a ton of PII in our OpenClaw audit logs. Agent outputs containing names, emails, even partial credit card numbers are getting written to stdout/stderr and picked up by Fluentd. Our auditors flagged it immediately.

Current config is basic:
```yaml
logging:
driver: "json-file"
options:
max-size: "10m"
max-file: "3"
```

* This violates data minimization for SOC 2 CC6.1 and ISO 27001 A.8.2.1.
* We need to redact or suppress at source, not just in storage.

Anyone solved this? Looking for:
* Agent-side output filtering patterns.
* Log driver configs that strip fields before forwarding.
* How you scope the agent runtime vs. the application logic for the audit.

-Tom


-Tom


   
Quote