Proceedings of the International scientific and practical conference ― Cambridge Science and Education Conference‖ (February 23-25, 2026) / Publisher website: www.naukainfo.com. – Cambridge, United Kingdom, 2026. - 289 p.

104 with autonomous computing resources sufficient to function under network constraints or complete digital isolation. The scientific novelty of the study lies in the development of an adaptive algorithm based on a three-state controller functioning model. Table 1. Analysis of Critical System Vulnerabilities by Functional Blocks Functional Block Attack Vector / Threat Impact on System and Safety Identification and Authorization Credential Compromise. Cloning of RFID/NFC tokens (e.g., via vulnerabilities in MIFARE Classic). Gain of full unauthorized access to other employees' accounts and PPE limits. Data Interception. Absence of encryption between the reader and the controller. Risk of replay attacks for illegal acquisition of protective equipment. Dispensing and Transaction Recording Network Paralysis. Dependence on server response during DDoS attacks or connection loss. The system blocks, making it impossible to access PPE even if physically present in the machine. Command Injection. Use of open MQTT channels without proper authentication. Possibility of unauthorized remote dispensing or damage to the machine's mechanisms. Accounting and Reporting Global Cloud Failures. Outages in major provider services (e.g., AWS, Azure). Loss of real-time limit data and inability to generate safety compliance reports. History Manipulation. Tampering with the server database or event logs. Deletion of violation records and destruction of the legal liability framework. Inventory Control Metric Spoofing. Interference with physical sensors (scales, presence sensors). Creation of "artificial shortages" or delayed replenishment of critical safety gear. Unlike standard systems that cease operation during packet loss, the proposed model dynamically changes its behaviour depending on network quality metrics:  -ONLINE mode (standard operation) is used with a stable connection (server response delay t < 2 sec). The system operates in real time: the terminal sends a request, receives a balance verification from the central database, and synchronises