How to track all download actions in Foundry

For the securiy purpose, I would like to track all download actions in Foundry near real-time.
Due to the difficulty in handling Audit.2 log, I was going to set all “Export” checkpoint types in Checkpoints app. However, in the document about download control (https://www.palantir.com/docs/foundry/security/download-controls#review-audit-logs-to-understand-where-downloads-occurred), it’s said that Checkpoints does not cover all download actions in Foundry.

So, how can I track all download actons in Foundry in the general way?
I’m happy to get good idea.

Thanks in advance.

Hello @Knaon,

Outside of audit logs and Checkpoints, there’s no platform-wide mechanism for the workflow you’re describing.

Audit logs will provide the most granular and exhaustive data. To make processing them easier, you can export audit logs back into Foundry. However, as noted in the docs, it can take up to 24 hours for audit logs to become available.

While the available “Export” Checkpoint types can’t offer the same coverage as audit logs, they still do cover a lot of interactions with the platform, so it may be worth giving Checkpoints a try to see if it suits your needs in practice. You could also use Checkpoints for a near-real-time review of most interactions, and then have an more exhaustive asynchronous review based on audit.

Thank you for reply, @michael !

I’m going to try checkpoints settings, and I understand, if I’d like to track all the download activities in Foundry, the only way is processing Audit Logs.
So, are there any ways or code templates to simply extract download logs of both frontend and backend? I heard that “dataExport” category is catching only backend download activities…

@Knaon No, there are no templates available to do what you’re describing.

It’s worth noting that most “download” actions on the platform involve backend calls, and will therefore appear in the backend audit logs. Many interactions in which downloaded data is transformed and rendered on an ad-hoc basis on the frontend are covered by the the Frontend export checkpoint type, so you may be able to use Checkpoints to help you identify additional relevant logs.

@michael , I understand.

So I’m going to try both Frontend Export checkpoint setttings and dataExport in parallel.

Thank you for your support.

1 Like

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