Browse Prior Art Database

Agent trusted zone for sensitive information exchange or confirmation

IP.com Disclosure Number: IPCOM000245355D
Publication Date: 2016-Mar-03
Document File: 2 page(s) / 27K

Publishing Venue

The IP.com Prior Art Database

Abstract

A setup is proposed of trusted groups of agents in customer environment where agents can verify between themselves that information received from outside is reliable. Also in a trusted zone, an administrator could update one of agents what to do in case of failure. Agent could share this information with trusted group members when agents ask what to do because of communication server issues.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Agent trusted zone for sensitive information exchange or confirmation

This proposal is related to the domain of using SaaS client-server solution. Agents are distributed in client environment. All configuration settings agents downloads from cloud servers.

There are 2 issues when using information from could located server only could be problematic:

- Hackers can deliver to agent information to switch to cooperate with different server, then using this different server, do "inappropriate " things. Would be good to have locally trusted source when agent can confirm that requested operation it correct.

- On the other hand, in case of serious server failure or internet connection issue, it could be necessary to reconfigure all agents to start cooperating with new server. User can use for this external tools to distribute this information to agents, however build in, secure solution would be appreciated.

We propose to setup trusted groups of agents in customer environment where agents can verify between themselves that information received from outside is reliable. Also in trusted zone, administrator could update one of agents what to do in case of failure. Agent could share this information with trusted group members

when agents ask what to do because of communication server issues.

Agent deployed in customer environment are grouped in trusted zones, where there some agents has authority to confirm or answer request for particular information. Trusted zone is confidential outside the local environment, so apart from administrator, none knows which agents have special authority to authorize some external requests.

Features:

• Trusted zones with distinguished agents to confirm some operations.

• Trusted zones with distinguished agents as entry points for additions information required by system (example: what to do bc of server failure).

The main idea is to pre-define the so called trusted zones with in the agents. Agents

which are grouped together in one trusted zone are able to


• Double check the re-configuration orders which are coming from the main server


• Look for help in case of problems with server communication

The exemplary usage scenario can look like this:

1. Environment migration from Server to Server
The mi...