On June 18, 2026, the Cyberspace Administration of China, the Ministry of Industry and Information Technology and the Ministry of Public Security jointly promulgated the Measures for Network Data Security Risk Assessment (hereinafter referred to as the "Measures"), which will take effect on August 20, 2026.
This is not an isolated new compliance requirement. Its institutional logic carries forward the existing institutional arrangements of the Data Security Law, the Cybersecurity Law and the Regulations on the Administration of Network Data Security concerning data classification and grading, important data protection, risk assessment, report submission and regulatory verification.
If the Measures for the Administration of Personal Information Protection Compliance Audits address the audit question of "whether personal information processing activities are lawful and compliant", then the Measures address the assessment question of "whether important data processing activities are secure and controllable". The former centres on the protection of personal information rights and interests; the latter centres on network data security and important data protection. Together they show that corporate data compliance is moving from "compliance of institutional texts" into a verifiable stage of "assessment, audit, reporting, rectification and evidence retention".
This article provides a quick interpretation of the issues enterprises care about most in the form of fifteen questions.
01. What is network data security risk assessment?
Article 2, paragraph 2 of the Measures expressly provides that network data security risk assessment refers to activities such as risk identification, risk analysis and risk evaluation conducted on the security of network data and network data processing activities.
This definition contains three key terms. First, the object of assessment is "network data". This means the assessment is not limited to personal information, nor to any particular information system, but covers the data an enterprise processes in the network environment. Second, the object of assessment also includes "network data processing activities". That is, the assessment does not merely look at whether the data itself is sensitive, but at how the enterprise collects, stores, uses, processes, transmits, provides, discloses and deletes data, and whether these processing activities may give rise to data security risks. Third, the content of the assessment is "risk identification, risk analysis and risk evaluation". Therefore, network data security risk assessment is not a simple institutional check, nor a formalised security statement, but requires a systematic judgment of the sources of risk in the enterprise's data processing activities, the likelihood of risk occurrence, the degree of risk impact, the effectiveness of security control measures and the residual risk.
From the perspective of corporate practice, network data security risk assessment should at a minimum cover the mapping of data assets and data processing activities, data classification and grading, identification of important data, data flow analysis, management of data recipients, management of entrusted processing and joint processing, data cross-border scenarios, system security measures, organisational management systems, emergency response mechanisms for data security incidents, and the closed loop of problem rectification.
02. Is network data security risk assessment the same as cybersecurity evaluation?
No.
Article 2 of the Measures defines network data security risk assessment as the identification, analysis and evaluation of risks to "network data" and "the security of network data processing activities". Its core object is data and data processing activities, not merely information systems.
Cybersecurity evaluation, especially cybersecurity classified protection evaluation, focuses on whether networks and information systems achieve the security protection capability of the corresponding level, such as technical and management requirements for identity authentication, access control, security audit, intrusion prevention, malicious code prevention, and data backup and recovery. Network data security risk assessment goes further and focuses on: what data is processed in the system, whether important data is involved, how data flows, whether it is provided to third parties, whether it is entrusted for processing, whether it goes cross-border, whether security measures match the data risks, and what impact may result from leakage, tampering, destruction, illegal acquisition or illegal use.
A simplified distinction can be drawn: cybersecurity evaluation is more like a "system security check-up"; network data security risk assessment is more like a "data processing activity check-up". This also means that an enterprise cannot simply substitute completion of classified protection evaluation for network data security risk assessment. For enterprises processing important data, classified protection evaluation can serve as one of the important foundational materials for risk assessment, but cannot replace the risk identification, analysis and evaluation of the important data processing activities themselves.
03. Which enterprises must conduct network data security risk assessment?
Article 5, paragraph 1 of the Measures expressly provides that important data processors shall conduct risk assessment annually. Therefore, the core entities obliged to conduct annual network data security risk assessment are network data processors that process important data, that is, important data processors.
There are two steps of judgment here. First, whether the enterprise is a network data processor. Under China's data security and network data security regulatory system, an enterprise may generally constitute a network data processor as long as it carries out activities such as data collection, storage, use, processing, transmission, provision, disclosure and deletion in the network environment. Second, whether the enterprise processes important data. Only network data processors that process important data fall within the scope of the mandatory obligation under Article 5, paragraph 1 of the Measures to "conduct risk assessment annually".
Therefore, in determining whether it must conduct annual network data security risk assessment, an enterprise should not merely ask "am I an internet company", but should ask: "do I process important data?" Some traditional industry enterprises, although not internet platforms, may also fall within the scope of important data processors if the data they process meets the criteria for identifying important data, for example data involving key fields such as financial operations, medical and health care, education management, transportation, energy supply, industrial production, geospatial information and supply chain operations.
04. Do enterprises that do not process important data also need to conduct risk assessment?
Article 5, paragraph 3 of the Measures provides that network data processors processing general data, that is, general data processors, are encouraged to conduct risk assessment at least once every 3 years.
This means that enterprises not processing important data generally do not bear the same mandatory annual assessment obligation as important data processors. However, the Measures do not completely exclude general data processors from the risk assessment system; rather, by way of "encouraging at least once every 3 years", they set a compliance-promotional requirement for general data processors.
From the perspective of strict legal obligation, the requirement that general data processors conduct risk assessment at least once every 3 years should not be directly understood as an obligation as mandatory as the annual assessment for important data processors. From the perspective of compliance practice, however, enterprises should not conclude that "as long as we do not process important data, no assessment is needed at all". The reason is that an enterprise's judgment as to whether it processes important data may not be accurate; general data may also give rise to higher security risks under particular scale, particular scenarios, particular combinations and particular flows; and in regulatory inspections, customer due diligence, financing and listing, data transactions, data cross-border, supplier admission and handling of major data security incidents, whether an enterprise has conducted data security risk assessment may become an important basis for external evaluation of its data governance capability.
Therefore, for general data processors, a more prudent approach is: do not simply understand the triennial risk assessment as a mandatory annual obligation, but gradually establish a periodic data security risk assessment mechanism, and at least conduct special assessments in scenarios such as major business adjustments, system upgrades, changes in data flows, introduction of third-party processing, and occurrence of data security incidents.
05. Do core data processors fall under these Measures?
Article 23, paragraph 1 of the Measures provides that risk assessment by network data processors processing core data shall be carried out in accordance with relevant state provisions.
This provision shows that core data processors cannot simply be handled under the rules for ordinary important data processors. Core data occupies a higher protection tier in China's data security system and usually involves major matters such as national security, the lifelines of the national economy, important livelihood, and major public interests. Core data will be managed by the state through higher-tier and stricter institutional rules.
Therefore, if the data an enterprise processes may involve core data, it should give priority to the special provisions of the state and industry competent authorities on core data catalogues, core data identification rules, security management of core data processing activities, core data cross-border and security assessment, rather than merely applying the general rules in the Measures on annual risk assessment for important data processors. The identification of core data and important data is not a matter over which enterprises have complete discretion. Enterprises should identify such data in light of national standards, industry rules and the requirements of competent authorities, and should also pay attention to whether they have been notified, determined or required by relevant departments to be included in the management of core data or important data catalogues.
06. How do enterprises determine whether they process important data?
Enterprises cannot determine whether they process important data merely by experience, still less simply exclude important data risks on the grounds that "we are not a platform enterprise", "we are not a data company" or "we only manage data internally".
Article 6 of the Measures provides that risk assessment work shall be carried out in accordance with the relevant requirements of the Data Security Law and the Regulations on the Administration of Network Data Security, with reference to the relevant national standards on data security risk assessment; where the relevant competent authorities have other provisions on risk assessment work in their industry or field, those provisions shall prevail. This shows that the identification of important data itself should be carried out within the framework of data classification and grading, industry rules and national standards.
Enterprises can determine whether they process important data from three levels. First, according to national-level data classification and grading rules. Enterprises should pay attention to the basic identification logic for general data, important data and core data in the Data Security Law, the Regulations on the Administration of Network Data Security and national standards such as the Data Security Technology - Rules for Data Classification and Grading. Generally speaking, important data is not determined by whether the data is important to a single enterprise, but by whether the data, once leaked, tampered with, destroyed, illegally acquired or illegally used, may affect national security, economic operations, social stability, public health and safety, public interests, etc. Second, according to the data classification and grading and important data identification rules of industry competent authorities. In recent years, different industries have successively issued or published data classification and grading rules. For example, the financial information services field has issued the Guidelines for Data Classification and Grading of Financial Information Services to guide financial information service institutions in carrying out data classification and grading and important data identification; the education field has issued the Guidelines for Data Classification and Grading of Education Data, providing a rule basis for education administrative departments, schools and other entities to carry out data classification and grading; and the health field had previously issued the Guidelines for Data Classification and Grading of Health Industry Data (Trial), clarifying the definitions of the scope of important data and core data in the health industry and guiding the industry in data classification and grading. Third, determine in light of the enterprise's own data processing scenarios. Even if a certain type of data may not constitute important data in a single, small-volume, static state, its risk level may change under particular scale, precision, coverage, time span, combination or flow scenario.
Therefore, to determine whether important data is processed, an enterprise should first complete four foundational tasks: data asset inventory, data classification and grading, important data identification, and formation of an important data catalogue. Without these four preliminary tasks, an enterprise's direct answer to the question "do I need to carry out an important data security risk assessment?" usually lacks a reliable basis.
07. How often must important data processors conduct assessments? Is it only a fixed annual assessment?
First, it must be made clear: for important data processors, conducting a network data security risk assessment once each year is a basic obligation established by Article 5, Paragraph 1 of the Measures. As long as an enterprise is an important data processor, it should not understand risk assessment as occasional, temporary work, or work carried out only after a regulatory requirement is imposed; rather, it should incorporate it into its annual data compliance plan and form a常态化 mechanism of annual assessment, report preparation, internal review, report submission, and problem rectification.
However, annual assessment is not the only scenario. Article 5, Paragraph 2 of the Measures further provides that where a major change occurs in the security status of important data and may adversely affect data security, a risk assessment should be promptly carried out on the part that has changed and its impact. It can thus be seen that important data security risk assessment includes at least two types of scenarios: one is annual assessment, that is, important data processors must carry out an overall, periodic assessment of their important data processing activities every year; the other is a special assessment triggered by a major change, that is, when a major change occurs in the security status of important data and may adversely affect data security, the enterprise should promptly carry out a special risk assessment on the part that has changed and its impact.
In practice, scenarios that may trigger a special assessment include major reconstruction of important data processing systems, substantive changes in the purpose, method, or scope of important data processing, provision of important data to new third parties, major changes in entrusted processing relationships for important data, changes in important data cross-border scenarios, major changes in important data storage locations, system architecture, or security control measures, major changes in control relationships or flows of important data caused by enterprise mergers and acquisitions, business restructuring, or system migration, and incidents such as leakage, tampering, destruction, illegal acquisition, or illegal use of important data. An enterprise cannot conduct only a formalistic assessment at a fixed time each year; rather, it should establish a dual-track mechanism of "annual assessment + trigger-based special assessment."
08. Is the three-year assessment for general data processors a mandatory obligation?
Article 5, Paragraph 3 of the Measures uses the expression "encourage," that is, general data processors are encouraged to carry out a risk assessment at least once every 3 years.
Therefore, from the perspective of the nature of the norm, the requirement that general data processors carry out a risk assessment at least once every 3 years is an advocacy and guidance requirement, and should not be directly equated with the mandatory obligation of annual risk assessment for important data processors. However, this provision is still of great significance: it shows that the network data security risk assessment system does not only serve important data processors; even if an enterprise does not process important data, risk assessment remains an important tool for data security governance; it may also gradually become a baseline for industry practice. For enterprises with large data scale, complex data processing activities, frequent external cooperation, and strict customer review, even if they do not process important data, they may still be required by customers, partners, audit institutions, investors, or regulators to explain their data security risk assessment situation.
In addition, periodic risk assessment can also help enterprises discover important data identification risks in advance. Some enterprises may mistakenly believe that they process only general data before conducting data classification and grading. Through a three-year or irregular risk assessment, changes in data types, data scale, data flows, and risk levels can be discovered in a timely manner. Therefore, general data processors may not follow the annual mandatory assessment requirements for important data processors, but it is still recommended that they establish an appropriate periodic assessment mechanism and carry out special assessments in scenarios such as high-risk business changes, data security incidents, major system adjustments, cross-border data transfer, entrusted processing, and data sharing and openness.
09. Can enterprises conduct risk assessments themselves?
Yes. Article 7, Paragraph 1 of the Measures provides that network data processors may conduct risk assessments themselves or entrust third-party assessment institutions to conduct them. Article 7, Paragraph 2 further provides that where a network data processor conducts a risk assessment itself, it shall designate a dedicated person to be responsible.
This means that the Measures do not require all risk assessments to be completed by external institutions. For enterprises with professional capabilities in data security, network security, legal compliance, and internal control audit, they may organize risk assessments themselves. However, self-assessment is not equal to a simple self-check, and even less equal to a security statement issued by the information technology department. An enterprise's self-assessment should still have a complete assessment plan, assessment responsible person, assessment scope, and assessment basis, and should be based on the data asset and processing activity list, data classification and grading, and important data identification results. Through procedures such as business interviews, system verification, policy review, and third-party management review, it should form conclusions on risk identification, risk analysis, and risk evaluation, and ultimately implement them as a problem list, rectification plan, rectification tracking mechanism, assessment report, and supporting working papers.
Self-assessment is more suitable for enterprises with relatively clear data processing scenarios, relatively mature internal data compliance teams and security teams, and a good foundation for data asset management. For enterprises with a wide scope of important data, complex business scenarios, frequent external data flows, or a need for strong external credibility, they may consider entrusting third-party assessment institutions to conduct assessments.
10. Can enterprises entrust third-party institutions to conduct risk assessments?
Yes. Article 7, Paragraph 1 of the Measures clearly provides that network data processors may entrust third-party assessment institutions to conduct risk assessments. Article 7, Paragraph 2 provides that where a network data processor entrusts an assessment institution to conduct a risk assessment, it shall clarify the rights and obligations of both parties by concluding a contract or other documents with legal effect.
Special attention should be paid to the fact that Article 10 of the Measures requires assessment institutions to make risk judgments fairly and objectively, and to be responsible for the authenticity, validity, and completeness of the risk assessment reports they issue; Article 11 provides that assessment institutions may not subcontract; Article 14 requires assessment institutions and their staff to keep confidential in accordance with the law the data, trade secrets, confidential business information, and other information obtained during the assessment process, and to promptly delete or properly dispose of relevant information after the assessment is completed in accordance with the contract.
These provisions mean that when an enterprise entrusts a third-party assessment institution, it should not focus only on price quotes and report templates, but should also focus on the assessment institution's professional capability, independence, confidentiality capability, data processing security capability, and report quality control mechanism. At the same time, an enterprise cannot be exempted from its own data security responsibilities merely because it has entrusted a third-party institution. The assessment institution provides professional assessment services, and the data security protection obligation remains with the network data processor.
11. Under what circumstances will regulators require enterprises to entrust assessments?
Article 17 of the Measures provides that where provincial or higher cyberspace administration departments, telecommunications authorities, public security organs, and other relevant departments discover specific circumstances in work such as verification of risk assessment reports and supervision and inspection, they may require network data processors to entrust certified assessment institutions to conduct risk assessments. These circumstances include: network data processing activities present relatively major security risks that may endanger national security or public interests; network data security incidents occur, resulting in leakage or theft of important data or large-scale personal information; and other circumstances prescribed by relevant departments.
Three issues need attention here. First, this is not the regulator directly designating a particular assessment institution for the enterprise, but rather the regulator may require the enterprise to entrust a "certified assessment institution" to conduct a risk assessment. Second, such assessments usually occur in scenarios with relatively high risks or where security incidents have already occurred, and differ from the annual assessments conducted by enterprises themselves, having a stronger regulatory disposition nature. Third, Article 17 of the Measures also provides that for the same network data security incident or risk, network data processors may not be repeatedly required to entrust assessment institutions to conduct risk assessments. This provision helps avoid repeated assessments of the same incident or the same risk and reduces unnecessary compliance burdens.
If an enterprise is required by regulators to entrust an assessment, it should also pay attention to the cooperation obligations under Article 18 of the Measures: the enterprise should provide necessary support to the assessment institution, including necessary access to network data facilities, network data, systems, and operation log records; complete the risk assessment within a limited time; after completing the assessment, submit the risk assessment report issued by the assessment institution to the relevant departments; and rectify the problems found in the assessment as required, and submit a rectification report within 15 working days after rectification is completed. In addition, Article 18 of the Measures also clearly provides that network data processors may not in any way require or suggest that assessment institutions issue false or improper risk assessment reports.
12. When should risk assessment reports be submitted?
Article 16, Paragraph 1 of the Measures provides that important data processors shall, within 20 working days after the annual risk assessment is completed, submit the risk assessment report to the relevant competent departments in accordance with their requirements. This shows that the annual risk assessment of important data processors is not merely for internal retention; there is a clear obligation to submit reports.
Enterprises need to focus on the "20 working days" period. This period starts from the completion of the annual risk assessment. Therefore, in the annual compliance plan, an enterprise should not only arrange the assessment start time, but should also work backward to set the assessment completion time, report finalization time, internal approval time, and formal submission time. A relatively prudent annual arrangement can be designed according to the following timeline:
Note: The above timetable is a suggested arrangement for annual risk assessment work. Enterprises may appropriately start earlier according to the submission requirements of competent departments, industry regulatory practice, business complexity, and whether a third-party institution is entrusted; if a major change occurs in the security status of important data, a special risk assessment should be promptly carried out on the part that has changed and its impact, without being limited by the annual timetable.
For large group enterprises, further consideration should be given to whether different entities, different business segments, and different regional companies separately constitute important data processors, and whether risk assessment reports should be prepared uniformly, prepared separately by entity, or adopt a method of group coordination with separate confirmation and submission by entities. These issues need to be determined before the assessment starts; otherwise, they may easily affect subsequent submission deadlines.
13. To whom should risk assessment reports be submitted?
Article 16, Paragraph 1 of the Measures provides that important data processors shall submit risk assessment reports to the relevant competent departments in accordance with their requirements; where the competent department is unclear, they shall submit to the provincial cyberspace administration department or the national cyberspace administration department.
Therefore, the basic rule for submission targets is: where there is a clear industry competent department, submit in accordance with the requirements of the relevant competent department; where the competent department is unclear, submit to the provincial cyberspace administration department or the national cyberspace administration department.
Article 16, paragraph 2 of the Measures further requires that the relevant competent authorities shall make public the channels and contact details for submitting risk assessment reports, promptly receive risk assessment reports submitted by important data processors, and, within 10 working days from the date of receipt of a risk assessment report, notify the cyberspace administration department at the same level of the report. The national cyberspace administration department shall compile the relevant reports and share them with the relevant departments of the State Council such as telecommunications, public security and state security. This rule reflects the regulatory mechanism of "industry competent authorities bearing primary responsibility, cyberspace administration departments providing overall coordination, and relevant departments sharing information".
For enterprises, in practice they should confirm in advance whether their industry already has a clear competent authority and submission channel, whether the provincial cyberspace administration department at their location has already made public the channels and contact details for submitting risk assessment reports, and whether group enterprises or cross-industry enterprises involve multiple competent authorities and need to communicate separately on submission channels. For enterprises with complex business types, especially group enterprises simultaneously involved in multiple types of business such as finance, healthcare, education, transportation, industry and internet platforms, the submission targets and submission channels may be more complex than for single-entity enterprises, and regulatory communication and internal coordination should be carried out in advance.
14. How long must risk assessment reports be kept?
Article 15, paragraph 1 of the Measures provides that important data processors conducting annual risk assessments shall prepare risk assessment reports in accordance with the provisions of the relevant competent authorities in accordance with the law; where the relevant competent authorities have no provisions on risk assessment reports, risk assessment reports may be prepared by reference to the relevant national standards on data security risk assessment; risk assessment reports shall be kept for at least 3 years.
Therefore, important data processors should keep the final version of the risk assessment report for at least 3 years. From a practical perspective, however, keeping only the final report is not enough. This is because Article 16, paragraph 3 of the Measures provides that cyberspace administration departments at or above the provincial level, telecommunications competent authorities, public security organs, state security organs and other relevant departments may inspect and verify the authenticity and accuracy of the risk assessment reports of important data processors, and important data processors shall cooperate in carrying out the inspection and verification.
If regulatory authorities verify the authenticity and accuracy of a report and the enterprise provides only the final report but is unable to provide the working papers, data lists, interview records, system verification records and rectification evidence supporting the report's conclusions, the credibility of the report will be affected. Therefore, enterprises are advised to retain the following materials as well:
From the perspective of the compliance evidence chain, a risk assessment report is not an isolated document but a concentrated presentation of an enterprise's data security governance capabilities. A report without working papers, without rectification and without a record of steps taken will find it difficult to withstand subsequent regulatory verification.
15. What are the similarities and differences between network data security risk assessment and personal information protection compliance audit?
Network data security risk assessment and personal information protection compliance audit are similar in institutional structure, so the new network data security risk assessment system can be understood by reference to the personal information protection compliance audit system with which enterprises are relatively familiar.
Article 2, paragraph 2 of the Measures for the Administration of Personal Information Protection Compliance Audits provides that personal information protection compliance audit refers to supervisory activities that review and evaluate whether the personal information processing activities of personal information processors comply with laws and administrative regulations. Article 3 provides that where a personal information processor conducts a personal information protection compliance audit on its own, it shall do so periodically through an internal body or by engaging a professional institution. Article 5 provides that where personal information processing activities present relatively high risks, may infringe upon the rights and interests of numerous individuals, or where a personal information security incident reaching a certain scale occurs, the protection department may require the personal information processor to engage a professional institution to conduct a compliance audit.
By comparison, Article 2 of the Measures provides for the identification, analysis and evaluation of risks to the security of network data and network data processing activities; Article 7 provides that network data processors may conduct risk assessments on their own or by engaging third-party assessment institutions; and Article 17 provides that in specific high-risk scenarios, regulatory authorities may require network data processors to engage certified assessment institutions to conduct risk assessments. The main similarities and differences between the two are as follows:
The two are not in a relationship of substitution but in a parallel relationship. For enterprises that simultaneously process large amounts of personal information and important data, they may in the future face both personal information protection compliance audits and network data security risk assessments at the same time. The former focuses on issues such as the legality of personal information processing, protection of individual rights and interests, notice and consent, automated decision-making, entrusted processing, joint processing and personal information protection impact assessments; the latter focuses on issues such as data security risks, identification of important data, flows of important data, changes in the security status of important data, the capabilities of third-party recipients, report submission and regulatory verification.
However, the two can also share a large amount of foundational work. For example, data asset inventories, processing activity inventories, system inventories, third-party inventories, data flow diagrams, security management systems, emergency plans, and access management and log management materials can all support both personal information protection compliance audits and network data security risk assessments. Therefore, enterprises should not establish a separate isolated process for each new regulation, but should take data asset mapping and data classification and grading as the foundation and carry out personal information protection compliance audits, important data security risk assessments, data export security assessments, cybersecurity classified protection evaluations, commercial cryptography application security assessments and day-to-day data security governance in a coordinated manner.
Conclusion: Enterprise data compliance is entering the "verifiable era"
Questions and answers
Which enterprises must conduct network data security risk assessments under the Measures for Network Data Security Risk Assessment?
Important data processors must conduct risk assessments annually. An enterprise must first determine whether it is a network data processor and whether it processes important data. Only those processing important data fall within the mandatory annual assessment obligation.
How often must important data processors conduct risk assessments under the Measures for Network Data Security Risk Assessment?
Important data processors must conduct an annual risk assessment. Additionally, when a major change occurs in the security status of important data and may adversely affect data security, they must promptly carry out a special assessment on the changed part and its impact.
When and to whom must important data processors submit risk assessment reports under the Measures for Network Data Security Risk Assessment?
Important data processors must submit the risk assessment report within 20 working days after the annual assessment is completed. Reports go to the relevant competent departments; if unclear, to the provincial or national cyberspace administration department.
Can enterprises conduct network data security risk assessments themselves under the Measures for Network Data Security Risk Assessment?
Yes, network data processors may conduct assessments themselves or entrust third-party institutions. Self-assessments require a dedicated person in charge and must follow a complete assessment plan, scope, and basis, resulting in a problem list, rectification plan, and assessment report.
How long must risk assessment reports be kept under the Measures for Network Data Security Risk Assessment?
Important data processors must keep risk assessment reports for at least 3 years. Enterprises are also advised to retain working papers, data lists, interview records, system verification records, and rectification evidence to support the report's conclusions during regulatory verification.
Laws and cases cited
Laws
- Data Security Law
- Cybersecurity Law
Regulations
- Measures for Network Data Security Risk Assessment
- Regulations on the Administration of Network Data Security
- Measures for the Administration of Personal Information Protection Compliance Audits
Standards
- Data Security Technology - Rules for Data Classification and Grading
- Guidelines for Data Classification and Grading of Financial Information Services
- Guidelines for Data Classification and Grading of Education Data
- Guidelines for Data Classification and Grading of Health Industry Data (Trial)
