Access control, MFA and SSO questions: sample answers and evidence

Security Questionnaires

Author:

Chris Mabry

Short answer: Access control questions come in two kinds, and most weak answers mix them up. One kind asks how your staff get into your systems (MFA, least privilege, access reviews, offboarding). The other asks what your customer's users can do in your product (SSO through SAML or OIDC, SCIM provisioning, roles, session controls). Answer each question for the side it's asking about, say what's enforced versus optional, and attach the access control policy and, for product features, your SSO documentation.

In Iris: SSO and SCIM answers can be drafted from your own identity-provider documentation and access policy, each with a cited source.

Who this is for: security, IT and sales engineering teams answering vendor assessments.

On this page

  1. Which side is the question about?
  2. How is it usually phrased?
  3. What is the reviewer really checking?
  4. Sample answers (fictional company)
  5. What evidence should you attach?
  6. How Iris answers this about itself
  7. How Iris drafts access control answers
  8. FAQ

Which side is the question about?

Workforce access (your staff)Customer access (your product)
Typical questionsMFA for staff, privileged access, access reviews, joiner/mover/leaverSSO support, SSO enforcement, SCIM, roles, session timeout
Who owns the answerIT / securityProduct / engineering
EvidenceAccess control policy, review records, offboarding procedureProduct security docs, SSO setup guide, role matrix
Common mistakeSaying "SSO supported" when asked about staff MFASaying "MFA enforced" when asked whether customers can enforce SSO

How is it usually phrased?

Common phrasing (paraphrased)SideWhat it's really asking
"Is MFA required for all employee access to production?"WorkforceEnforced, not optional; scope includes admin consoles
"How is privileged access granted and reviewed?"WorkforceLeast privilege, approvals, review frequency
"How often are user access rights reviewed?"WorkforceA stated cadence and a record that it happens
"How quickly is access removed when someone leaves?"WorkforceOffboarding timeline and who triggers it
"Does the application support SAML or OIDC single sign-on?"CustomerProtocols and supported identity providers
"Can we require SSO and disable password logins?"CustomerAn enforcement setting, not just availability
"Do you support SCIM for user provisioning and deprovisioning?"CustomerAutomated lifecycle from the buyer's IdP
"Describe role-based access in the product."CustomerDefault roles, custom roles, granularity
"Are sessions timed out after inactivity?"CustomerConfigurable session policy

What is the reviewer really checking?

  1. Enforcement over availability. "MFA available" is weaker than "MFA enforced through our identity provider."
  2. Deprovisioning. Reviewers care most about how fast access disappears. SCIM and a written offboarding timeline answer both sides.
  3. Evidence of reviews. A policy that says "quarterly" is only half an answer; reviewers may ask for the last review's date.
  4. Granularity. Can a buyer restrict which of their users see which content? Role and permission detail matters for sensitive data.

Sample answers (fictional company)

Written for Fernhill Software, a fictional SaaS vendor. Labelled examples.

Strong answer: workforce MFA

Answer: Yes.
Comment: MFA is enforced through Fernhill's identity provider for all workforce access to production systems, cloud consoles, source code and internal tools. Password-only login to these systems is disabled. Privileged roles are granted on approval and reviewed quarterly. See Access Control Policy §3–4.

Strong answer: customer SSO and SCIM

Answer: Yes.
Comment: Fernhill supports SAML 2.0 single sign-on with any SAML identity provider, and customer admins can enforce SSO for their organization. SCIM 2.0 provisioning and deprovisioning is supported; a setup guide for our most common identity provider is available. See Product Security Overview §2.

Weak answer, rewritten: access reviews

Weak: "Access is reviewed regularly by management."

"Regularly" and "management" give the reviewer nothing to verify.

Rewritten: User access to production and to systems holding customer data is reviewed quarterly by system owners; changes are tracked in our ticketing system. Leavers lose access on their last working day, triggered by HR in our identity provider. See Access Control Policy §5.

Honest partial: SCIM for every IdP

Answer: Partial.
Comment: SCIM 2.0 is supported. We publish a step-by-step guide for one identity provider; other SCIM-capable providers are supported through the standard but without a published guide. Our team will help with setup.

What evidence should you attach?

QuestionEvidence
Workforce MFA, privileged accessAccess control policy; IdP enforcement setting (screenshot or summary)
Access reviewsReview procedure; date of last completed review
OffboardingOffboarding procedure with timeline
SSO and SCIMProduct security overview; SSO and SCIM setup guides
RolesRole and permission matrix for the product
OverallSOC 2 Type II report (logical access section), if you have one

How Iris answers this about itself

Worked example, using Iris's own verified features: Iris supports SAML single sign-on with any SAML identity provider (for example Okta or Entra) and Google Workspace OIDC, with an option to enforce SSO login and session policies (timeout, close on browser close, extend on activity). SCIM 2.0 provisions and deprovisions users and groups, with a step-by-step Okta guide, the option to lock SCIM-managed users, and an exportable provisioning audit. Roles and permissions include default Admin, Standard User and Collaborator roles plus custom roles. Each claim is one a reviewer can check in the product.

How Iris drafts access control answers

  • Drafts only from your content: your access control policy, IdP documentation, product security overview and past approved answers.
  • Every answer cites its source with a High, Medium, Low or Contradictory label. If your policy says "quarterly" and an old answer says "annually", the draft is labelled Contradictory so a reviewer settles it.
  • When your documents don't cover a question, Iris answers "There is not enough information to answer the question" and the row stays unapproved until someone writes the answer.
  • Route the right half to the right team: assign workforce questions to IT or security and product questions to engineering, from the same project.
  • Tag-based access lets you restrict who in your own company sees sensitive security content in Iris.

Iris is rated 4.8/5 on G2 from 92 reviews (November 2026). Try Iris free on an RFP you've already answered, or a security questionnaire you've already completed.

FAQ

Is "SSO supported" enough?
No. Say which protocols, whether admins can enforce it, and whether SCIM handles deprovisioning.

What's the difference between SSO and MFA in a questionnaire?
SSO centralizes login in the buyer's identity provider; MFA adds a second factor. Buyers often enforce MFA in their own IdP and then require SSO into your product.

Should we say "Yes" to MFA if it's optional for customers?
Answer the question asked. If it asks about your staff, answer for staff. If it asks whether customers can enforce MFA, explain that enforcement happens through SSO in their IdP, if that's how your product works.

How often should access reviews happen?
Quarterly is common for production and sensitive systems, but state what your policy actually says. See NIST SP 800-63B for authentication background.

Where do offboarding questions overlap with HR?
Termination timing and device return. See employee security questions.

See it live

Respond to RFPs
without the grind.

Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.