What is the difference between the SIG and the CAIQ?
The SIG (Standardized Information Gathering questionnaire) is maintained by Shared Assessments and covers a broad range of risk domains, with fuller and lighter versions for different levels of scrutiny. The CAIQ (Consensus Assessments Initiative Questionnaire) comes from the Cloud Security Alliance and maps to its Cloud Controls Matrix, so it suits cloud services. Many programs use the SIG for general vendors and accept a CAIQ, often published through the CSA STAR registry, from cloud providers.
Is a SOC 2 report enough to approve a vendor?
It is strong evidence, but only if you read it. Check that the report period is recent, the scope covers the service you buy, the auditor’s opinion is unmodified, any exceptions are understood, carved-out subservice organizations are covered some other way, and the complementary user entity controls the vendor relies on you to perform are actually in place. Where the report period has ended, ask for a bridge letter.
Do we need to assess every vendor?
No, and trying to is why many programs stall. Tiering lets you put real effort into the vendors with access to sensitive data or critical operations and handle low-risk vendors with an inventory entry and standard terms. Regulators and frameworks expect oversight in proportion to risk, not identical treatment of every supplier.
What does the interagency guidance mean for a fintech?
The guidance, issued jointly by the Federal Reserve, the FDIC and the OCC, describes how banking organizations should manage third-party relationships across their life cycle. If you partner with a bank, its examiners expect the bank to oversee you, so you will see its due-diligence requests, contract terms and monitoring. A mature program of your own makes that relationship smoother and lets you manage your own vendors the same way.
Can you answer our customers’ security questionnaires for us?
Your answers are representations your company makes, so your team owns them. CyberlySecure helps you build an accurate answer library and evidence pack and reviews the difficult responses with you, so your team can reply quickly and consistently. We do not sign questionnaires or make representations on your behalf.
How does third-party risk fit with NIST CSF 2.0?
CSF 2.0 moved supply chain risk into the Govern function as its own category, GV.SC, covering strategy, roles, supplier criticality, contract requirements, due diligence, ongoing monitoring and end-of-relationship activities. Building your program around those outcomes gives you a structure that also maps cleanly to SOC 2, ISO/IEC 27001 and NIST SP 800-161.