> For the complete documentation index, see [llms.txt](https://docs.sola.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sola.security/integrations/data-sources.md). # Data Sources A data source is a secure connection from your [Sola workspace](/workspace/workspace-home.md) to your organizational data. Data can be imported from various sources, including cloud providers, cloud services, operational applications, security tools, and any other source desired. {% hint style="info" %} Learn more about [data privacy](https://trust.sola.security/). Data sources and records quota are subject to [pricing and packages](https://sola.security/pricing/). {% endhint %} ## Available data source integrations
Cover image
Amazon Web Services (AWS)Microsoft AzureGoogle Cloud Platform(GCP)/pages/dTeg8rm9ZrHE2ZOqoJF8/files/XbvHTR1eZP2voGGslPq3
Google Cloud Platform (GCP)Google DirectoryCloudflare/pages/cniC9rCUmBxof0YbUjRo/files/SxKhGXL3KOmmYiN3Uxg5
Microsoft AzureDatadogMongoDB Atlas/pages/cDh1ety5oMBT4cYOUf9z/files/Ulaa2Q4aRTyppuT50jaM
Google Workspace/pages/GqpaolDH8ngPhm9VFFl9/files/yYigK45Y4sbvR5VG70Xj
GitHub Cloud1PasswordWiz/pages/ngusUTzcPccv3taD1T2D/files/ylW3TJHHgqPkATKxSVJ3
Microsoft Entra ID/pages/am0RidgfPNbmYVnV1l3B/files/T78Gar4isXQ7PNh16uCP
Okta/pages/MDUj4HuDu6ONUzCnQuC6/files/PeEmTOhdNSTJ33pd7Pyg
MongoDB Atlas/pages/c3qttjsYfP9xXIqW4UyC/files/Lye4TWbVicllwHZfhvzB
Wiz/pages/Gkkl9bhJQM6dTMSj4taf/files/Rm9K9RwKAokWNXaY6IZb
Upwind/pages/DwhMl653jjgb1MW0fUGx/files/DBt4sx1voML0d9WefNwE
WordPress/pages/o9P8WoZVElnTW0OHtWaa/files/VwRPV8ukwkUnulBfLot8
Sola Web Checker/pages/LDAE231AqRCX1f6C7DlB/files/s2zSMCCscFPpUoa0k8eF
Lovable App Scanner/pages/imhSHAqFq9BwDgV0FikP/files/6ih4Oer83Gz4P2mnonKS
CSV File/pages/n7xXqeXUSfuPplBAF3dh/files/BcLkInfkrEhDj6O5UQuF
Zoom/pages/K5TytZBSd4tkTTDVg3TG/files/aWtX6H4RSawxkyr2ZEZE
Jira Cloud/pages/7AODKITipXp7A2zJcPf4/files/8rysYG2OWe7yHs1q07mI
Cloudflare/pages/rc9eTKo2Gc6NLTBzl1Gw/files/PUIIHjZttsHDNSerrG4a
SentinelOne/pages/wWRQ8SK8uhIxb9jtO6yW/files/b3lrtmkwIz5llZe0yDEV
NetSuite/pages/fPVAWZ7ZzW31zaZZGxfg/files/FEcedv5fv3hs8RovLzND
Claude Console/pages/08Upvgf5ojdl2NRKWbd3/files/MJQM6D07VOtJgJKRQ2Jj
Claude Enterprise/pages/bIfESan1qX0wxOWPsNNk/files/MJQM6D07VOtJgJKRQ2Jj
Claude Enterprise Analytics/pages/8JeOsgPzCFFFaoVayCXT/files/MJQM6D07VOtJgJKRQ2Jj
Semgrep/pages/D4GdWCYlyZssLZZGoaci/files/imUrIgVFlBklKmvZAeHG
Google Sheets
(Real time)		/pages/0Y6wxtTpG7smmKHTQRrT/files/TZfvVv95gWK05vKZPYG5
Sentinel Data Lake
(Real time)		/pages/3JSnDBAGdwPUa2Bp7Jsx/files/iTEdjfMDN8hYY9BX9rlY
Snowflake
(Real time)		/pages/668L3n4Gyq5myXeroogr/files/UF2GUVD11FStQnwtEf1G
CircleCI/files/hj621P602hr8ZUJenuA8
DatadogCSV
/files/8ye35Gb9jF4QzrRK8eNI
Crowdstrike/files/bOwoGDusmZFZGdUEL0X8
Salesforce/files/XVffDOcX9f47B7L0OYL6
OpenAI Platform/files/SWFoUmTKrUya1Nov6bqR
OX Security/files/gfpGCDEgvY2C3dRgV3kX
Jamf Pro/files/KrEqhQcWW469awijhsgZ
Jamf Security Cloud (formerly RADAR)/files/KrEqhQcWW469awijhsgZ
HiBob/files/ngUNpxDMoiH7vyQiev6u
JumpCloud/files/4pKkSOiwqxxNhJyJwk2Q
Mosyle/files/6JkGH4vbrHoXzXduf8UC
## Data source tables Each **data source** contains multiple **tables** that store structured data retrieved from your connected source. This data is organized for easy analysis and is available for [queries](/workspace/projects/queries.md), [visualizations](/workspace/projects/canvases.md), and [alerts](/workspace/projects/alerts.md). ### Sync status Sola syncs **your data daily** to ensure your insights stay up to date, and you can trigger a [manual sync](#triggering-a-manual-sync) at any time to refresh on demand. Sync cycle times vary based on the data size. Real-time integrations, such as [Google Sheets](/integrations/data-sources/google-sheets.md) (Snowflake and Sentinel Data Lake coming soon) are always up to date and do not follow a scheduled sync cycle. {% hint style="info" %} **Data availability during a sync** During a sync, your most recent data stays available to query. Sola updates it once the sync completes. {% endhint %} #### Checking sync status To check the status of your data: * **Data Sources page** - Click on a [data source](/integrations/data-sources.md) to see the sync status of its tables. * **Query Library** - Click on a specific [query](/workspace/projects/queries.md) to check which data tables are being used and their sync status. #### Last sync information Sync details are available at two levels: * **Data source level** - Displays the overall sync status and total number of records synced during the last update. * **Table level** - Shows individual table sync status and the number of records synced per table. {% hint style="info" %} **Table sync dependencies** Some table data depends on other tables to sync successfully. If a parent table fails to sync, its dependent (child) tables will also fail. For example, an AWS user roles table depends on successfully retrieving AWS users. If the AWS users table fails to sync, the AWS user roles table will also fail. {% endhint %} #### Triggering a manual sync Sola syncs your data automatically on a daily cycle. You can also trigger a sync on demand instead of waiting for the next scheduled cycle, for the entire data source or a single table. To trigger a manual sync, go to ***Integrations*** > ***Data Sources***. To sync the entire data source, select **Manual run** from the main list. To sync a single table, open the data source and table you want to refresh, and select **Manual run**. Sola refreshes the data and shows its sync status and progress while the sync runs. {% hint style="info" %} **How manual runs work** There is no limit on how often you can trigger a manual sync. Like scheduled syncs, the records a manual run pulls count toward your daily records limit. Your existing data stays available to query while the sync is in progress, and updates once the run completes. {% endhint %} {% hint style="info" %} **Manual run and real-time data sources** Manual runs apply to data sources that sync on a schedule. Real-time data sources, such as Google Sheets and Snowflake, are queried live at runtime and their data is always up to date. {% endhint %} ### Sync status types | Data source sync status | Table sync status | | ----------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | | **Synced** - All tables successfully synced in the last sync cycle. | **Synced** - The table or tables under the same group successfully synced in the last sync cycle. | | **Partially Synced** - Some tables did not sync in the last sync cycle. | **Syncing** - The table or tables under the same group are currently syncing. | | **Out of Sync** - The last sync failed. | **Tables failed** - The table or tables under the same group failed to sync in the last sync cycle. | | **Real-time** - Data is queried in real time. | **Disabled** - This table has been disabled and is not synced. | | | **Enabled** - This table has been enabled and will sync in the next scheduled sync. | | | **Real-time** - Data is queried in real time. | {% hint style="success" %} **Disabling and Enabling Tables** Disable a table if you no longer need its data to be included in sync cycles, reducing unnecessary data updates, and records quota. * Disabled tables will no longer sync or be available for queries, canvases, or alerts. * Disabling a parent table will also disable any child tables that depend on it. * Re-enable a table at any time to resume syncing and restore access to its data. {% endhint %} ### Snapshots and incremental data updates Data source tables support historical data collection, allowing you to explore changes over time. Table’s data is updated in one of two methods: * **Snapshots** - capture a single point-in-time state of the data. * **Incremental** - continuously collect changes, building a stream of historical records over time. To view and use historical snapshots saved by Sola and not only the latest snapshot, include the word “snapshots” in your query or Sola AI prompt. By querying snapshots or incremental tables, you can explore the history of your data, investigate posture changes in posture, track configuration drift, and review past states. For example, ask Sola AI to: * Show AWS EC2 inventory across multiple data snapshots. * Investigate snapshots of Github users granted admin access in the last few days. * Find Okta role or policy that has changed in the last 3 days across snapshots and how. {% hint style="info" %} Historical snapshots are available up to 90 days back, limited by when your data source was connected. {% endhint %} ## Data records and usage Data records represent the data entries Sola processes from connected data tables. Each row from a connected data source counts as one data record. Data record limits reset daily. If you reach your daily data record limit, data processing pauses until your next daily limit resets. **Upgrade your plan for higher limits.** {% embed url="" %} {% hint style="info" %} **Downgrading and data sync limits** If you downgrade your plan, existing connected data sources stay connected. After the downgrade takes effect, Sola applies the new plan limits going forward, which means data syncs fetch only the number of records included in the new plan. {% endhint %} {% hint style="info" %} **Daily data record limits and your data source sync** If a data source's initial sync doesn't complete before your daily limit resets, Sola continues it the next day, and keeps going day by day until it's complete. Once fully synced, later syncs only pull new and changed records, using far fewer records than the initial sync. {% endhint %} ### Real time data sources usage Real time data sources such as [Google Sheets](/integrations/data-sources/google-sheets.md) (Snowflake and Sentinel Data Lake coming soon) do not count toward your data record usage. These integrations operate as live connections rather than imported datasets. No copy of your data is stored in Sola. Queries run directly against the source system at runtime. When a row is added to a Google Sheet, a table is updated, or new records added, your data in Sola reflects those changes immediately. Usage is governed by the license for each integration and the source system's own limits, not by Sola's data record quota. {% hint style="info" %} **How real-time sync works**\ When you connect a real-time data source, Sola inspects it to learn its structure and checks periodically for any changes. {% endhint %} *** ## FAQs ### Why should I connect my data sources? Connecting your data sources allows you to find answers to your security questions using your own organizational data. The collected data is used to [create projects](/workspace/projects.md#creating-projects). ### Why should I trust Sola with my data? At Sola, we prioritize the [security and privacy](https://trust.sola.security/) of your data through strong encryption, strict access controls, and compliance with industry standards. Our systems are regularly audited, monitored for threats, and undergo continuous security improvements to ensure your sensitive data remains protected. ### What happens with my data? Sola has **read-only** access to your data. Once connected, your data is securely stored in **structured tables** that uniquely map the data content and its sources. This is what makes it easy to query and find answers to your specific use cases. **Sola AI** brings an additional layer of security knowledge available for you to use. ### What happens if I don’t connect my data? If you don’t connect a data source, you’ll only be able to explore **sample data** within Sola. While this allows you to see how things work, you won’t get **real insights** based on your organization’s security data. ### Why does Sola need wide permission-level read access to my data? The answers to your questions could be hidden anywhere in your data. Limiting access to your data will limit the insights and answers you can gather. [Learn more about data privacy](https://trust.sola.security/)
### What happens if my data source sync hits the daily data record limit partway through? Sola picks up the sync where it left off. If a data source's initial sync doesn't finish before your daily data record limit resets, it continues the next day, and keeps continuing day by day until the data source is fully synced, you may see this reflected as a [**Partially Synced**](#sync-status-types) status in the meantime. Once the initial sync completes, later syncs only pull new and changed records instead of the full dataset, which uses far fewer records and is unlikely to hit the limit again. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sola.security/integrations/data-sources.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.