Overview

Securing customer’s data is critical and CellarStone is committed to taking all steps to provide a safe and secure environment.

The data threats are broadly classified as Physical, Personnel, Procedural, & Technical.


Physical: Physical Systems may be accessed by unauthorized Users. All systems must be placed in a protected environment.

Security  Threats

Personnel: Unauthorized users can access the systems remotely. Proper authentication procedures and trusted user mechanisms should be implemented.

Procedural: Sometimes, knowingly or unknowingly data may be accessed by inappropriate users. So defining clear rules of data access and control can eliminate such threats.

Technical: Technology vulnerabilities are common now. Adopting the right tools to protect data, using proper debugging techniques, alerts and logging can help in mitigating these risks.

 

Multiple Layers of Security

MaxBlox leverages multiple layers of application based technology. MaxBlox has one of the most comprehensive technology architectures available.

layers of security

Various security aspects of the MaxBlox application from different perspectives are covered in the sections below.

 

Database Security:

An important benefit of a SaaS application is that it is inherently able to connect to the relevant tenant and other tenants are automatically disconnected in a single session. Once MaxBlox makes a connection to a single tenant after the login process, key aspects of that particular database is carried over to the connection details level, thereby automatically avoiding the chance of overlapping connection.

Apart from this, the database server itself is protected by IP filters that allow connections only from the servers that run the applications and services. This is in turn controlled by configuring the security to the port level. All other connections to the database server from any other servers will be rejected automatically and instantly. All the database connections are also logged to enable tracking and auditing in case of any unusual activity.

 

User Login:

As any other standard web application, in MaxBlox, the User login is facilitated through HTTP POST calls carried over secure HTTPS channel. The MaxBlox portal login pages are protected with security standards that can reject Cross Site scripting (XSS) attacks and SQL injection possibilities.

An advantage of having MaxBlox running over SaaS architecture is that, the login related databases are maintained in separate servers and individual security tuning can be done at this server and database level. These databases are usually made to run on separate auditing frequency and at a different level of security scrutiny.

appserver

Role Level Security:

Typically, access to resources and business functions in a SaaS application is managed by using roles that map to specific job functions within an organization. Each role is given one or more permission that enables users assigned to the role to perform actions in accordance with any relevant business rules.

user groups

Roles are managed within the application itself; they can contain individual user accounts. Individual user accounts can be assigned several different roles as required.

Depending on the roles to which a user is assigned, he or she is granted one or more permissions to perform specific operations or actions. These actions typically map directly to important business functions, or to the management of the application itself. For example, a purchasing application might include permissions for creating, submitting, approving, and rejecting purchase orders; an application for mortgage brokers might include permissions for checking a borrower's credit and granting a loan; and so forth. A single permission can be assigned to one or several roles, as necessary; each user will be granted the union of the permissions assigned to all roles to which the user belongs.

Functional Security

The menus, pages, and the mode of the pages inside MaxBlox portal goes through an additional security configuration that enables the compensation administrator to control what users will view once they are inside the application. These aspects of the pages can typically vary the page’s visibility to other users depending on whether the page can be edited by the user or not.

administrator

Row Owner security

Every record in the system is owned by the user who creates the record. The ownership of a record can be transferred to another user, if the administrator has provided the ability to do so. This security structure implies that the system knows who created, who modified, and who owns each record in the system.
On top of this structure a comprehensive business unit related security configuration is setup, so that the administrator can decide the record's visibility at each record level. The configurations facilitate security at Unit level, Units and Sub-Units level, and at the self-level, where a Unit can be anything that represents the security structure in an organization. For example, their security structure might be based on Territory and for others it might be the User’s role itself.


AD Integration

Business owners will have the peace of mind that all entry points to applications and data are kept in one single location within a secure AD Directory of the windows with the company's user policy, password-policy in mind. This helps because user policies should be dictated by the business owners not by the software vendors.

The AD Integration feature enables users to log in to MaxBlox using their user-account credentials from the Active Directory service provider, based on their Active Directory group membership.

single

Single Sign-On

Single sign-on (SSO) is a mechanism whereby a single action of user authentication and authorization can permit a user to access all other applications where he has access permission, without the need to enter multiple passwords. Single sign-on reduces human error, a major component of systems failure and is therefore highly desirable.

MaxBlox is integrated with Salesforce.com and has the ability to view the screens from Salesforce.com. The customer would only be required to login to his Salesforce.com account and would not need to login separately into MaxBlox. Salesforce.com identity is passed to MaxBlox and the login handler in MaxBlox authenticates the user and allow the access to the application.

Accessing Application – Authentication, Authorization & Access Control

MaxBlox uses role-based authentication system. All the users in the system can be defined with the role they perform. Each role defines which objects they are authorized to access and at what level of control (Read, Read-Write, Execute / Non-Execute etc).

authentication

MaxBlox Authenticates Users by Using SQL Authentication.

MaxBlox can also integrate with customer’s Active Directory and provide single sign-on access to the system. This way the user is not presented with another login screen to login into the application. The users are already logged into their corporate networks which are controlled by the administrator. MaxBlox can be configured to trust the user and forego its own login screen and give access to the system

login

 

Portal Module

Compressed & Encrypted Data

Important secured information such as Passwords are encrypted using Blow Fish 128-bit Algorithm and stored in the application database.
File transfers are also encrypted prior to transfers. Based on customer requirements, additionally VPN tunnel configurations are established.
In the Web Portal, the data is compressed from server using GZip and presented to the customer.

 

data

Sarbanes-Oxley(SOX Rules)

MaxBlox is in compliance with Sarbanes-Oxley Rules.

config

config2

Administrators can configure the relevant security rules, such as Password Expiry Days. They have the ability to configure the security rules, audit rule, access controlling rules and rules.

MaxBlox Environments

MaxBlox is deployable in one of the following ways:

• On-Premise Installation
• Hosted Environment – VPS – Multiple Databases
• Hosted Environment – VPS – Single Database
• Hosted Environment – Multi-tenant Environment


On-Premise Installation

This is the method in which the MaxBlox client will be installed in your local premises. The MaxBlox customer will be responsible for the maintenance and upgrades in this approach. The database maintenance and backup process also has to be executed on the premises by the customer. Different user groups may have access to separate apps in a multi-tenant environment.

Hosted Environment – VPS – Multiple Databases

In this method, a secure server will be allotted to multiple customers and the security of the access can be customized to a certain level. The numbers of databases in a server is decided based on the performance, similarities in the account setup, and the data to be handled. Upgrades, maintenance, and backups will be maintained by the vendor itself.

Hosted Environment – VPS – Single Database

This is similar to the above hosted setup, except for the fact that the server is provided to one single customer and the security can be controlled to a maximum extent. This is recommended for those who have high volumes of data and need more processing power dedicated to the organization.

Here are some of the typical Hardware configurations that we deploy for our MaxBlox variants.

table

Hosted Environment – Multi-tenant Environment

In this method, each account uses one or more applications within a multi-tenant hosted environment.

Audit Logging

Every action that the user performs can be logged in the system using the Audit Logging ability.
Customers can define for which object, what level of logging is required. The application comes with a default set of audit log options.

page

Conclusion

MaxBlox is a powerful, scalable, and flexible application platform software. MaxBlox’s architecture is designed to accommodate complex applications with comprehensive and multi-layered security.