EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB484002: MicroStrategy HyperIntelligence for Web Security and Privacy


Eduardo Alcazar-Bustillos

Quality Engineer, Senior • Strategy


This article addresses what permissions HyperIntelligence for Web uses and how these permissions can affect a user's security. The goal of this article is to help users understand MicroStrategy’s approach to security and emphasize that maintaining customer trust and security is critical to our mission.

As of Strategy 2020, you can view HyperIntelligence Cards on the web, your mobile device, or while perusing emails on Outlook using HyperIntelligence for Web, HyperIntelligence for Mobile, or HyperIntelligence for Office. 
When using HyperIntelligence for Web, Strategy wants to emphasize that your privacy and security are the top priority. As such, the goal of this article is to clarify certain permissions used in HyperIntelligence for Web for both Google Chrome and Microsoft Edge.

HyperIntelligence for Web Permissions


Strategy HyperIntelligence does not collect any data from a web page. Aside from the login information that is necessary for authentication, the only data that is transferred between the HyperIntelligence extension and the server is a list of keywords for enabled cards, and the card information when a match is hovered over. In both cases, this is data that has been provided to the Strategy platform by other authorized users.
The following permissions are used by HyperIntelligence:

webRequest, webRequestBlocking


These permissions allow the extension to modify or block requests in observed traffic. This is used to modify web request headers when authenticating through Strategy Library to allow for a seamless login experience. A user's data is not sent to the Strategy server using these permissions.
 

webNavigation

This permission allows the extension to read the current page's URL to determine which highlighting method will be used. 
 

Cookies


This permission allows the extension to read and modify cookies. This is only used to read cookies to determine if authentication is completed when using a third party authentication mode such as SAML or Trusted.

tabs 


This permission allows the extension to open and close new tabs. This is only used in conjunction with a third party authentication mode such as SAML or Trusted, as these authentication modes may require their own portal to be opened in a new tab to authenticate. 

https://*/, http://*//, file://*/


These permissions allow the extension to access web pages that use certain protocols. This is a necessary permission since all supported web pages begin with a protocol and the extension needs access to those web pages to run.

Storage


This permission allows the extension to store, retrieve, and track changes in a user's local data storage. The extension persists certain account information from the extension, such as the number of cards enabled. Non-HyperIntelligence data is not accessed by the extension.

nativeMessaging 


This permission allows the extension to communicate with native applications running on the machine, outside of the browser. This is used during the installation process. If the user inputs a URL into the extension installer, it is passed to the extension using this permission.

downloads


This permission allows the extension to make downloads. It is used to export error logs from the extension.

 


Comment

0 comments

Details

Knowledge Article

Published:

January 27, 2020

Last Updated:

August 4, 2020