System for authorising data access

1. A computer-implemented method for sharing data associated with a first user, the method comprising:

storing, at a first system, user data associated with the first user;

storing, at the first system, a first authorised entity database comprising a plurality of authorised entity labels each indicative of an identifier of an authorised entity, wherein storing the first authorised entity database comprises:

transmitting, from the first system to an authorisation system, a plurality of requests to access a second authorised entity database stored at the authorisation system; and

receiving and storing, at the first system, at least a portion of the second authorised entity database in response to each one of the plurality of requests to access the second authorised entity database;

wherein the plurality of requests to access the second authorised entity database are transmitted in a predefined time sequence, wherein the predefined time sequence comprises a predefined time interval between each adjacent one of the requests to access the second authorised entity database, and wherein the predefined time sequence is configurable, by the first system, based on system conditions;

storing, at the first system, an unauthorised entity database comprising a plurality of unauthorised entity labels each indicative of an identifier of an unauthorised entity;

receiving a first access message, from a second system, associated with a request for access to the user data stored at the first system, the first access message comprising a second system label indicative of an identifier of the second system;

in response to receiving the first access message, comparing the second system label with the plurality of authorised entity labels and the plurality of unauthorised entity labels stored at the first system;

in response to identifying that the second system label matches an authorised entity label and that the second system label does not match an unauthorised entity label, transmitting a grant message indicative that the request for access is granted; and

preventing transmission of the grant message, if the second system label in the first access message matches an unauthorised entity label and/or does not match an authorised entity label.

2. The computer-implemented method of claim 1 wherein storing the first authorised entity database at the first system comprises:

transmitting, from the first system to an authorisation system, a request to access the second authorised entity database stored at the authorisation system; and

receiving and storing, at the first system, at least a portion of the second authorised entity database in response to the request to access the second authorised entity database.

3. The computer-implemented method of claim 1 wherein the first access message comprises a request for an intent web token which validates a request for access to the user data stored at the first system.

4. The computer-implemented method of claim 1 wherein the first access message comprises a request for access to the user data stored at the first system.

5. The computer-implemented method of claim 1 wherein the first access message comprises a request to redirect a first user device to the first system for the first user to provide authorisation for the second system to access the user data.

6. The computer-implemented method of claim 1 further comprising:

receiving a second access message, from the second system, associated with the request for access to the user data stored at the first system, the second access message comprising the second system label; and

in response to receiving the second access message, comparing the second system label with the plurality of authorised entity labels stored at the first system and identifying a match between the second system label and at least one of the plurality of authorised entity labels stored at the first system and, in response, transmitting a grant message indicative that the request for access is granted.

7. The computer-implemented method of claim 6 wherein the second access message comprises a request for an execute web token which validates a request for the first system to transmit the user data to the second system.

8. The computer-implemented method of claim 6 wherein the second access message comprises a request for the first system to transmit the user data to the second system.

9. The computer-implemented method of claim 6 further comprising:

in response to receiving the second access message, comparing the second system label with the plurality of unauthorised entity labels stored at the first system and not identifying a match between the second system label and at least one of the plurality of unauthorised entity labels stored at the first system and, in response, transmitting a grant message indicative that the request for access is granted.

10. The computer-implemented method of claim 9 further comprising:

in response to receiving the second access message, comparing the second system label with the plurality of authorised entity labels stored at the first system and not identifying a match between the second system label and at least one of the plurality of authorised entity labels stored at the first system and, in response, preventing transmission of the grant message.

11. The computer-implemented method of claim 1 further comprising:

receiving or inputting, at the first system, an unauthorised entity detection message comprising a label indicative of an identifier of an entity suspected of fraudulent activity and/or suspected of being subject to a security breach; and

storing, in the unauthorised entity database at the first system, the label from the unauthorised entity detection message as an unauthorised entity label indicative of an identifier of an unauthorised entity.

12. A data management system for sharing data associated with a first user, the data management system comprising:

a data storage device configured to:

store user data associated with the first user;

store a first authorised entity database comprising a plurality of authorised entity labels each indicative of an identifier of an authorised entity, wherein storing the first authorised entity database comprises:

transmitting, from the first system to an authorisation system, a plurality of requests to access a second authorised entity database stored at the authorisation system; and

receiving and storing, at the first system, at least a portion of the second authorised entity database in response to each one of the plurality of requests to access the second authorised entity database;

wherein the plurality of requests to access the second authorised entity database are transmitted in a predefined time sequence, wherein the predefined time sequence comprises a predefined time interval between each adjacent one of the requests to access the second authorised entity database, and wherein the predefined time sequence is configurable, by the first system, based on system conditions; and

store an unauthorised entity database comprising a plurality of unauthorised entity labels each indicative of an identifier of an unauthorised entity;

wherein the data management system further comprises processing circuitry configured to:

receive a first access message, from a remote system, associated with a request for access to the user data stored at the first system, the first access message comprising a remote system label indicative of an identifier of the remote system;

compare the remote system label with the plurality of authorised entity labels and the plurality of unauthorised entity labels stored at the first system, in response to receiving the first access message;

transmit a grant message indicative that the request for access is granted, in response to identifying that the remote system label matches an authorised entity label and that the remote system label does not match an unauthorised entity label; and

prevent transmission of the grant message, if the remote system label in the first access message matches an unauthorised entity label and/or does not match an authorised entity label.