Controlled security domains
View Patent ↗A security domain control method includes defining a sequential series of security domains; designating one of the security domains as a current domain; generating a plurality of security tokens under the current security domain, each security token being configured to enable a party to exchange cryptographically secured messages with another party that is holding any one of: a token generated under the current security domain; a token generated under at least one next security domain in the series; and a token generated under at least one previous security domain in the series; and subsequently designating a next one of the security domains in the series as a current domain.
1. A method of controlling secure system, the method comprising:
a host server defining a series of security domains;
the host server sequentially designating each one of the series of security domains as a current domain, such that only one of the series of security domains is the current domain at any given time; and
the host server generating a plurality of security tokens under the current security domain, each security token being configured to enable a first party to exchange cryptographically secured messages with a second party that is holding a token generated under the current security domain; a third party that is holding a token generated under a next security domain in the series; and a fourth party that is holding a token generated under a previous security domain in the series.
2. The method as claimed in claim 1 , wherein each security token is configured to enable a party to exchange cryptographically secured messages with another party that is holding a token generated under two previous security domains in the series.
3. The method as claimed in claim 1 , wherein each security domain is defined using Public Key Infrastructure (PKI), and comprises a respective public key.
4. The method as claimed in claim 3 , wherein each security token comprises the respective public key of each one of the current security domain; the next security domain in the series; and the previous security domain in the series.
5. The method as claimed in claim 4 , wherein each security token further comprises the respective public key of a second previous security domain in the series.
6. The method as claimed in claim 1 , further comprising automatically updating a user's security token when the user logs into a secure server.
7. A non-transitory computer-readable medium comprising machine-readable software instructions for controlling a computer to implement the method of claim 1 .