HR and sales enablement · 5 min read

IT Approval of New SaaS Tools: Security Questionnaire Basics

IT approval of new SaaS tools goes faster with the right questions. Learn the security questionnaire basics for data, access, logs and exit.

Agent Q

Every handshake, a lead you can see.

QR and NFC business cards your company controls: always current, switched off when someone leaves, every scan a lead.

Book a free demoSee how it works

IT approval of new SaaS tools is a gate that sales, HR and marketing teams often find slow, and that IT teams find necessary. A clear security questionnaire makes the gate faster for everyone, because both sides know what is being asked and why.

This guide explains the basics: the questions that matter, what good answers look like and how business teams can prepare. It is written for IT heads, security teams and the managers who ask them for approval, and it is general guidance, not legal advice.

A manager reviewing a dashboard on a screen

Why SaaS approval matters

Every new tool that holds company or customer data becomes part of your risk surface. A tool used by a sales team may hold customer names, phone numbers, conversations and employee details.

Unapproved tools, often called shadow IT, are common because a manager can sign up in five minutes. The risks arrive later: no one knows where data lives, who has access or how to remove a leaver. A light but consistent approval process stops that without blocking useful tools.

Start with the business case, not the form

Before the questionnaire, IT needs context. Ask the requesting team for a one-page summary:

  • What problem does the tool solve and who will use it?
  • What data goes in: employee names, customer contacts, recordings, documents?
  • How many users, and which countries?
  • Which existing systems will it connect to?
  • What happens if it is unavailable for a day?

The answers set the depth of review. A tool that stores only public marketing content needs less scrutiny than one holding customer phone numbers.

The security questionnaire basics

Long vendor questionnaires can run to hundreds of questions. Most reviews rely on a core set. Group them in six areas.

1. Data and privacy

  • What personal data is collected and why?
  • Where is data stored, and can customers choose a region?
  • How long is data kept, and can it be deleted on request?
  • Is customer data kept separate from other customers' data?

2. Access control

  • Does the product support single sign-on and role-based access?
  • Can admins see who has access and remove it quickly?
  • Is there an off-switch for leavers?

3. Logging and audit

  • Are changes and logins logged, and for how long?
  • Can admins see who changed what and when?

4. Technical safeguards

  • Is data encrypted in transit and at rest?
  • Does the vendor perform regular security testing?
  • What third-party trackers or sub-processors are used?

5. Integrations

  • Which APIs and webhooks are offered?
  • Are webhooks signed so your systems can verify them?
  • Can the tool connect to your HR system without manual spreadsheets?

6. Continuity and exit

  • What is the incident response process and notification time?
  • Can you export your data if you leave?
  • What happens to data when the contract ends?

Tier the review by risk

Not every tool needs the same depth. A simple three-tier approach keeps the process fair and quick.

  • **Low risk:** no personal data, no integrations. A short form and a quick check are enough.
  • **Medium risk:** employee or customer contact data, limited integrations. Use the core questionnaire above.
  • **High risk:** sensitive data, deep integrations or large user numbers. Add a security call with the vendor, a document review and legal input.

Publish the tiers so business teams know in advance which path their request will take, and how long each is expected to take.

What good answers look like

Good answers are specific. "We take security seriously" is not an answer. "Data is encrypted in transit with HTTPS and each customer's data is separated" is. Look for plain statements, named features and a willingness to share documents.

Red flags include vague answers, refusal to say where data is stored, no admin audit trail and no way to remove users quickly. A vendor who struggles to answer basic questions is telling you something.

Record the decision

Whatever the outcome, write it down: who approved, on what date, with which conditions and when it will be reviewed again. Set a renewal reminder. Tools change, vendors change and the data you store changes, so approval should not be a one-time event.

Help business teams prepare

Business teams can speed up approval by doing four things before they ask.

  • Complete the one-page summary above.
  • Gather vendor documents: security overview, privacy policy and data processing terms.
  • Involve HR and legal early if employee or customer data is involved.
  • Offer a limited pilot with test data, so IT can evaluate without risk.

Our guide to writing a business case for HR, legal and IT shows how to frame the request.

USA, UAE and India considerations

In the USA, buyers often ask about security attestations and state-level privacy rules. In the UAE, data location and regional privacy rules often come up, and government-linked buyers can have stricter expectations. In India, data protection law and sector rules, especially in banking and insurance, shape the questions. Ask your legal team which rules apply to you, and write the answers into your checklist.

How Agent Q answers the common questions

For teams reviewing digital business cards, Agent Q is built around the questions above. Companies are walled off from each other, traffic uses HTTPS, there are no trackers, and every change is logged, including which admin changed a card and when.

Staff lists load from one file, and integrations include SAP SuccessFactors, Oracle HCM, Salesforce, a REST API and signed webhooks. A leaver off-switch keeps the card working but redirects it to the company page or a colleague. IT heads can read more on the page for those who approve new IT systems and the page for heads of IT security.

Personal digital card or company card?

Anyone can now make a personal digital card in a minute, and many of your people will. That is good news: clients are used to scanning and tapping. But a personal card carries the employee's own design, sends leads to them, and leaves with them. For a sales team, the card should belong to the company.

Personal digital cardCompany card (Agent Q)
Who issues itThe employee, on a personal accountThe company, for every employee
Brand and designWhatever each person picksYour brand; the layout is locked by an admin
When someone leavesThe card and the contacts leave tooOne switch: the card points to a colleague or your page
Leads from scansGo to the personCaptured for the company, counted per salesperson
Scale and controlOne person at a time, no auditThousands of staff, synced from HR, every change logged

Read more: company digital business cards · India · Dubai and the UAE · USA · a card policy you can copy

Frequently asked questions

What is a SaaS security questionnaire?

It is a list of questions an organisation asks a software vendor about data handling, access control, logging, encryption, integrations and exit. IT teams use the answers to decide whether a tool is safe to approve and to document the decision for audits.

What should IT check before approving a new SaaS tool?

Check what data the tool holds, where it is stored, who can access it, whether changes are logged, how users are removed, what integrations exist and how data can be exported. Also confirm incident handling and the contract terms for data at the end of service.

How can business teams get SaaS tools approved faster?

Send IT a one-page summary of the purpose, users and data, together with the vendor's security and privacy documents. Involve HR and legal early, and offer a small pilot with test data. Clear information shortens the review and shows respect for IT's role.

Turn every handshake into a lead you can see

Agent Q gives every employee a QR and NFC card your company controls: always current, switched off when someone leaves, and every scan can become a lead.

Keep reading.

HR and sales enablement · 5 min read

Proving Sales Training ROI to Leadership: A Simple Method

Proving sales training ROI to leadership takes a clear story, fair baselines and honest numbers. Use this method to build a case your CFO and CEO will trust.

HR and sales enablement · 5 min read

Business Case for Digital Business Cards: What Teams Ask

A business case for digital business cards must satisfy HR, legal, IT and brand. See the questions each team asks and a simple template to get approval.

HR and sales enablement · 5 min read

How to Write a Business Case for Sales Training for HR, Legal, IT

Write a business case for sales training that HR, legal and IT will support. See what each team asks, how to answer and a simple one-page template.