What is the primary risk of having an inaccurately defined authorization boundary?
An inaccurate authorization boundary omits systems, data or interconnections from the assessment scope, so those assets receive no security evaluation and their vulnerabilities remain unaddressed. This directly matches the risk of unprotected assets falling outside assessment scope.
Why this answer
The authorization boundary defines exactly which systems, components, and data are included in a security assessment and authorization decision. If that boundary is drawn inaccurately — too narrow or misaligned with the actual system — assets and vulnerabilities that should have been assessed fall outside the scope. Those excluded assets remain unprotected and unmitigated, which is the core risk the question is testing.
Exam trap
CGRC often tests the misconception that authorization boundary issues are procedural or administrative concerns, when the actual risk is always about assets and vulnerabilities escaping security assessment and oversight.
How to eliminate wrong answers
Option A is wrong because hardware procurement cost is a budgeting concern, not a security risk tied to boundary definition; an inaccurate boundary does not inherently increase hardware spend. Option B is wrong because the SDLC is a development process framework — a poorly defined authorization boundary does not constitute an SDLC violation, and the two concepts are unrelated in this context. Option C is wrong because annual performance reviews are an HR function with no technical or security linkage to authorization boundary definition.