Back To Basics: MIL-STD-810

I was recently discussing with a friend regarding a reliability testing project. We were discussing specifics on MIL-STD-810 and I wanted to discuss regarding that today.

MIL-STD-810 is the U.S. Department of Defence’s guide for engineering and validating hardware to survive real environments. It was launched in the 1960s, but the document has kept evolving. Its mainly about making your hardware survive dust, heat, rain, altitude, vibration etc and exposing weak designs. It is not just for defence products, if you build drones, outdoor electronics, field medical gear, or rugged laptops, you will meet these same parameters.

Inside the document there are three big parts. Part One explains how to build a life cycle environmental profile and how to sequence tests to simulate real life. Part Two is a bunch of laboratory methods with setups and procedures for temperature, humidity, rain, dust, fog, solar, icing, vibration, shock, and combined environments. Part Three provides climate data, so your test levels are realistic, instead of guessing.

Beyond that, it discusses how to choose test levels, set up the product, add simple sensors, and record results. You’ll see advice on test order, running tests together, packaging checks, mold exposure and work in areas with explosive gases.

Although I wouldn’t suggest reading the 1000+ page document end to end. I think it’s imperative that you know that something like this exists for free, and you can load it up in your favourite LLM and summarize for your particular use case. Because it teaches you to think like a reliability engineer. The standard does not hand you pass or fail numbers. If you need a start on how to build a quality rugged hardware, start here and fine tune it to your needs.

BTW, there is no “MIL-STD-810 certification”. The correct phrasing is tested in accordance with MIL Standard 810. Tell what you tested, why those levels were chosen, and what passed because MIL-STD-810 is not a certification standard.

If you liked the post, Share it with your friends!

Tech News: EU Cyber Resiliency Act(CRA)

Came across the European Union law which will impact any products you plan to manufacture and sell in EU. I have tried to summarize whatever I have understood below.

CRA is an EU law for products with digital elements. If you ship hardware with firmware into the EU, you’re in scope. It entered into force in Dec 2024. Reporting starts on Sep 2026. Most requirements apply from Dec 2027. Cybersecurity becomes part of CE. It will be mandatory for your product to be “CE” compliant.

If you are building a product, then you are mandated to do a cybersecurity risk assessment and build to it. You would have to keep an update path that can push security patches quickly and, by default, automatically with an opt-out if users wish to. You should provide security updates free of charge during your support period. Support periods are to be around 5yrs for consumer gear (Unless expected usage time is shorter) and longer for industrial. Your technical file must prove all of this for CE.

For hardware teams, the first practical step is to map your device to the CRA lists. Annex III in the bill names important product categories. If you make routers or modems, operating systems on devices, microcontrollers or FPGAs with security functions, or smart home locks and cameras, you likely sit in Class I. Firewalls and tamper-resistant microcontrollers fall into Class II. Class II expects a third-party assessment path such as EU-type examination plus production control. If it’s not in any of these, you can do self assessment. Read the document properly.

There is some leniency for FOSS non-commercial projects or if your product is in alpha/beta prototype stage.

If you liked the post, Share it with your friends!
1 4 5 6 7 8 93