r/ISO27001 • u/Varmo_ISMS • 20h ago
๐ Audit & Compliance Residual risk acceptance (6.1.3 f): what a weak sign-off looks like vs. one that holds up
6.1.3 f wants the risk owners to approve the treatment plan and accept the residual risks. The standard leaves the form open, and that's where it tends to get thin.
Weak, in my book:
One signature from the CISO under the whole risk register.
"Accepted" as a status in a spreadsheet, no name, no date.
Accepted by someone with no budget or authority over the thing at risk.
Residual risk above your own acceptance criteria, accepted anyway, no reason given.
One that holds up:
Risk: two freelancers work on customer data from their own unmanaged laptops.
Residual risk: medium, criteria say low or below.
Accepted by: head of operations, who owns the freelancer contracts.
Reason: both contracts end in March, enrolling the devices for 4 months isn't worth it.
Conditions: access through the virtual desktop only, no local downloads.
Valid until: 31 March, or sooner if a contract gets extended.
Three positions I'd defend:
A sign-off on the treatment plan is enough, you don't need a form per risk. But every risk owner has to sign for their own risks and the residual levels have to be in what they sign. One CISO signature only works if the CISO really owns all of them.
Above the criteria, the risk owner can't decide alone. Top management set the criteria (6.1.2 a), so an exception goes back to them, or the criteria say upfront who can approve one.
An acceptance that depends on conditions needs a date. Without one it's permanent, and nobody notices when the contract gets extended.
Where does your auditor or CB see it differently? Especially the second one, I've seen that argued both ways.

