Try : Insurtech, Application Development










Dev Ops(3)

Enterprise Solution(22)




Augmented Reality(17)

Customer Journey(12)


User Experience(34)

AI in Insurance(31)


Product Innovation(37)





Telehealth Care(1)


Artificial Intelligence(109)



Cognitive Computing(7)

Computer Vision(8)

Data Science(14)


Intelligent Automation(26)

Machine Learning(46)

Natural Language Processing(13)

FlowMagic — The Visual AI Platform for Insurer Workflows

For any operational effort across large organizations, a significant amount of time and resources are spent manually inputting data into downstream systems. These processes more specifically affect insurance practices that are deeply reliant on back-office processes. The bulk of the insurance workforce is condensed into operations and support functions (e.g. policy issuance and servicing). Here, data is typically unstructured and locked away in heaps of paper-based documents, emails, scanned images, excel worksheets, pdf, and word reports.

Typically in insurance, at least 90% of unstructured documents are manually processed, while an ‘Insurance Policy Administration System’ is on average between 15–20 years old — forcing them at times to lag behind their financial services peers. 

To make the most out of the massive quanta of inbound data stored in siloed systems, firms have recently begun to take a serious look at streamlining data migration using AI-based tools. The burgeoning reality is that a tremendous amount of man-hours are wasted in repetitive tasks leading to increased processing times and slower through rates for insurance.

Proportion of Unstructured Data in P&C Insurance (%)

portion of Unstructured Data in P&C Insurance (%)

Source: SPS Data

AI Gets Holed Up In Silos
According to a recent IDG study titled the ‘Future of Work’, less than 50% of global enterprises have deployed intelligent automation technologies (such as AI, Cognitive Automation or RPA), while over two-thirds find greater difficulty in integrating these people, process and AI. Over fifty percent of enterprises identify siloed deployments and overwhelmed internal application development teams as long-term issues. This can create friction between teams operating in silos and those trying to derive insights from unstructured docs. Nearly a third of enterprises identified getting AI into production and live services as the single biggest challenge to overcome.

According to a McKinsey paper, intelligent process automation is at the core of next-generation operational business models.

The Need For Intelligent Document Processing

The Need For Intelligent Document Processing

Source: Imaginea

A New Platform

MantraLabs has launched a unique solution to address the insurer’s pain-point through an intelligent platform built especially for silos, The solution addresses several dependency issues and is built to scale, making it a vendor-neutral platform that doesn’t require deep coding skills. The christened solution is FlowMagic — a simple and easy to use visual AI platform for insurer workflows.

FlowMagic applies proprietary AI techniques, Machine Learning and NLP, to extract any target data from unstructured documents. At the recently convened 4th Annual Insurance India Summit and Awards 2019 held in Mumbai, Mantra Labs presented a live demonstration of FlowMagic’s unique capabilities. Mantra Labs CEO Parag Sharma took the opportunity while speaking in front of industry leaders and attendees, to showcase our true AI-first approach to solving insurance challenges. FlowMagic truly embodies the spirit of that approach in tackling the problems plaguing traditional insurers — such as reducing document delivery times to the back-office by 80%.


Customizable Workflows
The platform is equipped with plug and play capability. Using quick drag and drop, one can create custom workflows to address the most pressing operational functions, such as insurance agent onboarding or verifying medical invoices. Mantra Labs has pre-built over 50 AI-powered apps for its users to take advantage of. The open platform also allows insurers to create their own apps that can be seamlessly integrated.


By leveraging machine learning, insurers can use FlowMagic to shift intensive operational functions into auto-pilot. The AI tool can automate the ‘classify, extract, and validate’ cycle for insurers and direct decision-ready insights straight to decision-makers.

Although declining, the Insurance field is still paper-intensive. Insurers are shifting towards AI-powered engines to replace unnecessary manned effort behind redundant operational tasks. These systems can bring about at least a 70% reduction in manual processing and 30% improvement in cost-efficiencies throughout the value chain. 

To know more about how FlowMagic is helping insurance leaders cognitively automate complex processes, reach out to us at hello@mantralabsglobal.com 


Knowledge thats worth delivered in your inbox

12 Tips To Secure Your Mobile Application

Cyber attacks and data theft have become so common these days especially when it comes to mobile applications. As a result, mobile apps that experience security breaches may suffer financial losses. With many hackers eyeing to steal customer data, securing these applications has become the number one priority for organizations and a serious challenge for developers. According to Gartner’s recent research, Hype Cycle for Application Security, investment in application security will increase by more than two-fold over the next few years, from $6 billion this year to $13.7 billion by 2026. Further, the report stated, “Application security is now top-of-mind for developers and security professionals, and the emphasis is now turning to apps hosted in public clouds,” It is crucial to get the fundamental components of DevOps security correct. Here are the 12 tips to secure your mobile application: 

1. Install apps from trusted sources:

It’s common to have Android applications republished on alternate markets or their APKs & IPAs made available for download. Both APK and IPA may be downloaded and installed from a variety of places, including websites, cloud services, drives, social media, and social networking. Only the Play Store and the App Store should be allowed to install trustworthy APK and IPA files. To prevent utilizing these apps, we should have a source check detection (Play Store or App Store) upon app start.

Also read, https://andresand.medium.com/add-method-to-check-which-app-store-the-android-app-is-installed-from-or-if-its-sideloaded-c9f450a3d069

2. Root Detection:

Android: An attacker could launch a mobile application on a rooted device and access the local memory or call specific activities or intents to perform malicious activities in the application. 

iOS: Applications on a jailbroken device run as root outside of the iOS sandbox. This can allow applications to access sensitive data stored in other apps or install malicious software negating sandboxing functionality. 

More on Root Detection- https://owasp.org/www-project-mobile-top-10/2016-risks/m8-code-tampering

3. Data Storing:

Developers use Shared Preferences & User Defaults to store key-value pairs like tokens, mobile numbers, email, boolean values, etc. Additionally, while creating apps, developers prefer SQLite databases for structured data. It is recommended to store any data in the format of encryption so that it is difficult to extract the information by hackers.

4. Secure Secret Keys:

API keys, passwords, and tokens shouldn’t be hardcoded in the code. It is recommended to use different techniques to store these values so that hackers cannot get away quickly by tampering with the application. 

Here’s a reference link: https://guides.codepath.com/android/Storing-Secret-Keys-in-Android

5. Code Obfuscation

An attacker may decompile the APK file and extract the source code of the application. This may expose sensitive information stored in the source code of the application to the attacker which may be used to perform tailored attacks. 

It is better to obfuscate the source code to prevent all the sensitive information contained in the source code.

6. Secure Communication:

An attacker may perform malicious activities to leverage the level of attacks since all communication is happening over unencrypted channels. So always use HTTPS URLs over HTTP URLs.

7. SSL Pinning:

Certificate pinning allows mobile applications to restrict communication only to servers with a valid certificate matching the expected value (pin). Pinning ensures that no network data is compromised even if a user is tricked into installing a malicious root certificate on their mobile device. Any app that pins its certificates would thwart such phishing attempts by refusing to transmit data over a compromised connection

Please refer: 


8. Secure API request & response data

The standard practice is to use HTTPS for the baseline protection of REST API calls. The information sent to the server or received from the server may be further encrypted with AES, etc. For example, if there are sensitive contents, you might choose to select those to encrypt so that even if the HTTPS is somehow broken or misconfigured, you have another layer of protection from your encryption.

9. Secure Mobile App Authentication:

In case an application does not assign distinct and complex session tokens after login to a user, an attacker can conduct phishing in order to lure the victim to use a custom-generated token provided by the attacker and easily bypass the login page with the captured session by using a MiTM attack.

i) Assign a distinct and complex session token to a user each time he/she logs on successfully to the application. 

ii) Terminate the session lifetime immediately after logging out. 

iii) Do not use the same session token for two or more IP addresses. 

iv) Limit the expiry time for every session token.

10.  Allow Backup 

Disallow users to back up an app if it contains sensitive data. Having access to backup files (i.e. when android:allowBackup=”true”), it is possible to modify/read the content of an app even on a non-rooted device. So it is recommended to make allow backup false. 

11. Restrict accessing android application screens from other apps

Ideally, your activities should not give any provision to the opening from other services or applications. Make it true only when you have a specific requirement to access your flutter screens from other apps otherwise change to android:exported= ”false”

12. Restrict installing packages from the android application

REQUEST_INSTALL_PACKAGES permission allows apps to install new packages on a user’s device. We are committed to preventing abuse on the Android platform and protecting users from apps that self-update using any method other than Google Play’s update mechanism or download harmful APKs.


Mobile Apps have become more personalized than ever before with heaps of customers’ personal data stored in them every day. In order to build trust and loyalty among users and prevent significant financial and credential losses for the companies, it is now crucial to make sure the application is secure for the user. Following the above-mentioned mobile app security checklists will definitely help to prevent hackers from hacking the app.

About the Author:

Raviteja Aketi is a Senior Software Engineer at Mantra Labs. He has extensive experience with B2B projects. Raviteja loves exploring new technologies, watching movies, and spending time with family and friends.

Read our latest blog: Implementing a Clean Architecture with Nest.JS


Knowledge thats worth delivered in your inbox

Loading More Posts ...