Authority management method and device, electronic equipment and storage medium
By rationally detecting and matching the verification attribute information of the target object and dynamically adjusting permissions, the problems of insufficient granularity and traffic invasion in the existing technology are solved, and refined permission management and safe and convenient operations of the target object are achieved. .
Patent Information
- Application Number
- CN202310498360.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-05
- Publication Date
- 2024-11-05
AI Technical Summary
The existing permission management methods are not granular enough when sending data to the target object's operation interface, resulting in the risk of traffic invasion, unable to effectively distinguish the particularity of different interfaces, resources and operations, and are inconvenient to control user permissions with high proficiency.
By obtaining the verification attribute information of the target object, conducting rationality detection and matching, dynamically adjusting permissions based on the matching results, realizing the current limiting processing of different attribute information dimensions, ensuring the security and convenience of user operations.
It realizes refined management of target object permissions, prevents traffic infringement, improves the security and convenience of user operations, and adapts to flexible and changing user permission needs.
Smart Images

Figure CN118898075A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a rights management technology, and in particular to a rights management method, device, system, equipment and storage medium. Background Art
[0002] In the related technology, in order to ensure the security of remote login of the target object and the security of executing instruction information, it is necessary to control the permission of the target object's operation interface to send data. However, the existing permission management method has insufficient granularity when managing permissions, and there is a risk of traffic encroachment when limiting the flow of large-traffic target objects. Therefore, it is necessary to provide a more refined permission management method. Summary of the invention
[0003] In view of this, the embodiments of the present invention provide a permission management method, device, electronic device, computer product and storage medium, which can realize more refined management of the permissions of the target object. By limiting the flow of different attribute information dimensions, the flow of the target object can be prevented from being occupied, making it easier and safer for users to operate the target interface. At the same time, the attribute information of the interface called by the user can be matched, and the user's permissions can be adjusted in time according to the matching results to adapt to the flexible changes in user permissions.
[0004] The technical solution of the embodiment of the present invention is achieved as follows:
[0005] An embodiment of the present invention provides a rights management method including:
[0006] Obtaining first attribute information of the target object for each verification attribute in the verification attribute set;
[0007] Detecting the rationality of each of the first attribute information of the target object to obtain a detection result, wherein the rationality of the first attribute information is used to indicate that the target object is provided with permission to operate the corresponding port according to the rationality standard;
[0008] When the detection result indicates that the rationality detection of each of the first attribute information has passed, obtaining an operation interface adopted by the target object to perform a target operation;
[0009] Acquire second attribute information of each verification attribute in the verification attribute set corresponding to the operation interface;
[0010] The first attribute information of each of the verification attributes is matched with the corresponding second attribute information respectively, and the operation authority of the target object for the operation interface is determined based on the matching result.
[0011] The embodiment of the present invention further provides a rights management device, including:
[0012] An information transmission module, used to obtain first attribute information of the target object for each verification attribute in the verification attribute set;
[0013] An information processing module, configured to detect the rationality of each of the first attribute information of the target object to obtain a detection result, wherein the rationality of the first attribute information is used to indicate that the target object is provided with permission to operate the corresponding port according to the rationality standard;
[0014] The information processing module is used to obtain an operation interface used by the target object to perform a target operation when the detection result indicates that the rationality detection of each of the first attribute information has passed;
[0015] The information transmission module is used to obtain second attribute information of each verification attribute in the verification attribute set corresponding to the operation interface;
[0016] The information processing module is used to match the first attribute information of each verification attribute with the corresponding second attribute information, and determine the operation authority of the target object for the operation interface based on the matching result.
[0017] In the above scheme,
[0018] The information processing module is used to record in real time the operation history of the operation interface used by the target object to perform the target operation;
[0019] The information processing module is used to determine the level of each dangerous operation according to the operation history;
[0020] The information processing module is used to adjust the safety score of the target object according to the level of each dangerous operation;
[0021] The information processing module is used to adjust the authority of the target object according to the security score of the target object.
[0022] In the above scheme,
[0023] The information transmission module is used to obtain the token of the target object in response to the permission authentication request;
[0024] The information processing module is used to verify the identity information of the target object through the token of the target object;
[0025] The information processing module is used to obtain the key of the target object when the identity information of the target object passes the verification, wherein the key is used to find the first attribute information of the target object for each verification attribute in the verification attribute set.
[0026] In the above scheme,
[0027] The information processing module is used to obtain a rationality standard that matches the verification attribute set, wherein the rationality standard includes at least one of the following:
[0028] The blank status of project information, product support status, regional information support status, the accuracy of the account ID and APPID of the main account in the account information, and the support status of resource information;
[0029] The information processing module is configured to perform a rationality check on the first attribute information according to the rationality standard, wherein the first attribute information includes at least one of the following:
[0030] The cloud server's resource prefix, project information, product name, region information, account information, and resource information.
[0031] In the above scheme,
[0032] The information processing module is used to detect the current limiting property of the operation interface;
[0033] When the operation interface is not limited, or
[0034] When the operation interface does not reach the current limit times, second attribute information of each verification attribute in the verification attribute set corresponding to the operation interface is generated.
[0035] In the above scheme,
[0036] The information processing module is used to perform single element matching on the first attribute information and the second attribute information to obtain a first matching result when the operation interface type is a common interface, or
[0037] The information processing module is used to perform all element matching on the first attribute information and the second attribute information to obtain a second matching result when the operation interface type is a dangerous interface.
[0038] In the above scheme,
[0039] The information processing module is used for, when the matching result is the first matching result,
[0040] When any set of corresponding attribute information in the first attribute information and the second attribute information matches, determining that the operation authority of the target object for the operation interface is authenticated; or
[0041] The information processing module is used for, when the matching result is the second matching result,
[0042] When each set of corresponding attribute information in the first attribute information and the second attribute information matches, it is determined that the operation authority of the target object for the operation interface is authenticated.
[0043] In the above scheme,
[0044] The information processing module is used to obtain the dangerous attribute information matching the operation interface;
[0045] The information processing module is used to determine the interface type of the operation interface according to the risk attribute information; or
[0046] The information processing module is used to detect data transmitted through the operation interface;
[0047] The information processing module is used to dynamically adjust the interface type of the operation interface according to the data transmitted by the operation interface to determine the interface type of the operation interface.
[0048] In the above scheme,
[0049] The information processing module is used to obtain the resource operability threshold when the target object performs the target operation;
[0050] The information processing module is used to determine the interface corresponding to the switch-type dangerous operation, wherein the switch-type dangerous operation is used to set the DNS switch state;
[0051] The information processing module is used to determine the interface corresponding to the resource-related dangerous operation, wherein the resource-related dangerous operation is used to authorize a specific resource;
[0052] The information processing module is used to determine the interface corresponding to the quota-type dangerous operation according to the resource operable threshold, wherein the quota-type dangerous operation is used to adjust the interface quantity quota matching the resource of the target object.
[0053] In the above scheme,
[0054] The information processing module is used to obtain an organizational structure that matches the target object;
[0055] The information processing module is used to determine a dynamic approval path according to the organizational structure; or
[0056] The information processing module is used to obtain a static approval path that matches the target object, wherein the dynamic approval path and the static approval path are used to approve the authority of the target object.
[0057] In the above scheme,
[0058] The information processing module is used to adjust the permission time limit of the target object in response to the received time limit adjustment instruction, wherein the permission time limit includes:
[0059] Single permission validity period and multiple permission validity period.
[0060] In the above scheme,
[0061] The information processing module is used to obtain data change information corresponding to each dangerous operation;
[0062] The information processing module is used to obtain the data storage table before rollback according to the data change information;
[0063] The information processing module is used to intercept any dangerous operation in each of the dangerous operations, and
[0064] Data is rolled back according to the data storage table before rollback, so as to achieve
[0065] Roll back to the data processing state before any of the dangerous operations.
[0066] An embodiment of the present invention further provides an electronic device, the electronic device comprising:
[0067] A memory for storing executable instructions;
[0068] The processor is used to implement the aforementioned permission management method when running the executable instructions stored in the memory.
[0069] An embodiment of the present invention further provides a computer program product, including a computer program or instructions, characterized in that the computer program or instructions implement the aforementioned permission management method when executed by a processor.
[0070] An embodiment of the present invention further provides a computer-readable storage medium storing executable instructions, which implement the aforementioned permission management method when executed by a processor.
[0071] The embodiments of the present invention have the following beneficial effects:
[0072] 1) The present invention obtains the first attribute information of the target object for each verification attribute in the verification attribute set; detects the rationality of each of the first attribute information of the target object to obtain a detection result; thereby, the rationality of the first attribute information can be detected in a timely manner, thereby reducing errors in the adjustment of the target object's operation authority for the operation interface due to unreasonable first attribute information.
[0073] 2) When the detection result indicates that the rationality detection of each of the first attribute information has passed, the operation interface used by the target object to perform the target operation is obtained; the second attribute information of each verification attribute in the verification attribute set corresponding to the operation interface is obtained; the first attribute information of each verification attribute is matched with the corresponding second attribute information respectively, and the operation authority of the target object for the operation interface is determined based on the matching result. In this way, the authority of the target object can be managed in a refined manner. By limiting the flow of different attribute information dimensions, the traffic of the target object can be prevented from being occupied, making it easier and safer for users to operate the target interface. At the same time, the attribute information of the interface called by the user can be matched, and the user's authority can be adjusted in time according to the matching result to adapt to the flexible and changing user authority usage requirements. BRIEF DESCRIPTION OF THE DRAWINGS
[0074] Figure 1 It is a schematic diagram of the use environment of the rights management method provided by the embodiment of the present invention;
[0075] Figure 2 An optional flowchart of the rights management method provided in the embodiment of the present application;
[0076] Figure 3 An optional flowchart of the rights management method provided in the embodiment of the present application
[0077] Figure 4 A schematic diagram of the processing logic of rights management in an embodiment of the present invention;
[0078] Figure 5 The following is a schematic diagram of an optional processing flow of the rights management method in an embodiment of the present invention;
[0079] Figure 6 A schematic diagram of a six-segment resource in an embodiment of the present invention;
[0080] Figure 7 Schematic diagram of the matching process of the first resource six-segment type and the second resource six-segment type in an embodiment of the present invention;
[0081] Figure 8 Associating representation intents for users and user groups;
[0082] Fig. 9 Intent for the strategies in this application;
[0083] Fig.10 A schematic diagram of the processing logic of dangerous operations in an embodiment of the present invention;
[0084] Fig.11 It is intended to record dangerous operations in the embodiment of the present invention;
[0085] Fig.12 This is a schematic diagram of storing data before rollback in an embodiment of the present invention;
[0086] Fig.13 A logical diagram of the balance between safety and efficiency in an embodiment of the present invention;
[0087] Fig.14 Intent for the security scoring database;
[0088] Fig.15 Recording intent for user rights adjustments;
[0089] Fig.16 A schematic diagram of the structure of an electronic device of an operation authority management device provided in an embodiment of the present invention. DETAILED DESCRIPTION
[0090] In order to make the purpose, technical solutions and advantages of the present invention clearer, the present invention will be further described in detail below in conjunction with the accompanying drawings. The described embodiments should not be regarded as limiting the present invention. All other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present invention.
[0091] In the following description, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.
[0092] Before further describing the embodiments of the present invention in detail, the nouns and terms involved in the embodiments of the present invention are described. The nouns and terms involved in the embodiments of the present invention are subject to the following interpretations.
[0093] 1) In response, it is used to indicate the conditions or states on which the executed operations depend. When the dependent conditions or states are met, one or more operations executed may be in real time or have a set delay. Unless otherwise specified, there is no restriction on the order in which the multiple operations executed are executed.
[0094] 2) Terminals, including but not limited to: ordinary terminals and dedicated cloud servers, wherein the ordinary terminals maintain a long connection and / or a short connection with the sending channel, and the dedicated cloud server maintains a long connection with the sending channel.
[0095] 3) Client, the carrier of specific functions in the terminal, for example, the mobile client (APP) is the carrier of specific functions in the mobile terminal, such as executing payment consumption functions or purchasing financial products.
[0096] 4) Policy: In access management, a policy is a syntax specification that defines and describes one or more permissions. The master account completes authorization by associating a policy with a user or user group. Administrators or sub-accounts authorized with policy management permissions can also create, update, delete policies, and authorize policies.
[0097] 5) A user group is a collection of multiple users (sub-accounts) with the same function. You can create different user groups based on business needs, associate appropriate policies with user groups, and assign different permissions.
[0098] 6) Master account: In access management and cloud access security agent, the master account refers to the master account identity created by the system for logging into the cloud service product when the user applies for a cloud service product account. The master account is the basic subject for metering and billing of cloud service product resources. The master account has full access to the resources owned by it by default, and can create sub-accounts and set permissions for the sub-accounts.
[0099] 7) Sub-accounts. In access management, sub-accounts are entities you create in cloud service products, with a certain identity ID and identity credentials. They are divided into sub-users, enterprise WeChat sub-users, collaborators, and message recipients. The difference between sub-users and collaborators is that sub-users completely belong to the main account, while collaborators are previously registered cloud service product main accounts. That is, collaborators can have two identities, one is the main account of their own account, and they can also switch to the collaborator of the corresponding main account.
[0100] 8) API, the full name of which is Application Programming Interface, can be translated into application program interface, which is a set of predefined functions or the agreement for connecting different components of a software system. The purpose is to provide application and developers with the ability to access a set of routines based on a certain software or hardware without accessing the original code or understanding the details of the internal working mechanism. DFS-SAPI: Defensor internal application programming interface.
[0101] 9) Defensor, a new generation of operation and commercialization platform of the network product center of cloud service products, DFS-5A, a self-developed permission management system of the Defensor platform, integrates Authentication, Authorization, Audit, Accounting and Analysis.
[0102] Before describing the rights management method provided by this application, the defects of the related technology are first described:
[0103] In order to manage the permissions of different users, the relevant technologies generally use the permission system to perform corresponding permission control, support the authorization and control of different roles, permissions and operations for different personnel, and limit the functional scope that personnel with different roles can operate. The industry has carried out corresponding permission control based on the common permission control model RBAC (Role Based Access Control), but there are the following defects:
[0104] 1) Currently, most permission management methods implement permission management at the interface level and page level separately. The permission control granularity is large and the degree of refinement is insufficient.
[0105] 2) Limiting the flow of operations for a single account is a common function of permission management, which limits the number of accesses or traffic within a certain time period for a certain account. If an account involves many resources, and the resources managed by the account exist in different regions, if only the flow of the account is controlled, it is possible that some regions may be occupied due to processing too many transactions, and the flow usage reaches the upper limit, resulting in access restrictions in other regions.
[0106] 3) Currently, most permission management methods verify whether the user has the permission for the interface, which is not enough to distinguish the particularities of different interfaces, different resources, and different operations. However, in many scenarios, interfaces, resources, operations, and operation scopes are different and need to be treated differently. Defining a fixed risk level for an interface or resource cannot meet the above scenarios.
[0107] 4) In the permission management method, the way to obtain permissions is generally to apply and approve, but for some more complex and sensitive operations, strict permission control is implemented, and each operation requires an application. It does not take into account the different risks of different operators. For those with higher proficiency and lower risk, they should have higher permissions. It is impossible to identify user proficiency on the fly, which makes it inconvenient for users to use.
[0108] In order to solve the above-mentioned defects, the embodiments of the present invention provide a permission management method, device, electronic device, computer-readable storage medium and computer program product, which can realize more refined management of the permissions of the target object. By limiting the flow of different attribute information dimensions, the flow of the target object can be prevented from being occupied, making it easier and safer for users to operate the target interface. At the same time, the attribute information of the interface called by the user can be matched, and the user's permissions can be adjusted in time according to the matching results to adapt to the flexible changes in user permissions. The following describes an exemplary application of the electronic device provided by the embodiment of the present application. The electronic device provided by the embodiment of the present application can be implemented in collaboration with a server with a permission management function and a terminal device with a target interface trigger function.
[0109] Figure 1A schematic diagram of a usage scenario of the rights management method provided in an embodiment of the present invention, see Figure 1 , with the continuous development of computer technology, cloud servers (CVM Cloud Virtual Machine) can provide secure and reliable elastic computing services, and can also provide different interfaces for transmission to meet user-specific usage scenarios. The terminal (including terminal 10-1 and terminal 10-2) is provided with corresponding clients that can perform different functions, wherein terminal 10-1 and terminal 10-2 obtain different information from the corresponding cloud server 200 through network 300, and can deploy different services in the cloud server by calling different operation interfaces, such as through the interface "Run Instances" of cloud server 200, to create cloud host V3, or through the operation interface "Modify Instances Project", to modify the instance project. The terminal is connected to server 200 through network 300, and network 300 can be a wide area network or a local area network, or a combination of the two, and a wireless link is used to realize data transmission.
[0110] In some embodiments, the cloud server 200 can be an independent physical server in the cloud network, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content distribution networks (CDNs), and big data and artificial intelligence platforms, where cloud services can be data write operations, read operations, and list operations, and terminals 10-1 and 10-2 can be smart phones, tablet computers, laptops, desktop computers, smart TVs, smart watches, car terminals, etc., but are not limited to these. Terminals 10-1 and 10-2 and cloud server 200 can be directly or indirectly connected via wired or wireless communications, which is not limited in the embodiments of the present application.
[0111] In order to more clearly illustrate the working process of the permission management method provided by the present application, the permission management method provided by the embodiment of the present application is specifically described below from the perspective of the cloud server performing permission management on the target object participating in the access management (Cloud Access Management, CAM) transaction in combination with different execution entities.
[0112] See also Figure 2 , Figure 2 An optional flowchart of the rights management method provided in the embodiment of the present application is provided. It can be understood that: Figure 2The execution subject of the steps shown is a cloud server with a permission management device. Among them, the embodiments of the present invention can be implemented in combination with cloud technology. Cloud technology refers to a hosting technology that unifies a series of resources such as hardware, software and network in a wide area network or a local area network to realize data calculation, storage, processing and sharing. It can also be understood as a general term for network technology, information technology, integration technology, management platform technology and application technology based on cloud computing business model applications. The background services of the technical network system require a large amount of computing and storage resources, such as video websites, picture websites and more portal websites, so cloud technology needs to be supported by cloud computing.
[0113] It should be noted that cloud computing is a computing model that distributes computing tasks on a resource pool composed of a large number of computers, so that various application systems can obtain computing power, storage space and information services as needed. The network that provides resources is called the "cloud". From the user's point of view, the resources in the "cloud" can be infinitely expanded, and can be obtained at any time, used on demand, expanded at any time, and paid for by use. As a basic capability provider for cloud computing, a cloud computing resource pool platform will be established, referred to as a cloud platform, generally referred to as Infrastructure as a Service (IaaS), and various types of virtual resources will be deployed in the resource pool for external customers to choose to use. The cloud computing resource pool mainly includes: computing devices (which can be virtualized machines, including operating systems), storage devices and network devices. Different operating permissions are granted to users who process data through cloud servers.
[0114] Cloud storage is a new concept that extends and develops from the concept of cloud computing. A distributed cloud storage system (hereinafter referred to as storage system) refers to a storage system that uses cluster applications, grid technology, and distributed storage file systems to bring together a large number of storage devices of various types (storage devices are also called storage nodes) in the network to work together through application software or application interfaces to provide data storage and business access functions. At present, the storage method of the storage system is to create a logical volume. When creating a logical volume, a physical storage space is allocated for each logical volume. The physical storage space may be composed of disks of a storage device or several storage devices. The client stores data on a logical volume, that is, the data is stored on the file system. The file system divides the data into many parts, each of which is an object. The object contains not only data but also additional information such as data identification (ID, ID entity). The file system writes each object into the physical storage space of the logical volume, and the file system records the storage location information of each object. Therefore, when the client requests to access the data, the file system can allow the client to access the data according to the storage location information of each object. The process of the storage system allocating physical storage space to a logical volume is as follows: based on the estimated capacity of the objects stored in the logical volume (this estimate often has a large margin relative to the actual capacity of the objects to be stored) and the grouping of independent redundant disk arrays (RAID, Redundant Array of Independent Disks), the physical storage space is pre-divided into stripes. A logical volume can be understood as a stripe, thereby allocating physical storage space to the logical volume.
[0115] When applied to cloud products, the front end of the cloud product can be a Web UI component, which is used to receive the target object's operation on the target interface to achieve the target function. Figure 2 The steps shown are explained.
[0116] Step 201: Obtain first attribute information of a target object for each verification attribute in a verification attribute set.
[0117] Among them, the verification attribute set can be expressed as a resource multi-segment type, for example, it can be: a resource six-segment type, a resource five-segment type..., this application does not make specific restrictions on this, taking the verification attribute set as a resource six-segment type as an example, for the target object for permission management and the target interface used when performing the target operation, there are corresponding resource six-segment types. The following six-segment description method can be used when granting single or multiple resource permissions. Each product has its own resources and corresponding resource definition details.
[0118] The six-part resource definition is as follows:
[0119] qcs:project_id:service_type:region:account:resource
[0120] The six-segment resource format contains the following six fields, with detailed meanings and examples as follows:
[0121] 1)qcs: short for qcloud service, which refers to the cloud resources of the target cloud server.
[0122] 2) project_id: describes the project information. It is only compatible with the early CAM logic. The current policy syntax prohibits filling in this information, so just leave it blank.
[0123] 3)service_type: describes the product abbreviation. When the service_type value is empty, it means all products. When it is not empty, it can be: cvm for cloud server and cdn for content distribution network.
[0124] 4)region: describes the region information. For region naming methods, please refer to the region list. When the value is empty, it means all regions.
[0125] 5) account: describes the primary account information of the resource owner. Currently, two methods are supported to describe the resource owner: uin and uid. Among them: uin method, that is, the account ID of the primary account, expressed as uin / ${uin}. Uid method, that is, the APPID of the primary account, expressed as uid / ${appid}. Only resource owners of COS and CAS services use this description method. When the value is empty, it indicates the primary account of the CAM user who created the policy.
[0126] 6) resource: describes the specific resource details of each product. Currently, two methods are supported to describe resource information: resource_type / ${resourceid} and<resource_type> / <resource_path> .
[0127] Among them, resource_type / ${resourceid}: resourcetype is the resource prefix, describing the resource type. For details, you can view the six-segment resource format of the product in the business interface that supports CAM; ${resourceid} is the specific resource ID, which can be viewed in each product console. When the value is *, it represents all resources of this type of resource. In addition,<resource_type> / <resource_path> : resourcetype is the resource prefix, describing the resource type; in this mode in the resource path, directory-level prefix matching is supported.
[0128] In some embodiments of the present application, when the target object operates the operation interface, unsafe situations such as remote login and no login for 30 days may occur. In order to ensure the security of permission management, before executing step 201, the identity information of the target object needs to be verified. The method of verifying the identity information of the target object includes but is not limited to: IP whitelist verification, token verification and signature verification. The above three verifications can be configured and supported in the permission management method provided in this application as optional items, and each configured service can have an independent verification method without affecting each other. Taking token verification as an example, it specifically includes: receiving a permission authentication request, responding to the permission authentication request, and obtaining the token of the target object; wherein the cloud server can receive the permission authentication request through the interface request domain name (cam.tencentcloudapi.com). After that, the identity information of the target object is verified through the token of the target object. If the token of the target object is consistent with the token stored in the database, it means that the identity information of the target object has passed the verification. When the identity information of the target object passes the verification, the key of the target object is obtained. The key can be used to find the first attribute information of the target object for each verification attribute in the verification attribute set, thereby ensuring the information security of the first attribute information corresponding to the target object and avoiding the leakage of the first attribute information.
[0129] Step 202: Detect the rationality of each first attribute information of the target object to obtain a detection result.
[0130] The rationality of the first attribute information is used to characterize that the target object is provided with permission to operate the corresponding port through the rationality standard. In some embodiments of the present application, taking the six-segment resource as an example as the first attribute information, the first attribute information includes at least one of the following:
[0131] The cloud server's resource prefix, project information, product name, region information, account information, and resource information.
[0132] At this time, it is necessary to first obtain a rationality standard that matches the verification attribute set, where the rationality standard includes at least one of the following:
[0133] The empty status of project information, product support status, regional information support status, the accurate status of the account ID and APPID of the main account in the account information, and the support status of resource information.
[0134] Afterwards, according to the rationality standard, the rationality check is performed on the first attribute information. During the rationality check, the resource prefix of the cloud server is checked through the empty state of the project information to determine whether the resource prefix of the cloud server meets the requirements of the empty state of the project information; the project information is checked through the product support status to determine whether the project that needs to be managed by authority meets the requirements of the product support status; the regional information is checked through the regional information support status, for example, the regional information support status is: ap-beijing for North China (Beijing) and ap-guangzhou for South China (Guangzhou), indicating that only target operations from North China (Beijing) and South China (Guangzhou) are responded to; the account number of the main account in the account information is The accurate status of the ID and the APPID of the main account is used to detect the account information (such as uin / 12345678 and uid / 10001234) to avoid misjudgment when the operation permissions of the target object are adjusted; the rationality of the resource information is detected through the supportable status of the resource information. For example, it can be determined that the resources available to the target object include: cloud server: all files under instance / ins-1, cloud database MySQL: all files under instanceId / cdb-1, object storage COS: all files under prefix / / 10001234 / bucket1 / *, to avoid misjudgment when the operation permissions of the target object are adjusted, resulting in data leakage.
[0135] Before executing step 203, in order to ensure the accuracy of authority management, the flow limiting granularity of the first attribute information of each verification attribute in the verification attribute set is realized to reach the resource level (that is, flow limiting can be performed according to each attribute information in the first attribute information), and at the same time, the resource-level flow limiting can be independent of each other to avoid mutual influence and prevent traffic encroachment. It is necessary to detect the flow limiting property of the operation interface; when the operation interface is not limited, or the operation interface does not reach the flow limiting number, the second attribute information of each verification attribute in the verification attribute set corresponding to the operation interface is generated. Therefore, when there is an account involving many resources, and the resources managed by the account exist in different regions, the resource prefix of the cloud server included in the first attribute information, project information, product name, regional information, account information, and resource information can be used to achieve independent flow limiting between different attributes, making the authority management of the target object more refined.
[0136] Step 203: When the detection result indicates that the rationality detection of each first attribute information is passed, an operation interface adopted by the target object to perform the target operation is obtained.
[0137] Step 204: Obtain second attribute information of each verification attribute in the verification attribute set corresponding to the operation interface.
[0138] In the processing of step 203 and step 204, each operation interface used by the target object to perform the target operation corresponds to a second attribute information.
[0139] In some embodiments of the present application, taking the data processing of elastic microservices as an example, the target operations included include: write operation, read operation and list operation. At this time, the interface authorization granularity is divided into two levels: resource level and operation level:
[0140] 1) Resource-level interface: This type of interface supports authorization for a specific resource.
[0141] 2) Operational level interface: This type of interface does not support authorization for a specific resource. If the policy syntax during authorization limits specific resources, CAM will determine that this interface is not within the authorization scope and is considered unauthorized.
[0142] The second attribute information of each verification attribute in the verification attribute set corresponding to the generated operation interface can refer to Table 1:
[0143] Table 1
[0144]
[0145] The target object can query and change the elastic microservice through the operation interface shown in Table 1.
[0146] Step 205: Match the first attribute information of each verification attribute with the corresponding second attribute information respectively, and determine the operation authority of the target object for the operation interface based on the matching result.
[0147] To better illustrate the process of matching the first attribute information with the second attribute information, see Figure 3 , Figure 3 An optional flowchart of the rights management method provided in the embodiment of the present application is provided. It can be understood that: Figure 3 The execution subject of the steps shown is a cloud server that uses a permission management device. Figure 2 The steps shown are explained.
[0148] Step 301: When the operation interface type is a common interface, the authority management device performs single element matching on the first attribute information and the second attribute information to obtain a first matching result.
[0149] In some embodiments of the present application, before executing step 301, the type of the operation interface may be determined first, which may be implemented in the following manner: 1) obtaining dangerous attribute information matching the operation interface; and determining the interface type of the operation interface according to the dangerous attribute information. Taking the parameter modification of the cloud server as an example, the correspondence between dangerous attribute information and interface type is shown in Table 2:
[0150] Table 2
[0151]
[0152] 2) Detect the data transmitted through the operation interface; dynamically adjust the interface type of the operation interface according to the data transmitted by the operation interface to determine the interface type of the operation interface. For example: perform real-time detection on the data transmitted in the target interface "DeleteDiskSecurityConfigurations", and when a deletion instruction is obtained, determine that the target interface "DeleteDiskSecurityConfigurations" is a dangerous interface.
[0153] Step 302: When the first matching result is that any set of corresponding attribute information in the first attribute information and the second attribute information matches, the authority management device determines that the operation authority of the target object for the operation interface is authenticated.
[0154] Step 303: When the first matching result is that no corresponding attribute information matches between the first attribute information and the second attribute information, the authority management device determines that the operation authority of the target object for the operation interface is not authenticated.
[0155] In some embodiments of the present invention, before executing step 304, a specific type of dangerous interface may be screened by identifying dangerous operations, specifically including the following methods:
[0156] 1) Determine the interface corresponding to the dangerous switch operation, where the dangerous switch operation is used to set the DNS switch status (wherein the ModifySwitchStatus interface controls the DNS switch status).
[0157] 2) Determine the interface corresponding to the resource-type dangerous operation, wherein the resource-type dangerous operation is used to authorize a specific resource (wherein the interface corresponding to the resource-type dangerous operation includes: the "AttachDisks" interface shown in Table 2 in the previous embodiment).
[0158] 3) Obtain the resource operable threshold when the target object performs the target operation; determine the interface corresponding to the quota-type dangerous operation based on the resource operable threshold, wherein the quota-type dangerous operation is used to adjust the interface quantity quota that matches the resources of the target object (wherein, the interfaces corresponding to the quota-type dangerous operations include: 1) "DescribeAlarmSMSQuota" is used to obtain the alarm SMS quota; 2) "DescribeAlarmPolicyQuota" is used to query the alarm policy quota; 3) "DescribeAlarmObjectQuota" is used to query the alarm object quota).
[0159] Step 304: When the operation interface type is a dangerous interface, the authority management device matches all elements of the first attribute information and the second attribute information to obtain a second matching result.
[0160] Step 305: When the second matching result is that each set of corresponding attribute information in the first attribute information and the second attribute information matches, the authority management device determines that the operation authority of the target object for the operation interface is authenticated.
[0161] Step 306: When the second matching result is that a set of corresponding attribute information in the first attribute information and the second attribute information does not match, the authority management device determines that the operation authority of the target object for the operation interface is not authenticated.
[0162] By executing Figure 3 In steps 301 to 306 shown, the permission management device determines whether the target object's operation permission for the operation interface is not authenticated or is authenticated. When the target object's operation permission for the operation interface is not authenticated, it is necessary to intercept the dangerous operation and perform a data rollback to ensure the security and continuity of data processing. Among them, the data rollback is achieved in the following ways: obtaining the data change information corresponding to each dangerous operation; obtaining the data storage table before rollback based on the data change information; intercepting any dangerous operation in each dangerous operation, and rolling back the data according to the data storage table before rollback, and finally rolling back to the data processing state before any dangerous operation to ensure the continuity of data processing.
[0163] By executing Figure 2 In the steps 201 to 205 shown, after determining the target object's operation rights for the operation interface based on the matching results, the target object A can obtain the operation rights for operation interface 1, but not the operation rights for operation interface 2. At this time, if you want to obtain the operation rights for operation interface 2, you need to apply to the system administrator. Before applying to the system administrator, you first need to obtain the approval path (dynamic approval path and static approval path are used to approve the rights of the target object). In some embodiments of the present invention, there are two ways to obtain the approval path:
[0164] 1) Due to changes in administrators, it is necessary to query administrator information through the operation interface "DescribeAdmins", and then obtain the organizational structure that matches the target object A; finally, based on the organizational structure, determine the dynamic approval path, and the administrator will approve the permissions through the dynamic approval path.
[0165] 2) When the administrator is fixed, a static approval path matching the target object is obtained, and the administrator performs permission approval through the static approval path.
[0166] In order to better illustrate the working process of the permission management method proposed in this application, the following is an example of the access management Web service. The following first explains the defects of the existing access management:
[0167] In order to manage the permissions of different users, the access management Web service generally uses the permission system to perform corresponding permission control, which supports the authorization and control of different roles, permissions and operations for different personnel, thereby limiting the functional scope that personnel in different roles can operate. The industry has carried out corresponding permission control based on the common permission control model RBAC, but there are the following defects:
[0168] 1) Currently, most permission management methods implement permission management at the interface level and page level separately. The permission control granularity is large and the degree of refinement is insufficient.
[0169] 2) Limiting the flow of operations for a single account is a common function of permission management, which limits the number of accesses or traffic within a certain time period for a certain account. If an account involves many resources, and the resources managed by the account exist in different regions, if only the flow of the account is controlled, it is possible that some regions may be occupied due to processing too many transactions, and the flow usage reaches the upper limit, resulting in access restrictions in other regions.
[0170] 3) Currently, most permission management methods verify whether the user has the permission for the interface, which is not enough to distinguish the particularities of different interfaces, different resources, and different operations. However, in many scenarios, interfaces, resources, operations, and operation scopes are different and need to be treated differently. Defining a fixed risk level for an interface or resource cannot meet the above scenarios.
[0171] 4) In the permission management method, the way to obtain permissions is generally to apply and approve, but for some more complex and sensitive operations, strict permission control is implemented, and each operation requires an application. It does not take into account the different risks of different operators. For those with higher proficiency and lower risk, they should have higher permissions. It is impossible to identify user proficiency on the fly, which makes it inconvenient for users to use.
[0172] In order to solve the above defects, an embodiment of the present invention provides a permission management method, which is applied to the Web service of access management. Access management (Cloud Access Management, CAM) is a Web service provided by cloud service products, mainly used to help customers securely manage access rights to resources under cloud service product accounts.
[0173] In the permission management method provided by this application, refer to Figure 4 , Figure 4FIG. 1 is a schematic diagram of the processing logic of the rights management in the embodiment of the present invention. Figure 4 In the processing logic shown, the rights management system DFS-5A covers the entire process from user login to logout. It first verifies the legitimacy of the user's identity (IOA verification), and then performs a six-stage resource rationality check. If there is no authority, it is necessary to apply for permission to access the MyOA process for approval; if the six-stage resource rationality check passes, the process of the target object operating the target interface is checked. If the six-stage resource rationality check fails, the six-stage resource of the target object needs to be adjusted to ensure that it meets the detection requirements of the rights management.
[0174] During the detection of the target object operating the target interface, if it is a dangerous operation, a deeper level of permission control is required, that is, when the user makes a normal interface request, a six-segment pattern of the currently accessed resource will be generated and matched with the six-segment pattern of the resource that has been granted permission. As long as any one is matched, the authentication can be passed. The interface for dangerous operations is different, and all six segments of resources must be matched to pass the authentication.
[0175] In the above process, when detecting the process of the target object operating the target interface, the process of the target operation can be detected in real time and dangerous operations can be blocked in time. Since data rollback is supported, after blocking the dangerous operation, the operation interface can be rolled back to the state before the dangerous operation is performed through data rollback, thereby ensuring the security and continuity of data processing.
[0176] In the above process, when detecting the process of the target object operating the target interface, the permission management system can also detect and record the user's actions throughout the entire process, analyze the operations of the target object, and thus adjust the security score of the target object, and use the security score to flexibly adjust the user's permissions, making permission management more flexible.
[0177] refer to Figure 5 , Figure 5 The following is an optional processing flow diagram of the rights management method in an embodiment of the present invention, which specifically includes the following steps:
[0178] Step 501: Obtain the first resource six-segment form of the target object.
[0179] Before executing step 501, the identity information of the target object needs to be verified, that is, the legitimacy of the user's identity is verified first (IOA verification). When the identity information of the target object is determined to have passed the verification using the token information (token), the key (code) of the target object is obtained, and then the six-segment resource matching the target object is searched through the key. At this time, the obtained six-segment resource is as follows: Figure 6 As shown, Figure 6This is a schematic diagram of the six-segment resource format in an embodiment of the present invention. The six-segment resource format definition method is as follows:
[0180] qcs:project_id:service_type:region:account:resource
[0181] Among them, you can set fine-grained permissions by setting fields. The restriction information includes qcs prefix, project, service, region, account, and resource.
[0182] Step 502: Detect the rationality of the six-segment format of the first resource of the target object to obtain a detection result.
[0183] In step 502, the rationality standard includes at least one of the following:
[0184] The empty status of project information, product support status, regional information support status, the accurate status of the account ID and APPID of the main account in the account information, and the support status of resource information.
[0185] Since the authorization granularity of cloud products is roughly divided into three levels: service level, operation level, and resource level. Therefore, unreasonable resource segments need to be adjusted to avoid the accuracy of user permissions being affected by unreasonable resource segments when permissions are adjusted. For example, the authorization granularity of cloud products includes: 1) Service level: defines whether the entire service has access rights, which is divided into allowing full operation rights for the service or denying full operation rights for the service. Cloud products with service-level authorization granularity do not support authorization for specific interfaces. 2) Operation level: defines whether a specific interface (API) of the service has access rights, for example: authorizing an account to perform read-only operations on cloud server services. 3) Resource level: defines whether a specific resource has access rights, which is the finest authorization granularity, for example: authorizing an account to only read and write operations on a cloud server instance. Products that support resource-level interface authorization will be identified as resource-level authorization granularity.
[0186] Step 503: When the detection result indicates that the six-stage rationality detection of the first resource has passed, an operation interface used by the target object to perform the target operation is obtained.
[0187] Before executing step 504, it is necessary to detect whether the operation interface is current-limited. When the operation interface is not current-limited, or the operation interface has not reached the current-limited times, step 504 can be executed to obtain the resource six-segment type of the interface.
[0188] Step 504: Obtain the second resource six-segment format of each verification attribute in the verification attribute set corresponding to the operation interface.
[0189] In some embodiments of the present invention, the interface authorization granularity is divided into two levels: resource level and operation level:
[0190] 1) Resource-level interface: This type of interface supports authorization for a specific resource.
[0191] 2) Operation-level interface: This type of interface does not support authorization for a specific resource. If the policy syntax during authorization limits specific resources, CAM will determine that this interface is not within the authorization scope and is considered unauthorized. Take resource-level write operations as an example:
[0192] 1) The interface is "RunInstances", which is used to create a cloud host V3. The corresponding six-segment resource is:
[0193] "qcs::cvm:${region}:uin / ${uin}:instance / *;
[0194] qcs::cvm:${region}:uin / ${uin}:image / ${imageId}”;
[0195] 2) The interface is "ModifyInstancesAttribute", which is used to modify instance attributes. The corresponding resource six-segment format is:
[0196] "qcs::cvm:${region}:uin / ${uin}:instance / ${instanceId};
[0197] qcs::cvm:${region}:uin / ${uin}:sg / ${sgId}”
[0198] Step 505: Match the first resource six-segment formula with the corresponding second resource six-segment formula respectively, and determine the operation authority of the target object for the operation interface based on the matching result.
[0199] refer to Figure 7 , Figure 7 This is a schematic diagram of the matching process of the first resource six-segment type and the second resource six-segment type in an embodiment of the present invention, which specifically includes the following steps:
[0200] Step 701: trigger the target interface call.
[0201] Step 702: Determine whether the target interface is current limited. If yes, execute step 703; otherwise, execute step 705.
[0202] Step 703: Query the number of API calls for the day.
[0203] Step 704: Determine whether the limit has been reached, if so, execute step 706, otherwise, execute step 708.
[0204] Step 705: Query the second resource six-segment type of the target interface.
[0205] Step 706: Match the first resource six-segment form of the target object with the second resource six-segment form of the target interface.
[0206] In some embodiments of the present invention, in step 706, the first resource six-segment form of the target object can be spliced into the corresponding first resource six-segment form according to the account and resource accessed by the user. It should be noted that: Figure 7 The target object shown can come from a user group, which is a collection of multiple users (sub-accounts) with the same functions. The main account and sub-accounts with administrator privileges can create different user groups according to business needs, and use user groups to perform batch authorization, set subscription messages, etc., so as to better manage users and their privileges. After creating a user group and completing authorization, you can add / remove policies for the user group to quickly change the privileges of the user group. The sub-accounts under the user group will manage the resources under the main account within the scope of the privileges obtained. Figure 8 It represents the intention of associating users with user groups, wherein the association relationship between users and user groups is stored, and only users associated with a certain user group have permissions within the user group. Fig. 9 This is the policy representation in this application, used to store the specific target interface resource six-segment format or the user's resource six-segment format. When a user group adds a policy, all users in the user group will have the permissions corresponding to the policy (for example, bind a policy with a policy ID of 524497 to a user group with a group ID of 3449). When a user group removes a policy, all users in the user group will no longer have the permissions corresponding to the policy. By adjusting Fig. 9 The six-segment storage of resources can achieve finer-grained restrictions under the interface granularity, distinguish the regions, products, accounts, and resource information corresponding to the resources operated by the interface to grant permissions and set flow-limiting data, thereby achieving more refined management of the permissions of the target objects.
[0207] In some embodiments of the present invention, through the above-mentioned processing, user groups, policy groups, and policies are used to perform coarse-grained permission management and control, policy binding interfaces, policy group binding policies, and user group binding policy groups. User groups are divided according to roles (roles can be substituted by any cloud service product account, and are not uniquely bound to a certain account. Roles do not have associated persistent certificates (passwords or access keys). The primary account only needs to use persistent certificates when applying for roles. When a user assumes a role, a temporary certificate will be dynamically created and provided to the user for corresponding access. The temporary certificate can be signed by a temporary key to call the open API of the basic service of the cloud service product to access the user's cloud resources). When a user joins a user group, he or she obtains the right to use all interfaces under the user group. Therefore, through the interconnection of the permission system and the business system: user groups can be marked in the permission system, and the marking information is customized by the business party. The marking can be obtained in the business and special processing can be performed to realize the business's autonomous expansion of permission functions, so as to adjust the user's permissions in time according to changes in usage needs, thereby supporting a wider range of business.
[0208] In some embodiments of the present invention, a role is a virtual identity with a set of permissions. It is used to grant the role carrier access to services, operations, and resources in cloud service products. You can associate the role with cloud resources, and access the APIs of other cloud products within the cloud resources based on the temporary key of the cloud service product security credential service STS (the temporary key can be updated periodically). Compared to directly using persistent keys for permission control, this method can further ensure the security of persistent keys under the account, and can also achieve more refined control and permission management based on role association policies.
[0209] Step 707: Obtain matching results.
[0210] Step 708: Return error prompt information.
[0211] In execution Figure 7 In the authentication process shown in the figure, different matches can be made through the six-segment resource format for different target operation types. Fig.10 , Fig.10 This is a logical diagram of the processing of dangerous operations in an embodiment of the present invention, in which when a user makes a normal interface request, the resource six-segment form of the currently accessed interface is obtained and matched with the resource six-segment form of the user who has been granted permission. As long as any one of them is matched, the authentication can be passed. The interface for dangerous operations is different. The authentication can only be passed when the resource six-segment form of the interface matches each attribute information in the resource six-segment form of the user.
[0212] exist Fig.10In the processing logic of the dangerous operation shown, it is possible to obtain dangerous attribute information that matches the operation interface; determine the interface type of the operation interface based on the dangerous attribute information; or detect the data transmitted through the operation interface; dynamically adjust the interface type of the operation interface based on the data transmitted by the operation interface to determine the interface type of the operation interface. Specifically, by configuring the dangerous attributes, rollback methods, and level operable thresholds of the DFS-SAPI, the danger level of the operation interface can be dynamically determined and a rollback operation can be performed. Dangerous operations are divided into three categories here: quota, switch, and resource. The danger levels of the switch and resource classes are uniquely determined, while the quota class supports flexible changes in danger levels based on different categories and resource operation thresholds, and dynamic permission control of each interface. In this way, dynamic setting of the functional danger level of the interface can be achieved, including:
[0213] 1) For functional interfaces with higher risk, the ability to specify a fixed risk level is provided. 2) Different risk levels are dynamically determined based on the parameter values passed by the interface. The demarcation methods include parameter thresholds, parameter enumeration inclusions, or parameter enumeration exclusions. For example, the cloud service product COS provides users with multi-channel, low-threshold log detection and auditing functions. For user access logs of buckets, such as deleting files (DeleteObject), overwriting files (PutObjectCopy), and modifying file permissions (PutObjectACL), they can all be obtained through the bucket access log function, and dangerous behaviors such as deletion operations can be traced and verified; for bucket configuration management behaviors, such as deleting buckets (DeleteBucket), modifying bucket access control lists (PutBucketACL), and modifying bucket policies (PutBucketPolicy), they can be obtained through cloud audit logs, and behaviors such as permission configuration modifications can also be traced and verified. The interface risk level is dynamically adjusted. The interfaces used in this process include the following types:
[0214] a) Leakage detection type interfaces, including: operating leakage detection data interface (SaDivulgeDataOperate), deleting detection scan rule policy interface (SaDivulgeScanRuleDelete), and setting leakage detection product detection scan rule policy interface (SaDivulgeScanRuleMutate and SaDivulgeScanRuleSet).
[0215] b) Interfaces related to security incidents, including: interfaces for operating security incidents (SaEventOperate), interfaces for opening cloud situational awareness product services (SaIntelligenceProductOpen), and interfaces for setting security weekly report configurations (SaSecVulIntelligenceSendMsgSetConfig).
[0216] c) Resource event class interfaces, including: resource score whitelist setting interface (ModifyAssetScoreWhitelist), resource mapping interface (ModifyStartAssetMapping), and configuration item status update interface (ModifyConfigStatus).
[0217] When it is determined that the target object has no authority to operate the dangerous interface shown in Table 3, the operation authority can be obtained through approval, and the approval method includes: 1) obtaining the organizational structure that matches the target object; according to the organizational structure, determining the dynamic approval path; 2) obtaining the static approval path that matches the target object, wherein the dynamic approval path and the static approval path are used to approve the authority of the target object. This makes the approval method of the operation authority more flexible.
[0218] In some embodiments of the present invention, since the target interface operation permission needs to be finely controlled as the user uses it, the permission time limit can be adjusted for the permission of the target object in response to the received time limit adjustment instruction. The adjustment method includes:
[0219] 1) Provide the ability to perform a single operation when permission is invalid; 2) Provide the ability to perform an unlimited number of operations during the permission invalidation period.
[0220] In some embodiments of the present invention, in order to provide the ability to specify the risk level for different interfaces, different resources, and different operation parameters, the data rollback function can be used to better ensure the security of special operations, which specifically includes the following steps:
[0221] Get the data change information corresponding to each dangerous operation; get the data storage table before rollback based on the data change information; intercept any dangerous operation in each dangerous operation, and roll back the data based on the data storage table before rollback to achieve rollback to the data processing state before any dangerous operation. Fig.11 As shown, Fig.11 This is an expression of the dangerous operation record in the embodiment of the present invention. Through the dangerous operation record, each dangerous operation performed by the user can be recorded and specific data change information can be stored. Fig.12This is a schematic diagram of the pre-rollback data storage table in an embodiment of the present invention. The pre-rollback data storage table can store information before data change, and implement rolling back operations to pre-stored data, thereby ensuring the security and continuity of data processing.
[0222] In some embodiments of the present invention, in order to achieve a balance between security and efficiency of rights management, a security score of the target object may be calculated. Fig.13 This is a logical diagram of the balance between security and efficiency in an embodiment of the present invention. For different users A and B, first calculate A's security score as 25 points and B's security score as 85 points. Specifically include the following steps: detect and record the operation history of the operation interface used by the target object to perform the target operation; determine the level of each dangerous operation based on the operation history; adjust the security score of the target object based on the level of each dangerous operation; adjust the permissions of the target object based on the security score of the target object. The following functions can be achieved: 1) Increase / decrease the security score with different values according to the danger level of the operation, use the security score to evaluate the proficiency of the user's operation, and obtain approval-free privileges of different danger levels when the security score is in different intervals. 2) Provide permission management personnel with the ability to increase and decrease user privileges within the security score limit. Among them, Fig.14 This is a database representation of the security score, which is used to record the user's security score information and then determine the privileges through code logic. Fig.15 The user authority adjustment record indicates the intention and is used to record the authority of the target object adjusted by the administrator, for example, for user A, the authority to operate the dangerous interface 1 is adjusted from no authority to authority.
[0223] pass Figure 7 The processing of steps 701 to 706 shown can achieve:
[0224] 1. Fine-grained permission control: Provides the function of fine-grained risk level classification, and controls permissions down to every parameter through a six-stage approach.
[0225] 2. API high concurrency flow control for large accounts: Six-stage permission management, with accounts, regions, and resources involved in flow control, solves the problem of traffic encroachment caused by flow control for large accounts.
[0226] 3. Dangerous operation protection: Provides the ability to specify danger levels for different interfaces, different resources, and different operation parameters, and provides rollback capabilities to better ensure the security of special operations.
[0227] 4. Balance between security and efficiency: Provide the ability to dynamically determine user privileges, analyze the user's operational proficiency, more humanely determine the dangerousness of the target object's operations, grant privileges, and allow reliable users to avoid cumbersome and meaningless permission acquisition processes.
[0228] The structure of the rights management device of the embodiment of the present invention is described in detail below. The rights management device can be implemented in various forms, such as a dedicated terminal with rights management function, such as the preceding Figure 1 Server 200 in. Fig.16 The schematic diagram of the electronic device structure of the operation authority management device provided by the embodiment of the present invention can be understood as follows: Fig.16 Only an exemplary structure of an electronic device running a rights management device is shown, not all structures, and may be implemented as needed. Fig.16 Partial or complete structure shown.
[0229] Fig.16 The electronic device 200 shown includes: at least one processor 210, a memory 240, and at least one network interface 220. The various components in the electronic device 200 are coupled together via a bus system 230. It is understood that the bus system 230 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 230 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, the bus system 230 is not described in detail. Fig.16 Various buses are labeled as bus system 230 .
[0230] The processor 210 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., where the general-purpose processor can be a microprocessor or any conventional processor, etc.
[0231] The memory 240 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state memory, hard disk drives, optical disk drives, etc. The memory 240 may optionally include one or more storage devices that are physically remote from the processor 210.
[0232] The memory 240 includes a volatile memory or a non-volatile memory, and may also include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), and the volatile memory may be a random access memory (RAM). The memory 240 described in the embodiments of the present application is intended to include any suitable type of memory.
[0233] In some embodiments, memory 240 can store data to support various operations, examples of which include programs, modules, and data structures, or a subset or superset thereof, as exemplarily described below.
[0234] Operating system 241, including system programs for processing various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks;
[0235] A network communication module 242, used to reach other electronic devices via one or more (wired or wireless) network interfaces 220, exemplary network interfaces 220 include: Bluetooth, Wireless Compatibility Authentication (WiFi), and Universal Serial Bus (USB), etc.;
[0236] In some embodiments, the rights management device provided in the embodiments of the present application can be implemented in software. Fig.16 The rights management device 243 stored in the memory 240 is shown, which can be software in the form of a program and a plug-in, etc., and includes the following software modules: an information transmission module 2081, an information processing module 2082. When the software modules in the rights management device are read into the RAM by the processor 201 and executed, the rights management method provided by the embodiment of the present invention will be implemented. The functions of each software module in the rights management device will be further described below, wherein:
[0237] The information transmission module 2081 is used to obtain the first attribute information of the target object for each verification attribute in the verification attribute set.
[0238] The information processing module 2082 is used to detect the rationality of each first attribute information of the target object and obtain a detection result.
[0239] The information processing module 2082 is used to obtain the operation interface used by the target object to perform the target operation when the detection result indicates that the rationality detection of each first attribute information has passed.
[0240] The information transmission module 2081 is used to obtain the second attribute information of each verification attribute in the verification attribute set corresponding to the operation interface.
[0241] The information processing module 2082 is used to match the first attribute information of each verification attribute with the corresponding second attribute information, and determine the operation authority of the target object for the operation interface based on the matching result.
[0242] In the above scheme,
[0243] The information processing module 2082 is used to record in real time the operation history of the operation interface used by the target object to perform the target operation;
[0244] The information processing module 2082 is used to determine the level of each dangerous operation according to the operation history;
[0245] The information processing module 2082 is used to adjust the safety score of the target object according to the level of each dangerous operation;
[0246] The information processing module 2082 is used to adjust the permissions of the target object according to the security score of the target object.
[0247] In the above scheme,
[0248] The information transmission module 2081 is used to obtain the token of the target object in response to the permission authentication request;
[0249] The information processing module 2082 is used to verify the identity information of the target object through the token of the target object;
[0250] The information processing module 2082 is used to obtain the key of the target object when the identity information of the target object passes the verification, wherein the key is used to find the first attribute information of the target object for each verification attribute in the verification attribute set.
[0251] In the above scheme,
[0252] The information processing module 2082 is used to obtain a rationality standard that matches the verification attribute set, wherein the rationality standard includes at least one of the following:
[0253] The blank status of project information, product support status, regional information support status, the accuracy of the account ID and APPID of the main account in the account information, and the support status of resource information;
[0254] The information processing module 2082 is used to perform a rationality check on the first attribute information according to the rationality standard, wherein the first attribute information includes at least one of the following:
[0255] The cloud server's resource prefix, project information, product name, region information, account information, and resource information.
[0256] In the above scheme,
[0257] The signal processing module 2082 is used to detect the current limiting property of the operation interface;
[0258] When the operation interface is not limited, or
[0259] When the operation interface does not reach the current limit times, second attribute information of each verification attribute in the verification attribute set corresponding to the operation interface is generated.
[0260] In the above scheme,
[0261] The information processing module 2082 is used to perform single element matching on the first attribute information and the second attribute information to obtain a first matching result when the operation interface type is a common interface, or
[0262] The information processing module 2082 is used to perform all element matching on the first attribute information and the second attribute information to obtain a second matching result when the operation interface type is a dangerous interface.
[0263] In the above scheme,
[0264] The signal information processing module 2082 is used for when the matching result is the first matching result, and
[0265] When any set of corresponding attribute information in the first attribute information and the second attribute information matches, determining that the operation authority of the target object for the operation interface is authenticated; or
[0266] The signal information processing module 2082 is used for when the matching result is the second matching result, and
[0267] When each set of corresponding attribute information in the first attribute information and the second attribute information matches, it is determined that the operation authority of the target object for the operation interface is authenticated.
[0268] In the above scheme,
[0269] The information processing module 2082 is used to obtain the dangerous attribute information matching the operation interface;
[0270] The information processing module 2082 is used to determine the interface type of the operation interface according to the risk attribute information; or
[0271] The signal processing module 2082 is used to detect the data transmitted through the operation interface;
[0272] The signal information processing module 2082 is used to dynamically adjust the interface type of the operation interface according to the data transmitted by the operation interface to determine the interface type of the operation interface.
[0273] In the above scheme,
[0274] The information processing module 2082 is used to obtain the resource operability threshold when the target object performs the target operation;
[0275] The information processing module 2082 is used to determine the interface corresponding to the dangerous switch operation, wherein the dangerous switch operation is used to set the DNS switch state;
[0276] The information processing module 2082 is used to determine the interface corresponding to the resource-type dangerous operation, wherein the resource-type dangerous operation is used to authorize a specific resource;
[0277] The information processing module 2082 is used to determine the interface corresponding to the quota-type dangerous operation according to the resource operable threshold, wherein the quota-type dangerous operation is used to adjust the interface quantity quota that matches the resources of the target object.
[0278] In the above scheme,
[0279] The information processing module 2082 is used to obtain the organizational structure that matches the target object;
[0280] The information processing module 2082 is used to determine the dynamic approval path according to the organizational structure; or
[0281] The information processing module 2082 is used to obtain a static approval path that matches the target object, wherein the dynamic approval path and the static approval path are used to approve the authority of the target object.
[0282] In the above scheme,
[0283] The information processing module 2082 is used to adjust the time limit of the target object's permission in response to the received time limit adjustment instruction, wherein the permission time limit includes:
[0284] Single permission validity period and multiple permission validity period.
[0285] In the above scheme,
[0286] The information processing module 2082 is used to obtain the data change information corresponding to each dangerous operation;
[0287] The information processing module 2082 is used to obtain the data storage table before rollback according to the data change information;
[0288] The signal processing module 2082 is used to intercept any dangerous operation in each dangerous operation and
[0289] Roll back data according to the data storage table before rollback to achieve
[0290] Roll back to the data processing state before any dangerous operation.
[0291] An embodiment of the present invention further provides an electronic device, the electronic device comprising:
[0292] A memory for storing executable instructions;
[0293] The processor is used to implement the aforementioned permission management method when running the executable instructions stored in the memory.
[0294] An embodiment of the present invention further provides a computer program product, including a computer program or instructions, characterized in that the computer program or instructions implement the aforementioned permission management method when executed by a processor.
[0295] The embodiment of the present invention further provides a computer-readable storage medium storing executable instructions, which implement the aforementioned permission management method when executed by a processor.
[0296] according to Fig.16 The electronic device shown, in one aspect of the present application, the present application also provides a computer program product or a computer program, the computer program product or the computer program includes a computer instruction, and the computer instruction is stored in a computer-readable storage medium. The processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the different embodiments and combinations of embodiments provided in various optional implementations of the permission method provided in the present application.
[0297] The above are only embodiments of the present invention and are not intended to limit the protection scope of the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the present invention.
Claims
1. A rights management method, characterized in that: The method comprises: Obtaining first attribute information of the target object for each verification attribute in the verification attribute set; Detecting the rationality of each of the first attribute information of the target object to obtain a detection result, wherein the rationality of the first attribute information is used to indicate that the target object is provided with permission to operate the corresponding port according to the rationality standard; When the detection result indicates that the rationality detection of each of the first attribute information has passed, obtaining an operation interface adopted by the target object to perform a target operation; Acquire second attribute information of each verification attribute in the verification attribute set corresponding to the operation interface; The first attribute information of each of the verification attributes is matched with the corresponding second attribute information respectively, and the operation authority of the target object for the operation interface is determined based on the matching result.
2. The method according to claim 1, characterized in that The method further comprises: Recording in real time the operation history of the operation interface used by the target object to perform the target operation; Determine the level of each dangerous operation based on the operation history; Adjusting the safety score of the target object according to the level of each dangerous operation; The authority of the target object is adjusted according to the security score of the target object.
3. The method according to claim 1, characterized in that Before obtaining the first attribute information of the target object for each verification attribute in the verification attribute set, the method further includes: In response to the permission authentication request, obtaining a token of the target object; Verifying the identity information of the target object through the token of the target object; When the identity information of the target object passes the verification, the key of the target object is obtained, wherein the key is used to find the first attribute information of the target object for each verification attribute in the verification attribute set.
4. The method according to claim 1, characterized in that: Detecting the rationality of each of the first attribute information of the target object includes: Obtaining a rationality standard that matches the verification attribute set, wherein the rationality standard includes at least one of the following: The empty status of project information, product support status, regional information support status, the accuracy of the account ID and APPID of the main account in the account information, and the support status of resource information; According to the rationality standard, a rationality check is performed on the first attribute information, wherein the first attribute information includes at least one of the following: The cloud server's resource prefix, project information, product name, region information, account information, and resource information.
5. The method according to claim 1, characterized in that Before obtaining the operation interface adopted by the target object to perform the target operation, the method further includes: Detecting the current limiting property of the operation interface; When the operation interface is not limited, or When the operation interface does not reach the current limiting times, second attribute information of each verification attribute in the verification attribute set corresponding to the operation interface is generated.
6. The method according to claim 1, characterized in that Matching the first attribute information of each verification attribute with the corresponding second attribute information respectively includes: When the operation interface type is a common interface, single element matching is performed on the first attribute information and the second attribute information to obtain a first matching result, or When the operation interface type is a dangerous interface, all elements of the first attribute information and the second attribute information are matched to obtain a second matching result.
7. The method according to claim 6, characterized in that Determining the operation authority of the target object for the operation interface based on the matching result includes: When the first matching result is that any set of corresponding attribute information in the first attribute information and the second attribute information matches, determining that the operation authority of the target object for the operation interface is authenticated; or When the second matching result is that each set of corresponding attribute information in the first attribute information and the second attribute information matches, it is determined that the operation authority of the target object for the operation interface is authenticated.
8. The method according to claim 6, characterized in that The method further comprises: Acquire the dangerous attribute information matching the operation interface; Determining the interface type of the operation interface according to the risk attribute information; or detecting data transmitted through the operation interface; The interface type of the operation interface is dynamically adjusted according to the data transmitted by the operation interface to determine the interface type of the operation interface.
9. The method according to claim 6, characterized in that The method further comprises: Obtaining a resource operable threshold when the target object performs a target operation; Determine an interface corresponding to a dangerous switch operation, wherein the dangerous switch operation is used to set a DNS switch state; Determine an interface corresponding to a resource-related dangerous operation, wherein the resource-related dangerous operation is used to authorize a specific resource; According to the resource operable threshold, an interface corresponding to a quota-type dangerous operation is determined, wherein the quota-type dangerous operation is used to adjust a quota of the number of interfaces that matches the resources of the target object.
10. The method according to claim 6, characterized in that The method further comprises: Obtaining an organizational structure that matches the target object; Determine a dynamic approval path based on the organizational structure; or A static approval path matching the target object is obtained, wherein the dynamic approval path and the static approval path are used to approve the authority of the target object.
11. The method according to claim 7, characterized in that After determining the target object's operation authority for the operation interface based on the matching result, the method further includes: In response to the received time limit adjustment instruction, the permission time limit of the target object is adjusted, wherein the permission time limit includes: Single permission validity period and multiple permission validity period.
12. A rights management device, characterized in that: The device comprises: An information transmission module, used to obtain first attribute information of the target object for each verification attribute in the verification attribute set; An information processing module, configured to detect the rationality of each of the first attribute information of the target object to obtain a detection result, wherein the rationality of the first attribute information is used to indicate that the target object is provided with permission to operate the corresponding port according to the rationality standard; The information processing module is used to obtain an operation interface used by the target object to perform a target operation when the detection result indicates that the rationality detection of each of the first attribute information has passed; The information transmission module is used to obtain second attribute information of each verification attribute in the verification attribute set corresponding to the operation interface; The information processing module is used to match the first attribute information of each verification attribute with the corresponding second attribute information, and determine the operation authority of the target object for the operation interface based on the matching result.
13. An electronic device, characterized in that: The electronic device comprises: A memory for storing executable instructions; A processor, configured to implement the permission management method described in any one of claims 1 to 11 when running the executable instructions stored in the memory.
14. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the rights management method described in any one of claims 1 to 11 is implemented.
15. A computer-readable storage medium storing executable instructions, characterized in that: When the executable instructions are executed by a processor, the permission management method described in any one of claims 1 to 11 is implemented.
Citation Information
Patent Citations
Access control method based on attribute-based access control policy
CN104967620A
Access control method based on trust and attributes in cloud computing environment
CN111431843A
Permission detection method and device, electronic equipment and readable storage medium
CN112464214A
Cited By
Account management method and device, equipment, medium and product
CN121603270A
