Information security for software delivery

ISO/IEC 27001
ISO/IEC 27001 certified
The chain
The assignment has to reach the person typing
In most legal systems, rights in creative work start with the person who created it and move only by operation of law or by written agreement. Some jurisdictions vest an employee's work in the employer automatically; many do not extend that to contractors, and the rules differ from country to country. Wording in the work-for-hire family is a category to ask about, not a universal fact — which is why "we paid for it" is a feeling, not a theory of ownership anywhere.
That is why the protection is a chain with two links, and both must hold. The first is your contract with the vendor, assigning the work product to you. The second is the vendor's contracts with the people who actually write the code — employees or subcontractors — assigning their work to the vendor so it has the rights to pass on. A vendor with a strong clause facing you and informal arrangements behind it is offering you a chain with a missing link, and the gap belongs to whoever typed the code. To be clear about what this page is: a map of the categories, written so you know which questions to put to your own counsel — not legal advice, and not a substitute for it.
The categories
The contract questions to settle before the rate card matters
Four categories, each phrased as the question to ask. A vendor comfortable with these questions has answered them before; hesitation is itself information.
Assignment timing
Does ownership vest in us as the work is created, or only on acceptance or final payment?
What a good answer protects: No window in which a commercial dispute clouds title to your own code.
The chain below the vendor
Are the engineers employees or contractors, and do their own agreements assign their work to the vendor?
What a good answer protects: No individual quietly retains rights in a module you believe you own.
Subcontracting consent
Can work be passed to third parties without our written consent, and do the same terms bind them?
What a good answer protects: The chain cannot grow links you have never seen.
Exit provisions
On termination for any reason, what happens to work in progress, documentation, credentials and access — and by when?
What a good answer protects: Leaving is an administrative task rather than a negotiation you enter without strength.
The technical half
Design the repositories so nothing ever needs handing back
The contract says who owns the code; the account structure decides who holds it. Get the second right and the first is rarely tested.
A flow of four steps — accounts created in the buyer's tenancy, engineers invited with named access, all work kept inside, departure handled as revocation — with a branch for the vendor that insists on hosting the code itself.
- 01
Your tenancy from day one
Repository, pipeline and cloud accounts are created in your name before the first commit, even when the vendor does the creating.
- 02
Engineers invited in
Named, individual accounts granted into your systems — no shared logins, and no vendor-side mirror of the repository.
- 03
The work stays inside
Branches, reviews, builds and documentation all live in your tenancy, so the history of the work is yours along with the work.
- 04
Departure is revocation
The engagement's last day is spent removing accounts, not requesting deliverables — there is nothing on the other side to request.
When a vendor insists on its own repository
Treat the insistence as a finding. Sometimes there is a workable reason; more often it means their delivery machinery assumes possession of your code, and you should ask what else would sit on their side of the line.
Our role
We accept these terms about ourselves before we propose them
- 01
The chain, shown
Assignment to the client in our contract, and employment agreements behind it that assign the engineers' work to us — the two links your counsel will want to see, available for their review.
- 02
Your tenancy, our default
We work inside client-held repositories and accounts as standard practice, so the technical arrangement matches what the contract promises rather than contradicting it.
- 03
Exit terms at signing
What happens to work in progress, documentation and access on termination is written into the agreement on day one, because those terms are cheap to grant before a dispute and expensive after.
The enforceable wording, the governing law and the jurisdictional questions belong with your counsel; our part is a structure clean enough that their review confirms rather than repairs.
Common questions
What buyers ask
Is a work-for-hire clause enough on its own to own offshore code?+
Treat it as one category of wording, not as a complete answer. Doctrines in that family exist in some jurisdictions with specific conditions, apply differently to employees and contractors, and may not exist at all in the countries your engagement actually touches. That is exactly why the reliable pattern is an express assignment — wording that transfers the rights to you regardless of which default doctrine would otherwise apply — running through both links of the chain. Which construction is enforceable across your contract's jurisdictions is a question for your counsel; this page's job is to make sure you ask it.
Does it matter whether the vendor's engineers are employees or contractors?+
Yes, because the second link of the chain often works differently for each. In many legal systems an employee's work product moves to the employer with relatively little wording, while a contractor's stays with the contractor unless a written agreement assigns it. A vendor staffing your project with freelancers under informal arrangements can present you a strong contract while holding a broken chain behind it. You do not need to audit anyone's HR files; you need the vendor to warrant, in the contract, that everyone who touches your work is bound by an assignment to the vendor — and to tell you when subcontractors are involved at all.
What should the exit provisions cover for work that is half finished?+
Three things, written before you sign rather than negotiated during a separation. First, that work in progress is assigned and delivered in whatever state it exists — an unfinished branch you own is worth more than a finished one you have to argue about. Second, a handover obligation with a named duration: documentation brought current, credentials transferred, and reasonable availability for questions. Third, the mechanics of access: whose accounts get closed and when. If you have followed the tenancy design on this page, that last item is nearly empty, which is the point — the exit clause you never need to enforce is the one that worked.
In this cluster
Walk the chain with your counsel
A checklist of the assignment, subcontracting and exit questions to put to any vendor, with our own answers to each provided in writing.
Start the conversation