# Verify an exit before you depend on a service

Taiga Learning · Worksheet
https://taiga.training/en/lessons/exit-portability/

Use fictional or approved information. Do not put secrets in this worksheet.

## Learning objectives
- Identify the assets and rights needed to operate without a supplier.
- Design a small exit exercise before a critical dependency develops.
- Separate export, transition, and deletion decisions.

## Exercise
A fictional supplier gives you a Git repository and a database export. List five other items you need to run the application independently. Choose one item and describe a test that would reveal a missing dependency.

## Your response
- Scenario and scope:
- Assumptions and open questions:
- Proposed answer or decision, with reasons:

## Verify your response
| Claim or criterion | Evidence or test | Result or gap | Owner |
| --- | --- | --- | --- |
| | | | |
| | | | |
| | | | |

## Next action
- Action, owner, and date:
- When will you review this response?

## Principle to retain
An exit is usable when another authorized team can understand, build, deploy, and operate the system with the assets and rights it receives.

## Sources
- [NIST: Secure Software Development Framework](https://csrc.nist.gov/pubs/sp/800/218/final)
- [Taiga docs: Data and privacy](https://docs.tai.ga/administration/data-and-privacy/)
- [Taiga docs: Integrations and environments](https://docs.tai.ga/administration/integrations-and-environments/)

This worksheet supports learning. Completing it does not itself authorize a production change.