Session 02 : Principles of Secure Design Flashcards

1
Q

Principles of Secure design?

A
  • Least privilege and isolation
  • End-to-end security
  • Fail-safe defaults
  • Open design
  • Defense in depth
  • Security by design
  • Tension between security and other design goals
  • complete mediation
  • Use of vetted security components
  • Economy of mechanism
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q
  1. Least Privilege and Isolation : what is ?
A
  • Users, programs, and systems should have the minimum access which needed to do their job.
  • Different system components should be isolated from each other so that if one part is compromised, the rest remains safe.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q
  1. Least Privilege and Isolation : examples ?
A
  • A cashier in a supermarket can access the billing system but not customer financial record.
  • In Windows and Linux, regukar users cannot install software or change system settings without admin rights.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q
  1. Least Privilege and Isolation : why it’s important ?
A
  • Reduce the damage an attacker can do if they gain access.
  • Prevents accidental mistakes from affecting the entire system.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

2) End-to-end security : what is?

A
  • Data should be protected at all stages-when stored, transmitted, and processed.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

2) End-to-end security : examples?

A
  • WhatsApp use end-to-end encryption, only the sender and receiver can read messages, even if intercepted.
  • Online banking encrypts data from the user’s browser to the bank’s server.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

2) End-to-end security : why it’s important?

A

Protects sensitive data from hackers who try to steal or modify it.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

3) Fail-Safe Defaults : what is?

A
  • The system should deny access by default and grant access only when explicitly allowed.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

3) Fail-Safe Defaults : examples?

A
  • If a user enters the wrong password multiple times, the account gets locked instead of allowing further attempts.
  • Firewall rules should block all network traffic by default and allow only approved connections
  • A new employee should not have access to confidential files unless specifically given permission.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

3) Fail-Safe Defaults : why it’s important?

A

Prevents unauthorized access if security settings are misconfigured.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

4) Open Design : what is ?

A

Security should not depend on secrecy of design but on strong security mechanisms that can withstand public scrutiny.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

4) Open Design : examples ?

A
  • Encryption algorithms (AES, RSA, SHA-256) are publicly know but remain secure because they rely on mathematical streangth.
  • Linux operating system is open-source, meaning anyone can review its security code.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

4) Open Design : why it’s important ?

A
  • Security through secrecy is weak because once exposed, the system become vulnerable.
  • Publicly tested security mechanisms are more trustworthy.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

5) Defence in Depth?

A
  • What? :
    • Use **multiple layers of security ** so that if one layer fails, others still provide protection.
  • Examples? :
    • Cybersecurity uses firewalls, antivirus, encryption, multi-factor authentication (MFA) to protect data.
  • Why it’s important:
    • Multipe layers reduce overall risk.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

6) Security by Design?

A
  • What ?
    • Security should be built into the system from the start, not added later as an afterthought.
  • Examples ?
    • Employ the security practices into SDLC
  • Why important ?
    • Fixing security flaws later is expensive and risky.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

7) Tensions Between Security and Other Design Goals

A
  • What ?
    • Security must be balanced with usability, performance, and cost.
  • Examples ?
    • Strong passwords increase security but make them hard to remember
    • MFA improves security but takes extra time.
    • Encrypted DBs are secure but need more processing power.
  • Why important ?
    • Too much security can make a system inconvenient and reduce productivity.
    • Finding the right balance ensures both security and efficiency.
17
Q

8) Compile Mediation

A
  • What ?
    • Every access request should be checked every time, not just once.
  • Examples ?
    • ATM transaction require a PIN for each withdrawl
    • Online banking logs you out after inactivity to prevent unauthorized access.
    • OSs rechek user permissions every time a file is accessed.
  • Why important ?
    • Prevent Session hijacking and unauthorized access.
18
Q

9) Use of vetted security components

A
  • What ?
    • Use of tursted and well-tested security tools instead of creating custom.
  • Examples ?
    • Use AES encryption, instead of inventing new encryption method.
    • Use verified security libraries, instead of writing custom.
  • Why important ?
    • New untested security solutions often have hidden vulnerabilities.
19
Q

10) Economy of mechanism

A
  • What ?
    • Keep security systems as simple as possible to reduce errors and vulnerabilites.
  • Examples ?
    • Use simple password system with strong encryption.
    • Unix file permissions are simpler than complex access control models but still effective.
    • Firewalls with clear rules are easier to maintain.
  • Why important ?
    • Complex systems are harder to test and often contain hidden vulnerabilities.
20
Q

11) Usable security

A
  • What ?
    • Security systems should be easy to use, so that people can follow security best practices without confusion or frustation.
  • Examples ?
    • Password managers make it easier to use strong, unique passwords for each account.
    • Fingerprint scanners on phones provide strong security without needing complex passwords.
    • 2FA apps make logins more secure and user-friendly
  • Why important ?
    • If secrity is too difficult, users will find workarounds.
21
Q

12) Security composability

A
  • What ?
    • Different security components should work together seamlessly to provide strong protection.
  • Examples ?
    • Online banking uses encryption, user authentication, firewalls, and fraud detection - each layer supports the others.
    • Web securtiy combines HTTPS, firewalls, input validation, and intrusion detection.
  • Why important ?
    • If security systems don’t work together properly, gaps may create weak points that hackers can exploit.
22
Q

13) Prevention, Detection, and Deterrence

A
  • What ?
    • A compleate security system should include 3 key steps.
      1. Prevention : Stop attacks before happens
      2. Detection : Identify attacks when they occur.
      3. Deterrence : Make attacks less attractive or too risky for attackers
  • Examples ?
    • Cybersecurity
      1. Prevention : Firewalls and antivirus softwares block malware.
      2. Detection : IDS monitor for unusual behaviour.
      3. Deterrence : Strong encryption and legal consequences make hacking difficult and risky.
    • Physical Security
      1. Prevention : Locked doors and Security guards
      2. Detection : Security cameras and alarms
      3. Deterrence : Warning signs
  • Why important ?
    • No single security measure is enough - a complete system needs all three to be effective.