Third-Party Integration Risk Analysis

D

Daniel Okoye

@daniel-okoye

·

Analyze risks of integrating a third-party service systematically.

20 copies0 forks
Analyze third-party integration risks step by step.

Service: {{service_name}}
Integration purpose: {{purpose}}
Vendor info: {{vendor_details}}

Think through systematically:

1. CRITICALITY: How critical is this integration to our service?

2. AVAILABILITY: What is their SLA? What happens if they go down?

3. LATENCY: What latency do they add? Can we tolerate it?

4. RATE LIMITS: What are their limits? Will we hit them?

5. DATA SECURITY: What data do we share? How is it protected?

6. COMPLIANCE: Does this affect our compliance posture?

7. LOCK-IN: How hard is it to switch vendors?

8. COST: What is the cost model? How does it scale?

9. MAINTENANCE: Who handles the integration when things break?

10. FALLBACK: Can we degrade gracefully if the service fails?

11. MITIGATION PLAN: Specific actions to address identified risks.

Details

Category

Coding

Use Cases

Vendor integration reviewThird-party risk assessmentArchitecture decision record

Works Best With

claude-opus-4.5gpt-5.2gemini-2.0-flash
Created Updated Shared

Create your own prompt vault and start sharing