Chapter 10 · Reading 2 of 5
Making a temporary policy exception accountable
Security+ SY0-801 · Objectives 5.1, 5.2
A laboratory instrument depends on a workstation that cannot immediately receive a required update. Turning the workstation off would interrupt an ongoing study. Leaving it connected indefinitely makes the security standard meaningless. Who can make a time-limited decision, and what would make that decision defensible?
Describe the departure from policy
Name the exact requirement, affected asset and reason normal compliance is temporarily infeasible. Ask the system owner what function must continue and what alternatives were considered. A department that simply prefers its existing process has a different case from a laboratory awaiting a vendor-certified replacement. The exception should be narrow enough that another department cannot use it as blanket permission.
Estimate what may go wrong during the exception period and who would bear the consequences. Separate the administrator implementing the safeguard from the business owner authorized to accept residual risk. A technician can confirm that a workstation is isolated. A director with the proper authority can decide whether the remaining risk is acceptable for the institution. Give the approver a clear account of both the proposed protection and its limits.
Give the exception a way to end
Document an expiry date, a corrective plan, a named owner and evidence that compensating controls still operate. For the laboratory, this might include an approved network restriction, a monitored maintenance path and regular review of the device inventory. Define what would trigger immediate reassessment, such as a new remote access dependency or evidence that the restriction no longer holds. Verify the safeguards after an unrelated network change as well as on the scheduled date.
At expiry the owner needs a decision. Retire the workstation, bring it into compliance, or submit a renewed justification under the current conditions. A pending replacement purchase does not automatically extend permission to operate. Report overdue exceptions separately so they remain visible to the people responsible for the risk.
A compensating control needs an owner too
Suppose the director accepts the laboratory exception on the condition that the network team reviews device connections weekly. The network team later moves to a new monitoring platform. The weekly report now covers ordinary workstations but excludes the instrument’s segment. The exception file still contains every signature. The condition supporting the director's decision has changed.
Ask the control operator to show the specific asset in the new report and demonstrate where an unexpected connection would be routed. Record the result and revisit the decision if evidence is missing. A compensating control with a failed data source provides less protection than its name implies. That is why exception reviews need an operational participant alongside the manager who accepts the remaining risk.
Read the register as a management tool
Several laboratories requesting the same exception may reveal a procurement or architecture problem. Look for patterns in dependency, duration and consequence. A shared replacement program may reduce residual exposure more effectively than repeated individual reviews. If the delay comes from a supplier, bring the requirement, dates and impact into the next vendor assessment. The record now connects a technical constraint to a decision about spending, accountability and service continuity.
Inspect the three records, then use the evidence to answer the question.
1. Approval
Owner approves exception E12 through September 30.
2. Expiry
Compensating review is required every Friday.
3. Current state
October inventory still lists E12 as active.
Apply the reading
What evidence would justify ending a temporary exception?
Compare your reasoning
Verify that the original requirement is met or the affected asset is retired and that temporary permissions are removed.