What this policy is
Specifies the security obligations the organization places on third parties that access its systems or data — contract clauses, technical controls, monitoring, and termination.
Why every organization needs one
Third-party access is one of the most-frequently-exploited entry points. The policy is the contractual and technical baseline that makes it manageable.
What a competent Third Party Security Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- Third-party access-classification
- Required security clauses in MSAs / DPAs
- Technical-control enforcement (SSO, monitoring, JIT)
- Disconnection workflow
- Review cadence (typically annual) and version control
- Approval, sign-off and effective date
How iCompaas tracks this policy
The icompaas policy-doc producer manages this document through an 8-state lifecycle: draft → generated → internal_qa → customer_review → in_review → approved → signed (with rejected as a terminal side-state). The producer publishes a policy_doc_third_party_security_policy_signed compliance finding once at least one document of this kind reaches the signed state for the account being assessed; the finding then rolls up into every compliance framework that references this policy (see the table below).
Compliance frameworks that reference this policy
The icompaas compliance controls library links every policy document to the controls in each framework that require, evidence, or otherwise rely on it. Below: every control across every framework in the iCompaas catalogue that names this policy as part of its evidence base. Each control links to its own dedicated page with auditor-view content + implementation guidance.
| Framework | Control | Title | Component |
|---|---|---|---|
| ISO/IEC 27001:2022 | A.5.14 | Information transfer | Organizational controls |
| ISO/IEC 27001:2022 | A.5.19 | Information security in supplier relationships | Organizational controls |
| ISO/IEC 27001:2022 | A.5.23 | Information security for use of cloud services | Organizational controls |
| ISO/IEC 27001:2022 | A.6.6 | Confidentiality or non-disclosure agreements | People controls |
| ISO/IEC 27001:2022 | A.8.30 | Outsourced development | Technological controls |
| ISO/IEC 27701:2025 | A.1.3.8 | Inform third parties | Obligations to PII principals |
| ISO/IEC 42001:2023 | A.7.3 | Acquisition of data | Technological controls |
7 controls across 3 frameworks reference this policy.
About this page
This article is part of the iCompaas Policy Documents library — one page per signed-document type the icompaas policy-doc producer tracks for customer accounts. The article is intentionally framework-agnostic: a customer signing a policy of this kind gets the same regulatory benefit across every framework that references it.