Third party register# Register of third parties ## Lens and screen The **Third Parties** menu centralizes name, contact, services, criticality, responsible, entrusted data, dependencies, contract/SLA, deadlines, exit plan and cyberscore. ## Manage a third party Create the form, document criticality and dependencies, then maintain contract and release. Modification or deletion is refused if the object belongs to another tenant; check the relationships before archiving. ## Supplier campaign Launch an evaluation: the version and weightings of the questionnaire are fixed. The provider responds via an expiring opaque token, without access to the tenant. An internal review is mandatory before updating the cyberscore. ## Best practices Scale frequency to criticality, require proof benchmarks, and test the release plan for strong dependencies. ## Prerequisites and responsibilities Designate an active internal owner. Gather available contract, SLA, services, data categories, dependencies and certificatio
RiskPilot
Website
FR
GitHub