MFA settings in view
Compare available enforcement settings with the answer in the supplier assessment.
Go beyond the questionnaire.
A reviewer can confirm what changed.
Inspect checks MFA, access sprawl, public exposure, and connected apps. Your reviewer sees the observed setting and the risk it creates.
We connect with read-only access to the application in scope, using your SSO provider, OAuth, or a read-only credential from your password vault. We show your team what can be checked.
We check available MFA configuration, permissions, public exposure, and connected applications.
We record observed gaps beside the vendor profile and the control your team uses to evaluate them.
We repeat appropriate checks when access or configuration changes so the review does not end with the first inspection.
An MFA answer tells you what the vendor intended. A read-only inspection of available settings tells you what the connected application shows, and gives a reviewer something concrete to investigate.
Coverbase Inspect captures the evidence; Fourth-Party Monitoring adds provider and software dependencies.
Compare available enforcement settings with the answer in the supplier assessment.
Look for permissions and connected accounts that exceed what the role requires.
Bring exposed settings into the vendor risk review with the observed evidence.
Inspect with read-only access, without changing the vendor's configuration.
What the read-only connection can show.
No. We add observed application evidence. Your questionnaire still covers controls we cannot check directly.
Read-only access to the application in scope, through your SSO provider, OAuth, or a read-only credential from your password vault. We agree on the checks with you.
Your risk team compares the observation with its controls and decides how to respond.
Yes, when read-only access to the application is in place. Settings we cannot reach stay in the questionnaire.
See what Coverbase can take on, starting with one supplier or one open question.