Risk archetypes highlight common project risks, their triggers, impacts and mitigations. Use these examples to build a comprehensive risk register and proactively manage issues before they become blockers.
Risk Statement: Logging of PII or secrets in logs exposes sensitive data and can lead to breaches. Triggers/Signals: Detection of passwords, API keys, or tokens in log entries Static code scanning reveals logging of sensitive variables Security audits or penetration tests flag insecure logging practices Incident reports of secrets being exposed Likelihood: Medium Impact: High … Read more
Risk Statement: The provider removes or changes endpoints before we migrate, breaking core functionality and causing downtime. Triggers / Signals: Deprecation notices from the provider New major version or SDK release Increase in 404/410 errors or deprecation response headers Provider emails or roadmap updates indicating sunset dates Likelihood: Medium Impact: High – potential for service … Read more
Risk Statement: Data corruption or loss occurs due to checksum drift during migration. Triggers / Signals: Checksum mismatches between source and destination High error rates during data imports Validation failures on imported records Anomalies in row counts across environments Likelihood: Medium Impact: High – corrupted data can lead to system instability and costly rework. Mitigations: … Read more