How data is secured in StarMH platform
This blog discusses how each module of StarMH platform ensures data security
Atif Baig
1/15/2024 - 1 min read
For best security, most of the StarMH modules/components are deployed on client's internal servers and so client's reporting data never reaches our servers at any point. This approach gives a great peace of mind to our clients from data security standpoint.
StarMH Designer: This is deployed on MapleHeap server within our secure VPN and can be accessed over the internet. The reason for this deployment type is that our clients never have to share any private/confidential data while using this designer tool.
StarMH Admin: This is deployed on the client's internal server to ensure best security for the private/confidential data. Ideally this should not be accessible outside of the client's VPN. The reason for this recommendation is that the admin application can be used to update production data inside the reporting database. It can also be used to add new StarMH reporting tables.
StarMH AI Module: StarMH AI module comprises of two components. One is StarMH deep learning API and the other one is a background process than performs daily AI model training and stores the predictions in the reporting database. Both of these components are set up on client's local servers which make them completely secure.
StarMH Session Manager: This is deployed on the client's internal server to ensure best security for the private/confidential data. Ideally this should not be accessible outside of the client's VPN as this can be used to create new StarMH dashboard sessions which should never be allowed for any application running outside the client's VPN.
StarMH Dashboard: It is deployed on the client's internal server. This is the only module that might need to be accessible over internet. However, to ensure security it can only be accessed with a valid StarMH session which is created using StarMH session manager that runs in client's local environment and not accessible over internet.
