User Tools

Site Tools


kb:cs:security-principles

Security Principles

Security is Part of Engineering Quality

Security is not treated as a separate concern from software quality, maintainability, or reliability.

Poor maintainability often increases security risk.

Prefer Simplicity

Complex systems are harder to:

  • review
  • validate
  • audit
  • maintain securely

Simple and explicit designs are generally safer.

Least Privilege

Systems and users should only have the access they actually require.

Examples:

  • avoid administrator execution when unnecessary
  • restrict exposed interfaces
  • minimize credential scope

Defense in Depth

No single security mechanism should be treated as perfect.

Multiple independent protections reduce risk.

Traceability

Security-relevant decisions and vulnerabilities should be:

  • documented
  • reviewable
  • reproducible

Realistic Threat Modeling

Security decisions should reflect realistic environments and operational constraints.

Industrial and test systems often have different threat profiles than internet-facing cloud systems.

kb/cs/security-principles.txt · Last modified: 2026/05/08 20:26 by joerg.hampel