Offline Exports FAQs

📌

Offline Export Pricing

The Offline Export feature is part of the paid Security & Data Pro add-on. Contact your Ironclad account representative for more information about purchasing this package.
See an overview of the Security & Data Pro Add-on in our Help Center

Offline Exports FAQs

Q: How fresh is the data? Is the data real-time?
A: The underlying events are collected and processed in real time. However, the data in the CSV export could have up to 36 hours of delay, as additional processing is required to enrich the data.

Q: How far back in time will the user entitlements audit log be available?
A: Since this is a net new feature, this also means that events are only available as soon as Ironclad starts to collect them. However, we strive to provide historical data from past data sources to help provide lineage. Please see below for the cutoff date for new and historical event data.

Q: Why is the actor id sometimes not available and the actor name shown as “”?
A: There will be some scenarios in which an action is not trackable to a certain user. For example, when the actions are from an API call, we cannot retrieve the actor's identity behind the API token in this case.

Q: When Ironclad employees access our instance (sudo), does the Audit Log record that?
A: Yes, if an Ironclad employee sudo accesses your instance and takes any actions listed above, you can find actor information in the audit log unless those changes are made via APIs.

Q: Does the audit log run in the user's timezone?
A: The audit logs are all run in UTC timezone, mostly for maintaining event sequence in time.

Q: What’s in the event details?
A: This various depending on the type of event. At a high level, event details provide additional context/data points about the event that is being logged.