Freshworks Marketplace

App cover art submitted by the app developer that represents the app

Tanium

Gain complete visibility of assets in Tanium through timely sync
Free
verified badge symbolVerified by Freshworksinfo tooltip icon
By clicking on "Install", you acknowledge and agree that your access and use of this application will be governed by the developer's terms of service and privacy policy. Freshworks may share your contact and usage information with the developer.
Install
OverviewReviewsHow to install?Privacy & SecurityNew
The integration between Freshservice and Tanium allows IT service management teams to keep track of all the assets in one place. The asset sync enables agents to get additional context about devices mapped to requester while resolving tickets. Key features possible with the Freshservice and Tanium integration: 1. Sync assets on Tanium to Freshservice at a specific window to add new assets and update existing asset details 2. View all the assets mapped to a requester via the Tanium widget on the ticket details page 3. Track all the Tanium assets from the Freshservice assets page Learn more: https://support.freshservice.com/en/support/solutions/articles/50000010241
empty_review_icon
No reviews available for this app.
Here is a quick step-by-step flow on how to successfully integrate & use these two apps 1. Start Installation - Click the "Install" button to open the App configuration page. 2. Validate Freshservice Credentials - The first tab on the configuration page is for validating Freshservice credentials. - Add the domain URL and API key to validate and proceed. 3. Configure Tanium Settings - Once the Freshservice connection is successful, the next step is Tanium configuration. - Enter your Tanium app URL and Credential to connect your Tanium account. Only Freshservice credentials are accepted. Please generate API token in Tanium to create corresponding credentials in Freshservice. - Here’s how to create API token in Tanium: https://help.tanium.com/bundle/ug_console_cloud/page/platform_user/console_api_tokens.html - Here’s how to create Freshservice credentials: https://support.freshservice.com/support/solutions/articles/50000003816-centralized-credential-store 4. Map Tanium Fields to Freshservice - In this step, you will be asked to map Tanium fields with that of Freshservice fields. Some fields are mandatory to complete the setup. - Once you finish this step, click on Install and your installation process is complete Detailed help article: https://support.freshservice.com/en/support/solutions/articles/50000010241
The information listed below is provided by the App Developer Partner pertaining to the data privacy policies of the latest app version available on the Freshworks Marketplace. The App Developer Partner is solely responsible for the accuracy of the information provided.
What is End-User data?
Any information that is generated or provided by individuals while using your apps in connection with Freshworks products.
Data Management and Storage
Does your app use AI or GenAI features?
No
Does your app use "Freshworks AI powered features or Freddy AI" and comply with Freshworks AI powered features and Freddy AI terms?
No
Does your app collect / process any End-User data?
No
Does your app store any End-User data?
Yes
What End-User data does your app store?
Encrypted credentials are stored
Countries where data is stored
Australia, Germany, India, United Arab Emirates, United States
What is the purpose of storing the data?
For scheduled synchronisation of asset resources.
Does your app share End-User Data with any third party entities?
No
Does your app transfer European Economic Area (EEA) residents’s End-User Data outside of the EEA?
No
Can the End-User data be exported?
No
Can End-User data be accessed through your app logs?
No
Is the End-User data encrypted at rest?
Yes
Elaborate the encryption methodology adopted
Below methodology is used for encryption 1. Encryption: Algorithm: AES with a 128-bit key with ECB(Electronic Codebook) mode 2. Padding: PKCS5Padding: Adds extra data to make sure it fits the encryption block size 3. Key Preparation: 3.1 Hashing: The secret key is turned into a fixed-size value using SHA-256 3.2 Truncating: The hashed key is shortened to 128 bits 4. Base64 encoding
Is the End-User data encrypted in transit?
Yes
Elaborate the encryption methodology adopted
Encrypted in transit using SSL/TLS protocols
Does your app adhere to the OWASP (Open Web Application Security Project) security standard?
Yes
Which OWASP guidelines or recommendations do you follow to ensure the security of customer data?
As per Freshservice OWASP guidelines (Authentication, Authorization Validation & SQLi Validation)
Does your app permanently delete the customer data as soon as the customer uninstalls the app?
No
What is the data retention period after app is uninstalled?
365
Does your app allow customers to request a custom End-User Data retention period?
No
close modal
close modal
Go to Developer Portal