Search
Free Trial

Hongke's latest articles

HongKe

Add your title text here

I. Introduction: Strategic Changes at the Data Layer under the Critical Infrastructure Legislation

[Hongke Solutions] EU AI Act: How AI Literacy Training for Enterprises can be Realized

With the EU AI Act coming into force and entering into phased application, AI governance is moving from a 'self-regulatory proposal' to a 'regulatory imperative'. The Act adopts a gradual approach in terms of timeline: the AI Act comes into force on August 1, 2024, and is expected to be fully applicable on August 2, 2026; the "Prohibited AI Practices" and the "AI Competence Obligations" have been applicable since February 2, 2025, so companies must be able to account for the adequacy of their employees' AI competence and the measures taken by the company now.

I. The core requirement of the bill: AI literacy is "to do and to continue to do".

Article 4 of the EU AI Act explicitly requires that providers and deployers of AI systems must "take measures" to ensure, within their capabilities, that their employees and those who operate/use AI systems on their behalf have an adequate level of AI literacy, taking into account their technical background, experience, education and training, as well as the context in which the AI system is used and the target audience affected. This takes into account their technical background, experience, education and training, as well as the context in which the AI system is being used and who is being impacted.
 
The key here is not just to "teach a lesson", but to be able to go back to the language of management: do you have the segmentation design, do you have the frequency and tracking, do you have the training content aligned to the actual usage situation, and can you justify it when asked by the auditor/authority.

Turning AI Knowledge into Compliance: A Four-Level Training Framework

In order to make AI literacy training effective, it is recommended to use a four-layer structure of "from shallow to deep, from knowledge to behavior", which is in line with the idea of "according to the person, according to the situation, according to the target of influence" as required in Article 4.
 
  • Basic Cognitive Layer: Establish basic AI concepts, capability boundaries, and common misunderstandings to reduce operational and compliance risks caused by "over-trust" or "misuse of tools".
  • Risk Identification Layer: Enable employees to look at AI usage scenarios from a compliance risk perspective and know which scenarios are particularly sensitive and require upgraded controls.
  • Compliance Operations: Write company rules into actionable processes (e.g., which tools to use, which data not to lose, which outputs to manually review, and when to go through the approval process), so that the "policies" can really be put into practice.
  • Culture of Responsibility Layer: Transparency, fairness, accountability, and human oversight become work habits, especially in AI-assisted decision-making contexts.

Role differentiation: different departments have to learn different things about the same statute.

The essence of Article 4 is to "customize the curriculum to suit the needs of each individual". Therefore, it is recommended that the syllabus and depth of the course should be divided by roles, so as to avoid the same set of teaching materials for the whole company, which will lead to "learning but not using".
 
  • Employee-wide: Focus on safety and compliance guidelines for the day-to-day use of AI tools (e.g., sensitive data, output auditing, error and bias awareness).
  • Technical/Data teams: Enhance how compliance requirements become verifiable control points (risk of bias, record retention, transparency and governance interface) during development, deployment and maintenance.
  • HR/Legal Affairs: For highly sensitive decision-making scenarios such as recruiting and performance, strengthen the sensitivity of regulations and internal control processes on the matter of "people will be affected by AI".
  • Management: learns about governance: how to set up training systems, division of responsibilities, audit evidence and cross-departmental collaboration mechanisms to ensure that the company is really "taking action".

Use KnowBe4 for "Manageable, Trackable, Auditable" Training Operations

If an organization is already security-conscious or has a compliance training program in place, merging AI literacy into an existing platform is often the least laborious and easiest way to form a chain of evidence.
 
In terms of KnowBe4's Compliance Plus direction, it focuses on the delivery of compliance courses using KnowBe4's training platform and offers short, interactive modules, automated training activities and report tracking, with an emphasis on regular updates, so that you can turn training into a 'going concern' rather than a one-off project.
 
In addition, it is publicly available information that Compliance Plus has a library of "over 500 modules" and focuses on customizability, continuous updates and integration with the KnowBe4 platform for delivery, a structure that is more in line with the "contextual and personnel-driven" approach desired in Article 4.
Go to Knowbe4 product page

Other Articles
Hongke Dynamic

[Hongke News] Why Rule-Intensive Businesses Are Better Suited for Low-Code: Making Decision Logic “Configurable” Instead of “Hard-Coded”

Many rule-intensive enterprises often face challenges during digital transformation, such as business rules being tightly coupled with underlying code, cumbersome tuning processes, and difficulties in unifying logic across systems. Low-code solutions can transform decision logic into visual configurations, shortening rule iteration cycles and clarifying the division of responsibilities between business and IT. The Decisions platform integrates a low-code environment with a rules engine to independently build a shared decision-making layer. It supports drag-and-drop rule management and cross-system integration and invocation, balancing operational flexibility with IT governance and regulatory requirements.

Read more
HongKeTechnology June 23, 2026
Hongke Case

[Hongke Case Study] Hongke Panorama SCADA System: Enabling Industrial Automation and IT/OT Convergence Through REST Web Services

Learn more about how Hongke Panorama Suite uses standard REST Web Services (REST APIs) to enable bidirectional data exchange, break down data silos on the industrial floor, and seamlessly connect SCADA systems with real-world weather, energy, and telemetry big data—thereby comprehensively accelerating the deep integration of enterprise IT and OT.

Read more
HongKeTechnology June 23, 2026
Hongke Case

[Hongke Solutions] SimData High-Fidelity Virtual Dataset Solution: Perception Training for Autonomous Driving Based on aiSim

Hongke has launched SimData, a high-fidelity virtual dataset built on the aiSim simulation platform and fully compatible with the nuScenes format. It provides high-quality multimodal training data for autonomous driving perception algorithms, LiDAR, and BEV models, effectively addressing the challenge of data collection in extreme scenarios (Edge Cases). Click now to learn about the development process and see real-world results!

Read more
HongKeTechnology June 16, 2026
close menu icon

Contact Hongke to help you solve your problems.

Let's have a chat