Anti-phish Token Injection for Third-party Communication Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing secure communication tunnels fail to authenticate electronic communications transmitted by legitimate third-parties on behalf of legitimate entities, leading to decreased recipient confidence in the security of such communications.
Innovation Solution
Incorporating an anti-phish, personalized, security token into electronic communications, which can be injected by an edge server using a database of unique tokens associated with each recipient, thereby authenticating the communication and increasing recipient confidence.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a secure communication tunnel is created for direct communication between legitimate entity and client, then communication security is improved, but the ability of third-parties to transmit communications on behalf of the entity is lost
Solution Approach 1:
The patent introduces an intermediary authentication mechanism (anti-phishing token system) that allows third-parties to act as mediators in communicating on behalf of the legitimate entity. The edge server validates third-party communications by injecting anti-phishing tokens, enabling third-parties to function within the secure communication framework without compromising security.
Solution Approach 2:
The patent segments the communication authentication process into separate components: the secure communication tunnel for encryption, the anti-phishing token database for authentication, and the edge server for token injection and validation. This segmentation allows the system to maintain secure direct communication while enabling third-party participation through verified token-based authentication.
2Reliability
If anti-phish security tokens are injected into electronic communications, then recipient confidence in authenticity is improved, but system complexity increases
Solution Approach 1:
The system implements self-service authentication where the edge server automatically retrieves and injects anti-phishing tokens into communications without requiring manual intervention. The database stores pre-generated tokens associated with recipients, and the edge server autonomously performs token injection, reducing operational complexity while maintaining high recipient confidence.
Solution Approach 2:
The patent performs preliminary actions by pre-generating and storing anti-phishing tokens in the database before communications occur. Tokens are associated with recipient identifiers in advance, allowing the edge server to quickly retrieve and inject appropriate tokens during communication transmission, avoiding complex real-time authentication processes.
Data Source
AI summary
Methods for securing an electronic communication is provided. In a registration process, an anti-phish, personalized, security token may be created and/or selected for a predetermined account. The token may be stored in a database at an enterprise location. An electronic communication may be generated at a third-party location on behalf of the enterprise. The communication may be forwarded from the third-party location to a recipient associated with the account. The communication may be intercepted at an edge server. The edge server may be located at the third-party location or the enterprise location. The edge server may be in communication with the database. The edge server may select, from the database, the anti-phish token that is associated with the account. The selected token may be injected into the communication. The communication with the token may be transmitted to the recipient.