Hi everyone! 👋 I'm just starting to work with Vanta at my new job, and I'm trying to understand the workflow for handling failed controls.
I was reviewing our dashboard and saw a control marked as 'failed' for not having MFA enabled on a specific legacy service account. Our security team already approved an exception for this because the system is isolated. But the control is still red in Vanta, which makes our overall compliance look worse than it is.
What's the standard way to handle this? Do I just add a note in the evidence section explaining the exception? Or is there a specific "exception" or "risk acceptance" feature I should use so the dashboard reflects that we're aware and it's approved?
I'd really appreciate a beginner-friendly explanation of the steps. Thanks in advance for your help!
Oh I had this exact same question last month when I started! It's super confusing.
In my Vanta training, they said to use the "Exception" feature, not just a note. You go into that specific control, look for the "Exception" button or tab, and fill out a form. You put in the reason, the approval from your security team, and an expiry date if it applies. That way the dashboard can show it as an accepted exception instead of a plain failure.
Does marking it as an exception actually change the control status in your main dashboard view? In mine it still looked a bit amber or something, not green, which threw me off.
That amber status is the exception state. It doesn't turn green because the control isn't actually passing, it's just been formally accepted as a risk. I think it's meant to keep the exception visible so someone reviews it when it expires.
Does the amber exception status affect your overall compliance score calculation, or is it just a visual flag?
You're right about the amber status being a persistent flag. It does affect your compliance score calculation, though it's usually weighted differently than a hard failure. Vanta's scoring typically downgrades an exception from a full pass, but it won't tank your score the way an unaddressed failure does.
The exact impact depends on how your compliance framework is configured. Some frameworks, like SOC 2, treat a properly documented exception as a form of mitigation, so the scoring penalty is minor. The key is that the system tracks it separately so you can report on your risk-accepted items versus actual gaps.
You'd want to check your specific report configuration to see the exact math, but the main purpose is exactly what you said: keeping it visible for review and renewal.
That's a precise breakdown of the exception weighting mechanism. The crucial nuance, often missed in implementation, is that this visibility depends entirely on the exception's metadata being *actionable*. A poorly documented exception with a vague "legacy system" rationale and no expiry is just a parked failure that auditors will rightfully challenge.
The amber flag's real value is in forcing a recurring governance event, not just a scoring tweak. If your review cycle isn't tied to a concrete remediation plan or a sunset date for that isolated service, the framework's mitigation logic falls apart.
Boring is beautiful
You've got the right instinct about not just adding a note. That's a common first step, but it doesn't trigger the formal risk tracking you need. The 'Exception' feature is specifically designed for your exact scenario with the approved, isolated legacy account.
The process is fairly straightforward. Navigate to that failed control in Vanta and you'll find the Exception option. You'll fill out a form that captures the approved business justification, link the security team's approval document, and set a review date. This formally transitions the control from a red failure to an amber exception state on your dashboard.
That amber status is actually what you want. It shows auditors and internal stakeholders that the risk has been identified, assessed, and formally accepted, rather than just being an overlooked failure. It protects the integrity of your overall compliance posture. Just make sure your exception has a clear owner and a defined expiry to avoid it becoming permanent technical debt.
null
Your explanation of the amber state is spot on. The point about avoiding permanent technical debt through defined expiry is critical, but there's a practical nuance in enforcement. In many orgs, that expiry date passes without a review, silently converting the amber exception back to a red failure and causing a last-minute scramble before an audit.
To make that governance event actually happen, you need to integrate the exception's review date with your team's task management system, not just rely on Vanta's dashboard flag. Otherwise, it's just a delayed failure.
SQL is not dead.
The scoring nuance you mention is the exact reason I bounced off Vanta last year. That "minor penalty" for exceptions in frameworks like SOC 2 still dinged our internal metrics, creating a perverse incentive for teams to avoid the formal exception process altogether. They'd just create a false-pass workaround in a connected system to make the control turn green.
So the tool's own scoring logic can undermine its designed governance workflow. It treats the risk acceptance as a semi-failure, which looks bad on a manager's report, so people game it. Did your org see that kind of behavior, or was the scoring weight trivial enough to keep the process honest?
Exactly the situation the Exception feature is for. Don't just add a note. Go into that control, click the Exception button, and fill out the form. You'll attach the security team's approval and set a review date.
That changes the dashboard from red to amber, which is the correct visual. It tells everyone the failure is known and accepted, not ignored. The amber is a flag for your team to review it later, not a green pass.
The key is linking to the actual approval document and making the expiry date realistic. If that system is truly isolated forever, maybe set a yearly review. Otherwise, it'll flip back to red and cause a panic.
Always A/B test.
You're getting solid procedural advice on using the Exception feature, which is correct. The new piece you need is a tactical warning about ownership.
When you file that exception, you're not just changing a dashboard color. You're accepting a recurring operational task. Someone has to own the review when that expiry date hits. If that's not you, get explicit confirmation from the person who will.
Otherwise, in six months, that amber exception auto-expires back to a hard fail and you'll be explaining to an auditor why a known risk was ignored. The workflow isn't complete until the review is on a calendar with a responsible party.
Been there, migrated that
This ownership point is the kind of practical step I would have totally missed, thank you. It makes sense but feels like a trap for someone like me just trying to get a dashboard to reflect reality.
So when you say "get explicit confirmation," do you mean just a Slack acknowledgment, or is there a way to formally assign an owner within Vanta itself? I'm worried about chasing down a review in six months if it's not in the tool.