---
title: "Comment by Adam Lewis on \"Clipboard and Inter-Process Data Copies: Monitoring Paths at the Operating System Boundary\" | Hashnode"
description: "Delayed rendering splits monitoring into two problems the article treats as one, so push on it. A monitor that only reads formats on WM_CLIPBOARDUPDATE sees the"
url: "https://hashnode.com/posts/clipboard-and-inter-process-data-copies-monitoring-paths-at-the-operating-system-boundary/6ae4628bd2cfe6c3b7c9adc4/comment/6aeba72eb6addf49c860c6ca"
---

[Discussion](https://hashnode.com/posts/clipboard-and-inter-process-data-copies-monitoring-paths-at-the-operating-system-boundary/6ae4628bd2cfe6c3b7c9adc4)

Comment [Clipboard and Inter-Process Data Copies: Monitoring Paths at the Operating System Boundary](https://hashnode.com/posts/clipboard-and-inter-process-data-copies-monitoring-paths-at-the-operating-system-boundary/6ae4628bd2cfe6c3b7c9adc4)

[Adam Lewis](https://hashnode.com/@nark3d)

[Nov 4](https://hashnode.com/posts/clipboard-and-inter-process-data-copies-monitoring-paths-at-the-operating-system-boundary/6ae4628bd2cfe6c3b7c9adc4/comment/6aeba72eb6addf49c860c6ca)

Delayed rendering splits monitoring into two problems the article treats as one, so push on it. A monitor that only reads formats on WM\_CLIPBOARDUPDATE sees the publication and never the request, so a policy that blocks by content is inspecting whatever the owner chose to put there. Provenance helps. Does it survive an owner that renders late from a protected window into an unprotected one, or does the attribution end up pointing at the publisher and missing the paste entirely? Have the audit record answer that before anyone trusts it.