What are the available integrations in SaaS on Snow Atlas? 
Integrations in SaaS on Snow Atlas are known as SaaS connectors. The available connectors are Adobe Creative Cloud, Aha!, Atlassian Confluence, Atlassian Jira, Atlassian Trello, Box, Cisco Webex, Coupa, Docusign, Dropbox, Google Workspace, Microsoft 365, Microsoft Entra ID, monday.com, Okta, Salesforce Sales Cloud, ServiceNow, Slack, Tableau, Zendesk, Zoho, and Zoom. 

For more information, see SaaS connectors.  

Can we add additional data that exiting connectors do not provide out-of-the-box?  

There are two features planned for the second quarter of 2025 that support this use case: custom fields and SaaS data imports. Custom fields will enable you to create custom data fields in the SaaS UI that you can use to further track and filter your subscriptions, applications and users. SaaS data imports will enable you to create API integrations with SaaS vendors that are not supported out-of-the-box. 

You can also contact Flexera Support to request that connectors capture additional data. The capabilities of the SaaS connectors are frequently expanded based on customer feedback. 

Does SaaS on Snow Atlas have any AI-driven features? 
Yes, SaaS on Snow Atlas includes AI-driven features for enhanced data analysis and insights. 

Are there APIs available for data requests?  
Yes, several endpoints are available. For more information, see SaaS APIs and Get started with APIs.  

Browser extensions and Snow Inventory Agent 

What types of browser extensions are available?  
SaaS on Snow Atlas offers two types of browser extensions: agent-based and agentless. 

Which browsers are compatible with the browser extensions? 

Google Chrome, Microsoft Edge, Mozilla Firefox, and Apple Safari. For more information, see Browser extensions. 

What are the limitations of not using the agent-based browser extension? 

The agent-based browser extension is the industry-leading approach for shadow SaaS detection, offering optimal visibility of your SaaS estate.  

The Snow Inventory Agent performs similar tasks as the Flexera Agent in collecting locally installed application data, but it cannot collect URL access without the browser extension; the agent is the tool used to enable the browser extension which detects and retrieves the URL access data. 

Will the agent-based browser extension work with the Flexera Agent?  

The agent-based browser extension will not currently work with the Flexera Agent and requires the Snow Inventory Agent. Flexera plans to add support for the Flexera Agent in the first quarter of 2026. 

The agentless browser extension incorporates within the browser using Token broker and Client certifications for encryption. This is presently available to Flexera customers. 

What permissions does the agent-based browser extension require on end-user devices? 
The required permissions are tabs, webRequest, and nativeMessaging. For more information, see Permissions list. 

Data Collection 

What data retrieved by the agent-based browser extension is stored by Snow Atlas? 
The data retrieved includes the URL visited by the user, the date and time of the visit in UTC, and the email address of the user tied to the mTLS certificate on the user's machine. 

At no point does the extension log keystrokes, passwords, or any other data. All web patterns that are collected are limited by a definition file, webapps.config. The browser extension does not collect any other URLs like internal domains or websites you host. 

For more information, see Data retrieved by the browser extension. 

What data will be collected from workstations or servers?  
Flexera does not handle any sensitive or private information about individuals on behalf of our clients. Just as with the Flexera client, the Snow Inventory Agent is designed to collect hardware and software inventory. 

For information on data collected by the Snow Inventory Agent, see Inventoried data types and attributes. For information on data collected by the browser extension, see Data retrieved by the browser extension. 

Deployment and Configuration 

When installing the Snow Extender, what are the requirements for the Windows Server and Container options? 
For information on the Snow Extender system requirements for Snow Atlas, see System Requirements. 

To support the full function of Snow Atlas, in addition to allowing access to the URLs listed in IP addresses for Snow Atlas, ensure that you allow access to the URLs from your environments by adding them to the trusted sites of the browsers that you use with Snow Atlas.  

Can a HA be implemented for either the Windows Server or Container option?  
HA can be implemented for the Windows Server option.  

Data storage and security 

Is data collected by the agent-based browser extension temporarily stored on the end user’s device? How long is it stored and how is it cleaned up? 
The usage data is collected from the browser and temporarily stored in a user's Temp directory. It is then processed against cloud rules, and if a match is found, the data is stored in memory. The system waits for the next batch of data until it reaches 50 matches. When 50 matches are found, the usage data is sent to the Snow Extender as a CRYSON file. This data is eventually sent to Snow Atlas once per day or at a chosen interval.  

Browser-collected data is deleted from the user’s Temp directory as soon as it is processed, regardless of whether a match is found. When the snowagent.exe executable file runs, it compiles all CRYSON files from the web-metering folder into a snowpack file and sends it to the Snow Extender. After this process, no CRYSON files remain in the web-metering folder. 

What does the authentication and authorization flow look like for the Snow Inventory Agent and browser extension? 
The Snow Inventory Agent will send its inventory file daily to the Snow Extender over internet traffic during a randomized, one-hour interval. The Snow Extender can be bound with an SSL certificate so the traffic can be sent either open or encrypted. The inventory file is then passed to Snow Atlas with TLS again. The keys used can be rotated out using your custom keys. 

What is Snow Atlas' data encryption policy for data in transit? What is the encryption policy for data at rest? 
Data from the end user is passed from the Snow Inventory Agent to the Snow Extender and eventually into Snow Atlas. Snow inventory files are encrypted with AES-128 when in transit to Snow Atlas. 

Data at rest is achieved through managed Microsoft Azure Storage. All data at rest is encrypted with AES 256-bit key length. 

For information, see Secure data transit design.  

What is the data retention policy in Snow Atlas?  
Data in SaaS on Snow Atlas is stored and displayed until it stops coming through the discovery source itself (for example, a connector). Once this source is deleted or removed, data is erased from the system. For historical reasons, all users' PII data is also erased except the internal user ID. 

Are there any GDPR or ICO implications for the data collected by SaaS? 
The data collected by SaaS Management complies with GDPR and ICO regulations. Detailed information on data handling and compliance can be provided upon request by contacting Flexera Support. 

Performance and Metrics 

Can the Snow Inventory Agent be configured to run with minimal CPU usage? 
The Snow Inventory Agent is designed to run at the lowest priority, and the workload is reduced when other processes are running. This is true for both the Flexera Agent and Snow Inventory Agent. 

What is the performance of the browser extension in terms of memory and CPU utilization? Are there any performance metrics or performance overheads available?  
The browser extension's performance, including memory and CPU utilization, is designed to be minimal. Detailed performance metrics and overheads can be provided upon request by contacting Flexera Support. 

Are there estimates of per-machine bandwidth requirements? 
The requirement is minimal. The inventory files are small, typically 30-50kb.