The idea is assume the board is compromised. Now what?
Answering that question is the key to robustness.
The idea is assume the board is compromised. Now what?
Answering that question is the key to robustness.
When I got a job at Boeing, I thought it was impossible to design an airplane with full redundancy. They showed me how it was done.
If a node is compromised, that shouldn't turn into full access to everything. Specifics would vary depending on your application, but while most user facing servers might need to be able to validate a login token, few would need to be able to issue a login token or access billing details.
If you compromise the node that has billing details or access to them, then you'll have them, but if you compromise a different node, you won't. That's better than compromise any host and get access to the 'private' network where there's no auth or encryption, which is kind of traditional.