Security engineering principles revised part2(Test Prep1)

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/51

encourage image

There's no tags or description

Looks like no tags are added yet.

Last updated 12:19 AM on 5/9/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai

No analytics yet

Send a link to your students to track their progress

52 Terms

1
New cards

Why is whitelisting safer than blacklisting? (Fail-safe in code)

Unknown inputs are automatically denied.

2
New cards

Why should systems never “guess intent”?(Fail-safe in code)

Invalid input should be rejected clearly.

3
New cards

Fail-safe middleware: What must run before business logic?

Authentication and authorisation middleware.

4
New cards

Fail-safe middleware: What should happen if middleware throws an exception?

Access must be denied.

5
New cards

Why are bypass paths dangerous?

Conditions like if(skipAuth) create vulnerabilities.

6
New cards

Fail-Safe Infrastructure: What should the default encryption posture be?

Encryption enabled by default

7
New cards

What should happen to unencrypted writes?

They should be rejected.

8
New cards

Why must backups fail loudly?

Silent failure means there are effectively no backups.

9
New cards

API Gateway Deny-by-Default:What does this ACL mean?

All routes are denied unless explicitly allowed.

10
New cards

Why is deny-by-default safer?

Undefined routes cannot bypass security.

11
New cards

Operational Fail-Safes: What should happen if a security scanner fails?

Deployment should stop.

12
New cards

What must every fail-closed event produce?

  1. Metrics

  2. Logs

  3. Alerts

13
New cards

Why are stack traces dangerous?(Trap: Soft 404s and Data Leaks)

They leak internal system details.

14
New cards

What information can verbose errors leak?

  1. Database names

  2. Server versions

  3. Internal architecture

15
New cards

What is the correct fix for verbose errors?

Log detailed errors internally and return minimal client errors.

16
New cards

(Trap: Insecure Not Found Checks)What should an unauthorised user receive?

Identical responses regardless of whether data exists.

17
New cards

(Trap: Insecure Not Found Checks) Insecure order

  1. Query DB

  2. Check auth

Attackers can probe whether records exist

18
New cards

(Trap: Insecure Not Found Checks) correct secure order?

  1. Check authorisation

  2. Query database

19
New cards

(Trap: Overbroad Try/Catch) What should happen when authentication fails?

The request must stop immediately.

20
New cards

Is Zero Trust a product?

No — it is an architectural philosophy.

21
New cards

What does Zero Trust assume about networks?

The network is not a trust boundary.

22
New cards

What does Zero Trust require?

Every request must be authenticated and authorised.

23
New cards

What was the old perimeter model?

Inside = safe, outside = dangerous.

24
New cards

Why is the old perimeter model broken?

Attackers enter using phishing, supply chain attacks, and stolen credentials.

25
New cards

What does Zero Trust assume?

Breach is inevitable.

26
New cards

Who must have verifiable identities in Zero Trust?

  1. Users

  2. Workloads

27
New cards

What is continuous authentication?

Re-verifying identity during sensitive operations.

28
New cards

Why is login-only authentication insufficient?

Session age and network location cannot be trusted.

29
New cards

What factors influence context-aware access?

  1. User identity

  2. Device health

  3. Workload

  4. Time

  5. Location

30
New cards

What is just-in-time access?

Permissions granted temporarily when needed.

31
New cards

What is risk-adaptive access?

Higher risk contexts require more verification.

32
New cards

What does mTLS provide?

Authenticated and encrypted service-to-service communication.

33
New cards

Why is application-layer access safer?

Access is limited to specific applications rather than entire networks.

34
New cards

What is micro-segmentation?

Limiting blast radius between services.

35
New cards

What is the problem with traditional VPNs?

VPN users often gain access to all servers.

36
New cards

What does an application access proxy do?

Grants access only to approved applications/APIs.

37
New cards

What is mutual TLS (mTLS)?

Both communicating services present certificates.

38
New cards

Why should source IPs not be trusted?

IPs can be spoofed or reused.

39
New cards

What do service meshes like Istio provide?

Transparent mTLS enforcement.

40
New cards

Why should raw bearer tokens not be forwarded internally?

Internal services should use scoped internal identities instead.

41
New cards

Why is PERMISSIVE mode dangerous in production?

It silently allows unencrypted traffic.

42
New cards

What three signals are checked in device-aware access?

  1. User identity

  2. Device compliance

  3. Sign-in risk

43
New cards

What happens when sign-in risk is high?

Step-up authentication or denial occurs.

44
New cards

Why is “allow any service in namespace X” dangerous?

Namespace-wide trust recreates perimeter security.

45
New cards

What should be trusted instead of network location?

Cryptographic identities.

46
New cards

Why is mTLS alone insufficient?

Encryption without authorisation still allows lateral movement.

47
New cards

Why is Zero Trust not a one-time project?

Threats and systems evolve continuously.

48
New cards

What should organisations secure first in Zero Trust?

  1. Admin access

  2. Production system

  3. Customer-data APIs

49
New cards

What does Least Privilege define?

Minimum allowed capability.

50
New cards

What does Fail-Safe Defaults handle?

Safe behaviour under uncertainty.

51
New cards

What does Zero Trust provide?

Explicit identity and context at every hop.

52
New cards

Why are logs and audit trails important?

They form the basis of digital forensics and incident response.