352CIS-3 Chapter 6

What is the main benefit of using isolation in systems?

How does encapsulation contribute to security in programming?

What does the principle of modularity aim to achieve in software design?

What does simplicity of design focus on in secure systems?

What does the open design principle promote?

Which principle would best prevent a single individual from abusing system privileges?

What is NOT a goal of the encapsulation principle?

In which way does isolation provide a security advantage?

Which of the following is a characteristic of simplicity of design?

How can modularity enhance security in systems?

What is the primary challenge involved in balancing security and usability in IT?

Why might users disable or avoid using two-factor authentication (2FA)?

What defines a trust relationship in IT?

What is one benefit of establishing a trust relationship between domains?

What is the main benefit of ensuring a system provides depth in defense?

How does poor usability impact a security system?

What is meant by 'Fail-Safe Defaults' in system design?

What constitutes a secure user-device interaction?

How does the principle of 'Least Astonishment' contribute to system security?

Which factor is critical in the design of effective security measures?

What is an example of a poor design choice in security systems?

What does minimizing the 'Trust Surface' in an IT ecosystem achieve?

What role does simplicity play in secure system design?

What is the main focus of secure design principles?

Why is usability an essential aspect of secure design?

Which aspect is often overlooked in security system designs?

Which of the following best describes 'Encapsulation' in system design?

What does the principle of 'Open Design' advocate in system architecture?

How does 'Simplicity of Design' contribute to security?

What is a core benefit of modularity in system design?

What is the primary benefit of modular design in software applications?

How does the principle of 'Simplicity of Design' affect security?

Complete mediation ensures what in a security system?

What advantage does 'Minimization of Implementation' offer?

In the context of layering and defense-in-depth, what is a key feature?

What is a potential drawback of complex system designs?

Which of the following best describes 'Encapsulation' in a software context?

Which principle helps to ensure that individual modules in a software application can be updated without affecting others?

Why is testing important in the context of simplicity of design?

Separation of Duties allows a single user to have multiple privileges to effectively manage the system.

Layering and Defense-in-Depth is a strategy that strengthens security by using multiple layers of defenses.

Fail Safe Defaults means that the system will grant maximum privileges to users by default.

The principle of Least Astonishment dictates that a system's behaviour should not surprise the users.

Minimizing the Trust Surface involves increasing the number of areas where trust is required in a system.

In Layering and Defense-in-Depth, if one layer is compromised, the next layer will provide ongoing protection.

The principle of Fail Secure ensures that a system continues to operate even during a failure.

Least Astonishment is primarily concerned with user experience and not with security.

Separation of Duties can help prevent fraud by dividing tasks among different individuals.

A smaller Trust Surface generally results in a more susceptible system to attacks.

Layering and defense-in-depth allows attackers to compromise a system without overcoming multiple barriers.

Fail-Safe Defaults require that systems grant access by default unless explicitly denied.

The principle of Least Astonishment aims to create unpredictable user interactions with a system.

Minimizing the Trust Surface increases the number of components that need to be trusted, thereby enhancing security.

The concept of Fail Secure ensures that a system exposes resources to unauthorized users during a failure.

A system following Secure Design principles is likely to demonstrate a commitment to minimizing vulnerabilities.

In the context of usability, systems should be designed in a complex manner to prevent user misunderstanding.

Defensive measures such as firewalls and intrusion detection systems contribute to the depth of defense in security.

Fail-Safe Defaults are not important because systems can recover from unauthorized access automatically.

Reducing the Trust Surface can lead to a more manageable security architecture by minimizing potential vulnerabilities.

Separation of Duties is not a principle that enhances security by dividing tasks among multiple users.

Layering and Defense-in-Depth ensures that if one layer of security is compromised, other layers provide additional protection.

Fail Safe Defaults refers to setting security measures that deny access unless explicitly granted.

The Least Astonishment principle suggests that systems should operate in unpredictable ways to enhance security.

Minimizing the Trust Surface in a system reduces the number of points that can be attacked, thereby enhancing security.

Fail Secure ensures that if a system encounters an error, it operates in a secure mode limiting access.

The defense-in-depth strategy incorporates multiple security layers to counteract physical attacks only.

Separation of Duties does not typically reduce the risk of insider threats.

Layering security measures creates redundancy, making a system more robust against breaches.

The primary aim of Fail Safe Defaults is to allow maximum access to users unless restrictions are applied.

Separation of duties is an essential principle in IT security that prevents one individual from having too much control over any single action.

Layering and defense-in-depth strategies aim to rely solely on a single security measure to protect sensitive information.

Fail safe defaults ensure that a system operates in a secure manner by default when a failure occurs.

The principle of least astonishment dictates that system behavior should be surprising to users in order to improve security.

Minimizing the trust surface in an IT ecosystem involves reducing the number of trusted interactions to improve security.

A failed authentication process in a secure system should automatically grant access to users based on their previous successful logins.

Fail secure systems prioritize preserving functionality over security when a failure occurs.

The principle of least astonishment is disrupted when users encounter unexpected behaviors in a system, thereby increasing security risks.

Effective separation of duties can lead to a lack of accountability in IT security processes.