Embedding Code in Electronic Messages for Secure Workflow Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for sending executable programming code via electronic messages often result in security flags or blocking, and require specialized architecture on both sender and receiver sides for point-to-point connections.
Innovation Solution
A method and system that includes a receiver device with a security component to authenticate the sender and authorize access to specific workflows, allowing parsing and execution of programming code within an electronic message without needing special architecture on the sender's side, using a receiving component, security component, and parsing component.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If programming code is sent as an attachment to an electronic message, then the code can be transmitted, but security systems may flag or block the message
Solution Approach 1:
The patent extracts the programming code from traditional attachment formats and embeds it directly within the electronic message body in a structured format. This separation removes the code from the attachment context that triggers security flags, allowing transmission without blocking while maintaining executable functionality.
Solution Approach 2:
The patent changes the format parameter of programming code from attachment-based to embedded text-based within the message body. By transforming the code representation and embedding it using structured delimiters and syntax highlighting, the message bypasses attachment-based security filters while preserving code integrity and executability.
2Reliability
If a point-to-point connection is created for secure code exchange, then security is improved, but special architecture is required on both sender and receiver sides
Solution Approach 1:
The patent makes the receiver device universal by enabling it to process embedded programming code through standard electronic message reception. The receiver performs security checks and code execution using built-in components without requiring specialized architecture, allowing any standard message receiver to handle secure code exchange.
Solution Approach 2:
The receiver device performs self-service security verification by checking whether the sender is authorized and whether the sender has permission to initiate workflows. This self-verification mechanism eliminates the need for complex mutual authentication architecture between sender and receiver, reducing device complexity while maintaining security.
3Reliability
If security checks are performed to verify sender authorization, then security is improved, but message processing time increases
Solution Approach 1:
The patent implements preliminary authorization verification where the receiver device checks sender credentials and workflow permissions before processing the embedded code. By performing these security checks upfront during message reception, the system ensures secure execution without delaying the actual workflow initiation, as authorization is confirmed before code parsing begins.
Data Source
AI summary
A method for a receiver device to process programming code contained in an electronic message. The electronic message is received. A security check is performed, including determining whether a sender of the electronic message is an authorized sender and determining whether the sender is authorized to access one or more workflows identified by an address of the electronic message. On a condition that the security check passes, the programming code is parsed and the one or more workflows identified by the address of the electronic message are performed at the receiver device based on the programming code.