Third-Party Compliance
What is Third-Party Compliance?
The requirement for vendors and partners to adhere to regulatory requirements and contractual security obligations.
Frameworks that govern third-party compliance
What the standards actually require on third-party compliance
Requirements naming third-party compliance across 2 standards, quoted from the control text.
OSFI B-131 control
Operate metrics + monitoring + continuous improvement + maturity per OSFI B-13 Domain 6 + cross-cutting expectations. Metrics, Monitoring and Continuous Improvement must (a) maintain technology and cyber risk metrics covering control coverage + maturity + inci...
OSFIB13-8 · Metrics, Monitoring, Continuous Improvement, Maturity →Agencies must monitor third-party compliance with security requirements throughout the engagement period.
IM8-TPM.3 · Third-Party Monitoring →Questions people ask about third-party compliance
What is Third-Party Compliance?
The requirement for vendors and partners to adhere to regulatory requirements and contractual security obligations.
Why is Third-Party Compliance important for compliance?
Third-Party Compliance is a key concept in Compliance and Regulatory. Understanding third-party compliance helps organizations meet regulatory requirements, reduce risk, and demonstrate due diligence during audits. Our compliance platform maps 686 frameworks with 311K cross-framework control mappings.
Which compliance frameworks address Third-Party Compliance?
Third-Party Compliance appears in the requirement text of OSFI B-13, Singapore Government Instruction Manual on ICT&SS Management (IM8). Across these standards we have identified 2 controls that name it directly, each linked to the control text on the compliance platform.
Where can I learn more about Third-Party Compliance?
Explore our compliance framework pages to see how third-party compliance applies across different standards and regulations. Our implementation guides provide step-by-step guidance, and the compliance platform offers AI-powered analysis of how this concept maps across 686 frameworks.
See how Third-Party Compliance applies across compliance frameworks
Our platform maps 686 frameworks with 311K cross-framework control mappings. Explore how this concept is addressed across standards.
Written and maintained by Gerard Blokdyk, The Art of Service.