Any attempt to prevent people from being able to see information.

• Information/Data Hiding

• Least Privilege

• Resource Encapsulation

• Layering

The goal is to simplify and decrease the number of ways the software can be exploited.

• Abstraction

• Domain Separation

• Modularity

• Minimization

A fancy word for summarizing or explaining in a way that can be easily understood.

• Process Isolation

• Abstraction

• Minimization

• Least Privilege

Keeping processes separate prevents the failure of one process from negatively impacting another.

• Information/Data Hiding

• Resource Encapsulation

• Process Isolation

• Simplicity of Design

Limits what access people have to your resources and what they can do with them.

• Least Privilege

• Layering

• Process Isolation

• Abstraction

Separating areas where resources are located prevents accidents and loss data, keeping information worlds from colliding.

• Layering

• Modularity

• Simplicity of Design

• Domain Separation

Resources including hardware, system objects, or processes- must be separated and used as intended.

• Domain Separation

• Resource Encapsulation

• Process Isolation

• Minimalization

If something is less complicated, it's less likely to have problems and easier to troubleshoot and fix.

• Modularity

• Simplicity of Design

• Layering

• Information/Data Hiding

Multiple layers of defense protect information. If one layer is defeated, the next layer should catch it.

• Layering

• Least Privilege

• Abstraction

• Modularity

Able to be inserted or removed from a project; each module has its own function, interchangeable with other modules.

• Process Isolation

• Least Privilege

• Simplicity of Design

• Modularity