3 ms·
There is no 'security product': you must engage in the permanent tracking of security flaw and intrusion: do heavily trap your kernel/applications, do man-in-th
by sylware 2y ago
There is no 'security product': you must engage in the permanent tracking of security flaw and intrusion: do heavily trap your kernel/applications, do man-in-the-middle traffic analysis between known traffic and unknown traffic, do not trust off-the-self crypto, etc.
But the basics are not even here: you should not use any compiler, all critical pieces of software should be assembly written with very lean SDK (aka extremely stable machine code), namely without the abuse of macro-preprocessor.
Everything else is just posture.
- saagarjha 2y agoI strongly disagree with this assessment
- sylware 2y agoWell, this is for the classic ASIC CPU world. But really critical stuff should go as deep as custom ASIC and/or FPGA. (A decade ago, I don't recall exactly, but those "security guys" did not even try with classic CPU ASICs, they were going custom _simple_ design on FGPA). That was a decade ago... nowadays...