Browse Prior Art Database

Monitoring usage of cloud SaaS applications with use of HTML 5 Web Storage

IP.com Disclosure Number: IPCOM000245624D
Publication Date: 2016-Mar-22
Document File: 3 page(s) / 26K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method is proposed for using HTML 5 Web Storage to detect and montior use of web applications for Software Asset Management pourposes.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 3

Monitoring usage of cloud SaaS applications with use of HTML 5

55 Web Storage

Web Storage

Monitoring of use of Cloud SaaS applications is important from License Compliance & Security Compliance. The idea allows to monitor usage of such applications by looking at HTML 5 Web Storage data on end-users devices (laptops, mobile devices, thin clients like Chromebook). Current SAM solutions do not provide such functionality. Monitoring use of cloud SaaS applications is very challenging especially when there is no access to SaaS central server for collecting license information. Since most cloud SaaS software is used by end-users through WebBrowser and HTML 5 standard becomes to be widely used, HTML 5 Web Storage could be utilized for monitoring use of SaaS application on end-user endpoints. In near future a typical SaaS application that runs on a web browser will use HTML 5 Web Storage to keep local data that is necessary to run application.

Also Web Storage will be used to keep data that is necessary for running such application in offline mode (when network connection to the cloud is not available at the moment).

The Web Storage will contain the following data:


1. Local configuration of the cloud application

2. Data on which SAAS application is working inside a the web browser e.g. document in a SaaS text editor

The solution would contain the following steps:

1. All end-user web browsers would contain a plugin that allow analysis of data in HTML 5 Web Storage. The plugin would be distributed to client computers by a SAM solution or included into a standard image of an operating system

2. The plugin would be available for desktop, mobile (e.g. phone) and embedded (e.g. Chromebook) web browsers

3. The plugin would contain set of rules (signatures) that define foot print of SAAS applications in HTML 5 Web Storage on end-user web storage. There could be two kind of signatures

a. discovery - to discover that a SaaS application was run on a web browser. This signature would typically be based on the Web Storage Key data, but also could be defined on patterns that would be matched on the Web Storage Value data

b. usage - to discover that a SaaS application was used actively by a user from last time when the signature was matched. Typically this signature would discover changes in the Web Storage Data that is related to a SaaS application. In particular, a set of data should be monitored on data that is often changed when an application is used e.g. in a SaaS Text Editor it could be part of storage where edited document is stored. On...