Portfolio practice / 3 MIN READ
A compensating-control case: what does next-day review leave uncovered?
Compare a fictional pre-export approval objective with next-day log review and write a bounded coverage-gap conclusion.
On this page
A proposed safeguard needs to be compared with the objective it is intended to satisfy. Evidence that the safeguard operates is different from evidence that it supplies comparable protection. This original fictional exercise keeps those questions separate.
Define the practice requirement
Fictional Cedar Analytics requires an authorized reviewer to approve bulk exports from a training reporting system before release. Its stated objective is to prevent unapproved exports from leaving the system. All records and data in this case are synthetic.
A team proposes replacing approval with a next-day review of export logs for one month. The supplied packet contains a complete log for Monday and a signed review completed Tuesday. No other restriction or safeguard is described.
Before reading on, write the original objective, proposed mechanism and time at which each mechanism acts. Avoid treating a signed review as a conclusion about adequacy.
Compare the mechanisms
| Question | Pre-export approval | Proposed next-day review |
|---|---|---|
| When does the action occur? | Before release, under the practice requirement | After exports have occurred |
| What does the supplied evidence show? | The requirement, not evidence of its actual implementation | One logged day and one completed review |
| What remains open? | Whether approval operated as required | How an unapproved export is prevented; review coverage beyond Monday; response to findings |
The Tuesday signature supports the narrow statement that the supplied Monday log was reviewed. It does not show that an unapproved export could not leave on Monday. The proposed process may detect a problem, but the case has not established comparable preventive protection.
NIST's compensating-control definition supplies context for comparing protection. It does not declare this invented alternative acceptable or require every real control to use this fictional approval process.
Write the finding and the next request
A bounded note is: “The supplied record demonstrates one next-day review. It does not establish how the alternative meets the stated prevention objective. I would request the proposed design, scope, response arrangements and evidence addressing that gap before recommending a decision.”
Do not write “the reviewer accepted the residual risk” unless the case provides that authority and decision. A technical comparison, a risk recommendation and formal authorization are separate records. Conversely, do not claim a real breach occurred: the case supplies no such event.
Revise when a new mechanism appears
Now the team says exports are held in a queue until review. This could change the timing comparison, but the statement alone is insufficient. Ask for evidence of the hold, release conditions, relevant population and how bypasses are handled. If the queue prevents release pending authorization, evaluate that design against the objective; do not keep criticizing it as unrestricted next-day detection.
Keep both versions of your note. Show which new evidence would resolve which gap and which questions remain. Do not run technical checks against a real system for this exercise.
For the resource decision, use compensating-control preparation. For a different issue, the policy-exception expiry case examines authorization dates and evidence of operation. A current date cannot repair a design gap, and an adequate design cannot extend an expired authorization.
PUT IT INTO PRACTICE
Risk & Evidence Portfolio Kit
Connect the individual document to a complete fictional case, with registers and a versioned decision memo.