Password application management method and device, equipment, medium and program product
By collecting, classifying, and standardizing the logs of various cryptographic devices in the cryptographic system, the actual operating cryptographic scheme was determined and compared with the reported scheme. This solved the problem of inaccurate application supervision data analysis results, achieved the accuracy and real-time nature of log data, and ensured the effectiveness of supervision.
Patent Information
- Application Number
- CN202511719087.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-21
- Publication Date
- 2026-02-17
AI Technical Summary
In existing technologies, the data analysis results of application supervision are not accurate enough because the real-time nature of the offline reported log lists is not strong, making it difficult to guarantee accuracy and distinguish between true and false information.
By collecting call logs and operation logs of various cryptographic devices in the cryptographic system, classifying and standardizing them, the actual cryptographic schemes of the supervised applications are determined, and compared with the reported cryptographic schemes, and the comparison results are recorded.
This ensures the accuracy and real-time nature of log data, guarantees the accuracy of data analysis results for application monitoring, and enables timely detection of inconsistencies between reported and actual usage plans.
Smart Images
Figure CN121543078A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular to a cryptographic application management method, apparatus, device, medium, and program product. Background Technology
[0002] Because applications are dynamically updated, the competent authorities need to dynamically supervise the cryptographic products and services used by each application. Currently, relevant responsible units are required to regularly submit a list of security device usage logs to the competent authorities, who then conduct data analysis on these logs to confirm whether the cryptographic products and services actually used by each application meet security requirements. However, because offline log submissions lack real-time updates and the authenticity of log content is difficult to verify, the accuracy of the data analysis results for application supervision is hard to guarantee.
[0003] Therefore, how to improve the accuracy of data analysis results in application supervision is a problem that needs to be solved by those skilled in the art. Summary of the Invention
[0004] In view of this, the purpose of this application is to provide a method, apparatus, device, medium, and program product for cryptographic application management, so as to improve the accuracy of data analysis results for application supervision. The specific solution is as follows:
[0005] Firstly, this application provides a cryptographic application management method, including:
[0006] Collect the call logs and operation logs of each cryptographic device in the cryptographic system to obtain the logs to be processed;
[0007] The log fields in the logs to be processed are classified and standardized to obtain the target data;
[0008] Based on the target data, determine the actual operating cryptographic scheme of the supervised application using the cryptographic system;
[0009] The actual running password scheme is compared with the reported password scheme of the supervised application, and the comparison results are recorded.
[0010] Optionally, call logs and operation logs of each cryptographic device in the cryptographic system are collected, including:
[0011] The system collects call logs and operation logs of each cryptographic device in the cryptographic system using at least one protocol; the at least one protocol includes: Syslog, snmp, TCP, UDP, HTTP, Elasticsearch and / or Kafka.
[0012] Optionally, the log fields in the logs to be processed are classified and standardized, including:
[0013] Determine the classification labels; the classification labels include: cryptographic device type, cryptographic service type, supported protocol type and / or supported network environment characteristics;
[0014] The log fields in the logs to be processed are classified according to the classification labels to obtain the classification results;
[0015] Convert each field in the classification results into readable characters;
[0016] Map the readable characters to regulatory fields.
[0017] Optionally, the fields in the classification results are converted into readable characters, including:
[0018] The fields in the classification results are cleaned, completed, and / or their proprietary characters are converted, and then uniformly converted into JSON format.
[0019] Optionally, determining the actual operating cryptographic scheme of the regulated application using the cryptographic system based on the target data includes:
[0020] Query the summary table of regulated applications to identify at least one regulated application using the cryptographic system;
[0021] Query the actual password behavior field of the at least one monitored application in the target data;
[0022] The actual operating password scheme of the at least one regulated application is generated based on the actual password behavior field.
[0023] Optionally, the actual cryptographic behavior field includes: cryptographic service type, cumulative number of calls and / or information on each call; the cryptographic service type includes: encryption, decryption, key generation, digest generation, signature and / or signature verification.
[0024] Optionally, if the comparison results confirm that the reported password scheme of any regulated application is inconsistent with the actual operating password scheme, the inconsistency information is recorded and the regulated application is marked as pending verification.
[0025] Secondly, this application provides a cryptographic application management device, comprising:
[0026] The collection module is used to collect the call logs and operation logs of each cryptographic device in the cryptographic system to obtain logs to be processed.
[0027] The processing module is used to classify and standardize the log fields in the log to be processed to obtain the target data;
[0028] The determination module is used to determine the actual operating cryptographic scheme of the supervised application using the cryptographic system based on the target data;
[0029] The comparison module is used to compare the actual running password scheme with the reported password scheme of the monitored application and record the comparison results.
[0030] Optionally, the collection module is specifically used for:
[0031] The system collects call logs and operation logs of each cryptographic device in the cryptographic system using at least one protocol; the at least one protocol includes: Syslog, snmp, TCP, UDP, HTTP, Elasticsearch and / or Kafka.
[0032] Optionally, the processing module is specifically used for:
[0033] Determine the classification labels; the classification labels include: cryptographic device type, cryptographic service type, supported protocol type and / or supported network environment characteristics;
[0034] The log fields in the logs to be processed are classified according to the classification labels to obtain the classification results;
[0035] Convert each field in the classification results into readable characters;
[0036] Map the readable characters to regulatory fields.
[0037] Optionally, the processing module is specifically used for:
[0038] The fields in the classification results are cleaned, completed, and / or their proprietary characters are converted, and then uniformly converted into JSON format.
[0039] Optionally, the module is specifically used for:
[0040] Query the summary table of regulated applications to identify at least one regulated application using the cryptographic system;
[0041] Query the actual password behavior field of the at least one monitored application in the target data;
[0042] The actual operating password scheme of the at least one regulated application is generated based on the actual password behavior field.
[0043] Optionally, the actual cryptographic behavior field includes: cryptographic service type, cumulative number of calls and / or information on each call; the cryptographic service type includes: encryption, decryption, key generation, digest generation, signature and / or signature verification.
[0044] Optionally, it also includes: a recording module, used to record inconsistency information and mark the monitored application as pending verification if it is confirmed based on the comparison result that the reported password scheme of any monitored application is inconsistent with the actual operating password scheme.
[0045] Thirdly, this application provides an electronic device, comprising:
[0046] Memory, used to store computer programs;
[0047] A processor is used to execute the computer program to implement the aforementioned disclosed cryptographic application management method.
[0048] Fourthly, this application provides a readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the aforementioned disclosed cryptographic application management method.
[0049] Fifthly, this application provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the aforementioned disclosed cryptographic application management method.
[0050] As can be seen from the above scheme, this application provides a cryptographic application management method, including: collecting call logs and operation logs of each cryptographic device in the cryptographic system to obtain logs to be processed; classifying and standardizing the log fields in the logs to be processed to obtain target data; determining the actual running cryptographic scheme of the supervised application using the cryptographic system based on the target data; comparing the actual running cryptographic scheme with the reported cryptographic scheme of the supervised application, and recording the comparison results.
[0051] As can be seen, this application collects call logs and operation logs from various cryptographic devices in the cryptographic system to obtain logs to be processed. Then, the log fields in these logs are classified and standardized. Based on this result, the actual cryptographic scheme used by the supervised application using the cryptographic system is determined. Finally, the actual cryptographic scheme is compared with the reported cryptographic scheme of the supervised application. Based on the comparison results, it can be confirmed whether the actual cryptographic scheme of the supervised application is consistent with its reported cryptographic scheme, thereby confirming whether the cryptographic products and services actually used by the supervised application meet security requirements. This scheme directly collects log data from each cryptographic device, ensuring the accuracy and real-time nature of the log data, thus guaranteeing the accuracy of the data analysis results for application supervision.
[0052] Correspondingly, the cryptographic application management device, equipment, medium, and program product provided in this application also have the above-mentioned technical effects.
[0053] Other features and advantages of this application will be described in detail in the following detailed description section. Attached Figure Description
[0054] 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.
[0055] Figure 1 This is a flowchart illustrating a cryptographic application management method according to an exemplary embodiment;
[0056] Figure 2 This is a schematic diagram of a cryptographic application management system according to an exemplary embodiment;
[0057] Figure 3 This is a schematic diagram of a cryptographic application management device according to an exemplary embodiment;
[0058] Figure 4 This is a schematic diagram of an electronic device according to an exemplary embodiment;
[0059] Figure 5 This is a schematic diagram of another electronic device according to an exemplary embodiment;
[0060] Figure 6 This is a schematic diagram of yet another electronic device according to an exemplary embodiment. Detailed Implementation
[0061] 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.
[0062] Currently, relevant responsible units are required to regularly submit a list of security device usage logs to the competent authority, which then conducts data analysis on these logs to confirm whether the cryptographic products and services actually used by each application meet security requirements. However, offline log submissions lack real-time updates, and the authenticity of log content is difficult to verify, making it challenging to guarantee the accuracy of application monitoring data analysis results. Therefore, this application provides a cryptographic application management solution that can directly collect log data from various cryptographic devices, ensuring the accuracy and real-time nature of the log data, thereby guaranteeing the accuracy of application monitoring data analysis results.
[0063] See Figure 1 As shown in an exemplary embodiment, this application discloses a cryptographic application management method, including:
[0064] S101. Collect the call logs and operation logs of each cryptographic device in the cryptographic system to obtain the logs to be processed.
[0065] In this embodiment, the cryptographic system can provide various cryptographic services such as encryption, decryption, key generation, digest generation, signing, and / or signature verification. Specifically, it can include various types of cryptographic devices such as signature servers, cryptographic computation servers, and key management servers. That is to say, each cryptographic device can be a signature server, a cryptographic computation server, and a key management server, etc.
[0066] It should be noted that call logs generally include information related to various cryptographic services called by the application, such as encryption, decryption, key generation, digest generation, signing, and / or signature verification, including call time and cumulative call count. Operation logs generally include information related to the daily operation of cryptographic devices, such as CPU utilization, memory usage, and real-time bandwidth. This embodiment aggregates the call logs and operation logs of each cryptographic device into a pending log.
[0067] To ensure the comprehensiveness of log collection, this embodiment provides a dedicated device to communicate with each cryptographic device in the cryptographic system. The communication protocol used can be Syslog, snmp, TCP, UDP, HTTP, Elasticsearch, and / or Kafka. Therefore, in one implementation, collecting the call logs and runtime logs of each cryptographic device in the cryptographic system includes: collecting the call logs and runtime logs of each cryptographic device in the cryptographic system through at least one protocol; the at least one protocol includes: Syslog, snmp, TCP, UDP, HTTP, Elasticsearch, and / or Kafka.
[0068] S102. Classify and standardize the log fields in the log to be processed to obtain the target data.
[0069] Considering that different cryptographic devices may use different record formats for time fields, the same cryptographic field, the same cryptographic algorithm, etc., this embodiment performs standardization processing such as cleaning, completion, and conversion on the log fields in the log to be processed, and classifies these fields according to classification labels. Classification can be performed first and then standardization, or standardization can be performed first and then classification. In one implementation, classifying and standardizing the log fields in the log to be processed includes: determining classification labels; classification labels include: cryptographic device type, cryptographic service type, supported protocol type, and / or supported network environment characteristics; classifying the log fields in the log to be processed according to the classification labels to obtain classification results; converting each field in the classification results into readable characters; and mapping the readable characters to regulatory fields. Converting each field in the classification results into readable characters includes: cleaning, completing, and / or converting proprietary characters in each field in the classification results, and uniformly converting them to JSON format. Network environment characteristics include: intranet, extranet, network bandwidth, etc.
[0070] S103. Determine the actual operating cryptographic scheme of the regulated application using the cryptographic system based on the target data.
[0071] Generally, application identification information such as the name of the regulated application is pre-recorded in a summary table of regulated applications. By looking up this table, each regulated application calling the relevant cryptographic services of the cryptographic system can be identified. Of course, the collected log data will also include application identification information such as the name of each regulated application actually calling the relevant cryptographic services of the cryptographic system. In one implementation, determining the actual cryptographic scheme used by the regulated application using the cryptographic system based on target data includes: querying the summary table of regulated applications to identify at least one regulated application using the cryptographic system; querying the actual cryptographic behavior field of at least one regulated application in the target data; and generating the actual cryptographic scheme of at least one regulated application based on the actual cryptographic behavior field. The actual cryptographic behavior field includes: cryptographic service type, cumulative number of calls, and / or information on each call; the cryptographic service type includes: encryption, decryption, key generation, digest generation, signing, and / or signature verification.
[0072] S104. Compare the actual operating cryptographic scheme with the reported cryptographic scheme of the supervised application and record the comparison results.
[0073] If the comparison results confirm that the reported password scheme of any regulated application is consistent with the actual operating password scheme, the regulated application is marked as having passed the verification. If the comparison results confirm that the reported password scheme of any regulated application is inconsistent with the actual operating password scheme, the inconsistency information is recorded, and the regulated application is marked as pending verification.
[0074] As can be seen, this embodiment collects call logs and operation logs from various cryptographic devices in the cryptographic system to obtain logs to be processed. Then, the log fields in these logs are classified and standardized. Based on this result, the actual cryptographic scheme used by the supervised application using the cryptographic system is determined. Finally, the actual cryptographic scheme is compared with the reported cryptographic scheme of the supervised application. Based on the comparison results, it can be confirmed whether the actual cryptographic scheme of the supervised application is consistent with its reported cryptographic scheme, thereby confirming whether the cryptographic products and services actually used by the supervised application meet security requirements. This scheme directly collects log data from each cryptographic device, ensuring the accuracy and real-time nature of the log data, thus guaranteeing the accuracy of the data analysis results for application supervision.
[0075] In one example, the log fields in the log to be processed can be found in Table 1.
[0076] Table 1
[0077]
[0078] Please see Figure 2 The competent authority's system connects to the signature server, cryptographic calculation server, and key management server in the cryptographic system. Applications within application system A call the signature service from the signature server, applications within application system B call the cryptographic calculation service from the cryptographic calculation server, and applications within application system C call the key management service from the key management server.
[0079] Specifically, the competent authority collects call logs and operation logs from the signature server, cryptographic calculation server, and key management server. These log fields undergo cleaning, formatting, transformation, and standardization to ensure they are recorded in JSON format, ultimately yielding standardized log data. The transformation typically involves converting algorithm identifiers into readable, uniform characters. It also considers the minimum regulatory requirements, such as clearly defining the specific steps of key generation and the execution timestamps for each step. Therefore, the specific steps of key generation and the execution timestamps for each step are identified through analysis of the log data.
[0080] Generally, encryption / decryption services focus more on the number of encryption / decryption attempts and algorithm names; key management services focus more on the number of keys generated and the generation strategy; and signature verification services focus more on the number of signature verification attempts and whether the verification passed. The competent authority's system supports multiple protocols such as Syslog, snmp, TCP, UDP, HTTP, Elasticsearch, and Kafka, and log collection can be performed using at least one of these protocols.
[0081] Furthermore, the log fields in the collected log data can be classified and tagged according to labels such as cryptographic device type, cryptographic service type, collection protocol type, and network environment characteristics. Cryptographic service types include: encryption, decryption, key generation, digest generation, signature and / or signature verification.
[0082] Standardized log data is transmitted to the competent authority's system, where it is analyzed and processed. For example, the system determines the actual cryptographic scheme used by the regulated applications, compares the actual scheme with the reported scheme, and verifies whether the applications are correctly using cryptographic algorithms and whether there are any vulnerabilities. This provides a more convenient and comprehensive means of supervising commercial cryptographic applications.
[0083] The following describes a cryptographic application management device provided in an embodiment of this application. The cryptographic application management device described below and the cryptographic application management method described above can be referred to each other.
[0084] See Figure 3 As shown in an exemplary embodiment, this application discloses a cryptographic application management device, including:
[0085] The collection module is used to collect the call logs and operation logs of each cryptographic device in the cryptographic system to obtain logs to be processed.
[0086] The processing module is used to classify and standardize the log fields in the logs to be processed, so as to obtain the target data;
[0087] The determination module is used to determine the actual operating cryptographic scheme of the supervised application using the cryptographic system based on the target data.
[0088] The comparison module is used to compare the actual running cryptographic scheme with the reported cryptographic scheme of the supervised application and record the comparison results.
[0089] In one implementation, the collection module is specifically used for:
[0090] The system collects call logs and runtime logs of each cryptographic device in the cryptographic system using at least one protocol; at least one protocol includes: Syslog, snmp, TCP, UDP, HTTP, Elasticsearch and / or Kafka.
[0091] In one implementation, the processing module is specifically used for:
[0092] Determine the classification labels; the classification labels include: cryptographic device type, cryptographic service type, supported protocol type and / or supported network environment characteristics;
[0093] The log fields in the logs to be processed are classified according to the classification labels to obtain the classification results;
[0094] Convert the fields in the classification results into readable characters;
[0095] Map readable characters to regulatory fields.
[0096] In one implementation, the processing module is specifically used for:
[0097] Clean, complete, and / or convert proprietary characters in each field of the classification results, and then convert them into JSON format.
[0098] In one implementation, the determining module is specifically used for:
[0099] Query the summary table of regulated applications to identify at least one regulated application that uses a cryptographic system;
[0100] Query at least one field in the target data representing the actual password behavior of the monitored application;
[0101] Generate at least one actual running password scheme for the regulated application based on the actual password behavior field.
[0102] In one implementation, the actual cryptographic behavior field includes: cryptographic service type, cumulative number of calls and / or information on each call; the cryptographic service type includes: encryption, decryption, key generation, digest generation, signature and / or signature verification.
[0103] In one implementation, it further includes a recording module, configured to record inconsistency information and mark the monitored application as pending verification if, based on the comparison results, it is confirmed that the reported password scheme of any monitored application is inconsistent with the actual operating password scheme.
[0104] For more detailed information on the working process of each module and unit in this embodiment, please refer to the relevant content disclosed in the foregoing embodiments, which will not be repeated here.
[0105] As can be seen, this embodiment provides a cryptographic application management device that can directly collect log data from various cryptographic devices, ensuring the accuracy and real-time nature of the log data, thereby guaranteeing the accuracy of the data analysis results for application monitoring.
[0106] The following describes an electronic device provided in an embodiment of this application. The electronic device described below can be referred to in conjunction with the cryptographic application management method and apparatus described above.
[0107] See Figure 4As shown in an exemplary embodiment, this application discloses an electronic device, including:
[0108] Memory 401 is used to store computer programs;
[0109] Processor 402 is configured to execute the computer program to implement the method disclosed in any of the above embodiments.
[0110] Figure 5 This is a block diagram illustrating an electronic device 500 according to an exemplary embodiment. For example... Figure 5 As shown, the electronic device 500 may include a processor 501 and a memory 502. The electronic device 500 may also include one or more of a multimedia component 503, an input / output (I / O) interface 504, and a communication component 505.
[0111] The processor 501 controls the overall operation of the electronic device 500 to complete all or part of the steps in the aforementioned password application management method. The memory 502 stores various types of data to support the operation of the electronic device 500. This data may include, for example, instructions for any application or method operating on the electronic device 500, and application-related data such as contact data, sent and received messages, pictures, audio, video, etc. The memory 502 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The multimedia component 503 may include a screen and audio components. The screen may be, for example, a touchscreen, and the audio component is used to output and / or input audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signals may be further stored in memory 502 or transmitted via communication component 505. The audio component also includes at least one speaker for outputting audio signals. I / O interface 504 provides an interface between processor 501 and other interface modules, such as a keyboard, mouse, buttons, etc. These buttons may be virtual or physical buttons. Communication component 505 is used for wired or wireless communication between the electronic device 500 and other devices. Wireless communication may include Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G, or 4G, or a combination thereof; therefore, the corresponding communication component 505 may include a Wi-Fi module, a Bluetooth module, or an NFC module.
[0112] In an exemplary embodiment, the electronic device 500 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the XXXX method described above.
[0113] In another exemplary embodiment, a computer-readable storage medium including program instructions is also provided, which, when executed by a processor, implement the steps of the cryptographic application management method described above. For example, the computer-readable storage medium may be the memory 502 including the program instructions described above, which may be executed by the processor 501 of the electronic device 500 to complete the cryptographic application management method described above.
[0114] Figure 6 This is a block diagram illustrating an electronic device 600 according to an exemplary embodiment. For example, the electronic device 600 may be provided as a server. (Refer to...) Figure 6 The electronic device 600 includes a processor 622, which may be one or more, and a memory 632 for storing computer programs executable by the processor 622. The computer program stored in the memory 632 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processor 622 may be configured to execute the computer program to perform the aforementioned cryptographic application management method.
[0115] Additionally, the electronic device 600 may also include a power supply component 626 and a communication component 650. The power supply component 626 can be configured to perform power management of the electronic device 600, and the communication component 650 can be configured to enable communication of the electronic device 600, such as wired or wireless communication. Furthermore, the electronic device 600 may also include an input / output (I / O) interface 658. The electronic device 600 can operate on an operating system stored in memory 632, such as Windows Server™, Mac OSX™, Unix™, Linux™, etc.
[0116] In another exemplary embodiment, a computer-readable storage medium including program instructions is also provided, which, when executed by a processor, implement the steps of the cryptographic application management method described above. For example, the computer-readable storage medium may be the memory 632 including the program instructions, which may be executed by the processor 622 of the electronic device 600 to complete the cryptographic application management method described above.
[0117] The following describes a readable storage medium provided in an embodiment of this application. The readable storage medium described below can be referred to in conjunction with the cryptographic application management method, apparatus and device described above.
[0118] A readable storage medium is provided for storing a computer program, wherein the computer program, when executed by a processor, implements the cryptographic application management method disclosed in the foregoing embodiments. Specific steps of this method can be found in the corresponding content disclosed in the foregoing embodiments, and will not be repeated here.
[0119] The following describes a computer program product provided by an embodiment of this application. The computer program product described below can be referred to in conjunction with other embodiments described herein.
[0120] A computer program product includes a computer program / instructions that, when executed by a processor, implement the steps of the aforementioned disclosed cryptographic application management method.
[0121] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium for storing a computer program that, when executed by a processor, implements the steps in any of the above embodiments.
[0122] The preferred embodiments of this application have been described in detail above with reference to the accompanying drawings. However, this application is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this application, various simple modifications can be made to the technical solution of this application, and these simple modifications all fall within the protection scope of this application.
[0123] It should also be noted that the various specific technical features described in the above embodiments can be combined in any suitable manner without contradiction. To avoid unnecessary repetition, this application will not describe the various possible combinations separately.
[0124] Furthermore, various different implementations of this application can be combined in any way, as long as they do not violate the spirit of this application, they should also be regarded as the content disclosed in this application.
Claims
1. A cryptographic application management method characterized by, The method comprises the following steps: Collecting the calling log and the running log of each cryptographic device in a cryptographic system to obtain a to-be-processed log; Classifying and standardizing the log fields in the to-be-processed log to obtain target data; Determining an actual running cryptographic scheme of a supervised application program using the cryptographic system according to the target data; Comparing the actual running cryptographic scheme with a reported cryptographic scheme of the supervised application program and recording a comparison result.
2. The password application management method according to claim 1, characterized by, The collecting of the calling log and the running log of each cryptographic device in a cryptographic system comprises the following steps: Collecting the calling log and the running log of each cryptographic device in a cryptographic system through at least one protocol; the at least one protocol comprises Syslog, snmp, TCP, UDP, HTTP, Elasticsearch and / or Kafka.
3. The password application management method according to claim 1, characterized by, The classifying and standardizing of the log fields in the to-be-processed log comprises the following steps: Determining a classification label; the classification label comprises a cryptographic device type, a cryptographic service type, a supported protocol type and / or a supported network environment feature; Classifying the log fields in the to-be-processed log according to the classification label to obtain a classification result; Converting each field in the classification result into a readable character; Mapping the readable character to a supervision field.
4. The password application management method according to claim 3, characterized by, The converting of each field in the classification result into a readable character comprises the following steps: Cleaning, completing and / or converting a special character of each field in the classification result, and uniformly converting the field into a JSON format.
5. The password application management method according to claim 1, characterized by, The determining of an actual running cryptographic scheme of a supervised application program using the cryptographic system according to the target data comprises the following steps: Querying a supervised application program summary table to determine at least one supervised application program using the cryptographic system; Querying an actual cryptographic behavior field of the at least one supervised application program in the target data; Generating an actual running cryptographic scheme of the at least one supervised application program based on the actual cryptographic behavior field.
6. The password application management method according to claim 5, characterized by, The actual cryptographic behavior field comprises a cryptographic service type, a cumulative calling number and / or each calling information; the cryptographic service type comprises encryption, decryption, key generation, digest generation, signature and / or signature verification.
7. The password application management method according to any one of claims 1 to 6, characterized by, The method further comprises the following steps: If it is confirmed that the reported cryptographic scheme of any supervised application program is inconsistent with the actual running cryptographic scheme based on the comparison result, recording inconsistent information and marking the supervised application program as to-be-checked.
8. A cryptographic application management apparatus characterized by comprising: The method comprises the following steps: A collecting module is configured to collect the calling log and the running log of each cryptographic device in a cryptographic system to obtain a to-be-processed log; A processing module is configured to classify and standardize the log fields in the to-be-processed log to obtain target data; A determining module is configured to determine an actual running cryptographic scheme of a supervised application program using the cryptographic system according to the target data; A comparison module is configured to compare the actual running cryptographic scheme with a reported cryptographic scheme of the supervised application program and record a comparison result.
9. An electronic device, comprising: The method comprises the following steps: A memory is configured to store a computer program; A processor is configured to execute the computer program to implement the cryptographic application management method according to any one of claims 1 to 7.
10. A readable storage medium, characterized by, A computer program product for saving a computer program, wherein the computer program, when executed by a processor, implements the cryptographic application management method according to any one of claims 1 to 7.
11. A computer program product comprising computer programs / instructions, characterized in that, The computer program / instructions, when executed by a processor, implement the method according to any one of claims 1 to 7.