Secure Email Module for Mobile Data Leakage Prevention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile computing devices face security risks due to data leakage and breaches when using native email clients, as they allow unintended data sharing and violate corporate security policies, especially with the loose standards on mobile devices and the ability of apps to send data as attachments.

Innovation Solution

The implementation of a secure email module that transparently handles encrypted data between mobile applications, native email clients, and secure proxies without modifying the underlying code, using a secure email module configured to authenticate applications, encrypt data, and enforce security policies to prevent data leakage and breaches by intercepting and replacing API calls, and managing data types and encryption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a native email client is used to send data from mobile applications, then email transmission functionality is enabled, but data security is compromised due to unintended data leakage and breaches

Engineering Contradiction:
Improveemail transmission functionalityVSAvoiddata security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces a secure email module as an intermediary component between mobile applications and the native email client. This module intercepts API calls from applications, authenticates them, and enforces security policies before allowing email transmission. The intermediary layer maintains both email functionality and data security by filtering and controlling the data flow without requiring changes to existing applications.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If security policies are enforced to prevent data leakage, then data security is improved, but application functionality is restricted

Engineering Contradiction:
Improvedata securityVSAvoidapplication functionality
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The secure email module implements dynamic security policy enforcement that adapts to different applications and data types. Rather than applying uniform restrictions, the system authenticates each application and applies specific security policies based on the application's identity and the nature of the data being transmitted. This dynamic approach allows legitimate application functionality to proceed while blocking only the harmful data leakage scenarios.

Inventive Principle:
Principle #15Dynamics

3Reliability

If code modification is implemented to secure email transmission, then data security is improved, but device complexity increases

Engineering Contradiction:
Improvedata securityVSAvoidsystem modification requirements
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the security functionality into a separate, standalone secure email module that operates independently from mobile applications. This segmentation allows security enforcement without requiring modifications to application code or the operating system core. The module intercepts and processes API calls at a higher level, maintaining security while preserving the simplicity and integrity of existing application codebases.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP3022677B1Systems and methods for securing email in mobile devices
Publication Date: 2019.08.28 CA TECH INC
  • EP3022677B1 patent drawingFigure 1
  • EP3022677B1 patent drawingFigure 2
  • EP3022677B1 patent drawingFigure 3

AI summary

A computer-implemented method for providing secure mobile email communications is described. At least one application programming interface (API) of a native email client is hooked in order to transmit data securely via email. The native email client is native to an operating system of the mobile device. An email originating from a registered application is detected, via the hooked API. The email includes the data to transmit securely. The registered application is registered in a registry according to a mobile application authentication procedure. The registry includes a plurality of registered applications authenticated according to the mobile application authentication procedure.