I recently went to a conference and talked to some people I would normally not be allowed near.
Here are their concerns:
- Out of band communication: being able to fall back to alternative channels of communication in case of breach to avoid intruders having perfect information about response strategy.
- E2E and MFA: These are tablestakes for any communication solution these days. Datalisp can obviously handle this since it is designed to be a general purpose solution for creating authenticated datastructures.
- Fallback strategies in case of failure of some kind. Here there are mostly two things to consider; being able to reason about (contextual!) trustworthiness of different versions of software so that you know which version to fall back to in case of some kind of software failure (i.e. resilient updates) and then offline-proof software, so being able to perform local reasoning (risk assessments) in case of network outage and then resolve any conflicts with upstream once connectivity is re-established.
- Selective disclosure of parts of software infrastructure to enable pooling of security; cross organization collaboration.
- Reproducible builds, completeness of build pipeline... i.e. having all behaviors that are depended on by the organization indexed in a menu and having associated risk assessments (basically what datalisp was designed for, although that holds for all these points).
- Being able to go back and forth between high level models or design discussion and the code that is supposed to implement said behaviour. Reason about completeness of translation/compilation at any level of granularity.
- Trust / risk assessments of any property in the system.
What I have been designing is a solution for p2p internet, but the only institutions that are already behaving rationally w.r.t. p2p are central banks (which already operate under a scale-free credit system of some sorts) so they are the ideal customers for this solution.
Please contact me about details.