Technical Safety Norms
Safe practice for software, data, infrastructure, security and engineering work.
Safety Norms: Web Application Security
This Safety Norms document sets out practical rules for people who design, build, test, deploy, and operate web applications. It treats web application security as a safety discipline, because unauthorized access, data exposure, and service disruption can harm users, staff, and the organization. The norms identify the people involved, the activities and tools that carry risk, and which controls are mandatory and which are recommended. Coverage includes access control, privacy, secure design, authorized testing, incident response, reliability, and responsible use. This is educational guidance intended as a starting point for locally approved procedures. It does not replace formal training, supervision, legal advice, or professional authorization. Laws, standards, and vendor instructions vary by jurisdiction and version, so verify current requirements with competent authorities or qualified professionals before relying on them.
Read the safety norms TechnicalSafety Norms: Site Reliability Engineering
This Safety Norms document gives Site Reliability Engineering teams a starting point for operating production systems without causing harm to workers, customers, the public, or the environment. Site reliability engineering applies software engineering to operations, so its risks include service outages that affect people who depend on them, exposure of personal data, unsafe physical work in data centers and edge sites, and energy and hardware waste. The norms distinguish mandatory rules from recommendations, assign responsibilities, set competence expectations, and describe preventive controls, permit-style approval for physical work, emergency escalation, records, and review. Requirements that depend on jurisdiction, contracts, or sector regulation must be verified with competent authorities or qualified professionals. Adapt these norms into locally approved procedures before use.
Read the safety norms TechnicalSafety Norms: Software Quality Assurance and Test Automation
This Safety Norms document gives software quality assurance and test automation teams a practical starting point for protecting people, systems, and data during testing. It covers test environments, automation frameworks, test data, defect handling, and release decisions. It separates mandatory rules from recommendations, names the responsible roles, and explains how to handle security findings, production incidents, privacy exposure, and physical hazards in test labs. Laws, standards, contracts, and vendor instructions vary by jurisdiction and version, so teams must verify current requirements with qualified professionals and their organization's compliance function. This is educational guidance. It does not replace approved local procedures, formal training, or supervision by authorized staff.
Read the safety norms TechnicalSafety Norms: Predictive Maintenance Technology
This document sets out practical safety norms for predictive maintenance technology, the practice of using sensors, condition monitoring, data analytics, and alerts to decide when industrial equipment should be inspected, adjusted, or repaired. It treats the subject as a working discipline that touches people on the plant floor, technicians who install and service sensors, analysts who interpret data, and managers who approve maintenance actions. The norms distinguish mandatory rules from recommendations, identify hazards arising from installation, data handling, and misleading alerts, and describe how roles, competence, controls, records, and emergency escalation fit together. Laws, standards, and manufacturer instructions are jurisdiction-dependent and must be verified with competent authorities and qualified professionals. This is educational guidance. It does not replace formal training, authorized procedures, energy isolation rules, supervision, or emergency services.
Read the safety norms TechnicalSafety Norms: Systems and Network Administration
This Safety Norms document sets practical rules for people who build, operate, secure, and repair computer systems and networks. It covers servers, virtual machines, directory services, firewalls, switches, backups, monitoring tools, and the access and change decisions that surround them. Mandatory rules are labeled as required, and suggestions are labeled as recommended. Laws, standards, and vendor instructions vary by jurisdiction and organization, so readers should verify current applicable versions with competent authorities, legal counsel, and qualified professionals. This is educational guidance. It is a starting point for locally approved procedures and does not replace formal training, supervision, vendor authorization, or emergency services.
Read the safety norms TechnicalSafety Norms: Industrial IoT Applications
This document sets out practical safety norms for Industrial IoT applications, where networked sensors, controllers, gateways, edge devices, and cloud analytics are connected to production equipment, utilities, and process systems. It covers the people who design, install, maintain, and operate these systems, the hazards they create or fail to prevent, and the controls that protect workers, the nearby public, and the environment. Mandatory rules are distinguished from recommendations. Laws, standards, codes, and manufacturer instructions vary by jurisdiction and must be verified with competent authorities and qualified professionals. This is educational guidance. It does not replace formal training, authorized procedures, site supervision, or emergency services. Use it as a starting point for locally approved procedures.
Read the safety norms TechnicalSafety Norms: Natural Language Processing
Natural language processing combines text and speech data, statistical or neural models, and computing infrastructure to analyze, classify, translate, or generate language. Its safety risks are less about moving machinery than about personal data exposure, unsafe model outputs, electrical and thermal hazards in workstations and server spaces, ergonomic strain from long sessions, and environmental impact from energy use and discarded hardware. This document sets out mandatory norms and recommended practices for students, researchers, and practitioners. It covers roles, competence, risk assessment, preventive controls, equipment and environmental safeguards, incident and emergency escalation, records, and review. It is educational guidance. It does not replace institutional policy, qualified supervision, legal review, or emergency services. Laws, standards, and manufacturer instructions vary by jurisdiction and must be verified with competent authorities or qualified professionals.
Read the safety norms TechnicalSafety Norms: Large Language Models
This Safety Norms document gives practical rules for teams that build, fine-tune, evaluate, deploy, or use large language models (LLMs). It covers the people, tools, data, and decisions involved in these systems, including training data handling, model access, prompt and tool integration, output review, and monitoring after release. Mandatory rules are written with must or mandatory labels, while recommendations use should. Because laws, standards, and contractual terms vary by jurisdiction and sector, readers must verify current requirements with qualified legal, security, and compliance professionals. This document is educational guidance. It is a starting point for locally approved procedures, not a replacement for formal training, supervision, or authorization.
Read the safety norms TechnicalSafety Norms: Industrial Automation Control
This Safety Norms document sets out practical rules for people who design, install, program, commission, maintain, and operate industrial automation control systems. These include programmable logic controllers, safety instrumented functions, variable frequency drives, operator interfaces, field sensors and actuators, and networked supervisory systems. Its purpose is to prevent injury to workers and the public, prevent uncontrolled releases to the environment, and protect process integrity and data. It separates mandatory rules from recommendations, identifies who holds accountability, and explains how work is authorized through permits, lockout, and change control. It is educational guidance and a starting point for locally approved procedures. It does not replace qualified engineering, formal training, supervision, or emergency services.
Read the safety norms TechnicalSafety Norms: Google Cloud Platform Basics
This document sets out practical safety norms for people learning the basics of Google Cloud Platform, including those who create projects, configure identity and access, store data, deploy workloads, and read billing and logs. It separates mandatory rules from recommendations and identifies the hazards that matter most in cloud work: over-privileged accounts, exposed storage, leaked credentials, unplanned costs, unauthorized testing, and unreliable changes. Norms cover roles, competence, preventive controls, safe operating practices, privacy and security safeguards, incident escalation, records, and review. It is educational guidance intended as a starting point for locally approved procedures. It does not replace formal training, organizational security policy, or professional advice, and laws, standards, and provider terms are jurisdiction-dependent and must be verified with qualified professionals.
Read the safety norms TechnicalSafety Norms: Infrastructure as Code
This document sets practical safety norms for Infrastructure as Code, the practice of defining cloud resources, networks, servers, identity policies, and deployment pipelines in version-controlled files. A single change can create, alter, or delete production systems, so mistakes carry operational, data, and security consequences. The norms separate mandatory rules from recommendations and assign responsibilities for authoring, reviewing, approving, and operating infrastructure code. They address access control, secrets, state protection, change review, authorized testing, incident response, and monitoring. Treat this as educational guidance and a starting point for locally approved procedures. Laws, standards, and provider terms vary by jurisdiction, so verify current requirements with qualified professionals and competent authorities before relying on them.
Read the safety norms TechnicalSafety Norms: Broadcast, Audio and Media Production Technology
This Safety Norms document gives a starting point for safe, lawful and responsible practice in broadcast, audio and media production technology. It covers the people, equipment, spaces and information involved in studio, field, remote and live production work, including rigging, electrical supply, audio levels, hearing protection, lighting, cable management, live event hazards, and the handling of personal data and third-party content. It separates mandatory rules from recommended practice and identifies where laws, standards and manufacturer instructions depend on jurisdiction. It is educational guidance and does not replace formal training, supervision, approved local procedures, or professional advice. Readers should verify current requirements with competent authorities and qualified professionals before relying on any norm.
Read the safety norms