Seed-stage B2B SaaS startup
Sample for a fictional organisation · 4,125 words[Company] Cloud Services Policy
- Version: 1.0
- Owner: CTO
- Approved by: CEO
- Effective date: [Effective date]
- Next review date: [Review date]
3. Shared Responsibility
A supplier runs each cloud service, and [Company] decides how it uses the service. Using a cloud service does not pass [Company]'s responsibility for its information to the supplier. The table gives each part of a cloud service, who is responsible for it and what [Company] does about it.
| Part of a cloud service | Who is responsible for it | What [Company] does |
|---|---|---|
| The buildings, equipment and networks that the service runs on, and the software of the service itself | The supplier | Finds out what the supplier is responsible for where section 4 requires it |
| The systems that [Company] builds or runs in a cloud account | [Company] | Protects and maintains them as it does every other system of its own |
| The accounts that staff hold with the service, and what each account is able to do | [Company] | Opens, limits and closes them under section 6 |
| The settings of the service that [Company] is able to change | [Company] | Sets and checks them under section 7 |
| The information that [Company] puts into the service, and who it is shared with | [Company] | Decides what goes in and where it is held under section 8 |
| Copies of that information from which it can be restored | The supplier and [Company] | Finds out what the supplier keeps where section 4 requires it, and keeps a copy of its own where section 8 requires one |
| The devices that staff use to reach the service | [Company] | Protects them as it does every other device used for its work |
A supplier may divide the parts differently. Before a cloud service that will hold confidential information is used, the person who will be its service owner reads what the supplier publishes about the parts it is responsible for and the parts it leaves to [Company], as section 4 requires. Where the supplier leaves to [Company] something that the table does not give to [Company], [Company] is responsible for that as well, and it goes in the cloud service record.
[Company] treats a report or a certificate on a supplier's security as evidence about the parts that the supplier is responsible for, and never as evidence about the parts that the table gives to [Company].
5. The Cloud Service Record
[Company] keeps a cloud service record, which lists every cloud service that this policy covers. The CTO makes sure that it is kept, and the entry for each cloud service holds the following.
- Service: the cloud service, its supplier, what [Company] uses it for and whether [Company] could carry on its work without it.
- Service owner: the member of staff responsible for [Company]'s use of the service.
- Information: the kinds of [Company]'s information that the service holds, and whether any of it is confidential.
- Approval: who approved the service and the day it was approved. For a cloud service that was in use before it was approved, the entry says so and holds any decision that the CTO made about it under section 4.
- Responsibilities: where the supplier's description of the parts it is responsible for is kept, and anything that the supplier leaves to [Company] and that the table in section 3 does not give to [Company].
- Accounts: the members of staff who administer [Company]'s account with the service.
- Location: the countries in which the supplier holds [Company]'s information, and any choice of them that [Company] made under section 8.
- Keys: whether the supplier or [Company] holds the keys that encrypt [Company]'s information in the service, and any decision about them under section 8.
- Copies: what copies of [Company]'s information the supplier keeps, how long after something is deleted the supplier is able to restore it, any copy that [Company] keeps under section 8 or decision under that section that it needs none, and the day that restoring from a copy that [Company] keeps was last tried.
- Settings: the day the settings were last checked under section 7, what the check found, and any setting that the service does not offer, with the decision made about it.
- Leaving: how [Company] takes its information out of the service and in what form, how long the information stays available after [Company] stops using the service, and, for a cloud service that [Company] could not carry on its work without, the day [Company] last confirmed under section 8 that it is able to take it out.
- Exceptions: any exception under section 10 that applies to the service, and the day the exception ends.
- Ending: the day [Company] stopped using the service, the day the steps in section 9 were completed and any confirmation from the supplier that it has deleted [Company]'s information.
Responsibilities, Location, Keys and Settings are filled in for a cloud service that holds confidential information. Copies and Leaving are filled in for a cloud service that holds confidential information or that [Company] could not carry on its work without. Any of these six fields that this paragraph does not have filled in for a cloud service may be left empty for it.
The cloud service record may be kept as more than one list and in any tool. A list that [Company] keeps under another of its rules, such as a list of its suppliers or of its assets, is part of the cloud service record for the cloud services it covers, provided that the lists between them hold, for every cloud service, what this section requires. No password, key or other secret is written in the cloud service record, and the entry for a cloud service that [Company] no longer uses stays in it.
Every cloud service has one service owner, who may be the member of staff responsible for its supplier under [Company]'s rules for suppliers. When a service owner leaves [Company], or their work changes so that they are no longer responsible for a cloud service, the CTO names a new service owner on or before their last working day or the day the change takes effect. Where a cloud service in the cloud service record is found to have no service owner, the CTO is told, and within 5 working days names one.
7. Settings
The service owner of a cloud service that holds confidential information makes sure that its settings meet this section. They are set before confidential information is put into the service or, for a cloud service that section 4 lets carry on being used, within the time that section 4 gives.
- Sign-in: staff sign in to the service as [Company]'s rules for passwords and multi-factor authentication require, and a way of signing in that those rules do not allow is turned off wherever the service lets it be turned off.
- What each account can do: each account is able to see and change only what the person's work needs, and no more people are able to administer the service than the work needs.
- Sharing: information in the service is shared outside [Company] only with the people and the services that the work needs. Sharing with anyone who holds a link is turned off for confidential information, and for other information unless the service owner has decided that the work needs it.
- Open to the internet: nothing in the service that holds confidential information is able to be read from the internet without signing in.
- Record of activity: the service's own record of sign-ins and of changes to its settings is turned on wherever the service offers one.
- Connections: the only services connected to the service are those approved under section 6.
- New features: a feature that uses [Company]'s information in a new way, such as an AI feature, is turned on only after the service owner has confirmed what the feature does with that information.
Where a cloud service does not offer one of these settings, its service owner records that in the cloud service record, and the CTO, or a person the CTO has named in writing, decides whether confidential information is put into the service and records the decision.
The CTO makes sure that the security settings of each service that a supplier runs for [Company], and that holds its confidential information, are checked when the service is first set up and at least every 12 months. For a cloud service that section 4 lets carry on being used, the first check is made when its settings are set under this section. Each check compares the settings of the service with this section. A setting that the service offers and that does not meet this section is put right or has an exception under section 10, and the day of the check and what it found go in the cloud service record.
Where a service owner learns that a supplier has changed a cloud service in a way that affects one of these settings, or has added a feature that uses [Company]'s information in a new way, the service owner tells the CTO and checks the settings again within 30 days.
A change to the settings of a cloud service that is a change under [Company]'s rules for change management is made as those rules require.
Read the full example
[Company] Cloud Services Policy
- Version: 1.0
- Owner: CTO
- Approved by: CEO
- Effective date: [Effective date]
- Next review date: [Review date]
1. Purpose and Scope
This policy sets how [Company] uses cloud services: who is responsible for what when a supplier runs a service for [Company], what is checked before a cloud service is used, what [Company] records about each one, how accounts with a cloud service are opened and used, how its settings are set and checked, where [Company]'s information is held and how copies of it are kept, and what is done when [Company] stops using a cloud service. It sits beneath [Company]'s information security policy.
This policy applies to everyone who is given access to [Company]'s systems, accounts or information: employees, contractors and anyone else working on its behalf. This policy calls them staff.
This policy covers every cloud service that is used for [Company]'s work or that holds [Company]'s information. It covers a cloud service whether or not [Company] pays for it, including a free service, a service on trial and a service that one member of staff signs up to for [Company]'s work. The supplier of a cloud service is also managed under [Company]'s rules for suppliers, where those rules cover the supplier. Where another of [Company]'s rules is stricter than this policy on the same matter, the stricter rule applies.
- Cloud service: a service that a supplier runs on its own systems and that [Company] uses over the internet through an account.
- Cloud account: an account with a cloud service in which [Company] builds or runs systems of its own, such as servers, databases and networks.
- Cloud service record: the record of [Company]'s cloud services, which section 5 describes.
- Service owner: the member of staff named in the cloud service record as responsible for [Company]'s use of a cloud service.
2. Roles and Responsibilities
- The CTO: keeps this policy and reviews it under section 10; makes sure that [Company] keeps the cloud service record that section 5 describes; makes sure that the checks in section 4 are made before a cloud service is used or, for a cloud service that section 4 lets carry on being used, within the time that section 4 gives; names a service owner where section 5 requires it; gives the approvals, takes the decisions and makes the confirmations that this policy gives to the CTO; makes sure that the settings of cloud services are checked under section 7; and approves exceptions under section 10. The CTO may name in writing a person to carry out any of these tasks other than approving exceptions, and remains responsible for them. Where this policy has staff report something to the CTO, or has the CTO told of something, a person the CTO has named in writing may be told instead.
- The CEO: approves this policy and each change to it under section 10, and approves an exception that the CTO asks for, under section 10.
- Service owners: make the checks that section 4 gives them, keep the entries for their cloud services in the cloud service record up to date, make sure that sections 6 to 9 are followed for each of their cloud services, and tell the CTO of the changes that sections 7 and 8 describe.
- All staff: use for [Company]'s work only a cloud service that section 4 allows to be used, open and use an account with a cloud service only as section 6 allows, put confidential information only into a cloud service that section 8 allows it to be put into, and tell the CTO of any cloud service in use that section 4 requires to be reported.
3. Shared Responsibility
A supplier runs each cloud service, and [Company] decides how it uses the service. Using a cloud service does not pass [Company]'s responsibility for its information to the supplier. The table gives each part of a cloud service, who is responsible for it and what [Company] does about it.
| Part of a cloud service | Who is responsible for it | What [Company] does |
|---|---|---|
| The buildings, equipment and networks that the service runs on, and the software of the service itself | The supplier | Finds out what the supplier is responsible for where section 4 requires it |
| The systems that [Company] builds or runs in a cloud account | [Company] | Protects and maintains them as it does every other system of its own |
| The accounts that staff hold with the service, and what each account is able to do | [Company] | Opens, limits and closes them under section 6 |
| The settings of the service that [Company] is able to change | [Company] | Sets and checks them under section 7 |
| The information that [Company] puts into the service, and who it is shared with | [Company] | Decides what goes in and where it is held under section 8 |
| Copies of that information from which it can be restored | The supplier and [Company] | Finds out what the supplier keeps where section 4 requires it, and keeps a copy of its own where section 8 requires one |
| The devices that staff use to reach the service | [Company] | Protects them as it does every other device used for its work |
A supplier may divide the parts differently. Before a cloud service that will hold confidential information is used, the person who will be its service owner reads what the supplier publishes about the parts it is responsible for and the parts it leaves to [Company], as section 4 requires. Where the supplier leaves to [Company] something that the table does not give to [Company], [Company] is responsible for that as well, and it goes in the cloud service record.
[Company] treats a report or a certificate on a supplier's security as evidence about the parts that the supplier is responsible for, and never as evidence about the parts that the table gives to [Company].
4. Approving a Cloud Service
Apart from a cloud service that this section lets carry on being used, no cloud service is used for [Company]'s work, or given [Company]'s information, until it has been approved and the checks in this section have been made. The approval is given under [Company]'s rules for suppliers where they cover the supplier and, where they do not, by the CTO or a person the CTO has named in writing. This applies to a free service and to a service on trial as it does to one that [Company] pays for.
- The member of staff who wants [Company] to use a cloud service says what it will be used for, what information it will hold, whether [Company] could carry on its work without it once it is in use, and who its service owner will be. These go in its entry in the cloud service record.
- For a cloud service that will hold confidential information, the person who will be its service owner finds out, from what the supplier publishes or says in writing, which parts of the service the supplier is responsible for and which it leaves to [Company], in which countries the supplier holds the information, and whether the supplier or [Company] holds the keys that encrypt it. That person enters these under Responsibilities, Location and Keys in the cloud service record before the service is used.
- For a cloud service that will hold confidential information, or that [Company] could not carry on its work without, the person who will be its service owner finds out in the same way what copies of [Company]'s information the supplier keeps, how long after something is deleted the supplier is able to restore it, how [Company] takes its information out of the service and in what form, and how long the information stays available after [Company] stops using the service. That person enters these under Copies and Leaving in the cloud service record before the service is used.
- Where the supplier does not say in which countries it holds the information, or gives [Company] no way to take its information out of the service, the cloud service is used for confidential information only under an exception approved under section 10.
- A cloud service is approved for the information that the request describes. Before it is used for confidential information that it was not approved for, the checks in this section are made for that information.
- A cloud service that [Company] already uses on the day this policy takes effect may carry on being used for the information it already holds. Within 3 months of that day, the checks in this section are made for it, it is entered in the cloud service record with a service owner, and it is brought to meet sections 6 to 8.
- A cloud service that staff started to use without approval after the day this policy takes effect, or that is found in use after those 3 months and is not in the cloud service record, is reported to the CTO, who decides whether its use stops until it has been approved. Where the CTO decides that its use carries on, it carries on only for the information it already holds. Within 30 days of the report, the cloud service is approved, entered in the cloud service record and brought to meet sections 6 to 8, or [Company]'s information is taken out of it and section 9 is followed.
5. The Cloud Service Record
[Company] keeps a cloud service record, which lists every cloud service that this policy covers. The CTO makes sure that it is kept, and the entry for each cloud service holds the following.
- Service: the cloud service, its supplier, what [Company] uses it for and whether [Company] could carry on its work without it.
- Service owner: the member of staff responsible for [Company]'s use of the service.
- Information: the kinds of [Company]'s information that the service holds, and whether any of it is confidential.
- Approval: who approved the service and the day it was approved. For a cloud service that was in use before it was approved, the entry says so and holds any decision that the CTO made about it under section 4.
- Responsibilities: where the supplier's description of the parts it is responsible for is kept, and anything that the supplier leaves to [Company] and that the table in section 3 does not give to [Company].
- Accounts: the members of staff who administer [Company]'s account with the service.
- Location: the countries in which the supplier holds [Company]'s information, and any choice of them that [Company] made under section 8.
- Keys: whether the supplier or [Company] holds the keys that encrypt [Company]'s information in the service, and any decision about them under section 8.
- Copies: what copies of [Company]'s information the supplier keeps, how long after something is deleted the supplier is able to restore it, any copy that [Company] keeps under section 8 or decision under that section that it needs none, and the day that restoring from a copy that [Company] keeps was last tried.
- Settings: the day the settings were last checked under section 7, what the check found, and any setting that the service does not offer, with the decision made about it.
- Leaving: how [Company] takes its information out of the service and in what form, how long the information stays available after [Company] stops using the service, and, for a cloud service that [Company] could not carry on its work without, the day [Company] last confirmed under section 8 that it is able to take it out.
- Exceptions: any exception under section 10 that applies to the service, and the day the exception ends.
- Ending: the day [Company] stopped using the service, the day the steps in section 9 were completed and any confirmation from the supplier that it has deleted [Company]'s information.
Responsibilities, Location, Keys and Settings are filled in for a cloud service that holds confidential information. Copies and Leaving are filled in for a cloud service that holds confidential information or that [Company] could not carry on its work without. Any of these six fields that this paragraph does not have filled in for a cloud service may be left empty for it.
The cloud service record may be kept as more than one list and in any tool. A list that [Company] keeps under another of its rules, such as a list of its suppliers or of its assets, is part of the cloud service record for the cloud services it covers, provided that the lists between them hold, for every cloud service, what this section requires. No password, key or other secret is written in the cloud service record, and the entry for a cloud service that [Company] no longer uses stays in it.
Every cloud service has one service owner, who may be the member of staff responsible for its supplier under [Company]'s rules for suppliers. When a service owner leaves [Company], or their work changes so that they are no longer responsible for a cloud service, the CTO names a new service owner on or before their last working day or the day the change takes effect. Where a cloud service in the cloud service record is found to have no service owner, the CTO is told, and within 5 working days names one.
6. Accounts and Access
- An account is opened for [Company]'s work only with a cloud service that section 4 allows to be used. It is opened in [Company]'s name and with a work email address.
- No member of staff uses for [Company]'s work an account with a cloud service that they hold for themselves, or puts [Company]'s information into one. This does not apply to an account with a messaging service that another of [Company]'s rules lets staff use for [Company]'s work, which is used only as that rule allows.
- Where a supplier lets [Company] manage all the cloud accounts that it has with that supplier together, every cloud account that [Company] has with the supplier is managed in that way, and none is opened outside it.
- At least two members of staff are able to administer [Company]'s account with each cloud service that holds confidential information, and the cloud service record names them.
- Staff are given access to a cloud service, and that access is changed and taken away, under [Company]'s rules for access control. Staff sign in to a cloud service as [Company]'s rules for passwords and multi-factor authentication require.
- The account with which a cloud account was opened, and any other account to which the supplier gives full control of a cloud account, is used only for a task that an account with less control is not able to do. The person who uses it records each use, and each use is reviewed within 5 working days by the CTO, or by a person the CTO has named in writing where the CTO is the one who used it.
- A cloud service is connected to another service, or given access to [Company]'s information in another service, only with the approval of the CTO or of a person the CTO has named in writing. The connection is removed when it is no longer needed.
- When a member of staff who administers [Company]'s account with a cloud service leaves [Company] or stops doing that work, the service owner makes sure, on or before their last working day or the day the change takes effect, that another member of staff is able to administer it and that the cloud service record is changed.
7. Settings
The service owner of a cloud service that holds confidential information makes sure that its settings meet this section. They are set before confidential information is put into the service or, for a cloud service that section 4 lets carry on being used, within the time that section 4 gives.
- Sign-in: staff sign in to the service as [Company]'s rules for passwords and multi-factor authentication require, and a way of signing in that those rules do not allow is turned off wherever the service lets it be turned off.
- What each account can do: each account is able to see and change only what the person's work needs, and no more people are able to administer the service than the work needs.
- Sharing: information in the service is shared outside [Company] only with the people and the services that the work needs. Sharing with anyone who holds a link is turned off for confidential information, and for other information unless the service owner has decided that the work needs it.
- Open to the internet: nothing in the service that holds confidential information is able to be read from the internet without signing in.
- Record of activity: the service's own record of sign-ins and of changes to its settings is turned on wherever the service offers one.
- Connections: the only services connected to the service are those approved under section 6.
- New features: a feature that uses [Company]'s information in a new way, such as an AI feature, is turned on only after the service owner has confirmed what the feature does with that information.
Where a cloud service does not offer one of these settings, its service owner records that in the cloud service record, and the CTO, or a person the CTO has named in writing, decides whether confidential information is put into the service and records the decision.
The CTO makes sure that the security settings of each service that a supplier runs for [Company], and that holds its confidential information, are checked when the service is first set up and at least every 12 months. For a cloud service that section 4 lets carry on being used, the first check is made when its settings are set under this section. Each check compares the settings of the service with this section. A setting that the service offers and that does not meet this section is put right or has an exception under section 10, and the day of the check and what it found go in the cloud service record.
Where a service owner learns that a supplier has changed a cloud service in a way that affects one of these settings, or has added a feature that uses [Company]'s information in a new way, the service owner tells the CTO and checks the settings again within 30 days.
A change to the settings of a cloud service that is a change under [Company]'s rules for change management is made as those rules require.
8. Information in a Cloud Service
- Confidential information is put only into a cloud service that section 4 allows to be used for it.
- The service owner of a cloud service that holds confidential information records in the cloud service record the countries in which the supplier holds [Company]'s information. Where the service lets [Company] choose where its information is held, the service owner makes the choice with the agreement of the CTO, or of a person the CTO has named in writing, and records it.
- Where a contract with a customer limits the countries in which customer data that [Company] holds under that contract may be held, that data is put only into a cloud service that holds it in those countries.
- Nothing in this section replaces what [Company]'s rules on personal data require before personal data is put into a cloud service or is held in another country.
- Where a service owner learns that a supplier has changed, or plans to change, the countries in which it holds [Company]'s information, the service owner tells the CTO, and the cloud service record is changed within 30 days.
- Where a cloud service that holds confidential information lets [Company] hold the keys that encrypt its information, the CTO decides whether [Company] holds them, and the decision is recorded in the cloud service record.
- For a cloud service that [Company] could not carry on its work without, [Company] keeps, outside the service, a copy of the information that it holds in the service, in a form it can use, unless the CTO has decided that the copies the supplier keeps are enough and has recorded the decision and the reason for it in the cloud service record.
- Restoring from a copy that [Company] keeps under this section is tried at least every 12 months, and the day and the result go in the cloud service record.
- For a cloud service that [Company] could not carry on its work without, the service owner confirms at least every 12 months that [Company] is still able to take its information out of the service in the way that its entry gives, and enters the day in the cloud service record.
9. Leaving a Cloud Service
When [Company] stops using a cloud service, including one that was on trial, its service owner makes sure that the steps below are carried out.
- The service owner tells the CTO before the use ends, or as soon as it has ended where it ends without warning.
- [Company] takes a copy of any of its information that it still needs from the service, in a form it can use, before its access to the service ends.
- Before a cloud account is closed, every system that [Company] runs in it is shut down and removed, and every key and other secret that was created in it is taken out of use.
- Every account that staff hold with the service is closed, every connection between the service and another service is removed, and every web address of [Company]'s that leads to the service is removed or pointed elsewhere.
- The supplier is asked to delete [Company]'s information from the service and from the copies that it keeps. For a cloud service that held confidential information, the service owner asks the supplier to confirm in writing that it has done so.
- The CTO, or a person the CTO has named in writing, confirms within 30 days of the day the use ended that these steps are complete. The day the use ended, the day the steps were completed and any confirmation from the supplier go in the cloud service record.
- Where a supplier tells [Company] that it will end a cloud service, or ends one without warning, the service owner tells the CTO as soon as they learn of it.
10. Exceptions, Breaches and Review
An exception to a rule in this policy is requested from and approved in writing by the CTO, with the reason and any conditions recorded, and lasts no longer than 12 months unless it is renewed in the same way. Where the CTO is the one who asks for the exception, the CEO approves it instead. An exception that applies to a cloud service is recorded in its entry.
Using a cloud service for [Company]'s work that section 4 does not allow to be used, opening or using an account other than as section 6 allows, putting confidential information into a cloud service that section 8 does not allow it to be put into, and hiding a cloud service from the CTO are breaches of this policy. A breach may lead to disciplinary action up to dismissal, in line with [Company]'s disciplinary process and the employment law of the country where the person works; for contractors and other non-employees it may lead to the engagement ending. Nobody is penalized for reporting, in good faith, a cloud service that is being used without approval or a mistake of their own.
The CTO reviews this policy at least every 12 months and after any significant change to [Company]'s systems, to the cloud services it uses or to the way its staff work, and each change to this policy is approved by the CEO.
Disclaimer
This document is provided for informational purposes only and does not constitute legal advice. It is provided "as is", without warranty of any kind, express or implied, and no liability is accepted for any loss or damage arising from its use. It is used at your own discretion. Review it with a qualified adviser before adopting it.