GB2488520A - Managing user access to a database by requesting approval from approver. - Google Patents

Managing user access to a database by requesting approval from approver. Download PDF

Info

Publication number
GB2488520A
GB2488520A GB1102713.3A GB201102713A GB2488520A GB 2488520 A GB2488520 A GB 2488520A GB 201102713 A GB201102713 A GB 201102713A GB 2488520 A GB2488520 A GB 2488520A
Authority
GB
United Kingdom
Prior art keywords
user
access
approver
request
database
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
GB1102713.3A
Other versions
GB201102713D0 (en
Inventor
Ramesh Sambamoorthy
Girish Bangarapet Shivakanth
Ravi Kumar Ventrapati
Sridhar Seetharamaiah
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
JK TECHNOSOFT UK Ltd
Original Assignee
JK TECHNOSOFT UK Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by JK TECHNOSOFT UK Ltd filed Critical JK TECHNOSOFT UK Ltd
Priority to GB1102713.3A priority Critical patent/GB2488520A/en
Publication of GB201102713D0 publication Critical patent/GB201102713D0/en
Publication of GB2488520A publication Critical patent/GB2488520A/en
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/40—User authentication by quorum, i.e. whereby two or more security principals are required
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6227—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database where protection concerns the structure of data, e.g. records, types, queries
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Economics (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Quality & Reliability (AREA)
  • Operations Research (AREA)
  • Databases & Information Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Marketing (AREA)
  • Game Theory and Decision Science (AREA)
  • Educational Administration (AREA)
  • Development Economics (AREA)
  • Storage Device Security (AREA)

Abstract

Disclosed is a system for managing user access to database systems. The method uses a central rules engine to process requests from users for access to the database system. The processed request is, sent with information relating to the user, to an approverâ s terminal for approval by that person. If the requested is approved an approval message is sent and the database is modified to enable access for the user. The rules may include compliance rules and separation of duties. The user information may include current access rights. The database system may be an enterprise resource planning database system. The request for approval may be sent to a second approver if the a response from the first is not received in a set time. The request may sent to a second approver and the database modified only if a approval message is received from both approvers.

Description

A METHOD AND SYSTEM FOR MANAGING USER ACCESS TO A
DATABASE
Field of Invention
The present invention is in the field of user access management. In particular, but not exclusively, the present invention relates a system for managing user access to a database.
Background
Databases store different sets of information. Some databases provide access to multiple users. It can be important to manage user access to different sets of information, that is, the user access must be compartmentalised to ensure that users only have access to the sets of information for which they are authorised.
Users can be authorised for different sets of information depending on reasons such as confidentiality, security or financial compliance laws.
For example, one database system is called enterprise resource planning (ERR). An ERR system integrates internal and external management information across an entire organisation into one system to standardise and simplfy access across the organization. Areas integrated include accounting, finance, budgeting, human resource, asset management, customer relationship management, marketing, supply chain and procurement.
There is no prior art system to manage the user authorisation process. If users require access to different sets of information they must make an IT support request or contact the database administrator.
It is an object of the present invention to provide a system for managing user access to a database which overcomes the disadvantages of the prior art, or at least provides a useful alternative.
Summary of Invention
According to a first aspect of the invention there is provided a computer-implemented method for managing user access to a database system, including: i) receiving a request from a terminal of a user for a specific type of access to a database system; ii) processing the request in accordance with a set of rules in conjunction with information relating to the user to determine whether access can be granted to the user; iii) transmitting a request for access approval to a terminal of an approver; iv) receiving an approval message; and v) modifying the database system to enable access for the user.
According to another aspect of the invention there is provided a system for managing user access to a database system, including: a communications transceiver configured to receive a request from a terminal of a user for a specific type of access to a database system; a memory configured to store a set of rules relating to user access; a processor configured to utilise the set of rules and information relating to the user to determine whether access can be granted to the user; a communications transmitter configured to transmit a request for access approval to a terminal of an approver; a communications receiver configured to receive an approval message; and a database interface system configured to modify the database system to enable access for the user.
Other aspects of the invention are described within the claims.
Brief Description of the Drawings
Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings in which: Figure 1: shows a system in accordance with an embodiment of the invention; Figure 2: shows a method in accordance with an embodiment of the invention; Figure 3: shows a method implementing in relation to an ERP system in accordance with an embodiment of the invention; and Figure 4: shows a hierarchy of approvers in accordance with an embodiment of the invention.
Detailed Description of Preferred Embodiments
The present invention provides a method, system, and software for managing user access to a database system such as an Enterprise Resource Planning (ERP) database system.
In Figure 1, a system for managing user access is shown. A server 100 is shown. The server 100 includes a communications transceiver 101 for communicating with a plurality of terminals 102, 103, 104. The transceiver 101 may communicate with the terminals 102, 103, 104 through a network infrastructure 105 such as a LAN, Internet, telecommunications infrastructure or a combination of networks. Several terminals are shown including a terminal 102 associated with a user and a terminal 104 associated with an approver.
The server 100 includes a processor 106 and a database 107. The database 107 includes a set of rules. The rules relate to user access within a database system 108.
The server 100 is connected to the database system 108 using a database interface system 109.
In one embodiment the server 100 and the database system 108 are discretely located.
A method according to an embodiment of the invention will now be described with reference to Figures 1 and 2.
The user terminal 102 transmits a request for access to the database system 108 to the server 100. The server 100 receives the request in step 200. In step 201, the processor 106 extracts the set of rules from the database 107 and matches the request with the set of rules and information relating to the user in step 202. The information relating to the user may also be extracted from the database 107 in step 203 or it may be extracted from the database system 108.
A software component may implement the rule matching process.
The rules specify limitations on the access requested by the user.
A message relating to the user's access request is transmitted to the approver terminal 104 in step 204. The approver is provided with access to the limitations of matching rules, for example, the message may include the limitations added in step 205. The approver responds, for example through his terminal 104, by electing to grant, decline, or modify the user's access request.
The server 100 receives the approver's response in step 206 and actions the response. When the response specifies grant of the request or modified request the server 100 accesses the database system 108 and modifies access rights for the user to grant the access request in one of steps 207 or 208 respectively.
An embodiment of the invention will now be described with reference to Figures 3 to 4.
In this embodiment of the invention, the database system is an enterprise resource planning (ERP) database system 300 such as MFG/PROTM provided by QADTM.
An access request may be generated by a current user or a new user. The access request may relate to access to portions of the ERP system 300. For example, the portions include, for example, Voucher Maintenance, AP Payment, Purchase Order Maintenance, P0 Receipt, Create Customer Master, and Sales Order Maintenance. The access may relate to, for example, read, write, or read/write.
The access request may relate to an access for a role. For example, for a user with a Purchasing Officer role the access request will relate to the Purchasing portion of the ERP system, and for a user with a Accounts Officer role the access request will relate to the Accounts Payable portion of the ERP system.
The access request is generated on a terminal 301 of the user. The terminal 301 is preferably a computer system.
The access request is transmitted to a central server 302 via a communications infrastructure 303 such as an email system over a computer network.
The central server 302 extracts information relating to the user from a database 304. The database 304 is preferably co-located with the central server 302. The database 304 may be a Progress database. Alternatively, the data may be extracted from the ERP database system 300. The information relating to the user may include previously granted access requests, and/or previously denied access requests.
Where the user is a new user, basic data of the user may be provided as information relating to the user in conjunction with the access request. Where the user is an existing user and the user is moved to a different role or is promoted, earlier access requests may be modified as revoked and thus inapplicable. Where the user is leaving, information relating to the user may include an inactive status notifier.
The central server 302 also extracts a set of rules from a database 305.
The rules set includes rules relating to risk compliance and management. In particular, the rules may relate to Separation of Duty conflicts. For example, the rules may include: a) If access request and user information would result in access being provided to user for both Voucher Maintenance and AP Payment. Access to both would permit the user to create fictitious voucher and then initiate of fraudulent payment.
b) If access request and user information would result in access being provided to user for both Purchase Order Maintenance and P0 Receipt.
Access to both would permit the user to purchase unauthorized items and hide the purchase by not fully receiving order.
c) If access request and user information would result in access being provided to user for both Create Customer Master and Sales Order Maintenance. Access to both would enable a user to maintain a fictitious customer and initiate orders.
The central server 302 matches the rules with the user request and information about the user.
If the rules are matched by the server 302, the server 302 may add a message relating to the infringed rule to the request for access message to the approver.
The message may be transmitted to the approver terminal 306 via an email communications infrastructure 303. In an alternative embodiment, short message service (SMS) across a telecommunications infrastructure is used instead of or in conjunction with email. In yet a further embodiment, messages are transmitted using a web-based internet or intranet portal 307 to provide an interactive request notification and approval system.
The message may include a notification that there is a pending user access request, the message may also include the following information: the user identity, where to go to approve/deny the request, rules that have been matched/infringed, and/or consequences of matched/infringed rules.
Approver details are stored within a database 308 at the central server 302.
The approver is selected based on the particular user; or based on a designation, department or location applicable to the user. Other methods of defining the approver to select can be envisaged, including, selecting the approver based on the matched rule or type of access request.
There may be a time limit on when an approver is required to respond to the request for access approval. If the time limit is exceeded, then the server 302 may transmit a request for access approval to another approver at terminal 309. The additional approver may be defined as a backup to the first approver or the additional approver may be defined as a backup to the user.
In addition, the request for access may require approval by multiple approvers. In this case, multiple requests for access may be transmitted to terminals 306, 310 for each of the multiple approvers, or a message from a first approver in the chain may trigger the server 302 to transmit a request for access message for the next approver.
The approver(s) 306, 309, 310 may respond to the message by replying to the email. Preferably the approver(s) 306, 309, 310 respond by accessing an intranet portal 307. The intranet portal may be hosted by the central server 302, or the intranet portal 307 may feed responses back to the central server 302.
The approver(s) 306, 309, 310 may respond by approving the request, by modifying the request and approving it, by providing a mitigation for the matched/infringed rules and approving the request, or by denying the request.
Where there are multiple approvers, all the approvers 306, 310 may have to approve the request before any modifications relating to access are made to the database system 300.
Where there are backup approvers, only one of approver 306, 309 may have to approve the request before any modifications relating to access are made to the database system 300.
Modifications to the database system 300 are made using a Common Interface Menu (CIM) flat file. A CIM file is a method in which standard QADTM Screens are invoked and data parsed into QADTM application by following all validations and error processing.
An example of a CIM file for making modifications is as follows: @@BATCH LOAD
UID
Name --- access-groups ---@@END The modifications correspond to the approved request.
Figure 4 shows an approver hierarchy illustrating backup approvers and multiple approvers. A request may be sent first to Approver Al. If Approver Al does not respond within a defined time period such as one week, the request may be sent to a backup approver to Approver Al. In this case the backup approver is Approver A2. Whichever Approver Al or A2 approves the request, the request may be then sent for a second level of approval to Approver B. Once Approver B approves the request, it may be sent for a third level of approval to Approver Cl. As for Approver Al, Approver Cl may have defined backup approver, and if Approver Cl does not respond to the request within a defined time period, the request may be sent to Approver 02. Once all levels have approved the request, the central server 302 may process the request by modifying the database system 300 to grant user access in accordance with the request It will be appreciated that the present invention may be implemented as software executing on computer hardware or within hardware itself.
A potential advantage of some embodiments of the present invention is that as the user access is determined by a set of rules at a single location, user access management can be performed efficiently and consistently.
A further potential advantage of some embodiments of the present invention is that the use of a central server reduces communication messages from the user terminals to approver terminals, and from the user terminals to the database system.
A yet further potential advantage of some embodiments of the present invention is that a user access requests can be automatically captured and collated permitting greater security and auditing capabilities.
While the present invention has been illustrated by the description of the embodiments thereof, and while the embodiments have been described in considerable detail, it is not the intention of the applicant to restrict or in any way limit the scope of the appended claims to such detail. Additional advantages and modifications will readily appear to those skilled in the art.
Therefore, the invention in its broader aspects is not limited to the specific details representative apparatus and method, and illustrative examples shown and described. Accordingly, departures may be made from such details without departure from the spirit or scope of applicant's general inventive concept.

Claims (27)

  1. Claims 1. A computer-implemented method for managing user access to a database system, including: i) receiving a request from a terminal of a user for a specific type of access to a database system; ii) processing the request in accordance with a set of rules in conjunction with information relating to the user to determine whether access can be granted to the user; iii) transmitting a request for access approval to a terminal of an approver; iv) receiving an approval message; and v) modifying the database system to enable access for the user.
  2. 2. A method as claimed in claim 1 wherein the set of rules include rules relating to compliance.
  3. 3. A method as claimed in claim 2 wherein the compliance rules relate to compliance with separation of duties.
  4. 4. A method as claimed in any preceding claim wherein the set of rules is stored within a database.
  5. 5. A method as claimed in any preceding claim wherein the information relating to the user includes current access rights to the database system.
  6. 6. A method as claimed in any preceding claim wherein the information relating to the user is extracted from a database.
  7. 7. A method as claimed in any one of claims I to 5 wherein the information relating to the user is extracted from the database system.
  8. 8. A method as claimed in claim 7 wherein the information relating to the user is dynamically extracted.
  9. 9. A method as claimed in any preceding claim wherein the database system is an enterprise resource planning database system.
  10. 1O.A method as claimed in any preceding claim wherein the request for access approval includes information relating to whether access can be granted.
  11. 11.A method as claimed in any preceding claim including the step of transmitting the request for access approval to a terminal of a second approver if a response is not received from the first approver within a predefined period.
  12. 12.A method as claimed in any preceding claim including the step of transmitting the request for access approval to a terminal of a second approver after receiving the approval message from the first approver, and modifying the database system only once a second approval message is received from the second approver.
  13. 13.A system for managing user access to a database system, including: a communications transceiver configured to receive a request from a terminal of a user for a specific type of access to a database system; a memory configured to store a set of rules relating to user access; a processor configured to utilise the set of rules and information relating to the user to determine whether access can be granted to the user; a communications transmitter configured to transmit a request for access approval to a terminal of an approver; a communications receiver configured to receive an approval message; and a database interface system configured to modify the database system to enable access for the user.
  14. 14.A system as claimed in claim 13 wherein the processor is further configured to extract the set of rules from the memory.
  15. 15.A system as claimed in any one of claims 13 to 14 wherein the memory is further configured to store information relating to the user.
  16. 16.A system as claimed in any one of claims 13 to 15 wherein the processor is further configured to extract the information relating to the user from the memory.
  17. 17.A system as claimed in any one of claims 13 to 16 wherein the set of rules include rules relating to compliance.
  18. 18.A system as claimed in claim 17 wherein the compliance rules relate to compliance with separation of duties.
  19. 19.A system as claimed in any one of claims 13 to 18 wherein the information relating to the user includes current access rights to the database system.
  20. 20.A system as claimed in any one of claims 13 to 19 except when dependent on claim 16 wherein the processor is further configured to extract the information relating to the user from the database system.
  21. 21.A system as claimed in claim 20 wherein the information relating to the user is dynamically extracted.
  22. 22.A system as claimed in any one of claims 13 to 21 wherein the database system is an enterprise resource planning database system.
  23. 23.A system as claimed in any one of claims 13 to 22 wherein the request for access approval includes information relating to whether access can be granted.
  24. 24.A system as claimed in any one of claims 13 to 23 wherein the communication transmitter is further configured to transmit the request for access approval to a terminal of a second approver if a response is not received from the first approver within a predefined period.
  25. 25.A system as claimed in any one of claims 13 to 24 wherein the communication transmitter is further configured to transmit the request for access approval to a terminal of a second approver after the approval message is received from the first approver, and the database interface system is configured to modify the database system only once a second approval message is received from the second approver.
  26. 26.Computer program configured for performing the method of any one of claims ito 12.
  27. 27.Computer-readable medium configured for storing the computer program of claim 26.
GB1102713.3A 2011-02-16 2011-02-16 Managing user access to a database by requesting approval from approver. Withdrawn GB2488520A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
GB1102713.3A GB2488520A (en) 2011-02-16 2011-02-16 Managing user access to a database by requesting approval from approver.

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
GB1102713.3A GB2488520A (en) 2011-02-16 2011-02-16 Managing user access to a database by requesting approval from approver.

Publications (2)

Publication Number Publication Date
GB201102713D0 GB201102713D0 (en) 2011-03-30
GB2488520A true GB2488520A (en) 2012-09-05

Family

ID=43859513

Family Applications (1)

Application Number Title Priority Date Filing Date
GB1102713.3A Withdrawn GB2488520A (en) 2011-02-16 2011-02-16 Managing user access to a database by requesting approval from approver.

Country Status (1)

Country Link
GB (1) GB2488520A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11017376B1 (en) 2015-12-28 2021-05-25 Wells Fargo Bank, N.A. Mobile device-based dual custody verification using micro-location

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200126008A1 (en) * 2018-10-17 2020-04-23 Caterpillar Paving Products Inc. System and method for selectively providing access to jobsite-related data

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003107224A1 (en) * 2002-06-18 2003-12-24 Arizona Board Of Regents, Acting For Arizona State University Assignment and management of authentication & authorization
US6941475B1 (en) * 2001-03-30 2005-09-06 Hewlett-Packard Development Company, L.P. System and method for efficient processing of service requests
WO2006127135A2 (en) * 2005-05-23 2006-11-30 Sap Governance Risk And Compliance, Inc. Access enforcer
US20060290967A1 (en) * 2005-06-24 2006-12-28 Takaaki Sumitomo Image processing system and apparatus and approval server
KR20100039059A (en) * 2008-10-07 2010-04-15 비씨카드(주) Method and syetem for security service of data processing
US20100223570A1 (en) * 2009-02-28 2010-09-02 Peter Gerstl Method and apparatus to model content state and access control in backend-systems and business processes

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6941475B1 (en) * 2001-03-30 2005-09-06 Hewlett-Packard Development Company, L.P. System and method for efficient processing of service requests
WO2003107224A1 (en) * 2002-06-18 2003-12-24 Arizona Board Of Regents, Acting For Arizona State University Assignment and management of authentication & authorization
WO2006127135A2 (en) * 2005-05-23 2006-11-30 Sap Governance Risk And Compliance, Inc. Access enforcer
US20060290967A1 (en) * 2005-06-24 2006-12-28 Takaaki Sumitomo Image processing system and apparatus and approval server
KR20100039059A (en) * 2008-10-07 2010-04-15 비씨카드(주) Method and syetem for security service of data processing
US20100223570A1 (en) * 2009-02-28 2010-09-02 Peter Gerstl Method and apparatus to model content state and access control in backend-systems and business processes

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11017376B1 (en) 2015-12-28 2021-05-25 Wells Fargo Bank, N.A. Mobile device-based dual custody verification using micro-location
US11580517B1 (en) 2015-12-28 2023-02-14 Wells Fargo Bank, N.A. Mobile device-based dual custody verification using micro-location

Also Published As

Publication number Publication date
GB201102713D0 (en) 2011-03-30

Similar Documents

Publication Publication Date Title
US10565360B2 (en) Verifying a user's identity based on adaptive identity assurance levels
US9407655B2 (en) Monitoring security risks to enterprise corresponding to access rights and access risk calculation
US9730044B2 (en) Telecommunications data usage management
US20140164249A1 (en) Method and system for secure authentication and information sharing and analysis
US8768801B1 (en) User managed spending plan
US20160321610A1 (en) Systems and methods for aggregating consumer data
EP1805710A2 (en) Financial institution portal system and method
US9384330B2 (en) Providing user attributes to complete an online transaction
CN105308614A (en) Policy enforcement delays
CN104704521A (en) Multi-factor profile and security fingerprint analysis
US20240241984A1 (en) System and method for controlling access to account transaction information
US20150134818A1 (en) Data sharing method and data sharing gateway configuration
US20160239675A1 (en) System and method for permission based digital content syndication, monetization, and licensing with access control by the copyright holder
CN112580091B (en) Fine-grained data access control method and device
US11373130B1 (en) Policy exception risk determination engine with visual awareness guide
CN108874836B (en) Method and device for transferring electronic ticket
KR102182681B1 (en) Method for Selling Data Stored on the IoT/M2M Platform
US20160132946A1 (en) System and method for identifying qualified parties to a transaction
GB2488520A (en) Managing user access to a database by requesting approval from approver.
US20170221067A1 (en) Secure electronic transaction
US20180255333A1 (en) System and method for repurchasing and relicensing electronic media
KR102119383B1 (en) System and method for service for facilitating agreement, and user device and computer program for the same
US20180075471A1 (en) Point exchange system and point exchange method
Tziakouris et al. Asset-centric security-aware service selection
US20220414622A1 (en) System for off-chain management, distribution and auditing of decentralized cryptocurrency

Legal Events

Date Code Title Description
WAP Application withdrawn, taken to be withdrawn or refused ** after publication under section 16(1)