E.g. Brain-computer interface could be such example. Some Chinese companies are known to be developing these kind of equipments for Alzimers'
As a cornerstone standard, I believe POSIX does aim to promote security. POSIX (and C to some extent) had introduced likes of `strlcpy`, `strlcat`, and removed `gets`, `makecontext`, etc. Input validation is essential, but it's not the whole picture. If you look at OWASP top ten for 2025, broken access control ranks 1st. US and EU has issued advisory on moving away from memory unsafe programming languages, and since the system interfaces of POSIX are based on C, it makes more sense to just switch to another proven language. The amount of boilerplate required to do even something simple is just too much and too error-prone. Also, POSIX isn't the only output of Open Group, For example: https://www.opengroup.org/forum/security/architecture > 2026年2月1日 11:30，Amit via austin-group-l at The Open Group > <[email protected]> 写道： > > On Sun, 1 Feb 2026 at 02:25, David A. Wheeler via austin-group-l at > The Open Group <[email protected]> wrote: >> >> >>> On Jan 31, 2026, at 12:17 PM, Amit <[email protected]> wrote: ... >> >>> In my opinion, denial of service is better than getting hacked. In >>> DoS, no personal information is leaked. But if someone gets hacked >>> then his/her personal information can be leaked. >> >> No. In some environments, it's much more important to >> keep the system running *even* if information leaks. >> In hospitals, for example, leaking medical records is bad, but >> having people die because the equipment won't run (availability) is much >> worse. > > The denial of service will happen to those people who want to process > really huge datasets - probably, more than 75% of the RAM size. > > Any equipment that is connected to the patient won't be processing > such huge datasets. > > Can you please give an example of an equipment that is connected to a > patient and it has to process really huge datasets? > > Amit
