Benefits
The first benefit to incorporate security in the lowest layers of ISA is that its safety is generalized every where ISA is deployed, and at anytime. This is a very important advantage when comparing to security problems recurrently occuring on all runtime environments (operating systems, browsers, etc.). Having a common security foundation for all artefacts, promotes security by design. For instance, the benefit of a shared base for rights management and access checks. If these foundations are “rock solid”, all ISA systems will take advantage. Together with an iterative improvement process, it warrants to reach an excellent security level. Remember that a system is only as secure as its weakest element.
Some security properties immediately appear desirable: Integrated crypting, integrated space insulation, resistance to common attacks (Cf. Common Types of Network Attacks) and even to deep spying, like those based on firmware (hard drive, routers, SIM cards, etc.).
The access and the rights must be uniformly managed. To ensure security, they have to be integrated to all objects incorporated in ISA.
Since encryption is one corner stone of security, an absolutely secure encrypting is a “must have”.
The authentication question has to be carefully examined, out of any fashions. Authentication should be as simple and efficient as possible. More advanced functions like “single sign on” could be incorporated in ISA.
Benefits list :
- Shared security foundation.
- Avoids weak points in the security chain.
- Absolute privacy.
- Unified access and rights managements.
Challenges
Define an absolutely sure crypting mechanism appears very difficult. In particular, for deep attacks based on the hardware/firmware.
Follow the most commonly shared Security Design Principles: Least Privilege, Fail-Safe Defaults, Economy of Mechanism, Complete Mediation, Open Design, Separation of Privilege, Least Common Mechanism, Psychological Acceptability, Weakest link, Secure Failure.
As you can't manage what you don't measure, security measurement is required. However, software measuring and more over its security properties is not trivial.
Establish a security evolution process and a distribution mechanism. This last aspect has to be taken into account in realization of Wish N°2 – Distribution.
As some readers could see, I'm not a security specialist. So all helps of the community for enriching and also for building this requirement are welcome! |