WO2017177819A1 - 数据库中密文数据换密失败的处理方法和装置 - Google Patents

数据库中密文数据换密失败的处理方法和装置 Download PDF

Info

Publication number
WO2017177819A1
WO2017177819A1 PCT/CN2017/078499 CN2017078499W WO2017177819A1 WO 2017177819 A1 WO2017177819 A1 WO 2017177819A1 CN 2017078499 W CN2017078499 W CN 2017078499W WO 2017177819 A1 WO2017177819 A1 WO 2017177819A1
Authority
WO
WIPO (PCT)
Prior art keywords
failure
record
ciphertext data
retry
policy
Prior art date
Application number
PCT/CN2017/078499
Other languages
English (en)
French (fr)
Inventor
李立
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Priority to MYPI2018703640A priority Critical patent/MY183034A/en
Priority to SG11201808892WA priority patent/SG11201808892WA/en
Priority to EP17781795.4A priority patent/EP3425579A4/en
Priority to KR1020187032659A priority patent/KR102204409B1/ko
Priority to JP2019503610A priority patent/JP6875499B2/ja
Publication of WO2017177819A1 publication Critical patent/WO2017177819A1/zh
Priority to US16/156,762 priority patent/US10884862B2/en
Priority to PH12018502186A priority patent/PH12018502186A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1415—Saving, restoring, recovering or retrying at system level
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766—Error or fault reporting or storing
    • G06F11/0778—Dumping, i.e. gathering error/state information after a fault for later diagnosis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1415—Saving, restoring, recovering or retrying at system level
    • G06F11/1443—Transmit or communication errors
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/22—Payment schemes or models
    • G06Q20/24—Credit schemes, i.e. "pay after"
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/356—Aspects of software for card payments
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/409—Device specific authentication in transaction processing
    • G06Q20/4093—Monitoring of device authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/061—Network architectures or network communication protocols for network security for supporting key management in a packet data network for key exchange, e.g. in peer-to-peer networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0891—Revocation or update of secret information, e.g. encryption key update or rekeying
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/805—Real-time
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/82—Solving problems relating to consistency

Definitions

  • the present application relates to the field of data processing, and in particular, to a method and apparatus for processing a ciphertext data exchange failure in a database.
  • PCI DSS Payment Card Industry Data Security Standard
  • PCI DSS security standard is considered to be the most authoritative data security protection at the moment, ensuring the security of sensitive information related to credit cards to the greatest extent possible.
  • the payment institution must change the ciphertext data of the credit card number in the credit card information database at regular intervals. Specifically, the ciphertext data of the card number in each record in the database is decrypted with the old password to obtain the card number plaintext, and then the new password is used to encrypt the plaintext to obtain the new ciphertext data of the card number, and then the new ciphertext data is replaced with the original ciphertext data. The ciphertext data in the record is updated, and the key version number in the record is updated to the version number of the new key and the change time in the update record.
  • the identifier of the record and the time when the key change fails are output to the failure log.
  • the technician analyzes the failure log, and specifies one or more retry time periods according to the change time period in which the failure record is located, and each change record belongs to each record of the specified retry time period, if the key version number of a record It has been updated to the new key version number and will not be retried, otherwise it will be re-typed.
  • This failure processing method requires manual analysis and specifies the retry period, and also needs to judge whether the record is successfully changed during retry, and the operation efficiency is low.
  • the present application provides a method for processing a ciphertext data exchange failure in a database, including:
  • the error information of the record is saved, including the identifier of the record and the reason for the failure;
  • the retrying policy is determined according to the reason for the failure of the saving, and the ciphertext data in the record with the identifier is re-densified by using the retrying strategy.
  • the application also provides a processing device for failing to change the ciphertext data in the database, including:
  • the error information saving unit is configured to save the error information of the record when the ciphertext data of a certain record fails to be encrypted, including the identifier of the record and the reason for the failure;
  • the policy and retry unit is configured to determine a retry policy according to the saved failure reason, and use the retry policy to re-denorate the ciphertext data in the record having the identifier.
  • the retrying policy of the record is determined according to the failure reason, and the failure record is automatically performed according to the retrying policy.
  • the re-recryption of ciphertext data, the targeted retry strategy can greatly improve the success rate of re-switching, greatly reducing the manpower work; at the same time, because only the failure record is retried, the operation efficiency of the failure processing is improved. .
  • FIG. 1 is a flowchart of a method for processing a ciphertext data change in a database in the embodiment of the present application
  • FIG. 3 is a flowchart of a failure record retry of the replacement task execution system in the application example of the present application;
  • FIG. 4 is a hardware structural diagram of a device to which the embodiment of the present application is applied;
  • FIG. 5 is a logical structural diagram of a processing apparatus for failing to encrypt a ciphertext data in a database in the embodiment of the present application.
  • the embodiment of the present application proposes a new method for processing the ciphertext data change failure in the database, saves the failure reason of the database record failure, and automatically performs the failure record ciphertext according to the retry policy determined by the failure reason.
  • the data is re-converted, so that not only the re-testing record does not need to be processed, but also the probability of successful re-succession is greatly improved, the execution efficiency of the failure processing is improved, and the automatic re-transformation can reduce the manual Work to solve the problems in the prior art.
  • Embodiments of the present application can be applied to any device having computing and storage capabilities, such as a mobile phone, a tablet, a PC (Personal Computer), a notebook, a server, a virtual machine, and the like.
  • the device to which the embodiment of the present application is applied may be a physical or logical device, or may be shared by two or more functions. The physical or logical devices cooperate with each other to implement various functions in the embodiments of the present application.
  • the flow of the processing method for the ciphertext data to change the confidentiality in the database is as shown in FIG. 1 .
  • Step 110 When the ciphertext data of a certain record fails to be changed, the error information of the record is saved, including the identifier of the record and the reason for the failure.
  • data is usually stored in the form of a table.
  • a column of a table is called a field
  • a row of the table is called a record
  • each record includes one or more field values corresponding to the columns of the table.
  • the data is stored in the table of the database in units of records, and operations such as reading, writing, and updating data in the table are usually performed for the records.
  • one or more field values in a record of the database may be ciphertext data, and different field values may use the same or different keys, which are not limited. If the ciphertext data of a record fails to be changed, an error message including the identifier of the record and the reason for the failure is saved.
  • the recorded identifier is used to uniquely identify a record within the scope of the saved error message.
  • the identifier of the record can be the primary key or unique index of the database table, or it can be a primary key or a combination of a unique index and other fields.
  • the combination of the table name and the primary key or the unique index may be used as the identifier of the record.
  • the primary key is one or more fields in the database table.
  • the primary key value of any record in the table is different from the primary key value of other records; the unique index is the value of one field or multiple fields in the database table.
  • a structure of sorting, and the unique index values of different records are different from each other, and are used to quickly query the value of the index field.
  • the change of ciphertext data in a record may fail for various reasons.
  • the cause of the failure can usually be located by the hardware or software exception when the failure occurs, or by reading a log describing the failure, warning, etc., and the cause of the failure is recorded in the error information of the record.
  • the reason for the failure of ciphertext data to be changed is related to the specific implementation of the scenario.
  • the failure reason may include an operation failure of the confidentiality and failure processing function component, a database read/write abnormality, and the like; If the ciphertext data is changed and its failure processing is performed on a different physical device than the database in the embodiment of the present application, the failure reason may be included in addition to the operation failure of the confidentiality and failure processing function component and the database read/write abnormality.
  • the communication between the two physical devices is abnormal.
  • the embodiments of the present application do not limit various specific reasons for failure.
  • Step 120 Determine a retry policy according to the saved failure reason, and use the retry policy to re-denorate the ciphertext data in the record with the identifier.
  • the retry strategy can include under what conditions the retry, how to retry, what parameters to retry, how many retryes, and so on.
  • the specific reason for the failure is different according to the application scenario and the specific implementation.
  • the retry policy set for the specific failure reason is also the same as the application scenario and the specific implementation requirements. There are no restrictions on the cause of failure and the retry strategy. Here are a few examples to illustrate.
  • the cause of failure usually includes database state exceptions.
  • Database state exceptions can include database inaccessibility, database jitter, database read and write errors, etc., because the self-recoverable database exception duration is often short, so the ciphertext data is changed.
  • the reason for the failure is that the database status is abnormal.
  • the retrying strategy may be to immediately re-change the ciphertext data in the record, and the number of re-changes does not exceed the first predetermined number of times.
  • the confidentiality of the ciphertext data in the database is performed by the variable execution function component calling the field value access function component, wherein the field value access function component records the ciphertext data in the record.
  • the value of the field is operated; after receiving the task of changing the ciphertext data in the database record, the function of changing the secret execution function uses the preset parameter to invoke the field value access function component to complete the task of changing the secret.
  • a field value access function component or a veneer execution function component can be a stand-alone program or application, or it can be part of a program or application that can run on the same or different physical or logical devices.
  • the field value access function component status exception can be one of the failure reasons.
  • Field Value Access Function Component status exceptions may include situations where the field value access function component itself is malfunctioning, and calls to field value access function components are broken. Since the failure recovery of the field value access function component usually takes a certain time, the retrying strategy may be: re-sending the ciphertext data in the record in which the failure of the field value access function component is abnormal after the first predetermined time interval. And the number of re-changes is not more than the second predetermined number of times. The time for the decryption failure may be written in the error message of the failure record to determine the time at which the retry can be performed according to the time when the key change failed and the first predetermined time.
  • the abnormality of the execution function component may also be one of the failure reasons.
  • the abnormal status of the change execution function component may include a situation in which the change function module itself operates in a malfunction, a communication failure, or the like.
  • the retry policy may be: immediately re-recording the ciphertext data in the record, and re-changing the secret does not exceed the third predetermined number of times.
  • the appropriate values and realities of the first predetermined number of times, the second predetermined number of times, and/or the third predetermined number of times is related to the current business operation situation. You can first set a certain value based on experience, and then adjust the set value according to factors such as the operation of the system and the proportion of successful retry. If the hardware or software of the application scenario, or the business load, the business process, or the like affects the operation of the system, the adjustment process may be repeated to obtain a suitable first predetermined number of times, a second predetermined number of times, and/or a third predetermined The value of the number of times.
  • the corresponding relationship between the reason for the failure and the retrying policy for the failure reason can be preset, and the corresponding retrying strategy can be found according to the failure reason of a certain record, and the retrying strategy is used to re-denature the record. If the re-denomination of the record is still unsuccessful according to the retry policy of a record, the error information of the record may be written into the failure log for manual analysis, intervention or other processing.
  • a dedicated retry function component can be employed to perform re-switching of the failed record.
  • the running logic of the retry function component can be implemented according to the needs of the actual application scenario.
  • a retry processing table can be maintained, and when the ciphertext data in a record fails to be changed, the error information of the record is recorded. Add to the retry processing table and mark as unsuccessful.
  • the retry function component When the retry function component satisfies the predetermined retry condition, the error information marked as unsuccessful in the retry processing table is read, and the record identifier and the failure reason in the error information are obtained; according to the retry strategy determined by the failure reason, The retry function component re-densifies the ciphertext data recorded in the database having the identifier. If the re-change is successful, the modification of the error message is marked as successful; if the re-transmission fails, the number of retries of the error message is changed; if the number of retries of the error message reaches the retry policy The maximum number of times, delete the error message in the retry processing table and write the error message to the failure log.
  • the parameters required for re-charging the ciphertext data in the database record may be written in the error information of the failure record, and the specific parameters are determined according to the implementation of the actual application scenario.
  • the error information of the failure record may include the old key version number and the new key version number.
  • the old password may be re-based according to the determined retry strategy.
  • the key corresponding to the key version number is used to decrypt the original ciphertext data to obtain plaintext data, and the new ciphertext data is obtained by encrypting the plaintext data according to the key corresponding to the new key version number, and replacing the failure record with the new ciphertext data.
  • Original ciphertext data is used to decrypt the original ciphertext data to obtain plaintext data
  • the new ciphertext data is obtained by encrypting the plaintext data according to the key corresponding to the new key version number, and replacing the failure record with the new ciphertext data.
  • the reason for the failure is that the ciphertext data in the record fails to be decrypted, the ciphertext data is already stored in the database, and the error cannot be solved by retrying; in this case, the record is not automatically retried, and Error information such as the identifier of the record is written in the failure log and left for manual processing.
  • the replacement task execution system (the secret-executing function component) receives the change-over task and the key-changing parameters for the task, including the old key version number and the new key version number.
  • the replacement task execution system can obtain the old key and the new key using the old key version number and the new key version number.
  • Each record in the credit card information database corresponds to a credit card, and the fields include a card index number, a card number ciphertext data, and a key version number of the encryption card number.
  • the card index number is used to uniquely represent a credit card in the credit card information database. In this application example, the card index number is used as the identifier of the record.
  • the replacement task execution system accesses the credit card information database by calling the card information database maintenance system (field value access function component), and performs the key exchange of the card number ciphertext data of each record, and the flow thereof is as shown in FIG. 2 .
  • Step 210 taking the first record in the credit card information database as the current record.
  • step 220 the card information database maintenance system is invoked to perform the current record change.
  • step 230 it is determined whether the current recorded change of confidentiality is successful. If it fails, step 240 is performed; if successful, step 250 is performed.
  • Step 240 Write the currently recorded card index number, failure reason, change execution time, old key version number, and new key version number as error information into the retry processing table, and retry the processing table.
  • the error message is marked as unsuccessful.
  • step 250 it is determined whether there is a next record in the credit card information database. If yes, the following record is the current record, and the process proceeds to step 220; if not, the password replacement process ends.
  • the reasons for the failure to change the password include the following four:
  • the first type the card information database maintenance system status is abnormal; the corresponding retry strategy is: retry after 1 hour of the change execution time, and allow up to 5 retry attempts;
  • the second type the credit card information database status is abnormal; the corresponding retry strategy is: immediate retry, up to 2 retry attempts;
  • the third type the replacement task execution system status is abnormal; the corresponding retry strategy is: immediate retry, allowing up to 2 retry attempts;
  • the fourth type the ciphertext data decryption fails, that is, the card number ciphertext data in the record cannot be decrypted into the plaintext data conforming to the card number data format by the old key; if the automatic retry is not performed, the error information is output to the failure log.
  • the replacement task execution system periodically performs an automatic retry of the failure record according to the error information saved in the retry processing table, and the flow thereof is as shown in FIG. 3.
  • Step 310 Read the first error information in the retry processing table as the current error information.
  • Step 320 Determine whether the flag of the current error message is unsuccessful. If yes, go to step 330; otherwise, go to step 380.
  • Step 330 Determine whether the cause of failure in the current error information is that the ciphertext data decryption fails, and if yes, go to step 370.
  • Step 340 Determine a retry policy according to the failure reason in the error information, and use the retry policy to invoke the card information database maintenance system to perform re-switching of the card number ciphertext data in the record with the card index number in the current error message until retrying Success or the maximum number of retries allowed for this retry policy.
  • Step 350 Determine whether the current error information is retried successfully. If yes, go to step 360; otherwise, go to step 370.
  • step 360 the flag of the current error information in the retry processing table is modified to be successful, and the process proceeds to step 380.
  • step 370 the current error information is written into the failure log, and the current error information in the retry processing table is deleted.
  • Step 380 Determine whether there is a next error message in the retry processing table. If yes, the following error message is used as the current error message, and the process proceeds to step 320; if not, the process of the automatic retry ends.
  • the embodiment of the present application further provides a processing device for failing to change the ciphertext data in the database.
  • the device can be implemented by software, or can be implemented by hardware or a combination of hardware and software.
  • the CPU Central Process Unit
  • the device in which the processing device for failing to encrypt the ciphertext data in the database usually includes a chip for transmitting and receiving wireless signals, and the like.
  • Other hardware, and/or other hardware such as boards used to implement network communication functions.
  • FIG. 5 is a schematic diagram of a processing device for failing to encrypt a ciphertext data in a database according to an embodiment of the present disclosure, including an error information saving unit, a policy, and a retry unit, wherein: the error information saving unit is configured to use a certain record. When the ciphertext data fails to be changed, the error information of the record is saved, including the identifier of the record and the reason for the failure; the policy and retry unit is configured to determine a retry policy according to the saved failure reason, and use the retry The policy re-deners the ciphertext data in the record with the identifier.
  • the failure cause includes: the database status is abnormal; the policy and the retry unit determine the retry policy according to the saved failure reason, including: when the failure reason is the database status abnormality, the retry policy is to immediately re-execute The change of the ciphertext data in the record is described, and the number of re-changes is not more than the first predetermined number of times.
  • the ciphertext data is changed by the field value access function component to the ciphertext data in the record.
  • the field value is operated;
  • the failure reason includes: the field value access function component status is abnormal;
  • the policy and the retry unit determine the retry policy according to the saved failure reason, including: when the failure reason is the field value access function component status abnormality
  • the retrying strategy is to re-denorate the ciphertext data in the record after the first predetermined time interval, and the number of re-changes is not more than the second predetermined number of times.
  • the ciphertext data exchange is invoked by the change execution function component to the field value access function component;
  • the failure cause includes: the change execution function component execution exception;
  • the policy and the retry unit are saved according to the save
  • the reason for the failure is determined by the retrying strategy, including: when the reason for the failure is that the execution of the function is changed, the retrying strategy is to immediately re-change the ciphertext data in the record, and the number of re-changes does not exceed The third predetermined number of times.
  • the device further includes a retry canceling unit, configured to re-denosize the ciphertext data in the record having the identifier when the reason for the failure is that the ciphertext data in the record fails to be decrypted.
  • a retry canceling unit configured to re-denosize the ciphertext data in the record having the identifier when the reason for the failure is that the ciphertext data in the record fails to be decrypted.
  • the device further includes a retry failure unit, configured to write the recorded error information into the failure log after failing to re-densify the ciphertext data in the record with the identifier by using a retry policy .
  • a retry failure unit configured to write the recorded error information into the failure log after failing to re-densify the ciphertext data in the record with the identifier by using a retry policy .
  • the error information holding unit is specifically configured to: when the ciphertext data in a record fails to be changed, add the error information of the record that fails the confidentiality to the retry processing table, and mark the unsuccessful
  • the policy and retry unit is specifically configured to: when the predetermined retry condition is met, read the error information marked as unsuccessful in the retry processing table, determine the retry strategy according to the failure reason, and adopt the determined weight
  • the test strategy re-densifies the ciphertext data with the record identified in the error message, and if the key change is successful, the mark of the error message is modified to be successful; otherwise, the number of retries of the error message is changed, when the number of retries reaches When the retrying policy allows the maximum number of times, the error information in the retry processing table is deleted and the error information is written into the failure log.
  • the error information further includes: an old key version number and a new key version number; the policy and the retry unit retrying the ciphertext data in the record having the identifier by using a retry policy
  • the secret includes: using the retrying policy, re-charging the ciphertext data in the record having the identifier according to the key corresponding to the old key version number and the key corresponding to the new key version number.
  • the ciphertext data includes: a credit card number ciphertext data.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-persistent memory, random access memory (RAM) and/or in a computer readable medium. Or a form such as non-volatile memory, such as read only memory (ROM) or flash memory (flash RAM). Memory is an example of a computer readable medium.
  • RAM random access memory
  • ROM read only memory
  • flash RAM flash memory
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

Abstract

本申请提供数据库中密文数据换密失败的处理方法和装置，该方法包括：当对某条记录的密文数据换密失败时，保存所述记录的错误信息，其中包括所述记录的标识和失败原因；根据保存的失败原因确定重试策略，采用所述重试策略对具有所述标识的记录中的密文数据重新进行换密。本申请的技术方案提高了重新换密的成功率，降低了人力工作，同时提高了失败处理的运行效率。

Description

数据库中密文数据换密失败的处理方法和装置
本申请要求2016年04月11日递交的申请号为201610221942.1、发明名称为“数据库中密文数据换密失败的处理方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及数据处理领域，尤其涉及一种数据库中密文数据换密失败的处理方法和装置。
背景技术
PCI DSS(Payment Card Industry Data Security Standard，支付卡行业数据安全标准)对于所有涉及信用卡的信息机构的安全方面作出了要求，其中包括安全管理、策略、过程、网络体系结构、软件设计等，以尽可能全面保障持卡人的交易安全。PCI DSS安全标准被认为是当前最权威的数据安全保护措施，能够在最大程度上保证与信用卡有关的敏感信息的安全性。
根据PCI DSS标准，支付机构的信用卡信息数据库中，所有的信用卡卡号以密文形式存储，并且加密卡号所使用的密钥至少要每年更换一次。因此，支付机构每隔一定时间，都要对信用卡信息数据库中信用卡卡号的密文数据进行换密。具体而言，将数据库中每条记录中卡号的密文数据以旧密码解密后得到卡号明文，再以新密码对明文加密后得到卡号的新密文数据，然后将新密文数据替换原有记录中的密文数据，并将该记录中的密钥版本号更新为新密钥的版本号、更新记录中的换密时间。
现有技术中，当对某条记录中的密文数据换密失败后，将该条记录的标识和换密失败的时间输出到失败日志中。技术人员分析失败日志，按照失败记录所在的换密时间段指定一个或多个重试时间段，对换密时间属于该指定重试时间段的每条记录，如果某条记录的密钥版本号已经更新为新密钥版本号，不再重试，否则重新进行换密。这种失败处理方式需要人工分析和指定重试时间段，并且在重试时还需要对记录是否换密成功做出判断，运行效率较低。
发明内容
有鉴于此，本申请提供一种数据库中密文数据换密失败的处理方法，包括：
当对某条记录的密文数据换密失败时，保存所述记录的错误信息，其中包括所述记录的标识和失败原因；
根据保存的失败原因确定重试策略，采用所述重试策略对具有所述标识的记录中的密文数据重新进行换密。
本申请还提供了一种数据库中密文数据换密失败的处理装置，包括：
错误信息保存单元，用于当对某条记录的密文数据换密失败时，保存所述记录的错误信息，其中包括所述记录的标识和失败原因；
策略及重试单元，用于根据保存的失败原因确定重试策略，采用所述重试策略对具有所述标识的记录中的密文数据重新进行换密。
由以上技术方案可见，本申请的实施例中，在数据库某条记录中的密文数据换密失败后，根据失败原因确定该条记录的重试策略，并按照重试策略自动进行失败记录中密文数据的重新换密，有针对性的重试策略能够极大的提高重新换密的成功率，大大降低了人力工作；同时由于只对失败记录进行重试，提高了失败处理的运行效率。
附图说明
图1是本申请实施例中一种数据库中密文数据换密失败的处理方法的流程图；
图2是本申请应用示例中替换任务执行系统的换密流程图；
图3是本申请应用示例中替换任务执行系统的失败记录重试流程图；
图4是本申请实施例所应用的设备的一种硬件结构图；
图5是本申请实施例中一种数据库中密文数据换密失败的处理装置的逻辑结构图。
具体实施方式
本申请的实施例提出一种新的数据库中密文数据换密失败的处理方法，保存换密失败的数据库记录的失败原因，按照由失败原因确定的重试策略来自动进行失败记录中密文数据的重新换密，从而不仅在重试时无需处理换密完毕的记录，而且能够极大的提高重试成功的概率，提高了失败处理的执行效率，同时自动执行的重新换密能够减少人工工作，以解决现有技术中存在的问题。
本申请的实施例可以应用在任何具有计算和存储能力的设备上，例如手机、平板电脑、PC(Personal Computer，个人电脑)、笔记本、服务器、虚拟机等设备。本申请实施例应用的设备可以是一个物理或逻辑设备，也可以是由两个或两个以上分担不同职责 的物理或逻辑设备、相互协同来实现本申请实施例中的各项功能。
本申请的实施例中，数据库中密文数据换密失败的处理方法的流程如图1所示。
步骤110，当对某条记录的密文数据换密失败时，保存该记录的错误信息，其中包括该记录的标识和失败原因。
数据库中，数据通常以表的形式来存储。表的一列称为一个字段，表的一行称为一条记录，每条记录包括一到多个对应于该表的列的字段值。数据以记录为单位保存在数据库的表中，对表中数据的读取、写入、更新等操作通常也针对记录来进行。
本申请的实施例中，数据库的一条记录中可以有一个到多个的字段值是密文数据，不同字段值可以采用相同或不同的密钥，不做限定。如果对某条记录的密文数据换密失败，保存包括该记录的标识和失败原因在内的错误信息。
记录的标识用来在所保存错误信息的范围内唯一确定一条记录。例如，如果保存对一个数据库表换密的错误信息，则记录的标识可以是该数据库表的主键或唯一索引，也可以是主键或唯一索引与其他字段的组合。再如，如果保存对多个数据库表换密的错误信息，由于不同表的主键或唯一索引可能有重复，则可以采用表名与主键或唯一索引的组合作为记录的标识。其中，主键是数据库表中的一个或多个字段，该表中任一条记录的主键值都与其他记录的主键值不同；唯一索引是对数据库表中一个字段或多个字段的值进行排序的一种结构，并且不同记录的唯一索引值互不相同，用来快速查询索引字段的值。
对一条记录中密文数据的换密可能因各种原因而失败。通常可以通过导致失败的故障发生时硬件或软件的异常来定位失败原因，也可以通过读取记载故障、警告等信息的日志来获取失败原因，并且将失败原因记载在该记录的错误信息中。
在不同应用场景中，密文数据换密的失败原因与该场景的具体实现有较大的关联度。例如，如果本申请实施例中密文数据换密及其失败处理、与数据库运行在同一个物理设备上，则失败原因可以包括换密及失败处理功能组件的运行故障、数据库读写异常等；如果本申请实施例中密文数据换密及其失败处理、与数据库运行在不同的物理设备上，则失败原因除换密及失败处理功能组件的运行故障、数据库读写异常外，还可以包括两个物理设备间的通信异常等。本申请的实施例对各种具体的失败原因不做限定。
步骤120，根据保存的失败原因确定重试策略，采用所述重试策略对具有所述标识的记录中的密文数据重新进行换密。
一些换密失败是由于运行过程中发生的暂时性异常造成的，在之后的运行中当暂时 性异常结束后，可以通过重试而成功换密。不同的暂时性异常所需要的恢复条件可能不同，因此，可以针对不同的失败原因，设置对应的重试策略，来尝试对换密失败的记录自动进行重新换密，以提高在无需人工干预的情况下的换密成功率。重试策略可以包括在什么条件下进行重试、以何种方式进行重试、采用怎样的参数进行重试、进行多少次重试等等。
如前所述，具体的失败原因因应用场景的不同和具体实现的不同而不同，针对具体失败原因而设置的重试策略最好也同样符合应用场景和具体实现的要求，本申请的实施例对失败原因和重试策略均不做限定。以下举几个例子来进行说明。
例如，失败原因通常包括数据库状态异常，数据库状态异常可以包括数据库无法访问、数据库抖动、数据库读写错误等情况，由于可自行恢复的数据库异常持续时间往往很短，因此对密文数据换密的失败原因是数据库状态异常的情形，重试策略可以是立即重新进行该记录中密文数据的换密，并且重新进行换密的次数不超过第一预定次数。
再如，在一种实现方式中，对数据库中密文数据的换密由换密执行功能组件调用字段值访问功能组件来进行，其中，由字段值访问功能组件对记录中密文数据所在的字段值进行操作；换密执行功能组件在接收到对数据库记录中密文数据的换密任务后，采用预设的参数调用字段值访问功能组件来完成换密任务。字段值访问功能组件或换密执行功能组件可以是一个独立运行的程序或应用，也可以是一个程序或应用中的一部分，二者可以运行在同一个或不同的物理或逻辑设备上。
这种实现方式中，可以将字段值访问功能组件状态异常作为失败原因中的一种。字段值访问功能组件状态异常可能包括字段值访问功能组件本身运行故障、对字段值访问功能组件的调用发生故障等情形。由于字段值访问功能组件的故障恢复通常需要一定时间，因此重试策略可以是：在间隔第一预定时间后重新进行失败原因为字段值访问功能组件状态异常的记录中密文数据的换密，并且重新进行换密的次数不超过第二预定次数。可以在失败记录的错误信息中写入换密失败的时间，以便根据换密失败的时间和第一预定时间来确定可以进行重试的时间。
在上述实现方式中，换密执行功能组件状态异常也可以作为失败原因中的一种。换密执行功能组件状态异常可能包括换密执行功能组件本身运行故障、通信故障等情形。当失败原因为换密执行功能组件执行异常时，重试策略可以是：立即重新进行记录中密文数据的换密，并且重新进行换密的次数不超过第三预定次数。
在上述几个例子中，第一预定次数、第二预定次数和/或第三预定次数的合适值与实 际应用场景的实现和当前业务运营情形相关，可以先根据经验设定某个值，然后根据系统的运行情况、重试成功的比例等因素来对设定值进行调整。如果应用场景的硬件或软件、或者业务负载、业务流程等影响系统运行的因素有变化时，还可以重复上述调整过程，以得到合适的第一预定次数、第二预定次数和/或第三预定次数的值。
可以预置失败原因与针对该失败原因的重试策略的对应关系，根据某条记录的失败原因即可查找到对应的重试策略，并采用该重试策略来对该记录重新进行换密。如果按照某条记录的重试策略对该记录的重新换密仍然以失败告终，可以将该记录的错误信息写入失败日志，供人工分析、干预或做其他处理。
在一种实现方式中，可以采用专门的重试功能组件来进行失败记录的重新换密。重试功能组件的运行逻辑可以根据实际应用场景的需要来实现，一个例子中，可以维护一张重试处理表，当某条记录中的密文数据换密失败时，将该记录的错误信息添加到重试处理表中，并标记为未成功。重试功能组件在满足预定重试条件时，读取重试处理表中标记为未成功的错误信息，取得该错误信息中的记录标识和失败原因；按照由该失败原因决定的重试策略，重试功能组件对具有该标识的数据库中记录的密文数据重新进行换密。如果重新进行的换密成功，则修改该错误信息的标记为成功；如果重新进行的换密失败，则更改该错误信息的重试次数；如果该错误信息的重试次数达到该重试策略允许的最大次数，删除重试处理表中的该错误信息并将该错误信息写入失败日志。
可以在失败记录的错误信息中写入对数据库记录中的密文数据重新进行换密时所需的参数，具体的参数根据实际应用场景的实现来确定。例如，失败记录的错误信息中可以包括旧密钥版本号和新密钥版本号，在对失败记录中的密文数据重新进行换密时，可以根据所确定的重试策略，重新根据旧密钥版本号对应的密钥来解密原密文数据得到明文数据，根据新密钥版本号对应的密钥加密明文数据得到新的密文数据，并以新的密文数据替换该失败记录中的原密文数据。
对并非由运行中暂时性异常导致的换密失败，则通常难以通过重试来成功换密。例如，如果失败原因是记录中密文数据解密失败，该密文数据已经存储于数据库中，无法通过重试来解决这一错误；在这种情况下，不对该记录进行自动重试，可以将该记录的标识等错误信息写入失败日志中，留待人工处理。
可见，本申请的实施例中，在数据库某条记录中密文数据换密失败后，保存该记录的失败原因，按照由失败原因确定的重试策略来自动进行失败记录中密文数据的重新换密，极大的提高了自动换密的成功率，减少了人工工作；并且由于在重新换密时无需处 理已经换密完毕的记录，提高了失败处理的运行效率。
在本申请的一个应用示例中，信用卡信息数据库中信用卡卡号的密文数据，每隔一定时间需要进行换密。当换密周期到时，替换任务执行系统(换密执行功能组件)接收到换密任务和用于本次任务的换密参数，其中包括旧密钥版本号和新密钥版本号。替换任务执行系统可以利用旧密钥版本号和新密钥版本号获取到旧密钥和新密钥。
信用卡信息数据库中每条记录对应一张信用卡，其字段包括卡索引号、卡号密文数据、加密卡号的密钥版本号。其中，卡索引号用来唯一代表信用卡信息数据库中的一张信用卡，在本应用示例中以卡索引号来作为记录的标识。
替换任务执行系统通过调用卡信息数据库维护系统(字段值访问功能组件)来访问信用卡信息数据库，进行其中每条记录的卡号密文数据的换密，其流程如图2所示。
步骤210，以信用卡信息数据库中的第一条记录作为当前记录。
步骤220，调用卡信息数据库维护系统来进行当前记录的换密。
步骤230，判断当前记录的换密是否成功，如果失败，执行步骤240；如果成功，转步骤250。
步骤240，将当前记录的卡索引号、失败原因、换密执行时间、旧密钥版本号和新密钥版本号作为错误信息，写入重试处理表中，并将重试处理表中的该条错误信息标记为未成功。
步骤250，判断是否信用卡信息数据库中有下一条记录，如果有，以下一条记录为当前记录，转步骤220；如果没有，换密流程结束。
换密的失败原因包括以下四种：
第一种：卡信息数据库维护系统状态异常；对应的重试策略为：在换密执行时间1小时后重试，最多允许5次重试；
第二种：信用卡信息数据库状态异常；对应的重试策略为：立即重试，最多允许2次重试；
第三种：替换任务执行系统状态异常；对应的重试策略为：立即重试，最多允许2次重试；
第四种：密文数据解密失败，即无法以旧密钥将记录中的卡号密文数据解密为符合卡号数据格式的明文数据；不进行自动重试，将本条错误信息输出到失败日志中。
替换任务执行系统定时按照重试处理表中保存的错误信息进行失败记录的自动重试，其流程如图3所示。
步骤310，读取重试处理表中的第一条错误信息作为当前错误信息。
步骤320，判断当前错误信息的标记是否为未成功，如果是，执行步骤330；否则转步骤380。
步骤330，判断当前错误信息中的失败原因是否为密文数据解密失败，如果是，转步骤370。
步骤340，按照错误信息中的失败原因确定重试策略，采用该重试策略调用卡信息数据库维护系统进行具有当前错误信息中卡索引号的记录中卡号密文数据的重新换密，直到重试成功或者达到该重试策略最多允许的重试次数。
步骤350，判断当前错误信息是否重试成功，如果是，执行步骤360；否则转步骤370。
步骤360，将重试处理表中当前错误信息的标记修改为成功，转步骤380。
步骤370，将当前错误信息写入失败日志中，删除重试处理表中的当前错误信息。
步骤380，判断重试处理表中是否有下一条错误信息，如果有，以下一条错误信息作为当前错误信息，转步骤320；如果没有，自动重试的流程结束。
与上述流程实现对应，本申请的实施例还提供了一种数据库中密文数据换密失败的处理装置。该装置可以通过软件实现，也可以通过硬件或者软硬件结合的方式实现。以软件实现为例，作为逻辑意义上的装置，是通过所在设备的CPU(Central Process Unit，中央处理器)将对应的计算机程序指令读取到内存中运行形成的。从硬件层面而言，除了图4所示的CPU、内存以及非易失性存储器之外，数据库中密文数据换密失败的处理装置所在的设备通常还包括用于进行无线信号收发的芯片等其他硬件，和/或用于实现网络通信功能的板卡等其他硬件。
图5所示为本申请实施例提供的一种数据库中密文数据换密失败的处理装置，包括错误信息保存单元和策略及重试单元，其中：错误信息保存单元用于当对某条记录的密文数据换密失败时，保存所述记录的错误信息，其中包括所述记录的标识和失败原因；策略及重试单元用于根据保存的失败原因确定重试策略，采用所述重试策略对具有所述标识的记录中的密文数据重新进行换密。
可选的，所述失败原因包括：数据库状态异常；所述策略及重试单元根据保存的失败原因确定重试策略，包括：当失败原因为数据库状态异常时，重试策略为立即重新进行所述记录中密文数据的换密，并且重新进行换密的次数不超过第一预定次数。
一个例子中，所述密文数据换密中由字段值访问功能组件对记录中密文数据所在的 字段值进行操作；所述失败原因包括：字段值访问功能组件状态异常；所述策略及重试单元根据保存的失败原因确定重试策略，包括：当失败原因为字段值访问功能组件状态异常时，重试策略为在间隔第一预定时间后重新进行所述记录中密文数据的换密，并且重新进行换密的次数不超过第二预定次数。
上述例子中，所述密文数据换密中由换密执行功能组件对字段值访问功能组件进行调用；所述失败原因包括：换密执行功能组件执行异常；所述策略及重试单元根据保存的失败原因确定重试策略，包括：当失败原因为换密执行功能组件执行异常时，重试策略为立即重新进行所述记录中密文数据的换密，并且重新进行换密的次数不超过第三预定次数。
可选的，所述装置还包括重试取消单元，用于当失败原因为记录中密文数据解密失败时，不对具有所述标识的记录中的密文数据重新进行换密。
可选的，所述装置还包括重试失败单元，用于在采用重试策略对具有所述标识的记录中密文数据的重新换密失败后，将所述记录的错误信息写入失败日志。
可选的，所述错误信息保存单元具体用于：当对某条记录中密文数据换密失败时，将换密失败的记录的错误信息添加到重试处理表中，并标记为未成功；所述策略及重试单元具体用于：在满足预定重试条件时，读取重试处理表中标记为未成功的错误信息，根据其中的失败原因确定重试策略，采用所确定的重试策略对具有错误信息中标识的记录重新进行密文数据换密，如果换密成功则将所述错误信息的标记修改为成功；否则更改所述错误信息的重试次数，当重试次数达到所述重试策略允许的最大次数时，删除重试处理表中的所述错误信息并将所述错误信息写入失败日志。
可选的，所述错误信息中还包括：旧密钥版本号和新密钥版本号；所述策略及重试单元采用重试策略对具有所述标识的记录中的密文数据重新进行换密，包括：采用所述重试策略，重新根据旧密钥版本号对应的密钥和新密钥版本号对应的密钥对具有所述标识的记录中的密文数据进行换密。
可选的，所述密文数据包括：信用卡卡号密文数据。
以上所述仅为本申请的较佳实施例而已，并不用以限制本申请，凡在本申请的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本申请保护的范围之内。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/ 或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本领域技术人员应明白，本申请的实施例可提供为方法、系统或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。

Claims (18)

  1. 一种数据库中密文数据换密失败的处理方法，其特征在于，包括：
    当对某条记录的密文数据换密失败时，保存所述记录的错误信息，其中包括所述记录的标识和失败原因；
    根据保存的失败原因确定重试策略，采用所述重试策略对具有所述标识的记录中的密文数据重新进行换密。
  2. 根据权利要求1所述的方法，其特征在于，所述失败原因包括：数据库状态异常；
    所述根据保存的失败原因确定重试策略，包括：当失败原因为数据库状态异常时，重试策略为立即重新进行所述记录中密文数据的换密，并且重新进行换密的次数不超过第一预定次数。
  3. 根据权利要求1所述的方法，其特征在于，所述密文数据换密中由字段值访问功能组件对记录中密文数据所在的字段值进行操作；所述失败原因包括：字段值访问功能组件状态异常；
    所述根据保存的失败原因确定重试策略，包括：当失败原因为字段值访问功能组件状态异常时，重试策略为在间隔第一预定时间后重新进行所述记录中密文数据的换密，并且重新进行换密的次数不超过第二预定次数。
  4. 根据权利要求3所述的方法，其特征在于，所述密文数据换密中由换密执行功能组件对字段值访问功能组件进行调用；所述失败原因包括：换密执行功能组件执行异常；
    所述根据保存的失败原因确定重试策略，包括：当失败原因为换密执行功能组件执行异常时，重试策略为立即重新进行所述记录中密文数据的换密，并且重新进行换密的次数不超过第三预定次数。
  5. 根据权利要求1所述的方法，其特征在于，所述方法还包括：当失败原因为记录中密文数据解密失败时，不对具有所述标识的记录中的密文数据重新进行换密。
  6. 根据权利要求1所述的方法，其特征在于，所述方法还包括：在采用重试策略对具有所述标识的记录中密文数据的重新换密失败后，将所述记录的错误信息写入失败日志。
  7. 根据权利要求1所述的方法，其特征在于，所述保存记录的错误信息包括：将换密失败的记录的错误信息添加到重试处理表中，并标记为未成功；
    所述根据保存的失败原因确定重试策略，采用所述重试策略对具有所述标识的记录中的密文数据重新进行换密，包括：在满足预定重试条件时，读取重试处理表中标记为未成功的错误信息，根据其中的失败原因确定重试策略，采用所确定的重试策略对具有错误信息中标识的记录重新进行密文数据换密，如果换密成功则将所述错误信息的标记修改为成功；否则更改所述错误信息的重试次数，当重试次数达到所述重试策略允许的最大次数时，删除重试处理表中的所述错误信息并将所述错误信息写入失败日志。
  8. 根据权利要求1至7任意一项所述的方法，其特征在于，所述错误信息中还包括：旧密钥版本号和新密钥版本号；
    所述采用重试策略对具有所述标识的记录中的密文数据重新进行换密，包括：采用所述重试策略，重新根据旧密钥版本号对应的密钥和新密钥版本号对应的密钥对具有所述标识的记录中的密文数据进行换密。
  9. 根据权利要求1所述的方法，其特征在于，所述密文数据包括：信用卡卡号密文数据。
  10. 一种数据库中密文数据换密失败的处理装置，其特征在于，包括：
    错误信息保存单元，用于当对某条记录的密文数据换密失败时，保存所述记录的错误信息，其中包括所述记录的标识和失败原因；
    策略及重试单元，用于根据保存的失败原因确定重试策略，采用所述重试策略对具有所述标识的记录中的密文数据重新进行换密。
  11. 根据权利要求10所述的装置，其特征在于，所述失败原因包括：数据库状态异常；
    所述策略及重试单元根据保存的失败原因确定重试策略，包括：当失败原因为数据库状态异常时，重试策略为立即重新进行所述记录中密文数据的换密，并且重新进行换密的次数不超过第一预定次数。
  12. 根据权利要求10所述的装置，其特征在于，所述密文数据换密中由字段值访问功能组件对记录中密文数据所在的字段值进行操作；所述失败原因包括：字段值访问功能组件状态异常；
    所述策略及重试单元根据保存的失败原因确定重试策略，包括：当失败原因为字段值访问功能组件状态异常时，重试策略为在间隔第一预定时间后重新进行所述记录中密文数据的换密，并且重新进行换密的次数不超过第二预定次数。
  13. 根据权利要求12所述的装置，其特征在于，所述密文数据换密中由换密执行 功能组件对字段值访问功能组件进行调用；所述失败原因包括：换密执行功能组件执行异常；
    所述策略及重试单元根据保存的失败原因确定重试策略，包括：当失败原因为换密执行功能组件执行异常时，重试策略为立即重新进行所述记录中密文数据的换密，并且重新进行换密的次数不超过第三预定次数。
  14. 根据权利要求10所述的装置，其特征在于，所述装置还包括：重试取消单元，用于当失败原因为记录中密文数据解密失败时，不对具有所述标识的记录中的密文数据重新进行换密。
  15. 根据权利要求10所述的装置，其特征在于，所述装置还包括：重试失败单元，用于在采用重试策略对具有所述标识的记录中密文数据的重新换密失败后，将所述记录的错误信息写入失败日志。
  16. 根据权利要求10所述的装置，其特征在于，所述错误信息保存单元具体用于：当对某条记录中密文数据换密失败时，将换密失败的记录的错误信息添加到重试处理表中，并标记为未成功；
    所述策略及重试单元具体用于：在满足预定重试条件时，读取重试处理表中标记为未成功的错误信息，根据其中的失败原因确定重试策略，采用所确定的重试策略对具有错误信息中标识的记录重新进行密文数据换密，如果换密成功则将所述错误信息的标记修改为成功；否则更改所述错误信息的重试次数，当重试次数达到所述重试策略允许的最大次数时，删除重试处理表中的所述错误信息并将所述错误信息写入失败日志。
  17. 根据权利要求10至16任意一项所述的装置，其特征在于，所述错误信息中还包括：旧密钥版本号和新密钥版本号；
    所述策略及重试单元采用重试策略对具有所述标识的记录中的密文数据重新进行换密，包括：采用所述重试策略，重新根据旧密钥版本号对应的密钥和新密钥版本号对应的密钥对具有所述标识的记录中的密文数据进行换密。
  18. 根据权利要求10所述的装置，其特征在于，所述密文数据包括：信用卡卡号密文数据。
PCT/CN2017/078499 2016-04-11 2017-03-29 数据库中密文数据换密失败的处理方法和装置 WO2017177819A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
MYPI2018703640A MY183034A (en) 2016-04-11 2017-03-29 Method and apparatus for processing failure of cipher change of ciphertext in database
SG11201808892WA SG11201808892WA (en) 2016-04-11 2017-03-29 Method and apparatus for processing failure of cipher change of ciphertext in database
EP17781795.4A EP3425579A4 (en) 2016-04-11 2017-03-29 METHOD AND DEVICE FOR PROCESSING THE FAILURE OF CHIFFRETEXT CHIFFER REPLACEMENT IN A DATABASE
KR1020187032659A KR102204409B1 (ko) 2016-04-11 2017-03-29 데이터베이스에서 암호문의 암호 변경의 실패를 처리하기 위한 방법 및 장치
JP2019503610A JP6875499B2 (ja) 2016-04-11 2017-03-29 データベース内の暗号文の暗号変更の障害を処理する方法及び装置
US16/156,762 US10884862B2 (en) 2016-04-11 2018-10-10 Method and apparatus for processing failure of cipher change of ciphertext in database
PH12018502186A PH12018502186A1 (en) 2016-04-11 2018-10-11 Method and apparatus for processing failure of cipher change of ciphertext in database

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610221942.1A CN107292618B (zh) 2016-04-11 2016-04-11 数据库中密文数据换密失败的处理方法和装置
CN201610221942.1 2016-04-11

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/156,762 Continuation US10884862B2 (en) 2016-04-11 2018-10-10 Method and apparatus for processing failure of cipher change of ciphertext in database

Publications (1)

Publication Number Publication Date
WO2017177819A1 true WO2017177819A1 (zh) 2017-10-19

Family

ID=60041360

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/078499 WO2017177819A1 (zh) 2016-04-11 2017-03-29 数据库中密文数据换密失败的处理方法和装置

Country Status (10)

Country Link
US (1) US10884862B2 (zh)
EP (1) EP3425579A4 (zh)
JP (1) JP6875499B2 (zh)
KR (1) KR102204409B1 (zh)
CN (1) CN107292618B (zh)
MY (1) MY183034A (zh)
PH (1) PH12018502186A1 (zh)
SG (1) SG11201808892WA (zh)
TW (1) TWI675311B (zh)
WO (1) WO2017177819A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020001303A1 (en) * 2018-06-25 2020-01-02 Beijing Didi Infinity Technology And Development Co., Ltd. Systems and methods for operation retry
CN112486719A (zh) * 2020-12-14 2021-03-12 上海悦易网络信息技术有限公司 一种用于rpc接口调用失败处理的方法及设备

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110780983A (zh) * 2019-09-10 2020-02-11 中国平安财产保险股份有限公司 任务异常处理方法、装置、计算机设备以及存储介质
CN111030868B (zh) * 2019-12-19 2023-12-05 紫光云(南京)数字技术有限公司 一种弹性公网ip下发设备失败的解决方法
CN111709736B (zh) * 2020-05-14 2023-04-07 支付宝(杭州)信息技术有限公司 一种处罚策略的处理方法、装置及电子设备
CN113419924B (zh) * 2021-08-23 2021-12-07 北京安华金和科技有限公司 一种基于会话保持的数据库操作风险提示处理方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101895846A (zh) * 2010-07-23 2010-11-24 中兴通讯股份有限公司 自适应短消息重试控制方法及装置
CN104376070A (zh) * 2014-11-12 2015-02-25 中国建设银行股份有限公司 更新数据库记录的控制方法和装置
CN104936308A (zh) * 2015-06-18 2015-09-23 西南交通大学 一种双连接路径更新失败的处理方法与装置

Family Cites Families (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4229818A (en) * 1978-12-29 1980-10-21 International Business Machines Corporation Method and apparatus for enciphering blocks which succeed short blocks in a key-controlled block-cipher cryptographic system
JP3748155B2 (ja) 1997-11-14 2006-02-22 富士通株式会社 改ざん防止／検出機能を有するファイル管理システム
US6108419A (en) * 1998-01-27 2000-08-22 Motorola, Inc. Differential fault analysis hardening apparatus and evaluation method
JPH11231778A (ja) * 1998-02-18 1999-08-27 Matsushita Electric Ind Co Ltd 暗号化装置及び復号装置、暗号化方法及び復号方法並びにそれらの方法を記録した記録媒体
US7559088B2 (en) 2004-02-04 2009-07-07 Netapp, Inc. Method and apparatus for deleting data upon expiration
JP2006155155A (ja) 2004-11-29 2006-06-15 Fujitsu Ltd 情報漏洩防止装置、方法およびそのプログラム
US8176158B2 (en) * 2005-08-09 2012-05-08 Tripwire, Inc. Information technology governance and controls methods and apparatuses
US7996679B2 (en) 2005-10-05 2011-08-09 International Business Machines Corporation System and method for performing a trust-preserving migration of data objects from a source to a target
US7694134B2 (en) 2005-11-11 2010-04-06 Computer Associates Think, Inc. System and method for encrypting data without regard to application
CN101047978A (zh) * 2006-03-27 2007-10-03 华为技术有限公司 对用户设备中的密钥进行更新的方法
US7793110B2 (en) 2006-05-24 2010-09-07 Palo Alto Research Center Incorporated Posture-based data protection
JP4288292B2 (ja) * 2006-10-31 2009-07-01 株式会社エヌ・ティ・ティ・ドコモ オペレーティングシステム監視設定情報生成装置及びオペレーティングシステム監視装置
US8385551B2 (en) 2006-12-22 2013-02-26 Telefonaktiebolaget L M Ericsson (Publ) Highly available cryptographic key storage (HACKS)
US8423789B1 (en) 2007-05-22 2013-04-16 Marvell International Ltd. Key generation techniques
US8225105B2 (en) 2007-08-13 2012-07-17 International Business Machines Corporation Method and apparatus for verifying integrity of computer system vital data components
US9158933B2 (en) * 2007-08-17 2015-10-13 Sybase, Inc. Protection of encryption keys in a database
JP4985312B2 (ja) * 2007-10-24 2012-07-25 セイコーエプソン株式会社 データ管理装置、データ管理システム及びプログラム
US8005227B1 (en) 2007-12-27 2011-08-23 Emc Corporation Key information consistency checking in encrypting data storage system
US8055633B2 (en) 2008-01-21 2011-11-08 International Business Machines Corporation Method, system and computer program product for duplicate detection
US7987496B2 (en) 2008-04-11 2011-07-26 Microsoft Corporation Automatic application of information protection policies
CN101291457B (zh) * 2008-05-30 2012-09-05 中兴通讯股份有限公司 一种ue上下文更新失败的处理方法
US8281388B1 (en) 2008-06-27 2012-10-02 Symantec Corporation Hardware secured portable storage
JP2010176303A (ja) * 2009-01-28 2010-08-12 Nippon Yunishisu Kk バッチ処理システムおよびこれに用いる情報端末装置、バッチ処理のリカバリ方法
US8707082B1 (en) * 2009-10-29 2014-04-22 Symantec Corporation Method and system for enhanced granularity in fencing operations
JP2011164907A (ja) * 2010-02-09 2011-08-25 Hitachi Solutions Ltd 情報管理システム
US8276022B2 (en) * 2010-04-30 2012-09-25 Yahoo! Inc. Efficient failure detection for long running data transfer jobs
US8762944B2 (en) 2011-03-23 2014-06-24 International Business Machines Corporation Build process management system
US9221079B1 (en) * 2011-08-02 2015-12-29 National Presort, Inc. System and method for real-time address correction
CN102332981A (zh) * 2011-10-12 2012-01-25 深圳市沃达通实业有限公司 三层密钥的加密方法及银行交易系统
CN102315933B (zh) * 2011-10-18 2014-02-05 飞天诚信科技股份有限公司 一种更新密钥的方法及系统
CN102387500B (zh) * 2011-10-25 2015-10-28 中兴通讯股份有限公司 一种业务密钥管理方法及系统
CN102413126B (zh) * 2011-11-04 2014-05-07 中国工商银行股份有限公司 一种银行卡交易前置设备的密钥同步方法及系统
US8726392B1 (en) * 2012-03-29 2014-05-13 Symantec Corporation Systems and methods for combining static and dynamic code analysis
JP5968156B2 (ja) 2012-08-08 2016-08-10 キヤノン株式会社 ジョブ処理システム、情報処理システム、ジョブ処理方法、情報処理方法、およびプログラム
US9053025B2 (en) 2012-12-28 2015-06-09 Intel Corporation Apparatus and method for fast failure handling of instructions
JP2015060286A (ja) * 2013-09-17 2015-03-30 株式会社日立システムズ クラウドコンピューティングでの遅延処理方法
US9405920B1 (en) * 2014-05-21 2016-08-02 Amazon Technologies, Inc. Data integrity verification
JP6373690B2 (ja) * 2014-09-05 2018-08-15 ルネサスエレクトロニクス株式会社 半導体装置
TW201610907A (zh) * 2014-09-10 2016-03-16 中華電信股份有限公司 電信訂單異質化資料同步轉換的方法
US11469902B2 (en) * 2019-03-29 2022-10-11 Intel Corporation Systems and methods of using cryptographic primitives for error location, correction, and device recovery

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101895846A (zh) * 2010-07-23 2010-11-24 中兴通讯股份有限公司 自适应短消息重试控制方法及装置
CN104376070A (zh) * 2014-11-12 2015-02-25 中国建设银行股份有限公司 更新数据库记录的控制方法和装置
CN104936308A (zh) * 2015-06-18 2015-09-23 西南交通大学 一种双连接路径更新失败的处理方法与装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3425579A4 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020001303A1 (en) * 2018-06-25 2020-01-02 Beijing Didi Infinity Technology And Development Co., Ltd. Systems and methods for operation retry
CN110704121A (zh) * 2018-06-25 2020-01-17 北京嘀嘀无限科技发展有限公司 一种操作重试的方法、系统及计算机装置
CN110704121B (zh) * 2018-06-25 2021-07-20 北京嘀嘀无限科技发展有限公司 一种操作重试的方法、系统及计算机装置
CN112486719A (zh) * 2020-12-14 2021-03-12 上海悦易网络信息技术有限公司 一种用于rpc接口调用失败处理的方法及设备

Also Published As

Publication number Publication date
TW201738801A (zh) 2017-11-01
PH12018502186A1 (en) 2019-09-23
US20190042367A1 (en) 2019-02-07
KR20180128064A (ko) 2018-11-30
CN107292618B (zh) 2020-04-28
TWI675311B (zh) 2019-10-21
EP3425579A1 (en) 2019-01-09
JP6875499B2 (ja) 2021-05-26
US10884862B2 (en) 2021-01-05
JP2019514147A (ja) 2019-05-30
CN107292618A (zh) 2017-10-24
EP3425579A4 (en) 2019-11-06
SG11201808892WA (en) 2018-11-29
MY183034A (en) 2021-02-08
KR102204409B1 (ko) 2021-01-19

Similar Documents

Publication Publication Date Title
WO2017177819A1 (zh) 数据库中密文数据换密失败的处理方法和装置
EP3547198B1 (en) Method, system and apparatus for data access
US9621549B2 (en) Integrated circuit for determining whether data stored in external nonvolative memory is valid
US10599863B2 (en) Database encryption to provide write protection
US20210124730A1 (en) Blockchain based distributed file systems
US20210357516A1 (en) Method for duplexing database
CN113568568B (zh) 一种基于分布式存储的硬件加密方法、系统及装置
CN111539042B (zh) 一种基于核心数据文件可信存储的安全操作方法
US11868339B2 (en) Blockchain based distributed file systems
CN104282098A (zh) 一种税控装置的开票及抄税过程升级方法
CN102034040A (zh) 一种加密卡内日志实现方法
US11397830B2 (en) Security rules compliance for personally identifiable information
CN112416269A (zh) 一种射频传输信息加密访问方法、装置、电子设备及介质
CN112395591A (zh) 改密方法及系统
CN111404662B (zh) 一种数据处理方法及装置
CN114095175B (zh) 一种可灰度校验的数据保密方法、装置及存储介质
KR102430085B1 (ko) 암호화 기능을 수행하는 커널 모듈
US11693845B2 (en) System and method for event-based data acquisition in real-time applications
JP2006195992A (ja) ファイル使用状況の記録方法及びコンピュータの読み取り可能な記録媒体
CN116204131A (zh) 电子设备的秘钥数据读写方法和系统
CN111404863A (zh) 一种数据处理方法及装置
KR20190020719A (ko) 데이터베이스의 이중화를 위한 방법
Kyte Data Encryption

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2017781795

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2019503610

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017781795

Country of ref document: EP

Effective date: 20181003

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20187032659

Country of ref document: KR

Kind code of ref document: A

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17781795

Country of ref document: EP

Kind code of ref document: A1