Pilvi™ Technology Description

 

layersPilvi™ Technology is developed to sell cloud services. It has a unique engine that handles selling, provisioning, managing and billing of different usage based services. Technology is made to scale and proven to be secure. It consist of three separate but interoperable layers.

Client Layer responsive web applications provides the unique user experience to end users and shop managers. They are developed with the Backbone.js library and provides a seamless experience in web and mobile.

API Layer is the RESTful API gateway to Pilvi service. It authenticates the calls, interprets the messages and passes them to the core. It’s designed to be light and scalable so that it can handle traffic peaks easily.

Pilvi Core manages the entire service and provides connections to third party cloud services and other integration points. It consists of several interoperable Java EE modules. The modules are running in a clustered environment on GlassFish application servers.

 

Pilvi™ Technology Security

 
Pilvi takes security very seriously. We will do our utmost to protect the data stored and relayed by our platform. We have taken multiple measures to guarantee that our platform is secure to use. We have a continuous security awareness program and we hold regular risk management workshops in order to assess possible new risks.

Only authorized persons have access to our source code repositories and we undergo regular code reviews in order to identify possible vulnerabilities before the code is shipped.

Pilvi™ Technology utilizes multiple controls and lines of defense to protect the platform’s data and prevent possible attacks.

 
Standard platform security measures:

  • SSL is used to encrypt all traffic between the client software and Pilvi API’s
  • API’s require the client software to identify itself in order to open a session for the user
  • API’s don’t allow for user-provided data to be accessed without proper filtering and escaping, thus providing protection against SQL injection attempts and cross-site scripting
  • user passwords are salted and hashed using bcrypt and stored as hashes
  • all persistent data that is deemed sensitive is encrypted using symmetric-
    key encryption according to the OpenPGP standard
  • all user data can be physically separated from less sensitive service data
  • access to persistent storage is provided per subsystem
  • session keys are required to be generated using a cryptographically strong algorithm
  • multi-factor authentication is supported out of the box for additional user login security

 

Want to find out more?

Check our location and contact details and contact us.