Integrate Seamward
Redaction
Remove sensitive fields before transmission.
Runs before transmission
Field removal and hashing happen inside the customer process before an observation is queued for Seamward.
Default redaction
Review the sensitive field classes removed automatically.
Authorization, proxy authorization, cookies, set-cookie, and API-key headers are always dropped. The default payload policy also drops common password and token fields recursively.
Custom policy
Drop or hash application-specific fields.
Add case-insensitive field names to dropFields or hashFields. Hashing uses a key derived inside the collector so identifiers can correlate without exposing their source values.
Verify redaction
Inspect safe test observations before production use.
- Use a safe test payload that contains representative sensitive fields.
- Send it through the instrumented handler.
- Inspect the resulting structural evidence and confirm dropped values are absent.
- Add application-specific fields to the policy before production traffic.