Security_Design_Principles_Presentation.pptx

Security_Design_Principles_Presentation.pptx

• 1.
  Security Design Principles Anoverview of key principles for building secure systems (Class Presentation)
• 2.
  Introduction • Security DesignPrinciples are basic rules for building secure systems. • They protect data, prevent misuse, and reduce cyberattack risks. • These apply to software, networks, and organizational security.
• 3.
  Least Privilege • Giveusers only the access they need. • Limits damage if an account is compromised. • Example: A cashier can access sales data, not salaries.
• 4.
  Defense in Depth •Use multiple layers of security for protection. • If one layer fails, others still defend the system. • Example: Firewall + antivirus + strong passwords.
• 5.
  Fail-Safe Defaults • Denyaccess by default unless specifically allowed. • Systems should stay secure even when errors occur. • Example: Login errors should block access, not allow it.
• 6.
  Separation of Duties •Divide responsibilities among different people or systems. • Prevents fraud and insider misuse. • Example: One person requests, another approves payment.
• 7.
  Economy of Mechanism •Keep security systems simple and clear. • Simple systems are easier to test and maintain. • Example: Simple login systems reduce vulnerabilities.
• 8.
  Complete Mediation • Checkpermissions every time a resource is accessed. • Don’t assume access remains valid. • Example: Verify access for every file read/write.
• 9.
  Open Design • Securityshould not depend on hidden designs. • Transparency helps experts find and fix weaknesses. • Example: Open-source code allows public security review.
• 10.
  Least Common Mechanism •Avoid sharing common resources unnecessarily. • Reduces risk of one user affecting others. • Example: Separate memory or file spaces per user.
• 11.
  Psychological Acceptability • Securityfeatures should be easy to use. • If too hard, users will ignore or disable them. • Example: Use fingerprint or password managers.
• 12.
  Security by Design •Include security in all stages of development. • Identify threats early using threat modeling. • Prevention is cheaper than fixing later.
• 13.
  Conclusion • Security DesignPrinciples build trust and reliability. • They protect systems from attacks and misuse. • Security should always be part of the design process.