TSA Security Schedule & Cyber Clause Library
Draft the security schedule for a transition services agreement: sample clause wording for security standards, shared-system access, incident notification, audit rights, data return and exit, a checklist of obligations by party, and a register of every transitional service. All clause text is sample wording to discuss with counsel.
Template & sample only · See the sample ↓ — a structured starting point with sample content, not legal, audit, certification or investment advice.
Draft the security schedule for a transition services agreement (TSA): sample clause language for the cyber topics that usually cause disputes, a checklist of security obligations by party, and a register of each transitional service with its security owner and exit dependency. Every clause here is SAMPLE wording to discuss with counsel — not legal advice.
- Provider privileged access to recipient data restricted, logged and reportable
- Shared credentials, certificates and keys rotated at separation of each service
- Exit criteria per service agreed (what “separated” means and who signs it off)
Your context
Clause library — operating the TSA securely
Each field holds SAMPLE wording to start the conversation with counsel. Replace party names, timelines and standards with what your deal team actually agrees.
Clause library — incidents, audit and exit
Risk allocation topics for the purchase agreement
These usually sit in the sale and purchase agreement rather than the TSA. Listed as topics and sample framing for counsel — the exact wording and limits are a negotiation for your legal and deal advisers.
Security obligations by party
Tick off which obligations the draft TSA actually allocates. The tag shows who usually carries it.
Security baseline for the Services defined and attached as an annexProvidermaterial
Mutual incident notification with a fixed timeline and a named contact each sideBothmaterial
Cooperation in investigations, including forensic access to logs and imagesBoth
Cross-party access lists reviewed monthly; removal within one business dayBothmaterial
Provider privileged access to recipient data restricted, logged and reportableProvidermaterial
Data segregation and documented shared data storesProvider
Vulnerability remediation timelines and monthly reportingProvider
Log retention and log-extract delivery on requestProvider
Subcontractor notice and flow-down of security termsProvider
Audit / assurance right defined, with frequency and who paysRecipient
Security change control: neither side changes shared controls without noticeBoth
Recipient obligations: its users follow the provider’s acceptable-use and security policiesRecipient
Data return format, deletion and deletion certificate per serviceProvidermaterial
Shared credentials, certificates and keys rotated at separation of each serviceBothmaterial
Domain, DNS and email-routing transfer obligations listedProvider
Exit criteria per service agreed (what “separated” means and who signs it off)Bothmaterial
Extension right and price if separation slipsRecipient
Joint TSA security governance forum with a meeting cadenceBoth
TSA service register
One row per transitional service. The exit dependency is what has to exist on the recipient side before the service can end.
Loading…
TL;DRWhat this template gives you
4 points
- During a TSA the seller keeps running systems the buyer now depends on, and the two companies share access, data and risk. Vague security terms are where TSA disputes start.
- A clause library with sample wording for 13 topics: security standards, shared-system access, data segregation, vulnerability management, logging, subcontractors, incident notification, audit rights, data return, exit assistance, warranties, indemnities and insurance.
- 18 obligations tagged by party (provider, recipient, both) so you can see what the draft actually allocates, plus a service register that flags services with no security owner.
- Every clause is marked as sample wording to discuss with counsel. This is not legal advice.
Frequently asked questions
What security terms belong in a transition services agreement?
At minimum: the security baseline the provider must keep, how each side accesses the other’s systems, incident notification in hours with named contacts, audit or assurance rights, data segregation, return and deletion of data at the end of each service, rotation of shared credentials, and exit criteria per service. The template gives sample wording for each to take to counsel.
Can I paste these clauses into my TSA?
No. They are sample wording to start a discussion with your legal advisers, who will adapt them to the deal, the governing law and the rest of the agreement. Warranty, indemnity and insurance topics usually sit in the purchase agreement rather than the TSA.
Is this a finished document I can rely on?
No. Every tool in this suite is a template with sample content. It gives you a structured, editable starting point and generates a document from your own answers, but it is not legal, audit, certification, investment or professional advice. Review and adapt the output, and have it checked by the appropriate specialist before you rely on it.
Who can use it?
The page and sample are public. Customising the template is Pro; a free account gets 3 runs in total, shared across every Pro tool, and the generated document is free to view on the page. Download is Pro: downloading or copying the document (Word, PDF, Markdown, CSV) is never part of the free runs. Pro is $5/month or $40/year. Your work is saved in your own browser.
More security tools
The tools people use most on PlayCISO.
Catch injected instructions hiding in content your AI agent should only read.
Score your readiness against the first international standard for AI security threats.
Critical CVEs across 21 major vendors, month by month — and what the 2026 surge means.
Build an ordered ruleset, replay labelled packets and catch shadowed and any-to-any rules.
Self-assess all six Functions, from Govern to Recover, and see your weakest one.
Search 172 threat actors across Microsoft, CrowdStrike, Mandiant and community names.