Courseiva
Control Selection →mediumMultiple Choice

CGRC Practice Question: When selecting controls, you notice that a specific NIST 800-53 control includes…

When selecting controls, you notice that a specific NIST 800-53 control includes 'assignment' statements. What is the purpose of these statements?

⚠ Common exam trap

The trap is confusing assignment statements (parameter placeholders) with control ownership or baseline categorization — candidates often assume 'assignment' means assigning a person or priority level.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

To define specific parameters for control implementation.

In NIST SP 800-53, assignment statements are placeholders within a control that the organization must fill in with specific values or parameters tailored to its environment. For example, a control might say 'the organization reviews audit records [Assignment: organization-defined frequency]' — the organization defines that frequency. This makes controls adaptable rather than one-size-fits-all.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    To define specific parameters for control implementation.

    Why this is correct

    Assignment statements in NIST 800-53 controls mark organisation-defined values, letting each organisation insert its own specifics such as frequency, roles or thresholds. They parameterise the control so it can be tailored to the organisation's risk context.

  • ✗

    To categorize the control by its priority level.

    Why it's wrong here

    Priority categorisation in NIST 800-53 comes from control baselines and the FIPS 199 impact level, not from assignment statements. The priority angle is tempting because baselines indicate which controls are essential, but assignment statements instead mark placeholders where the organisation inserts its own specific values.

  • ✗

    To link the control to a regulatory requirement.

    Why it's wrong here

    Assignment statements define organisation-defined values the implementer supplies when tailoring a control, not a mapping to regulatory requirements. The regulatory linkage is tempting because NIST 800-53 controls map to frameworks, but that mapping appears in separate catalogues, whereas assignment statements parameterise the control's own text.

  • ✗

    To assign the control to a specific system administrator.

    Why it's wrong here

    Assignment statements are not personnel assignments; they are placeholders requiring the organisation to insert specific values, such as frequency or role, when tailoring the control. Naming an administrator is tempting because controls often reference responsible roles, but that responsibility is captured in the control's own text, not its assignment statements.

About these practice questions

One of 341 original CGRC practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

You might also like

Similar CGRC questions

Written and reviewed by Johnson Ajibi, MSc IT Security

Security Systems Architect · founder of Courseiva

Last reviewed September 2026 · checked against the official (ISC)² exam blueprint

This CGRC practice question is part of Courseiva's free (ISC)² certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CGRC exam.