How can I estimate the data volume that Nightfall needs to scan?
Estimating the amount of data that Nightfall will scan in your organization is an essential step in planning for the usage of historical scans.
The data requirements vary based on the integration. Refer to the respective integration below to understand the potential data volume required to scan via historical scans:
| Integration | Reference |
|---|---|
Slack | The total amount of data usage is not readily available in the Slack console. Nightfall recommends you export your Slack workspace data for historical scans on Slack. The exported archive file contains messages and links to files shared in Slack. Hence, the size of the exported archive file will likely be very small compared to the total amount of data to be scanned via Nightfall. Nightfall recommends you export workspace data for up to the last three months, as an example, and request the Nightfall team to run a historical scan on this exported data. Once the historical scan is complete, Nightfall can help you identify the total data scanned (GB) for the respective time period. You can use this information to understand the average monthly data volume in your Slack environment to extrapolate the total data volume required to scan data over a larger time period. For a basic understanding on usage limits in Slack, refer https://slack.com/intl/en-in/help/articles/115002422943-Usage-limits-for-free-workspaces |
Google Drive | Google workspace administration console provides visibility of the storage usage on Google drive. You can use this information to estimate the total data volume required for historical scans on Google drive. Refer to the Google workspace documentation for details on where to find the storage usage on Google drive https://support.google.com/a/answer/12002268?hl=en&ref_topic=13135206&sjid=7783233059016813973-AP |
Salesforce | Salesforce console provides visibility of the storage usage that can be used to estimate the total data volume required for historical scans on Salesforce.
Refer to the Salesforce documentation for details on where to find the storage consumption in Salesforce: https://help.salesforce.com/s/articleView?id=sf.admin_monitorresources.htm&type=5 |
Jira/ Confluence | Atlassian admin console may not provide clear visibility of the storage consumption on Jira and Confluence. Hence, Nightfall recommends a sample historical scan for a limited time period, last three months as an example, to be executed to estimate the total data volume required for historical scans on Jira and Confluence. Refer to the Jira and Confluence documentation for a basic overview on where to find the storage consumption: https://support.atlassian.com/security-and-access-policies/docs/track-storage-and-move-data-across-products/ |
GitHub | You can get visibility of the total storage consumption in GitHub to understand the total data volume required for historical scans on GitHub. Refer to the GitHub documentation for details on where to find the storage usage: https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage |
Zendesk | Refer to Zendesk documentation for details on where to find storage usage: https://support.zendesk.com/hc/en-us/articles/4408823446938-Managing-your-account |
Last updated