Describe RBAC and why it's preferred over DAC in DSAC contexts.

Prepare for the DSAC Annex F Test with comprehensive flashcards and multiple choice questions. Access hints and explanations for each question to ensure you’re ready for your exam!

Multiple Choice

Describe RBAC and why it's preferred over DAC in DSAC contexts.

Explanation:
Role-Based Access Control assigns permissions to roles rather than to individual users, so access is granted based on a person’s job function. In data security contexts, this means you create roles that reflect what someone needs to do with data—such as data analyst, data steward, or data reader—and attach only the necessary permissions to each role. When a person changes roles, you move them to a different role rather than recalibrating permissions for many accounts, which helps prevent privilege creep and makes onboarding and offboarding cleaner. This approach also makes audits straightforward. You can review exactly what each role permits and which users hold those roles, giving a clear, centralized view of who has access to what. It supports enforcing least privilege and separation of duties by keeping permissions tightly coupled to defined responsibilities rather than to individual identities. Dynamic, session-based or identity-only approaches don’t provide the same scalable, policy-driven control. Granting permissions per session or basing access on identity alone can lead to broader, harder-to-trace access or ad hoc privilege spread, making audits more complex.

Role-Based Access Control assigns permissions to roles rather than to individual users, so access is granted based on a person’s job function. In data security contexts, this means you create roles that reflect what someone needs to do with data—such as data analyst, data steward, or data reader—and attach only the necessary permissions to each role. When a person changes roles, you move them to a different role rather than recalibrating permissions for many accounts, which helps prevent privilege creep and makes onboarding and offboarding cleaner.

This approach also makes audits straightforward. You can review exactly what each role permits and which users hold those roles, giving a clear, centralized view of who has access to what. It supports enforcing least privilege and separation of duties by keeping permissions tightly coupled to defined responsibilities rather than to individual identities.

Dynamic, session-based or identity-only approaches don’t provide the same scalable, policy-driven control. Granting permissions per session or basing access on identity alone can lead to broader, harder-to-trace access or ad hoc privilege spread, making audits more complex.

Subscribe

Get the latest from Examzify

You can unsubscribe at any time. Read our privacy policy