Data protection implementation method and device, computer device and storage medium
By creating a list of encrypted files on the hard drive and using the hard drive's own encryption algorithm to encrypt the target files, the problems of data security and user experience in hard drive encryption methods are solved, and flexible encryption and security protection of local files on the hard drive are achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- LENOVO (BEIJING) LTD
- Filing Date
- 2021-12-31
- Publication Date
- 2026-04-14
AI Technical Summary
In existing technologies, hard drive encryption methods cannot reliably guarantee data security after the password is forgotten, and the encryption and decryption process is cumbersome, affecting the user experience.
By creating a list of encrypted files on the hard drive, recording the address information of the files to be encrypted, and using the hard drive's own encryption algorithm to encrypt the target files, flexible encryption of local files on the hard drive is achieved, supporting quick encryption operations and decryption interface verification.
It improves the flexibility and security of data protection, allowing users to operate unencrypted files even if they forget their hard drive password, avoiding the loss of encrypted data during formatting and enhancing the user experience.
Smart Images

Figure CN114329651B_ABST
Abstract
Description
Technical Field
[0001] This application mainly relates to the field of computer security applications, and more specifically to a data protection implementation method, apparatus, computer equipment, and storage medium. Background Technology
[0002] Hard drives are one of the most important storage devices in computer equipment. Most of the applications required for computer operation and the data they generate are stored on hard drives. To improve the security of computer data, the entire hard drive can be encrypted. In this way, any access request to the hard drive requires the correct password to be responded to. Once the password is forgotten, the hard drive cannot be used, which is very troublesome. Moreover, the process of accessing application data that does not require encryption is cumbersome, which reduces the user experience.
[0003] To achieve flexibility in computer data protection, a software-based data protection method called Windows BitLocker has been proposed. This method can encrypt all or part of the data stored on the Windows operating system to meet the protection needs of target data on a computer. However, this data protection method cannot reliably guarantee the security of encrypted data; it can be destroyed by formatting the hard drive or reinstalling the operating system. Summary of the Invention
[0004] In view of this, this application proposes a data protection implementation method, the method comprising:
[0005] Identify the target file to be encrypted on the hard drive; the target file is at least a portion of the hard drive files.
[0006] In response to the encryption operation on the target file, obtain the address information of the target file;
[0007] The address information of the target file is added to the list of encrypted files in the hard disk, and the target file stored on the hard disk is encrypted.
[0008] The encrypted file list is used to indicate access control for the hard disk files containing the address information.
[0009] Optionally, if the address information includes a logical block address, adding the address information of the target file to the encrypted file list on the hard disk and encrypting the target file stored on the hard disk includes:
[0010] Add the logical block address of the target file to the list of encrypted files on the hard disk;
[0011] The preset encryption application of the hard drive is invoked to encrypt the target file, thereby preventing any application from accessing the target file before decryption.
[0012] Optionally, the method further includes:
[0013] Obtain a file processing request for the hard disk;
[0014] If the address information of the requested file is found to be included in the encrypted file list, the hard drive decryption interface is output.
[0015] In response to the hard drive decryption password entered on the hard drive decryption interface, the file to be processed stored on the hard drive is decrypted;
[0016] In response to the file processing request, perform corresponding processing operations on the decrypted file to be processed.
[0017] Optionally, responding to the file processing request and performing corresponding processing operations on the decrypted file to be processed includes:
[0018] In response to the file processing request, at least part of the content of the decrypted file to be processed is updated, deleted, or queried.
[0019] The updated file content is encrypted, and the new address information generated by the updated file content is added to the corresponding position in the encrypted file list;
[0020] Output the content of the file queried in the decrypted file to be processed.
[0021] Optionally, responding to the file processing request and performing corresponding processing operations on the decrypted file to be processed includes:
[0022] In response to the decryption operation of the file to be processed, the address information of the file to be processed is removed from the list of encrypted files, and the encryption operation on the file to be processed is decrypted.
[0023] Optionally, the response to the encryption operation of the target file, obtaining the address information of the target file, includes:
[0024] In response to an encrypted shortcut operation performed on the target file in the selected state, the logical block address of the target file is obtained;
[0025] The encrypted shortcut operation includes one or more combinations of specific function key input operations, voice input operations, and specific gesture input operations.
[0026] Optionally, the list of encrypted files is created and maintained by the firmware of the hard drive.
[0027] This application also proposes a data protection implementation device, the device comprising:
[0028] The target file determination module is used to determine the target file to be encrypted on the hard disk; the target file is at least a portion of the hard disk files.
[0029] The address information acquisition module is used to obtain the address information of the target file in response to an encryption operation on the target file.
[0030] An encryption processing module is used to add the address information of the target file to the encrypted file list created by the firmware of the hard disk, and to encrypt the target file stored on the hard disk.
[0031] The encrypted file list is used to indicate access control for the hard disk files containing the address information.
[0032] This application also proposes a computer device, the computer device comprising:
[0033] A memory for storing programs implementing the data protection method described above, and the memory includes a hard disk for storing multiple files.
[0034] A processor is used to load and execute the program stored in the memory to implement the data protection method described above.
[0035] This application also proposes a storage medium on which a computer program is stored, the computer program being loaded and executed by a processor to implement the data protection method described above.
[0036] Therefore, this application provides a data protection method, apparatus, computer device, and storage medium. By adding the address information of selected hard disk files to the encrypted file list created on the hard disk, and activating its own encryption algorithm to encrypt the contents of these hard disk files, partial hard disk file encryption is achieved, improving the flexibility of data protection. Even if the hard disk password is forgotten, the unencrypted hard disk files can still be operated on, meeting application needs. Compared with software data protection methods that are prone to destroying encrypted data during hard disk formatting, this application can still retain the encrypted target files on the hard disk during hard disk formatting, further improving the security of hard disk files. Attached Figure Description
[0037] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.
[0038] Figure 1 A flowchart illustrating an optional example of the data protection implementation method proposed in this application;
[0039] Figure 2 This is a flowchart illustrating another optional example of the data protection implementation method proposed in this application.
[0040] Figure 3 This is a flowchart illustrating another optional example of the data protection implementation method proposed in this application.
[0041] Figure 4 This is a flowchart illustrating another optional example of the data protection implementation method proposed in this application.
[0042] Figure 5 This is a schematic diagram of an optional example of the data protection implementation device proposed in this application;
[0043] Figure 6 A schematic diagram of another optional example of the data protection implementation device proposed in this application;
[0044] Figure 7 A schematic diagram of the hardware structure of an optional example of a computer device suitable for implementing the data protection method proposed in this application;
[0045] Figure 8 A schematic diagram of the hardware structure of a computer device for another alternative example of the data protection implementation method proposed in this application. Detailed Implementation
[0046] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0047] Reference Figure 1This is a flowchart illustrating an optional example of the data protection implementation method proposed in this application. This method is applicable to computer devices with hard drives, such as various types of terminal devices. The embodiments of this application can be used to implement encrypted protection of local data on the hard drive of a computer device, improving the flexibility of data protection. Figure 1 As shown, the method may include:
[0048] Step S11: Determine the target file to be encrypted on the hard drive;
[0049] In this embodiment of the application, the target file may be at least part of the hard disk file of the computer device. The target file to be encrypted can be flexibly selected according to the actual data protection requirements to achieve local encryption of the hard disk. This application does not limit the method of determining the target file.
[0050] In some embodiments, the computer device can output the files on the hard drive. The user can use an input device (such as a mouse, keyboard, touch screen, microphone, etc.) to determine the target files to be encrypted on the hard drive based on the input information collected by the device. At this time, the determined target files can be placed in a state of being to be encrypted, such as by adjusting the display status of the target files or configuring the encrypted file identifier, so that the user can intuitively verify whether the determined target files are all files to be encrypted and whether they are complete through the adjusted display status.
[0051] Step S12: Respond to the encryption operation on the target file and obtain the address information of the target file;
[0052] Step S13: Add the address information of the target file to the list of encrypted files on the hard disk, and encrypt the target file stored on the hard disk.
[0053] In this embodiment of the application, in order to meet the flexible encryption requirements of some hard disk files, it is proposed to create an encrypted file list in the hard disk to record the address information of the hard disk files that need to be encrypted, such as the LBA (Logic Block Address) of the hard disk file. In practical applications, this encrypted file list can be used to indicate access control for the hard disk files containing its address information. That is, in scenarios where one or more hard disk files need to be read, written, or updated, when accessing the corresponding hard disk file, the computer device needs to first determine whether the hard disk file to be accessed is encrypted based on the contents of the encrypted file list, thereby determining whether the hard disk file can be directly accessed. The implementation process can be referred to the description of the corresponding part of the following embodiment, and will not be repeated here.
[0054] Based on this, after determining the hard disk file that needs to be encrypted, this application can perform encryption operation on the target file according to the preset encryption operation method. During the encryption operation, the computer device can add the address information of each of the determined target files to the encrypted file list created by the hard disk, and use the hard disk's own encryption method to encrypt the target file so that other devices or applications can access the encrypted target file (hereinafter referred to as the encrypted file). Only after successful hard disk password verification can the encrypted file be accessed and the various processing operations on the encrypted file be completed.
[0055] It should be noted that this application does not restrict the hard drive encryption method. For example, the AES (Advanced Encryption Standard, also known as Rijndael encryption) algorithm built into the hard drive can be used to encrypt the contents of the target file stored on the hard drive, thereby improving the storage security of the target file.
[0056] Therefore, this application can add the address information of selected hard disk files to the list of encrypted files created on the hard disk, and activate its own encryption algorithm to encrypt the contents of these hard disk files, thereby realizing partial hard disk file encryption and improving the flexibility of data protection. Even if the hard disk password is forgotten, the unencrypted hard disk files can still be operated on, meeting application needs. Compared with software data protection methods, which are prone to destroying encrypted data when the hard disk is formatted, this application can still retain the encrypted target files on the hard disk when the hard disk is formatted, further improving the security of hard disk files.
[0057] Reference Figure 2 This is a flowchart illustrating another optional example of the data protection implementation method proposed in this application. This method can be an optional refinement of the data protection implementation method described above, but is not limited to the refinement described in this embodiment. Figure 2 As shown, the method may include:
[0058] Step S21: Determine the target file to be encrypted on the hard drive;
[0059] Step S22: Respond to the encryption shortcut operation performed on the target file in the selected state to obtain the logical block address of the target file;
[0060] In this embodiment of the application, in order to improve the convenience and efficiency of hard disk file encryption operation, the application can pre-configure encryption shortcuts. In this way, the encryption shortcut operation can be performed directly on the determined target file according to the encryption shortcut, which can trigger the computer device to automatically execute step S22 and subsequent processing steps. The application does not limit the implementation method of encryption shortcut operation.
[0061] Optionally, the aforementioned encryption shortcut operations may include, but are not limited to, one or more combinations of specific function key input operations, voice input operations, specific gesture input operations, etc., and can be flexibly selected and configured according to the actual situation. Specific function keys may be physical keys on the input device, such as one or more combination function keys on a keyboard; function keys configured on the computer itself; right-clicking on a target file and selecting from a pop-up encryption prompt window to determine whether to add the target file's address information to the encrypted file list; or virtual keys displayed on the screen.
[0062] Voice input operation can be performed when the target file is selected, with the computer device collecting the user's voice signals related to encrypting the target file, such as "add the target file to the encrypted file list for encryption processing" or "encrypt file". This application does not limit the content of the voice signal input required to perform the voice input operation. Keywords according to step S22 and subsequent encryption processing steps of this application can be pre-configured. In this way, by recognizing the collected voice signal and determining the existence of the preset keywords, subsequent steps can be performed on the selected target file. In another possible implementation, the computer device can also perform semantic recognition on the collected voice signal. If the semantic recognition result indicates that an encryption operation is to be performed on the target file, subsequent steps can be directly executed. This application does not limit the implementation method of the computer device responding to voice input operations.
[0063] Specific gesture input operations can be specific gestures entered by the user on the touch screen of a computer device (such as a terminal device), such as touch trajectories configured for encryption operations, or specific gestures made by the user's hand captured by the camera of the computer device. This application does not limit the implementation method and representation of specific gesture operations, and can be determined as appropriate.
[0064] Step S23: Add the logical block address of the target file to the list of encrypted files created by the firmware of the hard disk;
[0065] In this embodiment, the hard disk can be an HDD (Hard Disk Drive), and its firmware can be software embedded in the hardware of the hard disk, which can be responsible for driving, controlling, decoding, transmitting, and detecting, such as managing the storage location of data, recording the temperature of the hard disk during operation or errors that occur, etc. This application does not limit the type of hard disk or its firmware structure.
[0066] In practical applications, a hard drive password can be pre-configured to encrypt the contents of files on the hard drive. The hard drive firmware creates a list of encrypted files, and this application does not restrict the method by which this list is recorded. As analyzed above, after performing a quick encryption operation on the hard drive file to be encrypted, the logical block address used to access the file can be added to the encrypted file list. This allows the electronic device to directly determine the currently encrypted files on the hard drive by querying the encrypted file list.
[0067] Step S24: Call the hard drive's preset encryption application to encrypt the target file, so as to prevent any application from accessing the target file before decryption.
[0068] According to the method described above, during the process of a computer device responding to an encryption shortcut operation performed on a determined target file, it can call the hard drive's own preset encryption application, such as the AES module listed above. This application does not restrict the encryption algorithm used for hard drive encryption. By activating the preset encryption application, only the target file in the selected state can be encrypted, that is, partial encryption of the hard drive can be achieved, thereby preventing other applications or devices from directly accessing the encrypted target file. In other words, no operation can be performed on the encrypted target file before decryption, such as read / write operations, content update operations, deletion operations, etc., thus achieving data protection in the target file.
[0069] Moreover, the hardware encryption method used in this application enables the protection of local data on the hard drive. Compared with the software-based data protection method for the entire hard drive, even if the hard drive is formatted, this application can prevent the encrypted target file content from being formatted, thus improving the flexibility and reliability of data protection.
[0070] Reference Figure 3 This is a flowchart illustrating another optional example of the data protection implementation method proposed in this application. This embodiment describes the process of accessing encrypted target files on a hard drive, but is not limited to the applicable scenarios of the data protection implementation method described in this embodiment. Figure 3 As shown, the method may include:
[0071] Step S31: Obtain a file processing request for the hard drive;
[0072] The file processing request can be generated by any application on the computer device or by any application on another device (referred to as the second computer device), and is a processing request for one or more hard disk files on the computer device. This processing request can be automatically generated during the application's execution process, or it can be generated in response to a selection and processing operation on at least one hard disk file of the computer device. Optionally, the user can also directly operate the computer device, locate one or more hard disk files on its hard drive (in which case the computer device often only outputs the filename of the hard disk file), perform a double-click or other launch operation on the hard disk file, and generate a file processing request for that hard disk file, etc. This application does not limit the method of generating the above-mentioned file processing request; it can be determined as appropriate.
[0073] In some embodiments, the file name of an encrypted hard disk file can be hidden to further improve file security. In this case, a file identifier with unique characteristics, such as the file name of the hard disk file to be processed, is required to generate a file processing request containing the file identifier. The implementation process is not described in detail in this application.
[0074] Step S32: If the address information of the requested file to be processed is found to be included in the list of encrypted files on the hard disk, the hard disk decryption interface is output.
[0075] It should be understood that file processing requests received by computer devices typically include the address information of the file to be processed, such as logical block addresses. Since the encrypted file list on the hard drive records the address information of all encrypted files on the current hard drive, the address information of the file to be processed is compared with the address information contained in the encrypted file list to determine whether the encrypted file list contains the address information of the file to be processed. If it does, it means that the corresponding file to be processed is an encrypted file, and a hard drive decryption interface for the file to be processed can be output, prompting the user to enter a preset hard drive decryption password. If it does not, it means that the corresponding file to be processed is not encrypted, and the file processing request can be directly executed, processing the file data stored at the address information on the hard drive according to the address information of the file to be processed.
[0076] It should be noted that this application does not limit the implementation method of the hard drive decryption interface output by the computer device. If the computer device has a display screen, the hard drive decryption interface can be directly displayed on the display screen. In this case, the appearance of the hard drive decryption interface can match the preset hard drive password type, such as a hard drive decryption interface with a character input box (for the user to input a character-type hard drive decryption password) and / or a multi-touch dot matrix (for the user to connect the touch points and input a preset graphic-type hard drive decryption password) or a hard drive decryption interface with a touch area (for the user to input a hard drive decryption password), etc., instructing the user to input the corresponding type of hard drive decryption password.
[0077] Optionally, the hard drive decryption password can also be a voice password. In this case, the computer device can output a voice recording interface that instructs the user to input a voice signal as the hard drive decryption interface. The computer device's microphone can be activated to collect or receive voice signals to be verified from other sound acquisition devices. In some embodiments, the hard drive decryption password can be an image password such as a face or fingerprint. The hard drive decryption interface output by the computer device can be a face / fingerprint acquisition interface, and the user can be prompted to enter their face / fingerprint as needed. The output of different types of hard drive decryption interfaces can be determined according to the actual situation, and this application will not provide examples of each type.
[0078] As analyzed above, the computer device can also send a hard disk password entry command to other acquisition devices with hard disk decryption password acquisition function, so that the acquisition device outputs a hard disk decryption interface. After that, the hard disk decryption password acquisition can be completed in accordance with, but not limited to, the method described above. The implementation process will not be described in detail in this application.
[0079] Step S33: In response to the hard disk decryption password entered on the hard disk decryption interface, decrypt the file to be processed stored on the hard disk.
[0080] Step S34: Respond to the file processing request and perform corresponding processing operations on the decrypted file to be processed.
[0081] After obtaining the hard drive decryption password from the hard drive decryption interface, the computer device needs to verify the obtained hard drive decryption password using the preset hard drive password. If the two passwords are the same, the file to be processed stored on the hard drive can be decrypted. Subsequently, the decrypted file to be processed can be processed according to the request processing method.
[0082] It should be understood that the methods for correctly verifying decryption passwords for different types of hard drives often differ. For example, for hard drive decryption passwords with fixed content, such as characters or dot-matrix graphics, the usual method is to verify that the password is exactly the same as the preset hard drive password content to confirm successful decryption. For hard drive decryption passwords containing content such as faces, fingerprints, voice (i.e., voiceprints), or graphics drawn based on blank areas, at least one suitable algorithm from artificial intelligence, such as speech recognition, image processing, machine learning, or deep learning, can be used to perform similarity detection with the preset hard drive password of the corresponding type. If the detected similarity is greater than the similarity threshold (such as 95%, depending on the situation), the two passwords can be considered to have the same content, and the password verification is successful.
[0083] Conversely, if the detected similarity is equal to or less than the similarity threshold, decryption can be considered a failure, and a corresponding prompt message can be output. Alternatively, the user can be allowed to re-enter the hard drive decryption password for verification. If verification fails after a preset number of consecutive attempts, access to the file to be processed by the application or the user can be prohibited for a preset time period. Optionally, if the detected similarity is equal to or less than the similarity threshold, this application can also prompt the user to use other decryption methods for further verification. In this case, multiple hard drive passwords can be pre-configured, with the passwords listed later in the sequence being more complex. The implementation process is not detailed in this application.
[0084] For the decrypted file to be processed, read, write, delete, and update operations can be performed on it, which can be determined according to the actual processing needs. This application does not describe the implementation methods of various processing operations in detail. It should be noted that in the update processing operation of the decrypted file to be processed, since the original content of the file to be processed was previously encrypted, in order to protect the updated file to be processed, the updated file content can be encrypted according to the method described in the above embodiment. If the updated content generates new address information, the new address information can be added to the corresponding position in the encrypted file list, so that subsequent access to the updated file to be processed still requires password verification according to the method described above, and processing can only be performed after successful decryption.
[0085] Based on this, such as Figure 4 As shown, step S34 above may include, but is not limited to, the following implementation steps:
[0086] Step S41: Respond to the file processing request and output the decrypted file to be processed;
[0087] Step S42: Update at least part of the content of the decrypted file to be processed;
[0088] In practical applications, if it is necessary to update the content of an encrypted file on the hard drive, the password verification method described above can be used to successfully decrypt the file by calling the hard drive's own AES algorithm. The decrypted file content can then be output. Users can update the file content by adding, deleting, or modifying it through input devices. The implementation process is not detailed in this application.
[0089] Step S43: Encrypt the updated file content and add the new address information generated by the updated file content to the corresponding position in the encrypted file list.
[0090] According to the file content update method described above, if the updated file content generates new address information, which is different from the address information of the file to be processed before the update, the new address information can be added to the encrypted file list according to the method described above (such as execution based on encryption operation), or the update detection of the address information of the file can be automatically triggered to determine that there is new address information and automatically execute step S43. The implementation process is not described in detail in this application.
[0091] In the process of updating the decrypted file to be processed, some file content may be deleted, making it impossible to find any content based on the address information corresponding to this part of the file content. In order to save space in the encrypted file list and reduce invalid comparison steps of address information, this application can delete the address information corresponding to this part of the deleted file content in the encrypted file list. The deletion process is not described in detail in this application.
[0092] In some other embodiments, the aforementioned processing request for hard disk files can also include operations such as querying the content of encrypted files or deleting encrypted files. For file query requests, after the file to be processed is successfully decrypted, the decrypted content of the queried file can be directly output, such as the entire content of the file to be processed or the content of a specified file. This application does not limit the method of outputting the file content and can determine it according to the file type. For example, for text files, the queried file content can be output through a display screen; for audio files, the decrypted file to be processed can be output through a sound player, etc.
[0093] In some other embodiments, when faced with the desire to delete one or more files on the hard drive, the above-mentioned file processing request can be a file deletion request. In this way, after successful decryption after hard drive password verification, the file deletion request can be responded to directly and the requested file can be deleted. At the same time, the address information of the file to be processed can also be removed from the encrypted file list.
[0094] In some embodiments, for encrypted files on the hard drive, if further encryption is no longer required, the encryption permission settings can be removed. Referring to the encryption operation implementation process described above, this application can pre-configure a quick implementation method for the encryption removal operation, such as one or more combinations of specific function key input operations, voice input operations, or specific gesture input operations. This application does not limit the content of these methods and can be determined as needed. Thus, after the user identifies the encrypted file to be deencrypted on the hard drive, they can perform the encryption removal operation. The computer device can respond to the encryption removal operation by removing (i.e., deleting) the address information of the encrypted file from the encrypted file. Simultaneously, it can invoke a preset encryption application on the hard drive to deencrypt the file (i.e., a file to be processed). This application does not limit the implementation method for removing access permissions related to file encryption.
[0095] Before performing the encryption decryption operation, the encrypted file to be decrypted needs to be password verified according to the method described above. After successful decryption, the encryption decryption operation can be performed to improve data encryption security.
[0096] Based on the descriptions of the above embodiments, for the encrypted file list created by the firmware in the hard disk, in different processing scenarios such as encrypting, deencrypting, updating, and deleting files in the hard disk, the address information corresponding to the processed file content can be added to the encrypted file list or deleted from the encrypted file list. The files that maintain the address information recorded in the encrypted file list are all hard disk encrypted files, thus reliably protecting such hard disk file data.
[0097] Reference Figure 5 This is a schematic diagram of an optional example of the data protection implementation device proposed in this application. This device can be used to flexibly protect at least a portion of the file data on a hard disk, such as... Figure 5 As shown, the device may include:
[0098] The target file determination module 51 is used to determine the target file to be encrypted in the hard disk; the target file is at least a portion of the hard disk file.
[0099] Address information acquisition module 52 is used to obtain the address information of the target file in response to an encryption operation on the target file.
[0100] The encryption processing module 53 is used to add the address information of the target file to the encrypted file list created by the firmware of the hard disk, and to encrypt the target file stored on the hard disk.
[0101] The encrypted file list is used to indicate access control for the hard disk files containing the address information. In this embodiment, the encrypted file list can be created and maintained by the firmware of the hard disk, and the implementation process will not be described in detail in this application.
[0102] In some embodiments, such as Figure 6 As shown, the address information acquisition module 52 may include:
[0103] The logical block address acquisition unit 521 is used to obtain the logical block address of the target file in response to an encryption shortcut operation performed on the target file in the selected state.
[0104] The encrypted shortcut operation includes one or more combinations of specific function key input operations, voice input operations, and specific gesture input operations.
[0105] Optional, such as Figure 6 As shown, the encryption processing module 53 described above may include:
[0106] The encrypted logical block address recording unit 531 is used to add the logical block address of the target file to the encrypted file list in the hard disk;
[0107] The encryption unit 532 is used to call the preset encryption application of the hard disk to encrypt the target file, so as to prevent any application from accessing the target file before decryption.
[0108] In some other embodiments, such as Figure 6 As shown, the above-mentioned device may further include:
[0109] File processing request acquisition module 54 is used to acquire file processing requests for the hard disk;
[0110] The hard disk decryption interface output module 55 is used to detect that the address information of the requested file to be processed is included in the encrypted file list, and output the hard disk decryption interface.
[0111] The decryption processing module 56 is used to decrypt the file to be processed stored on the hard disk in response to the hard disk decryption password input to the hard disk decryption interface;
[0112] The file processing module 57 is used to respond to the file processing request and perform corresponding processing operations on the decrypted file to be processed.
[0113] In one possible implementation, the file processing module 57 described above may include:
[0114] The request response unit is used to respond to the file processing request and update, delete, or query at least part of the content of the decrypted file to be processed.
[0115] An update data processing unit is used to encrypt the updated file content and add the new address information generated by the updated file content to the corresponding position in the encrypted file list;
[0116] The file output unit is used to output the content of the file queried in the decrypted file to be processed.
[0117] In yet another possible implementation, the file processing module 57 may further include:
[0118] The encryption decryption unit is used to respond to the encryption decryption operation of the decrypted file to be processed, remove the address information of the file to be processed from the encrypted file list, and decrypt the file to be processed.
[0119] It should be noted that the various modules and units in the above-mentioned device embodiments can all be stored in the memory as program modules. The processor executes the above-mentioned program modules stored in the memory to realize the corresponding functions. The functions realized by each program module and its combination, as well as the technical effects achieved, can be referred to the description of the corresponding part of the above-mentioned method embodiments. This embodiment will not repeat them here.
[0120] This application also provides a computer-readable storage medium on which a computer program can be stored, which can be invoked and loaded by a processor to implement the various steps of the data protection implementation method described in the above embodiments.
[0121] Reference Figure 7 This is a schematic diagram of the hardware structure of an optional example of a computer device applicable to the data protection implementation method proposed in this application. The computer device can be a terminal device or a service device. The terminal device can be an electronic device such as a smartphone, tablet computer, wearable device, augmented reality (AR) device, virtual reality (VR) device, robot, smart medical device, smart transportation device, smart home device, desktop computer, etc. The service device can be a physical server, a service cluster composed of multiple physical servers, or a cloud server with cloud computing capabilities. The service device can communicate and connect with the terminal device through a wired network or wireless network to meet the data transmission requirements. The implementation process can be determined according to the scenario, and will not be described in detail here.
[0122] This application uses a computer device as an example for illustration, such as... Figure 7As shown, the computer device may include at least one memory 71, at least one processor 72, and at least one communication interface 73, wherein:
[0123] The memory 71, processor 72, and communication interface 73 can all be connected to the communication bus in the computer device to realize data transmission between them. This application does not describe in detail the communication connection methods between the various components within the computer device, which can be determined as needed. In this application, the memory 71 includes a hard disk 711 for storing multiple files. This application does not limit the file types. In practical applications, the hard disk 711 may include, but is not limited to, the aforementioned HDD. Depending on the data storage and processing capabilities required by the computer device, a suitable type of hard disk 711 can be selected, such as a solid-state drive (SSD). This application does not impose any restrictions on this.
[0124] The memory 71 can be used to store a program that implements the data protection implementation method described in the above method embodiments; the processor 72 can load and execute the program stored in the memory 72 to implement each step of the data protection implementation method described in the above corresponding method embodiments. The specific implementation process can be referred to the description of the corresponding part of the above embodiments, and will not be repeated in the embodiments of this application.
[0125] In this embodiment, memory 71 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device or other volatile solid-state storage device. Processor 73 may be a central processing unit (CPU), application-specific integrated circuit (ASIC), digital signal processor (DSP), application-specific integrated circuit (ASIC), off-the-shelf programmable gate array (FPGA), or other programmable logic device. This application does not limit the structure and model of the memory 71 and processor 72 described above, and they can be flexibly adjusted according to actual needs.
[0126] The communication interface 73 may include a first data interface of a communication module that enables data interaction via a wireless communication network, enabling communication connection with external devices, and a second data interface that enables data interaction between internal components of the computer device and wired connection to external devices, such as a USB interface, serial / parallel port, multimedia interface, etc. The communication module containing the first data interface may include, but is not limited to, a WIFI module, a 5G / 6G (fifth generation mobile communication network / sixth generation mobile communication network) module, a GPRS module, a GSM module, a near field communication module, etc. This application does not limit the number and type of communication interfaces 73 included in the computer device.
[0127] It should be understood that, Figure 7 The structure of the computer device shown does not constitute a limitation on the computer device in the embodiments of this application. In practical applications, the computer device may include more than Figure 7 The number of more or fewer components shown, or the combination of certain components, such as Figure 8 As shown, the computer device may also include at least one input component such as a touch sensing unit for sensing touch events on a touch display panel, a keyboard, a mouse, a camera, a microphone, etc.; at least one output component such as a monitor, a speaker, a vibration mechanism, a lamp, etc.; an antenna; a sensor module; a power supply module, etc. Figure 8 The input and output components listed are not shown. The hardware structure can be determined according to the type of computer equipment and its functional requirements. They are not listed here.
[0128] Finally, it should be noted that, regarding the above embodiments, unless the context explicitly indicates an exception, the words "a," "an," "an," and / or "the" do not specifically refer to the singular and may also include the plural. Generally speaking, the terms "comprising" and "including" only indicate the inclusion of explicitly identified steps and elements, and these steps and elements do not constitute an exclusive list; the method or apparatus may also include other steps or elements. An element defined by the phrase "comprising an..." does not exclude the presence of other identical elements in the process, method, product, or apparatus that includes the element.
[0129] In the description of the embodiments of this application, unless otherwise stated, " / " means "or", for example, A / B can mean A or B; "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more.
[0130] The terms used in this application, such as "first" and "second," are for descriptive purposes only, used to distinguish one operation, unit, or module from another, and do not necessarily require or imply any such actual relationship or order between these units, operations, or modules. Furthermore, they should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include one or more of that feature.
[0131] Furthermore, flowcharts are used in this application to illustrate the operations performed by a computer device according to embodiments of this application. It should be understood that the preceding or following operations are not necessarily performed precisely in sequence. Instead, the steps can be processed in reverse order or simultaneously. Additionally, other operations can be added to these processes, or one or more steps can be removed from them.
[0132] Furthermore, the various embodiments in this specification are described in a progressive or parallel manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus, computer device, and storage medium disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple, and relevant parts can be referred to the method section.
[0133] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A data protection implementation method, the method comprising: Identify the target file to be encrypted on the hard drive; The target file is at least a portion of a hard disk file; In response to the encryption operation on the target file, obtain the logical block address of the target file; The logical block address of the target file is added to the encrypted file list created and maintained by the firmware of the hard disk, and the preset encryption application of the hard disk is invoked to encrypt the target file, so as to prevent any application from accessing the target file before decryption; The encrypted file list is used to indicate access control for the hard disk files containing the logical block addresses.
2. The method according to claim 1, further comprising: Obtain a file processing request for the hard disk; If the logical block address of the requested file is found to be included in the encrypted file list, the hard disk decryption interface is output. In response to the hard drive decryption password entered on the hard drive decryption interface, the file to be processed stored on the hard drive is decrypted; In response to the file processing request, perform corresponding processing operations on the decrypted file to be processed.
3. The method according to claim 2, wherein responding to the file processing request and performing corresponding processing operations on the decrypted file to be processed includes: In response to the file processing request, at least part of the content of the decrypted file to be processed is updated, deleted, or queried. The updated file content is encrypted, and the new address information generated by the updated file content is added to the corresponding position in the encrypted file list; Output the contents of the file queried in the decrypted file to be processed.
4. The method according to claim 2, wherein responding to the file processing request and performing corresponding processing operations on the decrypted file to be processed includes: In response to the encryption decryption operation on the decrypted file to be processed, the logical block address of the file to be processed is removed from the encrypted file list, and the encryption operation on the file to be processed is decrypted.
5. The method according to claim 1, wherein obtaining the logical block address of the target file in response to an encryption operation on the target file includes: In response to an encrypted shortcut operation performed on the target file in the selected state, the logical block address of the target file is obtained; The encrypted shortcut operation includes one or more combinations of specific function key input operations, voice input operations, and specific gesture input operations.
6. A data protection implementation device, the device comprising: The target file determination module is used to determine the target file to be encrypted on the hard drive; The target file is at least a portion of a hard disk file; The address information acquisition module is used to respond to the encryption operation on the target file and obtain the logical block address of the target file. The encryption processing module is used to add the logical block address of the target file to the encrypted file list created and maintained by the firmware of the hard disk, and call the preset encryption application of the hard disk to encrypt the target file so as to prevent any application from accessing the target file before decryption; The encrypted file list is used to indicate access control on the hard disk file containing logical block addresses.
7. A computer device, comprising: a memory for storing a program for implementing the data protection implementation method according to any one of claims 1-5, and the memory comprises a hard disk for storing a plurality of files, a processor for loading and executing the program stored in the memory, to implement the data protection implementation method according to any one of claims 1-5.
8. A storage medium having a computer program stored thereon, the computer program being loaded and executed by a processor to implement the data protection implementation method according to any one of claims 1-5.
Citation Information
Patent Citations
Hard disk encrypting method and operation system
CN103530581A
File encryption method, terminal and computer readable storage medium
CN107886002A