3 ms·
rules and regulations [...] in a different league than what most developers are familiar with. [...] the design (not the code) apparently did not take into
by michaelt 10y ago
rules and regulations [...] in a different league than what
most developers are familiar with. [...] the design (not the
code) apparently did not take into account any messaging
security, relying on obscurity as its only defence.
Imagine you were building a suspension bridge to the highest safety standards, and you had people with microscopes manually inspect every grain of sand and cement that went into the foundations. But the suspension cables were made of old washing lines.
You would be achieving a very high and a very low standard of inspection at the same time.
Some people would say standards of inspection are only as strong as their weakest link; that the whole claim of such inspection is to prove the absence of such weak links; and that a standard that has approved such a bridge has, by so doing, shown the claimed proof of safety is a useless joke.
Other people would say the inspection is a checklist of common errors, rather than a proof of the safety of every aspect of the system; that proof of perfect safety was never its claim or goal; and that this merely shows there should be some extra boxes on the checklist, which was in any case a constantly evolving document.
- TickleSteve 10y agoInspection in this case is a proof that the design you're certifying is fit-for-purpose. So in your example, it would show that the loading and stresses on your washing lines were sufficiently low to meet the safety margin of the bridge. Certification of safety-related and medical devices is not a check-box exercise, it looks at the dynamic and static behaviour of your system as a whole (not just the software).
- michaelt 10y agoPerhaps I wasn't clear in my analogy. I mean the washing lines weren't fit for purpose (just like the insecure comms wasn't fit for purpose) but the inspection didn't identify them as unfit for purpose (just like the inspection didn't identify the insecure comms as unfit for purpose) Given that something unfit for purpose was certified, certification doesn't prove something is fit for purpose. Of course, certification may indicate something is probably more fit for purpose than something that failed the same certification or didn't attempt it.
- TickleSteve 10y agoThe inspection of the washing-line design should have identified this... unless human-failure. So your point is: "we don't know what we don't know"? True. I see no way around this.