For client companies

What to ask the people who develop your software.

Many companies entrust a small software house with developing and running systems on which their work depends: a customer portal, a management application, an integration with suppliers. This page sets out the questions worth putting to that supplier in order to know whether those systems would remain usable in its absence, and describes in plain terms what a good answer should contain.

The document prints on two A4 pages and leaves space next to each question for writing down the supplier's answer by hand.

Why the question matters

A system is built in a few days. What is needed to run it often stays with one person.

With coding assistants based on artificial intelligence, a software house of two or three people can now build in a few days what once took months. That speed has a cost that is usually invisible: the information needed to run the system, that is, where it is installed, which accounts administer it, where the access keys are kept and how it is restored after a failure, remains in the memory of the person who built it.

As long as that person is available, the problem does not surface. It becomes apparent on the day they are not, because of illness, a change of job or the closure of the business. At that point the company finds that it owns a system it cannot run and that nobody else can take over quickly.

Companies that fall within the scope of the European NIS2 directive on cybersecurity are required, among their risk-management measures, to address supply chain security, including their relationships with direct suppliers (Directive (EU) 2022/2555, Article 21). Documentation of the kind described on this page can help with that; it does not, however, replace the assessments that the legislation requires of the company, which should be carried out with its own advisers.

Nine questions

The questions to put to the supplier, and what to expect in reply.

The questions require no technical knowledge. For each one, the page states in plain terms what makes a good answer. An incomplete answer does not mean that the supplier works badly: it marks a point to be clarified and, where necessary, written into the contract.

  1. Where is the documentation of the system, and when was it last updated?

    A good answer

    The supplier names a specific place, which the company can also access, and a recent date. The documentation states at least where each part of the system is installed, which external services it uses and how it is restored after a failure. A document written at the start of the project and never updated describes a system that has changed in the meantime.

  2. Who holds the access keys, and where are they kept?

    A good answer

    Access keys are the passwords and codes that allow servers, databases and services to be administered. A good answer names an encrypted store (a vault), the people who have access to it and a list of the keys by name. Files on one person's computer, spreadsheets or email messages are not adequate safekeeping.

  3. In whose name are the domain, the servers and the accounts of external services registered?

    A good answer

    A list, service by service, with the holder of each one: the domain, the hosting, the email delivery service, the payment service. Where a service is registered to the supplier, the answer states how it would be transferred to the company. An account registered to a person who can no longer be reached can be difficult to recover.

  4. What happens if the supplier is unavailable for a few weeks, or no longer available at all?

    A good answer

    A written procedure: whom to contact, how soon a reply can be expected, where the instructions for intervening are kept. The essential information on each system, that is, where it is installed, whom to call and how it is restored, is collected in a document that can be consulted even when the supplier does not respond.

  5. Who would take over, and has the company approved that person?

    A good answer

    The supplier names a specific person, with name and contact details, outside its own organisation, and the company has had the opportunity to know and approve that person. The stand-in receives personal, time-limited access, not the supplier's passwords, and hands it back at the end of the engagement.

  6. Can the company obtain its emergency keys, and how long would it take?

    A good answer

    Emergency keys are the keys that allow the company to regain control of its own systems. A good answer provides that the company can request them through a procedure and within a period set out in the contract, in a manner similar to the transfer of a domain, and that the supplier can suspend the release only for a stated reason.

  7. Can the backups actually be restored, and when was this last tested?

    A good answer

    Taking backups is not enough: restoring them must have been tested. A good answer gives the date and outcome of the last restore test actually carried out, and states how often the test is repeated. The statement "we back up every night", on its own, does not answer the question.

  8. Who has had access to the systems, and is there a record of it?

    A good answer

    The supplier can state who has access today and who has had it in the past, with dates, on the basis of a log rather than from memory. When a team member leaves the software house, their access is revoked and the keys they knew are replaced.

  9. What happens at the end of the contract?

    A good answer

    A list of what is handed over to the company, with the timing and the form: the documentation in a format readable without the supplier's software, the access keys, the code and the accounts of the services. These commitments are written into the contract and are not left to goodwill at the time.

With Symbiont

How a software house that uses Symbiont answers these questions.

Symbiont is an application for software houses that build systems with artificial intelligence. When your software house uses it, the company receives access to a web page with its own systems, without installing any software and free of charge. The list below shows what it finds there, question by question.

Question 1The documentation
The description of each system is a text file, continuity.yaml, kept in the client's code repository and updated by the coding assistant while the system is being developed. From the web page the company consults the documentation, downloads it and opens the continuity report, with the summary, the main risks and the plan to address them.
Question 2The access keys
The keys are kept in the vault, the encrypted store. The platform records only their names and where they are kept, never their values.
Question 3Account ownership
The page of each system shows to whom each service is registered, the emergency access and the second authentication factors.
Questions 4 and 5The supplier's absence and the stand-in
The page shows the trusted stand-in appointed by the software house: the company sees the person's name and confirms the appointment, or objects with a reason. If a system is not working and the software house does not respond within the waiting period (48 hours, unless set otherwise), the company requests the stand-in from the same page. The stand-in works with personal, time-limited access and, at the end, hands it back item by item. Every six months the stand-in is asked whether they are still available.
Question 6The emergency keys
The company requests them from its own page, giving a reason. They are released at the end of the agreed period: 30 days, unless the contract states otherwise. The software house can block the release only by giving a reason that the company can read, for at most 30 days at a time; a lack of response does not block the release.
Question 7The backups
For each system the page lists the checks carried out, with the date and the computer they were run from: certificates, domains, access to the code, databases and backups. The restore test rebuilds the backup in a temporary database, counts the data and then deletes it. A result is valid for 90 days; after that, the page marks it as "to be re-checked".
Question 8The access log
The log records who had access to what, and when. The company is notified when an act of sharing concerns its systems.
Question 9The end of the contract
The description remains in the client's repository and is readable without Symbiont. The terms of the final hand-over, such as timing and the transfer of accounts, remain a matter for the contract between the company and the software house.
What Symbiont does not guarantee. The checks run on the software house's computers: they record an actual check, with its date, but they are not an independent verification. The automatic release of emergency keys requires a preliminary step: the company's vault account must have been invited and confirmed by the software house. With a vault owned by the company or with Bitwarden cloud, the release remains a manual step. The details are on the Security page.
For advisers

For accountants, IT consultants and compliance consultants.

  • The list of questions may be handed to your clients freely, in print or in electronic form.
  • It is available as a PDF, in English and in Italian, on two A4 pages, with space for writing down the supplier's answers by hand.
  • A company that uses the Symbiont web page can invite its own advisers to consult it, with access that expires.
The next step

Recommend Symbiont to your software house.

If you consider that the questions on this page deserve a documented answer, you can recommend Symbiont to the software house that develops your systems. The service is free of charge for the client company; the cost is borne by the software house, for each system it manages, as shown on the pricing page.

The button opens a pre-filled message, to be addressed to your software house.

For the client company.

The film shows the web page that the company consults: the systems with their status, the checks with their dates, the emergency keys and the trusted stand-in. The data is fictional.